Package: debian-install
Version: netinstall sarge amd64
Severity: minor

In install-report.template there's a request to send an installation
report to [EMAIL PROTECTED] When I did, I got "Message with no
Package: tag cannot be processed."

These installation reports are surely valuable and I suggest you 
provide a working submission method in install-report.template.

I'm resubmitting as a bugreport, though this doesn't really seem appropriate.

INSTALL REPORT

Debian-installer-version: sarge-amd64-netinst.iso from 20-Feb-2005
uname -a: Linux 2.6.12-rc1 #1 Sat Apr 2 09:35:55 PST 2005 x86_64 GNU/Linux
Date: 1 April 2005
Method: I booted off the netinstall iso in a CD drive.
Machine: Gigabyte K8NS Ultra-939 with three SATA drives
Processor: AMD Athlon 64 3000+ 512K 90nm (939) CPU
Memory: DDR (400) 3200 - 1 GB (2 pcs 512) Corsair memory
Root Device: SATA Seagate 200GB hard drive, /dev/sda
Root Size/partition table:

Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda1               255912     97597    144662  41% /
tmpfs                   513564         0    513564   0% /dev/shm
/dev/sda9              2844332      1724   2698028   1% /home
/dev/sda8               369000      8241    341099   3% /tmp
/dev/sda5              4807056   1906236   2656636  42% /usr
/dev/sda6              2885780    474440   2264752  18% /var
/dev/sda10           178140168  12083100 157008060   8% /tv1
/dev/sdb1            195319464     23996 195295468   1% /tv2
/dev/sdc1            195263012       272 195262740   1% /tv3

Output of lspci
0000:00:00.0 Host bridge: nVidia Corporation: Unknown device 00e1 (rev a1)
0000:00:01.0 ISA bridge: nVidia Corporation: Unknown device 00e0 (rev a2)
0000:00:01.1 SMBus: nVidia Corporation: Unknown device 00e4 (rev a1)
0000:00:02.0 USB Controller: nVidia Corporation: Unknown device 00e7 
(rev a1)
0000:00:02.1 USB Controller: nVidia Corporation: Unknown device 00e7 
(rev a1)
0000:00:02.2 USB Controller: nVidia Corporation: Unknown device 00e8 
(rev a2)
0000:00:05.0 Bridge: nVidia Corporation: Unknown device 00df (rev a2)
0000:00:06.0 Multimedia audio controller: nVidia Corporation: Unknown 
device 00ea (rev a1)
0000:00:08.0 IDE interface: nVidia Corporation: Unknown device 00e5 (rev a2)
0000:00:0a.0 IDE interface: nVidia Corporation: Unknown device 00e3 (rev a2)
0000:00:0b.0 PCI bridge: nVidia Corporation: Unknown device 00e2 (rev a2)
0000:00:0e.0 PCI bridge: nVidia Corporation: Unknown device 00ed (rev a2)
0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge
0000:02:06.0 Multimedia video controller: Conexant Winfast TV2000 XP 
(rev 05)
0000:02:06.2 Multimedia controller: Conexant: Unknown device 8802 (rev 05)
0000:02:07.0 VGA compatible controller: nVidia Corporation NV4 [RIVA 
TNT] (rev 04)
0000:02:08.0 Multimedia video controller: Conexant Winfast TV2000 XP 
(rev 05)
0000:02:08.2 Multimedia controller: Conexant: Unknown device 8802 (rev 05)
0000:02:0a.0 Multimedia video controller: Conexant Winfast TV2000 XP 
(rev 05)
0000:02:0a.2 Multimedia controller: Conexant: Unknown device 8802 (rev 05)
0000:02:0b.0 Ethernet controller: Marvell Technology Group Ltd. Yukon 
Gigabit Ethernet 10/100/1000Base-T Adapter (rev 13)
0000:02:0d.0 Unknown mass storage controller: Silicon Image, Inc. 
(formerly CMD Technology Inc) SiI 3512 [SATALink/SATARaid] Serial ATA 
Controller (rev 01)
0000:02:0e.0 FireWire (IEEE 1394): Texas Instruments TSB82AA2 IEEE-1394b 
Link Layer Controller (rev 01)

