Bug#648286: ITP: r8168 -- Realtek r8168 device driver for Linux (DKMS version)
>
> They can do that now, as we don't stop them from installing the version
> Realtek distributes.
And do not help either. So do we care?
> Users don't want alternative drivers; they just want a working driver
> installed automatically. The answer to 'this package is buggy' should
> not be 'never mind, try another one'.
Of course everyone wants one working hassle-free driver, preferably
free from blobs.
But there is a difference between buggy and not working.
Our work can stop when driver do not work and it may not be a good
time to put life on hold while troubleshooting problematic diver
knowing the remedy is out there. At least few of us prepared to do
such sacrifice every time driver didn't work for them.
>> Having another driver available for our users is not against our traditions.
>>
>> > The major reason for out-of-tree driver updates is to support new
>> > hardware on older kernel versions, but we already do that through
>> > backports.
>>
>> Right, but in this case we can't backport so at the moment for some
>> unfortunate owners of Realtek cards alternative driver is the only
>> option.
> [...]
>
> I just *did* backport r8169 from 3.0 into squeeze.
O, that's what you mean... Great, I'm looking forward to see the
feedback from people affected by the issue.
Cheers,
Dmitry.
Reply to: