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