Bernd Eckenfels wrote: > > In article <3D5140D0.813D27A9@cri74.org> you wrote: > > Almost everything works fine with a 2.4.18 kernel > > There are some little problems about media status that can "setfault" > > ifconfig > > can you provide me with more info, so i can fix this? What was the > segfaulting command line? Hello, The problem occurs in 2.4.18 kernel, I can't say if it's already the case in 2.4.19 because kernel freeze before I can try this :) But, according to Chat Tindel, it shoud have been fixed in the latest patches : ftp://ftp.sourceforge.net/pub/sourceforge/bonding/bonding-2.4.18-20020729 If I'm not wrong, the problem is bout media reporting that not all network drivers support. I've forgotten to say that it freezes ifconfig with version 1.42 With an older version, for example 1.39, I've got this : eth1 Link encap:Ethernet HWaddr 00:50:DA:33:BE:50 Media:net-tools 1.54 inet addr:192.168.0.6 Bcast:192.168.0.127 Mask:255.255.255.128 UP BROADCAST RUNNING PROMISC ALLMULTI SLAVE MULTICAST MTU:1500 Metric:1 RX packets:1309 errors:0 dropped:0 overruns:0 frame:0 TX packets:623 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:9 Base address:0x4400 You can notice that the Media value is very strange... But the main problem is not this, it's the 2.4.19 freeze with bonding. Thanks a lot for your help ! B.R. ------------- Fabien SALVI Centre de Ressources Informatiques Archamps, France -- http://www.cri74.org PingOO GNU/linux distribution : http://www.pingoo.org - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
