3com NIC using wrong media type

3com NIC using wrong media type

Post by m.. » Sat, 10 Oct 1998 04:00:00



Being new to Linux, I need a pointer.

A new install of Caldera 1.3 identifies my 3c509 card properly, but on
boot, I see that the driver is binding to the BNC port on the NIC,
when I need it to use the TP port. Where can I change the necessary
parameter?

 
 
 

3com NIC using wrong media type

Post by John Kenyo » Sun, 11 Oct 1998 04:00:00


Get a copy of the latest "Etherdisk" from www.3com.com
Create a DOS floppy with this stuff on it.

Boot your machine off a plain DOS diskette (No need for config.sys
etc)

Run the 3c5x9cfg.exe program off you etherdisk diskette.
If you want to save a copy of the configuration file onto a DOS
floppy.

Reboot machine, try again. I would advise against using any kind
of plug and play on this card, this also applies to automatic media
type detection.

/John

All replies to NG please...


> Being new to Linux, I need a pointer.

> A new install of Caldera 1.3 identifies my 3c509 card properly, but on
> boot, I see that the driver is binding to the BNC port on the NIC,
> when I need it to use the TP port. Where can I change the necessary
> parameter?


 
 
 

1. Q: Linksys LNE10/100TX NIC with 82c169 problems: Wrong media type?

Hi there,

my Linksys 10/100 card is recognized by release 4.0, but a ping to my
gateway fails. A ping to localhost and my own IP address works fine. It's
probably a misconfigured route but I suspect that my media type is wrong as
ifconfig shows "no carrier".

Here's what dmesg says concerning the NIC, ifconfig dc0 and my uname -a
output:
---
dmesg
pcib0: <Host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
isab0: <Intel 82371FB PCI to ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX ATA controller> port 0xe800-0xe80f at device 7.1 on
pci0
pci0: <S3 968 graphics accelerator> at 10.0 irq 15
dc0: <82c169 PNIC 10/100BaseTX> port 0xe400-0xe4ff mem 0xf7ff0000-0xf7ff00ff
irq 9 at device 11.0 on pci0
dc0: Ethernet address: 00:a0:cc:27:2e:a2
miibus0: <MII bus> on dc0
ukphy0: <Generic IEEE 802.3u media interface> on miibus0
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
dc0: supplying EUI64: 00:a0:cc:ff:fe:27:2e:a2

[..]

dc0: starting DAD for fe80:0001::02a0:ccff:fe27:2ea2
dc0: DAD complete for fe80:0001::02a0:ccff:fe27:2ea2 - no duplicates found

---
ifconfig dc0 output:

dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
 inet 134.176.85.175 netmask 0xffffff00 broadcast 134.176.85.255
 inet6 fe80::2a0:ccff:fe27:2ea2%dc0 prefixlen 64 scopeid 0x1
 ether 00:a0:cc:27:2e:a2
 media: 100baseTX status: no carrier
 supported media: autoselect 100baseTX <full-duplex> 100baseTX 10baseT/UTP
<full-duplex> 10baseT/UTP none

---
uname -a:
FreeBSD somehost.somedomain.sometld 4.0-RELEASE FreeBSD 4.0-RELEASE #0: Mon
Mar 20 22:50:22 GMT 2000

What's wrong here?

Thanks in advance
Stefan

2. NEC 4x4 ATAPI CD-Rom Changer

3. "Wrong media type" when mounting cdrom.

4. sharetab v. dfstab

5. weird CD problem: "Wrong medium type"

6. Samba 3.0.22 - too many open files

7. Configuring NIC transfer (media) type

8. New User Question: What are Slices?

9. Slow Cable Modem\Setting NIC media type

10. mount: wrong fs type,... What's wrong?

11. NIC using wrong interface

12. Why is sendmail using the wrong NIC???

13. Problems using 3Com NIC module 3c59x