search for: 100basetx

...nue You probably have a hardware problem with your RAM chips TLAN: eth0: Adaptor Error = 0x180002 TLAN: eth0: Starting autonegotiation. TLAN: eth0: Autonegotiation complete. TLAN: eth0: Link active with AutoNegotiation enabled, at 100Mbps Full-Duplex TLAN: Partner capability: 10BaseT-HD 10BaseT-FD 100baseTx-HD 100baseTx-FD TLAN: eth0: Adaptor Error = 0x180002 TLAN: eth0: Starting autonegotiation. TLAN: eth0: Autonegotiation complete. TLAN: eth0: Link active with AutoNegotiation enabled, at 100Mbps Full-Duplex TLAN: Partner capability: 10BaseT-HD 10BaseT-FD 100baseTx-HD 100baseTx-FD

...out bge0: failed to read EEPROM device_attach: bge0 attach returned 6 bge1: <Broadcom BCM5703 B0, ASIC rev. 0x1100> mem 0xe8600000-0xe860ffff irq 21 at device 1.0 on pci3 miibus0: <MII bus> on bge1 brgphy0: <BCM5703 10/100/1000baseTX PHY> on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge1: Ethernet address: 00:21:5e:4d:05:c8 any hints? P.S. I see EEPROM timeout fixes were already merged to RELENG_6 (I have post-fix version certainly). May that issue be somehow related? -- wbr, pluknet

anyone know how to force network cards talk at gig speeds when all it wants to do is establish a connection at 100mbits root at host1 [/backup/cpbackup/daily]# mii-tool eth0: negotiated 100baseTx-FD, link ok eth1: negotiated 100baseTx-FD flow-control, link ok 01:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11) Subsystem: Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express Flags: bus master, fast devsel,...

Hello, My computer is not connecting to the local network with the following configuration: dmesg.boot contains the following lines: ----------------------------------------- vr0: <VIA VT3043 Rhine I 10/100BaseTX> port 0xec00-0xec7f mem 0xfeafbc00-0xfeafbc7f irq 11 at device 12.0 on pci2 vr0: Ethernet address: 00:40:05:a5:00:04 miibus0: <MII bus> on vr0 amphy0: <Am79C873 10/100 media interface> on miibus0 amphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ifconfig -a reports the f...

I'm experiencing similar problems with a 3C996-T under 4.8-REL. In particular, connecting a 4.8-REL machine to a 5.1-REL machine leads to some interesting situations: I can do simple pings across the link, but ssh fails, and heavy pings crash the 4.8 machine. Similarly changing the interface configuration with ifconfig tends to crash the 4.8 machine (mtu, link0, up/down, etc). The

Guys, I've heard about some absurd RAM requirements for 9.1, has anybody tested it? e.g. http://forums.freebsd.org/showthread.php?t=36314 -- View this message in context: http://freebsd.1045724.n5.nabble.com/9-1-minimal-ram-requirements-tp5771583.html Sent from the freebsd-stable mailing list archive at Nabble.com.

...NT 16 interface pcib0: <Host to PCI bridge> on motherboard pci0: <PCI bus> on pcib0 pcib1: <PCI to PCI bridge (vendor=1106 device=b099)> at device 1.0 on pci0 pci1: <PCI bus> on pcib1 pci1: <NVidia model 0110 graphics accelerator> at 0.0 irq 11 rl0: <RealTek 8139 10/100BaseTX> port 0xec00-0xecff mem 0xdfffff00-0xdfffffff irq 11 at device 12.0 on pci0 rl0: Ethernet address: 00:50:fc:96:57:d3 miibus0: <MII bus> on rl0 rlphy0: <RealTek internal media interface> on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto uhci0: <VIA 83C572 USB...

...02 PHY(5704)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 00:00:1a:19:f1:04 eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap [1] Both machines are wired in the same way: eth0 is connected do 100mbit switch, eth1 to a gigabit switch. But: # mii-tool eth0: negotiated 100baseTx-FD, link ok eth1: negotiated 100baseTx-FD flow-control, link ok If I force eth1 to 1000 with ethtool, I get no link and then it autonegotiates itself back to 100. I can't even get them to talk at gigabit speed if I connect both machines together with crossover cable! Am I doing something wron...

...oller> at 6.0 tl0: <Compaq Netelligent 10/100 Proliant> port 0x6480-0x648f mem 0x40001500-0x4000150f irq 5 at device 7.0 on pci1 tl0: Ethernet address: 00:08:c7:78:08:57 miibus0: <MII bus> on tl0 nsphy0: <DP83840 10/100 media interface> on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto tlphy0: <ThunderLAN 10baseT media interface> on miibus0 tlphy0: 10base2/BNC, 10base5/AUI sym0: <875> port 0x6000-0x60ff mem 0x40000000-0x40000fff,0x40001400-0x400014ff irq 11 at device 9.0 on pci1 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking dc0: <Intel 21...

