Incoming from Charles Muller: > Uwe Dippel wrote: > > (with 2.2.20 kernel: network connection functioning) > > debian:/home/chuck# ifconfig eth0 > eth0 Link encap:Ethernet HWaddr 00:90:F5:1F:3B:BA > inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0 ............^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:3 errors:0 dropped:0 overruns:0 frame:0 > TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:1240 (1.2 KiB) TX bytes:684 (684.0 b) > Interrupt:11 > > (under 2.4.18 kernel: no connection) > debian:/home/chuck# ifconfig eth0 > eth0 Link encap:Ethernet HWaddr 00:90:F5:1F:3B:BA > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > Interrupt:11 Base address:0x2000 .........................^^^^^^^^^^^^^^^^^^^
In case it wasn't obvious, that's the difference. I would think some combination of ifconfig, route, and supplying a base address for the IO port would fix it. -- Any technology distinguishable from magic is insufficiently advanced. (*) http://www.spots.ab.ca/~keeling - - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
