| 1 |
On Sun, Mar 10, 2013 at 12:42 PM, Daniel Wagener <stelf@×××.net> wrote: |
| 2 |
> On Sun, 10 Mar 2013 12:36:55 -0600 |
| 3 |
> Canek Peláez Valdés <caneko@×××××.com> wrote: |
| 4 |
> |
| 5 |
>> On Sun, Mar 10, 2013 at 12:28 PM, Daniel Wagener <stelf@×××.net> wrote: |
| 6 |
>> > Hello, |
| 7 |
>> > |
| 8 |
>> > I ran into some trouble about an hour ago… |
| 9 |
>> > |
| 10 |
>> > My workstation has an onboard Realtek Ethernet which only works with the r8168 driver. |
| 11 |
>> > Unfortunately, this driver is not in the kernel, but available to be compiled as a kernel module. (I guess because of som patents) |
| 12 |
>> > That worked for quite some time, until i thought "hey, you got an hour of time, your workstation is still on 3.7.4, why don't you just upgrade it to 3.8.2?" |
| 13 |
>> > So I did, only to find out that Linus and his friends changed the way drivers are initialized… (__devinit got unsupported for example) |
| 14 |
>> > |
| 15 |
>> > Of course, the guys who wrote that r8169 have not changed their code yet. |
| 16 |
>> > |
| 17 |
>> > tl;dr: |
| 18 |
>> > My network is broken since 3.8.0. |
| 19 |
>> > |
| 20 |
>> > So for an immediate fix I am emerging 3.7.10 (since emerge --depclean deleted the Kernel source when it found the source fo 3.7.8 which got removed as soon as 3.8.2 was emerged…) to get it working again. |
| 21 |
>> > For the long run im thinking of buying a PCI(e) card with Kernel support. |
| 22 |
>> > Or maybe, if I find some time I will fix the driver myself. |
| 23 |
>> > |
| 24 |
>> > My question now is: |
| 25 |
>> > Who should I talk to so something like this does not happen again? |
| 26 |
>> > A certain gentoo dev, who could issue warnings on emerging kernels, something like excerpts from the changelog? |
| 27 |
>> > Myself, because I missed what I described above? |
| 28 |
>> > The devs of the r8169? |
| 29 |
>> > Linus & co for breaking things? |
| 30 |
>> > Myself bcause I forgot something else? |
| 31 |
>> > Realtek? |
| 32 |
>> > Or someone completely different? |
| 33 |
>> |
| 34 |
>> Mmmh. What sources do you use? In vanilla-sources-3.8.2, there is a |
| 35 |
>> r8169 driver: |
| 36 |
>> |
| 37 |
>> ./drivers/net/ethernet/realtek/r8169.c |
| 38 |
>> |
| 39 |
>> config R8169 |
| 40 |
>> tristate "Realtek 8169 gigabit ethernet support" |
| 41 |
>> |
| 42 |
>> Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter. |
| 43 |
>> |
| 44 |
>> To compile this driver as a module, choose M here: the module |
| 45 |
>> will be called r8169. This is recommended. |
| 46 |
>> |
| 47 |
>> What is more, I'm using that driver. It works without a problem. Do |
| 48 |
>> you use a different driver with the same name? |
| 49 |
>> |
| 50 |
>> Regards. |
| 51 |
> |
| 52 |
> |
| 53 |
> oh great, so I actually mixed it up… |
| 54 |
> the 8169 is in the Kernel yes, but what i need is the 8168 |
| 55 |
|
| 56 |
The in-kernel drive (supposedly) supports 8168: |
| 57 |
|
| 58 |
r8169.c: RealTek 8169/8168/8101 ethernet driver. |
| 59 |
|
| 60 |
Have you tried it recently? When drivers are in-kernel, they usually |
| 61 |
are improved greatly between versions, perhaps it works now with your |
| 62 |
card if it didn't before. |
| 63 |
|
| 64 |
Otherwise, I don't know about your problem. |
| 65 |
|
| 66 |
Regards. |
| 67 |
-- |
| 68 |
Canek Peláez Valdés |
| 69 |
Posgrado en Ciencia e Ingeniería de la Computación |
| 70 |
Universidad Nacional Autónoma de México |
Archives