Re: forcedeth as a module only?

[Christian Kujau]

Christian Kujau schrieb:
> Manfred Spraul schrieb:
>>
>>Could you try the attached patch? It polls for link changes instead of
>>relying on the irq. Additionally, I have enabled some debug output.

oh jolly, i think it worked!

eth0: forcedeth.c: subsystem: 01462:0250 bound to 0000:00:05.0
netconsole: device eth0 not up yet, forcing it
eth0: no link detected by phy - falling back to 10HD.
eth0: no link during initialization.
eth0: nv_update_linkspeed: PHY advertises 0x0de1, lpa 0x41e1.
eth0: changing link setting from 66536/0 to 65636/1.
eth0: link up.
netconsole: network logging started
[...]
eth0: nv_update_linkspeed: PHY advertises 0x0de1, lpa 0x41e1.
...

the last line gets repeated a couple of times, that must be the printk you
enabled.

thank you!
Christian.

(it's always stunning how a bugreport with that sparse details can lead to
a working kernel patch. cool.)
-- 
BOFH excuse #303:

fractal radiation jamming the backbone
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/