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.
Hi folks,
searched the forum and couldn't find anything similar to what is happening to my laptop after last night update/upgrade.
If i remember correctly, it was the latest 5.15.2 kernel patch.
After reboot inoticed two things:
1) extremely slow to startx (at least 30seconds on a i7 processor with 32Gb of memory RAM)
2) once X starts, there is no mouse on the screen. I cant see the mouse pointer on screen anymore. It is there as I can see highlighting of certain icons when i move the mouse and, if I right-click the usual menu appear. I managed to updatedb moving through the screen until I found the konsole command line like a blindfolded but nothing happened.
Rebooted, nothing changed.
Disconnected the mouse and tried diferent USB port, nothing.
It seems that the pointer has become invisible or transparent so I managed to move through the system settings and changed the pointer icons (all by following just the highlights), nothing.
Logged in as root, still no mouse.
Same thing using the laptop mouse-pad.
However, when I log out of 'X', the mouse is visible as the usual 'square cursor' moving around the black screen.
However, when I log out of 'X', the mouse is visible as the usual 'square cursor' moving around the black screen.
That's because the non-X mouse is handled independently by gmp. Did your update include xorg-server or the video driver? I'll make a tenuous guess that that's where the problem lies because the mouse driver, evdev, is clearly working, picking up the mouse movements from udev and passing them on successfully.
That's because the non-X mouse is handled independently by gmp. Did your update include xorg-server or the video driver? I'll make a tenuous guess that that's where the problem lies because the mouse driver, evdev, is clearly working, picking up the mouse movements from udev and passing them on successfully.
Thanks for the input.
I am not sure whether the video-driver and/or the xorg-server also updated.
However, how does it justify the very 'lonnnng' time to startx?
I would like to point out that the same update did not cause such issues on my desktop system.
Nvidia GK106 is reportedly affected by this bug, maybe your GPU, too. On the other hand, the last nouveau update to -current seems to be a rebuild on Feb 15th. I don't know when your update before the last one was, but obviously something got broken in between. Could you try rolling back the relevant x/series updates, for instance the libxdrm update on Nov 9th? If the binary package is not available then you can grab the SlackBuild files from a mirror and build with an older source.
Nvidia GK106 is reportedly affected by this bug, maybe your GPU, too. On the other hand, the last nouveau update to -current seems to be a rebuild on Feb 15th. I don't know when your update before the last one was, but obviously something got broken in between. Could you try rolling back the relevant x/series updates, for instance the libxdrm update on Nov 9th? If the binary package is not available then you can grab the SlackBuild files from a mirror and build with an older source.
Thank you.
lspci outputs that the video controller is: Nvidia GF108GLM (quadro 1000M) (rev a1).
I wonder whether updating regularly/often is an issue, considering the dubious stability of the latest current development; the previous update before the last one (that broke everything), was done about 2wks ago. And now I have to try to revert back to that time.
In my limited experience, every time i have tried to revert back to anything i.e. kernel and/or video drivers it ended real bad.
GF108 series mentioned in the bug report, too. If your second to last update was 2 weeks ago then you might have upgraded you kernel from 5.14 to 5.15. Still, if the culprit is the bug I referred to, it should have existed in 5.14 as well.
The update to kernel 5.15 was expected, as it is the LTS one. I compile my kernels all the time (and sometimes video driver-related librares) and haven't had major troubles. Just keep you old kernel around until you are sure that the new one works as expected .
If you have the time I would also give try reverting libdrm to 2.4.107, though. Just use the script with the older version source:
GF108 series mentioned in the bug report, too. If your second to last update was 2 weeks ago then you might have upgraded you kernel from 5.14 to 5.15. Still, if the culprit is the bug I referred to, it should have existed in 5.14 as well.
The update to kernel 5.15 was expected, as it is the LTS one. I compile my kernels all the time (and sometimes video driver-related librares) and haven't had major troubles. Just keep you old kernel around until you are sure that the new one works as expected .
If you have the time I would also give try reverting libdrm to 2.4.107, though. Just use the script with the older version source:
As mentioned, trying to revert back to the older libdrm didn't work and crashed the system; I couldn't even startx, at all. So, i re-reverted to the latest libdrm-2.4.108 and at least I could start X, again (i had to download the packages on another PC).
Anyway, I could try to revert back to kernel 5.14.
I'm sorry it didn't work. Before suggesting the downgrade I looked at the changelog to see whether the upgrade was after the kernel upgrade or not. It was after, which means the old libdrm should work with kernel 5.15 (unless something specifically in version 5.15.2 broke it). I hope you find a solution/fix soon.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
.
