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

Bug#451085: marked as done (linux-image-2.6.22-3-amd64: Does not boot)

Your message dated Tue, 13 Nov 2007 11:14:59 +0100
with message-id <47397923.5070503@pu-pm.univ-fcomte.fr>
and subject line Bug#451085: linux-image-2.6.22-3-amd64: Does not boot
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: linux-image-2.6.22-3-amd64
Version: 2.6.22-6
Severity: critical
Justification: breaks the whole system

Hi,

The new linux-image-2.6.22-3-amd64 (2.6.22-6) does not boot on my system, it stops after "Booting linux..[ENTER]".

Best regards,
Eugen Dedu

-- Package-specific info:

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.22-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.22-3-amd64 depends on:
ii  e2fsprogs                    1.40.2-1    ext2 file system utilities and lib
ii  initramfs-tools [linux-initr 0.91b       tools for generating an initramfs
ii  module-init-tools            3.3-pre11-4 tools for managing Linux kernel mo

linux-image-2.6.22-3-amd64 recommends no packages.

-- debconf information:
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.22-3-amd64/postinst/create-kimage-link-2.6.22-3-amd64: true
  linux-image-2.6.22-3-amd64/postinst/depmod-error-initrd-2.6.22-3-amd64: false
  linux-image-2.6.22-3-amd64/prerm/would-invalidate-boot-loader-2.6.22-3-amd64: true
  linux-image-2.6.22-3-amd64/postinst/old-system-map-link-2.6.22-3-amd64: true
  linux-image-2.6.22-3-amd64/preinst/overwriting-modules-2.6.22-3-amd64: true
  linux-image-2.6.22-3-amd64/preinst/failed-to-move-modules-2.6.22-3-amd64:
  linux-image-2.6.22-3-amd64/postinst/depmod-error-2.6.22-3-amd64: false
  linux-image-2.6.22-3-amd64/prerm/removing-running-kernel-2.6.22-3-amd64: true
  linux-image-2.6.22-3-amd64/postinst/bootloader-error-2.6.22-3-amd64:
  linux-image-2.6.22-3-amd64/preinst/abort-overwrite-2.6.22-3-amd64:
* linux-image-2.6.22-3-amd64/preinst/already-running-this-2.6.22-3-amd64:
  linux-image-2.6.22-3-amd64/postinst/bootloader-test-error-2.6.22-3-amd64:
  linux-image-2.6.22-3-amd64/postinst/old-initrd-link-2.6.22-3-amd64: true
  linux-image-2.6.22-3-amd64/preinst/bootloader-initrd-2.6.22-3-amd64: true
  linux-image-2.6.22-3-amd64/preinst/lilo-initrd-2.6.22-3-amd64: true
  linux-image-2.6.22-3-amd64/preinst/lilo-has-ramdisk:
  linux-image-2.6.22-3-amd64/preinst/abort-install-2.6.22-3-amd64:
  linux-image-2.6.22-3-amd64/preinst/elilo-initrd-2.6.22-3-amd64: true
  linux-image-2.6.22-3-amd64/postinst/old-dir-initrd-link-2.6.22-3-amd64: true
  linux-image-2.6.22-3-amd64/preinst/initrd-2.6.22-3-amd64:
  linux-image-2.6.22-3-amd64/postinst/kimage-is-a-directory:

--- End Message ---
--- Begin Message --- 
maximilian attems wrote:

On Tue, Nov 13, 2007 at 10:50:19AM +0100, Eugen Dedu wrote:

I executed "# lilo" and reboot the computer and it works now.
So the question is why didn't it execute lilo automatically? It's the first time I need to manually execute lilo after upgrading the kernel.
please post the output of cat /etc/kernel-img.conf 

$ cat /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no

Sorry, it's my fault...
debian-installer installed symlinks in / and I have moved them to /boot without knowing that I must also modify the line link_in_boot in /etc/kernel-img.conf... 


lilo is a pain anyway, grub is much nicer and boots allmost any box
beside strange old bioses.

Thank you for your fast reply,
--
Eugen Dedu



sunny greetings, amicalement


Here it's the winter :o)...

Thank you and have a good night,
--
Eugen Dedu

--- End Message ---
Reply to: