You are not logged in.
patrick_g wrote:rootinthemood wrote:Yes I tried that before but did not work for me.
However just an early KMS start of the i915 driver did it for me(without the kernel blacklist option). Tried a bunch of restarts and so far so good.I still see this issue even after upgrading to 6.9.3.
I would like to try your solution. How do you set an early KMS start of the i915 driver?https://wiki.archlinux.org/title/Kernel … _KMS_start
So put 'i915' in MODULES and regenerate initramfs.
This works for me, but for some reason it disables wayland. What I mean by this is that login in (using GDM) launches automatically a GNOME session on x11. Also GDM doesn't show any option for launching GNOME on Wayland. The wiki https://wiki.archlinux.org/title/Kernel … _KMS_start doesn't specify anything about wayland having to be handled any differently. Any clues?
Offline
GDM will do that when the nvidia driver is loaded without some precautions, if that's the case for you, see: https://wiki.archlinux.org/title/GDM#Wa … DIA_driver
i915 on it's own should not be a bearing factor for this behaviour.
Offline
Since I don't have NVIDIA hardware on this machine I just added i915 and was thus surprised by the behavior. So reverted. Right now I'm on 6.9.6 and things seem to have settled down, but I'll try your approach if they don't. Thank you!
Offline
I am having the same issues with a system 76 laptop and an Nvidia card.
After updating my kernel from the 6.8 to the 6.9 version and rebooting, I'm stuck in the boot sequence.
I see an error :
"Framebuffer coreboot8: probe with driver framebuffer failed with error -17".https://i.imgur.com/UnSh7q4.jpg
Tried to Google this error but found nothing relevant. Any idea?
Offline
Thank you rootinthemood.
I modified my /etc/mkinitcpio.conf to put i915 in MODULES and regenerated initramfs and now the problem appears to be solved.
After 12 boots I haven't seen any boot failure (previously it was approximately one failure for 3 or 4 boots).
If My laptop has Nvidia, putting i915 in MODULES would not work for me. Correct?
Also how does your mkinitcpio.conf looks after being modified to include i915 in MODULES? and how do you regenerate initramfs?
Thanks!
Offline
Does your laptop SOLELY have nvidia? Most laptops have both, and the actual relevant graphics card is normally the integrated GPU. But for nvidia you'd add nvidia nvidia_modeset nvidia_uvm nvidia_drm as listed in: https://wiki.archlinux.org/title/Kernel … _KMS_start -- which also mentions how to regenerate the initramfs.
While you're at it you likely also wan to enable proper modesetting via kernel parameter: https://wiki.archlinux.org/title/NVIDIA … de_setting
Offline
Does your laptop SOLELY have nvidia? Most laptops have both, and the actual relevant graphics card is normally the integrated GPU. But for nvidia you'd add nvidia nvidia_modeset nvidia_uvm nvidia_drm as listed in: https://wiki.archlinux.org/title/Kernel … _KMS_start -- which also mentions how to regenerate the initramfs.
While you're at it you likely also wan to enable proper modesetting via kernel parameter: https://wiki.archlinux.org/title/NVIDIA … de_setting
Yes as you said, My laptop has both, An integrated graphics and Nvidia. I am trying to get a configuration where It only uses Nvidia. For some reason X11 has become unusable, as it freezes completely. Should I still include i915 on modules?
Thanks!
Offline
Unless you have an UEFI setting to completely disable the integrated card that's a logically impossible goal.
Add i915 to the modules, potentially even in addition to the nvidia modules.
Offline
I'm running Arch with kernel 6.10.x on a System76 Lemur Pro (lemp10) and was having this issue. Adding the kernel parameter initcall_blacklist=simpledrm_platform_driver_init didn't work for me. I would get a blank screen at boot. I tried typing in my LUKS password, but the screen just stayed blank.
So instead, I fixed it by enabling early kms start for the intel i915 driver. I'm using dracut, so this is what I did:
Created /etc/dracut.conf.d/earlykms.conf and added the following to the file:
force_drivers+=" i915 "
Then I ran:
sudo dracut-rebuild
My system has been booting up now for several days without issue
Offline
System76 darp6 here with the same problem, been dealing with it for a little while now.
Early KMS i915 does indeed fix the issue.
Anyone have a link to something reported upstream? Should we submit something?
Offline