Installation on Asus K8N4-E Deluxe still fails

[Kv237]

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

Sweden

[HXC]

Post by Kv237
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
Sweden

I am afraid the nforce chip is causing these troubles, I have exactly
the same ethernet controller working without problems on my asus A8v
-deluxe with via chipset. Did you try kanotix?

[Lennart Sorensen]

Post by HXC
I am afraid the nforce chip is causing these troubles, I have exactly
the same ethernet controller working without problems on my asus A8v
-deluxe with via chipset. Did you try kanotix?

An A8V does not have the same ethernet. It has a marvell yukon (at
least mine does). The model of the phy is completely non interesting
unless you are doing low level weird stuff in the driver. It is the
model of the MAC that is interesting. That is what the driver actually
talks to. On the A8V that is a marvell, on the K8N it would be the
nvidia (forcedeth) MAC.

--
Len Sorensen

[Lennart Sorensen]

Post by Kv237
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

[Kv237]

References: <***@csclub.uwaterloo.ca>

Sorry for the prevous message. I'm using /bin/mail on the local server, and
has to add all headers manually.

The bios is the 1010.bin bios from the Asus website. Using eSupport.com BIOS agent it is reported as:

Bios Type: Phoenix - AwardBIOS v6.00PG
BIOS ID: 10/21/2005-NF-CK804-K8N4E
OEM Sign-On: Asus K8N4-E Deluxe ACPI BIOS Revision 1010
Chipset: AMD 1100 rev 0
Superio: ITE 8712F rev 7 found at port 2Eh
CPU: AMD Athlon(tm) 64 Processor 3200+ 2200 MHz MAX: 3700 MHz
BIOS ROM In Socket : YES
BIOS ROM Size: 512K
Memory installed: 1024 MB
Memory Maximum: 3072 MB
Memory Slot 01: 512 MB
Memory Slot 02: 512 MB
Memory Slot 03: 0 MB
ACPI Revision: 1.0

(Some irrelevant information was deleted from the report)

The report from "ifconfig -a" is as follows:
lo Link encap: local loopback
LOOPBACK MTU: 16436 Metric:1
RX packets: 0 errors:0 dropped:0 overruns:0 frame:0
TX packets: 0 errors:0 dropped:0 overruns:0 carrier: 0
collisions:0 txquelen: 0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

And that is all from ifconfig.

I am also using a static IP adress, so DHCP is not a relevant issue.

Best regards,

Sören Jonsson

[Gabor Gombas]

[...]

Look at the kernel messages when the forcedeth module is inserted.
Google finds reports that on this motherboard forcedeth fails to find
the IOMEM region of the NIC (you should look for a message saying
"forcedeth: Couldn't find register window for device eth0"). If that's
the case, you should file a bug report against the kernel, preferably
with the output of "lspci -vvv" attached.

Gabor

[Kv237]

References: <***@boogie.lpds.sztaki.hu>

I could indeed find the line "forcedeth: Couldn't find register window..."
using grep forcedeth /var/log/syslogs.

I will file a bug report against the kernel, but it has to wait until the
weekend. I have to find a way to extract the output from lspci -vvv from the
computer without using pen and paper.

I can probably sort this out on my own, but I need a few uninterupted hours
in order to do this.

Thank you all for your help.

Best regards,

Sören Jonsson