Error during boot [solved]

[isadora]

Did the reboot and udev is running!!!!

 

Now i saw a [FAILED] coming through during boot.

In /var/log/messages i found:

 

Dec 9 19:22:36 isadora kernel: checking if image is initramfs...it isn't (no cpio magic); looks like an initrd

Dec 9 19:22:36 isadora kernel: ACPI: Looking for DSDT in initrd ... not found!

 

Does this need any attention???

 

Thanks very very muchfor assistance on the struggle devfsd&udev

 

 

isadora

[Guest anon]

Yes, after editing lilo and then running lilo -v

Reboot as bvc says. If it works then you should have no problem deleting that file or the whole dev package.

[isadora]

It works great yet, beside one [FAILED] during boot:

 

unmounting init.rd --device is busy

 

Cosmetic?????

 

isadora

[Guest anon]

Try adding "nolapic" to lilo.conf file.

Example; (don't copy the whole line)

image=/boot/vmlinuz
       label="linux"
       root=/dev/sda9
       initrd=/boot/initrd.img
       append="nolapic resume=/dev/sda7 splash=silent"
       vga=788
       read-only
image=/boot/vmlinuz
       label="linux-nonfb"
       root=/dev/sda9
       initrd=/boot/initrd.img
       append="nolapic resume=/dev/sda7 splash=silent"

[isadora]

Tried that out, the entry goes as follows:

 

append="devfs=nomount acpi=ht nolapic resume=/dev/hde8 splash=silent"

 

But after reboot still the message about failing to unmount initrd (device is busy)

 

 

isadora

[adamw]

heh, my first cat was called isadora...anyway, don't know what's causing the initrd problem, but the post at the top of this page - no, you don't need to worry, both those messages are perfectly normal. Linux has the ability to load a custom DSDT table if you put it into the initrd - this is for laptops whose installed DSDT is excessively broken, you can fix problems with them by building a custom DSDT into the initrd. For 99% of systems you don't need to do that, hence the message is nothing at all to worry about.

[rudiz]

heh, my first cat was called isadora...anyway, don't know what's causing the initrd problem, but the post at the top of this page - no, you don't need to worry, both those messages are perfectly normal. Linux has the ability to load a custom DSDT table if you put it into the initrd - this is for laptops whose installed DSDT is excessively broken, you can fix problems with them by building a custom DSDT into the initrd. For 99% of systems you don't need to do that, hence the message is nothing at all to worry about.

<{POST_SNAPBACK}>

http://acpi.sourceforge.net/dsdt/index.php

[rudiz]

Here u can find a patch for kerne; 2.6.8.1:

http://gaugusch.at/kernel.shtml

[adamw]

You don't need that patch. As the message implies, Mandrake's kernel is already patched with DSDT loading capability. All you need to do to use a custom DSDT on a Mandrake system is build it into the initrd.

[isadora]

That sounds quite complex to me. How to do???

[iphitus]

Dont worry whatsoever about this message, it's totally harmless and nothing to worry about.

 

The first message is the kernel trying to unmount the initrd. And initrd, or initial ram disk is a file which contains a basic file system. Mandrake uses these to load drivers into the kernel at boot time. The custom DSDT also uses an initrd.

The second message is the kernel checking the initrd for a custom DSDT, which isnt contained in Mandrakes initrds. This is perfectly fine and nothing to worry about.

As for unmounting the initrd, its not really a worry. Unless you have a system with low memory, you'll be fine, all it will do is use a few meg of memory. It probably cant unmount the initrd because a file on it is still open, there isnt anything you can do about this really. Again, it's not a concern.

 

iphitus

[isadora]

Thanks iphitus, alot.

I stop this thread, as far as it concerns me.

 

Thanks to everybody for helping me out.