Fedora Core 2 eth0: link down.

[NRaygun]

I've been playing with Fedora Core 2 and Samba. As I play with SWAT to get Samba to work(I still havent!), my machine "takes a break" after a while.

I use PuTTY to SSH into the box. After a while of playing, it stops responding. The machine is in the basement. I go down to the basement and the machine displays:

eth0: link down.
eth0: link up.
eth0: link down.
eth0: link up.
eth0: link down.
eth0: link up.

...over and over.

Any ideas?

It's making an already frustrating time with Samba even more frustrating.

 

[n0cmonkey]

Anything else in the logs?

 

[NRaygun]

Which logs in particular?

(sorry, I'm more of a Windows guy)

 

[cmetz]

NRaygun, what kind of NIC do you have?

 

[n0cmonkey]

/var/log/messages typically

 

[NRaygun]

Thanks folks. Here's the info:

NIC = Netgear FA311 Rev -C1

Relevant info from a "tail -30 messages":
May 22 11:40:05 fedora1 kernel: eth0: Autonegotiation advertising 0x5e1 partner 0x41e1.
May 22 11:40:05 fedora1 kernel: eth0: link up.
May 22 11:40:06 fedora1 kernel: eth0: Autonegotiation advertising 0x5e1 partner 0x00.
May 22 11:40:06 fedora1 kernel: eth0: link down.
May 22 11:40:08 fedora1 kernel: eth0: Autonegotiation advertising 0x5e1 partner 0x41e1.
May 22 11:40:08 fedora1 kernel: eth0: link up.
May 22 11:40:09 fedora1 kernel: eth0: Autonegotiation advertising 0x5e1 partner 0x00.
May 22 11:40:09 fedora1 kernel: eth0: link down.
May 22 11:40:11 fedora1 kernel: eth0: Autonegotiation advertising 0x5e1 partner 0x41e1.
May 22 11:40:11 fedora1 kernel: eth0: link up.
May 22 11:40:11 fedora1 kernel: eth0: Autonegotiation advertising 0x5e1 partner 0x00.
May 22 11:40:11 fedora1 kernel: eth0: link down.
May 22 11:40:13 fedora1 kernel: eth0: Autonegotiation advertising 0x5e1 partner 0x41e1.
May 22 11:40:13 fedora1 kernel: eth0: link up.
May 22 11:40:14 fedora1 kernel: eth0: Autonegotiation advertising 0x5e1 partner 0x00.
May 22 11:40:14 fedora1 kernel: eth0: link down.
May 22 11:40:16 fedora1 kernel: eth0: Autonegotiation advertising 0x5e1 partner 0x41e1.
May 22 11:40:16 fedora1 kernel: eth0: link up.

I also get the above with a "dmesg".

Any ideas? I wonder if I need to set the speed of the NIC?

 

[NRaygun]

OK, I give up! 🙁

The network problem mysteriously went away. In fact, it's quite stable now. I literally did nothing. Actually, I take that back. I went to Ikea with my wife and kids. When I got back, I checked the system. It had the up/down messages on the console but it looked like they stopped for some unknown reason.

I'm giving up on Linux as a server until additional documentation is available and it matures. Unfortunately that means I'll continue to use Windows 2000 Server.

Here are my reasons:

1. The network problem I ran into just went away. I dont feel comfortable with putting my files on this system. Could have been a NIC problem, power, etc. I'll never know.
2. Using SWAT, I couldnt even get a simple share to work. I've been all over Google and Samba.org. Still no go.
3. I had to turn off the firewall on XP to make some things work. I dont have to do this with the 2000 server.
4. I've spent way too much time with Linux with no results. I could have setup a dozen Windows Servers in this time and I'm not even a network admin.

I'd really like to make Linux work. I think it's speed, power, and cost are attractive. I just couldnt make it work with a resonable amount of effort.

Oh well.

Here's what I was using:
Dell XPS D300 (PII 300MHz)
128MB RAM
Netgear FA311 Rev-C1
6GB hard drive
Riva128 video card

OS = Fedora Core 2

Thanks everyone for your help. I'll brace myself for the flames.

 

[n0cmonkey]

1. I'm willing to put money on the fact it was a crappy NIC. 😉
2. SAMBA is tough. It took me a while to get it. Not sure if I could do it again. But SWAT never helped.
3. Not sure what you're talking about (I don't use XP).
4. Sometimes that happens.
5. bourbon is good. 😀