LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
Reload this Page [SOLVED] mkinitrd errors when /boot/initrd-tree is cleared
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 04-21-2022, 09:00 PM   #1
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 7,371

Rep: Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593
mkinitrd errors when /boot/initrd-tree is cleared

After the recent updates to slackware64-current, if the /boot/initrd-tree is cleared or manually deleted get modules not found messages, however the initrd.gz created works as it should

Code:
mkinitrd  -c -F
WARNING:  Could not find module "/lib/modules/5.17.4/kernel/drivers/usb/host/xhci-hcd.ko"
OK: /lib/modules/5.17.4/kernel/drivers/usb/host/xhci-pci-renesas.ko added.
OK: /lib/modules/5.17.4/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/kernel/drivers/usb/host/ehci-hcd.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/usb/host/ohci-hcd.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/usb/host/ohci-pci.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/usb/host/ehci-hcd.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/usb/host/ehci-pci.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/usb/host/xhci-hcd.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/usb/host/uhci-hcd.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/usb/host/ehci-hcd.ko added.
WARNING:  Could not find module "/lib/modules/5.17.4/kernel/drivers/hid/hid.ko"
OK: /lib/modules/5.17.4/kernel/drivers/hid/hid.ko added.
WARNING:  Could not find module "/lib/modules/5.17.4/kernel/drivers/hid/usbhid/usbhid.ko"
WARNING:  Could not find module "/lib/modules/5.17.4/kernel/drivers/i2c/i2c-core.ko"
OK: /lib/modules/5.17.4/kernel/drivers/hid/hid.ko added.
WARNING:  Could not find module "/lib/modules/5.17.4/kernel/drivers/hid/i2c-hid/i2c-hid.ko"
OK: /lib/modules/5.17.4/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/hid/hid-generic.ko added.
WARNING:  Could not find module "/lib/modules/5.17.4/kernel/drivers/acpi/video.ko"
WARNING:  Could not find module "/lib/modules/5.17.4/kernel/drivers/platform/x86/wmi.ko"
WARNING:  Could not find module "/lib/modules/5.17.4/kernel/net/rfkill/rfkill.ko"
OK: /lib/modules/5.17.4/kernel/drivers/hid/hid.ko added.
WARNING:  Could not find module "/lib/modules/5.17.4/kernel/drivers/input/sparse-keymap.ko"
OK: /lib/modules/5.17.4/kernel/drivers/acpi/battery.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/acpi/platform_profile.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/platform/x86/asus-wmi.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/hid/usbhid/usbhid.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/hid/hid-asus.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/hid/hid-cherry.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/hid/usbhid/usbhid.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/hid/hid-logitech.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/hid/usbhid/usbhid.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/hid/hid-logitech-dj.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/hid/hid-logitech-hidpp.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/hid/hid-lenovo.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/hid/hid-microsoft.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/hid/hid-multitouch.ko added.
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"
57669 blocks
/boot/initrd.gz created.
Be sure to run lilo again if you use it.
Did another check with just the ext4 module and If I
Code:
rm /boot/initrd-tree/lib/modules/5.17.4/kernel/fs/ext4/ext4.ko
mkinitrd -F
no warning messages however If I

Code:
rm -rf /boot/initrd-tree/lib/modules/5.17.4/kernel/fs/ext4
mkinitrd -F
I get
Code:
...OK: /lib/modules/5.17.4/kernel/drivers/hid/hid-microsoft.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/hid/hid.ko added.
OK: /lib/modules/5.17.4/kernel/drivers/hid/hid-multitouch.ko added.
OK: /lib/modules/5.17.4/kernel/fs/jbd2/jbd2.ko added.
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"
57669 blocks
/boot/initrd.gz created.
Be sure to run lilo again if you use it.
root@slackbox:~# ls /boot/initrd-tree//lib/modules/5.17.4/kernel/fs/ext4/
ext4.ko
As already the stated the /boot/initrd.gz works and able to boot with the generic kernel without any problems.
This slackware64-current is a fresh installation of slackware64-15
Last edited by colorpurple21859; 04-21-2022 at 09:15 PM.
 
