Bug#601069: Squeeze Installation Report
Package: installation-reports Boot method: USB stick (zcat boot.img.gz > /dev/sdc) Image version: http://people.debian.org/~joeyh/d-i/images/daily/hd-media/boot.img.gz http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso Date: 23 October 2010 14:00 +1300 (NZDT) Machine: Gigabyte Mini-ITX board Processor: Intel Atom Memory: 2Gb Partitions: /dev/sda1 ext3 9611492683468 8439784 8% / tmpfstmpfs 1032220 4 1032216 1% /lib/init/rw udev tmpfs 1027896 144 1027752 1% /dev tmpfstmpfs 1032220 0 1032220 0% /dev/shm /dev/sda6 ext3 467139176202884 443206988 1% /home Output of lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation N10 Family DMI Bridge [8086:a000] (rev 02) Subsystem: Giga-byte Technology Device [1458:5000] Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller [0300]: Intel Corporation N10 Family Integrated Graphics Controller [8086:a001] (rev 02) Subsystem: Giga-byte Technology Device [1458:d000] 00:1b.0 Audio device [0403]: Intel Corporation N10/ICH 7 Family High Definition Audio Controller [8086:27d8] (rev 02) Subsystem: Giga-byte Technology Device [1458:a002] Kernel driver in use: HDA Intel 00:1c.0 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 1 [8086:27d0] (rev 02) Kernel driver in use: pcieport 00:1c.1 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 2 [8086:27d2] (rev 02) Kernel driver in use: pcieport 00:1d.0 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 [8086:27c8] (rev 02) Subsystem: Giga-byte Technology Device [1458:5004] Kernel driver in use: uhci_hcd 00:1d.1 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 [8086:27c9] (rev 02) Subsystem: Giga-byte Technology Device [1458:5004] Kernel driver in use: uhci_hcd 00:1d.2 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 [8086:27ca] (rev 02) Subsystem: Giga-byte Technology Device [1458:5004] Kernel driver in use: uhci_hcd 00:1d.3 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 [8086:27cb] (rev 02) Subsystem: Giga-byte Technology Device [1458:5004] Kernel driver in use: uhci_hcd 00:1d.7 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller [8086:27cc] (rev 02) Subsystem: Giga-byte Technology Device [1458:5006] Kernel driver in use: ehci_hcd 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev e2) 00:1f.0 ISA bridge [0601]: Intel Corporation NM10 Family LPC Controller [8086:27bc] (rev 02) Subsystem: Giga-byte Technology Device [1458:5001] 00:1f.2 SATA controller [0106]: Intel Corporation N10/ICH7 Family SATA AHCI Controller [8086:27c1] (rev 02) Subsystem: Giga-byte Technology Device [1458:b005] Kernel driver in use: ahci 00:1f.3 SMBus [0c05]: Intel Corporation N10/ICH 7 Family SMBus Controller [8086:27da] (rev 02) Subsystem: Giga-byte Technology GA-8I945PG-RH Mainboard [1458:5001] Kernel driver in use: i801_smbus 01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06) Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard [1458:e000] Kernel driver in use: r8169 02:00.0 SATA controller [0106]: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller [197b:2363] (rev 02) Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard [1458:b000] Kernel driver in use: ahci 02:00.1 IDE interface [0101]: JMicron Technology Corp. JMB362/JMB363 Serial ATA Controller [197b:2363] (rev 02) Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard [1458:b000] Kernel driver in use: pata_jmicron 03:00.0 Network controller [0280]: RaLink RT2561/RT61 802.11g PCI [1814:0301] Subsystem: ASUSTeK Computer Inc. Device [1043:837e] Kernel driver in use: rt61pci Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[0] Configure network: [0] Detect CD: [n/a] Load installer modules: [0] Detect hard drives: [0] Partition hard drives: [0] Install base system:[0] Clock/timezone setup: [0] User/password setup:[0] Install tasks: [0] Install boot loader:[0] Overall install:[0] Comments/Problems: Text installer. In the task selection menu, I wasn't sure how to select/deselect individual tasks. I ended up putting the cursor on the first box (graphical desktop install) and hitting to see what would happen. Well, the system raced off and started doing a graphical desktop install - which I didn't want! The only option seemed to be to abort the install and start again from the beginning. I now see that some other screens have a note at the bottom ' to select'. I think this would help considerably on the tasks menu. Overall, a nice clean
Bug#600861: [console-setup-mini] Package console-setup-mini needs to be xserver installed?
Marek Straka, le Fri 22 Oct 2010 15:11:31 +0200, a écrit : > >> Why is Bugreport Nr. 546983 > >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=546983 > >> not listed under bugreports of console-setup-mini: > >> http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=console-setup-mini > > > >Err, because it is fixed. We don't keep all the 600 000 bugs on the > >summary pages, that'd be unreadable. > > There was listed only 1 resolved bug. If there would be 2, it would not > be "unreadable". You are talking about console-setup which is a very recent package, thus very few bug reports overall. Think about packages like bash, which have like a hundred bugs that are still open. Add to that 5 hundreds old bugs, clearly you don't want to show them any more, as they're supposed to be fixed. > There was quite well described how this package works. > And last commit was on 22 Nov 2009. Most usefull hints: Ok, I'm just saying that these aren't useful to fix the bug at stake here. > If the installation of xkb-data helps to setup keymap for console even > before installation of xserver, it could be in "Recommended". Anton will actually fix the scripts which don't actually depend on it. 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/20101022143053.ga5...@const.bordeaux.inria.fr
Bug#600861: [console-setup-mini] Package console-setup-mini needs to be xserver installed?
>> Why is Bugreport Nr. 546983 >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=546983 >> not listed under bugreports of console-setup-mini: >> http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=console-setup-mini > >Err, because it is fixed. We don't keep all the 600 000 bugs on the >summary pages, that'd be unreadable. There was listed only 1 resolved bug. If there would be 2, it would not be "unreadable". There was quite well described how this package works. And last commit was on 22 Nov 2009. Most usefull hints: --- I am unable to reproduce this. Can you make the following tests: 1. What happens if you run on the console 'setupcon' as root? 2. What happens if you run on the console /etc/init.d/keyboard-setup start 3. What happens if you run on the console /etc/init.d/console-setup start 4. If all this works that check that there are files /etc/rcS.d/S06keyboard-setup and /etc/rcS.d/S49console-setup 5. If some of this doesn't work, then open /etc/default/console-setup and put there VERBOSE_OUTPUT=yes Then send the output of 'setupcon' --- If the installation of xkb-data helps to setup keymap for console even before installation of xserver, it could be in "Recommended". Maybe in the future could be in bug summary page of any package link somewhere to http://wiki.debian.org/any_package where would be described how this package works. My problem is done - so this can be closed. -- 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/20101022151131.38ae5...@straka.info
Bug#601011: debootstrap: Fails without an error when it can't create devices
On Fri, Oct 22, 2010 at 03:04:28PM +0200, Mike Hommey wrote: > Package: debootstrap > Version: 1.0.25 > Severity: important > > When debootstrap can't extract devices.tar.gz for some reason, it exists > with an error code 2, but doesn't say anything as to why it failed. > > Following with strace, it appears the one failing is tar, because it can't > extract (mknod) the devices from devices.tar.gz. This happened on my system > because I was trying to debootstrap from within an lxc instance created > with the default template which disabled a whole bunch of devices. > > Please at least handle the error and display tar's error message. > > A bonus point if you just ignore the error, as the failing devices here were > really not important to the chroot: > dev/full > dev/kmem > dev/loop* > dev/mem > dev/port > dev/ram* FWIW, cdebootstrap doesn't create these expect dev/full, which it fails to create but doesn't care. Mike -- 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/20101022131903.ga16...@glandium.org
Bug#571136: please remove useless devices from devices.tar.gz
On Tue, Feb 23, 2010 at 07:58:17PM +0100, Marco d'Itri wrote: > Package: debootstrap > Version: 1.0.20 > Severity: normal > > devices.tar.gz should contain only the devices which are strictly > needed, even if udev is not installed the others can be created by > makedev. > > At least the ram* devices should be removed because they were needed > by initrds and are not useful anymore. > > Why create loop*? > > Why create mem kmem core port? > > FYI, the only devices needed by udev to start are null and console. FWIW, the inclusion of these devices in devices.tar.gz makes debootstrap fail without even a message (filed a separate bug for that) when tar can't mknod the devices (which happens from within a lxc container with the default template). Note cdebootstrap either doesn't create them or doesn't care if it can't create them. Cheers, Mike -- 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/20101022130650.ga16...@glandium.org
Bug#601011: debootstrap: Fails without an error when it can't create devices
Package: debootstrap Version: 1.0.25 Severity: important When debootstrap can't extract devices.tar.gz for some reason, it exists with an error code 2, but doesn't say anything as to why it failed. Following with strace, it appears the one failing is tar, because it can't extract (mknod) the devices from devices.tar.gz. This happened on my system because I was trying to debootstrap from within an lxc instance created with the default template which disabled a whole bunch of devices. Please at least handle the error and display tar's error message. A bonus point if you just ignore the error, as the failing devices here were really not important to the chroot: dev/full dev/kmem dev/loop* dev/mem dev/port dev/ram* Cheers, Mike -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages debootstrap depends on: ii wget 1.12-2.1 retrieves files from the web Versions of packages debootstrap recommends: ii gnupg 1.4.10-4 GNU privacy guard - a free PGP rep debootstrap suggests no packages. -- no debconf information -- 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/20101022130428.16347.31045.report...@jigen.glandium.org
Bug#600861: [console-setup-mini] Package console-setup-mini needs to be xserver installed?
On Fri, Oct 22, 2010 at 01:30:17AM +0200, Samuel Thibault wrote: > > if \ > [ "$VARIANT" = '' ] \ > && which gzip >/dev/null \ > && [ -d /usr/share/X11/xkb ] # /usr is mounted > then > if \ > [ ! -f /etc/console-setup/cached.kmap.gz ] \ > || [ /etc/console-setup/cached.kmap.gz \ > etc. > > setupcon checks for /usr/share/X11/xkb, but console-setup-mini doesn't > depend on xkb-data, which provides that directory. Is that on purpose? > If so, console-setup-mini should at least recommend it, to get it > working by default. Console-setup-mini doesn't need xkb-data. The bug is in the test setupcon uses to see if /usr is mounted. The line && [ -d /usr/share/X11/xkb ] # /usr is mounted has to be replaced by && [ -d /usr/share ] # /usr is mounted Anton Zinoviev -- 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/20101022082816.ga11...@debian.lan
