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.
KV bump -> 5.10.7. NB: i915/drm patch in changelog + libdrm upgrade in SW-current. 24+ hours running & nary a burp | hiccup. (Promising, but, certainly too soon to proclaim victory.) Any other reports from the community?
KV bump -> 5.10.7. NB: i915/drm patch in changelog + libdrm upgrade in SW-current. 24+ hours running & nary a burp | hiccup. (Promising, but, certainly too soon to proclaim victory.) Any other reports from the community?
Mine has also be behaving since .5. Still to early to proclaim the issue is "gone" though.
Agreed, too early. In my case it does seem like a one off though, desktop was running 5.10.4 and had a single lock-up
upon resuming from suspend-to-ram, had no lock-ups at all on other machines including my laptop.
I just experienced a full lockup on my desktop requiring a hard reset button. This is a fully up-to-date 64-current with 5.10.7 running kde5, rebooted yesterday after updates, suspended overnight until I resumed this morning. It worked great for maybe 3 hours until the lockup while konsole was open with mc running, dolphin running & focused on ~/Downloads while superposition was downloading & firefox with 3 tabs open. Before resetting after lockup I tried to ping & ssh from terminal on my chromebook, no joy.
On reboot my /home partition recovered orphaned inodes and my /boot/efi partition needed fsck to reset a dirty bit. Here's info center/system info copied to clipboard:
After bringing up the system the Xorg.0.log looks clean. ACPI throws startup errors seen in syslog:
Code:
Jan 15 06:06:24 slacker kernel: [ 0.005699] ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20200925/tbfadt-615)
Jan 15 06:06:24 slacker kernel: [ 0.842927] pci 0000:00:00.2: can't derive routing for PCI INT A
Jan 15 06:06:24 slacker kernel: [ 0.842931] pci 0000:00:00.2: PCI INT A: not connected
Jan 15 06:06:24 slacker kernel: [ 0.844483] PPR GT IA PC
Jan 15 06:06:24 slacker kernel: [ 6.244189] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20200925/psargs-330)
Jan 15 06:06:24 slacker kernel: [ 6.244792] ACPI Error: Aborting method \_SB.PCI0.VGA.LCD._BCM due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
Jan 15 06:06:24 slacker kernel: [ 6.245405] ACPI Error: Evaluating _BCM failed (20200925/video-357)
Jan 15 06:06:24 slacker kernel: [ 15.347554] amdgpu 0000:00:01.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
Jan 15 06:06:24 slacker kernel: [ 40.915672] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
I'll try running down these errors to see what I can find but thought posting sooner rather than later might be helpful.
I had similar experiences, hang-ups, freezes, etc. No luck with any of the different 5.10 kernels (tested up to 5.10.7) on my NVIDIA Quadro FX 580 (nouveau driver).
All problems went away when I changed to 5.4 kernel (5.4.89). No hick-ups or any other issues with KV.
I saw somewhere a suggestion to remove xf86-video-intel driver as it has some problems. On my setup it worked and now no freezes for few days after removal.
"I am running up-to-date Arch Linux on a system with an Intel I5-9400 processor, 16 GB of ram, Asus mini-ITX motherboard. I do not use a desktop system, just a window manager (bspwm), starting X with startx at the login shell. I have tried using a different window manager and have seen the same problem described below.
About once/day, I am experiencing complete X freezes. The system is unresponsive to mouse or keyboard inputs, even attempts to switch consoles. I can ssh into the system from another and attempts to kill the xorg process with kill -9 fail, which suggests a driver problem to me. When I try to reboot, I get messages from systemd that it is waiting for the xorg process to die. Perhaps 5 or 10 minutes later, the system finally reboots."
My main sys is similar: xorg + wm + startx on SW-current, without systemd, of course. The ssh results are what I see, too.
Of relevance. Who is running kernel mode setting only, xorg-video-intel only, & both simultaneously? The majority of Linux users seem to do only the first; the second might be an extinct breed; the final scheme...? In the first category, there seem to be no or few problems on the latest kernels. Others have troubles. Comments?
Of relevance. Who is running kernel mode setting only, xorg-video-intel only, & both simultaneously? The majority of Linux users seem to do only the first; the second might be an extinct breed; the final scheme...? In the first category, there seem to be no or few problems on the latest kernels. Others have troubles. Comments?
If you're referring to the X driver, you're either running the "intel" driver or the "modesetting" driver. I don't think there's any way to run both simultaneously (I'm not sure what that would mean).
Slackware-current ships with both drivers available. In that situation, X picks the intel driver. I.e., if you install Slackware-current on a system with Intel graphics, and you haven't messed with things, you're running the intel driver.
If you want to use the modesetting driver on Intel graphics hardware, you can either remove the xf86-video-intel package, or set up an Xorg config file. (See posts 2, 14, and 16 in https://www.linuxquestions.org/quest...el-4175688351/.)
To answer your question: I've had zero crashes since switching to the modesetting driver with kernel 5.10.3. I'm currently on 5.10.7.
After removing xf86-video-intel package, Xorg is now running on my Intel PC with Slackware-current-64 very well with kernel 5.10.x. On sddm log-on screen it see already that two displays with different resolutions are in use, and shows the screen with the different resolutions. Looks problem is solved with the removal of xf86-video-intel-x86_64-1.txz.
Quote:
Originally Posted by derekn13
If you're referring to the X driver, you're either running the "intel" driver or the "modesetting" driver. I don't think there's any way to run both simultaneously (I'm not sure what that would mean).
Slackware-current ships with both drivers available. In that situation, X picks the intel driver. I.e., if you install Slackware-current on a system with Intel graphics, and you haven't messed with things, you're running the intel driver.
If you want to use the modesetting driver on Intel graphics hardware, you can either remove the xf86-video-intel package, or set up an Xorg config file. (See posts 2, 14, and 16 in https://www.linuxquestions.org/quest...el-4175688351/.)
To answer your question: I've had zero crashes since switching to the modesetting driver with kernel 5.10.3. I'm currently on 5.10.7.
The Slackware leaders should provide some "official" guidance about these video / graphic drivers choices, configuration,... It is only now being clarified on LQ.
I saw somewhere a suggestion to remove xf86-video-intel driver as it has some problems. On my setup it worked and now no freezes for few days after removal.
I have removed xf86-video-intel but still had the X freezes. I reverted to 5.4 after 5.10.4 so I don't know if 5.10.7 fixes my issue. I will try again this week. Obviously something got seriously broken in kernel 5.10.x.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
