> 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 DH
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 whet
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
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
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
> > > >
>
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 UR
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
> >
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
> > > Manufactu
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
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
> > Ver
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 followe
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 20
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
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
___
free
"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, on
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
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.
>
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 bein
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 "freebs
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
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 vers
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
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
> 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.
__
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.
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 ..
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
>
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'
> > dev
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 dhclie
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:
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
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 inter
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 ca
33 matches
Mail list logo
