Bug#653259: /etc/default/busybox-syslogd: also not documented
As above, /etc/default/busybox-syslogd is also not documented. I had to read /etc/init.d/busybox-syslogd to discover that /etc/default/syslogd was the wrong file. In passing, busybox-syslogd fails to install if sysklogd has not been purged. ael -- 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/20121211224204.GA6286@elf.conquest
Bug#575806: console-setup-mini does not change fonts: had to install console-setup instead
Package: console-setup-mini Version: 1.51 Severity: important With /etc/default/console-setup containing FONTFACE=Fixed FONTSIZE=14 for example, setupcon does not change the font. Similarly dpkg-reconfigure console-setup-mini does nothing. Installing console-setup instead of the mini version, all these things work. So the mini version is broken? ael --- -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.33 (PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages console-setup-mini depends on: ii debconf [debconf-2.0] 1.5.28 Debian configuration management sy ii keyboard-configuration1.51 system-wide keyboard preferences Versions of packages console-setup-mini recommends: ii kbd 1.15.1-2 Linux console font and keytable ut Versions of packages console-setup-mini suggests: ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip -- 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/20100329121209.4048.10033.report...@conquest3.conquest
Bug#565511: installation-reports: Failure with ext4 on Acer Aspire One
Package: installation-reports Severity: normal SSD was Super Talent FEM32GF13M 32G SSD rather than the Acer supplied 8 GB version. I selected ext4 to format the SSD. The installer choose a swap partition of around 1 GB. Could not get past the format/partition stage: the installer kept saying that it could not mount swap. After many loops, I went alt-2 terminal and tried mkswap etc manually. mkswp /dev/sda5 gave no such file or directory. fdisk on /dev/sda showed sda5, *but* it was not present in /proc/partitions. Eventually I manually repartitioned via fdisk and created a swap partition as sda2. mkswap then worked. Installer then stopped complaining about the swap but then looped because it could not mount root, the ext4 sda1 partition. Eventually discovered error messages (on alt-4?) showing things like bad geometry,.. block count 7634836 exceeds size of device... I tried ext3 instead manually: mke2fs gave a warning 295 blocks unused Gave up and re-installed this time using ext3 for root=sda1. I kept my previous swap built manually. ? Perhaps this is simply an ext4 bug? But maybe there is something odd about the Super Talent SSD which is new to the market. I doubt many are installed since this is specific to Acer Aspire One netbook, and requires a good deal of hardware knowledge and hacking to install. -- Package-specific info: Boot method: usbstick Image version: daily squeeze hd-image 13/1/10 Date: Date and time of the install Machine: Acer Aspire One with SuperSSD Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: After changing to ext3 ... [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [0] Detect network card:[0] wired ok, wifi missed Configure network: [0] Detect CD: [ ] not relevant, no cd Load installer modules: [0] Detect hard drives: [0] Partition hard drives: [E] as above ext4 broken. ext3 maybe ok Install base system:[0] Clock/timezone setup: [0] User/password setup:[0] Install tasks: [0] Install boot loader:[0] Overall install:[0] Comments/Problems: Trackpad not found, so not functional. wiki.debian.org/DebianAcerOne says that the gsynaptics package is needed. Although maybe my text selection stopped that loading? Even with just text and laptop, seemed to be a bit bloated for a netbook. Would like the graphical install to offer choice including xfce, etc for lightweight installs. Removing all the redundant cruft after initial installation takes *so* long. I am filing this report before any serious customization or investigation while it is fresh in my mind. Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- 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 20100113-16:54 X_INSTALLATION_MEDIUM=hd-media == Installer hardware-summary: == uname -a: Linux elf 2.6.30-2-486 #1 Sat Sep 26 00:03:46 UTC 2009 i686 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GME Express Memory Controller Hub [8086:27ac] (rev 03) lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:015b] lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03) lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:015b] lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03) lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:015b] lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller [8086:27d8] (rev 02) lspci -knn: Subsystem: Acer Incorporated [ALI] Device [1025:015b] lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 [8086:27d0] (rev 02) 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 02) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 [8086:27d4] (rev 02) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 82801G (ICH7
Bug#565511: ext4.ko module missing from initramfs
On further investigation, I find that /lib/modules/2.6.30-2-686/kernel/fs/ext4/ext4.ko is missing from the initramfs. I assume that this explains the failure. I do now seem to remember choosing a slim initrd during installation. Going into rescue mode, I could not find any way to revert to a full initrd. I could not see any bug about this against linux-image-2.6.30-2-686. I assume it generates initrd? But then I don't know how the installer can select a slim version. During my investigation, I noticed that the grub2 entry started with an insmod ext2 which seemed a little odd on an ext3/4 system. So it seems that while the installer supports ext4, the installed target system initrd does not. So I guess that I will have to compile my own kernel on the target and then change to ext4 via the rescue mode (it's the root partition) later. ael -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546983: uk keymap also fails
Package: console-setup-mini Version: 1.45 Severity: normal Same problem here. US keymap on all consoles as well as X. I have to loadkeys uk to get proper map. This happens on two squeeze boxes (another is ok?). Problem on both an i386 as well as this amd64 box. In passing, on the i386 box, Numlock stays on and requires two attempts to clear it. Might be related, but probably needs more info to debug. Although this report was generated when running stock git kernel, happens also with debian kernel. - -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-rc3_c2 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages console-setup-mini depends on: ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy Versions of packages console-setup-mini recommends: ii kbd 1.15-4 Linux console font and keytable ut Versions of packages console-setup-mini suggests: ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip -- debconf information: * console-setup/variant: United Kingdom console-setup/unsupported_options: true * console-setup/ctrl_alt_bksp: true console-setup/modelcode: pc105 console-setup/use_system_font: console-setup/fontsize: console-setup/unsupported_layout: true console-setup/layoutcode: gb console-setup/codesetcode: Lat15 * console-setup/altgr: The default for the keyboard layout * console-setup/codeset: # Latin1 and Latin5 - western Europe and Turkic languages console-setup/toggle: No toggling * console-setup/fontface: Do not change the boot/kernel font console-setup/fontsize-text: 16 * console-setup/compose: No compose key debian-installer/console-setup-udeb/title: console-setup/other: console-setup/switch: No temporary switch console-setup/unsupported_config_layout: true * console-setup/charmap: UTF-8 console-setup/optionscode: terminate:ctrl_alt_bksp console-setup/unsupported_config_options: true console-setup/layout: console-setup/variantcode: * console-setup/model: console-setup/fontsize-fb: 16 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510015: Problem is missing ext2 module
I had noticed that only the ext3 module was in the hd-media/initrd, but had assumed that could load ext2 filesystems as well as ext3. It looks as if I was wrong. If I install ext2 into /lib/modules/..., from a vfat filesystem, depmod and modprobe ext2, the iso files are then successfully found. The module installation from an alternative console, of course. Thus this bug report should now be against whichever module is responsible for building initrd. And the level of the report should probably move up to critical? Comments: 1) I thought ext2 could mount an ext3 file (as ext2), so if lack of space was the motive for excluding ext2, that seems an odd choice. But I might be wrong about ext2. 2) ext2 is most definitely needed: journalling filesystems on flash media which has a limited erase cycle life have to be avoided. 3) If there is a some overriding reason to include ext3 which precludes ext2, then there needs to be an alternative initrd. Note that many netbooks can only be booted from usbsticks (unless there happens to be an external usb hard drive to hand which is seldom the case). Bug 509938 expands on that in the form of a suggested patch to the installation manual. ael -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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
