tulip.o in 2.4.1 insists on selecting 10baseT, no command
line option can convince it otherwise. tulip.o in 2.2.16 auto
detected media and worked fine.
de4x5.o in 2.4.1 needs to be told the media, then works fine.
de4x5.o in 2.2.16 auto detected media and worked fine.
3c509.0 in 2.4.1 insists on AUI media when cold-booted (power off,
then on), no command line option can convince it otherwise. First
cold-booting into kernel 2.2.16 and then warm-booting into 2.4.1
works; it will then use the config stored in EEPROM. Same if I
cold-boot into DOS, run the 3c509 config utility and then warm-boot
into 2.4.1. This makes it impossible for the system to reboot with
kernel 2.4.1 after power failure.
That 3 (three!) ethernet drivers which worked flawlessly in 2.2.16
misbehave in 2.4.1 to varying degrees seems to me to indicate that
there might be some underlying problem affecting all those drivers.
Any thoughts or suggestions?
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/