Bug#313637: kernel-image-2.6-686: Why no 2.6.11?
Package: kernel-image-2.6-686 Version: 101 Severity: normal Is there a reason why this package doesn't depend on kernel-image-2.6.11-1-686? I couldn't find anything too serious in the bug list for that package, nor an entry for the reason in the bug list for this package. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-2-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages kernel-image-2.6-686 depends on: ii kernel-image-2.6.8-2-686 2.6.8-16 Linux kernel image for version 2.6 -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#257093: kernel-image-2.6.6-2-686: kernel will not load file system
Package: kernel-image-2.6.6-2-686 Version: 2.6.6-2 Severity: important When I boot up in this kernel I can not succeed. The eventual problem is that none of the modules can be loaded because of a read-only file system. But why can't a read-only kernel module be loaded? I'd give a better report, but I can only see this when I set up grub to boot this image. Some other relevant info: 1. I use grub not lilo. I boot this kernel with kernel /boot/vmlinuz-2.6.6-2-686 root=/dev/hdb1 (I think I've tried with and without the root parameter) initrd /boot/initrd.img-2.6.6-2-686 boot 2. I have used most other 2.6.* kernels, with grub in the same way, without any similar errors. I use 2.6.6-1-686 right now. [EMAIL PROTECTED]:~]$ uname -r 2.6.6-1-686 -jason short -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.6-1-686 Locale: LANG=en_US, LC_CTYPE=en_US Versions of packages kernel-image-2.6.6-2-686 depends on: ii coreutils [fileutils] 5.0.91-2 The GNU core utilities ii fileutils 5.0.91-2 The GNU file management utilities ii initrd-tools 0.1.70 tools to create initrd image for p ii module-init-tools 3.1-pre2-2 tools for managing Linux kernel mo -- no debconf information
Bug#257093: kernel-image-2.6.6-2-686: kernel will not load file system
Andreas Metzler wrote: Is this is a new error or have you experienced it for some time now and just could not spatre the time to report the bug until now? I am asking because this sounds like another instance of http://bugs.debian.org/254950 module-init-tools complains about read only filesystem at boot time. I have gotten it every time I try to boot this particular kernel, but never when booting any other kernel. The error message sounds identical to the one in 254950. The version of module-init-tools you are running currently has this bug fixed, but you might still have the old broken version on the initrd which is generated at installation of the kernel-image package. Could you try to regenerate initrd either by running mkinitrd -o /boot/initrd.img-2.6.6-2-686 /lib/modules/2.6.6-2-686 or by uninstaling and re-installing kernel-image-2.6.6-2-686 and check whether the error is fixed? (I am not completely sure about the initrd-commandline, so if it does not work please try the purge+install approach). I'm trying that now. jason
Bug#257093: kernel-image-2.6.6-2-686: kernel will not load file system
Andreas Metzler wrote: The version of module-init-tools you are running currently has this bug fixed, but you might still have the old broken version on the initrd which is generated at installation of the kernel-image package. Could you try to regenerate initrd either by running mkinitrd -o /boot/initrd.img-2.6.6-2-686 /lib/modules/2.6.6-2-686 or by uninstaling and re-installing kernel-image-2.6.6-2-686 and check whether the error is fixed? (I am not completely sure about the initrd-commandline, so if it does not work please try the purge+install approach). That fixes the problem. Thanks. jason
