2017-07-09, 04:31
(2017-07-08, 22:36)sboa Wrote: Can you help me? I really like your builds!
PS
AlexElec
OK let's try this again.
From what you've said previously your i915 GPU worked up to #0417, but from #0418 onwards you get a blank screen.
I can see in the #0429 kernel log you posted that the i915 GPU on your Sandy Bridge CPU is not being detected/initialised correctly:
Code:
Apr 30 14:18:32 LibreELEC kernel: ALSA device list:
Apr 30 14:18:32 LibreELEC kernel: No soundcards found.
Apr 30 14:18:32 LibreELEC kernel: [drm] Cannot find any crtc or sizes - going 1024x768
Apr 30 14:18:32 LibreELEC kernel: fbcon: inteldrmfb (fb0) is primary device
Apr 30 14:18:32 LibreELEC kernel: Console: switching to colour frame buffer device 128x48
Apr 30 14:18:32 LibreELEC kernel: i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
whereas in #0417 it is working normally:
Code:
May 09 11:34:04 LibreELEC kernel: ALSA device list:
May 09 11:34:04 LibreELEC kernel: No soundcards found.
May 09 11:34:04 LibreELEC kernel: fbcon: inteldrmfb (fb0) is primary device
May 09 11:34:04 LibreELEC kernel: Console: switching to colour frame buffer device 240x67
May 09 11:34:04 LibreELEC kernel: i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
Can you add the parameter "drm.debug=0xe" to your kernel command line (probably in /flash/EFI/BOOT/syslinux.cfg) so that the file looks like:
Code:
DEFAULT linux
PROMPT 0
LABEL linux
KERNEL /KERNEL
APPEND boot=LABEL=System disk=LABEL=Storage ssh quiet drm.debug=0xe
and then reboot into #0417 (ie. working GPU) and run "dmesg | pastebinit".
Then boot into the #0418 build (with non-working GPU) and again run "dmesg | pastebinit".
Paste both links here (note that uploading rar files full of zip files that are themselves full of log files isn't really helping).
You can then remove "drm.debug=0xe" and reboot into whatever version of *ELEC is working for you.
This is the changelog for the 4.10.11 kernel that #0418 introduced: https://cdn.kernel.org/pub/linux/kernel/...og-4.10.11 - there are some i915 changes but I don't know if they're relevant or why they'd only be affecting your hardware and nobody else. There were no kernel config changes in #0418 other than for SpinelPlus remote control (change to module).
Also, check there are no BIOS updates available for your motherboard. It might even be worth resetting your motherboard CMOS.