Your message dated Sun, 19 Jun 2011 01:55:06 +0200
with message-id <[email protected]>
and subject line Bug#506660: lilo: large-memory debconf change results in non
booting system ...
has caused the Debian Bug report #506660,
regarding lilo: large-memory debconf change results in non booting system even
though BIOS much newer than 2001.
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 [email protected]
immediately.)
--
506660: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506660
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lilo
Version: 1:22.8-6.4
Severity: normal
When the new debconf prompt is given concerning automatically adding
large-memory option, it tells the user that the related BIOS problems
is in "older systems (earlier than 2001)".
This ssems to be incorrect. My AWARD BIOS on this AMD XP3200+ system
is dated 12/31/2003 so I answered "y" to the large-memory question,
and my system became unbootable as a result, going into a continuous
reboot loop immediately after loading the kernel and initrd.
The debconf question should perhaps be updated to give a less misleading
impression as to the safety of allowing the package to make this change.
Perhaps someone else has more accurate data on the BIOS limitation in
question but from my experience it is not necessarily safe for BIOSES
earlier than 2004.
I'm also concerned about the implications of this change on first
installation because according to debconf the default, if the question is
not shown, is always "true". I am looking into using Debian on some small
single-board systems at work which have BIOses from around 2003 or older.
Perhaps liloconfig and update-lilo should force the answer to "false"
unless the installation is being done on a very modern CPU type where
you can be sure the BIOS is recent enough.
Nick
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (850, 'testing'), (600, 'stable'), (3, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
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 lilo depends on:
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii libc6 2.7-16 GNU C Library: Shared libraries
ii libdevmapper1.02.1 2:1.02.27-4 The Linux Kernel Device Mapper use
ii mbr 1.1.10-1 Master Boot Record for IBM-PC comp
lilo recommends no packages.
Versions of packages lilo suggests:
pn lilo-doc <none> (no description available)
-- debconf information:
liloconfig/fstab_broken:
liloconfig/banner:
liloconfig/use_lba32: true
liloconfig/configuring_base:
* lilo/runme: true
liloconfig/wipe_old_liloconf: false
liloconfig/activate_error:
lilo/new-config:
liloconfig/maintitle:
liloconfig/mbr_error:
liloconfig/lilo_warning:
liloconfig/no_changes:
* lilo/add_large_memory: true
liloconfig/liloconf_incompatible:
lilo/bad_bitmap:
lilo/upgrade:
liloconfig/liloconf_exists:
liloconfig/use_current_lilo: true
liloconfig/instruction:
liloconfig/select_bitmap: /boot/coffee.bmp
liloconfig/lilo_error:
liloconfig/odd_fstab:
liloconfig/install_from_root_device: true
liloconfig/make_active_partition: true
liloconfig/install_mbr: false
--- End Message ---
--- Begin Message ---
Source: lilo
Source-Version: 1:22.8-6.4
We believe that the bug you reported were fixed since the 23.1-1 / 23.1-2
version of lilo.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
Joachim Wiedorn <[email protected]> (supplier of updated lilo package)
--- End Message ---
