On 24 Aug, Kim, Jeong-Hwan wrote: > Hi, Every one > > My Network card is 3Com 509B. > When installing Debian I selected 3C509B as network card. > I hoped to have installed the Network Card correctly. > However, I peforms network commands such as ping, telent, ffp, etc., there is > no response. > (even not error message) > The 3Com 509B is not supported by Debian???? > I have another NIC 3Com 900B TP0. > Can the Debian support the 3C900B TP0??? > Please let me know the information of Debian's support for Network card of > 3Com. > > Thanks in advance. > > I think your 3c509b should work. Probably the other one too, but I'm not familiar with that one. There was some discussion of the 3c509 on this list a week or two ago. I never heard the final outcome of that episode, but there are a few things to be set on the card. Below is some of the possibly relevant exchange from before. If this doesn't help you might want to look back at the other messages that were exchanged previous to this one and if still not working, maybe post again with more details.
Don MacDougall ps. In process of posting this message I seem to have inadvertently reposted a copy of the below message to the list. My apologies to all for the extra posting. DWM On 19 Aug, To: debian-user@lists.debian.org wrote: > > Yes, this is surely your problem the 3c509 combo card has a BNC and a > twisted pair port and possibly also an AUI port as well. You have the > twisted pair (10baseT port chosen. It is changed by software. I've > never tried it in linux, but in Windows NT4 and I think also 95 it can > be set from the Network control panel. If you don't have that option, > I think you probably need the diskette that came with the card. It will > probably boot in dos and then allow you to change the port. If you > don't have that, I think you can probably download the program from > support.3com.com, put it on a dos boot disk and then be in business. > > Don MacDougall > > > On 19 Aug, Marc Mongeon wrote: >> Is this a card with two network ports? Unless I'm mistaken, "10BaseT" >> refers to the RJ-45 (telephone-like) port, while the BNC port should be >> called "10Base2" or something. You need to change the port using either >> switch settings on the card, or a software utility that came with the card. >> My memory on this is a little fuzzy, so I hope I'm not full of crap. >> >> Marc >> >> ---------- >> Marc Mongeon <[EMAIL PROTECTED]> >> Unix Specialist >> Ban-Koe Systems >> 9100 W Bloomington Fwy >> Bloomington, MN 55431-2200 >> (612)888-0123, x417 | FAX: (612)888-3344 >> ---------- >> "It's such a fine line between clever and stupid." >> -- David St. Hubbins and Nigel Tufnel of "Spinal Tap" >> >> >>>>> "Alex V. Toropov" <[EMAIL PROTECTED]> 08/19 4:02 AM >>> >>> Yes - the windows-machines can see each other in the windows-network. >>> (Workgroupname Olsen as the domainname at the linux box.) >>> The windows pc's can ping each other, but not the linux. >>> >>> I'm using bnc-cables, and the linux is in the middle. I've tried to change >>> the T's - no effect. >>> The start-up messages show no problems initializing the network-card. >> (Loading >>> modules ..... vfat smbfs 3c509 at 0x300 tag 1, 10baseT port, address 00 60 >> 08 >>> 31 22 84, IRQ 10) >>> (eth0: Setting Rx mode to 1 addresses) >>> >>> Yours Henning >> >> >> Well, one logical thing to test - try "route -n" >> You should see line like >> 192.168.1.0 0.0.0.0 255.255.255.0 ............ eth0 >> >> If it exists then I can't see any logical errors and I think the problem is >> in NIC >> may be You can change cards between computers and see if linux card will >> work in PC and vise verse.
