[opensuse-arm] RPi2, Tumbleweed and "official" 7" RPi touchscreen
Hi, I've had one RPi2 running headless with Tumbleweed for quite some time now, and it does fine, so thanks everyone for making that work! That said, I now have acquired the "official" RPi 7" touchscreen to use with a second RPi2, and it actually displays the text console nicely on first boot of the Build 385 JeOS image, but on second boot it stays completely black (not even the backlight is on). In addition, the network interface also does not come up (same as on first boot), so the build gets completely unusable for me. I tried the old build 307 that I had used initially to get the other RPi2 up months ago, and the screen is completely black with that, but the network is fine and I could update it to a current Tumbleweed, which it still boots fine and is accessible from the network. That said, the screen stays dark on this as well. Given that the first boot with build 385 works and AFAIK uses the same kernel and probably bootloader, and the difference is there right from booting the system, it feels like it can't be that hard to get it working in the end. That said, the difference has to be in some parameters or things available during boot. I attached two dmesg outputs, one ("noscreen") from the updated-to-current system that can be accessed remotely, one ("screenworking") from a build 385 first boot. One difference that strikes me there is that the non-working version says (omitting times): simple-framebuffer 3db79000.framebuffer: framebuffer at 0x3db79000, 0x81800 bytes, mapped to 0xb7d00000 simple-framebuffer 3db79000.framebuffer: format=r5g6b5, mode=592x448x16, linelength=1184 simple-framebuffer 3db79000.framebuffer: fb1: simplefb registered! The working version has the following instead: simple-framebuffer fdb3f000.framebuffer: framebuffer at 0xfdb3f000, 0xbb800 bytes, mapped to 0xb7d00000 simple-framebuffer fdb3f000.framebuffer: format=r5g6b5, mode=800x480x16, linelength=1600 simple-framebuffer fdb3f000.framebuffer: fb1: simplefb registered! The "mode=800x480x16" actually fits this screen correctly. Any idea what I can try to get it working? I have found out enough to play with kernel command line parameters by editing boot.script and regenerating boot.scr from it, but I got stuck there as removing this from the commandline didn't help and I'm not sure what else I can do there that may help. That said, once the display actually shows stuff, the second question will be the touch input - if the rpi-ft5406 driver available in the kernel right now? I saw there are sources for it in https://github.com/raspberrypi/linux/blob/rpi-4.5.y/drivers/input/touchscree... at least for 4.5, not sure for how far back they exist/work. Thanks, KaiRo
With my configuration listed below, the newest build (2016.03.04-build3) still lights up the screen backlight (contrary to an older updated build) but it looks like it's not even launching the firstboot right now, the green activity LED does not show that the Pi2 would do anything. KaiRo Robert Kaiser schrieb:
Hi,
I've had one RPi2 running headless with Tumbleweed for quite some time now, and it does fine, so thanks everyone for making that work!
That said, I now have acquired the "official" RPi 7" touchscreen to use with a second RPi2, and it actually displays the text console nicely on first boot of the Build 385 JeOS image, but on second boot it stays completely black (not even the backlight is on). In addition, the network interface also does not come up (same as on first boot), so the build gets completely unusable for me.
I tried the old build 307 that I had used initially to get the other RPi2 up months ago, and the screen is completely black with that, but the network is fine and I could update it to a current Tumbleweed, which it still boots fine and is accessible from the network. That said, the screen stays dark on this as well.
Given that the first boot with build 385 works and AFAIK uses the same kernel and probably bootloader, and the difference is there right from booting the system, it feels like it can't be that hard to get it working in the end. That said, the difference has to be in some parameters or things available during boot.
I attached two dmesg outputs, one ("noscreen") from the updated-to-current system that can be accessed remotely, one ("screenworking") from a build 385 first boot.
One difference that strikes me there is that the non-working version says (omitting times): simple-framebuffer 3db79000.framebuffer: framebuffer at 0x3db79000, 0x81800 bytes, mapped to 0xb7d00000 simple-framebuffer 3db79000.framebuffer: format=r5g6b5, mode=592x448x16, linelength=1184 simple-framebuffer 3db79000.framebuffer: fb1: simplefb registered!
The working version has the following instead: simple-framebuffer fdb3f000.framebuffer: framebuffer at 0xfdb3f000, 0xbb800 bytes, mapped to 0xb7d00000 simple-framebuffer fdb3f000.framebuffer: format=r5g6b5, mode=800x480x16, linelength=1600 simple-framebuffer fdb3f000.framebuffer: fb1: simplefb registered!
The "mode=800x480x16" actually fits this screen correctly.
Any idea what I can try to get it working? I have found out enough to play with kernel command line parameters by editing boot.script and regenerating boot.scr from it, but I got stuck there as removing this from the commandline didn't help and I'm not sure what else I can do there that may help.
That said, once the display actually shows stuff, the second question will be the touch input - if the rpi-ft5406 driver available in the kernel right now? I saw there are sources for it in https://github.com/raspberrypi/linux/blob/rpi-4.5.y/drivers/input/touchscree... at least for 4.5, not sure for how far back they exist/work.
Thanks, KaiRo
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Robert Kaiser schrieb:
That said, I now have acquired the "official" RPi 7" touchscreen to use with a second RPi2, and it actually displays the text console nicely on first boot of the Build 385 JeOS image, but on second boot it stays completely black (not even the backlight is on). In addition, the network interface also does not come up (same as on first boot), so the build gets completely unusable for me.
Some positive news: In the current 2016.03.25 image both the screen and the ethernet port work now, even on second boot! \o/ I now have an minimal LXQt desktop running on that screen, with Firefox to show a web-based dashboard (if I could boot into a Firefox right away and have some kind of windowmanager so "popup" windows work, I wouldn't even need a desktop environment to run, I usually just want to display some web-based UI).
That said, once the display actually shows stuff, the second question will be the touch input - if the rpi-ft5406 driver available in the kernel right now?
I see I can modprobe it and then lsmod lists it, so it seems to exist. Need to play with how to actually get it working with Xorg, though. Cheers, Robert Kaiser -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
I have never been able to get the gui working 100% no matter what i do
its stuck in 800x480 resolution, however to get things like firefox
and certain GUI's working correctly, you have to install Mesa-libEGL1
and Mesa-libEGL-devel packages, this will prompt you to remove the
raspberypi-userland package, you want to do this, have mesa replace
it, it is the only way you will get anything to actually work
correctly. Hopefully this helps, it sure would be nice if someone
could figure out why its stuck in 800x480, so far I have not had any
luck yet, anyone has pointers please let us know.
On Fri, Mar 25, 2016 at 10:10 PM, Robert Kaiser
Robert Kaiser schrieb:
That said, I now have acquired the "official" RPi 7" touchscreen to use with a second RPi2, and it actually displays the text console nicely on first boot of the Build 385 JeOS image, but on second boot it stays completely black (not even the backlight is on). In addition, the network interface also does not come up (same as on first boot), so the build gets completely unusable for me.
Some positive news: In the current 2016.03.25 image both the screen and the ethernet port work now, even on second boot! \o/
I now have an minimal LXQt desktop running on that screen, with Firefox to show a web-based dashboard (if I could boot into a Firefox right away and have some kind of windowmanager so "popup" windows work, I wouldn't even need a desktop environment to run, I usually just want to display some web-based UI).
That said, once the display actually shows stuff, the second question will be the touch input - if the rpi-ft5406 driver available in the kernel right now?
I see I can modprobe it and then lsmod lists it, so it seems to exist. Need to play with how to actually get it working with Xorg, though.
Cheers, Robert Kaiser
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- Michael Emory Cerquoni -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Op zaterdag 26 maart 2016 00:08:18 schreef Michael Emory Cerquoni:
I have never been able to get the gui working 100% no matter what i do its stuck in 800x480 resolution, however to get things like firefox and certain GUI's working correctly, you have to install Mesa-libEGL1 and Mesa-libEGL-devel packages, this will prompt you to remove the raspberypi-userland package, you want to do this, have mesa replace it, it is the only way you will get anything to actually work correctly. Hopefully this helps, it sure would be nice if someone could figure out why its stuck in 800x480, so far I have not had any luck yet, anyone has pointers please let us know.
@Michael I have the feeling you are talking about a screen connected via the HDMI interface, where Robert is talking about a touchscreen connected via that special RPi interface. So please start another discussion on your problem with the HDMI connected screen. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Michael Emory Cerquoni schrieb:
I have never been able to get the gui working 100% no matter what i do its stuck in 800x480 resolution, however to get things like firefox and certain GUI's working correctly, you have to install Mesa-libEGL1 and Mesa-libEGL-devel packages, this will prompt you to remove the raspberypi-userland package, you want to do this, have mesa replace it, it is the only way you will get anything to actually work correctly. Hopefully this helps, it sure would be nice if someone could figure out why its stuck in 800x480, so far I have not had any luck yet, anyone has pointers please let us know.
Yes, sure you want to replace those packages, that's what I did as well. Resolution isn't an issue for me though, as this screen actually is 800x480, so that's what I want. Right now, my issues are that the touch functionality seems to not work, and I really wonder why the Firefox in the Tumbleweed ARM repo is about a year old (34.0.5) instead of at least somewhat current. Cheers, Robert Kaiser -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (3)
-
Freek de Kruijf -
Michael Emory Cerquoni -
Robert Kaiser