Hi, I mentioned in a former post that ifup would make the kernel oops when trying to bring the eepro100 up.
I booted fine with 2.4.14 , network starting scripts disabled. Here is dmesg output: >eepro100.c:v1.09j-t 9/29/99 Donald Becker >http://cesdis.gsfc.nasa.gov/linux/driv >ers/eepro100.html >eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin ><[EMAIL PROTECTED] >w.sw.com.sg> and others >eth0: Intel Corp. 82557 [Ethernet Pro 100], 00:D0:B7:F9:FC:70, IRQ 55. I have a segfault when i try to manually bring eth0 up when i use gdb to run the program (though there are no debug symbols): >Starting program: /sbin/ifconfig "eth0 10.0.0.206 up" >eth0 10.0.0.: error fetching interface information: Device not found >(no debugging symbols found)...(no debugging symbols found)... >Program exited with code 01. Is there a known issue with eepro100 on 2.4.14 ? I haven't seen any post on this topic though. No eepro100 problems with 2.4.9 yet. Thanks, Philippe. PS: System is a Dell 7150 4x800MHz , 4Go RAM + Debian Unstable. BIOS is A01 CPU Revision 6
