Non-Fatal boot errors on Debian 5.0 amd64
 

After I installed Debian Lenny Stable (2.6.26-2-amd64) on my laptop,(Acer Extensa 4420) I was greeted by the following errors, none of which are fatal;

[ 0.004000] Aperture beyond 4GB. Ignoring.
[ 0.108006] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
[ 0.315583] PCI: Cannot allocate resource region 7 of bridge 0000:00:06.0
[ 0.315627] PCI: Cannot allocate resource region 8 of bridge 0000:00:06.0
[ 4.021296] ata1: softreset failed (device not ready)
[ 5.398606] mmc0: Unknown controller version (2). You may experience problems.

I would like to know what these mean, and how to solve them.

Sorry, don't know.

I just wanted to mention that I have no immediate idea what Debian 5 is, as I always think of Debian releases by name -- "lenny", "etch", "sid", etc. It would be helpful to always include the release name along w/ the number -- save a lot of head scratching. So, "Debian 5.0 lenny, currently stable" would be a nice complete reference here.

No clue why it happens but it is simple to get rid of , you can turn off IOAPIC in your BIOS or.


At the grub boot screen, use your arrow keys to highlight "kernel /boot/linuz-2.6.15-25-386 root=/dev/sda3 ro quiet splash" (your exact paths and numbers might be a little different). Then type 'e' to edit the boot options; you will be taken to another screen. Append 'noapic' to the end of the boot options, and hit enter. Then just type 'b' to boot.

To make these changes permanent, do the following:

sudo gedit /boot/grub/menu.lst

and append 'noapic' to the line the says "#defoptions=", then

update grub

and reboot

You could try the grub kernel parameter, 'pci=assign-buses'.

It could be useful also to try updating the kernel image, many of those "fancy" bootload errors occur due to incompatibilities between the kernel image and the system. Well, at least thats what I have experienced till the moment :P