[SOLVED] How to know if my kernel is the generic?

Xerxeslins · 07-13-2014, 01:05 PM

First of all, I tried running the standard procedure to have the generic kernel, through:

/usr/share/mkinitrd/mkinitrd_command_generator.sh

But such a message appeared:

ls: can not access /sys/module/*_hcd/drivers/*: File or directory not found

I checked and this directory (drivers) does not actually exist on my computer. The script may not be able to automate the process in all situations.

Then I read the following text to create the initrd file:

http://mirrors.slackware.com/slackwa.../README.initrd

the command I used was:

mkinitrd -c -k 3.10.17 -m ext4 -f ext4 -r /dev/sda4

Finally, I got a file /boot/initrd.

I specified this file into the lilo.conf, according to the instructions. After all that I have created new links for: config, System.map and vmlinuz. I pointed to the generic options. See the output of ls -la | grep generic:

Quote:

xerxeslins @ darkstar: ~ $ ls /boot/ -la | grep generic
lrwxrwxrwx 1 root root 22 Jul 13 14:39 config -> config-generic-3:10:17
-Rw-r - r - 1 root root 137813 Feb 14 19:40 config-generic-3:10:17
lrwxrwxrwx 1 root root 26 Jul 13 14:40 System.map -> System.map-generic-3:10:17
-Rw-r - r - 1 root root 2213142 Feb 14 19:40 System.map-generic-3:10:17
lrwxrwxrwx 1 root root 23 Jul 13 14:39 vmlinuz -> vmlinuz-generic-3:10:17
-Rw-r - r - 1 root root 3450176 Feb 14 19:40 vmlinuz-generic-3:10:17

Of course I updated lilo.

Rebooted the system and everything seems to be ok.

But, since I do not follow the standard procedure, will I really am with the generic kernel? How to know?

Thank you!

Didier Spaier · 07-13-2014, 01:30 PM

Well, as the saying goes, there's more than one way to skin a cat

Here is one:

Code:

zcat /proc/config.gz > running_config
diff running_config /boot/config-generic-3:10:17

If the output of the last command is empty, you are running the generic kernel (assuming you have a 64 bit Slackware).

But wait a minute, something looks weird in your output of ls /boot/ -la | grep generic: I expected e.g. config-generic-3-10-17, not config-generic-3:10:17.

Xerxeslins · 07-13-2014, 01:44 PM

Quote:

Originally Posted by Didier Spaier

Well, as the saying goes, there's more than one way to skin a cat

Here is one:

Code:

zcat /proc/config.gz > running_config
diff running_config /boot/config-generic-3:10:17

If the output of the last command is empty, you are running the generic kernel (assuming you have a 64 bit Slackware).

But wait a minute, something looks weird in your output of ls /boot/ -la | grep generic: I expected e.g. config-generic-3-10-17, not config-generic-3:10:17.

command output is empty! Yes! Thank you! (yes, slackware 64 bit)

About "3:10:17" happens that English is not my native language. I used the google translator to create this post, apparently the translator changed some words. Although I have corrected, still some left uncorrected.

TracyTiger · 07-13-2014, 01:45 PM

Quote:

Originally Posted by Didier Spaier

But wait a minute, something looks weird in your output of ls /boot/ -la | grep generic: I expected e.g. config-generic-3-10-17, not config-generic-3:10:17.

The file permissions groupings are also odd. Perhaps the listing was retyped instead of copy/paste.

EDIT: OP explained the use of a translator.