Two other things that I noticed, which can be seen in the output data I posted in my prior message, but which I did not really stress:
1) a) When I do a search for 8139too, the actual module file, which is 8139too.o, was found in the directory for the 2.2 kernel. b) Since I selected the 8139 driver when I built the 2.4 kernel, we should also have a second 8139too.o somewhere in a 2.4 directory. c) But there isn't, which makes me think that perhaps it was never properly installed during the build. > debian:/home/chuck# locate 8139too > /lib/modules/2.2.20/net/8139too.o > /usr/src/linux-2.4.23/Documentation/networking/8139too.txt > /usr/src/linux-2.4.23/drivers/net/8139too.c > /usr/src/linux-2.4.23/include/config/8139too > /usr/src/linux-2.4.23/include/config/8139too.h > /usr/src/linux-2.4.23/include/config/8139too/8129.h > /usr/src/linux-2.4.23/include/config/8139too/pio.h > /usr/src/linux-2.4.23/include/config/8139too/tune > /usr/src/linux-2.4.23/include/config/8139too/tune/twister.h When, as Uwe suggests, I run modconf in 2.4, its default directory is > /lib/modules/2.4.23/kernel/drivers/net But if I copy the 8139too.o file from the 2.2 kernel to that directory and run modconf, it is rejected (as shown in verbose form in my prior message). I am not saying that S. Keeling's suggestion of supplying the proper address is not the solution, but even so, shouldn't I be showing another 8139too.o module, somewhere under a 2.4 directory? 2) When I run "lsmod" under 2.2, I get a list of modules, including 8139too. When I run "lsmod" under 2.4, I get nothing. Chuck ----------------------- Charles Muller Toyo Gakuen University <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
