Bug#688346: installation-reports: Impossible boot with LVM crypted disk on non-QWERTY keyboard
Le 21/09/2012 22:20, Marc-Aurèle DARCHE a écrit : The problem lies in the fact that the system mapping for the keyboard is wrong at boot time when the passphrase is asked I should have added that this keyboard mapping problem is a regression from Squeeze. Warm regards, -- Marc-Aurèle DARCHE AFUL http://aful.org/ Association Francophone des Utilisateurs de Logiciels Libres French speaking Libre Software Users' Association -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607392: installation-reports: Successful installation with small remark about char encoding at boot
Quoting M.-A. DARCHE (ma.dar...@cynode.org): Just one remark about 2 small character encoding problems. Here they are: 1. mode (d??panage) 2. Chargement du disque m??moir initial And actually this is the whole GRUB screen which seems badly encoded/displayed. Here is what it reads: « Debian GNU/Linux, avec Linux 2.6.32-5-amd64 Debian GNU/Linux, avec Linux 2.6.32-5-amd64 (mode d?pannage) Utilisez les touches pour s?lectionner une entr?e. Pressez 'entr?e' pour d?marrer le syst?me s?lectionn?, 'e' pour ?diter les commandes avant de d?marrer, ou 'c' pour une invite de commandes. » The point 1. (bad encoding for at least the French translation for the whole GRUB screen) is now fixed. It seems that it has been fixed by the upload to testing of the following packages: grub-common 1.98+20100804-11 grub-pc 1.98+20100804-11 And the point 1. was really the more important. But the point 2. is not fixed yet: In /boot/grub/grub.cfg there is this line echo'Chargement du disque mémoire initial ...' but at the system boot it is displayed as Chargement du disque m??moire initial ... = the accented character is replace by ??. Très cordialement / warm regards -- Marc-Aurèle DARCHE AFUL http://aful.org/ Association Francophone des Utilisateurs de Logiciels Libres French speaking Libre Software Users' Association -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546836: xserver-xorg-video-mga: Hit by this bug too: Failed to initialize DMA! (-2)
Package: xserver-xorg-video-mga Version: 1:1.4.11.dfsg-4 Severity: normal Hello, I am, too, hit by the same bug. And for me too, the only solution has been to switch to the vesa Driver instead of the mga Driver :-( Everything worked fine with Matrox cards on Debian while XFree was used. Since the switch to Xorg in Lenny, it started to do X freezes and now in Squeeze it does black screens. I'm providing this Xorg.*.log file that features the message Failed to initialize DMA so that this bug report is more easily found by users having the same problem and hopefully to developers that can help. Cheers -- Package-specific info: /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 Dec 23 16:25 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1889472 Dec 2 02:16 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 03:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G550 AGP (rev 01) /var/lib/x11/xorg.conf.md5sum does not exist. Kernel version (/proc/version): Linux version 2.6.32-5-amd64 (Debian 2.6.32-29) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Fri Dec 10 15:35:08 UTC 2010 Xorg X server log files on system: -rw-r--r-- 1 root root 34080 Jan 2 18:40 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32.26-dsa-amd64 x86_64 Debian Current Operating System: Linux systema 2.6.32-5-amd64 #1 SMP Fri Dec 10 15:35:08 UTC 2010 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/systema-root ro quiet Build Date: 02 December 2010 01:10:32AM xorg-server 2:1.7.7-10 (Julien Cristau jcris...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Thu Dec 30 17:49:35 2010 (==) Using system config directory /usr/share/X11/xorg.conf.d (==) No Layout section. Using the first Screen section. (==) No screen section available. Using defaults. (**) |--Screen Default Screen Section (0) (**) | |--Monitor default monitor (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (WW) `fonts.dir' not found (or not valid) in /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType. Entry deleted from font path. (Run 'mkfontdir' on /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType). (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins (==) ModulePath set to /usr/lib/xorg/modules (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. (II) Loader magic: 0x7c7500 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (--) using VT number 8 (--) PCI:*(0:3:0:0) 102b:2527:102b:22c0 Matrox Graphics, Inc. MGA G550 AGP rev 1, Mem @ 0xf000/33554432, 0xf200/16384, 0xf300/8388608, BIOS @ 0x/131072 (II) Open ACPI successful (/var/run/acpid.socket) (II) LoadModule: extmod (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension SELinux (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: dbe (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so (II) Module dbe: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: glx (II) Loading /usr/lib/xorg/modules/extensions/libglx.so (II) Module glx: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0
Bug#608265: installation-reports: Successful installation (SCSI + SATA + IDE) with small remarks
Package: installation-reports Severity: normal Tags: d-i -- Package-specific info: Boot method: Netinst USB Image version: http://cdimage.debian.org/cdimage/squeeze_di_beta2/amd64/iso-cd/debian-squeeze-di-beta2-amd64-netinst.iso http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/hd-media/boot.img.gz Date: 2010-12-23 Machine: Assembled PC workstation (SCSI + SATA + IDE) Partitions: FilesystemType 1K-blocks Used Available Use% Mounted on /dev/mapper/systema-root ext333559340 3485244 28369344 11% / tmpfstmpfs 2031064 0 2031064 0% /lib/init/rw udev tmpfs 2025556 220 2025336 1% /dev tmpfstmpfs 2031064 0 2031064 0% /dev/shm /dev/sda1 ext2 233191 18794201956 9% /boot Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Here are below the remarks on the small problems that I've found. The remarks are ordered by increasing importance. So let's start with the less critical. A. As one could expect, #607392 is still present in this install since it uses the same images B. On the keyboard layout screen the choice for the French layout is written as follows: Français (fr-latin9). I think this should simply be written as Français. The situation for the French keyboard layout, where there is only one choice, is not the same as for Brazilian where there are two layouts to choose from Brazilian (br-abnt2) and Brazilian (br-latin1). C. In the installed system one can read in /etc/fstab: Use 'vol_id --uuid' to print the universally unique identifier while the vol_id program was not to be found on the system after it was installed. And apt-file search vol_id only indicates that fai-setup-storage: /usr/lib/fai/fai-vol_id not vol_id. There is the blkid utility in the util-linux package that could act as a replacement for vol_id and could be advertised as such in /etc/fstab, but I've found blkid to have a buggy or confusing behavior when printing its output to the console, so reincluding vol_id in a package and in the installed system might be the simplest and best solution. D. At the partition stage I've had a hard time that required me to redo an install. I was installing from an USB key with an .iso on it but at the same time there were 2 hard drives plugged to the system with both ext3 partitions on them and one of those disks was a previous installation of Debian. The installer first tried to find an .iso on those hard-drive partitions and failed with somehow alarming messages and colors while it should better have waited until scaning the USB key to find the .iso on it. While scaning the hard-drives for ..iso it mounted their partitions, without (properly) umounting them and those partitions were then not available for me to choose at the Partition hard drives stage. The installer told me that those partitions were mounted (sorry I have not the exact message anymore) and that I should unmount them before being able to partition them, but switching to the console it seems to indicate that no such partitions were mounted. So my recommendations would be: - Don't alert the user that no .iso is found before scanning all possible media (HD, USB, etc.) - Be sure to unmount every partition checked for finding .iso files (even if no .iso was found) and be sure to don't keep false information about what partition is mounted (even if no .iso was found) And of course thanks again for your good and hard work :-) -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=6.0 (squeeze) - installer build 20101127 X_INSTALLATION_MEDIUM=hd-media == Installer hardware-summary: == uname -a: Linux systema 2.6.32-5-amd64 #1 SMP Sat Oct 30 14:18:21 UTC 2010 x86_64 GNU/Linux lspci -knn: 00:00.0 RAM memory [0500]: nVidia Corporation MCP55 Memory Controller [10de:0369] (rev a1) lspci -knn: Subsystem: Giga-byte Technology Device [1458:5001] lspci -knn: 00:01.0 ISA bridge [0601]: nVidia Corporation MCP55 LPC Bridge [10de:0360] (rev a2) lspci -knn:
Bug#607392: installation-reports: Successful installation with small remark about char encoding at boot
Le 18.12.2010 08:14, Christian PERRIER a écrit : Quoting M.-A. DARCHE (ma.dar...@cynode.org): Just one remark about 2 small character encoding problems. Here they are: 1. mode (d??panage) 2. Chargement du disque m??moir initial The 1. appears on the 2nd bootloader line. This corresponds to the French translation of rescue mode, with the accented character being replaced by ?. The 2. appears when mounting an dm-crypt device. I don't really understand what you mean by 2nd bootloader line. Could you give us the steps needed to reproduce the bug you found? Is this what you see on the installed system? I confirm that this is what I see on the installed system, just installed by the Debian Installer. The boot loader I'm talking about is the GRUB screen that is displayed at the boot time, and that got installed by the Debian Installer. And actually this is the whole GRUB screen which seems badly encoded/displayed. Here is what it reads: « Debian GNU/Linux, avec Linux 2.6.32-5-amd64 Debian GNU/Linux, avec Linux 2.6.32-5-amd64 (mode d?pannage) Utilisez les touches pour s?lectionner une entr?e. Pressez 'entr?e' pour d?marrer le syst?me s?lectionn?, 'e' pour ?diter les commandes avant de d?marrer, ou 'c' pour une invite de commandes. » And then after I hit Enter in Grub the Linux kernel messages are the following: « Chargement de Linux 2.6.32-5-amd64 ... Chargement du disque m??moire initial ... » So I did a mistake in my initial report: it's one « ? » for each accented character at the GRUB screen, and then two « ? » at the following kernel messages. Please let me know how I can help further. Très cordialement / warm regards -- Marc-Aurèle DARCHE AFUL http://aful.org/ Association Francophone des Utilisateurs de Logiciels Libres French speaking Libre Software Users' Association -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607392: installation-reports: Successful installation with small remark about char encoding at boot
Package: installation-reports Severity: minor Tags: d-i -- Package-specific info: Boot method: Netinst USB Image version: http://cdimage.debian.org/cdimage/squeeze_di_beta2/amd64/iso-cd/debian-squeeze-di-beta2-amd64-netinst.iso http://ftp.nl.debian.org/debian/dists/testing/main/installer-amd64/current/images/hd-media/boot.img.gz Date: 2010-12-16 Machine: Lenovo ThinkPad X300 Partitions: FilesystemType 1K-blocks Used Available Use% Mounted on /dev/mapper/systema-root ext358757308 34397056 21375500 62% / tmpfstmpfs 1009580 0 1009580 0% /lib/init/rw udev tmpfs 1004076 236 1003840 1% /dev tmpfstmpfs 1009580 0 1009580 0% /dev/shm /dev/sda1 ext2 233191 16277204473 8% /boot Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Everything perfect. Thanks a lot for all your wonderful work. Just one remark about 2 small character encoding problems. Here they are: 1. mode (d??panage) 2. Chargement du disque m??moir initial The 1. appears on the 2nd bootloader line. This corresponds to the French translation of rescue mode, with the accented character being replaced by ?. The 2. appears when mounting an dm-crypt device. Best and warm regards -- == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=6.0 (squeeze) - installer build 20101127 X_INSTALLATION_MEDIUM=hd-media == Installer hardware-summary: == uname -a: Linux systema 2.6.32-5-amd64 #1 SMP Sat Oct 30 14:18:21 UTC 2010 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 0c) lspci -knn: Subsystem: Lenovo Device [17aa:20b3] lspci -knn: Kernel driver in use: agpgart-intel lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c) lspci -knn: Subsystem: Lenovo Device [17aa:20b5] lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a03] (rev 0c) lspci -knn: Subsystem: Lenovo Device [17aa:20b5] lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82566MM Gigabit Network Connection [8086:1049] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20b9] lspci -knn: Kernel driver in use: e1000e lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 [8086:2834] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20aa] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 [8086:2835] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20aa] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 [8086:283a] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20ab] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio Controller [8086:284b] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20ac] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 [8086:283f] (rev 03) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 [8086:2841] (rev 03) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 [8086:2843] (rev 03) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 [8086:2830] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20aa] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 [8086:2831] (rev 03) lspci -knn: Subsystem: Lenovo Device [17aa:20aa] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1d.2 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 [8086:2832] (rev 03) lspci -knn: Subsystem:
Bug#511679: installation-guide-i386: Provide information on how to restore USB stick to its previous state
Otavio Salvador a écrit : Hello, On Sun, Nov 15, 2009 at 7:01 AM, M.-A. DARCHE ma.dar...@cynode.org wrote: parted mklabel your usbstick msdos $ LC_ALL=C sudo parted mklabel /dev/sdb msdos Error: Could not stat device mklabel - No such file or directory. Retry/Cancel? Sorry, my fault. parted /dev/sdb mklabel msdos You can use: parted /dev/sdb mkpart To create a partition on it. After that you'll need to format it later. Here are the operations below: $ sudo parted /dev/sdb mklabel msdos Warning: The existing disk label on /dev/sdb will be destroyed and all data on this disk will be lost. Do you want to continue? parted: invalid token: msdos Yes/No? yes New disk label type? [msdos]? Information: You may need to update /etc/fstab. $ sudo parted /dev/sdb mkpart primary fat32 0 1041 Information: You may need to update /etc/fstab. [I have tried different values for end, and 1041 is the highest that is accepted. Otherwise I get error message such as: Error: The location 1042 is outside of the device /dev/sdb.] $ /sbin/fdisk -l /dev/sdb Disk /dev/sdb: 1040 MB, 1040187392 bytes 118 heads, 55 sectors/track, 313 cylinders Units = cylinders of 6490 * 512 = 3322880 bytes Disk identifier: 0x000810f9 Device Boot Start End Blocks Id System /dev/sdb1 1 314 1015807+ c W95 FAT32 (LBA) Partition 1 has different physical/logical endings: phys=(126, 117, 55) logical=(313, 4, 26) $ mount /media/usb $ df /dev/sdb1 991M 4,0K 991M 1% /media/usb The capacity is still of the original 2Gb :-( Thanks again for your help and giving me this hint on parted. Cheers, -- Marc-Aurèle DARCHE AFUL http://www.aful.org/ Association Francophone des Utilisateurs de Logiciels Libres French speaking Libre Software Users' Association -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511679: installation-guide-i386: Provide information on how to restore USB stick to its previous state
Otavio Salvador a écrit : On Sat, Nov 14, 2009 at 3:29 PM, M.-A. DARCHE ma.dar...@cynode.org wrote: parted behaves very strangely on my Debian Lenny stable. It accepts only to work on mounted partitions. Is that how it should be? No, it should work on devices as well. That seems logical to me that it should behave that way, but it doesn't seem to do so, at least with the stable version (parted 1.8.8.git.2008.03.2) and on my setup :'( What worries me is that you had pasted dd erasing whole device and this would destroy the MBR as well and then it might not be a MBR issue. OK, I thought that somehow the MBR would not be affected by dd operations. If you: dd if=/dev/zero of=your usbstick OK done partprobe $ sudo partprobe $ echo $? 0 parted mklabel your usbstick msdos $ LC_ALL=C sudo parted mklabel /dev/sdb msdos Error: Could not stat device mklabel - No such file or directory. Retry/Cancel? Thanks for your help and time on this -- Marc-Aurèle DARCHE AFUL http://www.aful.org/ Association Francophone des Utilisateurs de Logiciels Libres French speaking Libre Software Users' Association -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511679: installation-guide-i386: Provide information on how to restore USB stick to its previous state
Otavio Salvador a écrit : Hello, Hello Debian :-) It took me some time to answer because I wanted to do some more tests prior to answering. On Fri, Nov 6, 2009 at 4:13 AM, Frans Pop elen...@planet.nl wrote: Did you ever find a procedure that restored the stick to its full capacity? No I did not find any procedure that could restore the stick to its full original capacity. I did some more research and tests (see below) with no success and I lost hope, sticking with my now 1Gb USB stick. So I think the installation guide should at least state: - there are some risks to lose original capacity - do a full image backup to restore the USB-stick afterward ... and that could make this ticket closed since we haven't anything better to propose so far. Of course I'm still interested to read there if someone can provide a solution. Tests done == 1. dd - I have used dd again = still 1.0Gb capacity :-( $ sudo LC_ALL=C dd if=/dev/zero of=/dev/sdb dd: writing to `/dev/sdb': No space left on device 2031617+0 records in 2031616+0 records out 1040187392 bytes (1.0 GB) copied, 326.42 s, 3.2 MB/s SDFormatter --- The SD Association was mentionned many times on help forums, etc. along with their http://www.sdcard.org/consumers/formatter/ It could only run on Windows systems. So I had to get a VM with Windows on it to be able to test it. I did all the possible format operations (quick, full, erase on | off, format size adjustment on | off) with no success. I suspect the solution to be in the MBR somehow ... and I don't know what to modify *inside* the MBR. parted mklabel msdos ought to clear it up (and you'll lose your data) but after creating new partition it ought to continue to work. Does it work for you? parted behaves very strangely on my Debian Lenny stable. It accepts only to work on mounted partitions. Is that how it should be? Cheers, -- Marc-Aurèle DARCHE AFUL http://www.aful.org/ Association Francophone des Utilisateurs de Logiciels Libres French speaking Libre Software Users' Association -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510176: Info received (Bug#510176: installation-reports: No network through DHCP router)
This ticket can be closed since the device has been damaged and doesn't work anymore. Cheers, -- Marc-Aurèle DARCHE AFUL http://www.aful.org/ Association Francophone des Utilisateurs de Logiciels Libres French speaking Libre Software Users' Association -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510176: installation-reports: No network through DHCP router speedtouch 530
M.-A. DARCHE a écrit : Frans Pop a écrit : On Tuesday 06 January 2009, M.-A. DARCHE wrote: Could there be a problem in the way the ethernet card is labeled or tracked by the installer? If so, is there a way to make the dhcpdiscover try on all available interfaces instead of only the one detected/selected? I doubt that. And as we don't have any other reports of DHCP not working during installation, my bet is on a local network problem. OK. But strange because other Debian boxes can get leases from this DHCP router. Since my last email I have changed of ISP to have a wider bandwidth. My two Debian boxes (1 Etch and 1 Lenny) both manage to connect without any problem to the brand new DHCP router modem (which is no more a SpeedTouch 530). But the installation still fails. I'm attaching to this email the new debian-installer log obtained with the new ISP and new DHCP router modem. This was obtained with 20090126 daily netboot image. So I would tend to conclude that this is not a local network problem, but rather a hardware one. I have one other experiment I'll try tomorrow: installing another machine on the same local network. I'll keep you posted. There are two ways you could investigate this further: - try to do the network setup manually from one of the debug shells (on VT2 or VT3) I didn't manage to do that. Could you give me the command lines please? - use a packet sniffer like wireshark on a separate computer to see the actual network traffic between the system being installed and your router Sorry, I haven't had the time to try this option yet. Thanks for your time, -- Marc-Aurèle DARCHE Modèles économiques liés aux logiciels libres : http://www.aful.org/professionnels/modeles-economiques-logiciels-libres AFUL Association Francophone des Utilisateurs de Linux/Logiciels Libres French speaking Linux and Libre Software Users' Association -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511679: installation-guide-i386: Provide information on how to restore USB stick to its previous state
Package: installation-guide-i386 Version: Current version http://d-i.alioth.debian.org/manual/en.i386/ch04s03.html Severity: wishlist Hello I have installed Lenny Testing through a USB stick as described in http://d-i.alioth.debian.org/manual/en.i386/ch04s03.html It boots OK as it should etc. The problem now is that I cannot recover/restore my USB stick to its previous state. Before me installing the Debian installer on it, the USB capacity (size) was 2Gb and now when I open the USB device with either fdisk or cfdisk it only shows a 1Gb capacity. That's why I think that the Debian GNU/Linux Installation Guide should feature a small section on Howto restore the USB stick to its previous state. So that people like me are not left with a crippled USB mass storage afterward. Best and warm regards -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510176: installation-reports: No network through DHCP router speedtouch 530
Frans Pop a écrit : On Tuesday 06 January 2009, M.-A. DARCHE wrote: Could there be a problem in the way the ethernet card is labeled or tracked by the installer? If so, is there a way to make the dhcpdiscover try on all available interfaces instead of only the one detected/selected? I doubt that. And as we don't have any other reports of DHCP not working during installation, my bet is on a local network problem. OK. But strange because other Debian boxes can get leases from this DHCP router. There are two ways you could investigate this further: - try to do the network setup manually from one of the debug shells (on VT2 or VT3) - use a packet sniffer like wireshark on a separate computer to see the actual network traffic between the system being installed and your router I'll try both of those suggestions and will let you know. Thanks for your time -- Marc-Aurèle DARCHE Do not pay for software you don't want: http://www.racketware.info/ AFUL http://www.aful.org/ Association Francophone des Utilisateurs de Linux/Logiciels Libres French speaking Linux and Libre Software Users' Association -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510176: installation-reports: No network through DHCP router speedtouch 530
Frans Pop a écrit : On Tuesday 30 December 2008, M.-A. DARCHE wrote: Comments/Problems: The installation could not go on due to the fact that the DHCP server from the SpeedTouch 530 router modem was not found. No lease could be obtained from it. I have retried many times, even providing a machine name along. So no network, no time server found, no mirror available. It looks like the hardware-summary was made on the (already installed) Etch system. Is that correct? It is. You are right. I thought that using reportbug package might provide useful information. From the loaded modules in that summary, I see that you use PPPoE, but I see no sign of PPPoE support in the installation log. If you need PPPoE support, please try booting with the following boot parameter: modules=ppp-udeb I used to rely on PPPoE on the Etch system but from some weeks I am only using the router modem as a DHCP server on that Etch system. And this is like this that I was intending to install and use the new Lenny system. The modules=ppp-udeb boot parameter I know of as it is how I have installed the Etch system. The problem might be that the debian-installer gets confused by the fact that there are 2 network interfaces on this machine: a classical Ethernet card and a FireWire card (that I don't use). That's not it. From your syslog: Dec 30 01:10:39 kernel: [ 214.500529] forcedeth :00:08.0: ifname eth0, PHY OUI 0x5043 @ 1, addr 00:16:e6:86:b1:02 Dec 30 01:10:39 kernel: [ 214.500535] forcedeth :00:08.0: highdma csum vlan pwrctl mgmt timirq gbit lnktim msi desc-v3 Dec 30 01:10:39 net/hw-detect.hotplug: Detected hotpluggable network interface eth0 Dec 30 01:10:40 kernel: [ 215.252106] ieee1394: Host added: ID:BUS[0-00:1023] GUID[0016e65600b9dd23] Dec 30 01:10:42 hw-detect: insmod /lib/modules/2.6.26-1-486/kernel/drivers/ieee1394/sbp2.ko Dec 30 01:10:42 kernel: [ 217.008577] eth1394: eth1: IPv4 over IEEE 1394 (fw-host0) Dec 30 01:10:42 hw-detect: insmod /lib/modules/2.6.26-1-486/kernel/drivers/ieee1394/eth1394.ko Dec 30 01:10:42 net/hw-detect.hotplug: Detected hotpluggable network interface eth1 [...] Dec 30 01:10:53 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port67 interval 7 Dec 30 01:11:00 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 So, the forcedeth card is eth0 and the firewire one is eth1, and DHCP is trying correctly on eth0. I thought this might be the cause of the issue because on the Etch system the ethernet card is seen as eth1. Could there be a problem in the way the ethernet card is labeled or tracked by the installer? If so, is there a way to make the dhcpdiscover try on all available interfaces instead of only the one detected/selected? Best and warm regards, -- Marc-Aurèle DARCHE AFUL http://www.aful.org/ Association Francophone des Utilisateurs de Linux/Logiciels Libres French speaking Linux and Libre Software Users' Association signature.asc Description: OpenPGP digital signature
Bug#385768: installation-reports: Failed to reboot x86 SCSI system
Christian Perrier wrote : Then it doesn't even boot No idea...:) Hopefully other people will be more helpful. I have found the problem :-) This was my fault : bad configurations at the SCSI controller (wrong boot ID and no auto-spinning for the new boot device). I had neatly optimized my SCSI setting and forgot to fully adapt it for the new Debian Installer tests on the new disk. Sorry for the unjustified alert :-\ So the actual result of a new install after updated SCSI configuration is now : Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] Config network: [E] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] As for the network, I have simply installed pppoeconfig after the system rebooted and then I had a working connection to the Internet, just like with Sarge. I'll do some more tests regarding the Ethernet Speedtouch modem (using Mandriva + configuring the modem through HTTP) and I will then suggest an information text that I hope the DI team will find appropriate/legitimate enough to include somewhere to help the Ethernet Speedtouch users. Just to be sure : there isn't anymore second stage install (if I'm not mistaken about the second stage install term) now ? When the system reboots its now supposed to be operational ? I'm asking because if I remember well this was different with Sarge and I want to be sure that there isn't any step missing in what happened on my machine. Thanks, -- Marc-Aurèle DARCHE AFUL http://www.aful.org/ Association Francophone des Utilisateurs de Linux/Logiciels Libres French speaking Linux and Libre Software Users' Association
Bug#385768: installation-reports: Failed to reboot x86 SCSI system
Christian Perrier a écrit : This wasn't successful but I guess this is the old problem that we have with Alcatel Speedtouch DSL modems with (at least) the first Debian Installer on Debian Sarge. I might provide install reports dedicated to network configuration later when I manage to reboot the machine with Etch Debian Installer. Is this a USB DSL modem ? These things usually need some firmware crap to be loaded and the installer currently doesn't support this for them. IIRC, there's a dedicated package for these modems so that mostly means that you should install the stuff after the general system install. No this is not the USB DSL modem. This is the ethernet one. I realize I should have been more precise on this after sending my report, sorry. I already described the problem when testing Sarge installers : http://lists.debian.org/debian-boot/2004/10/msg00357.html and I guess the situation has not changed. According to what was said on debian-boot@lists.debian.org in 2004, the modem is faulty because it acts has a DHCP server, and is discover as such by the Debian Installer, while it doesn't provide a route to the outside. The modem is supposed to be configurable enough through its web interface, cf. http://forum.zebulon.fr/index.php?showtopic=88739 to be able to act as a true DHCP server. The main problem is that this is not the shipping default and thus joe users simply think that Debian cannot be installed on those ethernet modems. The other problem is that many users fear a bit to break the configuration of their modem. This is my case, I'm a bit reluctant to break my working connection :-\ But I will try to install another distribution such as Mandriva to test how well it performs with this modem very present in France. This might give us some hints. Anyway as I said in 2004, I think that a little text part should be added somewhere stating that the Alcatel Ethernet Speedtouch does not work out of the box with Etch. I suggested that it should be in the errata and it seems it was a wrong choice. So maybe the release notes would be a better place. 2. Reboot This is the blocker for this install. When the machine reboots, the system says that there isn't any SCSI bootable device. I provide below the grub-installer trace just in case, but it seems everything is fine from here. Moreover /dev/sdb1 is rightly marked as bootable in the partition table. I haven't any idea on what's wrong. I have kept the SCSI disk on which this install was done for any post-mortem examination. So if you need any logs, please just ask. What would help is as much as possible thigns from the boot messages. As I said : the system says that there isn't any SCSI bootable device. The reboot doesn't go further, nothing is loaded, no little trace of a first stage of GRUB or anything. So I guess that the MBR wasn't written, as simple as that. grep -i mbr /var/log/installer/* returns nothing in case of writing to the mbr should be mentioned in the installer logs. How could I check the content of the MBR of the disk ? What command should I run ? Is it possible ? I must say that I did the installation 5 times to be sure that I was concentrated enough and not trying to do something more advanced with the partitions like testing the LVM and encryption features :-) So this present report is truly about the simplest default install of Debian Etch that is :-) And I should also say that the machine on which I'm trying this Etch installer is a machine which has been successfully installed with different Debian stable releases over the years (and not simply APT updated). This is why I really think that there is a problem since the installers that come with Potato (floppies) and Sarge have managed to install Debian on it. Thanks Christian and thanks to all, -- Marc-Aurèle DARCHE AFUL http://www.aful.org/ Association Francophone des Utilisateurs de Linux/Logiciels Libres French speaking Linux and Libre Software Users' Association
Bug#385768: installation-reports: Failed to reboot x86 SCSI system
Package: installation-reports Version: etch_di_beta3/i386/iso-cd/debian-testing-i386-netinst.iso Severity: important Boot method: CD Image version: http://cdimage.debian.org/cdimage/etch_di_beta3/i386/iso-cd/debian-testing-i386-netinst.iso Date: 2006-09-03 Machine: PC i686 + SCSI (no IDE disks/CD drives) Processor: Pentium II (Klamath) Memory: 512Mb Partitions: Disk /dev/sdb: 36.7 GB, 36703934464 bytes 255 heads, 63 sectors/track, 4462 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdb1 * 1427734354971 83 Linux /dev/sdb242784462 1486012+ 5 Extended /dev/sdb542784462 1485981 82 Linux swap / Solaris Output of lspci and lspci -n: :00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 02) :00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 02) :00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02) :00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01) :00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) :00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02) :00:08.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895 (rev 01) :00:0b.0 Multimedia audio controller: Ensoniq ES1370 [AudioPCI] (rev 01) :00:0c.0 Ethernet controller: VIA Technologies, Inc. VT86C100A [Rhine] (rev 06) :01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G550 AGP (rev 01) :00:00.0 0600: 8086:7190 (rev 02) :00:01.0 0604: 8086:7191 (rev 02) :00:07.0 0601: 8086:7110 (rev 02) :00:07.1 0101: 8086:7111 (rev 01) :00:07.2 0c03: 8086:7112 (rev 01) :00:07.3 0680: 8086:7113 (rev 02) :00:08.0 0100: 1000:000c (rev 01) :00:0b.0 0401: 1274:5000 (rev 01) :00:0c.0 0200: 1106:3043 (rev 06) :01:00.0 0300: 102b:2527 (rev 01) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] Config network: [E] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [E] Comments/Problems: Base System Installation Checklist: First, the first Sarge Debian Installer runs fine on this machine both using Linux kernel 2.4 and 2.6. 1. Config network This wasn't successful but I guess this is the old problem that we have with Alcatel Speedtouch DSL modems with (at least) the first Debian Installer on Debian Sarge. I might provide install reports dedicated to network configuration later when I manage to reboot the machine with Etch Debian Installer. 2. Reboot This is the blocker for this install. When the machine reboots, the system says that there isn't any SCSI bootable device. I provide below the grub-installer trace just in case, but it seems everything is fine from here. Moreover /dev/sdb1 is rightly marked as bootable in the partition table. I haven't any idea on what's wrong. I have kept the SCSI disk on which this install was done for any post-mortem examination. So if you need any logs, please just ask. Sep 2 21:28:15 grub-installer: info: Installing grub on '(hd0)' Sep 2 21:28:16 grub-installer: info: grub-install supports --no-floppy Sep 2 21:28:16 grub-installer: info: Running chroot /target /sbin/grub-install --recheck --no-floppy (hd0) Sep 2 21:28:16 grub-installer: Probing devices to guess BIOS drives. This may take a long time. Sep 2 21:28:40 grub-installer: Installation finished. No error reported. Sep 2 21:28:40 grub-installer: This is the contents of the device map /boot/grub/device.map. Sep 2 21:28:40 grub-installer: Check if this is correct or not. If any of the lines is incorrect, Sep 2 21:28:40 grub-installer: fix it and re-run the script `grub-install'. Sep 2 21:28:40 grub-installer: Sep 2 21:28:40 grub-installer: (hd0)^I/dev/sda Sep 2 21:28:40 grub-installer: info: grub-install ran successfully Sep 2 21:28:40 grub-installer: Searching for GRUB installation directory ... Sep 2 21:28:40 grub-installer: found: /boot/grub Sep 2 21:28:41 grub-installer: Testing for an existing GRUB menu.list file ... Sep 2 21:28:41 grub-installer: Sep 2 21:28:41 grub-installer: Sep 2 21:28:41 grub-installer: Could not find /boot/grub/menu.lst file. Sep 2 21:28:41 grub-installer: Sep 2 21:28:41 grub-installer: Generating /boot/grub/menu.lst Sep 2 21:28:41 grub-installer: Searching for splash image ... Sep 2 21:28:41 grub-installer: none found, skipping ... Sep 2 21:28:41 grub-installer: Found kernel: /boot/vmlinuz-2.6.16-2-686 Sep 2 21:28:41 grub-installer: Updating /boot/grub/menu.lst ... Sep 2 21:28:41 grub-installer: done Sep 2 21:28:41 grub-installer: Thanks
Bug#368296: Answer to bug report
The upstream, the Nuxeo company, has no time to implement this functionality unless a client is ready to pay for it. However we find this request for master documents support legitimate and this would be a nice feature to have. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
