On 10/09/2011 07:46 PM, Jonathan Nieder wrote: > Hi, > > Joerg Morbitzer wrote: > >> Package: linux-2.6 >> Version: 2.6.32-38 > [...] >> Linux version 2.6.32-5-kirkwood (Debian 2.6.32-30) (b...@decadent.org.uk) >> (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Wed Jan 12 15:27:07 UTC 2011 > > Was the new kernel flashed correctly?
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 ... sheeva:~# flash-kernel Generating kernel u-boot image... done. Creating backup of /boot/uImage. Creating new /boot/uImage. Generating initrd u-boot image... done. Creating backup of /boot/uInitrd. Creating new /boot/uInitrd. sheeva:~# ... did a reboot ... and there you go, the USB disks get recognised again. Fixed for me at least. So I assume the new kernel wasn't really flashed. On the other hand: if the previous kernel was still in place why would it suddenly fail? Strange ... Kind regards, Joerg. Does rebooting help? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
