mkinitrd_command_generator.sh doesn't recognize kernel file ...?

chexmix · 06-12-2013, 09:53 PM

Hi --

I just updated my netbook to Slack64-current, with the 3.9.5 kernel. I couldn't seem to get mkinitrd_command_generator.sh to work correctly while 3.8.13 was still running, so I rebooted (I don't run LILO as this is a dual-boot machine with Debian ... I use grub). I knew I would have to boot using the Slack 14 DVD (since I hadn't created an initrd), but I'd done this before, so did not worry too much ...

However, when I rebooted using the disc and attempted to build an initrd, I got the following:

Code:

root@catbutt:/usr/share/mkinitrd# ./mkinitrd_command_generator.sh /boot/vmlinuz-generic-3.9.5
File '/boot/vmlinuz-generic-3.9.5' does not look like it is a kernel file!

and indeed, behold:

Code:

root@catbutt:/boot# file vmlinuz-generic-3.9.5
vmlinuz-generic-3.9.5: x86 boot sector

... huh?

Never seen the like. I mean, sure, I can see where the line in the script is that's generating that message, but ...

... I guess I'm wondering how I convince not only mkinitrd_command_generator.sh, but the file command / my system that that file is indeed a kernel file.

Any advice would be welcome. This has me confused.

Thx,

Glenn

kfritz · 06-12-2013, 10:18 PM

Similar results here running in a VM:

Code:

root@sl64-current:~# file /boot/vmlinuz-huge-3.9.5 
/boot/vmlinuz-huge-3.9.5: x86 boot sector
root@sl64-current:~# file /boot/vmlinuz-generic-3.9.5 
/boot/vmlinuz-generic-3.9.5: x86 boot sector
root@sl64-current:~# /usr/share/mkinitrd/mkinitrd_command_generator.sh /boot/vmlinuz-huge-3.9.5 
File '/boot/vmlinuz-huge-3.9.5' does not look like it is a kernel file!
root@sl64-current:~# uname -a
Linux sl64-current 3.8.13 #2 SMP Sun May 12 17:23:24 CDT 2013 x86_64 QEMU Virtual CPU version 1.2.0 AuthenticAMD GNU/Linux

So, I don't think you muffed anything.

nivieru · 06-13-2013, 01:07 AM

You should try

Code:

/usr/share/mkinitrd/mkinitrd_command_generator.sh -k 3.9.5

It worked for me.

Alien Bob · 06-13-2013, 06:20 AM

Thanks for reporting this.

The 'file' utility changed its output message... bad bad.
This patch to the script will make it work again (for old as well as new Slackware versions):

Code:

$ diff -uar source/a/mkinitrd/mkinitrd_command_generator.sh{.orig,}
--- source/a/mkinitrd/mkinitrd_command_generator.sh.orig        2012-12-11 23:28:40.000000000 +0100
+++ source/a/mkinitrd/mkinitrd_command_generator.sh     2013-06-13 13:16:00.480483900 +0200
@@ -380,7 +380,7 @@
           KFILE=$(basename $KFILE)
         fi
         KFILE=${KFILEPATH}/$KFILE
-        if [ -z "$(file $KFILE | grep 'Linux kernel x86 boot')" ]; then
+        if [ -z "$(file $KFILE | grep -E 'Linux kernel x86 boot|x86 boot sector')" ]; then
           echo "File '$KFILE' does not look like it is a kernel file!"
           exit 1
         fi

I will notify Pat so that he can apply this to the Slackware tree.

Eric

eloi · 06-13-2013, 09:56 AM

Hi chexmix,

Learning to use mkinitrd directly is easier

.

If the kernel you pass to mkinitrd options is not present, mkinitrd will tell
you with an error message.

Once you know what you *specifically* need and how to do it, write a shell
script yourself. If it takes you more than 30 lines you're giving more
importance to your creation than to the function it was created to.

For example, I don't use LVM or RAID so this is all what I need in my desktop
after a fresh Slackware installation (the awk string contains one space and one
tab between the square brackets):

Code:

#!/bin/sh
# Slackware: generate initrd and set generic kernel in lilo

[ `whoami` != "root" ] && echo "You must be root" && exit 1

kernel=`uname -r`
file=`awk '/[	 ]+\/[	 ]+/ { print $3 }' /etc/fstab`
root=`awk '/[	 ]+\/[	 ]+/ { print $1 }' /etc/fstab`
swap=`awk '/swap/ { print $1 }' /etc/fstab`

rm /boot/{vmlinuz,System.map,config}
ln -s /boot/vmlinuz-generic-$kernel /boot/vmlinuz
ln -s /boot/System.map-generic-$kernel /boot/System.map
ln -s /boot/config-generic-$kernel /boot/config

grep 'initrd\ *=\ */boot/initrd.gz' /etc/lilo.conf >/dev/null ||
sed -i '/Linux bootable partition config ends/iinitrd=\/boot\/initrd.gz' \
	/etc/lilo.conf

mkinitrd -c -k $kernel -f $file -m $file -r $root -h $swap && lilo

exit 0

And being simple is useful like a memory-aid too. When you are in front of a
problem like the one you describe you easily figure out how to workaround it.

Using free software does not free you, your mind does.

Walter

Alien Bob · 06-13-2013, 12:04 PM

I do not think you ever need mkinitrd_commandline_generator.sh with a simple setup like yours.
The script is obviously not meant for you but for others with a more complex setup (LVM, RAID, LUKS, USB keyboard, exotic controllers etc).

Eric

volkerdi · 06-13-2013, 01:00 PM

Quote:

Originally Posted by Alien Bob

I do not think you ever need mkinitrd_commandline_generator.sh with a simple setup like yours.

It's a useful script for anyone wanting to use the generic kernel, and I do think it's better to run the generic kernel than the huge one to get all the unused drivers out of the system memory.

01micko · 06-13-2013, 04:27 PM

FWIW, running the generic kernel makes a noticeable speed difference on my compaq-cq60 laptop (-current).

Poprocks · 06-13-2013, 07:56 PM

I've never noticed a difference in speed myself, but it's nice to be able to unload and reload non-behaving device drivers (doesn't happen often, but it does happen) by way of reloading modules rather than rebooting the entire system.

TobiSGD · 06-13-2013, 08:11 PM

Usually I run the mkinitrd_commandline_generator.sh only one time on a new machine, then I just enter the options it provides into /etc/mkinitrd.conf and use mkinitrd directly with the -k and -F options. Works all the time.

eloi · 06-14-2013, 02:57 AM

It's the approach I suggest in human language what is useful, the idea. The script is just an example.

chexmix · 06-14-2013, 07:11 AM

Many thanks to everyone who replied. Lots of food for thought and practice.

I issued

Code:

/usr/share/mkinitrd/mkinitrd_command_generator.sh -k 3.9.5

per nivieru and it worked swell.

If my reporting this helped the world's best Linux distro (or anyone who uses it) in a small way, that makes me happy.

eloi · 06-17-2013, 05:31 AM

Perhaps this talk about stuff by George Carlin is better than me to explain where is the bug:

http://youtu.be/MvgN5gCuLac

---
Just a clarification for the readers of this forum.

The Barrel of Shit Theory vs the Flush Toilet Theory (that I've already used on other thread) is just a funny metaphor that used a school teacher I had in my young years referring to thinking. Using it I am advocating the KISS Unix philosophy that Slackware supposedly follows.

Alien Bob · 06-17-2013, 06:08 AM

Quote:

Originally Posted by eloi

Perhaps this talk about stuff by George Carlin is better than me to explain where is the bug:

http://youtu.be/MvgN5gCuLac

First, the bug was discussed, a patch was created and submitted already.
Second, I take offense to the phrase "Barrel of Shit" when you refer to this bug that you are not willing to discuss.
For you, only one answer remains: *PLONK*

Eric