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.
I gave up VirtualBox for Qemu, and now I can't run VMs with 5.10.x. Maybe I should try a different hobby. ;-) Nah, I'll just stick with 5.9.x until they help me figure out the problem.
5.10.1 doesn't boot on my rx580 based system: the screen hangs with a blank screen on boot. Building from git master works. I noticed there are some amdgpu related git patches that may resolve my issue: I'll apply them to 5.10.1 and report the results.
Last edited by alex14641; 12-22-2020 at 11:34 PM.
Reason: additional info
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,167
Original Poster
Rep:
Year 2020, Round 76.
Another batch of updates has been scheduled for release on Monday, 21 December 2020, at approximately 12:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Sunday (depending on your time zone).
The details:
Sun Dec 20 03:10:57 UTC 2020
Linus didn't think this was a scary kernel and in spite of skipping a few
branches here before getting to this one, I don't either. Not scary enough
to make me think I need to start it out in /testing, anyway. I have a good
feeling about this kernel. Enjoy! :-)
a/kernel-firmware-20201218_646f159-noarch-1.txz: Upgraded.
a/kernel-generic-5.10.1-x86_64-1.txz: Upgraded.
a/kernel-huge-5.10.1-x86_64-1.txz: Upgraded.
a/kernel-modules-5.10.1-x86_64-1.txz: Upgraded.
d/kernel-headers-5.10.1-x86-1.txz: Upgraded.
k/kernel-source-5.10.1-noarch-1.txz: Upgraded.
5.10.1 has fixed my Intel LAN driver issue, and I now have temp monitoring of my 5900x. Only thing is I still don't have temp monitoring of my nvme drives through HWMON. This was added in kernel 5.5, so it should be available but I don't see it. I am looking over the kernel config now to see if maybe it wasn't added. Can anyone with a nvme driver see temperatures through running "sensors"?
5.10.1 has fixed my Intel LAN driver issue, and I now have temp monitoring of my 5900x. Only thing is I still don't have temp monitoring of my nvme drives through HWMON. This was added in kernel 5.5, so it should be available but I don't see it. I am looking over the kernel config now to see if maybe it wasn't added. Can anyone with a nvme driver see temperatures through running "sensors"?
Yeah I just checked the kernel GUI config. The option is there but it is off right now. In fact it doesn't even show up until you change "NVM Express block device" from static to a module, then the option for nvme temp monitoring becomes available. Not sure why that is. But I am going to try and pass "CONFIG_NVME_HWMON=y" to Pat's config file and make a custom kernel and see if that gets it.
Yeah I just checked the kernel GUI config. The option is there but it is off right now. In fact it doesn't even show up until you change "NVM Express block device" from static to a module, then the option for nvme temp monitoring becomes available. Not sure why that is. But I am going to try and pass "CONFIG_NVME_HWMON=y" to Pat's config file and make a custom kernel and see if that gets it.
So far so good. Just rebooted, reinstalled Nvidia drivers (It's a Christmas miracle that I remembered before starting X!), and loaded WoW just to see if anything were to blow up. Nothing's blown up so far...
success! Only caveat is that simply adding "CONFIG_NVME_HWMON=y" does not work. I misread the depends line in the kernel config. For this to work it requires "NVME_CORE [=m]=y && HWMON [=m]=y || NVME_CORE [=m]=m && HWMON [=m]" in the kernel config. So either hardware monitoring support has to be static and not a module. Or NVME_CORE needs to be a module and not static. For my experiment I made hardware monitoring support a module instead of static. After I was done I got a interesting surprise, not only did I have nvme temperature support but it was also showing the temperature of my wifi adapter. That doesn't matter since I am about to disable it in the bios now that my Intel i225-V works properly.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.