Slack and 3c59x

[jholl]

Hello, I am having problems getting my 3c905c-tx card to run in full duplex. I have a 10/100 switch and all of my other computers are connecting at 100 FD however this one will not i have tried to set it to run at 100 FD to no avail. I am using Slackware 9.0 with the default kernel 2.4.20 my card was automattically installed during setup using the 3c59x.o module. I have set the options where the card loads to go to full duplex
/sbin/modprobe 3c59x options=0x204
in the rc.netdevice
I am setting this wrong if so where do i need to put the options command.
I have tried once to complie the module from the source at scyld and it worked for like 2 min then when i rebooted it would load then i would lose eth0.
Another weird thing is my switch (a small linksys) shows me running at 100 half duplex. meanwhile when i run mii-tool it says the following
eth0 10mbit, half-duplex, no link (or something like that)
any suggestions? I have used lin on and off for like 4 years but nothing in depth. And i just decided to switch to it full time and have all of my mp3's etc are on different computer and would like to transfer them back to my computer

[mdwatts]

Have a look in the text files in the kernel documentation directory to see if you can find other options on how to force full duplex.

/usr/src/linux/Documentation/networking

[DMR]

The need to force the NICs operating mode indicates a problem; you should fix the problem instead of trying to force 100M or F-D.

Assuming that your card, cables, and switch are all in good working order, I'd say the problem lies with the driver and/or your particular version of the 3c509.

-Is the card a straight tx model, or is it a tx-M?
-What is the version of the driver?
-Have you checked 3Com site for any driver updates or to see if there are known issues with the driver?

[jholl]

my card is a 3c905cTx-M
I don't know how to tell what version of the module i am using so i looked through my kernel source and read in the 3c95x.c source file
defin DRV_VERSION LK1.1.16 and a date of 19 july 2001. Slackware doesn't include the source on the iso anymore so i had to download it seperate. is there i way i can verify this.

I have looked on scyld web site and read through all of the documentation however still unclear on what to do. I would like rebuild the driver, I had it compiled and used it but after a while it would mess up...(It would loose connectivity).
I have also verified my switch and cable to be ok. This card ran full duplex 3 days ago in windows before I switched to linux.
Thanks for you help
JH

[bandwidth_pig]

I run the same NIC and have indeed used it with the 3c59x (Vortex Boomerang module) and it has worked flawlessly. Based upon the descrption of your problems, I think your NIC is going out. Reasons being:

1. You mention there is no link. This means that your NIC is unable to communicate with your switch at all to synch up at layer 2.
2. You have been able to communicate intermitantly with your switch, but you are unable to negotiate duplex settings correctly, which again would indicate a problem with either the NIC or the switch. Your other machines are connecting at 100, so unless there is a problem with the specific port on the switch it seems unlikely a switch related issue. Since you are having no problems with the other ports, swapping ports would quickly prove the switch good. If you still can't latch up at the propper duplex setting, you know it's not the port.
3. You could attempt to set the switch port to a half duplex setting just for grins to see if the negotiation at layer two will take place (link up). If it still does not work, there is no question it is your NIC.

Luckily, NIC cards are cheap, so you should be able to replace it low cost. Good luck to you.

[DMR]

Originally posted by bandwidth_pig
1. You mention there is no link. This means that your NIC is unable to communicate with your switch at all to synch up at layer 2. Not necessarily. jholl said that mii-tool reports 10M/HD/no link; that can also be the result of a driver issue (trust me- I've been through it with different versions of the Realtek rtl8139/8139too drivers).

Originally posted by bandwidth_pig
2. You have been able to communicate intermitantly with your switch, but you are unable to negotiate duplex settings correctly, which again would indicate a problem with either the NIC or the switch. Again, not always; see above.

Originally posted by bandwidth_pig
Since you are having no problems with the other ports, swapping ports would quickly prove the switch good.Yup.

Originally posted by bandwidth_pig
3. You could attempt to set the switch port to a half duplex setting just for grins to see if the negotiation at layer two will take place (link up). If it still does not work, there is no question it is your NIC.Once again, no- see my response to point #1.


jholl,

The reason that I asked if you have the "M" moel is that I've read posts on various driver-support boards concerning that model. I'll get back to you after I'm able to some more research (dinner calls right now).

[jholl]

After I read bandwidth_pigs post I switched my card since I always keep spare cards with me for work. I switched the card with a Dlink 530TX+ and its running 100mbFD fine. I agree with DMR that it was the driver I have experienced cards not negotiating properly due to drivers. However since this is my first time with out a way to get back to windows on my system(If its not there I won't miss it ;) ) I won't bother messing with the 3com until I know more about Lin.
Thanks For Everyones Help
JH

[DMR]

Originally posted by jholl
I won't bother messing with the 3com until I know more about Lin. Hey, there's no sense beating your head against a hardware/driver problem if you have a working replacement.

:)

[bandwidth_pig]

I suppose anything is possible DMR. But what confuses me is I have the exact same NIC running the exact same driver and it has worked for me for years. Why would that be the case? Issue with the compiler?

[DMR]

Originally posted by bandwidth_pig
I suppose anything is possible DMR. But what confuses me is I have the exact same NIC running the exact same driver and it has worked for me for years. Why would that be the case? Issue with the compiler? Probably not the compiler. But if you've have that exact NIC running with the same version of driver before, I don't know what to suggest right now. I'll post again after I get the chance to research it more (the BBQ is begging me to put some steak on it right now).

:)

[bandwidth_pig]

Ahhh. I'm a BBQ man myself. And a serious steak lover. You like to marinade yours? I take the art of the BBQ quite serious. I should thaw some ribeyes for tonight.

I like mine somewhat red. Not much. But enough that it is still juicy. I have found that if I let the grill get nice and hot (let it sit on high for about fifteen minutes with the lid shut) and then turn it down on medium, slap my steaks on and let them seal up for about 30 seconds (no more...don't want to over cook) on each side, then turn down to low and cook for 7-9 minutes on each side they come out quite tasty. Matter of fact, I like to just pour a little minced garlic over them. No sauce. No nothing. Just a little garlic. Quite good.

[DMR]

Originally posted by bandwidth_pig
(let it sit on high for about fifteen minutes with the lid shut) and then turn it down on medium, slap my steaks on and let them seal up for about 30 seconds (no more...don't want to over cook) on each side, then turn down to low and cook for 7-9 minutes...Sit on high? Turn down to medium? Turn down to low? Serious BBQ man my flank steak!
Sounds like you're one of those yuppie outdoor Grizzly Adams wannabe types who thinks a gas grill is "roughing it".

:D :D

[bandwidth_pig]

BAH! Another charcoal zealot.

[bandwidth_pig]

BTW....most amusing to have somebody from "Fairfax California" tell me I'm a Grizzly Adams wannabe. I'm in Idaho. Tell me ALL about roughing it!!

LOL :D

[DMR]

Originally posted by bandwidth_pig
I'm in Idaho.Sorry to hear that man...

:p