Bug#512261: Bug 512261 Update - More Details
Package: installation-reports After reformatting the Linux partitions for a clean reinstallation from: lenny_di_rc1/amd64/iso-cd/debian-testing-amd64-netinst.iso from 05-Nov-2008 choosing Linux-image-2.26-AMD64 then, at the option to choose between the generic drivers and the targeted drivers, that choosing the targeted drivers caused the installation failure initially reported. When the generic drivers were installed, the installation completed OK. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#512261: Bug 512261 Update - Resolution
Package: installation-reports Installation was able to complete without errors when the following iso file was used. http://cdimage.debian.org/cdimage/lenny_di_rc1/amd64/iso- cd/debian-testing-amd64-netinst.iso 05-Nov-2008 The only inconvenience was that GRUB 2 did not automatically detect an MS-DOS partition. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511177: Bug 511177 Update 2 - Possible Resolution
Package: installation-reports The image file below may solve the reported problems. This was not tried because Etch installed successfully and an upgrade is possible from that. This image, however, is the one recommended when all others fail installation. The amd64 version of this image installed successfully on an Athlon 64 x2 machine on which the reported image failed. http://cdimage.debian.org/cdimage/lenny_di_rc1/i386/iso- cd/debian-testing-i386-netinst.iso 05-Nov-2008 -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511177: Bug 511177 Update 2 - Incorrect Partition Numbers Explained
Package: installation-reports Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily- builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso 07-Jan-2009 UPDATE 2: Partition Numbering Issue Explained In the initial report and the first update, I noted that during the installation process the partitioner had incorrectly reported the partition numbers. The cause of this has been discovered. The hard disk was originally partitioned with 2 primary partitions and 1 extended partition, like this: Primary #1 = partition 0 Primary #2 = partition 1 Primary #3 = partition 2 (extended partition) Then Primary #2 was resized (reduced) to make room for a Debian boot partition, which became: Primary #4 = partition 3 - even though it is physically before the extended partition. That is why the partitions appeared to be incorrectly numbered during the installation. I apologize if my report sent someone looking for a problem that did not exist. Thank you, again. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511177: Bug 511177 Update
Package: installation-reports Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily- builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso 07-Jan-2009 UPDATE: (i.e. what I forgot to report previously) 1. When attempting to install GRUB from the above Image Version (after the Linux-image failed to install), I noticed that GRUB only detected the Windows 98 partition but not the MS-DOS partition. GRUB with the Etch installer correctely identified both partitions. 2. After reporting this bug with the above Image Version, I realized that the installer was from 'sid'. So I downloaded the Lenny-Testing-i386-KDE weekly image of 05-Jan-2009 to try again. The exact same problems previously reported occurred with this CD image, as with all other Lenny installs previously attempted. 3. After several more attempts of installing Lenny, I reinstalled Etch r5 without any problems (other than the partitioner incorrectly identifying the partition numbers - as previously reported). For both Etch and Lenny installs, I've used the text-based 'expert' option. 4. Even though I have spent several days configuring Etch, I would still prefer to install Lenny - somehow - or upgrade from Etch to Lenny - somehow - to get the newer features. If installing Lenny means wiping out Etch to try any installer fixes that are made, I would be willing to do that. If no installer fixes are going to be attempted to address the issues I reported, I would appreciate knowing so that I can attempt an upgrade to Lenny. Thank you for your consideration. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511177: Lenny - Unable to install the selected kernel
Package: Install base system Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily- builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso 07-Jan-2009 Date: 07-Jan-2009 and approx. 15:00 EST USA Machine: Abit KT7A-RAID mobo Athlon 1.2GHz T-bird 512MB RAM VIA Apollo KT133A chipset HighPoint HPT370 RAID chipset ATi Radeon VE (7000) Generic 105 key PS/2 keyboard Logitech LX3 USB mouse connect through a PS/2 adapter Maxtor 20GB HD Teac CD burner Ethernet card Sound Blaster sound card 4 USB ports Hanns-G LCD monitor The parallel port and 1 serial port have been disabled. It is a very basic, no-frills system. Partitions: PRIMARY PARTITIONS: Partition 1: FAT 125MB MSDOS Partition 2: FAT32 1.47GB Windows 98 Partition 3: EXT3 203MB /boot EXTENDED PARTITION: Partition 4: FAT32 1.17GB Partition 5: FAT32 352MB Partition 6: FAT32 400MB Partition 7: FAT32 996MB Partition 8: FAT32 7MB Partition 9: FAT32 1.07GB Partition 10: FAT32 753MB Partition 11: FAT32 996MB Partition 12: EXT3 5.76GB /home Partition 13: EXT3 4.87GB /root Partition 14: Swap Area 996MB Output of lspci -knn (or lspci -nn): Don't know what this is and Debian will not install to get it. 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:[E] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [ ] Install boot loader:[E] Overall install:[ ] Comments/Problems: I've tried multiple times to install Lenny on my computer that ran Etch just fine. Each time I try to install Lenny (starting a year ago), during the install process the error Unable to install the selected kernel pops up during the Configuring linux-image-2.6.26-1-486 process. This also happens when I try installing linux-image-2.6- 486. These are the only two kernel images offered. Etch r2 to r5 always offered the 686 kernel. This Lenny installation CD does contain the 686 kernels but only offers the 486 kernels. In terminal 4, the log shows: mkinitramfs-kpkg failed to create initrd image Failed to create initrd image dpkg: error processing linux-image-2.6.26-1-486 (--nfigure) subprocess post-installtion script returned error xit status 9 E: Sub-process /usr/bin/dpkg returned error code 1 For my latest install attempt of Lenny, I selected None at the kernel prompt thinking I could install the correct kernel later. However, GRUB failed to install. I install GRUB in the /boot partition because I use another boot loader (System Commander) that resides in the MBR and detects GRUB in /boot. What I got from terminal 4 was: main-menu[1205]: (process:3101): sed: /target/etc/kernel-img.cf: No such file or directory. The other problem I found with both Etch r5 and Lenny installers is that they do not correctly identify the hard drive partition numbers during the Partition hard drives: phase beyond partitions 1 and 2. The partitioner sees partition 3 as #4, partition 4 as #5, partition 5 as #6 and so on. When I installed GRUB for Etch r5, I had to designate /dev/hde4 to install it into partition 3 (/boot), which should be /dev/hde3. Etch r2 showed the correct partition numbers. I'm fairly new to Debian and Linux in general. I'm glad to help make Debian better but I have not yet learned the fancy stuff, like checking MD5s, and have forgotten much of what I learned 7 months after I accidentally trashed my Etch install. As such, I kind of starting over. I know Etch installs and runs just fine but I don't know what else to offer to get Lenny to install cleanly. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
