Hi,

On some of the newer kernels I seem to be having a problem whereby if the network connection is lost, and then re-connected the computer doesn't seem to recognise the cable being put back in for about 10 minutes or so, or until I rerun /etc/rc.d/rc.inet1.

This doesn't happen on the 2.4.26/.29 kernel provided by Pat, nor the 2.6.10 with the config file provided and a few things like compiling Reiserfs support into the kernel , disabling sound, the low performance usb driver. However it does occur on a 2.6.11.x, 2.6.12.2 and the recent 2.6.14.3 from -current all using Pat's .config file. I have also tried using the config file from my 2.6.10 kernel on the new 2.6.14.3 kernel, but that has no effect

I have experienced the same behaviour on 3 different computers with 3 different nics.

I'm not exactly sure where I need to be looking to sort this, and putting something like the thread title in google isn't helping much, so could someone give me a few pointers please

cheers

no one?


I downloaded slax 5.0.6 (for an unrelated reason) and I was trying it out, I was just having a nosy around and found it was running a 2.6.12.something kernel so I thought I'd see if it had the same problem. So I knocked off the power to my switch tried to make a connection to the internet, which failed obviously and then powered up my switch and tried to make another connection, this failed. Only after I reran /etc/rc.d/rc.inet1 and /etc/rc.d/rc.inet2 was I able to reconnect to the internet.

I'm a hesitant to upgrade the kernel on my server which is headless becuase I have the server on a UPS, but the network switch isn't, in the event of a powercut the server carries on running but the switch doesn't, and the switch only powers back up when I fire the geny up. If running a later kernel I will then be unable to connect to the server and as it is headless and locked away I have no way of reruning /etc/rc.d/rc.inet1.

Even if no one has a solution for this, could someone kindly test this on their own machine to see if the same behaviour is experienced, or if its just my hardware. Is it a known problem? Or likely a badly configured kernel?

I have encountered this problem on three computers and now 4 different network cards and the result is always the same

Cheers for any info