The Multimedia controllers are three pcHDTV 3000 cards, with working 
drivers in the 2.6.12-rc1 kernel.

and lspci -n:
0000:00:00.0 0600: 10de:00e1 (rev a1)
0000:00:01.0 0601: 10de:00e0 (rev a2)
0000:00:01.1 0c05: 10de:00e4 (rev a1)
0000:00:02.0 0c03: 10de:00e7 (rev a1)
0000:00:02.1 0c03: 10de:00e7 (rev a1)
0000:00:02.2 0c03: 10de:00e8 (rev a2)
0000:00:05.0 0680: 10de:00df (rev a2)
0000:00:06.0 0401: 10de:00ea (rev a1)
0000:00:08.0 0101: 10de:00e5 (rev a2)
0000:00:0a.0 0101: 10de:00e3 (rev a2)
0000:00:0b.0 0604: 10de:00e2 (rev a2)
0000:00:0e.0 0604: 10de:00ed (rev a2)
0000:00:18.0 0600: 1022:1100
0000:00:18.1 0600: 1022:1101
0000:00:18.2 0600: 1022:1102
0000:00:18.3 0600: 1022:1103
0000:02:06.0 0400: 14f1:8800 (rev 05)
0000:02:06.2 0480: 14f1:8802 (rev 05)
0000:02:07.0 0300: 10de:0020 (rev 04)
0000:02:08.0 0400: 14f1:8800 (rev 05)
0000:02:08.2 0480: 14f1:8802 (rev 05)
0000:02:0a.0 0400: 14f1:8800 (rev 05)
0000:02:0a.2 0480: 14f1:8802 (rev 05)
0000:02:0b.0 0200: 11ab:4320 (rev 13)
0000:02:0d.0 0180: 1095:3512 (rev 01)
0000:02:0e.0 0c00: 104c:8025 (rev 01)

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:     [E]
Partition hard drives:  [O]
Create file systems:    [O]
Mount partitions:       [O]
Install base system:    [O]
Install boot loader:    [O]
Reboot:                 [O]

Comments/Problems:

The Gigabyte K8NS Ultra-939 board has two gigabyte NICs, the Marvell Yukon and 
a second
one, identified in the motherboard manual as a 100/10 ICS1883 LAN PHY, that is 
in fact
an nforce gigabyte controller, part of the nforce3 250 chipset (cf.
http://cogweb.net/owens/Images/Gigabyte-K8NS-Ultra-939.jpg line 5). It needs the
forcedeth driver, which D-I correctly loaded; however, this driver did not work 
during
my install. In fact loading this driver prevented the other NIC from working, 
so I was
stumped for hours, until I realized the sk98lin was the right driver, the NIC 
was
working, and I just had to unload forcedeth. I subsequently installed the 
2.6.12-rc1
kernel from kernel.org and the driver worked.

The Gigabyte K8NS Ultra-939 board also has two SATA chipsets, the sil 3512 and 
the
nforce3 250. The first was detected during install and the right sata_sil 
driver loaded;
this allowed the installation to go ahead, though I saw only one of three 
drives. After
booting, I realized there was a second chipset and loaded the sata_nv driver. 
Looking
over the /var/log/debian-installer logs, I see sata_nv was also detected, but 
somehow
those drives didn't show up. Not sure why.

<Description of the install, in prose, and any thoughts, comments
      and ideas you had during the initial install.>

I discovered you could use Ctrl-Alt-F1 etc to see in more detail what was going 
on
during the install; this was extremely helpful, and it might be worth dropping 
a hint
somewhere.

Overall, you've done really good work. It's still hard to get all the pieces in 
place.



-- System Information:
Debian Release: 3.1
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.12-rc1
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to