On Tue, Oct 10, 2006 at 10:23:01AM +0200, Kv237 wrote: > Installation report > Installation image: > http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso > Download date 2006-10-10 > > Installation attempts: 5 > > Hardware > Motherboard: Asus K8N4-E Deluxe > Chipset: Nvidia nForce 4-4X > Built in ethernet controller: Marwell 88E81111 Gigabit Lan PHY > Additional ethernet controller: D-Link DFE 530 TX 10/100 ethernet > controller > CPU: AMD64 3200+ > Ram memory: 1024 MB > > Installation status: FAILED > > The installation attempts consistently failed in the installation step > "Identify network hardware", with the message "No ethernet card was > detected...". > In an attempt to resolve this, first the forcedeth driver was selected > manualy and then the via-rhine driver. In both cases the installation program > responded with the same message. This procedure was attempted on all five > installation attempts. The forcedeth was attempted since it is the recomended > driver for nForce mobos, and the via-rhine since it is the recommended driver > for the D-link card. > > During the installation attempts it was noted that the forcedeth driver was > named "forcedeth: nVidia nForce (2) 10/100 Ethernet adapter". A starting > point might therefore be to investigate if this is the latest version of > forcedeth. Another point to investigate is possibly an incompatibility > between the netinst software and the chipset. > > The formal language is deliberately chosen in an attempt to create a concise > and complete report. > > With my best regards, > > S?ren Jonsson, MSc Computer Science
You could try a BIOS upgrade if you haven't already made sure it is up to date. Apparently a lot of nvidia boards have some bios mistakes when setting up the ethernet (such as getting the MAC address backwards) which can confuse the driver. Does ifconfig -a from console 2 show eth0 and eth1 as present? Maybe it is dhcp that is failing instead. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
