Problem with re0
> Both the em and re drivers have had a lot of work done recently. Are > you trying with 8.2RC1 ? Tried with 8.2RC2 (via fixit shell with em): the same symptoms sadly. Card recognized, driver loaded as a result ifconfig reports it as available interface. Though neither static IP addressing nor DHCP makes it accessible on network. Interface cannot ping even the default gateway and neither this machine can be pinged. I am very sad :-( ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
Pyun YongHyeon (pyu...@gmail.com) [11.01.31 23:14] wrote: > > Then I have no idea. Does other OS work with your hardware without > issues? As last resort, could you try vendor's FreeBSD driver? The > vendor's driver applies a bunch of magic DSP fixups which re(4) > does not have. I don't know whether it makes difference or not but > it would be worth a try. Note, vendor's driver treat your > controller as old 8139 such that it disables all offload features > and does not work on non-x86 architectures. > i386 exposes the same problem :( as for vendor's drivers, i didn't try them yet ... -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
On Mon, Jan 31, 2011 at 02:15:09PM +0200, Zeus V Panchenko wrote: > Pyun YongHyeon (pyu...@gmail.com) [11.01.31 04:08] wrote: > > > The RTL8168/8111D sample board I have does not show this kind of > > > issue. This happens only when established link is 1000baseT, right? > > > I slightly changed PHY's link detection code so would you try that > > > patch at the following URL? > > > http://people.freebsd.org/~yongari/re/rgephy.link.patch3 > > > > Previous one had a bug, please update one. > > http://people.freebsd.org/~yongari/re/rgephy.link.patch4 > > no change :( > interface continues to flap > Then I have no idea. Does other OS work with your hardware without issues? As last resort, could you try vendor's FreeBSD driver? The vendor's driver applies a bunch of magic DSP fixups which re(4) does not have. I don't know whether it makes difference or not but it would be worth a try. Note, vendor's driver treat your controller as old 8139 such that it disables all offload features and does not work on non-x86 architectures. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
Milan Obuch (freebsd-...@dino.sk) [11.01.31 17:31] wrote: > > I checked my cables and one of them had bad pairing. Worked in 100 Mb mode, > but not in 1 Gb mode. After I replaced it I check with flood ping, 1472 bytes > packets again and no sign of problem here - one reply missing in almost 21 > millions tries. How are your flaps 'visible'? What fails? Ping test is > simple, > so I could overlooked something, but now it works for in 1 Gb mode, too... > while NIC flaps i see switch port on/off and in dmesg: ... re0: link state changed to UP re0: link state changed to DOWN re0: link state changed to UP re0: link state changed to DOWN re0: link state changed to UP re0: link state changed to DOWN re0: link state changed to UP re0: link state changed to DOWN re0: link state changed to UP re0: link state changed to DOWN re0: link state changed to UP ... -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
On Monday 31 January 2011 03:07:02 Pyun YongHyeon wrote: > On Sun, Jan 30, 2011 at 05:15:10PM -0800, Pyun YongHyeon wrote: > > On Sun, Jan 30, 2011 at 02:53:15PM +0100, Milan Obuch wrote: > > > On Sunday 30 January 2011 07:40:48 Zeus V Panchenko wrote: > > > > another detail for this nic > > > > > > > > dmidecode > > > > Base Board Information > > > > > > > > Manufacturer: ASUSTeK Computer INC. > > > > Product Name: AT5NM10-I > > > > Version: Rev x.0x > > > > Serial Number: MT7006K15200322 > > > > > > I did not followed this thread closely, but I checked my new board and > > > it is the same. > > > > > > > uname -a > > > > FreeBSD 8.2-PRERELEASE amd64 > > > > > > > > system was cvsup-ed 2011.01.20 > > > > > > > > if_re.c,v 1.160.2.17 2011/01/15 00:32:15 yongari > > > > > > > > dmesg > > > > rgephy0: PHY 1 on miibus0 > > > > rgephy0: 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: > > > > 20:cf:30:89:5e:95 > > > > re0: [FILTER] > > > > > > > > pciconf -lv > > > > re0@pci0:2:0:0: class=0x02 card=0x83a31043 chip=0x816810ec > > > > rev=0x03 hdr=0x00 vendor = 'Realtek Semiconductor' > > > > > > > > device = 'Gigabit Ethernet NIC(NDIS 6.0) > > > > (RTL8168/8111/8111c)' class = network > > > > subclass = ethernet > > > > > > All details are the same for my board (modulo serial number and MAC, of > > > course), and in my case it works with no problem, but only in 100 Mb > > > switch port. In 1 Gb port I have no link. I must verify my cables, > > > port on switch itself works just fine with another 1 Gb (intel) card. > > > > Would you try a patch at the following URL? > > http://people.freebsd.org/~yongari/re/rgephy.link.patch3 > > Previous one had a bug, please use updated one. > http://people.freebsd.org/~yongari/re/rgephy.link.patch4 > > > > > while connected directly NIC <-> NIC they flaps too > > > > > > I will try this against another 1 Gb card too, just to see what > > > happens... in 100 Mb mode it works just fine, as I mentioned already - > > > running flood ping with 1472 bytes packets for more than an hour I see > > > only four responses missing in more than 21 millions tries... > > > > > > Regards, > > > Milan > I checked my cables and one of them had bad pairing. Worked in 100 Mb mode, but not in 1 Gb mode. After I replaced it I check with flood ping, 1472 bytes packets again and no sign of problem here - one reply missing in almost 21 millions tries. How are your flaps 'visible'? What fails? Ping test is simple, so I could overlooked something, but now it works for in 1 Gb mode, too... Regards, Milan ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
Pyun YongHyeon (pyu...@gmail.com) [11.01.31 04:08] wrote: > > The RTL8168/8111D sample board I have does not show this kind of > > issue. This happens only when established link is 1000baseT, right? > > I slightly changed PHY's link detection code so would you try that > > patch at the following URL? > > http://people.freebsd.org/~yongari/re/rgephy.link.patch3 > > Previous one had a bug, please update one. > http://people.freebsd.org/~yongari/re/rgephy.link.patch4 no change :( interface continues to flap -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
On Sun, Jan 30, 2011 at 05:20:32PM -0800, Pyun YongHyeon wrote: > On Sun, Jan 30, 2011 at 08:40:48AM +0200, Zeus V Panchenko wrote: > > another detail for this nic > > > > dmidecode > > Base Board Information > > Manufacturer: ASUSTeK Computer INC. > > Product Name: AT5NM10-I > > Version: Rev x.0x > > Serial Number: MT7006K15200322 > > > > uname -a > > FreeBSD 8.2-PRERELEASE amd64 > > > > system was cvsup-ed 2011.01.20 > > > > if_re.c,v 1.160.2.17 2011/01/15 00:32:15 yongari > > > > dmesg > > rgephy0: PHY 1 on miibus0 > > rgephy0: 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: 20:cf:30:89:5e:95 > > re0: [FILTER] > > > > pciconf -lv > > re0@pci0:2:0:0: class=0x02 card=0x83a31043 chip=0x816810ec rev=0x03 > > hdr=0x00 > > vendor = 'Realtek Semiconductor' > > device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)' > > class = network > > subclass = ethernet > > > > > > while connected directly NIC <-> NIC they flaps too > > > > so, the issue with switch related causes can be excluded i believe > > > > The RTL8168/8111D sample board I have does not show this kind of > issue. This happens only when established link is 1000baseT, right? > I slightly changed PHY's link detection code so would you try that > patch at the following URL? > http://people.freebsd.org/~yongari/re/rgephy.link.patch3 Previous one had a bug, please update one. http://people.freebsd.org/~yongari/re/rgephy.link.patch4 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
On Sun, Jan 30, 2011 at 05:15:10PM -0800, Pyun YongHyeon wrote: > On Sun, Jan 30, 2011 at 02:53:15PM +0100, Milan Obuch wrote: > > On Sunday 30 January 2011 07:40:48 Zeus V Panchenko wrote: > > > another detail for this nic > > > > > > dmidecode > > > Base Board Information > > > Manufacturer: ASUSTeK Computer INC. > > > Product Name: AT5NM10-I > > > Version: Rev x.0x > > > Serial Number: MT7006K15200322 > > > > > > > I did not followed this thread closely, but I checked my new board and it > > is > > the same. > > > > > uname -a > > > FreeBSD 8.2-PRERELEASE amd64 > > > > > > system was cvsup-ed 2011.01.20 > > > > > > if_re.c,v 1.160.2.17 2011/01/15 00:32:15 yongari > > > > > > dmesg > > > rgephy0: PHY 1 on miibus0 > > > rgephy0: 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: 20:cf:30:89:5e:95 > > > re0: [FILTER] > > > > > > pciconf -lv > > > re0@pci0:2:0:0: class=0x02 card=0x83a31043 chip=0x816810ec rev=0x03 > > > hdr=0x00 vendor = 'Realtek Semiconductor' > > > device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)' > > > class = network > > > subclass = ethernet > > > > > > > All details are the same for my board (modulo serial number and MAC, of > > course), and in my case it works with no problem, but only in 100 Mb switch > > port. In 1 Gb port I have no link. I must verify my cables, port on switch > > itself works just fine with another 1 Gb (intel) card. > > > > Would you try a patch at the following URL? > http://people.freebsd.org/~yongari/re/rgephy.link.patch3 > Previous one had a bug, please use updated one. http://people.freebsd.org/~yongari/re/rgephy.link.patch4 > > > > > > while connected directly NIC <-> NIC they flaps too > > > > > > > I will try this against another 1 Gb card too, just to see what happens... > > in > > 100 Mb mode it works just fine, as I mentioned already - running flood ping > > with 1472 bytes packets for more than an hour I see only four responses > > missing in more than 21 millions tries... > > > > Regards, > > Milan ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
On Sun, Jan 30, 2011 at 08:40:48AM +0200, Zeus V Panchenko wrote: > another detail for this nic > > dmidecode > Base Board Information > Manufacturer: ASUSTeK Computer INC. > Product Name: AT5NM10-I > Version: Rev x.0x > Serial Number: MT7006K15200322 > > uname -a > FreeBSD 8.2-PRERELEASE amd64 > > system was cvsup-ed 2011.01.20 > > if_re.c,v 1.160.2.17 2011/01/15 00:32:15 yongari > > dmesg > rgephy0: PHY 1 on miibus0 > rgephy0: 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: 20:cf:30:89:5e:95 > re0: [FILTER] > > pciconf -lv > re0@pci0:2:0:0: class=0x02 card=0x83a31043 chip=0x816810ec rev=0x03 > hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)' > class = network > subclass = ethernet > > > while connected directly NIC <-> NIC they flaps too > > so, the issue with switch related causes can be excluded i believe > The RTL8168/8111D sample board I have does not show this kind of issue. This happens only when established link is 1000baseT, right? I slightly changed PHY's link detection code so would you try that patch at the following URL? http://people.freebsd.org/~yongari/re/rgephy.link.patch3 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
On Sun, Jan 30, 2011 at 02:53:15PM +0100, Milan Obuch wrote: > On Sunday 30 January 2011 07:40:48 Zeus V Panchenko wrote: > > another detail for this nic > > > > dmidecode > > Base Board Information > > Manufacturer: ASUSTeK Computer INC. > > Product Name: AT5NM10-I > > Version: Rev x.0x > > Serial Number: MT7006K15200322 > > > > I did not followed this thread closely, but I checked my new board and it is > the same. > > > uname -a > > FreeBSD 8.2-PRERELEASE amd64 > > > > system was cvsup-ed 2011.01.20 > > > > if_re.c,v 1.160.2.17 2011/01/15 00:32:15 yongari > > > > dmesg > > rgephy0: PHY 1 on miibus0 > > rgephy0: 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: 20:cf:30:89:5e:95 > > re0: [FILTER] > > > > pciconf -lv > > re0@pci0:2:0:0: class=0x02 card=0x83a31043 chip=0x816810ec rev=0x03 > > hdr=0x00 vendor = 'Realtek Semiconductor' > > device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)' > > class = network > > subclass = ethernet > > > > All details are the same for my board (modulo serial number and MAC, of > course), and in my case it works with no problem, but only in 100 Mb switch > port. In 1 Gb port I have no link. I must verify my cables, port on switch > itself works just fine with another 1 Gb (intel) card. > Would you try a patch at the following URL? http://people.freebsd.org/~yongari/re/rgephy.link.patch3 > > > > while connected directly NIC <-> NIC they flaps too > > > > I will try this against another 1 Gb card too, just to see what happens... in > 100 Mb mode it works just fine, as I mentioned already - running flood ping > with 1472 bytes packets for more than an hour I see only four responses > missing in more than 21 millions tries... > > Regards, > Milan ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
On Sunday 30 January 2011 07:40:48 Zeus V Panchenko wrote: > another detail for this nic > > dmidecode > Base Board Information > Manufacturer: ASUSTeK Computer INC. > Product Name: AT5NM10-I > Version: Rev x.0x > Serial Number: MT7006K15200322 > I did not followed this thread closely, but I checked my new board and it is the same. > uname -a > FreeBSD 8.2-PRERELEASE amd64 > > system was cvsup-ed 2011.01.20 > > if_re.c,v 1.160.2.17 2011/01/15 00:32:15 yongari > > dmesg > rgephy0: PHY 1 on miibus0 > rgephy0: 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: 20:cf:30:89:5e:95 > re0: [FILTER] > > pciconf -lv > re0@pci0:2:0:0: class=0x02 card=0x83a31043 chip=0x816810ec rev=0x03 > hdr=0x00 vendor = 'Realtek Semiconductor' > device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)' > class = network > subclass = ethernet > All details are the same for my board (modulo serial number and MAC, of course), and in my case it works with no problem, but only in 100 Mb switch port. In 1 Gb port I have no link. I must verify my cables, port on switch itself works just fine with another 1 Gb (intel) card. > > while connected directly NIC <-> NIC they flaps too > I will try this against another 1 Gb card too, just to see what happens... in 100 Mb mode it works just fine, as I mentioned already - running flood ping with 1472 bytes packets for more than an hour I see only four responses missing in more than 21 millions tries... Regards, Milan ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
another detail for this nic dmidecode Base Board Information Manufacturer: ASUSTeK Computer INC. Product Name: AT5NM10-I Version: Rev x.0x Serial Number: MT7006K15200322 uname -a FreeBSD 8.2-PRERELEASE amd64 system was cvsup-ed 2011.01.20 if_re.c,v 1.160.2.17 2011/01/15 00:32:15 yongari dmesg rgephy0: PHY 1 on miibus0 rgephy0: 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: 20:cf:30:89:5e:95 re0: [FILTER] pciconf -lv re0@pci0:2:0:0: class=0x02 card=0x83a31043 chip=0x816810ec rev=0x03 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)' class = network subclass = ethernet while connected directly NIC <-> NIC they flaps too so, the issue with switch related causes can be excluded i believe -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
Hi all,
the same problem i wrote in the first posts about year ago :(
onboard re(4) tremendous flapping
while ( cable connects nic and switch )
{
re0: link state changed to UP
re0: link state changed to DOWN
}
here the details:
dmidecode
Base Board Information
Manufacturer: ASUSTeK Computer INC.
Product Name: AT5NM10-I
Version: Rev x.0x
Serial Number: MT7006K15200322
uname -a
FreeBSD 8.2-PRERELEASE amd64
system was cvsup-ed 2011.01.20
if_re.c,v 1.160.2.17 2011/01/15 00:32:15 yongari
dmesg
rgephy0: PHY 1 on miibus0
rgephy0: 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: 20:cf:30:89:5e:95
re0: [FILTER]
pciconf -lv
re0@pci0:2:0:0: class=0x02 card=0x83a31043 chip=0x816810ec rev=0x03 hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)'
class = network
subclass = ethernet
flapping starts with cable pluging to the nic and to the switch, even without
ip assignment
switch used is TP-LINK TL-SG5426
the problem persists already about year and the only solution is to use
external nic ...
any idea/news?
--
Zeus V. Panchenko
IT Dpt., IBS ltdGMT+2 (EET)
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
On 1/2/2011 4:20 PM, Gabor Radnai wrote: > "The question has come up several times. What should be changed in > re(4) to cover this?" Both the em and re drivers have had a lot of work done recently. Are you trying with 8.2RC1 ? ---Mike ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Problem with re0
"The question has come up several times. What should be changed in re(4) to cover this?" Well, if this question has come up several times a) it has a reason: same chip works for some but not for others b) description is not clear that driver is only supporting this chip if and when ... Anyhow, one advise to"fix" my problem was to get a decent nic. I did: Intel Gigabit CT desktop adapter. But still no luck, same symptoms: insert card to PCI-E x 1 slot, FreeBSD boots, card detected, see outgoing messages through this card (via tcpdump) but no replies (e.g. from DHCP server) are processed. I see ip address was offered by DHCP server but driver does not get/process any answer and sets ip address to 0.0.0.0 ... and one more new thing from em driver: by reporting "watchdog timeout - reset" interface is getting down-up frequently. So, neither RTL8111 nor this Intel 82574L chip is working under FreeBSD via PCI-E, quite frustrating. Though works under Linux. Might be a PCI-E related communication issue of FreeBSD? Or is there special configuration to force PCI-E to work with network cards in network drivers or sysctl variable am not aware of? ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
On Mon, 13 Dec 2010, Gabor Radnai wrote: Realtek 8111 is not supported - that's the final conclusion? If so can this be made clear in re driver manual? r...@pci0:4:0:0:class=0x02 card=0x514c1462 chip=0x816810ec rev=0x02 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)' class = network subclass = ethernet Works fine here. The manufacturer (MSI) claims this is an 8111C. The question has come up several times. What should be changed in re(4) to cover this? ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
On Mon, Dec 13, 2010 at 3:26 PM, Chuck Swiger wrote: > On Dec 13, 2010, at 11:54 AM, Gabor Radnai wrote: > > Realtek 8111 is not supported - that's the final conclusion? If so can > this be made clear in re driver manual? > > At least some people have reported the Realtek 8111 working for them. > > This said, Realtek's older 10/100 NICs were infamous for being slow, buggy > hardware that I'd choose to discard rather than install into a machine, and > their gigabit NICs aren't much better. Get a Intel em or Broadcom bce/bge > NIC instead. > I guess it depends on various conditions: r...@pci0:3:0:0: class=0x02 card=0x75811462 chip=0x816810ec rev=0x03 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)' class = network subclass = ethernet I can sustain over 700 Mb transfers, and it does somewhat better than the bge nic I have which peaks at around 600Mb. Personally, I've never had great performance out of any Broadcom, but my experience is somewhat limited there and haven't used any relatively current chipsets. FreeBSD galacticdominator.com 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #5: Thu Nov 25 19:14:00 CST 2010 a...@galacticdominator.com:/usr/obj/usr/src/sys/GENERIC amd64 This nic has been working on the stable branch for over a year from when I aquired the system and I've never had an issue with it. -- Adam Vande More ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
On Dec 13, 2010, at 11:54 AM, Gabor Radnai wrote: > Realtek 8111 is not supported - that's the final conclusion? If so can this > be made clear in re driver manual? At least some people have reported the Realtek 8111 working for them. This said, Realtek's older 10/100 NICs were infamous for being slow, buggy hardware that I'd choose to discard rather than install into a machine, and their gigabit NICs aren't much better. Get a Intel em or Broadcom bce/bge NIC instead. Regards, -- -Chuck ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Problem with re0
Realtek 8111 is not supported - that's the final conclusion? If so can this be made clear in re driver manual? Thanks. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
Hi, On Thu, Dec 2, 2010 at 10:30 PM, Pyun YongHyeon wrote: > > On Thu, Dec 02, 2010 at 09:56:42PM +0100, Gabor Radnai wrote: > > Hi, > > > > Could someone pls advise how to inject HEAD driver to stable release without > > full kernel rebuild (if possible)? > > > > If you have updated to stable/8, the driver code would be the same. > So need to replace driver with HEAD version. How exactly? What do you mean on 'replace': compile from source, just copy the binary from a snapshot image to /boot/kernel or ... ? > > > I tried this way but found no assurance/evidence actually kernel using the > > new driver: > > 1. download full HEAD source with help of csup > > 2. in /usr/src/sys/modules/re did make install which in turn compiled re > > driver and installed into default /boot/kernel > > 3. reboot > > > > So far so good but still re0 driver cannot properly handle rtl8111 chip > > seeing the very same symptoms as in case of > > the driver shipped with RELEASE. > > > > If my memory is correct, your controller is somewhat old 8168 PCIe > controller. I also have the same TP-Link TG-3468 PCIe network card > which seems to be the only stand-alone PCIe 8168 controller in > market. I don't see any problems using the controller so would you > summarize your issue again?(Sorry, if you already post it) If you check the original post I did all details there but a quick summary: I have two TP-Link TG-3468 PCIe network cards which is using Realtek 8168/8111 chip. re0: port 0xac00-0xacff mem 0xfdbff000-0xfdbf irq 16 at device 0.0 on pci1 re0: Using 1 MSI messages re0: Chip rev. 0x3800 re0: MAC rev. 0x miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: d8:5d:4c:80:b4:88 re0: [FILTER] When I try to use it cannot process DHCP answer properly (sets IP address to 0.0.0.0/255.255.255.255), neither works if using fix IP. Link is up, cable is working but card simply cannot communicate. I switched back and forth all components I could: new cable, connect to different switch port, replace card, use the cable/switch port which is working for integrated motherboard NIC, disable integrated NIC ... no luck so far. Thanks. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
On Thu, Dec 02, 2010 at 09:56:42PM +0100, Gabor Radnai wrote: > Hi, > > Could someone pls advise how to inject HEAD driver to stable release without > full kernel rebuild (if possible)? > If you have updated to stable/8, the driver code would be the same. So need to replace driver with HEAD version. > I tried this way but found no assurance/evidence actually kernel using the > new driver: > 1. download full HEAD source with help of csup > 2. in /usr/src/sys/modules/re did make install which in turn compiled re > driver and installed into default /boot/kernel > 3. reboot > > So far so good but still re0 driver cannot properly handle rtl8111 chip > seeing the very same symptoms as in case of > the driver shipped with RELEASE. > If my memory is correct, your controller is somewhat old 8168 PCIe controller. I also have the same TP-Link TG-3468 PCIe network card which seems to be the only stand-alone PCIe 8168 controller in market. I don't see any problems using the controller so would you summarize your issue again?(Sorry, if you already post it) > Thanks. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Problem with re0
Hi, Could someone pls advise how to inject HEAD driver to stable release without full kernel rebuild (if possible)? I tried this way but found no assurance/evidence actually kernel using the new driver: 1. download full HEAD source with help of csup 2. in /usr/src/sys/modules/re did make install which in turn compiled re driver and installed into default /boot/kernel 3. reboot So far so good but still re0 driver cannot properly handle rtl8111 chip seeing the very same symptoms as in case of the driver shipped with RELEASE. Thanks. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Problem with em0 (was Re: Problem with re0)
Just a "me too" to echo Gabor's request for guidance for checking out and using new drivers from HEAD. In my case I'd like to try the new em(4) Jack's been talking about. I've been running FreeBSD machines for several years, but this is the first time I've found myself having driver problems On 21-Nov-2010, Gabor Radnai writes: > > Ok, please try latest re(4) in HEAD. > > I am noob with this, sorry. Could you please give guidance? > If I copy if_re.ko from snapshot image to /boot/kernel/ is it > sufficient or have to build a whole new kernel from HEAD source? Can > somehow just compile a new driver if copy does not work? > > Thanks. > ___ ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
> Ok, please try latest re(4) in HEAD. I am noob with this, sorry. Could you please give guidance? If I copy if_re.ko from snapshot image to /boot/kernel/ is it sufficient or have to build a whole new kernel from HEAD source? Can somehow just compile a new driver if copy does not work? Thanks. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
re0: flags=8843 metric 0 mtu 1500 options=389b ether d8:5d:4c:80:b4:88 inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 media: Ethernet autoselect (1000baseT ) status: active nfe0: flags=8843 metric 0 mtu 1500 options=80008 ether 00:1a:92:38:dc:95 inet 192.168.0.200 netmask 0xff00 broadcast 192.168.0.255 media: Ethernet autoselect (1000baseT ) status: active lo0: flags=8049 metric 0 mtu 16384 options=3 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff00 nd6 options=3 On Fri, Nov 12, 2010 at 11:53 PM, Pyun YongHyeon wrote: > On Fri, Nov 12, 2010 at 10:18:40PM +0100, Gabor Radnai wrote: > > Hi, > > > > I hope you are interested in inet section it looks like this (will able > to > > send the exact output only a bit later unfortunately as removed the card) > : > > inet 0.0.0.0 netmask 255.255.255.255 > > > > This might be caused by dhclient(i.e. dhclient(8) failed to receive > DHCP ACK). > BTW, you still didn't show me the output of ifconfig re0 after UP > the interface(i.e. ifconfig re0 up). > > > Thanks, > > Gabor > > > > On Thu, Nov 11, 2010 at 10:26 PM, Pyun YongHyeon > wrote: > > > > > On Thu, Nov 11, 2010 at 09:56:26PM +0100, Gabor Radnai wrote: > > > > Hi, > > > > > > > > I have an Asus M2NPV-VM motherboard with integrated Nvidia MCP51 > Gigabit > > > > Ethernet NIC and > > > > TP-Link TG-3468 PCIe network card which is using Realtek 8111 chip. > > > > > > > > I have problem with the re driver: the Nvidia network interface is > > > working > > > > properly but the other > > > > though it seems recognized by OS I cannot use. Sporadically it > remains > > > down > > > > and if it gets up then > > > > does not get ip address via DHCP nor help if I set static ip address. > Can > > > > manipulate via ifconfig but > > > > unreachable via IP. > > > > > > > > I replaced cable, interchanged cable working with Nvidia, restarted > > > > switch/router but no luck so far. > > > > Also using this nic in a Windows machine - it works. Using my Asus > mob > > > with > > > > Ubuntu Live CD - card works. > > > > > > > > Can it be a driver bug or this type of chip is not supported by re > > > driver? > > > > > > > > > > Eh, you already know the answer, recognized by re(4) but does not > > > work so it's a bug of re(4). Would you show me the output of > > > ifconfig re0 after UP the interface(i.e. ifconfig re0 up). > > > > ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
On Sat, Nov 13, 2010 at 09:09:18AM +0200, Zeus V Panchenko wrote:
> Pyun YongHyeon (pyu...@gmail.com) [10.11.13 01:01] wrote:
> >
> > Please be more specific for the issue. Your description is hard to
> > narrow down possible cause.
> >
> > > i was sure it is the problem of the onboard rt nics ...
> > >
> >
> > pciconf output of all re(4) controllers are useless because the
> > vendor uses the same device id. Please show me the output of dmesg
> > which will contain necessary information to identify your
> > controller revision.
> >
>
> oh, sorry :(
>
> here is what you say:
>
> the integrated onboard nic:
> re0: port
> 0xe800-0xe8ff mem 0xfafff000-0xfaff,0xfaff8000-0xfaffbfff irq 17 at
> device 0.0 on pci2
> re0: Using 1 MSI messages
> re0: Chip rev. 0x2800
> re0: MAC rev. 0x
> miibus0: on re0
> rgephy0: PHY 1 on miibus0
> rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
> 1000baseT-FDX, auto
> re0: Ethernet address: 48:5b:39:d2:1d:89
> re0: [FILTER]
>
>
> external PCI nic:
> re1: port 0xd800-0xd8ff mem
> 0xfbeffc00-0xfbeffcff irq 17 at device 0.0 on pci1
> re1: Chip rev. 0x1000
> re1: MAC rev. 0x
> miibus1: on re1
> rgephy1: PHY 1 on miibus1
> rgephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
> 1000baseT-FDX, auto
> re1: Ethernet address: 00:21:91:f4:5f:e4
> re1: [FILTER]
>
>
> all that data i was posting here before (several months ago) and
> nothing changed since that time
>
> due to production state of the boxes i was forced finally to switch to
> external nics and to configure it with vlans and even to unplug the
> cable of the onboard nic
>
> since nic with plugged cable but without assigned ip address did begin
> flap (may be it's specific of the swith it plugged in, it is TP-Link
> TL-SG5426 but no other nic behaves this way)
>
> i have 7 boxes of this configuration and all 6 are running
> now on external nics
>
>
> if i can provide any debug/info/e.t.c. please let me know, i'd be
> happy it'd work at last :)
>
Ok, please try latest re(4) in HEAD. If that does not change the
behavior, give attached patch spin and let me know whether it makes
any difference. Note, the attached may trigger watchdog timeouts
under certain conditions but if you do not remove UTP cable that
wouldn't happen. I have to verify whether it can really trigger
watchdog timeouts and it takes more time on my side.
Index: sys/dev/re/if_re.c
===
--- sys/dev/re/if_re.c (revision 215345)
+++ sys/dev/re/if_re.c (working copy)
@@ -2151,9 +2151,10 @@
RL_LOCK_ASSERT(sc);
mii = device_get_softc(sc->rl_miibus);
- mii_tick(mii);
- if ((sc->rl_flags & RL_FLAG_LINK) == 0)
+ if ((sc->rl_flags & RL_FLAG_LINK) == 0) {
+ mii_tick(mii);
re_miibus_statchg(sc->rl_dev);
+ }
/*
* Reclaim transmitted frames here. Technically it is not
* necessary to do here but it ensures periodic reclamation
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
Pyun YongHyeon (pyu...@gmail.com) [10.11.13 01:01] wrote: > > Please be more specific for the issue. Your description is hard to > narrow down possible cause. > > > i was sure it is the problem of the onboard rt nics ... > > > > pciconf output of all re(4) controllers are useless because the > vendor uses the same device id. Please show me the output of dmesg > which will contain necessary information to identify your > controller revision. > oh, sorry :( here is what you say: the integrated onboard nic: re0: port 0xe800-0xe8ff mem 0xfafff000-0xfaff,0xfaff8000-0xfaffbfff irq 17 at device 0.0 on pci2 re0: Using 1 MSI messages re0: Chip rev. 0x2800 re0: MAC rev. 0x miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 48:5b:39:d2:1d:89 re0: [FILTER] external PCI nic: re1: port 0xd800-0xd8ff mem 0xfbeffc00-0xfbeffcff irq 17 at device 0.0 on pci1 re1: Chip rev. 0x1000 re1: MAC rev. 0x miibus1: on re1 rgephy1: PHY 1 on miibus1 rgephy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re1: Ethernet address: 00:21:91:f4:5f:e4 re1: [FILTER] all that data i was posting here before (several months ago) and nothing changed since that time due to production state of the boxes i was forced finally to switch to external nics and to configure it with vlans and even to unplug the cable of the onboard nic since nic with plugged cable but without assigned ip address did begin flap (may be it's specific of the swith it plugged in, it is TP-Link TL-SG5426 but no other nic behaves this way) i have 7 boxes of this configuration and all 6 are running now on external nics if i can provide any debug/info/e.t.c. please let me know, i'd be happy it'd work at last :) -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
On Fri, Nov 12, 2010 at 09:07:59AM +0200, Zeus V Panchenko wrote: > Hi, > > Gabor Radnai (gabor.rad...@gmail.com) [10.11.11 23:22] wrote: > > pciconf: > > n...@pci0:0:20:0:class=0x068000 card=0x816a1043 chip=0x026910de rev=0xa3 > > hdr=0x00 > > vendor = 'NVIDIA Corporation' > > device = 'MCP51 Network Bus Enumerator' > > class = bridge > > r...@pci0:1:0:0:class=0x02 card=0x816810ec chip=0x816810ec rev=0x01 > > hdr=0x00 > > vendor = 'Realtek Semiconductor' > > device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)' > > class = network > > subclass = ethernet > > > > i have the same problem (i was writing here before, but still no idea) > with onboard (Realtek Gigabit Ethernet NIC(NDIS 6.0) > (RTL8168/8111/8111c)) nic while the same driver but another vendor > (D-Link DGE-528T Gigabit adaptor (dlg10086)) nic works fine ... > > the flapping of the realtek interface is so much drastic, that i was > forced to unplug the cable even on the ip less nic > Please be more specific for the issue. Your description is hard to narrow down possible cause. > i was sure it is the problem of the onboard rt nics ... > pciconf output of all re(4) controllers are useless because the vendor uses the same device id. Please show me the output of dmesg which will contain necessary information to identify your controller revision. > uname: > FreeBSD 8.1-STABLE #3 amd64 > > pciconf -lv: > r...@pci0:2:0:0: class=0x02 card=0x83a31043 chip=0x816810ec rev=0x03 > hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)' > class = network > subclass = ethernet > r...@pci0:1:0:0: class=0x02 card=0x43001186 chip=0x43001186 rev=0x10 > hdr=0x00 > vendor = 'D-Link System Inc' > device = 'Used on DGE-528T Gigabit adaptor (dlg10086)' > class = network > subclass = ethernet > > dmidecode: > Handle 0x0002, DMI type 2, 15 bytes > Base Board Information > Manufacturer: ASUSTeK Computer INC. > Product Name: AT5NM10-I > Version: Rev x.0x > Serial Number: MT7006K15200628 > Asset Tag: To Be Filled By O.E.M. > Features: > Board is a hosting board > Board is replaceable > Location In Chassis: To Be Filled By O.E.M. > Chassis Handle: 0x0003 > Type: Motherboard > Contained Object Handles: 0 > > Handle 0x0012, DMI type 8, 9 bytes > Port Connector Information > Internal Reference Designator: LAN > Internal Connector Type: None > External Reference Designator: LAN > External Connector Type: RJ-45 > Port Type: Network Port > > -- > Zeus V. Panchenko > IT Dpt., IBS ltd GMT+2 (EET) > ___ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
On Fri, Nov 12, 2010 at 10:18:40PM +0100, Gabor Radnai wrote: > Hi, > > I hope you are interested in inet section it looks like this (will able to > send the exact output only a bit later unfortunately as removed the card) : > inet 0.0.0.0 netmask 255.255.255.255 > This might be caused by dhclient(i.e. dhclient(8) failed to receive DHCP ACK). BTW, you still didn't show me the output of ifconfig re0 after UP the interface(i.e. ifconfig re0 up). > Thanks, > Gabor > > On Thu, Nov 11, 2010 at 10:26 PM, Pyun YongHyeon wrote: > > > On Thu, Nov 11, 2010 at 09:56:26PM +0100, Gabor Radnai wrote: > > > Hi, > > > > > > I have an Asus M2NPV-VM motherboard with integrated Nvidia MCP51 Gigabit > > > Ethernet NIC and > > > TP-Link TG-3468 PCIe network card which is using Realtek 8111 chip. > > > > > > I have problem with the re driver: the Nvidia network interface is > > working > > > properly but the other > > > though it seems recognized by OS I cannot use. Sporadically it remains > > down > > > and if it gets up then > > > does not get ip address via DHCP nor help if I set static ip address. Can > > > manipulate via ifconfig but > > > unreachable via IP. > > > > > > I replaced cable, interchanged cable working with Nvidia, restarted > > > switch/router but no luck so far. > > > Also using this nic in a Windows machine - it works. Using my Asus mob > > with > > > Ubuntu Live CD - card works. > > > > > > Can it be a driver bug or this type of chip is not supported by re > > driver? > > > > > > > Eh, you already know the answer, recognized by re(4) but does not > > work so it's a bug of re(4). Would you show me the output of > > ifconfig re0 after UP the interface(i.e. ifconfig re0 up). > > ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
Hi, I hope you are interested in inet section it looks like this (will able to send the exact output only a bit later unfortunately as removed the card) : inet 0.0.0.0 netmask 255.255.255.255 Thanks, Gabor On Thu, Nov 11, 2010 at 10:26 PM, Pyun YongHyeon wrote: > On Thu, Nov 11, 2010 at 09:56:26PM +0100, Gabor Radnai wrote: > > Hi, > > > > I have an Asus M2NPV-VM motherboard with integrated Nvidia MCP51 Gigabit > > Ethernet NIC and > > TP-Link TG-3468 PCIe network card which is using Realtek 8111 chip. > > > > I have problem with the re driver: the Nvidia network interface is > working > > properly but the other > > though it seems recognized by OS I cannot use. Sporadically it remains > down > > and if it gets up then > > does not get ip address via DHCP nor help if I set static ip address. Can > > manipulate via ifconfig but > > unreachable via IP. > > > > I replaced cable, interchanged cable working with Nvidia, restarted > > switch/router but no luck so far. > > Also using this nic in a Windows machine - it works. Using my Asus mob > with > > Ubuntu Live CD - card works. > > > > Can it be a driver bug or this type of chip is not supported by re > driver? > > > > Eh, you already know the answer, recognized by re(4) but does not > work so it's a bug of re(4). Would you show me the output of > ifconfig re0 after UP the interface(i.e. ifconfig re0 up). > ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
Hi, Gabor Radnai (gabor.rad...@gmail.com) [10.11.11 23:22] wrote: > pciconf: > n...@pci0:0:20:0:class=0x068000 card=0x816a1043 chip=0x026910de rev=0xa3 > hdr=0x00 > vendor = 'NVIDIA Corporation' > device = 'MCP51 Network Bus Enumerator' > class = bridge > r...@pci0:1:0:0:class=0x02 card=0x816810ec chip=0x816810ec rev=0x01 > hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)' > class = network > subclass = ethernet > i have the same problem (i was writing here before, but still no idea) with onboard (Realtek Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)) nic while the same driver but another vendor (D-Link DGE-528T Gigabit adaptor (dlg10086)) nic works fine ... the flapping of the realtek interface is so much drastic, that i was forced to unplug the cable even on the ip less nic i was sure it is the problem of the onboard rt nics ... uname: FreeBSD 8.1-STABLE #3 amd64 pciconf -lv: r...@pci0:2:0:0: class=0x02 card=0x83a31043 chip=0x816810ec rev=0x03 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)' class = network subclass = ethernet r...@pci0:1:0:0: class=0x02 card=0x43001186 chip=0x43001186 rev=0x10 hdr=0x00 vendor = 'D-Link System Inc' device = 'Used on DGE-528T Gigabit adaptor (dlg10086)' class = network subclass = ethernet dmidecode: Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: ASUSTeK Computer INC. Product Name: AT5NM10-I Version: Rev x.0x Serial Number: MT7006K15200628 Asset Tag: To Be Filled By O.E.M. Features: Board is a hosting board Board is replaceable Location In Chassis: To Be Filled By O.E.M. Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0012, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: LAN Internal Connector Type: None External Reference Designator: LAN External Connector Type: RJ-45 Port Type: Network Port -- Zeus V. Panchenko IT Dpt., IBS ltdGMT+2 (EET) ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Problem with re0
On Thu, Nov 11, 2010 at 09:56:26PM +0100, Gabor Radnai wrote: > Hi, > > I have an Asus M2NPV-VM motherboard with integrated Nvidia MCP51 Gigabit > Ethernet NIC and > TP-Link TG-3468 PCIe network card which is using Realtek 8111 chip. > > I have problem with the re driver: the Nvidia network interface is working > properly but the other > though it seems recognized by OS I cannot use. Sporadically it remains down > and if it gets up then > does not get ip address via DHCP nor help if I set static ip address. Can > manipulate via ifconfig but > unreachable via IP. > > I replaced cable, interchanged cable working with Nvidia, restarted > switch/router but no luck so far. > Also using this nic in a Windows machine - it works. Using my Asus mob with > Ubuntu Live CD - card works. > > Can it be a driver bug or this type of chip is not supported by re driver? > Eh, you already know the answer, recognized by re(4) but does not work so it's a bug of re(4). Would you show me the output of ifconfig re0 after UP the interface(i.e. ifconfig re0 up). ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Problem with re0
Hi, I have an Asus M2NPV-VM motherboard with integrated Nvidia MCP51 Gigabit Ethernet NIC and TP-Link TG-3468 PCIe network card which is using Realtek 8111 chip. I have problem with the re driver: the Nvidia network interface is working properly but the other though it seems recognized by OS I cannot use. Sporadically it remains down and if it gets up then does not get ip address via DHCP nor help if I set static ip address. Can manipulate via ifconfig but unreachable via IP. I replaced cable, interchanged cable working with Nvidia, restarted switch/router but no luck so far. Also using this nic in a Windows machine - it works. Using my Asus mob with Ubuntu Live CD - card works. Can it be a driver bug or this type of chip is not supported by re driver? Thanks, Gabor uname -v FreeBSD 8.1-RELEASE #0 r210200M: Wed Jul 21 14:21:18 CEST 2010 r...@neo.vx.sk:/usr/obj/usr/ src/sys/GENERIC pciconf: n...@pci0:0:20:0:class=0x068000 card=0x816a1043 chip=0x026910de rev=0xa3 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'MCP51 Network Bus Enumerator' class = bridge r...@pci0:1:0:0:class=0x02 card=0x816810ec chip=0x816810ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)' class = network subclass = ethernet rc.conf: ifconfig_nfe0="inet 192.168.0.200 netmask 255.255.255.0" defaultrouter="192.168.0.1" ifconfig_re0="DHCP" dmesg: nfe0: port 0xc800-0xc807 mem 0xfe02b000-0xfe02bfff irq 21 at device 20.0 on pci0 miibus1: on nfe0 e1000phy0: PHY 19 on miibus1 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto nfe0: Ethernet address: 00:1a:92:38:dc:95 nfe0: [FILTER] re0: port 0xac00-0xacff mem 0xfdbff000-0xfdbf irq 16 at device 0.0 on pci1 re0: Using 1 MSI messages re0: Chip rev. 0x3800 re0: MAC rev. 0x miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: d8:5d:4c:80:b4:88 re0: [FILTER] ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