Old 04-22-2022, 02:16 AM   #2
kgha
Senior Member
 
Registered: May 2018
Location: Sweden
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,081

Rep: Reputation: 751Reputation: 751Reputation: 751Reputation: 751Reputation: 751Reputation: 751Reputation: 751
Similar experience here, after installing the latest (5.17.4) kernel (didn't touch the /boot/initrd-tree though):
Code:
bash-5.1# mkinitrd -c -k 5.17.4 -m ext4
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"
58629 blocks
/boot/initrd.gz created.
Be sure to run lilo again if you use it.
But here too the /boot/initrd.gz works and I'm able to boot generic kernel without issues.
Last edited by kgha; 04-22-2022 at 02:31 AM.
 
Old 04-22-2022, 03:33 AM   #3
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,409

Rep: Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145
I already tried to figure out what was going on with this mkinitrd

https://www.linuxquestions.org/quest...0/#post6347724

Basically, you have to be in / for the warning to disappear
 
4 members found this post helpful.
Old 04-22-2022, 05:11 AM   #4
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 7,371

Original Poster
Rep: Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593
Quote:
Basically, you have to be in / for the warning to disappear
I get the same results. It has something to do with coreutils upgrade, If I downgrade to Slackware15 coreutils the warnings go away If not in /
Code:
Upgrading coreutils-9.1-x86_64-1 package using ./coreutils-9.0-x86_64-3.txz
 
Old 04-22-2022, 05:34 AM   #5
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,409

Rep: Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145Reputation: 4145
Quote:
Originally Posted by colorpurple21859 View Post
I get the same results. It has something to do with coreutils upgrade, If I downgrade to Slackware15 coreutils the warnings go away If not in /
Code:
Upgrading coreutils-9.1-x86_64-1 package using ./coreutils-9.0-x86_64-3.txz
Yes, that's what I saw too
https://www.linuxquestions.org/quest...ml#post6347510
 
Old 04-22-2022, 08:13 AM   #6
twy
Member
 
Registered: Jun 2004
Distribution: Slackware64
Posts: 99

Rep: Reputation: Disabled
If modules are compiled into the kernel (not as loadable modules), then the loadable module files will be missing. If you use -m ext4, then mkinitrd will probably assume that ext4 (and modules it depends on) are loadable module files and looks for them. So, check if ext4 is really a module. Personally, I compile all modules having to do with storage and networking (or, drivers needed to boot) into my kernel and then I do not have to use MODULES_LIST in /etc/mkinitrd.conf or -m on the command line. I still have to use initial root disk (initrd) to setup mdraid6, luks, lvm, and then mount my ext4 "final root disk" before switch_root (on initrd) can boot my final root disk.

If you use the huge kernel, then I think that any modules listed to mkinitrd will be missing. If you use a generic kernel, but change the linux config to compile-in ext4 and other modules, those modules will be missing and do not need to be listed to mkinitrd.

If you already know all this and the problem is something else, then sorry!
 
Old 04-22-2022, 08:53 AM   #7
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 2,979

Rep: Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556
I suspected coreutils as well. I normally do my mkinitrd's from /boot

Code:
/boot# mkinitrd -F -k 5.17.3:5.17.4
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"
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.
OK: /lib/modules/5.17.4/kernel/fs/jbd2/jbd2.ko added.
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"
63101 blocks
/boot/initrd.gz created.
Be sure to run lilo again if you use it.
The modules are copied to the tree in the right places so the boot will succeed.

Works fine from "/"
Code:
/# mkinitrd -F -k 5.17.3:5.17.4
OK: /lib/modules/5.17.3/kernel/fs/jbd2/jbd2.ko added.
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.
OK: /lib/modules/5.17.3/kernel/fs/ext4/ext4.ko added.
OK: /lib/modules/5.17.4/kernel/fs/jbd2/jbd2.ko added.
OK: /lib/modules/5.17.4/kernel/fs/mbcache.ko added.
OK: /lib/modules/5.17.4/kernel/fs/jbd2/jbd2.ko added.
OK: /lib/modules/5.17.4/kernel/fs/mbcache.ko added.
OK: /lib/modules/5.17.4/kernel/fs/ext4/ext4.ko added.
63101 blocks
/boot/initrd.gz created.
Be sure to run lilo again if you use it.
I can live with that I guess. I will be reminded if I forget to switch to '?'
Last edited by chrisretusn; 04-22-2022 at 08:54 AM.
 
1 members found this post helpful.
Old 04-22-2022, 09:02 AM   #8
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 2,979

Rep: Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556Reputation: 1556
I probably should have paid more attention to https://www.linuxquestions.org/quest...0/#post6347724
 
Old 04-22-2022, 11:39 AM   #9
truepatriot76
Member
 
Registered: Apr 2014
Location: California, USA
Distribution: slackware64-current
Posts: 232

Rep: Reputation: 195Reputation: 195
Interesting - I run my kernel update script from /root... and, of course, had plenty of warnings. Generic kernel 5.17.4 was working fine as of last night.
 
Old 04-22-2022, 12:46 PM   #10
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 7,371

Original Poster
Rep: Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593
Quote:
Interesting - I run my kernel update script from /root... and, of course, had plenty of warnings. Generic kernel 5.17.4 was working fine as of last night.
Generic kernel works here also, just get warning messages that I do not normally get.
 
Old 04-22-2022, 07:44 PM   #11
obrisc
LQ Newbie
 
Registered: Mar 2014
Posts: 5

Rep: Reputation: Disabled
Quote:
Originally Posted by marav View Post
Basically, you have to be in / for the warning to disappear
That's it. cd / and no more warnings.
 
Old 04-22-2022, 07:50 PM   #12
truepatriot76
Member
 
Registered: Apr 2014
Location: California, USA
Distribution: slackware64-current
Posts: 232

Rep: Reputation: 195Reputation: 195
Yep, I just amended my script until Pat fixes it - and if he doesn't, no big deal.
 
Old 04-26-2022, 04:50 PM   #13
WhiteWolf1776
Member
 
Registered: Oct 2010
Location: Bowling Green, KY
Distribution: Slackware
Posts: 288

Rep: Reputation: 95
everything working properly in today's -current build
 
Old 04-26-2022, 05:47 PM   #14
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 7,371

Original Poster
Rep: Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593
The warnings are gone with the last set of updates, so I'm going to mark this solved
 
Old 04-26-2022, 11:29 PM   #15
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 3,550

Rep: Reputation: 3404Reputation: 3404Reputation: 3404Reputation: 3404Reputation: 3404Reputation: 3404Reputation: 3404Reputation: 3404Reputation: 3404Reputation: 3404Reputation: 3404
Those warnings are still present when firmware files are copied to initrd.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Current64: mkinitrd-1.4.11-x86_64_22 - sbin/mkinitrd.orig burdi01 Slackware 5 04-17-2021 05:08 AM
[SOLVED] Slackware 14.2 Install mkinitrd ERROR: No /lib/modules/4.4.14-smp kernel modules tree found for kernel " 4.4.14-smp" laxware Slackware 4 01-04-2019 12:40 PM
[SOLVED] initrd and generic kernel fails to boot with errors after using mkinitrd generator adamschock Slackware 8 06-26-2010 02:30 PM
sudo mkinitrd -o /boot/initrd.img-2.6.32.9 2.6.32.9 sudo: mkinitrd: command not foun vishwas181 Linux - Newbie 1 02-27-2010 01:16 AM
Modify INITRD without MKINITRD? harrywertm Linux - General 1 05-10-2009 01:35 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:31 PM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration