> Can you try something newer (eg 2.4.19-pre7)? There have been a number
> of changes to the pcnet32 driver, one of them (from Paul Mackerras)
> should fix your problem.
It fixes indeed the problem on the init of the card, but I have made a
deeper diagnosis of the problem and there are things left.
I have even got it to work with 2.4.18 without any patch. The problems
appear just when you do a netboot of the machine, if you just boot from the
disk 2.4.18 does ok. But if you boot from the net you get the problem with
detection on 2.4.18 which is solved on 2.4.19 pres, but also you get another
problem with the card, and it is that communication doesn't work like it
should, this problem is not corrected on 2.4.19preX as of pre7 at least.
This problems as I said before are caused when booting from the net and not
when the machine is booted from disk. It looks like the card is left on a
bad state by the openfirmware, in fact I've seen openfirmware fail several
times to retrieve big kernel files (more than 1 MB) and afterwards even fail
to do a bootp request, so I think that the card is left on a bad state that
drives as to things like this one:
A scp of a kernel to another machine connected to the same switched 10Mb LAN:
vmlinux-2.4.18 100% |*****************************| 2399 KB 05:10
RX packets:1619 errors:0 dropped:0 overruns:0 frame:0
TX packets:2831 errors:1417 dropped:0 overruns:0 carrier:1417
If I have time I'll test the driver that Tom Gall was sugesting me.
Thanks a lot!
-- Manty/BestiaTester -> http://manty.net - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/