Open pcaffardi opened 5 years ago
guysoft
commented
5 years ago What is the contents of /boot/config.txt afterwards?
I am not sure how this can happen, because FullPageOS just adds stuff on top of Raspbian, the non-acceleration version has nothing out of the ordinary.
Have you tried 0.9.0 which is stable?
Another wild guess would be
pcaffardi
commented
5 years ago I appended these lines to /boot/config:
hdmi_drive=1
hdmi_group=2 hdmi_mode=87 hdmi_timings=480 0 0 20 2 272 1 2 2 4 0 0 0 50 0 6528000 6
I just tried the 0.9.0 stable version with same behaviour. I am using a 3A power supply, that works with any other distribution but this one. I tried raspbian with same SD card and it does work.
This is the video showing my test: https://www.youtube.com/watch?v=FCrcnshbmmI
guysoft
commented
5 years ago Ok, its not the resize of the partition resize, because it boots after it, then it scans the drives with fsck and reboots again.
Another thought, the no-acceleration image has this set in the gui module, If you are having a hard time, I can try building a nightly (but it would be faster if you just try removing that).
echo "gpu_mem=128" >> /boot/config.txt
You can try removing gpu_mem=128 from /boot/config.txt.
Source: https://github.com/guysoft/CustomPiOS/blob/devel/src/modules/gui/start_chroot_script#L38
Please update, because I might need to remove that line in the no-acceleration version. (Note I am trying to narrow what is different in FullPageOS in relation to raspbian, since we know that works, and the good news there isn't much).
marria05
commented
5 years ago I'm seeing a very similar issue. I'm using a Raspberry Pi to feed a tile on a large multiscreen monitor wall. The Pi is connected to an HDMI to SDI converter (Blackmagic Micro Converter), which then goes off into the video wall. The first boot works, then every subsequent boot causes screen corruption, my WFM thinks the output is 1080p30, but the Pi thinks it's 1080p60. I've tried setting the mode manually, but it always defaults to 1080p60 and tvservice says there are no usable modes available for use on the screen.
If I put a vanilla copy of Raspbian on it, it works, and I'm able to set the correct output resolution and framerate (in my case, this is 1080i50). tvservice also lists a whole bunch of available CEA compatible modes.
The only way I've been able to make FullPageOS work is to plug it directly into an HDMI monitor. But regardless what I set in /boot/config.txt it always seems to default to 1080p60.
guysoft
commented
5 years ago @marria05 There was already a report on blackmagic controllers causing problems, see: https://github.com/guysoft/FullPageOS/issues/171#issuecomment-366337296
marria05
commented
5 years ago This isn't the 4K version, just a standard Micro Converter.
https://www.blackmagicdesign.com/products/microconverters
These ones only do up to 3G-SDI (1080p60).
It's just odd that it behaves perfectly with bog standard Raspbian.
What were you doing?
I use a custom touchscreen panel attached to HDMI. It works by adding these lines to /boot/config.txt:
hdmi_drive=1 hdmi_group=2 hdmi_mode=87 hdmi_timings=480 0 0 20 2 272 1 2 2 4 0 0 0 50 0 6528000 6
These settings are well tested with any other distribution (raspbian, etc...).
What did you expect to happen?
I expected to see the HDMI output on my touch display.
What happened instead?
I tried it with last versions of FullPageOS (accelerated and not) and it works ONLY at first boot, but when the system reboots after expanding the file system, the HDMI output is broken (strange all while with slow changing contents), but anything else works (SSH and so on).
Was there an error message displayed? What did it say?
No error at all. Only white screen immediatly at boot.
Version of FullPageOS?
2018-07-22_2018-06-27-fullpageos-no-acceleration-stretch-lite-0.10.0 2018-09-13_2018-06-27-fullpageos-stretch-lite-0.10.0
Screenshot(s) showing the problem:
Trust me. Anything fine before the first reboot, after the display shows always white screen with strange lines changing while booting (maybe wrong HDMI settings but WHY only after first reboot?).