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.
Built, installed and booted 5.15.35 along with NVIDIA-Linux-x86_64-510.60.02.run and VMWare Workstation Pro 16.2.3
I was also able to build and install the tuxedo-keyboard and tuxedo_keyboard_ite kernel modules for Keyboard RGB LED Control on my Sager NP9672M-G1 Laptop ) ( experimental ! and only partial functionality for now ).
and it makes the initrd just fine but since 5.17.4 is outputs the following -
Code:
mkinitrd -c -R -k 5.17.4 -f ext4 -m ext4:crc32c_generic
WARNING: Could not find module "/lib/modules/5.17.4/kernel/fs/jbd2/jbd2.ko"
OK: /lib/modules/5.17.4/kernel/fs/mbcache.ko added.
WARNING: Could not find module "/lib/modules/5.17.4/kernel/fs/ext4/ext4.ko"
55331 blocks
/boot/initrd.gz created.
Be sure to run lilo again if you use it
The two modules that it complains about are indeed in /lib/modules/5.17.4/kernel/fs and it loads them on boot as usual. Does anyone have an idea what is causing the complaints?? Been using this mkinitrd command for a very long time but just with 5.17.4 I get these messages. Thanks in advance
and it makes the initrd just fine but since 5.17.4 is outputs the following -
Code:
mkinitrd -c -R -k 5.17.4 -f ext4 -m ext4:crc32c_generic
WARNING: Could not find module "/lib/modules/5.17.4/kernel/fs/jbd2/jbd2.ko"
OK: /lib/modules/5.17.4/kernel/fs/mbcache.ko added.
WARNING: Could not find module "/lib/modules/5.17.4/kernel/fs/ext4/ext4.ko"
55331 blocks
/boot/initrd.gz created.
Be sure to run lilo again if you use it
The two modules that it complains about are indeed in /lib/modules/5.17.4/kernel/fs and it loads them on boot as usual. Does anyone have an idea what is causing the complaints?? Been using this mkinitrd command for a very long time but just with 5.17.4 I get these messages. Thanks in advance
I noticed that also on 5.17.3
Code:
WARNING: Could not find module "/lib/modules/5.17.3/kernel/fs/jbd2/jbd2.ko"
WARNING: Could not find module "/lib/modules/5.17.3/kernel/fs/ext4/ext4.ko"
WARNING: Could not find module "/lib/modules/5.17.3/kernel/drivers/cpufreq/amd_pstate.ko"
and it makes the initrd just fine but since 5.17.4 is outputs the following -
Code:
mkinitrd -c -R -k 5.17.4 -f ext4 -m ext4:crc32c_generic
WARNING: Could not find module "/lib/modules/5.17.4/kernel/fs/jbd2/jbd2.ko"
OK: /lib/modules/5.17.4/kernel/fs/mbcache.ko added.
WARNING: Could not find module "/lib/modules/5.17.4/kernel/fs/ext4/ext4.ko"
55331 blocks
/boot/initrd.gz created.
Be sure to run lilo again if you use it
The two modules that it complains about are indeed in /lib/modules/5.17.4/kernel/fs and it loads them on boot as usual. Does anyone have an idea what is causing the complaints?? Been using this mkinitrd command for a very long time but just with 5.17.4 I get these messages. Thanks in advance
I'm just now upgrading from 5.16.x to 5.17.x on Slackware64-15.0. So 5.17.4 is my first 5.17.x compile. I don't see your problem (using a barely-modified Slackware .config):
Code:
# ./prepare_boot_files.sh
#
# mkinitrd_command_generator.sh revision 1.45
#
# This script will now make a recommendation about the command to use
# in case you require an initrd image to boot a kernel that does not
# have support for your storage or root filesystem built in
# (such as the Slackware 'generic' kernels').
# A suitable 'mkinitrd' command will be:
mkinitrd -c -k 5.17.4-etr -f ext4 -r luksnvme0n1p5 -m xhci-pci:ohci-pci:ehci-pci:xhci-hcd:uhci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-asus:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:jbd2:mbcache:crc32c_intel:crc32c_generic:ext4 -C /dev/nvme0n1p5 -u -F -s /boot/initrd-tree-5.17.4-etr -o /boot/initrd-5.17.4-etr.gz
# ./prepare_boot_files.sh | sh
OK: /lib/modules/5.17.4-etr/kernel/drivers/usb/host/xhci-hcd.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/usb/host/xhci-pci-renesas.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/usb/host/xhci-pci.ko added.
WARNING: Could not find firmware "/lib/firmware/renesas_usb_fw.mem"
OK: /lib/modules/5.17.4-etr/kernel/drivers/usb/host/ehci-hcd.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/usb/host/ohci-hcd.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/usb/host/ohci-pci.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/usb/host/ehci-hcd.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/usb/host/ehci-pci.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/usb/host/xhci-hcd.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/usb/host/uhci-hcd.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/usb/host/ehci-hcd.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/usbhid/usbhid.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/i2c/i2c-core.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/i2c-hid/i2c-hid.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/hid-generic.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/acpi/video.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/platform/x86/wmi.ko added.
OK: /lib/modules/5.17.4-etr/kernel/net/rfkill/rfkill.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/input/sparse-keymap.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/acpi/battery.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/acpi/platform_profile.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/platform/x86/asus-wmi.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/usbhid/usbhid.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/hid-asus.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/hid-cherry.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/usbhid/usbhid.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/hid-logitech.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/usbhid/usbhid.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/hid-logitech-dj.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/hid-logitech-hidpp.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/hid-lenovo.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/hid-microsoft.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/hid/hid-multitouch.ko added.
OK: /lib/modules/5.17.4-etr/kernel/fs/jbd2/jbd2.ko added.
OK: /lib/modules/5.17.4-etr/kernel/fs/mbcache.ko added.
OK: /lib/modules/5.17.4-etr/kernel/fs/jbd2/jbd2.ko added.
OK: /lib/modules/5.17.4-etr/kernel/fs/mbcache.ko added.
OK: /lib/modules/5.17.4-etr/kernel/fs/ext4/ext4.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/usb/host/ohci-hcd.ko added.
OK: /lib/modules/5.17.4-etr/kernel/drivers/usb/storage/usb-storage.ko added.
OK: /lib/modules/5.17.4-etr/kernel/fs/fat/fat.ko added.
OK: /lib/modules/5.17.4-etr/kernel/fs/nls/nls_cp437.ko added.
OK: /lib/modules/5.17.4-etr/kernel/fs/nls/nls_iso8859-1.ko added.
OK: /lib/modules/5.17.4-etr/kernel/fs/fat/fat.ko added.
OK: /lib/modules/5.17.4-etr/kernel/fs/fat/msdos.ko added.
OK: /lib/modules/5.17.4-etr/kernel/fs/fat/fat.ko added.
OK: /lib/modules/5.17.4-etr/kernel/fs/fat/vfat.ko added.
OK: /lib/modules/5.17.4-etr/kernel/crypto/af_alg.ko added.
OK: /lib/modules/5.17.4-etr/kernel/crypto/algif_skcipher.ko added.
80104 blocks
/boot/initrd-5.17.4-etr.gz created.
Be sure to run lilo again if you use it.
Hm... but I did notice jbd2.ko is listed twice. That seems weird.
# mkinitrd -c -k 5.17.3 -f ext4 -r /dev/nvme0n1p3 -m crc32c_generic:hid:jbd2:mbcache:ext4
WARNING: Could not find module "/lib/modules/5.17.3/kernel/drivers/hid/hid.ko"
WARNING: Could not find module "/lib/modules/5.17.3/kernel/fs/jbd2/jbd2.ko"
OK: /lib/modules/5.17.3/kernel/fs/mbcache.ko added.
OK: /lib/modules/5.17.3/kernel/fs/jbd2/jbd2.ko added.
OK: /lib/modules/5.17.3/kernel/fs/mbcache.ko added.
WARNING: Could not find module "/lib/modules/5.17.3/kernel/fs/ext4/ext4.ko"
54022 blocs
/boot/initrd.gz created.
Be sure to run lilo again if you use it.
For those making use of the Linux 5.15 LTS kernel... is a notable point release for back-porting an Intel P-State driver fix for Intel Alder Lake systems that leads to much better performance in properly deciding between P and E core selection. Here are some benchmarks...
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,142
Original Poster
Rep:
Quote:
Originally Posted by cwizardone
It went down, again, at 23:44:21 EST on Fri Apr 15 2022.
Since this started I've sent three e-mails. One was never answered and two basically replied with, "not my problem." If anyone knows the system admin. at Indiana University, would you be kind enough to let them know their message board is in need of some serious maintenance.
Thanks!
After being down for another 8 days, The Linux-Kernel Archive By Thread message board came back to life at 00:15:01 EST, this morning 24 April 2022.
Obviously, no one is minding the store.
Where are the adults?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.