Package: installation-reports INSTALL REPORT
Debian-installer-version: Beta 4 uname -a: Linux worldmusic 2.6.3-1-386 #2 Tue Feb 24 20:20:23 EST 2004 i686 GNU/Linux Date: Mon, 24 May 2004 15:45:00 +0200 Method: expert26 at first, linux26 afterwards (see details) Machine: Fujitsu-Siemens Lifebook C1020 Processor: Pentium 4 M 2.2Ghz Memory: 512M Root Device: /dev/hda5 Root Size/partition table: Disk /dev/hda: 60.0 GB, 60011642880 bytes 16 heads, 63 sectors/track, 116280 cylinders Units = cylinders of 1008 * 512 = 516096 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 39 19624+ 83 Linux (/boot) /dev/hda2 40 1977 976752 82 Linux swap /dev/hda3 1978 79482 39062520 f W95 Ext'd (LBA) /dev/hda5 1978 79482 39062488+ 83 Linux (/) Output of lspci and lspci -n: 0000:00:00.0 Host bridge: VIA Technologies, Inc. P4M266 Host Bridge 0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] 0000:00:0a.0 CardBus bridge: O2 Micro, Inc. OZ6933 Cardbus Controller (rev 01) 0000:00:0a.1 CardBus bridge: O2 Micro, Inc. OZ6933 Cardbus Controller (rev 01) 0000:00:0c.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link) 0000:00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8233 PCI to ISA Bridge 0000:00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 0000:00:11.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 23) 0000:00:11.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 23) 0000:00:11.4 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 23) 0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 30) 0000:01:00.0 VGA compatible controller: S3 Inc. VT8375 [ProSavage8 KM266/KL266] 0000:00:00.0 Class 0600: 1106:3148 0000:00:01.0 Class 0604: 1106:b091 0000:00:0a.0 Class 0607: 1217:6933 (rev 01) 0000:00:0a.1 Class 0607: 1217:6933 (rev 01) 0000:00:0c.0 Class 0c00: 104c:8026 0000:00:0d.0 Class 0200: 10ec:8139 (rev 10) 0000:00:11.0 Class 0601: 1106:3074 0000:00:11.1 Class 0101: 1106:0571 (rev 06) 0000:00:11.2 Class 0c03: 1106:3038 (rev 23) 0000:00:11.3 Class 0c03: 1106:3038 (rev 23) 0000:00:11.4 Class 0c03: 1106:3038 (rev 23) 0000:00:11.5 Class 0401: 1106:3059 (rev 30) 0000:01:00.0 Class 0300: 5333:8d04 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: [O] Install boot loader: [O] Reboot: [E] Comments/Problems: I first booted the installer in the expert26 mode. This worked flawlessly, although I was annoyed by the fact that it gave me the "hardware detection" dialog three times, every time with all IDE drivers filled in. I know that my system has a Via 82xx IDE controller, so the first time and the second time, I disabled everything but that controller; but by the third time, I was bored. It would be nice if this could be changed a bit so that the system doesn't insist over and over again in loading modules I know I don't need, but if not; hell, this is expert mode after all. The reboot didn't work: my system thought the hard disk wasn't bootable. Since that hard disk had just been replaced because it couldn't be read from anymore, I first thought something was wrong with the IDE controller, too; however, after wiping the hard disk, I realized I had forgotten to mark one partition bootable. I redid the installation (not in expert mode this time), making sure there was exactly one partition marked bootable, and sure enough, it worked. Conclusion: my BIOS is smarter than what's good for it, and refuses to boot a hard disk if it does not see (at least|exactly) one partition marked as bootable. Although I went by it pretty fast and could have missed it, I don't remember having seen a warning message to tell me that this might occur with some BIOS implementations. It would be nice if such a warning would be given. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
