From owner-freebsd-questions@freebsd.org Wed Nov 1 18:06:12 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D0B83E6194B for ; Wed, 1 Nov 2017 18:06:12 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 95D6B7C3DF for ; Wed, 1 Nov 2017 18:06:12 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-io0-x231.google.com with SMTP id 101so7982846ioj.3 for ; Wed, 01 Nov 2017 11:06:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=sDULpmbBeOo8DiGEURc82I98ZJwkDrkGbLL/VpzHbPw=; b=nqKTN+LQ+HBvMMscby532+QchusvEChf4MIa/JgmbaLGjuIDBbSK+oYt8jndoNXMsJ CGuqcFx2INBN9Ki69MNGDXGUHxHTNkEjpvAquyfKbNU8HPk8cR0DjV3kVu9RekuzIit9 zM14HiiG8axkWonXWiz7C6i388YC4Aqo0vZEjuuAtz7hvlg6BZM9K3RuEv08ir7pNgRo Vk52Twd2dEG2MxcKbgBP5cYguDiB+A23Uiyw/Ek4HhaLEtXgbvJIsPZogtOtrmJ7Gano SmqRyh6UEyOfxpHuwjHaS+3d7DT8aZl05gfSK76SSq9z/6PSyxqYWLOc8r6+Ulj4HWca VmoA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=sDULpmbBeOo8DiGEURc82I98ZJwkDrkGbLL/VpzHbPw=; b=VbLNhk4/qVaa0UcNINfrqE5Q/26orkkHc7XpEwRRHzPivOzJJPwuy6j5V/fWghyl6b nwj5canojnCKgOCNs0bF5TKt5Vd6WwH5zBUrw+MTLvWfDn2c7W1ulstgmk3oz3jJx7QB 0gRn33PpIE5ky5KAnwZL+r8E1nKSkw9+jIBnR/Q/5CAq3svV3/rPPDOdFfJS66DA76ce DFOcqes8hlhcNkcFfVskSXAOgtb93awXbL4Z3WWSZyRsY0+lMx3QzZPexdB9aoscrP32 gvY0C2H7uRS+UXJF7N/NQfNENenKrNw+nwKTnpVdyuwyMhnCiWqEbrj8QKeHKhR7dROn ge4w== X-Gm-Message-State: AMCzsaXQUoxyhX63X4DQY2dv+Ecf5Lp/R63tbM76dwi3rndIlG/eihYA o9g2rjo7oaztJs+r5uSFXJ4brg== X-Google-Smtp-Source: ABhQp+QBip1azRTRxGpcH8ov5wgKLVwSzkSKzx5pim5eKehl2NetxWvtpaRT5CbntDCsphUiIsdMDw== X-Received: by 10.36.224.78 with SMTP id c75mr1641155ith.71.1509559572091; Wed, 01 Nov 2017 11:06:12 -0700 (PDT) Received: from [10.0.10.7] (cpe-65-25-50-122.neo.res.rr.com. [65.25.50.122]) by smtp.googlemail.com with ESMTPSA id u84sm482130ioi.53.2017.11.01.11.06.11 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 01 Nov 2017 11:06:11 -0700 (PDT) Message-ID: <59FA0D12.1000209@gmail.com> Date: Wed, 01 Nov 2017 14:06:10 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Matthew Seaman CC: freebsd-questions@freebsd.org Subject: Re: Gigabit Ethernet adapter problem References: <59F895A5.1040809@gmail.com> <6ea04a6e-0c25-16e4-8007-8b647e473813@infracaninophile.co.uk> In-Reply-To: <6ea04a6e-0c25-16e4-8007-8b647e473813@infracaninophile.co.uk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Nov 2017 18:06:12 -0000 Matthew Seaman wrote: > On 31/10/2017 15:24, Ernie Luzar wrote: >> em - Intel(R) PRO/1000 Gigabit Ethernet adapter driver >> >> The boot messages show the Gigabit Ethernet adapter is correctly >> identified at boot time as shown below. >> >> em0: port 0xf080-0xf09f >> mem 0xf7d00000-0xf7d1ffff,0xf7d3c000-0xf7d3cfff irq 20 at >> device 25.0 on pci0 >> em0: Using an MSI interrupt >> em0: Ethernet address: d0:50:99:93:75:98 >> em0: netmap queues/slots: TX 1/1024, RX 1/1024 >> >> >> But after the system is up and running ifconfig em0 shows >> >> em0: flags=8843 >> metric 0 mtu 1500 >> options=4019b> TSO4,VLAN_HWTSO> >> ether d0:50:99:93:75:98 >> hwaddr d0:50:99:93:75:98 >> inet 10.0.10.2 netmask 0xff000000 broadcast 10.255.255.255 >> nd6 options=29 >> media: Ethernet autoselect (100baseTX ) >> status: active >> >> and we see that (100baseTX ) has been selected as default >> and it should be (1000baseTX ). >> >> How do I force the Ethernet adapter into Gigabit mode? > > This sort of down-grade is either because the switch port you've go the > machine plugged into is somehow set to negotiate to 100Mb/s, or else > you've got some dodgy cabling and consequently the system has backed off > to 100Mb/s because it can't sustain 1000Mb/s. > > Try looking at the output of 'netstat -i' -- if there are any errors > listed in the ierrs or oerrs columns, and particularly if they are > increasing over time. That indicates some sort of hardware problem, > usually due to a network cable having broken or been kinked or even tied > too tightly into a bundle. Start by swapping out the ethernet cable -- > it's cheap to replace. > > Cheers, > > Matthew > Turns out my Gigabit problem was the inline switch. It has a manufactures label calling itself "Gigafast 10/100". I replaced it with a new Gigabit switch and now all devices have Gigabit connection. Thanks to all who replied.