Bug#705971: debian-installer hangs when tty console in use (console-setup)
severity 705971 normal thanks Quoting Stefano Forli (ntro...@gmail.com): > Package: debian-installer > Version: 20130415 > Severity: critical > Tags: installation, wheezy, console-setup > > It seems that if a TTY console is in use during the installation, the > whole installation process hangs and can't be recovered (see below). > It is possible to switch to different tty's, but It is not possible to > activate other consoles nor kill the one still active (blinking > cursor, unresponsive). > The log file showed this message, then hungs there for several minutes > > [xxx] configuring console-setup... > It's hard to tell when exactly during the installation process you had this message. What step where you in? What do you mean by "a TTY console is in use during the installation"? Lowering the severity anyway as I don't think this is a bug (if one) that affects all installs. signature.asc Description: Digital signature
Processed: Re: Bug#705971: debian-installer hangs when tty console in use (console-setup)
Processing commands for cont...@bugs.debian.org: > severity 705971 normal Bug #705971 [debian-installer] debian-installer hangs when tty console in use (console-setup) Severity set to 'normal' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 705971: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13667008862339.transcr...@bugs.debian.org
Bug#705971: debian-installer hangs when tty console in use (console-setup)
The bug happened when the actual installation of packages started. Unfortunately, I didn't save the log message before rebooting. The TTY I mentioned is one of the text consoles available through Ctrl-Alt-Fx (I would say the one I had was the 3), with a Busybox prompt. When the installer stops and hangs at the console-setup configuration, it is not possible to kill the old busybox process nor start a new one. I guess the 'normal' priority is right, although for me it was a show-stopper for my installation, and I had to abort and repeat the entire process. I'll try to install it again using a VM to see if I can catch it with more details (and snapshots, maybe?). Thanks for the reply. S. On Mon, Apr 22, 2013 at 10:06 PM, Christian PERRIER wrote: > severity 705971 normal > thanks > > Quoting Stefano Forli (ntro...@gmail.com): >> Package: debian-installer >> Version: 20130415 >> Severity: critical >> Tags: installation, wheezy, console-setup >> >> It seems that if a TTY console is in use during the installation, the >> whole installation process hangs and can't be recovered (see below). >> It is possible to switch to different tty's, but It is not possible to >> activate other consoles nor kill the one still active (blinking >> cursor, unresponsive). >> The log file showed this message, then hungs there for several minutes > >> >> [xxx] configuring console-setup... >> > > > It's hard to tell when exactly during the installation process you had > this message. What step where you in? > > What do you mean by "a TTY console is in use during the installation"? > > Lowering the severity anyway as I don't think this is a bug (if one) > that affects all installs. > > > -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAEF7wuL=pxrcqkovvsua3jhp-+9vu_muoxi34burw-s88td...@mail.gmail.com
Re: [Debian installer] Problem with umounting hd-media
Hi, I didn't know the existence about the debian-boot mailinglist... Thanks Brian ! I'm up to date now ;-) So I copy/paste my issue here : We are installing some Debian wheezy on tests servers and we are assuming some issues : One of them are really annoying : - We install the system with USB flash drive. - After booting on it, the USB stick is mounted on /hd-media/ - The .iso image situated in hd-media is loop mounted on /cd-rom/ - After that, the installer umount /hd-media/ and /cd-rom/ is still mounted 1. we need data on USB key to use trunk module 2. we need data on USB key to launch post-install script It is impossible to remount USB stick on /hd-media/ because it is busy (iso on cd-rom). We don't know if it is a bug or a normal behavior... But we need to keep data on USB Stick accessible on the server during all the install process. Please, we need advice on this case. Have a good day & enjoy Linux ;-) --- *JG* -- Forwarded message -- From: Brian Date: 2013/4/23 Subject: Re: [Debian installer] Problem with umounting hd-media To: debian-u...@lists.debian.org On Tue 23 Apr 2013 at 10:58:16 +0200, Julien Groselle wrote: > We are installing some Debian wheezy on tests servers and we are assuming > some issues : > One of them are really annoying : > - We install the system with USB flash drive. Using a methods from either Section 4.3.2. or Section 4.3.3. of the manual? > - After booting on it, the USB stick is mounted on /hd-media/ > - The .iso image situated in hd-media is loop mounted on /cd-rom/ Mounting takes place when an ISO is selected. > - After that, the installer umount /hd-media/ and /cd-rom/ is still mounted The unmounting of /dev/sdX actually takes place at the Detect network hardware stage. > 1. we need data on USB key to use trunk module > 2. we need data on USB key to launch post-install script > > It is impossible to remount USB stick on /hd-media/ because it is busy (iso > on cd-rom). > > We don't know if it is a bug or a normal behavior... It is not the behaviour with a Squeeze ISO but someone on debian-boot is likely to know whether the change in iso-scan is intentional. I'd say it is worth sending a mail there. > But we need to keep data on USB Stick accessible on the server during all > the install process. > > Please, we need advice on this case. 1. Provide the data on another USB stick, or 2. Write the ISO to a USB stick as in Section 4.3.1. There is free space remaining to partition and format. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130423142206.GB3248@desktop
Bug#685241: task-lxde-desktop: please add a PDF reader to recommends
control: retitle -1 task-lxde-desktop: please add a PDF reader to recommends control: affects -1 lxde Well, 'epdfview' seems to be quite poor application; maybe 'evince-gtk' is a better candidate... Best wishes, Bob
Processed: Re: Bug#685241: task-lxde-desktop: please add a PDF reader to recommends
Processing control commands: > retitle -1 task-lxde-desktop: please add a PDF reader to recommends Bug #685241 [task-lxde-desktop] task-lxde-desktop: please add epdfview into recommends Changed Bug title to 'task-lxde-desktop: please add a PDF reader to recommends' from 'task-lxde-desktop: please add epdfview into recommends' > affects -1 lxde Bug #685241 [task-lxde-desktop] task-lxde-desktop: please add a PDF reader to recommends Added indication that 685241 affects lxde -- 685241: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.b685241.13667333972031.transcr...@bugs.debian.org
Processed: Re: Bug#705878: Change default Debian web browser to Chromium
Processing control commands: > retitle -1 Change default Debian web browser to Chromium Bug #705878 [iceweasel] iceweasel: Change default browser of debian to chromium Changed Bug title to 'Change default Debian web browser to Chromium' from 'iceweasel: Change default browser of debian to chromium' > reassign -1 task-desktop 3.14+nmu2 Bug #705878 [iceweasel] Change default Debian web browser to Chromium Bug reassigned from package 'iceweasel' to 'task-desktop'. No longer marked as found in versions iceweasel/10.0.12esr-1. Ignoring request to alter fixed versions of bug #705878 to the same values previously set Bug #705878 [task-desktop] Change default Debian web browser to Chromium Marked as found in versions tasksel/3.14+nmu2. > affects -1 task-gnome-desktop task-kde-desktop task-lxde-desktop > task-xfce-desktop Bug #705878 [task-desktop] Change default Debian web browser to Chromium Added indication that 705878 affects task-gnome-desktop, task-kde-desktop, task-lxde-desktop, and task-xfce-desktop -- 705878: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705878 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.b705878.13667340256489.transcr...@bugs.debian.org
Re: RFC: initramfs-tools support for early firmware loading
On Mon, Apr 22, 2013 at 19:23:50 -0300, Henrique de Moraes Holschuh wrote: > As of Linux kernel 3.9, support for supplying early firmware data to the > kernel has been added. Currently, it is used for early microcode updates > for Intel processors, and ACPI table overrides. > > This is a very important feature, that we should support as soon as > practical. ACPI table overrides can massage less-than-stellar firmware into > something usable, and early CPU microcode update are the only way (other > than a BIOS upgrade) to avoid certain CPU defects. > > To supply early firmware data to the kernel, we have to *prepend* an > uncompressed cpio archive to the initramfs image. The initramfs image > itself can be compressed as usual. > > Currently, initramfs-tools has undocumented support for appending data to > the initramfs image. This is now useless. We need to enhance > initramfs-tools to support adding arbritary files to a cpio archive that > needs to be prepended to the initramfs image. > Seems a bit odd that you're sending a mail about initramfs-tools to two mailing lists, none of which are the initramfs-tools maintainer? (Hint: that would be initramfs-to...@packages.debian.org, aka debian-ker...@lists.debian.org) Cheers, Julien signature.asc Description: Digital signature
Bug#705971: debian-installer hangs when tty console in use (console-setup)
Control: tags -1 + unreproducible Hello, Stefano Forli, le Mon 22 Apr 2013 15:02:31 -0700, a écrit : > It seems that if a TTY console is in use during the installation, the > whole installation process hangs and can't be recovered (see below). > It is possible to switch to different tty's, but It is not possible to > activate other consoles nor kill the one still active (blinking > cursor, unresponsive). I couldn't reproduce it. I've tried opening the shell on VT2 and VT3, then came back to the main menu to answer until base gets installed, console-setup configured fine. I've also tried to come back to VT2 before console-setup configures, and didn't get a hang. I've tried both with the graphical installer and the text installer. > I'm using the Wheezy netinstaller amd64 downloaded on 4/22/2013 I've done my tests using the rc1 netinst image. How much memory do you have, btw? I've used 1G. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130423205139.gj6...@type.youpi.perso.aquilenet.fr
Processed: Re: Bug#705971: debian-installer hangs when tty console in use (console-setup)
Processing control commands: > tags -1 + unreproducible Bug #705971 [debian-installer] debian-installer hangs when tty console in use (console-setup) Added tag(s) unreproducible. -- 705971: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.b705971.13667503061242.transcr...@bugs.debian.org
Bug#705971: debian-installer hangs when tty console in use (console-setup)
> What do you mean by "a TTY console during the installation"? Lowering the severity anyway as I don't think this is a bug (if one) that affects all installs. With all the install problems reports? I would certainly expect having to open up a shell to fix things to install MORE THAN EVER. One usually one tries to provide more tools to work with for a boot / root install kit not less. but i'm not upgrading the bug report. I have no idea if anyone else can confirm or deny it it ever happened. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5176f8e5.6000...@cox.net
Bug#705971: debian-installer hangs when tty console in use (console-setup)
John D. Hendrickson and Sara Darnell, le Tue 23 Apr 2013 17:11:01 -0400, a écrit : > > > > What do you mean by "a TTY console during the installation"? > >Lowering the severity anyway as I don't think this is a bug (if one) > >that affects all installs. > > With all the install problems reports? I would certainly expect having to > open up a shell to fix things to install MORE THAN EVER. > One usually one tries to provide more tools to work with > for a boot / root install kit not less. I have often used it, yes. > but i'm not upgrading the bug report. I have no idea if anyone > else can confirm or deny it it ever happened. As I said in another mail, I was unable to reproduce it (and never seen this kind of issue). Thus keeping the priority low. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130423212141.gl6...@type.youpi.perso.aquilenet.fr
Bug#705961: installation-reports: debian-installer does not create an EFI partition by default
Hi Steve, I am afraid I can not repeat the whole installation. I have copied already all teh files I had in my old computer to the new one, so it would be a mess to repeat the whole process again. I have made an exercise, but I don't think it is very useful. I just repeated the first steps of the installation (with cdnetinst of 20130423) until the step of the partition: - I started the Linux CD through the UEFI loader - I got the weird error message of the "prefix" while loading the installer grub (I remember to see this one also during a former installation) - In the partitions step, I deleted my current Linux partitions and asked the guided partition to propose new partitions. It made just one partition for Linux and one for swap. Then I did not want to commit the changes proposed, so I just left. But I think to remember that in my former installation the program issues a warning after that saying that I have no EFI partitions defined (while actually there is one of ~300 MB in fat32, the Windows one). I am sorry I can not go beyond this point. I have the suspicion that the problem may have to do with an HP loader that is what actually use to boot Windows if I do not pass through Linux GRUB. Anyway, if nobody else complains it mens that this was an effect of the failed installation I made with Squeeze before. You can close the bug, at least from my side. Thanks a lot for your help. Cheers, Jorge I believe so. I certainly had that intention, and I don't think the d-i would have seen the former partitions as EFI if booting in legacy mode, right?I remember to see that weird message "prefix not found", but I do not remember in which boot. I am sorry I could nto send this report before, I would have this information more fresh in my mind. I hope it helps, but if you do not receive any similar report it may have to do with the two trials of installation before the succesful one. Yes, I think so. If you're prepared to delete your existing Debian installation and try again from scratch using Wheezy, that's more likely to work. But I understand if you don't want to spend the time on that now...!
Re: RFC: initramfs-tools support for early firmware loading
On Tue, 23 Apr 2013, Julien Cristau wrote: > On Mon, Apr 22, 2013 at 19:23:50 -0300, Henrique de Moraes Holschuh wrote: > > As of Linux kernel 3.9, support for supplying early firmware data to the > > kernel has been added. Currently, it is used for early microcode updates > > for Intel processors, and ACPI table overrides. > > > > This is a very important feature, that we should support as soon as > > practical. ACPI table overrides can massage less-than-stellar firmware into > > something usable, and early CPU microcode update are the only way (other > > than a BIOS upgrade) to avoid certain CPU defects. > > > > To supply early firmware data to the kernel, we have to *prepend* an > > uncompressed cpio archive to the initramfs image. The initramfs image > > itself can be compressed as usual. > > > > Currently, initramfs-tools has undocumented support for appending data to > > the initramfs image. This is now useless. We need to enhance > > initramfs-tools to support adding arbritary files to a cpio archive that > > needs to be prepended to the initramfs image. > > > Seems a bit odd that you're sending a mail about initramfs-tools to two > mailing lists, none of which are the initramfs-tools maintainer? (Hint: > that would be initramfs-to...@packages.debian.org, aka > debian-ker...@lists.debian.org) Meh, my bad. I will repost there, and drop debian-boot. Thanks! -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130423232637.ga13...@khazad-dum.debian.net
Re: [rfc patch] grub-installer - help please
On Mon, Apr 22, 2013 at 02:38:24PM +1000, Vincent McIntyre wrote: > Hi, > > I am attempting to fix the grub-installer issues last referenced in the > thread "# d-i wheezy rc2 preparation, take 2". The current state of my > patch is shown at the end of this message. The basic idea is to add a > question which lets the user select which disk to use for installation > of the grub bootloader and show this when appropriate. > > I built a modified udeb and installed it with udpkg near the end of the > installation, after tasksel was complete. > > The problem I am having is that debconf is failing with an 'internal error', > error code 100 when I try to have the new question asked. > Can anyone see what I am doing wrong with the way I am asking debconf to > do things? The syslog, when I run my modified version from a terminal > in the installer (DEBCONF_DEBUG=5 sh grub-installer /target) > looks like this: I resolved the issue (I was missing the Choices and Choices-C fields in the template file). I've got a tested patch now and it seems to be working, will post it shortly. Vince -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130424004541.ga23...@mayhem.atnf.csiro.au
[PATCH] grub-installer: Support menu selection of grub boot disk
Support user selection of grub boot disk from a list of disks
via a new question, grub-installer/choose_bootdev.
Check for a mismatch between a preseeded value of grub-installer/bootdev
and the guess at the default boot disk made by grub-installer,
and prompt the user to choose the correct disk.
This should help the user avoid grub-installer writing to the MBR
of the wrong device (e.g. #696877) and fix the issue of preseeded
values of bootdev being ignored (e.g. #666974).
Signed-off-by: Vincent McIntyre
---
debian/grub-installer.templates | 16 +
debian/po/templates.pot | 17 +
grub-installer | 130 +--
3 files changed, 159 insertions(+), 4 deletions(-)
diff --git a/debian/grub-installer.templates b/debian/grub-installer.templates
index 888a656..5d15411 100644
--- a/debian/grub-installer.templates
+++ b/debian/grub-installer.templates
@@ -86,6 +86,22 @@ _Description: Device for boot loader installation:
drive;
- "/dev/fd0" will install GRUB to a floppy.
+Template: grub-installer/choose_bootdev
+Type: select
+Choices-C: ${CHOICES}
+Choices: ${DESCRIPTIONS}
+# :sl2:
+_Description: Select disk for boot loader installation:
+ You need to make the newly installed system bootable, by installing
+ the GRUB boot loader on a bootable device. The usual way to do this is to
+ install GRUB on the master boot record of your first hard drive. If you
+ prefer, you can install GRUB elsewhere on the drive, or to another drive,
+ or even to a floppy.
+ .
+ Select a disk from the list. GRUB will be installed to the master boot
+ record of that disk. If you want to install GRUB somewhere other than the
+ master boot record of one of these disks, select 'Enter device manually'.
+
Template: grub-installer/password
Type: password
# :sl2:
diff --git a/debian/po/templates.pot b/debian/po/templates.pot
index dad01db..54085e6 100644
--- a/debian/po/templates.pot
+++ b/debian/po/templates.pot
@@ -198,6 +198,23 @@ msgid ""
" - \"/dev/fd0\" will install GRUB to a floppy."
msgstr ""
+#. Type: string
+#. Description
+#. :sl2:
+#: ../grub-installer.templates:7001
+msgid "Select disk for boot loader installation:"
+msgstr ""
+
+#. Type: string
+#. Description
+#. :sl2:
+#: ../grub-installer.templates:7001
+msgid ""
+"Select a disk from the list. GRUB will be installed to the master boot\n"
+"record of that disk. If you want to install GRUB somewhere other than the\n"
+"master boot record of the listed disks, select 'Enter device manually'.\n"
+msgstr ""
+
#. Type: password
#. Description
#. :sl2:
diff --git a/grub-installer b/grub-installer
index f01eda1..8eefd23 100755
--- a/grub-installer
+++ b/grub-installer
@@ -1,5 +1,5 @@
#! /bin/sh
-
+# export DEBCONF_DEBUG=5
set -e
. /usr/share/debconf/confmodule
#set -x
@@ -217,6 +217,51 @@ devices_to_ids()
echo "$ids"
}
+
+# Produce a comma-separated list of '/dev/X (id)' strings suitable for debconf.
+# The first argument will select /dev/X or (id) strings to be returned.
+# The second argument will cause that to be the only one returned.
+# Examples:
+# echo $(device_list)
+# /dev/sda (ata-SAMSUNG_SSD_PM810_2.5__7mm_128GB_S0NRNEABC02304), /dev/sdb
(ata-WDC_WD2002FAEX-007BA0_WD-WMAY05111513)
+# echo $(device_list description /dev/sdb)
+# (ata-WDC_WD2002FAEX-007BA0_WD-WMAY05111513)
+
+device_list()
+{
+ [ -d /dev/disk/by-id ] || return
+
+ local result arg id path dev disk output
+
+ result="$1"
+ case "$result" in
+ /*) result="both"; arg="$1" ;;
+*) arg="$2" ;;
+ esac
+ case "$result" in
+ disk*|device*) filter_dev() { cut -d' ' -f1; }; ;;
+ description*) filter_dev() { cut -d' ' -f2; }; ;;
+ *) filter_dev() { cat; }; ;;
+ esac
+
+ # /dev/disk/by-id has multiple links for the same physical disk.
+ # Sorting the output on only one column gives just one disk,path pair
+ # for each physical disk. Then filter to get the column(s) requested.
+ output="$(
+ for path in /dev/disk/by-id/*; do
+ [ -e "$path" ] || continue
+ id="$(echo "$path" | sed -e 's+^.*/++')"
+ dev="$(readlink -f "$path")"
+ disk="$(device_to_disk "$dev")"
+ [ -n "$arg" ] && dev="$arg"
+ [ "$dev" = "$disk" ] && printf '%s (%s)\n' "$disk" "$id"
+ done | \
+ sort -k1,1 -s -u | filter_dev | sed -e 's/$/, /'
+ )"
+ output="$(echo $output | sed -e 's/, *$//')"
+ echo "$output"
+}
+
rootfs=$(findfs /)
bootfs=$(findfs /boot)
[ -n "$bootfs" ] || bootfs="$rootfs"
@@ -590,7 +635,66 @@ esac
db_progress STEP 1
db_progress INFO grub-installer/progress/step_bootdev
+select_bootdev() {
+ [ "X" = "X${DEBCONF_DEBUG}" ] || log "select_bootdev: arg='$1'"
+
+ local manual_entry
Bug#705259: Only some EFI systems affected
It seems on the Lenovo (and all UEFI systems?) Windows is not anymore booted through the nt loader but through an efi boot loader residing in the efi partition. I can assert that some EFI systems are not affected by this. My Windows 8 install on an ASUS F2A85-M can be booted from the GRUB entry, which is similar to the one GRUB generated for Dieter. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51774186.4060...@gmail.com