...05e1 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 1000 0300 0000 0000 0000 03ed 0300 0000 0036 000c 0f00 ff40 0026 0000 0000 000b. Basic mode control register 0x3000: Auto-negotiation enabled. You have link beat, and everything is working OK. This transceiver is capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT. Able to perform Auto-negotiation, negotiation not complete. Your link partner does not do autonegotiation, and this transceiver type does not report the sensed link speed. MII PHY #24 transceiver registers: 3000 780d 0040 6176 05e1 0000 0000 0000 0000 0...

...rverWorks NB6635 3.0LE host to PCI bridge> on motherboard IOAPIC #1 intpin 11 -> irq 2 IOAPIC #1 intpin 0 -> irq 9 IOAPIC #1 intpin 2 -> irq 16 IOAPIC #0 intpin 9 -> irq 17 pci0: <PCI bus> on pcib0 pci0: <S3 Savage 4 graphics accelerator> at 1.0 pcn0: <AMD PCnet/PCI 10/100BaseTX> port 0x2000-0x201f mem 0xfeb7fc00-0xfeb7fc1f irq 2 at device 2.0 on pci0 pcn0: Ethernet address: 00:02:55:91:a4:ad miibus0: <MII bus> on pcn0 ukphy0: <Generic IEEE 802.3u media interface> on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: <Intel 82550...

Hi, Last week I discovered that my samba-server seems rather slow. When I searched around I discovered that I wasn't the only one experiencing this, but I didn't find a solution. I experimented a little, and I hope someone can suggest a solution. First my server : SuSE 8.1, with Samba 2.2.5 (comes with the distribution). From a WinME-client I uploaded a 160Mb file to the samba-server.

...f,0xf0100000-0xf0103fff irq 16 at device 0.0 on pci2 re0: Using 1 MSI-X message re0: Chip rev. 0x2c800000 re0: MAC rev. 0x00000000 miibus0: <MII bus> on re0 rgephy0: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 1 on miibus0 rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Ethernet address: 90:2b:34:5f:bd:21 pcib3: <ACPI PCI-PCI bridge> irq 17 at device 28.5 on pci0 pci3: <ACPI PCI bus> o...

...o look at: >> ifconfig -a pn0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255 ether 87:ff:87:ff:87:ff media: autoselect (10baseT/UTP <half-duplex>) supported media: autoselect 100baseT4 100baseTX <full-duplex> 100baseTX <half-duplex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP <half-duplex> 10baseT/UTP lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500 tun0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500 ppp0: flags=8010<POINTOPOINT,MULTI...

...-------------- xer:/root# cat /var/run/dmesg.boot | grep xl xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xec00-0xec7f mem 0xfceffc00-0xfceffc7f irq 23 at device 11.0 on pci2 miibus0: <MII bus> on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:01:02:e0:04:1b xl1: <3Com 3c905C-TX Fast Etherlink XL> port 0xe880-0xe8ff mem 0xfceff800-0xfceff87f irq 20 at device 12.0 on pci2 miibus1: <MII bus> on xl1 xlphy1: <3c905C 10/100 internal PHY> on miibus1 xlphy1: 10baseT, 10baseT-FDX...

...switches see it as 100baseT too. > > anyone else run into anything like this before? oh. # mii-tool -v eth0 eth0: negotiated, link ok product info: vendor 00:50:43, model 11 rev 1 basic mode: autonegotiation enabled basic status: autonegotiation complete, link ok capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control # ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT...

I've plugged in two 3com OfficeConnect 10/100 3CSOHO100B-TX in my freebsd 4.8 box and they are not detected. Do I have to enable some support in the kernel ? Cheers Hannes

Hi, I'm having lots of difficulties with BCM5719, which is the default network card of HP Proliant DL 360 G8 servers. I can get a few ping replies before I get a couple of these: bge0: watchdog timeout -- resetting bge0: watchdog timeout -- resetting Then everything hangs. Can not log in using ssh.

I have just checked the Openbsd box on the if interface. fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 address: 00:02:55:30:54:28 media: Ethernet autoselect (100baseTX full-duplex) status: active inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255 inet6 fe80::202:55ff:fe30:5428%fxp0 prefixlen 64 scopeid 0x1 xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 address: 00:01:02:78:11:e8 media:...

...gt; [root@fw-inet1 proc]# mii-diag eth1 > Basic registers of MII PHY #24: 3000 782d 0040 6176 05e1 45e1 0003 0000. > Basic mode control register 0x3000: Auto-negotiation enabled. > You have link beat, and everything is working OK. > Your link partner advertised 45e1: Flow-control 100baseTx-FD 100baseTx > 10baseT-FD 10baseT, w/ 802.3X flow control. > [root@fw-inet1 proc]# mii-diag eth2 > Basic registers of MII PHY #24: 3000 786d 0000 0000 01e1 45e1 0007 2801. > Basic mode control register 0x3000: Auto-negotiation enabled. > You have link beat, and everything is wor...