Processed: Bug#331679: cdebconf-priority: Impossible to change prio from default to medium
Processing commands for cont...@bugs.debian.org: tag 331679 pending Bug#331679: cdebconf-priority: Impossible to change prio from default to medium There were no tags set. Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509857: installation-report for d-i rc1 on silicon graphics O2
Hi Frans, do you mean that I have to preseed the installation using option: d-i debian-installer/allow_unauthenticated Thanks, Giuseppe -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509857: installation-report for d-i rc1 on silicon graphics O2
On Saturday 27 December 2008, Giuseppe Sacco wrote: do you mean that I have to preseed the installation using option: d-i debian-installer/allow_unauthenticated Yes. Or set that at the boot prompt. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#416208: Installation report HP-715/64 (HIL)
Processing commands for cont...@bugs.debian.org: reassign 416208 rootskel Bug#416208: Installation report HP-715/64 (HIL) Bug reassigned from package `debian-installer' to `rootskel'. tags 416208 pending Bug#416208: Installation report HP-715/64 (HIL) There were no tags set. Tags added: pending thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509870: Install Report
Package: installation-reports Boot method: network Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso Date: 26/12/2008 22h41 Machine: HP550 Memory: 1Go Partitions: /dev/sda6 on / type ext3 (rw,errors=remount-ro) tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) procbususb on /proc/bus/usb type usbfs (rw) udev on /dev type tmpfs (rw,mode=0755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620) /dev/sda3 on /mnt/data type ext3 (rw) /dev/sda5 on /mnt/suse type ext3 (rw) Output of lspci -knn (or lspci -nn): lspci -knn 00:00.0 Host bridge [0600]: Intel Corporation Mobile GME965/GLE960 Memory Controller Hub [8086:2a10] (rev 0c) Kernel driver in use: agpgart-intel Kernel modules: intel-agp 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GME965/GLE960 Integrated Graphics Controller [8086:2a12] (rev 0c) 00:02.1 Display controller [0380]: Intel Corporation Mobile GME965/GLE960 Integrated Graphics Controller [8086:2a13] (rev 0c) 00:19.0 Ethernet controller [0200]: Intel Corporation 82562GT 10/100 Network Connection [8086:10c4] (rev 03) Kernel driver in use: e1000e Kernel modules: e1000e 00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 [8086:2834] (rev 03) Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:1a.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 [8086:283a] (rev 03) Kernel driver in use: ehci_hcd Kernel modules: ehci-hcd 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio Controller [8086:284b] (rev 03) Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel 00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 [8086:283f] (rev 03) Kernel driver in use: pcieport-driver Kernel modules: shpchp 00:1c.1 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 [8086:2841] (rev 03) Kernel driver in use: pcieport-driver Kernel modules: shpchp 00:1c.4 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 [8086:2847] (rev 03) Kernel driver in use: pcieport-driver Kernel modules: shpchp 00:1d.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 [8086:2830] (rev 03) Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:1d.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 [8086:2831] (rev 03) Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:1d.2 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 [8086:2832] (rev 03) Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:1d.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 [8086:2836] (rev 03) Kernel driver in use: ehci_hcd Kernel modules: ehci-hcd 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev f3) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller [8086:2815] (rev 03) Kernel modules: iTCO_wdt 00:1f.1 IDE interface [0101]: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller [8086:2850] (rev 03) Kernel driver in use: PIIX_IDE Kernel modules: ata_generic, piix, ide-pci-generic 00:1f.2 SATA controller [0106]: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller [8086:2829] (rev 03) Kernel driver in use: ahci Kernel modules: ahci 10:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection [8086:4229] (rev 61) Kernel driver in use: iwl4965 Kernel modules: iwl4965 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] iwl-4965-1.uucode 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: Install ok but i didn't manage to load microcode firmware for iwl-4965 (present on usb-key: iwl-4965-1.uucode, iwl-4965-1.uucode, firmware-iwlwifi_0_13_all.deb) then i do install on my wired network
Bug#509875: extended partition is too small when creating logical partition at end of volume
Package: partman-base This issue was encountered using a lenny i386 CD, the CD was downloaded/burnt around 2008-09-05 Consider the following volume: total capacity: 80GB Primary partitions: 128MB (/boot), 10GB (FAT32), 10GB (NTFS) The user now chooses to create another 10GB partition, and when prompted, chooses: - type: logical (not primary) - location: end (not beginning) The partitioner creates a 10GB extended partition at the end of the disk, and a 10GB logical partition within this space. The other 50GB, between the end of the third primary partition (NTFS) and the beginning of the logical partition is unusable. I believe the correct behaviour would be something like this: - warn the user in any situation where unusuable gaps will exist after partition and/or - ask the size and location questions twice: once for the extended partition, and again for the logical partition within the extended partition and/or - force the user to do things like this with cfdisk (bug 274290) and/or - automatically create an extended partition that uses all available space (although this is assuming that the user won't replace or resize the NTFS partition later) Workaround: - use gparted to resize the extended partition after installation of Debian, leaving the logical partition in the same place Related: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=274290 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=333086 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=386574 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi , guys , may I ask you a question ?
Hi, guys, Thank you for reading my letter, really. I am a great fan of debian, and love it very much. Howere now, I have a question with this debian-installer, that how can I install debian with it by using wireless? I can't find a option for this. I really need your answer, it's nice to write to your guys, thank you very much. Regards, Chandler -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Revisiting partman-nbd
Hi, Back in spring, I did some preliminary work on a 'partman-nbd', to support an installation to the Network Block Device. I didn't finish it then, for two reasons: - Just as I was working on it, a patch was submitted to the Linux kernel to make NBD support partition tables. At the time, I was working on figuring out how to make partman understand that an NBD device is this 'weird' thing that, like an LVM volume, can be formatted but not partitioned. Since that patch came up, I postponed the work on partman-nbd - I did not have proper support to actually boot off an NBD device yet, so I made sure to properly support that first. Now the NBD partitioning support has made it into 2.6.26, and the root-on-NBD stuff has been in lenny for quite a while; I just uploaded a package which also understands root-on-partitioned-NBD a few days ago. So today, I thought I'd revisit partman-nbd, and see what needs to be done to make it work. I'm still having some issues apparently, though, and I thought I'd toss them up here. I feel I should make clear that I'm not aiming for any of this to make it into the lenny installer -- squeeze is soon enough. But since I have some spare time now... Because of some implementational details[1], when you load the NBD module, the kernel will create device nodes for all the NBD devices that it supports. It /used/ to be the case that those devices would report a size equal to the maximum block device size as supported by the particular kernel you're running on, but this would confuse the LVM utilities such that it'd open the (unconnected) NBD device nodes, and try to read some data from them, resulting in read errors (since there's nothing to read). As such, the kernel was changed around the same time the partitioning support was added to report a size of 0 for unconnected NBD devices. Unfortunately, this now seems to confuse partman; we apparently can't be right for everyone. When loading the NBD kernel module before /lib/partman/init.d/30parted is run, we will get the following error message: Unable to determine geometry of file/device /dev/nbd0. You should not use Parted unless you REALLY know what you're doing! followed by Warning! and the options 'Ignore' or 'Cancel' for the user to choose; and this is repeated for each and every NBD device that is available. Unless kernel parameters are used to change the defaults, that means 16 of them. Obviously loading the NBD kernel module /after/ 30parted is run doesn't help -- the next time partman is restarted, we'll get those warnings anyway, because then some (though not all) NBD devices may have been connected, which will (obviously) prevent unloading the module... I tried creating a /lib/partman/init.d/24nbd-devices which would precreate the =dev=nbd0 etc directories in /var/lib/partman/devices; but it would appear that /l/p/i/30parted just ignores their existence, and tries (and fails) to open the device nodes anyway. When checking the code, I do see that partman does check for a few things, such as whether a particular device node is part of a multipath or SATA-RAID setup, and skips them in those cases. While I could of course suggest a change be made to partman so that similar checks would be performed for NBD, I can't help but think that it would be much more efficient if there were a way for a partman module to signal that a particular device node should be skipped; perhaps by creating the device directory and creating a file skip in that directory, or something similar. init.d/30parted could then contain a line like this: test -f /var/lib/partman/devices/$dirname/skip continue it could then be the responsibility of partman-dmraid, partman-nbd, and so on, to mark the devices that need to be skipped before 30partman is ran. Thoughts? [1] To connect an NBD device node, nbd-client must open() the device node, and then call some ioctl()s on it; there is no 'master' device node that is used to create others, or some such. So the device node needs to exist, even if it is not in use, since you cannot open() a device node that does not exist. -- Lo-lan-do Home is where you have to wash the dishes. -- #debian-devel, Freenode, 2004-09-22 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509921: installation-reports: No problems installing Lenny on HP Compaq nc8430
Package: installation-reports Severity: minor -- Package-specific info: Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/20081218-1/amd64/iso-cd/debian-testing-amd64-netinst.iso Date: 22.12.2008 Machine: HP Compaq nc8430 Partitions: /dev/mapper/vg0-root ext311534616 5640432 5308252 52% / tmpfstmpfs 1031724 8 1031716 1% /lib/init/rw udev tmpfs 10240 156 10084 2% /dev tmpfstmpfs 1031724 0 1031724 0% /dev/shm /dev/sda2 ext3 474472 29283420690 7% /boot /dev/mapper/vg0-home ext311534616 8614460 2802972 76% /home /dev/mapper/vg0-opt ext3 1919048282340 1597716 16% /opt /dev/mapper/vg0-vm ext323069156 10162412 12672372 45% /mnt/VM /dev/mapper/vg0-tmp ext3 281611 10380265415 4% /tmp /dev/mapper/vg0-vartmp ext3 91219 11378 77957 13% /var/tmp 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: No Problems during installation. WLAN, X. suspend to disc, suspend to RAM: everything worked perfectly after booting the new installation. Great work! Thanks Martin -- 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=5.0 (lenny) - installer build 20081217-22:56 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == umame -a: Linux compaq 2.6.26-1-amd64 #1 SMP Wed Nov 26 18:26:02 UTC 2008 x86_64 unknown lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03) lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express PCI Express Root Port [8086:27a1] (rev 03) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller [8086:27d8] (rev 01) lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 [8086:27d0] (rev 01) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 [8086:27d2] (rev 01) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 [8086:27d6] (rev 01) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 [8086:27c8] (rev 01) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1d.1 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 [8086:27c9] (rev 01) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1d.2 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 [8086:27ca] (rev 01) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1d.3 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 [8086:27cb] (rev 01) lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci-hcd lspci -knn: 00:1d.7 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller [8086:27cc] (rev 01) lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: Kernel modules: ehci-hcd lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev e1) lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge [8086:27b9] (rev 01) lspci -knn: 00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family) IDE Controller [8086:27df] (rev 01) lspci -knn: Kernel driver in use: PIIX_IDE lspci -knn: Kernel modules: piix lspci -knn: 00:1f.2 SATA controller [0106]: Intel
Installation manual: syslinux is no longer restricted to fat
Package : installation-reports Documentation: http://d-i.alioth.debian.org/manual/en.i386/ch04s03.html etc. Section 4.3: Preparing Files for USB Memory Stick Booting. This section is out of date in that it suggests that it is necessary to create a FAT16 partition on the USB stick in order to boot. This is a serious inconvenience and is no longer true since syslinux now supports ext2 in the shape of extlinux: http://syslinux.zytor.com/wiki/index.php/EXTLINUX Until grub2 is working reliably, syslinux/extlinux seems to be the only sensible way to boot on machines with only usb ports. So requiring a (probably temporary) fat partition on a usb stick is a major inconvenience, especially since large sticks on which it is possible to include several dvd iso images are now widely and cheaply available. Thus Section 4.3.2.1. Partitioning the USB stick needs rewriting. Perhaps it should start along the following lines: We will show how to set up the memory stick to use either an ext2 or a fat partition. Most usb sticks come pre-configured with a single fat32 or fat16 partition, often with a MBR (Master Boot Record) already set up in the first sector of the underlying device. If you want to keep the fat partition, perhaps so that the stick can be used on both linux and other operating systems, then you can use syslinux as described below. Otherwise, you might want at least one ext2 partition for the extra facilities it offers. In that case, you will use the syslinux variant called extlinux. (http://syslinux.zytor.com/wiki/index.php/EXTLINUX) If you decide to change the partitions on the usb stick, you can use fdisk, cfdisk, or sfdisk among others including tools that run on other operating systems. Just ensure you include at least one fat or at least one ext2 partition to hold the vmlinuz and initrd.gz installer files. If you have a new partition, next a filesystem of the right sort needs to be created. For a fat partition, use mkdosfs; for ext2, use mke2fs. If the partition is /dev/sdXn, then either # mkdosfs /dev/sdXn or # mke2fs /dev/sdXn In order to start the installer kernel after booting from the usb stick, we will put a boot loader on the stick. Although any boot loader (apart from grub which currently has problems with usb sticks) should work, it's convenient to use syslinux package, since it can use either fat or ext2 and can be reconfigured by just editing a text file. If you choose fat, most operating systems can be used to make changes to the configuration of the boot loader. Install the syslinux package (which includes extlinux) and, if you are using fat, also the mtools package. To install the boot loader, for fat, # syslinux /dev/sdXn Again, take care that you use the correct device name. For ext2, you mount the target filesystem first: # mount -t ext2 /dev/sdXn /mountpoint mountpoint above is an (normally empty) directory which you can create with the mkdir command if there is no existing mount point available. Then # extlinux /mountpoint We now have boot sector in the partition and either linux.sys or extlinux.sys which contain the boot loader code in the root of the target directory: both syslinux and extlinux can place them elsewhere, but we only cover the simplest case here. === 4.3.2.2. Adding the installer image The sentence: Next you should create a syslinux.cfg configuration file, which at a bare minimum should contain the following two lines: should become Next you should create a configuration file: either syslinux.cfg (fat) or extlinux.conf (ext2). At a bare minimum, it should contain the following two lines: A E Lawrence -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509938: installation-reports: Booting from USB stick not restricted to FAT
Subject: installation-reports: Booting from USB stick not restricted to FAT Package: installation-reports Severity: minor Tags: patch *** Please type your report below this line *** Documentation: http://d-i.alioth.debian.org/manual/en.i386/ch04s03.html etc. Section 4.3: Preparing Files for USB Memory Stick Booting. This section is out of date in that it suggests that it is necessary to create a FAT16 partition on the USB stick in order to boot. This is a serious inconvenience and is no longer true since syslinux now supports ext2 in the shape of extlinux: http://syslinux.zytor.com/wiki/index.php/EXTLINUX Until grub2 is working reliably, syslinux/extlinux seems to be the only sensible way to boot on machines with only usb ports. So requiring a (probably temporary) fat partition on a usb stick is a major inconvenience, especially since large sticks on which it is possible to include several dvd iso images are now widely and cheaply available. Thus Section 4.3.2.1. Partitioning the USB stick needs rewriting. Perhaps it should start along the following lines: We will show how to set up the memory stick to use either an ext2 or a fat partition. Most usb sticks come pre-configured with a single fat32 or fat16 partition, often with a MBR (Master Boot Record) already set up in the first sector of the underlying device. If you want to keep the fat partition, perhaps so that the stick can be used on both linux and other operating systems, then you can use syslinux as described below. Otherwise, you might want at least one ext2 partition for the extra facilities it offers. In that case, you will use the syslinux variant called extlinux. (http://syslinux.zytor.com/wiki/index.php/EXTLINUX) If you decide to change the partitions on the usb stick, you can use fdisk, cfdisk, or sfdisk among others including tools that run on other operating systems. Just ensure you include at least one fat or at least one ext2 partition to hold the vmlinuz and initrd.gz installer files. If you have a new partition, next a filesystem of the right sort needs to be created. For a fat partition, use mkdosfs; for ext2, use mke2fs. If the partition is /dev/sdXn, then either # mkdosfs /dev/sdXn or # mke2fs /dev/sdXn In order to start the installer kernel after booting from the usb stick, we will put a boot loader on the stick. Although any boot loader (apart from grub which currently has problems with usb sticks) should work, it's convenient to use syslinux package, since it can use either fat or ext2 and can be reconfigured by just editing a text file. If you choose fat, most operating systems can be used to make changes to the configuration of the boot loader. Install the syslinux package (which includes extlinux) and, if you are using fat, also the mtools package. To install the boot loader, for fat, # syslinux /dev/sdXn Again, take care that you use the correct device name. For ext2, you mount the target filesystem first: # mount -t ext2 /dev/sdXn /mountpoint mountpoint above is an (normally empty) directory which you can create with the mkdir command if there is no existing mount point available. Then # extlinux /mountpoint We now have boot sector in the partition and either linux.sys or extlinux.sys which contain the boot loader code in the root of the target directory: both syslinux and extlinux can place them elsewhere, but we only cover the simplest case here. === 4.3.2.2. Adding the installer image The sentence: Next you should create a syslinux.cfg configuration file, which at a bare minimum should contain the following two lines: should become Next you should create a configuration file: either syslinux.cfg (fat) or extlinux.conf (ext2). At a bare minimum, it should contain the following two lines: A E Lawrence -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (990, 'stable'), (500, 'proposed-updates') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.27.10 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509937: installation-reports: Booting from USB stick not restricted to FAT
Subject: installation-reports: Booting from USB stick not restricted to FAT Package: installation-reports Severity: minor Tags: patch *** Please type your report below this line *** Documentation: http://d-i.alioth.debian.org/manual/en.i386/ch04s03.html etc. Section 4.3: Preparing Files for USB Memory Stick Booting. This section is out of date in that it suggests that it is necessary to create a FAT16 partition on the USB stick in order to boot. This is a serious inconvenience and is no longer true since syslinux now supports ext2 in the shape of extlinux: http://syslinux.zytor.com/wiki/index.php/EXTLINUX Until grub2 is working reliably, syslinux/extlinux seems to be the only sensible way to boot on machines with only usb ports. So requiring a (probably temporary) fat partition on a usb stick is a major inconvenience, especially since large sticks on which it is possible to include several dvd iso images are now widely and cheaply available. Thus Section 4.3.2.1. Partitioning the USB stick needs rewriting. Perhaps it should start along the following lines: We will show how to set up the memory stick to use either an ext2 or a fat partition. Most usb sticks come pre-configured with a single fat32 or fat16 partition, often with a MBR (Master Boot Record) already set up in the first sector of the underlying device. If you want to keep the fat partition, perhaps so that the stick can be used on both linux and other operating systems, then you can use syslinux as described below. Otherwise, you might want at least one ext2 partition for the extra facilities it offers. In that case, you will use the syslinux variant called extlinux. (http://syslinux.zytor.com/wiki/index.php/EXTLINUX) If you decide to change the partitions on the usb stick, you can use fdisk, cfdisk, or sfdisk among others including tools that run on other operating systems. Just ensure you include at least one fat or at least one ext2 partition to hold the vmlinuz and initrd.gz installer files. If you have a new partition, next a filesystem of the right sort needs to be created. For a fat partition, use mkdosfs; for ext2, use mke2fs. If the partition is /dev/sdXn, then either # mkdosfs /dev/sdXn or # mke2fs /dev/sdXn In order to start the installer kernel after booting from the usb stick, we will put a boot loader on the stick. Although any boot loader (apart from grub which currently has problems with usb sticks) should work, it's convenient to use syslinux package, since it can use either fat or ext2 and can be reconfigured by just editing a text file. If you choose fat, most operating systems can be used to make changes to the configuration of the boot loader. Install the syslinux package (which includes extlinux) and, if you are using fat, also the mtools package. To install the boot loader, for fat, # syslinux /dev/sdXn Again, take care that you use the correct device name. For ext2, you mount the target filesystem first: # mount -t ext2 /dev/sdXn /mountpoint mountpoint above is an (normally empty) directory which you can create with the mkdir command if there is no existing mount point available. Then # extlinux /mountpoint We now have boot sector in the partition and either linux.sys or extlinux.sys which contain the boot loader code in the root of the target directory: both syslinux and extlinux can place them elsewhere, but we only cover the simplest case here. === 4.3.2.2. Adding the installer image The sentence: Next you should create a syslinux.cfg configuration file, which at a bare minimum should contain the following two lines: should become Next you should create a configuration file: either syslinux.cfg (fat) or extlinux.conf (ext2). At a bare minimum, it should contain the following two lines: A E Lawrence -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (990, 'stable'), (500, 'proposed-updates') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.27.10 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509765: installation-reports: NTFS is corrupted after resizing on ASUS Eee PC 1000H
Hi there! On Thu, 25 Dec 2008 22:55:31 +0100, Luca Capello wrote: X-Debbugs-Cc:ing the debian-eeepc-devel mailing list for obvious reasons. Please Cc: me in replies, I am not subscribed to the list. Still true (but obviously now with a cc:). Feel free to duplicate/rename/reassign this bug. Since I do not own this machine, I cannot do further tests, sorry. Due to unplanned circumstances, I still have the machine, so I performed more tests :-) NB, I reordered the quoting parts. 1) the NTFS XP partition is now corrupted and need chkdsk By default the Eee PC 1000H had Windows XP installed with two partitions: 85GB (the system one) and 65GB. I reduced the first one to 50GB through the d-i and it worked without any problem (at least d-i did not show me any error). [...] When I mount the same partition on Debian (stock NTFS support, no NTFS-3G yet), dmesg shows: NTFS volume version 3.1. NTFS-fs error (device sda1): load_system_files(): Volume is \ dirty. Mounting read-only. Run chkdsk and mount in Windows. I booted on a Windows XP Pro installation CD-Rom (external USB drive), chose the recovery option and then launched `chkdsk c:`. Then rebooted into Debian and indeed mount did not complain anymore: NTFS driver 2.1.29 [Flags: R/W MODULE]. NTFS volume version 3.1. Unfortunately, the GRUB error is still there: However, if I try to boot on XP through GRUB-Legacy I get the following error (translated from Italian): root (hd0,0) Filesystem type unknown, partition type 0x7 savedefault makeactive chainloader +1 Error reading from disk Press CTRL+ALT+DEL to reboot It seems the problem comes from Windows XP itself, but TestDisk [1] did not show any error WRT the NTFS Boot Sector. Also removing the boot flags from /dev/sda1 and /dev/sda3 or setting it to /dev/sda1 only did not solve the problem. Using XP's fixmbr resulted in an unbootable system: corrupted partition table, but d-i in rescue mode did not have any problem with it and `grub-install /dev/sda` fixed at least the boot. Microsoft `ofdisk /mbr` failed: obviously there is no more GRUB and thus directly the error message from XP. XP's fixboot failed as well: GRUB is still there, but I have now the correct English translation: A disk read error occurred Press Ctrl+Alt+Del to restart Searching for this error on Google revealed that it can be considered a common error caused by unknown factors and still unsolved. Since it is sometime a symptom of a broken hard disk, I tested the latter disk through the HITACHI Drive Fitness Test [2] (version 4.09 Build 00, Apr 10 2007, from Ultimate Boot CD 4.1.0 [3]): the hard disk is healthy, confirmed by smartd [4] after an extended self-test. I wanted to check a last time if the problem was the partition table, but Power Quest Partition Magic 8.0 failed to understand it. At this point, after two full days of tests, I decided to give up and start from scratch again: first, I wiped the partition table out with dd, then I created a big FAT32 partition with Microsoft ofdisk and formatted it with oformat. After having wiped the partition table out again with dd, I used the ASUS Recovery CD to re-install XP. This last step recreated two NTFS partitions (85GB and 70GB) and the EFI one (40MB), thus there is no more the hidden FAT32 used for recovery. Finally the fun began: booting the d-i, as the first time with the Debian Eee PC image. This time I chose to differently partition the hard disk (to be clear, all the steps were done from partman): --8---cut here---start-8--- Disk /dev/sda: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1364829302528+ 7 HPFS/NTFS /dev/sda23649 19452 1269456305 Extended /dev/sda3 19453 19457 40162+ ef EFI (FAT-12/16/32) /dev/sda53649972748829536 83 Linux /dev/sda69728 10092 2931831 82 Linux swap / Solaris /dev/sda7 10093 1945275184168+ 83 Linux --8---cut here---end---8--- The installation finished and now XP boots without any problem. I do not really know where the previous problem came from: however, since I do not have anymore that environment to further debug it, please feel free to close this bug. Thx, bye, Gismo / Luca Footnotes: [1] http://packages.debian.org/testdisk [2] http://www.hitachigst.com/hdd/support/download.htm [3] http://www.ultimatebootcd.com/ [4] http://packages.debian.org/smartmontools pgpJgUWDPcgEH.pgp Description: PGP signature
[D-I Manual] Build log for en (27 Dec 2008)
A build of the Debian Installer Manual was triggered by an update to SVN.
There were no errors during the build process.
The new version of the manual has been uploaded successfully.
A log of the build is available at:
- http://d-i.alioth.debian.org/manual/logs/en.log
===
It is possible to use RSS to track changes to the manual.
For more information, see:
http://d-i.alioth.debian.org/manual/translators.html
===
Note: PDF output is not yet supported for some languages; help
with this would be appreciated.
===
If you have any questions about the build or this message, feel
free to contact me at faw AT funlabs DOT org.
===
Updated files ('svn up')
Uen/appendix/preseed.xml
Updated to revision 56988.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#392042: software RAID volumes can not be partitioned
I just ran into this after, over a period of two days, trying to figure out why D-I / partman doesn't allow me to partition /dev/md0, and why it would not even recognize a manual partitioning created via `cfdisk`. I think it would be very useful if partman supported partitionable md devices. It would save you from having to configure, and in case of failure, rebuild, several individual (classic, non-partitionable) md arrays. (Also, using LVM on top of a single big md device as a substitute for partitioning isn't really an option because LVM doesn't support write barriers.) Let me know if I can help with this -- anything short of providing a patch, given that I have absolutely no clue of the partman internals. -Julian signature.asc Description: This is a digitally signed message part.
Bug#392042: software RAID volumes can not be partitioned
A thought: The patch from #303914 might have to be partially undone in order to (re)admit partitionable md devices. signature.asc Description: This is a digitally signed message part.
