On Sun, 2011-10-09 at 21:24 +0200, Joerg Morbitzer wrote:
> On 10/09/2011 08:16 PM, Jonathan Nieder wrote:
> > Joerg Morbitzer wrote:
> >
> >> Mmmh, I am quite sure that I didn't see any error message when running
> >> the upgrade to 6.0.3, and I can find those messages in /var/log/dpkg.log ...
> >>
> >> 2011-10-09 17:27:03 configure linux-image-2.6.32-5-kirkwood 2.6.32-38
> >> 2.6.32-38
> >> 2011-10-09 17:27:03 status unpacked linux-image-2.6.32-5-kirkwood 2.6.32-38
> >> 2011-10-09 17:27:04 status half-configured linux-image-2.6.32-5-kirkwood
> >> 2.6.32-38
> >> 2011-10-09 17:28:05 status installed linux-image-2.6.32-5-kirkwood 2.6.32-38
> >>
> >> ..., however, I just re-flashed the kernel ...
> > [..!
.]
> >> ... did a reboot ... and there you go, the USB disks get recognised
> >> again. Fixed for me at least.
> >
> > Hm, what version of flash-kernel do you have installed? Please also send
> > the output of
> >
> > grep . /etc/kernel/postinst.d/*
> >
> > so we can see whether the hooks are set up correctly.
>
>
cut --------------------------
> sheeva:~# dpkg -l | grep flash-kernel
> ii flash-kernel 2.37
> utility to make certain embedded devices bootable
> sheeva:~#
>
cut --------------------------
>
>
>
cut --------------------------
> sheeva:~# grep . /etc/kernel/postinst.d/*
> #!/bin/sh
> version="$1"
> bootopt=""
[...]
This is the usual initramfs-tools hook script. In 'squeeze',
update-init!
ramfs is
supposed to run flash-kernel.
When you saw this problem, had you rebooted since the kernel upgrade?
Ben.
--
Ben Hutchings
Reality is just a crutch for people who can't handle science fiction.