Bug#253216: Sony VAIO install 2004-04-17
Package: installation-reports
INSTALL REPORT
Debian-installer-version: floppy images, 2004-06-07 from p.d.o/~joeyh
uname -a: Linux vindicate 2.4.26-1-686 #1 Sat May 1 18:04:05 EST 2004 i686 GNU/Linux
Date: June 6, 2004
Method: floppies (boot and root)
Machine: Sony Vaio PCG-V505DXP(UC)
Processor: Pentium-M 1.4GHz
Memory: 512MB
Root Device: IDE
Root Size/partition table:
/dev/hda3 on / type xfs (rw)
/dev/hda1 on /boot type ext3 (rw)
/dev/hda4 on /home type xfs (rw)
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 248 124960+ 83 Linux
/dev/hda2 115287 116280 500976 f W95 Ext'd (LBA)
/dev/hda3 249 58377 29297016 83 Linux
/dev/hda4 58378 115286 28682136 83 Linux
/dev/hda5 115287 116280 500944+ 82 Linux swap
Output of lspci and lspci -n:
0000:00:00.0 Host bridge: Intel Corp. 82855PM Processor to I/O Controller (rev 03)
0000:00:01.0 PCI bridge: Intel Corp. 82855PM Processor to AGP Controller (rev 03)
0000:00:1d.0 USB Controller: Intel Corp. 82801DB (ICH4) USB UHCI #1 (rev 03)
0000:00:1d.1 USB Controller: Intel Corp. 82801DB (ICH4) USB UHCI #2 (rev 03)
0000:00:1d.2 USB Controller: Intel Corp. 82801DB (ICH4) USB UHCI #3 (rev 03)
0000:00:1d.7 USB Controller: Intel Corp. 82801DB (ICH4) USB2 EHCI Controller (rev 03)
0000:00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI Bridge (rev 83)
0000:00:1f.0 ISA bridge: Intel Corp. 82801DBM LPC Interface Controller (rev 03)
0000:00:1f.1 IDE interface: Intel Corp. 82801DBM (ICH4) Ultra ATA Storage Controller (rev 03)
0000:00:1f.3 SMBus: Intel Corp. 82801DB/DBM (ICH4) SMBus Controller (rev 03)
0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801DB (ICH4) AC'97 Audio Controller (rev 03)
0000:00:1f.6 Modem: Intel Corp. 82801DB (ICH4) AC'97 Modem Controller (rev 03)
0000:01:00.0 VGA compatible controller: ATI Technologies Inc RV250 5c61 [Radeon Mobility 9200 M9+] (rev 01)
0000:02:05.0 CardBus bridge: Ricoh Co Ltd RL5c475 (rev b8)
0000:02:05.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C551 IEEE 1394 Controller
0000:02:08.0 Ethernet controller: Intel Corp. 82801BD PRO/100 VE (MOB) Ethernet Controller (rev 83)
0000:02:0b.0 Network controller: Intel Corp. PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04)
0000:00:00.0 Class 0600: 8086:3340 (rev 03)
0000:00:01.0 Class 0604: 8086:3341 (rev 03)
0000:00:1d.0 Class 0c03: 8086:24c2 (rev 03)
0000:00:1d.1 Class 0c03: 8086:24c4 (rev 03)
0000:00:1d.2 Class 0c03: 8086:24c7 (rev 03)
0000:00:1d.7 Class 0c03: 8086:24cd (rev 03)
0000:00:1e.0 Class 0604: 8086:2448 (rev 83)
0000:00:1f.0 Class 0601: 8086:24cc (rev 03)
0000:00:1f.1 Class 0101: 8086:24ca (rev 03)
0000:00:1f.3 Class 0c05: 8086:24c3 (rev 03)
0000:00:1f.5 Class 0401: 8086:24c5 (rev 03)
0000:00:1f.6 Class 0703: 8086:24c6 (rev 03)
0000:01:00.0 Class 0300: 1002:5c61 (rev 01)
0000:02:05.0 Class 0607: 1180:0475 (rev b8)
0000:02:05.1 Class 0c00: 1180:0551
0000:02:08.0 Class 0200: 8086:103d (rev 83)
0000:02:0b.0 Class 0280: 8086:1043 (rev 04)
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: [ ]
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: [O]
Comments/Problems:
o I used a USB floppy device to install the system. It worked, to my surprise.
However, when the prompt for the root floppy appeared, the LDM/SCSI code in
the kernel spewed some stuff about how /dev/sda had nothing useful on it.
This could confuse users.
o The partitioner asked me whether I wanted to partition my floppy drive
(/dev/sda). Bad idea...
o I wonder why, since we are moving to UTF-8, we don't set SCREEN_FONT by default
in /etc/console-tools/config to latarcyrheb-sun16 and the default locale to UTF-8
for American English installs? It's a good feature and if executed correctly it
is transparent to the user.
o I think the kernel install should make /vmlinuz and /initrd.img symlinks for the
running kernel so that one doesn't have to run update-grub every time. The kernel
build system is in charge of moving vmlinuz to vmlinuz.old on a new install, for
example.
Overall, pretty impressive...
--
Joshua Kwan
Reply to: