Bug #315
openXorg/Wayland show black screen when system memory is 4GB or higher
0%
Description
Board: ASROCK G41M-VS3 R2.0
CB Revision: coreboot-4.14-1258-gfbc46a3bfb
When this board has one memory stick with 2GB of ram, or two memory sticks with 1GB and 2GB (3GB total) there's no issue with display; Xorg and wayland (using weston) work as expected. But when there's 4GB or maybe more (two 2GB sticks only available, haven't tried a single 4GB stick) the system works as expected up to just before starting Xorg or wayland, the screen goes black and nothing else happens. Returning to a tty by means of Ctrl-Alt-# 'ing to some other tty doesn't bring display back, neither does exitting/killing Xorg or wayland. Not even forcefully removing and reloading the relevant kernel modules (i915, drm) does anything to bring the display back, display will only comeback with a reboot.
When the screen goes black there's no system freeze of any kind, and the kernel complains with a single line:
"i915 0000:00:02.0: [drm] ERROR CPU pipe A FIFO underrun"
that isn't very helpful for debugging imo.
Attached dmesg loglevel=9 logs of stock bios, coreboot with 4GB (coreboot_bad) and with 2GB (coreboot_good), cbmem console log of coreboot with 2GB (cbmem_good).
Files
Updated by Master Geek over 3 years ago
- File cbmem_bad.log cbmem_bad.log added
- File cbmem_good.log cbmem_good.log added
Updated by Master Geek over 3 years ago
First cbmem_good.log file was made with a build with console log level set to 6 (INFO). The cbmem logs below are from a build with log level 7 (DEBUG).
Updated by Master Geek over 3 years ago
After removing some jumper connectors on the board I was able to boot and start Xorg/Wayland while using 4GB of ram (2 sticks of 2GB each). Have yet to try and relocate the jumpers in the same positions as they were to reproduce the issue but I think that's a quirk of this specific board of mine. The jumpers had to do with something called 'EuP', I think it has to do with power settings but I'm not sure.
There's one for globally enabling/disabling it, and other two for selectively enabling it for Audio and LAN; when I got it booting I noticed audio just stopped working. Linux detected the soundcard as always and it wasn't muted nor was the volume low but there was genuinely no output through the stereo jack of the case. Replacing the jumper for the audio got it enabled.
I think this issue at the very least should have a lower severity/priority now.
Updated by Master Geek over 3 years ago
Honoring PaulePanther's request I document here that it seems 'EuP' (Energy Using Product) is related to a power saving, power efficiency regulation of sorts. As per this document:
"EuP, stands for Energy Using Product, was a provision regulated by European Union to define the power consumption for the completed system. According to EuP, the total AC power of the completed system shall be under 1.00W in off mode condition. To meet EuP standard, an EuP ready motherboard and an EuP ready power supply are required. According to Intel’s suggestion, the EuP ready power supply must meet the standard of 5v standby power efficiency is higher than 50% under 100 mA current consumption."
So it kind of makes sense for it to play bad with coreboot somehow...