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.
Is there a mirror that doesn't have the update? I want to go back to 5.10.2 or even 5.4.XX. My computer (itself in the case) makes beep sounds when I press tab here
Code:
bash-5.1$
Display all 5959 possibilities? (y or n)
.
My computer makes scary whining and clicking sounds (sounds like a tape recorder hiss) with 5.10.3 but not in Windows. I was lazy and didn't save a backup kernel.
Last edited by RadicalDreamer; 12-27-2020 at 05:12 PM.
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 928
Rep:
Quote:
Originally Posted by RadicalDreamer
Is there a mirror that doesn't have the update? I want to go back to 5.10.2 or even 5.4.XX. My computer (itself in the case) makes beep sounds when I press tab here
Code:
bash-5.1$
Display all 5959 possibilities? (y or n)
.
My computer makes scary whining and clicking sounds (sounds like a tape recorder hiss) with 5.10.3 but not in Windows. I was lazy and didn't save a backup kernel.
It is the snd_pcsp module, I blacklisted it in '/etc/modprobe.d'.
I don't know if there are any side effects for blacklisting it.
edit-
Quote:
Originally Posted by RadicalDreamer
Is there a mirror that doesn't have the update? I want to go back to 5.10.2 or even 5.4.XX.
hello everyone,
I am sorry if, perhaps, i am repeating a help request form another thread (mine) but i am kinda losing hopes to get my video card to work again and, since this is a latest kernel thread i decided to post it here.
I believe that it is a problem of the latest kernel 5.10.onward because my nvidia card was working perfectly with kernel versions: 4.19.X , 5.4.X , 5.9.X and when i upgraded to 5.10.2 and then 5.10.3 it stopped working.
This happened simultaneously on a desktop and a laptop both with nvidia video cards.
Signs&Symptoms:
lost functionality of the HDMI/DVI controller as my second screen connected to one of each started glitching and eventually causing a total system crash/freeze (including loss of keyboard and mouse) Attempted Management:
1) sbopkg was installing only the driver but failed to build the kernel
2) installing the new nvidia proprietary driver (from root on init3) resulted in
Quote:
ERROR: Unable to load the kernel module 'nvidia.ko'. This happens most frequently when this kernel module was built against the wrong or improperly configured kernel sources, with a version of gcc that differs from the one used to build the target kernel, or if another driver, such as nouveau, is present and prevents the NVIDIA kernel module from obtaining ownership of the NVIDIA GPU(s), or no NVIDIA GPU installed in this system is supported by this NVIDIA Linux graphics driver release.
no matter what driver's version i tried
So, i was suggested to try the slackbuilds packages:
3) build the nvidia-kernel (no variable passed)
4) build the nvidia-driver (passing the COMPAT32="yes" and CURRENT="yes" variables, as suggested on the README file)
5) blacklist nouveau, as suggested on the README file
6) install the TGZs pckgs with installplkg
7) rebooted
OUTCOME
1) screen resolution 1024x768 (completely impossible to setup a second video output)
2) both nvidia kernel and driver 460.X.X are installed
3) 'nvidia-settings' from console gives:
Quote:
bash-5.1$ nvidia-settings
ERROR: NVIDIA driver is not loaded
ERROR: Unable to load info from any available system
bash-5.1$ nvidia-settings -v
nvidia-settings: version 460.27.04
The NVIDIA X Server Settings tool.
This program is used to configure the NVIDIA Linux graphics driver.
For more detail, please see the nvidia-settings(1) man page.
NVIDIA-455.45.01 works fine here on 5.10.3 dual screen. I reinstall nvidia using source binary after every kernel/mesa upgrade.
I think 5.10.3 feels less sluggish than 5.10.2-2. The output of dmesg is a lot cleaner as well, no more udevd error. Bluetooth still not working though.
If you dual boot with Windows, make sure that "fast startup" is not enabled as it may leave the adapter in an inconsistent state.
I've also read that on some machines rebooting to BIOS, disabling bluetooth, rebooting to BIOS again and reenabling can fix things up.
Thanks, looks to be Slackware related though (maybe kernel?), bluetooth works after booting a PureOS ISO from USB (that's kernel 4.9).
If you dual boot with Windows, make sure that "fast startup" is not enabled as it may leave the adapter in an inconsistent state.
I've also read that on some machines rebooting to BIOS, disabling bluetooth, rebooting to BIOS again and reenabling can fix things up.
Just read this thread and tried out. It's not working for me Bluetooth works on 5.4.84 though.
I've run into problems here with a mouse using the Bluetooth Low Energy protocol. The "fix" (for now), is to find the devices info file under /var/lib/bluetooth/ and remove the [IdentityResolvingKey] line and the line directly below it.
Apparently this issue happens with 5.9.x and newer.
Bluetooth works with 5.9.16 and 5.4.85. When using 5.10.X is says to enable it. This only happens with 5.10.X. When I downgrade the kernel everything is back to normal. I'm at work right now, when I get off, I'll post a screenshot.
I had a couple of lockups with 5.10.2 and this morning again with 5.10.3. Am rebuilding 5.10.3 after today's config update. If lockups continue will revert to 5.9.x
Edit: After some reading I rebuilt the Nvidia 455.45.01 driver using the --no-unified-memory option. Built fine after reminding me that a module wouldn't be built so I can't cuda (which I don't anyway).
I tried booting 5.10.3 and it locked up in record time, after 2 mins. Xorg gets stuck, and it can't be straced or killed:
Adding idle=poll stops it from happening, which means its something related to (gpu) power management. However, using idle=poll on a laptop is a terrible solution, but it gave me a full day worth of uptime without lockups. I also tried running igt-gpu-tools, more specifically run-tests.sh - which crashes after performing 25 tests, and when i add idle=poll it doesn't crash, but dmesg gets filled with errors. It looks like 5.10.x introduces something intel gpu doesn't really like.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,097
Original Poster
Rep:
Year 2020, Round 78.
Another batch of updates has been scheduled for release on Wednesday, 30 December 2020, at approximately 12:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Tuesday (depending on your time zone).
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,097
Original Poster
Rep:
Quote:
Originally Posted by SCerovec
I guess it will take some time to see things go back to normal regarding new 5.10.x kernel. Nothing we didn't see before, right?
There will be 717 patches to 5.10.4, which is due out by Wednesday. Maybe that will fix a few of the problems (or introduce a few more)?
I've not had any problems with this box, and the kernel, since switching to 5.10.0 (now running 5.10.3).
Last edited by cwizardone; 12-28-2020 at 09:47 AM.
Reason: Typo.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Bluetooth works on 5.4.84 though.
