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.
It's not surprising at all that it needs some time and work for VirtualBox to adapt their drivers to a new kernel (of which I am grateful to them although I prefer Qemu). OTOH if they claim that a driver does support a specific kernel version and you can't use or build it against this version I suggest that you file an issue with them instead of posting it in a thread that they most probably will not read.
Last edited by Didier Spaier; 11-15-2019 at 08:38 AM.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,105
Original Poster
Rep:
Quote:
Originally Posted by Didier Spaier
It's not surprising at all that it needs some time and work for VirtualBox to adapt their drivers to a new kernel (of which I am grateful to them although I prefer Qemu). OTOH if they claim that a driver does support a specific kernel version and you can't use or build it against this version I suggest that you file an issue with them instead of posting it in a thread that they most probably will not read.
They don't.
It is Nvidia who claims their latest long term driver fixes the 5.4-rc kernel installation problems. As I've posted elsewhere,
Quote:
.....Updated the Module.symvers sanity check, which is part of the NVIDIA kernel module build process, to accommodate the recent addition of a new field in the Module.symvers file format. This fixes the error "The Module.symvers file is missing [...]" seen during driver installation or DKMS rebuilds with Linux 5.4 RC kernels.
Fixed kernel module build problems with Linux kernel 5.4.0 release candidates......
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,105
Original Poster
Rep:
Quote:
Sat Nov 16 03:31:45 UTC 2019
ap/alsa-utils-1.2.1-x86_64-1.txz: Upgraded.
l/alsa-lib-1.2.1-x86_64-1.txz: Upgraded.
l/alsa-plugins-1.2.1-x86_64-1.txz: Upgraded.
l/imagemagick-7.0.9_4-x86_64-1.txz: Upgraded.
extra/pure-alsa-system/alsa-lib-1.2.1-x86_64-1_alsa.txz: Upgraded.
extra/pure-alsa-system/alsa-plugins-1.2.1-x86_64-1_alsa.txz: Upgraded.
testing/packages/kernel-generic-5.4.0_rc7-x86_64-2.txz: Rebuilt.
testing/packages/kernel-headers-5.4.0_rc7-x86-2.txz: Rebuilt.
testing/packages/kernel-huge-5.4.0_rc7-x86_64-2.txz: Rebuilt.
testing/packages/kernel-modules-5.4.0_rc7-x86_64-2.txz: Rebuilt.
testing/packages/kernel-source-5.4.0_rc7-noarch-2.txz: Rebuilt.
CRYPTO_CRC32C_INTEL m -> y
Make modules before cleaning up the source tree. This does some magic in
Module.symvers that fixes building the NVIDIA kernel modules.
+--------------------------+
Bingo!
The Nvidia driver now builds with the 5.4.0-rc7 kernel!
Many thanks to Mr. Volkerding.
Edit in: So far everything, except VirtualBox, works as it should.
Last edited by cwizardone; 11-16-2019 at 05:09 AM.
Edit in: So far everything, except VirtualBox, works as it should.
Just installed the latest testing branch, VirtualBox-6.0.15-134636-Linux_amd64.run, it works.
Code:
bash VirtualBox-6.0.15-134636-Linux_amd64.run
Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation.............
VirtualBox Version 6.0.15 r134636 (2019-11-14T15:53:16Z) installer
Removing previous installation of VirtualBox 6.0.14 r133895 from /opt/VirtualBox
Installing VirtualBox to /opt/VirtualBox
Python found: python, installing bindings...
VirtualBox has been installed successfully.
Today, I downloaded and installed the 32-bit kernel 5.4.0-rc7-smp package set into Slackware 14.2 (32-bit) on an ASUS Eee PC 1025c. This boots to the console. I have not yet used the computer for any other purpose.
If we ever needed an example to demonstrate why the production of the Linux Kernel if done in The Cathedral manner would have cost some $40 Billion USD, this thread is it!
New kernel packages are available for Slackware 14.2 to fix security issues.
Here are the details from the Slackware 14.2 ChangeLog:
+--------------------------+
patches/packages/linux-4.4.202/*: Upgraded.
CRYPTO_CRC32C_INTEL m -> y
+X86_INTEL_TSX_MODE_AUTO n
+X86_INTEL_TSX_MODE_OFF y
+X86_INTEL_TSX_MODE_ON n
These updates fix various bugs and security issues, including mitigation for
the TSX Asynchronous Abort condition on some CPUs.
Be sure to upgrade your initrd after upgrading the kernel packages.
If you use lilo to boot your machine, be sure lilo.conf points to the correct
kernel and initrd and run lilo as root to update the bootloader.
If you use elilo to boot your machine, you should run eliloconfig to copy the
kernel and initrd to the EFI System Partition.
For more information, see:
Fixed in 4.4.201: https://cve.mitre.org/cgi-bin/cvenam...=CVE-2019-0155 https://cve.mitre.org/cgi-bin/cvenam...=CVE-2019-0154
Fixed in 4.4.202: https://cve.mitre.org/cgi-bin/cvenam...CVE-2019-11135
(* Security fix *)
+--------------------------+
But I believe we'll want another update of the kernel-firmware package for 14.2 too, the current one still is kernel-firmware-20191108_f1100dd, so from before the -201 and -202 kernel upgrades.
But I believe we'll want another update of the kernel-firmware package for 14.2 too, the current one still is kernel-firmware-20191108_f1100dd, so from before the -201 and -202 kernel upgrades.
You know that kernel-firmware packages are not connected to kernel releases, don't you? It is not common that stable Slackware has now received several kernel updates in a couple of weeks, but there have been some security issues. It does not mean that the firmware images need weekly updates. After 2019-11-08, these firmware images have got updates in linux-firmware git:
Code:
linux-firmware: Update firmware file for Intel Bluetooth AX201
linux-firmware: Update firmware file for Intel Bluetooth AX200
linux-firmware: Update firmware file for Intel Bluetooth 9560
linux-firmware: Update firmware file for Intel Bluetooth 9260
amdgpu: update navi14 vcn firmware
amdgpu: update navi10 vcn firmware
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
