On Wed, 14 Apr 2010 22:14:17 -0500 Ron Johnson <ron.l.john...@cox.net> wrote:
> On 2010-04-14 21:58, Stan Hoeppner wrote: > > Ron Johnson put forth on 4/14/2010 8:28 AM: > >> On 2010-04-13 22:50, Stan Hoeppner wrote: > >>> Hugo Vanwoerkom put forth on 4/13/2010 3:53 PM: > >> [snip] > >>> Either way, avoid onboard RealTek ethernet as it's not currently > >>> supported > >>> well by Debian. One might be able to make it work, but the > >>> process requires > >>> some serious hoop jumping. > >>> > >> Really? RealTek chips are as common as flies on horse poop, and > >> works perfectly for me. > > > > Check the list archives. Not long ago (couple months maybe) Debian > > released a 2.6.3x.x (not sure if it was Stable or Testing) kernel > > that omitted the RealTek firmware blob due to "non free" status of > > the code, thus bricking ethernet for quite a few users who upgraded > > to the new kernel via regular aptitude upgrades. Is this situation > > fixed with newer Debian kernels or are you manually telling the > > driver where to grab the firmware file on the root filesystem? Was > > this situation limited to just that one kernel release? > running 2.6.32-trunk on an Atom/Intel board and I'm not seeing any problems. RTL8111/8168B is what's listed via lspci I'm getting 1GB performance I do see the firmware messages: r8169 requesting rtl8169-1.fw so I'm not sure why it doesn't seem to be a problem. There is a disturbing trend on the part of HW manufacturers to have these customize firmware blobs, and that's not good. Brian -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100414203534.3b42f...@windy.deldotd.com
