search for: autonegotiation

...1(eth2) entering learning state br2: port 1(eth2) entering forwarding state br2: topology change detected, propagating Uhhuh. NMI received. Dazed and confused, but trying to continue 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 compl...

Howdy: This is (at least slightly) off-topic, but I've seen more knowledgeable folks than I mention autonegotiation in this venue and, since I didn't get any response on the vortex-bugs mailing list, I thought I'd ask here (also, the interface in question supports samba so...). And there should be some good news for some folks too. If this is old news, sorry (I've been too busy to keep up with the...

...C is plugged into the 2nd ethernet port on the phone. It > will drop the PC's connection for about 30 seconds, then > bring the connection back up for about 30 seconds. It does > this continually regardless of how the port is configured on > the phone. [...] Sounds like failing autonegotiation. Lock it down to a speed an duplex on the phone as well as on the device attached to the phone. Daryl G. Jurbala Introspect.net Consulting Tel: +1 215 825 8401 Fax: +1 508 526 8500 http://www.introspect.net PGP Key: http://www.introspect.net/pgp

Hi all, I have two HP DL145 G1 machines, running centos4 (2.6.9-22.0.2.ELsmp). Nics are recognized as: eth0: Tigon3 [partno(BCM95704) rev 2002 PHY(5704)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 00:00:1a:19:f1:05 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap [1] eth1: Tigon3 [partno(BCM95704) rev 2002 PHY(5704)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet

Hi, I've had extremely bad smbclient put performance when connecting from my Linux box to a Windows 95 box. I only get about 10KBytes/s! All other forms of data transfer work fine, and I get from 600-700KBytes/s. This is on a local 10BT LAN. I've seen a few other reports of this, but no solutions as of yet. smbclient does puts just fine to another Linux/Samba Server. I'm using

[Sorry if this is off-topic for this list, please advise me if there''s a better place to ask this] I have an embeded motherboard with 4 natsemi (DP8315) ethernet chips. I''m running a 2.6.9 kernel (I''ve tried 2.6.11 too) and a very minimal Slackware distribution. Now about the problem: The network interfaces seem to NOT transmit anything when the interface is

...9; says its > 100baseT and doesn't even list gigE as an option, and the cisco > 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 mode...

We've just moved one a new server from our sever room, where I built it, to the datacenter. We want to force autoneg off, and tell it gigabit and full duplex. Using ethtool, I get no errors setting the speed or duplex. HOWEVER, autoneg on works... and autoneg off utterly refuses to work, and gives: ethtool -s eth0 autoneg off Cannot set new settings: Invalid argument not setting autoneg

...is a private network on a cheap gigabit-switch (under controll from a serverhoster). sometime the ethernet-card lost the "speed" and "duplex" information and change it to "unknown". i can only fix this with a network-restart (or ifup/ifdown). now i will disable the autonegotiation - but i does not work. thanks sebastian

Dear colleagues, experimenting with new amd64-based router we found strange re(4) behaviour when working in autoselect media mode: whenever promisc mode turned on, renegotiating occurs, leading to 3 to 45 (depending on STP settings on the switch) network unavailability. Moreover, some other re(4) setting changes seem to disturb link state unneededly (such as ifconfig re0 -vlanhwtag) The most

Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 252 bytes Desc: OpenPGP digital signature Url : http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20060904/6ca2ff93/signature-0001.pgp

On 10/10/2016 09:31 PM, John R Pierce wrote: > > oh. Yeah, the entire "net-tools" package is deprecated. I tend to forget which of the two (ethtool or mii-tool) is in that set. # Avoid using any of these: $ rpm -ql net-tools

...Feb 5 08:41:48 pi4b systemd-networkd[155]: eth0: Gained carrier Feb 5 08:41:48 pi4b systemd-networkd[155]: eth0: Configured Feb 5 08:41:48 pi4b systemd-networkd-wait-online[181]: ignoring: lo - Ok, to network configures ok. And i notice Feb 5 08:41:48 pi4b systemd-udevd[178]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. - Setting it might speed up the boot process a bit but as shown network works fine. Failed to open /etc/resolv.conf: Invalid argument ( typo somewhere? ) Check the content. Feb 5 08:41:48 pi4b avahi-daemon[340]: Failed to open /etc...

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.

...est' Jan 15 14:00:53 waltz pptp[751]: anon log[ctrlp_disp:pptp_ctrl.c:770]: Received Stop Control Connection Request. Jan 15 14:00:53 waltz pptp[751]: anon log[ctrlp_rep:pptp_ctrl.c:243]: Sent control packet type is 4 'Stop-Control-Connection-Reply' Jan 15 14:10:22 waltz kernel: eth0: Autonegotiation advertising 0x5e1 partner 0x00. Jan 15 14:10:22 waltz kernel: eth0: link down. Jan 15 14:37:57 waltz pptp[777]: anon log[usage:pptp.c:91]: pptp called with wrong arguments, program not started. Jan 15 14:38:15 waltz pppd[778]: unrecognized option '-v' Jan 15 15:09:11 waltz kernel: eth0: Au...

...ot@fw-inet1 proc]# mii-diag eth0 > Basic registers of MII PHY #24: 3000 782d 0040 6176 05e1 0021 0000 0000. > Basic mode control register 0x3000: Auto-negotiation enabled. > You have link beat, and everything is working OK. > Your link partner is generating 10baseT link beat (no autonegotiation). > [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-cont...

Hi List, I am running a x86_64 Centos server, after a reboot the network has decided to not work.. this particular machine has 8 eth ports eth0-7. eth0 and eth3 were bonded (mode 1 ) after reboot the bond did not work. It came up OK but no data was passing through it. all other interfaces on the machine were working. I decided to remove the bond, so after removing the bond i was left with eth0

Am 02.07.2015 um 20:16 schrieb Gordon Messmer: > Have you yet: > setsebool -P use_samba_home_dirs 1 > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > > No, I didn't set it. Now I've set it and when logging into text console I no longer have the problem with the home

I've got a pair of identical CentOS 6.7 servers, with SuperMicro X8DTE-F motherboards, these have 2 each Intel 82574L ethernet ports. The eth0 ports are plugged in with 10' runs of brand new cat 5e cable to a Cisco Nexxus 9000 switch (provided by the data center). These servers keep coming up at 100baseT rather than gigE. I've swapped ports and cables with a different server,

I'm trying to maximize throughput between my Samba server and my Win2k (SP3 and 4) clients. Samba's configured to allow up to 64k packets and the server is on a GigE network (3com card, acenic driver) with SCSI UW2 drives (software RAID1 and RAID5 volumes). All clients are 100MB/sec FDX on a switched LAN. I can get sustained 35MB/sec transfers (read and write) on the disk subsystem