Package: kernel-image-2.6.11-1-686 Version: 2.6.11-5 Severity: grave Justification: renders package unusable
I upgraded from 2.6.11-3 to 2.6.11-5 (dist-upgrade) and the kernel fails to boot with error messages indicating that a few files cannot be found. The transcripts of upgrade sessions and the error messages while booting follow: $ agdu Reading Package Lists... Done Building Dependency Tree... Done Calculating Upgrade... Done The following packages will be upgraded: kernel-image-2.6.11-1-686 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0B/15.9MB of archives. After unpacking 0B of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 90899 files and directories currently installed.) Preparing to replace kernel-image-2.6.11-1-686 2.6.11-3 (using .../kernel-image-2.6.11-1-686_2.6.11-5_i386.deb) ... The directory /lib/modules/2.6.11-1-686 still exists. Continuing as directed. Unpacking replacement kernel-image-2.6.11-1-686 ... Searching for GRUB installation directory ... found: /boot/grub . Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst . Searching for splash image... none found, skipping... Found kernel: /vmlinuz-2.6.11-1-686 Found kernel: /vmlinuz-2.6.10-1-686 Found kernel: /vmlinuz-2.4.18-bf2.4 Found kernel: /memtest86.bin Found kernel: /memtest86+.bin Updating /boot/grub/menu.lst ... done Setting up kernel-image-2.6.11-1-686 (2.6.11-5) ... dpkg: warning, architecture `i686-pc-linux-gnu' not in remapping table <=== is this ok? dpkg: warning, architecture `i686-pc-linux-gnu' not in remapping table <=== is this ok? Not touching initrd symlinks since we are being reinstalled (2.6.11-3) Not updating image symbolic links since we are being updated (2.6.11-3) Searching for GRUB installation directory ... found: /boot/grub . Testing for an existing GRUB menu.list file... found: /boot/grub/menu.lst . Searching for splash image... none found, skipping... Found kernel: /vmlinuz-2.6.11-1-686 Found kernel: /vmlinuz-2.6.10-1-686 Found kernel: /vmlinuz-2.4.18-bf2.4 Found kernel: /memtest86.bin Found kernel: /memtest86+.bin Updating /boot/grub/menu.lst ... done While booting (messages hand typed - I did not find a way to capture these as the boot process failed): [snip] hda: Host Protected Area disabled. hda: 78156288 sectors (40016 MB) w/1821KiB Cache, CHS=16383/255/63, UDMA(100) /dev/ide/host0/bus0/target0/lun0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 > Kernel can not convert a name into desc number Check your 'root=' argument passed on boot by bootloader. initrd-tools: 0.1.80 /sbin/init: 360: cannot open bin/root: no such file umount: bin: not mounted /sbin/init: 362: cannot create proc/sys/kernel/real-root-dev: Directory non existant cat: proc/cmdline: No such file or directory umount: proc not mounted [snip] After this, the messages from 'Kernel can not...' are repeated in a loop. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.10-1-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages kernel-image-2.6.11-1-686 depends on: ii coreutils [fileutils] 5.2.1-2 The GNU core utilities ii fileutils 5.2.1-2 The GNU file management utilities ii initrd-tools 0.1.80 tools to create initrd image for p ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
