Hi Alan Thanks again for your help!
I just did it the quick and dirty way by editing /etc/rc.d/rc.local and running "/sbin/mii-tool -F 100baseTx-FD" after bootup. I'll guess we'll wait and see if it breaks in the next few days Thanks! Gonzalo On Mon, 2002-02-18 at 10:59, Alan Vink wrote: > Try the command below to "force specified media technology" - > > [root@tokolosh root]# mii-tool --help > usage: mii-tool [-VvRrwl] [-A media,... | -F media] [interface ...] > -V, --version display version information > -v, --verbose more verbose output > -R, --reset reset MII to poweron state > -r, --restart restart autonegotiation > -w, --watch monitor for link status changes > -l, --log with -w, write events to syslog > -A, --advertise=media,... advertise only specified media > -F, --force=media force specified media technology > media: 100baseT4, 100baseTx-FD, 100baseTx-HD, 10baseT-FD, 10baseT-HD, > (to advertise both HD and FD) 100baseTx, 10baseT > [root@tokolosh root]# > > Also update the list with a summary, improves the content and helps anyone > else with the same problem. > > Kind Regards, > Alan Vink > > -----Original Message----- > From: Gonzalo Servat [mailto:[EMAIL PROTECTED]] > Sent: Monday, 18 February 2002 10:36 AM > To: [EMAIL PROTECTED] > Subject: RE: [SLUG] NETDEV WATCHDOG: eth0: transmit timed out > > > Hi Alan > > Thanks for your reply > > Now that you mention it, there is a bit more to it: > > Feb 17 04:53:24 loki kernel: NETDEV WATCHDOG: eth0: transmit timed out > Feb 17 04:53:24 loki kernel: eth0: 21140 transmit timed out, status > fc340000, SIA ffffff7e 0000d000 0000d070 fffffec8, resetting... > Feb 17 04:53:24 loki kernel: eth0: transmit timed out, switching to MII > media. > Feb 17 04:53:25 loki kernel: eth0: Setting full-duplex based on MII#1 > link partner capability of 41e1. > Feb 17 04:53:32 loki kernel: NETDEV WATCHDOG: eth0: transmit timed out > > So yeah, as you said it tries negotiating and then finally giving up. > > How exactly would I hard set this network card driver to 100BaseTx-FDX? > > > > On Mon, 2002-02-18 at 10:28, Alan Vink wrote: > > >With the 2.2.x kernel, I didn't have any network card problems. > > >With the new kernel, I loose network connectivity (box is fine, just no > > >network until I reboot) every few days. The error all over dmesg is: > > > > > >NETDEV WATCHDOG: eth0: transmit timed out > > > > > >I thought instead of using the default kernel I'd upgrade and I'm now > > >running 2.4.17, however, the problem is still there. > > > > > >I should mention I didn't use ipchains when it ran a 2.2.x kernel but > > >I'm now using iptables on the 2.4.x kernel. Also, the network card is > > >using the tulip driver which is compiled into the kernel. > > > > > >Any ideas/suggestions would be greatly appreciated! > > > > > > > Gonzalo, it seems to be a common thing, if you check the SLUG archives, > you > > will notice a thread "DEC "211143-PC" nic on RH 7.2" at the end of 2001. > It > > is the tulip driver, that is not functioning correctly under the new > Kernel. > > You will notice in your log files, that the nic starts hunting and > > auto-negotiating before finaly giving up. Hard set it to your desired > media. > > eg -100baseTx-FDX, otherwise re-build your own drivers. > > > > PS - For us it was a "wasting precious time" issue, and thus we removed > the > > old DEC nics, and replaced them with others..I believe this will depend on > > you priorities, > > > > Hope it helps, Kind Regards - > > Alan Vink > > > > > -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
