On Thu, 10 Mar 2005 11:38:01 +0000, Derek Jennings <[EMAIL PROTECTED]> wrote: > On Thursday 10 March 2005 03:16, Amy wrote: > > On Thu, 10 Mar 2005 00:58:43 +0000, Derek Jennings > > > > <[EMAIL PROTECTED]> wrote: > > > The command > > > modinfo 3c59x > > > lists the options for that driver, and we can refer to this page for a > > > description http://www.scyld.com/vortex.html > > > > > > To force this driver to be full duplex edit the file /etc/modprobe.conf > > > as root user > > > (Alt+F2 and type 'kdesu konqueror' in the box to get a root copy of > > > konqueror file manager) > > > Add the line > > > options 3c59x full_duplex=1 > > > > > > Then reboot > > > > > > derek > > > > Do I have to reboot? Shouldn't there be some way to restart the > > card/settings/whatever without rebooting? I'm spoiled and really > > really don't want to have to reboot my computer unless it is > > absolutely required. It feels like it takes too frellin' long to wait > > for it to shut down and restart itself. *pout* > > No rebooting is not essential. I just thought for a recent Windows refugee it > would be something you were used to doing. > > ifdown and ifup are sufficient to cause the card to autodetect again, but it > will not force reloading of the driver. What you need to do is > > service network stop > rmmod 3c59x > modprobe 3c59x > service network start > > derek Part of the reason I left windows was to avoid stupid things like restarting my computer. Ug. That and I liked that my computer doesn't go funny on me just because it's been on for hours and/or days at a time.
I ended up getting help from a friend though, which seems to have temporarily fixed the problem. We'll see if it holds whenever I end up having to turn my computer off for whatever reason. Probably the next time will be when I go to take it over to my boyfriend's house, but that will also include the adventure of getting it to work with a wireless adapter since he and his roommate have a wireless network happening. My friend talked me through using mii-tool to figure out what's up. First he had me check what the actual connection was (mii-tool eth1), to make sure it matched what the router was telling me. Then he had me use "mii-tool -F 100baseTx-FD eth1" to set it for full duplex mode. eth0 is the NIC onboard on the motherboard, I use a PCI NIC because my last motherboard had trouble with the onboard NIC. Anyhow, now, my router still doens't have the dull duplex light turned on, but if I do enough with my internet connection, it'll come on long enough to cooperate, and I am indeed back up and running for now. I'll make another post to this thread later if this change doesn't stick and I still have problems. But I should most likely be able to fix it with the other information provided in the thread if this doesn't stick if/when I have to restart next. Thanks for all your help! -- I have 49 invites to gmail, do you have a gmail account yet? Do you want one? Talk to me! ~~ >^..^< ~~ http://deathkitten.net "Words are, of course, the most powerful drug used by mankind." ~Rudyard Kipling "Several friends have asked me if I will again leave the country. In light of the failure--a second time--to count all the votes, that won't be necessary. My country has left me." ~Greg Palast
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
