If you provide a dt-blob.bin to do the pin remuxing, then you'll see the rainbow screen.
Hmm. Odd. So you just have the LCD and HDMI connected? If you disconnect either does it start up?DougieLawson wrote: ↑Mon Jun 25, 2018 7:01 pmI gave this a try on my RPi3B with the Official LCD. I got the rainbow screen (on both the LCD and the TV) but the boot didn't continue from that point.
That 3B is set-up to boot from a USB stick.
It was already running 4.14.50-v7+ #1122 before I started the experiment.
I may try again with a USB serial console on GPIO14/15 enabled. I should also try a regular SDCard rather than the USB stick.
Correct. It's mostly Videocore changes and that bit of HW is the same across the Pi range.
Oh, I was mislead by the first post of this forum entry that stated: "These instructions assume a Pi2B/3B board."jamesh wrote: ↑Tue Jul 03, 2018 3:09 pmCorrect. It's mostly Videocore changes and that bit of HW is the same across the Pi range.
Ah, yes. Problem is that James only provided a kernel7.img (for Pi2/3).
I didn't test it under those circumstance, so possible. Sounds like it simply not booting at all. Probably the start_x.elf is not starting up, or even being loaded. No idea why not.procount wrote: ↑Tue Jul 03, 2018 3:27 pm@JamesH - I think there is a problem with the new start_x.elf that prevents it running in a version of Raspbian that is installed via NOOBS/PINN, in my case it is on /dev/mmcblk0p6.
I repeated my 2nd test attempt on the same version of Raspbian, but installed by PINN. Copied over Kernel7.img and start_x.elf. It all works fine on a reboot, until I set start_x=1 and then it doesn't boot. Both screens are blank and the network is not working - no ssh or vnc although they are enabled and tested working before setting start_x=1.
Hmm. Thought the overscan should be the same as before. I'll need to check.procount wrote: ↑Wed Jul 04, 2018 10:46 amAnother difference with this start_x.elf is that it defaults to overscan enabled, whereas start.elf defaults to overscan disabled. I had to force `disable_overscan=1` to make the behaviour the same. (I didn't check if this applies to the original start_x.elf as well). Surely these should be the same, or is there another reason I'm not aware of?
I got a bit further using this for /etc/X11/xorg.conf, but the desktop is only visible on one screen, and all it has on it is the wallpaper and a waste basket - no menu or anything else. I can swap it between the screens, but not get both up at the same time.procount wrote: ↑Tue Jul 03, 2018 1:24 pmI copied /usr/share/X11/xorg.conf.d/99-fbturbo.con to /etc/X11/xorg.conf, changing /dev/fb0 to /dev/fb1, but I this doesn't seem sufficient as it does nothing. I guess I need additional screen and monitor sections? Anyone got an example xorg.conf file that works?
Code: Select all
Section "Device" Identifier "FBDEV 0" Driver "fbturbo" Option "fbdev" "/dev/fb0" EndSection Section "Device" Identifier "FBDEV 1" Driver "fbturbo" Option "fbdev" "/dev/fb1" EndSection Section "Screen" Identifier "VGA" Device "FBDEV 0" Monitor "Monitor name 0" EndSection Section "Screen" Identifier "HDMI" Device "FBDEV 1" Monitor "Monitor name 1" EndSection Section "ServerLayout" Identifier "Default Layout" Screen 0 "VGA" Screen 1 "HDMI" RightOf "VGA" EndSection
Code: Select all
ls /dev/fb* -> /dev/fb0