Bug#500516: Lenny distro of Linux magazine september 2008
Package: installation-reports
Boot method: <How did you boot the installer? CD? floppy? network?>
Image version: <Full URL to image you downloaded is best>
Date: <Date and time of the install>
Machine: <Description of machine (eg, IBM Thinkpad R32)>
Processor:
Memory:
Partitions: <df -Tl will do; the raw partition table is preferred>
Output of lspci -knn (or lspci -nn):
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [E ]
Detect network card: [OK ]
Configure network: [OK ]
Detect CD: [OK ]
Load installer modules: [OK ]
Detect hard drives: [OK ]
Partition hard drives: [OK ]
Install base system: [OK ]
Clock/timezone setup: [OK ]
User/password setup: [OK ]
Install tasks: [OK ]
Install boot loader: [E ]
Overall install: [E ]
Comments/Problems:
Problem 1:
GRUB 2.0 wasn't properly configured : the correct boot drive wasn't correct
calculated. When it wasn't HD0 it was wrong and this with many different
installations. When correcting the map with the drives Lenny booted up
correctly.
The devicemap was wrong and did not contained all drives and in wrong order.
1 tested system was with SCSI card + IDE drives
1 tested system with SATA drive and IDE DVD/CDROM
1 other system with mixed sata, scsi and ide drives
On all systems the debian wasn't installed on the first drive but on the last
drive.
PROBLEM 2:
But then had problems with the X-window system to obtain the correct vertical
refresh rate. It seems the values of the monitor weren't correctly taken. it
rendered an useless screen.
When manually the correct refresh value and monitor values were introduced it
booted perfect in KDE/GNOME.
This DVD on contained errors who were also present on previous releases of
GRUB. I do not understand why this hasn't been corrected/investigated. This
ruins existing Microsoft or Linux installations on the same computer. They
wouldn't even startup anymore due to the fact that their bootrecord was
overwritten. (HD(0,0)) although another section was selected to write the
bootrecord too. (HD3,0) or (HD3,2).
Only on the hd(0,0) was installation in booting succesfull.
mvg,
Patrick Op de Beeck
Drabstraat 40
B-2640 Mortsel
Europe
Reply to: