Bug#267402: Install Report (Sony Vaio PCG-F590 + USB Ethernet)
Package: installation-reports
INSTALL REPORT
Debian-installer-version: rc1
uname -a: Linux andrewpollock 2.4.26-1-386 #1 Thu Jul 22 12:46:23 JST 2004 i686 GNU/Linux
Date: Sun Aug 22 21:36:07 EST 2004
Method: netinst CD, installed from ftp.au.debian.org via transparently proxied HTTP
Machine: Sony Vaio PCG-F590
Processor: Pentium III
Memory: 256M
Root Device: IDE, /dev/hda
Root Size/partition table:
Disk /dev/hda: 20.0 GB, 20003880960 bytes
255 heads, 63 sectors/track, 2432 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 1337 10739421 7 HPFS/NTFS
/dev/hda2 * 1338 2383 8401995 83 Linux
/dev/hda3 2384 2432 393592+ f W95 Ext'd (LBA)
/dev/hda5 2384 2432 393561 82 Linux swap
Filesystem Type 1K-blocks Used Available Use% Mounted on
/dev/hda2 ext3 8270100 230476 7619528 3% /
tmpfs tmpfs 128512 0 128512 0% /dev/shm
Output of lspci and lspci -n:
0000:00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
0000:00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
0000:00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
0000:00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
0000:00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
0000:00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 03)
0000:00:08.0 FireWire (IEEE 1394): Sony Corporation CXD3222 i.LINK Controller (rev 02)
0000:00:09.0 Multimedia audio controller: Yamaha Corporation YMF-744B [DS-1S Audio Controller] (rev 02)
0000:00:0a.0 Communication controller: Conexant HSF 56k Data/Fax Modem (Mob WorldW SmartDAA) (rev 01)
0000:00:0c.0 CardBus bridge: Ricoh Co Ltd RL5c478 (rev 80)
0000:00:0c.1 CardBus bridge: Ricoh Co Ltd RL5c478 (rev 80)
0000:01:00.0 VGA compatible controller: Neomagic Corporation NM2380 [MagicMedia 256XL+] (rev 10)
0000:00:00.0 0600: 8086:7190 (rev 03)
0000:00:01.0 0604: 8086:7191 (rev 03)
0000:00:07.0 0601: 8086:7110 (rev 02)
0000:00:07.1 0101: 8086:7111 (rev 01)
0000:00:07.2 0c03: 8086:7112 (rev 01)
0000:00:07.3 0680: 8086:7113 (rev 03)
0000:00:08.0 0c00: 104d:8039 (rev 02)
0000:00:09.0 0401: 1073:0010 (rev 02)
0000:00:0a.0 0780: 14f1:2443 (rev 01)
0000:00:0c.0 0607: 1180:0478 (rev 80)
0000:00:0c.1 0607: 1180:0478 (rev 80)
0000:01:00.0 0300: 10c8:0016 (rev 10)
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot worked: [O]
Configure network HW: [E]
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: [O]
Comments/Problems:
The PCG-F590 does not have an onboard Ethernet adapter. When I have to plug
into a wired network, I use a USB-Ethernet adapter. I have a few, the one I
used for this install was an SMC adapter, here's the lsusb output:
Bus 001 Device 001: ID 0000:0000
Bus 001 Device 002: ID 0707:0201 Standard Microsystems Corp.
(lsusb -v output can be supplied if desired, but it's really verbose).
So when it came to detecting the network hardware, I was presented with a
list of adapters. I switched to the second virtual terminal and modprobed
the pegasus module, and switched back to the first virtual terminal, and
selected "none of the above", and opted not to load a module from a driver
disk. I then got a red screen saying that no network device had been
detected.
Upon acknowledging this error message, I was told that the installer was
trying to configure the network using DHCP, which was successful, and the
install continued as normal.
I've already filed a wishlist bug (#262638) against ethdetect with a
better-than-nothing way of avoiding having to manually modprobe the pegasus
driver. I think the pegasus chipset is the most common USB-Ethernet adapter
chipset, so this is going support the majority of USB-Ethernet adapters out
there.
Oh, and I was asked about a HTTP proxy twice, once when the normal APT
source lines were updated, and once before the security APT source was
updated.
Reply to: