Date: Wed, 11 Apr 2018 13:34:36 -0400 From: Allan Jude <allanjude@freebsd.org> To: freebsd-hackers@freebsd.org Subject: Re: Realtek re(4) driver Message-ID: <054b8c2c-7cd4-fdc2-d02c-d9d8e0ca3c20@freebsd.org> In-Reply-To: <CAA3ZYrCdBWi%2BXSge%2BYfDH73a5QpaK0oOVTABb2k16NA5xUx%2BdA@mail.gmail.com> References: <CAA3ZYrCdBWi%2BXSge%2BYfDH73a5QpaK0oOVTABb2k16NA5xUx%2BdA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --yBp3oDMkBl3y2uwa2ZFKcSsMY4CYm7JgO Content-Type: multipart/mixed; boundary="ixyI2VglhJV56xSMmShiSj8CMqDMiBCyM"; protected-headers="v1" From: Allan Jude <allanjude@freebsd.org> To: freebsd-hackers@freebsd.org Message-ID: <054b8c2c-7cd4-fdc2-d02c-d9d8e0ca3c20@freebsd.org> Subject: Re: Realtek re(4) driver References: <CAA3ZYrCdBWi+XSge+YfDH73a5QpaK0oOVTABb2k16NA5xUx+dA@mail.gmail.com> In-Reply-To: <CAA3ZYrCdBWi+XSge+YfDH73a5QpaK0oOVTABb2k16NA5xUx+dA@mail.gmail.com> --ixyI2VglhJV56xSMmShiSj8CMqDMiBCyM Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 2018-04-10 18:50, Dieter BSD wrote: > Multiple people have found that FreeBSD's re(4) driver for Realtek > Ethernet chips has problems. Something like a rcp(1) with another > FreeBSD box merely runs slower due to the stalls, but if the other end > has buggy network code and/or if the transfer is forced to use UDP > (Unreliable Data Protocol) data is lost. :-( >=20 > Rumor has it that Realtek has a driver that works properly with FreeBSD= =2E >=20 > FreeBSD's developers are apparently unable to: > a) Fix the existing FreeBSD re(4) device driver so that it works correc= tly. > b) Replace the existing FreeBSD re(4) device driver with Realtek's driv= er. > c) Make Realtek's driver into a port/pkg. > d) At least add a warning to the re(4) man page, with the URL for > Realtek's driver. >=20 > Therefore every user with Realtek Ethernet chips are forced to somehow > discover that Realtek has a working driver, then somehow obtain a copy > of this mythical driver, get it to compile and build a custom kernel. > They then need to write a test suite and verify that Realtek's driver > does in fact work properly for their applications. >=20 > I am currently suffering data loss due to this. Therefore I am > attempting to obtain a copy of the mythical Realtek device driver. > I managed to find >=20 >> http://www.realtek.com.tw/Downloads/downloadsView.aspx?Langid=3D4&PNid= =3D13&PFid=3D5&Level=3D5&Conn=3D4&DownTypeID=3D3&GetDown=3Dfalse >=20 > But it does not work for me. It has a listing for >=20 >> Description Version Update Time File Size Download Site 1 >> FreeBSD 7.x and 8.0 1.94 2017/9/15 93k Global >=20 > The machine with the re ports is running 10.3, hopefully the 7&8 code > will compile and work on 10. But the real problem is that clicking on > "Global" does not work. Some browsers do nothing. Firefox creates > a new window with http://www.realtek.com.tw/downloads/ > which is going backwards. I was expecting something like a tar file > containing the source code. >=20 > I also tried google, and emailing a FreeBSD user that runs the Realtek > driver, but both pointed me to the above non-working URL. I'm > told that seamonkey works, but... >=20 > So my question is: could someone please tell me the URL that points > *directly* to the mythical Realtek device driver? (without > the broken javascheist garbage) > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.o= rg" >=20 I think it would be useful to collect the 'pciconf -lv' output of the re(4) devices that have issues, so they can be differentiated from the ones that work fine. This would be the first step to getting a developer setup with a reliable reproduction platform, so the bug could be tracked down. --=20 Allan Jude --ixyI2VglhJV56xSMmShiSj8CMqDMiBCyM-- --yBp3oDMkBl3y2uwa2ZFKcSsMY4CYm7JgO Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJazkcwAAoJEBmVNT4SmAt+YlUP/3nCX999PiwnYQGZ2y5GCfeC HM1Re7ExSrprSYVxuHH6BnXK3/9//4B16wQzQjkLR9jIuPp148XYobvSoEzn9ERX mz8gibqc1dkT8XiI+fd8U96k6ZAOC2EsbPdg5sNaasx3YqIuRb1A1eFMClpA17Cs fB5Q5qDfGBN4/KX+vziQP9YoGDx+5F9ImJltV0uLoChxfxUSIBnymlQzJEf731xM nC5NZbdhgxPKevv4rWsja8pj+8TfUz/4A9FwgCqRVKWNkDL39sUMtUAzQyNCPBTM ZlaheDs9CNvjScq92ZGgJ//XL5daAsCeS6Z4tKpHiM5rIfpRbAD0Q9mJ0p9olQPI BrRHEQz8TUWs9/Y4Xe2x+EbeZBWzAecov9n1WKCKSQjoazyuxEn0rpCm9UX2Fy+z Jbxp2/t0nZe8Na831n1j6MfIq9aP3NLenPpcy3gAm5YC5jkX7+oyEa4VrqIu+jt+ eyFoCw5nYd2EleJCXVijyPuGplvyCC4lFsxTdUrxqHEdEgI59mo7iatjcqk3W4Qm 73H9+AiqGGEl/wK7rBQAhJ19R/d0ZYfyO5qKcTR3Av5XkUqMxeDoUZFwSoXi+BOP oyFtcLheDAI+D1Pe17m29ZnCnKUwVyeQ6Vcya8EnMoFr94HnUbw7OY6mkpbP2pUo 0Zb8EVdgZWqmcFTjMb2m =wbiV -----END PGP SIGNATURE----- --yBp3oDMkBl3y2uwa2ZFKcSsMY4CYm7JgO--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?054b8c2c-7cd4-fdc2-d02c-d9d8e0ca3c20>