How can I avoid the following [ FAILED ]'s?

indienick · 07-17-2006, 04:50 PM

I'm running Mandriva 2006.0, which by default uses the 2.6.12-12mdk kernel (2.6.12.?).

I recently decided to update my kernel to 2.6.17.1, and everything went smoothly. I used the following commands:

Code:

$ make oldconfig
$ make menuconfig
$ make
$ make bzImage
$ make modules
$ make modules_install
$ make install

I used oldconfig to mimick the old kernel config, (to keep things like "supermount"), and menuconfig to select a specific ALSA driver.

Everything went fine during the compilation. However, when I rebooted, and selected the image from the LILO propmt, I got the following "[ FAILED ]"s (I'm not exactly sure what the messages were, but they were quite close to what I'm typing out):

- could not mount filesystem type 'supermount'
- could not start shorewall (due to unsatisfied ip_tables)...yadda yadda yadda

I don't mind that these come up, but the most bothersome (in post-boot use) is the 'supermount' issue, because it makes things a little difficult for me to write to a floppy (not that I usually do, but once in a while).

As for the 'ip_tables' thing, I searched in the menuconfig for every possible instance of 'ip_tables', and selected them (as modules), and I'm still getting the same issue.

Are the 'supermount' and 'ip_tables' modules something special for the Mandriva kernel? (Another reason I re-compiled my kernel is because the mdk one is somewhat clunky - mine weighed in at 1.4MB). I've also noticed my machine is running alot faster now, than when it ran the 2.6.12-12mdk kernel.

So, any help on the above [ FAILED ] messages would be greatly appreciated.

PS. Is it just me, or does there seem to be a new kernel version every couple of days?

rkelsen · 07-17-2006, 06:37 PM

Quote:

Originally Posted by indienick

I'm running Mandriva 2006.0, which by default uses the 2.6.12-12mdk kernel (2.6.12.?).

I recently decided to update my kernel to 2.6.17.1, and everything went smoothly.

First question: Why did you upgrade?

You should only upgrade your kernel if your hardware is not completely supported by your current kernel. The old saying "If it ain't broke, don't fix it" applies every single time.

The kernel used by your distribution has been modified to add functionality and make it work properly with all the software packages supplied. Switching to a "vanilla" kernel is not a good idea on many modern distributions. If you must upgrade, you should choose an alternate kernel provided by your distribution rather than one you downloaded from kernel.org.

Quote:

Originally Posted by indienick

I used oldconfig to mimick the old kernel config, (to keep things like "supermount"), and menuconfig to select a specific ALSA driver.

"supermount" is not included in a standard kernel tree. It is one of the modifications mentioned above.

Quote:

Originally Posted by indienick

Everything went fine during the compilation. However, when I rebooted, and selected the image from the LILO propmt, I got the following "[ FAILED ]"s

If there are services you aren't using, you can disable them across all runlevels by doing a "chmod -x" to the appropriate script under /etc/init.d (or /etc/rc.d/init.d as the case may be).

Quote:

Originally Posted by indienick

- could not start shorewall (due to unsatisfied ip_tables)

There are many things which were changed between 2.6.12 and 2.6.17. Running a "make oldconfig" to generate a config for 2.6.17 based upon a 2.6.12 config WILL result in missing items.

Quote:

Originally Posted by indienick

PS. Is it just me, or does there seem to be a new kernel version every couple of days?

Yes. In some cases, there are several releases made on the same day!

So, in your shoes, I would go back to a Mandriva kernel. I see that there have been a few updates to the 2006.0 kernel. It is now at version 2.6.12-23mdk. (The "-23mdk" part of the filename is the Mandriva patch level). This will be the only way to get full funtionality from the rest of your setup.

indienick · 07-18-2006, 09:51 AM

Alright! Thanks a bunch for your reply!

EDIT: The reason I upgraded to a "vanilla" kernel is because of a lack of hardware support for my sound card.

rkelsen · 07-18-2006, 05:56 PM

Quote:

Originally Posted by indienick

The reason I upgraded to a "vanilla" kernel is because of a lack of hardware support for my sound card.

What brand/type is it?

indienick · 07-19-2006, 11:00 AM

My sound card's an AztechLabs ISA PnP 2320 (azt2320).

The reason I tried to go vanilla with the kernel was because I couldn't find the kernel source (to recompile adding the Alsa AZT2320 module - or to compile Alsa from source).

rkelsen · 07-20-2006, 08:07 PM

Quote:

Originally Posted by indienick

My sound card's an AztechLabs ISA PnP 2320 (azt2320).

That card is supported by the ALSA drivers.

Quote:

Originally Posted by indienick

I couldn't find the kernel source (to recompile adding the Alsa AZT2320 module - or to compile Alsa from source).

There should be a kernel source package available for your distribution. It may not provide the complete kernel sources, but should be enough to allow you to compile drivers.

indienick · 07-20-2006, 08:47 PM

I know the card's supported, but this was before I discovered that there was a kernel source RPM on the install DVD.

All's working fine and dandy now

.
Thanks for all your help.

gloomy · 07-24-2006, 02:14 AM

Quote:

You should only upgrade your kernel if your hardware is not completely supported by your current kernel. The old saying "If it ain't broke, don't fix it" applies every single time.

You should also upgrade whenever a kernel security flaw is discovered.

slimjim · 07-24-2006, 05:43 AM

Or if you just want to suck it and see, try it out - not recommended for business-critical machines of course, but fine if you view computing as an interest, for your desktop machine, and you have a backout strategy.

I'm presently using a kernel compiled from kernel-source-2.6.16.1mdk-1-1mdk.i586.rpm with Mandriva 2006, and it's working nicely.

indienick · 07-24-2006, 03:37 PM

oooo, sweet, slimjim.

where'd you get the source from (and was in an rpm)?