No console output/bootup on Bitrig anymore #381
Comments
|
Are you using initramfs? If so try test firmware here: |
|
Yes. Exactly! I had the issue that I can't load my fully blown kernel to kernel_address 0x00300000 directly. Apparently it's too big to be put there like that. Instead I have a tiny program loaded as kernel to 0x8000 and the actual kernel loaded as initramfs. The tiny program just jumps to 0x00300000. Your posted firmware makes it work again. |
popcornmix
added a commit
that referenced
this issue
Feb 27, 2015
kernel: staging: add FBTFT drivers See: raspberrypi/linux#836 kernel: dts: overlay: add support for various displays See: raspberrypi/linux#853 kernel: BCM2835-V4L2: Fix compliance test failures See: raspberrypi/linux#856 firmware: ldconfig: Fix for off by one on config list count See: #374 See: #381 See: #378
popcornmix
added a commit
to Hexxeh/rpi-firmware
that referenced
this issue
Feb 27, 2015
kernel: staging: add FBTFT drivers See: raspberrypi/linux#836 kernel: dts: overlay: add support for various displays See: raspberrypi/linux#853 kernel: BCM2835-V4L2: Fix compliance test failures See: raspberrypi/linux#856 firmware: ldconfig: Fix for off by one on config list count See: raspberrypi/firmware#374 See: raspberrypi/firmware#381 See: raspberrypi/firmware#378
|
Can you confirm latest rpi-update firmware fixes the issue. |
|
Works well for me, closing the issue, thanks! |
neuschaefer
pushed a commit
to neuschaefer/raspi-binary-firmware
that referenced
this issue
Feb 27, 2017
kernel: staging: add FBTFT drivers See: raspberrypi/linux#836 kernel: dts: overlay: add support for various displays See: raspberrypi/linux#853 kernel: BCM2835-V4L2: Fix compliance test failures See: raspberrypi/linux#856 firmware: ldconfig: Fix for off by one on config list count See: raspberrypi#374 See: raspberrypi#381 See: raspberrypi#378
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I'm porting the Bitrig operating system to the raspberry pi and have bootup issues since cc47954.
In the commit before, I get proper serial/console output. Since that commit, updated by copying start*.elf and fixup*.dat, I do not get any output anymore.
Did something special change about the console in that commit? What has changed in the firmware?
The text was updated successfully, but these errors were encountered: