Slackware64-current kernel 6.6.7 and i915 module crash and blank screen
I have a 2006vintage Lenovo Thinkpad T510 I use for portable computing sometimes and Slackware64-current testing. It's been running just fine on Current for the past year. The recent upgrade to kernel-6.6.7, however, results in some sort of i915 crash and no viable framebuffer. I tried both generic and huge version. System is useable via ssh, just no display. I've reverted to 6.1.66 that works for the intel GPU. No issues with AMD GPUs (so far!).
laptop is i7-620M integrated iGPU i915 Code:
smod |grep i915 Code:
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller]) Code:
Dec 16 14:38:00 arwen kernel: pci 0000:00:00.0: Intel HD Graphics Chipset Code:
Dec 16 13:12:17 arwen kernel: ------------[ cut here ]------------ There is some chatter on fedora, redhat, *buntoo etc on similar problems with kernel 6.5.x and 6.6.x. Posting here to see if any other old timers with antique laptops are also having intel GPU issues. |
I run 6.6.7, Slackware, i915 video, have no problem. I build my own kernel.
|
Quote:
Perhaps there is some change in the Kernel (series) that we're unaware of (Perhaps study Linus release statements for Kernel 6.5 and 6.6 on Kernel mailing lists). I assume you installed a new firmware package as well. You use any boot parameters with that? Anyways, your trace points to udevd being the problem in this case.. And/or check line 3497 in drivers/gpu/drm/i915/display/i9xx_wm.c:3497, for further details. Might be somewhat related, some regression back in 2018, causing a similar issue with modprobe. https://bugs.freedesktop.org/show_bug.cgi?id=105992 |
Quote:
With the 6.6.6 and 6.7-rc2 kernels there were spontaneous reboots, so I've switched to the NVIDIA-Linux-x86_64-535.129.03.run (production) driver. So far, so good. Perhaps, the problem could be with the recently updated mesa or xorg packages? Just a thought. :scratch: |
Mesa sometimes (constantly?) drops old GPUs support
I don't think Slackware-current is the best choice for old hardware But, you could give this a try: https://www.linuxquestions.org/quest...ml#post6409053 |
@marav, I don't think this is a mesa issue, since screen stops during boot. system is up, just headless with no intel frame buffer and hence no video on the laptop panel.
@RandomTroll, how old is your intel GPU? Recent or vintage like mine? @cwizardone, The nvidia issue is was different. Slackware loads and runs as expected, via ssh remote headless, video issue starts when i915 and drm loads during boot, way before login and before startx. I can even log in (blind) and try to 'startx'. It tries, finds monitor params, modes, EDID, but is unable to set a modeline. As I said in the OP, fully updated Slackware64-Current with kernel-6.6.7, no intel video, and rolling back ONLY the kernel to 6.1.66 restores full function including X.Org and Xfce. No boot parameters. It's not some old bug from 2018 since 14.x through 15.0 and Current up to now have worked just fine. No initrd. Same modules loaded. hardware is detected. LILO is simple: Code:
# Start LILO global section |
Quote:
Perhaps see if there is something relevant here: https://lkml.org/lkml/2023/10/30/11 And there should be a similar one for 6.5 https://lkml.org/lkml/2023/8/27/348 This line: "Could not determine valid watermarks for inherited state" probably is related if you trace that line 3497 to something relevant. Meanwhile you could test with "nomodeset" as a Kernel parameter. |
Quote:
Code:
intel_gpu_top Quote:
|
Well, this is weird. Since this lappy INtell GPU seems to be still supported in the kernel, and only slightly older than RandomTroll, and I use it to test stuff, I decided to reinstall a fresh Slackware64-currnt as of 17-Dec updates. Blank screen, but otherwise operational (headless access via ssh) Tried "nomodeset i915_modeset=0" and I get a nice old timey 1024x768 frame buffer and X (Xfce) works. No GPU acceleration or other resolution options.
But wait, there's more! I fire up the latest Slackware64-live-current (kernel 6.6.7) on a USB and *POOF* everything works. Pretty KDE/Plasma. Correct resolution. xrandr reports choices for LVDS-1 and the presence of the other VGA and DP ports. Weird. So now I have to figure out why liveslak-current works but a regular clean, full install with lilo (MBR) boot does not. The Game's AFOOT! |
Hmm.. So, the driver and firmware of 6.6.7 works (given the right conditions at least).
What happens if you boot into the installation WITH the Slackware installation disk (as described initially when booting disk)? (skip lilo) |
Sadly, upgrading to Slackware-Current (6.6.8 Kernel) didn't change anything.
I have a Sandybridge CPU. :( |
Quote:
regards Henrik |
Quote:
Code:
grep "acceleration enabled" /var/log/Xorg.0.log and on your installed -current? |
This laptop is pre-UEFI, so uses old time BIOS boot. The slackware64-currt install boots fine since huge.s does set "nomodeset". There is kms.s which replicates the problem. liveslak USB boots via syslinux and I haven't looked into those boot parameters yet,
I did discover, that once laptop is booted, pressing Fn-F4 key combo to hibernate (or closing the lid, which I stumbled upon), and the pressing power button to wake up, resets the LCD screen and all is normal. Screen power management? Is this dummy selecting on of the unused video ports (VGA, DisplayPort)? 'acpi=off' is no good. At least now I know where to go looking. @franzen, re-read my earlier posts. This blank screen during/after boot occurs BEFORE running X.org with 'startx' |
No display issues with a fully upgraded -current (kernel 6.6.8) on my old (15 yrs) Asus eee 900. Inxi gives the following gpu info:
Code:
intel mobile 915GM/GMS/910GML Express Graphic |
All times are GMT -5. The time now is 03:26 AM. |