[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Kernel 2.6.17

On Mon, Feb 05, 2007 at 07:07:48PM +0100, Nigel Henry wrote:
> [...]
> Back to the 2.6.18 kernel that I set to download, and install last night. This 
> morning synaptic was complaining with a "post install script error 9". Don't 
> know what that is.
> [...]

I am also not familiar with the exit codes, but I managed to get exit
code 9 too. This happens, when the creation of the initrd image fails.
I am not sure if this may have more than one causes. At least one
possibility is that there is not enough space left on your /boot

First you schould check the free space on /boot. In a x-terminal this
can be done by running "df /boot".

Also I'd suggest you run as root "dpkg --audit". This will show you which
command to run to possibly fix the error.

> [...]
> Also I had no new entry in lilo for the 2.6.18 kernel 
> after running lilo. /boot showed an entry for vmlinuz-2.6.18-3-686, but no 
> entry for it's initrd.img.
> [...]

This is because the post intall script failed before the step that
runs the boot loader's update script.

> [...]
> On Fedora Core 5 I had no problems with the machine shutting down completely 
> with the 2.6.17 kernel, but the moment I booted with a 2.6.18 one, the 
> machine would no longer shutdown completely, and neither would the 2.6.17 one 
> anymore. the original 2.6.15 kernel still shutdown completely though. Using 
> "acpi=force as a kernel parameter when booting (that's using Grub) resolves 
> the problem
> I've read of a similar bug amongst the debian bugs. Not sure if it was to do 
> with the 2.6.18 kernel, but there was a fix there.
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=390547
> [...]

This is mentioned in the release notes for Etch:


	"5.1.2 Automatic poweroff stops working
	...Adding acpi=off apm=power_off to the kernel's command line,
	e.g. in grub or lilo configuration files should fix this issue..."

I hope these information will be of help for your problems. Actually I
had to guess a lot from your message. Please send some more
information if the problem cannot be resolved easily. For example you
could post the complete output of the install command for your kernel.
Which was your default kernel in Sarge since you wrote about a working
2.4 kernel. There are some issues concerning an upgrade to a 2.6
kernel. The more information you can provide the easier it is to find
the cause for errors.

Maybe it is also a good idea to open up a new thread on this list
since i think not everyone reads this one through to its end. This way
maybe more people can provide helpful info.


Attachment: signature.asc
Description: Digital signature

Reply to: