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

Bug#464919: marked as done (Fails to boot (reboots after BIOS data check))

Your message dated Tue, 12 Feb 2008 23:28:45 +0100
with message-id <20080212222845.GI22054@baikonur.stro.at>
and subject line Re: Bug#464919: Fails to boot (reboots after BIOS data check)
has caused the Debian Bug report #464919,
regarding Fails to boot (reboots after BIOS data check)
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
464919: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464919
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.24-1-686
Version: 2.6.24-3
Severity: important

Machine reboots right after booting - after "the dots" and "BIOS data
check successful.", before "Uncompressing kernel".

It didn't occur in 2.6.24-2 and it doesn't occur in 2.6.22-3.

I'm running it on Intel Core2Duo E6600 on ASRock 775Dual-VSTA (VIA
chipset mainboard). I haven't changed CMOS settings or added any
hardware recently.



-- Package-specific info:

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-3-686 (SMP w/2 CPU cores)
Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.24-1-686 depends on:
ii  debconf [debconf-2.0]        1.5.19      Debian configuration management sy
ii  initramfs-tools [linux-initr 0.91d       tools for generating an initramfs
ii  module-init-tools            3.3-pre11-4 tools for managing Linux kernel mo

Versions of packages linux-image-2.6.24-1-686 recommends:
ii  libc6-i686                    2.7-6      GNU C Library: Shared libraries [i

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

--- End Message ---
--- Begin Message --- 
On Tue, Feb 12, 2008 at 11:17:50PM +0100, Jacek Politowski wrote:
> On Tue, Feb 12, 2008 at 01:57:22AM +0100, maximilian attems wrote:
> >On Sat, 09 Feb 2008, Jacek Politowski wrote:
> 
> >> check successful.", before "Uncompressing kernel".
> 
> >try to manualy rerun lilo, does that help?
> 
> It helped, thanks.

ok cool, thanks for feedback - closing.
 
> Probably, the bug can be closed now, if it was only a glitch on my
> system, not something with the package in general.
> (next time I'll try running LILO before reporting)

hmm searching a box with lilo, hmm zu none at hands at anymore,
be sure to have do_bootloader = yes in /etc/kernel-img.conf
and none of the grub hooks.

see man kernel-img.conf

--- End Message ---
Reply to: