[SOLVED] Slackware64-current kernel 6.6.7 and i915 module crash and blank screen
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
There are different acpi versions that have names of windows versions. Perhaps the kernel changed the default acpi version it selects for your laptop, and you need to force a different one with kernel boot line parameter? A shot in the dark, may not work. I don't have any hardware from that intel generation.
If I'm in runlevel 4 then I have to ctl-alt f10 followed by ctl-alt f7 to get the displaymanager login screen
Then the laptop appears to work normally.
Interesting that my desktop PC also on Slackware-Current, is badly behaved with respect to switching to low power states. It's an i7-3770K with a descrete AMD graphics card.
If it goes to sleep I have to restart network manager to get the network adapter working and if I try to logout of reboot then KDE freezes for a minute or so. I was full Wayland and have switched to x11. This appears to have fixed the freeze.
$ lspci -v
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller
Flags: bus master, fast devsel, latency 0, IRQ 30
Memory at f0000000 (64-bit, non-prefetchable) [size=4M]
Memory at e0000000 (64-bit, prefetchable) [size=256M]
I/O ports at 5000 [size=64]
Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
Kernel modules: i915
i810 is super old, so it's probably not that. You can search on wikipedia for Intel "generations" and it will show CPU's (and GPU's) for that generation too (Pentium 3 I think it was). But i810 was the only specific mention.. Other drivers had been removed too, without being named..
Probably isn't related, but it could be. What's more likely is that all these recent changes in the i915 driver might have introduced new issues to people with some cards (they work when people roll back to earlier Kernel version). It's difficult to know without going really indepth in the changelogs etc. But from what I've seen from changelogs just from Linus 6.4, 6.5, 6.6, there are really alot of changes to i915. Probably before that as well. Don't know if it's within the norm, or an abnormal amount of changes though..
bump this thread: does anyone know if any recent kernel has fixed this issue?
a side question: if I keep the old kernel (6.1.66) and upgrade other -current packages, will it be any issues? I recently encounter odd issues (seems due to libc) and I suspect it's due to kernel is compiled with old libc but -current packages is compiled with a new libc, not sure if my guess is true.
As of Slackware64-Current kernel 6.6.15 the screen on my intel-based Lenovo Thinkpad T510 (June 2010) still goes blank when i915 kms kicks in during boot scrawl. As I mentioned previously, the workaround is to wait until the boot cycle is complete (0.5 -1 min), press Fn-F4 (hibernate key), wait until power key starts the rhythmic hibernation light pulse, tap the power key to wake up, and all is back to normal. (login, startx etc).
For me this is now a minor annoyance (I don't reboot very often) and everything else seem seems to work. Well, except for the wifi chip which appears to be fried.
update. (and also be advised that I have been using and installing Slackware for 25+ years, and while no expert, do know how to install and boot up a box).
This issue does not effect my AMD Ryzen boxes with amdgpu.
This issue has plagued me since Current added 6.6.x kernel. As I mentioned above, 6.1.x and earlier there where no issues. After some more poking around and upgrading to latest current, kernel 6.6.27 and now both the Lenovo Thinkcentre M91p SFF and Lenovo Thinkpad T510 are effectively headless when installed via the stock Slackware64-current boot USB, newest updates, and set up with lilo. Slackware64-15.0 installs and boots fine, as per usual since 14.0 and 14.2. No issues. Heck, I even had the M91p running Freebsd 13 for a few months (not bad, but setting up X was a horror given my Slackware muscle memory).
When i915 modesetting kicks in the screen goes blank. Until then you can see the boot scrawl. I can ssh in; I can even log in "blind".
Now, booting liveslack 1.8.1 (09-APR-2024) works fine! You can see the boot scrawl to the point were modesetting kicks in, the screen blinks blank and comes back up with better font/text resolution. Assuming I found the correct files; looking at the grub boot line:
Code:
menuentry "Start Slackware64 current SLACKWARE liveslak-1.8.1.1 ($sl_lang)" --hotkey b {
linux ($root)/boot/generic load_ramdisk=1 prompt_ramdisk=0 rw printk.time=0 kbd=$sl_kbd tz=$sl_tz locale=$sl_locale xkb=$sl_xkb
initrd ($root)/boot/initrd.img
}
the syslinux boot:
Code:
label live
menu label Start SLACKWARE Live
menu default
kernel /boot/generic
append initrd=/boot/initrd.img load_ramdisk=1 prompt_ramdisk=0 rw printk.time=0 kbd=us
text help
Slackware64-current, kernel 6.6.25.
Add 'load=nvidia' to the commandline
if you have a recent NVIDIA card.
endtext
Well...that didn't work. I can boot and run Slackware64 Current Live USB just fine, install it to the hard drive, and i915 still flips out when rebooting via lilo from MBR. What the heck?
From dmesg, and trying previous suspend/wake trick (at
Guess I'll revert back to Slackware64 15.0 until I can find out what the heck is happening with i915 modeset and power management on older embedded Intel IGP (Lenovo).
Solved.
During installation of Slackware64-Current (be sure to set up a small GPT BIOS boot partition type EF02 before your root and swap), skip both elilo and lilo installation. When done installing/configuring, exit setup to shell - do not reboot. Then follow https://docs.slackware.com/howtos:sl...ut_uefi#grub_2
to set up for grub2 boot.
Solved.
During installation of Slackware64-Current (be sure to set up a small GPT BIOS boot partition type EF02 before your root and swap), skip both elilo and lilo installation. When done installing/configuring, exit setup to shell - do not reboot. Then follow https://docs.slackware.com/howtos:sl...ut_uefi#grub_2
to set up for grub2 boot.
So, what is the issue exactly? Is this issue caused by lilo/elilo?
Or is it rather that the KMS driver seems to require UEFI and/or GPT suddenly? Or perhaps you are using UEFI bios, but set up the system without UEFI boot?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
verlay:loop:efivarfs:xhci-pci
