Your message dated Wed, 7 Jun 2006 18:49:32 +0200 with message-id <200606071849.32674.elendil@planet.nl> and subject line Bug#371089: Installation report has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Installation report
- From: Bjarne Vestergaard <bjvest@tiscali.dk>
- Date: Wed, 7 Jun 2006 12:37:28 +0200
- Message-id: <[🔎] 200606071237.29631.bjvest@tiscali.dk>
Package: installation-reports Boot method: floppy Image version: June 1, 2006 Date: June 1, 2006 to June 7, 2006 Machine: Via chipset Processor: Intel 486 DX/4 Memory: 24 Mb Ram Partitions: Filesystem Type 1K-blocks Used Available Use% Mounted on /dev/hda1 reiserfs 483756 278744 205012 58% / tmpfs tmpfs 10796 0 10796 0% /dev/shm tmpfs tmpfs 10796 44 10752 1% /dev Output of lspci and lspci -n: 0000:00:00.0 Non-VGA unclassified device: VIA Technologies, Inc. VT82C505 0000:00:0a.0 VGA compatible controller: Avance Logic Inc. [ALI] ALG2301 0000:00:00.0 0000: 1106:0505 0000:00:0a.0 0300: 1005:2301 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: [O] 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: [E] Install boot loader: [E] Reboot: [E] Comments/Problems: Downloaded the "testing" floppy images from ftp.se.debian.org. Modified the syslinux.cfg on boot.img to contain the following two lines at the top: SERIAL 0 9600 0x3 CONSOLE 0 and added "console=ttyS0,9600n8" to each of the "append" lines. This made install via null-modem cable work. Succeeded to load modules to do an ReiserFS root file system. Failed to install kernel and boot loader (the installer said the step failed - no particular reason). Had to install kernel and boot loader manually from a command prompt (chose "Execute shell" from installer). Transcript of problems during the manual install: -------------- sh-3.1# dpkg -i /var/cache/apt/archives/linux-image-2.6.15-1-486_2.6.15-8_i386.d eb Selecting previously deselected package linux-image-2.6.15-1-486. (Reading database ... 7373 files and directories currently installed.) Unpacking linux-image-2.6.15-1-486 (from .../linux-image-2.6.15-1-486_2.6.15-8_i 386.deb) ... Could not find mkinitramfs-kpkg mkinitrd.yaird. at /var/lib/dpkg/tmp.ci/preinst line 236, <STDIN> line 9. Done. dpkg: dependency problems prevent configuration of linux-image-2.6.15-1-486: linux-image-2.6.15-1-486 depends on initramfs-tools | yaird | linux-initramfs-t ool; however: Package initramfs-tools is not installed. Package yaird is not installed. Package linux-initramfs-tool is not installed. Package initramfs-tools which provides linux-initramfs-tool is not installed. dpkg: error processing linux-image-2.6.15-1-486 (--install): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.15-1-486 sh-3.1# dpkg -i /var/cache/apt/archives/initramfs-tools_0.60_all.deb Selecting previously deselected package initramfs-tools. (Reading database ... 9388 files and directories currently installed.) Unpacking initramfs-tools (from .../initramfs-tools_0.60_all.deb) ... dpkg: dependency problems prevent configuration of initramfs-tools: initramfs-tools depends on udev (>= 0.076-5); however: Package udev is not installed. dpkg: error processing initramfs-tools (--install): dependency problems - leaving unconfigured Errors were encountered while processing: initramfs-tools sh-3.1# dpkg -i /var/cache/apt/archives/udev_0.091-2_i386.deb Selecting previously deselected package udev. dpkg: regarding .../archives/udev_0.091-2_i386.deb containing udev: udev conflicts with hotplug hotplug (version 0.0.20040329-25) is installed. dpkg: error processing /var/cache/apt/archives/udev_0.091-2_i386.deb (--install) : conflicting packages - not installing udev Errors were encountered while processing: /var/cache/apt/archives/udev_0.091-2_i386.deb sh-3.1# dpkg -r hotplug (Reading database ... 9448 files and directories currently installed.) Removing hotplug ... sh-3.1# dpkg -i /var/cache/apt/archives/udev_0.091-2_i386.deb (Reading database ... 9422 files and directories currently installed.) Unpacking udev (from .../archives/udev_0.091-2_i386.deb) ... ************************************************************** * Please purge the hotplug package! * (/etc/init.d/hotplug has been found on this system) ************************************************************** Setting up udev (0.091-2) ... A chroot environment has been detected, udev not started. sha1sum: /boot/initrd.img-2.6.15-1-486: No such file or directory /boot/initrd.img-2.6.15-1-486 has been altered. Cannot update. sh-3.1# dpkg --purge hotplug (Reading database ... 9516 files and directories currently installed.) Removing hotplug ... Purging configuration files for hotplug ... sh-3.1# dpkg -i /var/cache/apt/archives/udev_0.091-2_i386.deb (Reading database ... 9484 files and directories currently installed.) Preparing to replace udev 0.091-2 (using .../archives/udev_0.091-2_i386.deb) ... Unpacking replacement udev ... Setting up udev (0.091-2) ... A chroot environment has been detected, udev not started. ---------------------------------- Ran lilo before reboot. The reboot failed with a kernel panic as the default kernel did not have ReiserFS support built in. Had to manually add "initrd=/boot/initrd.img-2.6.15-1.486" to the lilo.conf file and run lilo again.
--- End Message ---
--- Begin Message ---
- To: Bjarne Vestergaard <bjvest@tiscali.dk>, 371089-done@bugs.debian.org
- Subject: Re: Bug#371089: Installation report
- From: Frans Pop <elendil@planet.nl>
- Date: Wed, 7 Jun 2006 18:49:32 +0200
- Message-id: <200606071849.32674.elendil@planet.nl>
- In-reply-to: <[🔎] 200606071237.29631.bjvest@tiscali.dk>
- References: <[🔎] 200606071237.29631.bjvest@tiscali.dk>
On Wednesday 07 June 2006 12:37, Bjarne Vestergaard wrote: > Comments/Problems: > Succeeded to load modules to do an ReiserFS root file system. Failed to > install kernel and boot loader (the installer said the step failed - no > particular reason). Had to install kernel and boot loader manually from > a command prompt (chose "Execute shell" from installer). Transcript of > problems during the manual install: This is because the installation floppies boot with a 2.4 kernel and you selected a 2.6 kernel for the installed system. That is not supported. Instead you should select a 2.4 kernel (during an install at default priority this will happen automatically) and upgrade to 2.6 after the reboot. We hope to change the floppies to use a 2.6 kernel before the release of Etch. Closing the report as this is basically a user error (although we should probably not allow you to select a 2.6 kernel, but that is a known issue). Cheers, FJPAttachment: pgpyCM835tiyJ.pgp
Description: PGP signature
--- End Message ---