Re: forcedeth fails on second port with error -12
Greetings:
This board had a bad habit of leaving the second NICs MAC address all zeros. I don't know if this is the root cause of your problem or not, but since it mentions it in your dmesg it might be worth a look. There was a BIOS upgrade that fixed it. Both NICs are working properly on my machine.
-Scott
-------------- Original message ----------------------
From: Sebastian Haase <haase@msg.ucsf.edu>
> Hi,
> I have two on board ethernet on Tyan Thunder K8WE (s2895).
> It seems the forcedeth driver works fine.
> But only for eth0. Eth1 doesn't show up...
> I thought I might need to specifically reload the module a second time with
> different options for the second port (like in /etc/modutils or so) !?!?!????
>
> then I discovered an error message in dmesg:
> <cut and paste from dmesg>
> forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.48.
> ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LMAC] -> GSI 21 (level, high) ->
> IRQ 18
> PCI: Setting latency timer of device 0000:00:0a.0 to 64
> eth0: forcedeth.c: subsystem: 010f1:2895 bound to 0000:00:0a.0
> ACPI: PCI Interrupt Link [LNK3] enabled at IRQ 19
> GSI 19 sharing vector 0xC9 and IRQ 19
> ACPI: PCI Interrupt 0000:80:0a.0[A] -> Link [LNK3] -> GSI 19 (level, high) ->
> IRQ 19
> PCI: Setting latency timer of device 0000:80:0a.0 to 64
> 0000:80:0a.0: Invalid Mac address detected: 00:00:00:00:00:00
> Please complain to your hardware vendor. Switching to a random MAC.
> 0000:80:0a.0: open: Could not find a valid PHY.
> ACPI: PCI interrupt for device 0000:80:0a.0 disabled
> forcedeth: probe of 0000:80:0a.0 failed with error -12
> Probing IDE interface ide0...
> </cut and paste from dmesg>
>
> lspci shows that 0000:80:0a.0 should be my second NIC.
>
> Any idea what error -12 could mean ?
>
> Thanks,
> Sebastian Haase
>
>
> --
> To UNSUBSCRIBE, email to debian-amd64-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
Reply to: