Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
[gentoo-user] ethernet dont use kernel module
98 views
Skip to first unread message
Facundo Curti
Mar 8, 2014, 7:20:01 PM3/8/14
to
Hi all. I'm again :P (I'm becoming an annoying).
I have a realtek 8111F ethernet.
I boot from a live-usb, make an lspci -v and says ethernet uses r8169 module.
I compiled my kernel with this module, and when I start the system eth0 does not exist (Just lo), and a lspci -v says anything about modules.
Also I tried doing modprobe r8169 with no errors, but I still with out eth0.
So, any ideas why it is happening? :/
As always.. I hope make me understand, my english is no too good
Thank you list! Bytes! ;)
Canek Peláez Valdés
Mar 8, 2014, 8:00:02 PM3/8/14
to
dmesg | grep -i 8169
I'm pretty sure you will need some kind of firmware for your card. The
logs in dmesg will tell.
Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México
Facundo Curti
Mar 8, 2014, 11:30:01 PM3/8/14
to
This dont show anything ._.
Here my dmseg complete: bpaste.net/show/186667
And my .config from kernel: http://bpaste.net/show/186668
Canek Peláez Valdés
Mar 9, 2014, 12:00:01 AM3/9/14
to
On Sat, Mar 8, 2014 at 10:28 PM, Facundo Curti <facu....@gmail.com> wrote:
> This dont show anything ._.
>
> Here my dmseg complete: bpaste.net/show/186667
>
> And my .config from kernel: http://bpaste.net/show/186668
Please don't top-post.
> This dont show anything ._.
>
> Here my dmseg complete: bpaste.net/show/186667
>
> And my .config from kernel: http://bpaste.net/show/186668
You have the module compiled in the kernel. That should not be a
problem, but perhaps for debugging having it as a module would help
(to see what happens when you rmmod and modprobe it).
From the kernel source code, it seems that the module requires some
firmware. Do you have linux-firmware installed? If not, install it and
see if now gets recognized.
From the logs, the only acknowledgement of your network card I see are
the following lines:
[ 0.191153] pci 0000:03:00.0: [10ec:8168] type 00 class 0x020000
[ 0.191167] pci 0000:03:00.0: reg 10: [io 0xe000-0xe0ff]
[ 0.191193] pci 0000:03:00.0: reg 18: [mem 0xf0004000-0xf0004fff 64bit pref]
[ 0.191211] pci 0000:03:00.0: reg 20: [mem 0xf0000000-0xf0003fff 64bit pref]
[ 0.191279] pci 0000:03:00.0: supports D1 D2
[ 0.191280] pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.191305] pci 0000:03:00.0: System wakeup disabled by ACPI
That is weird, if it's a firmware problem, it should complain about it
in the logs.
From your system, what does lspci says?
Facundo Curti
Mar 9, 2014, 1:10:01 AM3/9/14
to
Sorry about top posting, My bad. Gmail jaja. I need to find a email client :P
Thank you for help. I'm trying to install firmware as you sugest. But now I have the problem, when I do modprobe r8168 it says:
Error: Could not insert 'r8168': Function not implemented
Canek Peláez Valdés
Mar 9, 2014, 1:20:01 AM3/9/14
to
On Sun, Mar 9, 2014 at 12:08 AM, Facundo Curti <facu....@gmail.com> wrote:
[snip]
> Thank you for help. I'm trying to install firmware as you sugest. But now I
> have the problem, when I do modprobe r8168 it says:
>
> Error: Could not insert 'r8168': Function not implemented
If I'm reading your kernel config correctly, you cannot modprobe
r8168; you have it compiled in the kernel. If you set it up as a
module (CONFIG_R8169=m), then I don't understand the "Function not
implemented" message.
[snip]
> Sorry about top posting, My bad. Gmail jaja. I need to find a email client
> :P
No prob.
> :P
> Thank you for help. I'm trying to install firmware as you sugest. But now I
> have the problem, when I do modprobe r8168 it says:
>
> Error: Could not insert 'r8168': Function not implemented
r8168; you have it compiled in the kernel. If you set it up as a
module (CONFIG_R8169=m), then I don't understand the "Function not
implemented" message.
Dale
Mar 9, 2014, 1:30:02 AM3/9/14
to
Facundo Curti wrote:
> But now I have the problem, when I do modprobe r8168 it says:
>
> Error: Could not insert 'r8168': Function not implemented
Typo maybe? It should be r8169.
> But now I have the problem, when I do modprobe r8168 it says:
>
> Error: Could not insert 'r8168': Function not implemented
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
Facundo Curti
Mar 9, 2014, 1:40:02 AM3/9/14
to
No, sorry. Was a mistake in the first place. The name of the module is r8168 :P
On Sun, Mar 9, 2014 at 12:08 AM, Facundo Curti <facu....@gmail.com> wrote:
[snip]
> Sorry about top posting, My bad. Gmail jaja. I need to find a email client
> :P
No prob.
> Thank you for help. I'm trying to install firmware as you sugest. But now I
> have the problem, when I do modprobe r8168 it says:
>
> Error: Could not insert 'r8168': Function not implemented
If I'm reading your kernel config correctly, you cannot modprobe
r8168; you have it compiled in the kernel. If you set it up as a
module (CONFIG_R8169=m), then I don't understand the "Function not
implemented" message.
Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México
So, how you can see, now I have a kernel module. But I still cannot see a eth0 device :/
at first I througth it could be a misconfig, but:
ifconfig -a: http://bpaste.net/show/186691/
dmesg | grep 8168:
[ 0.190299] pci 0000:03:00.0: [10ec:8168] type 00 class 0x020000 |
Any way modprobe r8168 still not work :/
Thank you! :)
Canek Peláez Valdés
Mar 9, 2014, 3:00:02 AM3/9/14
to
Well, that's progress, I suppose.
> So, how you can see, now I have a kernel module. But I still cannot see a eth0 device :/
If you are using systemd (and by your logs, I see you do), you will not have an eth0 device. You will have something like enp3s2 or similar, unless you used net.ifnames=0 in your kernel command line, or you followed the steps from [1] to disable the predictable network interface names.
I don't think that's the output from ifconfig. Could you please post it?
> dmesg | grep 8168:
>
> [ 0.190299] pci 0000:03:00.0: [10ec:8168] type 00 class 0x020000
>
> Any way modprobe r8168 still not work :/
I still don't recognize the error. What does lsmod | grep "816[89]" says?
Facundo Curti
Mar 9, 2014, 3:20:01 AM3/9/14
to
2014-03-09 3:59 GMT-03:00 Canek Peláez Valdés <can...@gmail.com>:
Well, that's progress, I suppose.If you are using systemd (and by your logs, I see you do), you will not have an eth0 device. You will have something like enp3s2 or similar, unless you used net.ifnames=0 in your kernel command line, or you followed the steps from [1] to disable the predictable network interface names.
> So, how you can see, now I have a kernel module. But I still cannot see a eth0 device :/
Yes, Im using systemd. Also I have a UEFI motherboard and a SDD disk.
I don't think that's the output from ifconfig. Could you please post it?
I still don't recognize the error. What does lsmod | grep "816[89]" says?
> dmesg | grep 8168:
>
> [ 0.190299] pci 0000:03:00.0: [10ec:8168] type 00 class 0x020000
>
> Any way modprobe r8168 still not work :/
It says:
[ 0.190299] pci 0000:03:00.0: [10ec:8168] type 00 class 0x020000
[ 0.818610] sd 0:0:0:0: [sda] 4096-byte physical blocks
Facundo Curti
Mar 9, 2014, 3:40:01 AM3/9/14
to
Sorry, bad paste.
I still don't recognize the error. What does lsmod | grep "816[89]" says?
It says:
[ 0.190299] pci 0000:03:00.0: [10ec:8168] type 00 class 0x020000
[ 0.816810] sd 0:0:0:0: [sda] 4096-byte physical blocks
^
I'm writing this by hand because I cant connect to lan. I need to boot from usb each time I want upload to bpaste lol
.
.The first time I discarded the last line because the matching was a time label.
Facundo Curti
Mar 9, 2014, 4:20:02 AM3/9/14
to
I have news... I boot from USB, and a lspci -v says:
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 09) Subsystem: ASUSTeK Computer Inc. P8H77-I Motherboard Flags: bus master, fast devsel, latency 0, IRQ 43 I/O ports at e000 [size=256] Memory at f0004000 (64-bit, prefetchable) [size=4K] Memory at f0000000 (64-bit, prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Count=4 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 4d-00-00-00-68-4c-e0-00 Kernel driver in use: r8169 Kernel modules: r8169
But when I boot normally (with my gentoo), lspci -v says:
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 09) Subsystem: ASUSTeK Computer Inc. P8H77-I Motherboard Flags: bus master, fast devsel, latency 0, IRQ 14 I/O ports at e000 [size=256] Memory at f0004000 (64-bit, prefetchable) [size=4K] Memory at f0000000 (64-bit, prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Count=4 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 4d-00-00-00-68-4c-e0-00 Kernel modules: r8168
> Typo maybe? It should be r8169.
You are rigth :P
So, we are back to beginning ._. I need load a module (r8169), and modprobe does not works :P
> If I'm reading your kernel config correctly, you cannot modprobe
> r8168; you have it compiled in the kernel. If you set it up as a
> module (CONFIG_R8169=m), then I don't understand the "Function not
> implemented" message.
> r8168; you have it compiled in the kernel. If you set it up as a
> module (CONFIG_R8169=m), then I don't understand the "Function not
> implemented" message.
I already compiled the kernel with r8169 as module as you suggested. But is the same :P
# modprobe r8169
modprobe: ERROR: could not insert 'r8169': Function not implemented
To install the firmware [1], I need to run a script "autorun.sh". When I do that, say me this:
I'm going crazzy lol
Thank you! Bytes! ;)
Canek Peláez Valdés
Mar 9, 2014, 4:30:02 AM3/9/14
to
First of all, you should not need to run any script. udev should
handle everything by itself.
> http://bpaste.net/show/186711/
Second of all:
could not open /proc/modules: No such file or directory
How is that even possible? In the first .config you posted, you had
CONFIG_MODULES unset, but I'm assuming you changed CONFIG_R8169 to 'm'
by running make menuconfig and going into the correct option, and that
you don't just edited your .config file. Right?
Because if you edited your .config by hand, that *CANNOT* result in
anything good, unless you know precisely what are you doing, and even
then most people would not recommend it.
It looks like you don't have kernel module support. Is that so?
What does the following command prints:
find /lib/modules -name "*r816*"
Regards.
handle everything by itself.
> http://bpaste.net/show/186711/
Second of all:
could not open /proc/modules: No such file or directory
How is that even possible? In the first .config you posted, you had
CONFIG_MODULES unset, but I'm assuming you changed CONFIG_R8169 to 'm'
by running make menuconfig and going into the correct option, and that
you don't just edited your .config file. Right?
Because if you edited your .config by hand, that *CANNOT* result in
anything good, unless you know precisely what are you doing, and even
then most people would not recommend it.
It looks like you don't have kernel module support. Is that so?
What does the following command prints:
find /lib/modules -name "*r816*"
Regards.
Facundo Curti
Mar 9, 2014, 4:40:02 AM3/9/14
to
2014-03-09 5:28 GMT-03:00 Canek Peláez Valdés <can...@gmail.com>:
First of all, you should not need to run any script. udev should
handle everything by itself.
> http://bpaste.net/show/186711/
Second of all:
could not open /proc/modules: No such file or directory
How is that even possible? In the first .config you posted, you had
CONFIG_MODULES unset, but I'm assuming you changed CONFIG_R8169 to 'm'
by running make menuconfig and going into the correct option, and that
you don't just edited your .config file. Right?
Because if you edited your .config by hand, that *CANNOT* result in
anything good, unless you know precisely what are you doing, and even
then most people would not recommend it.
Yes, of course :) I used make menuconfig, and i put modules ON.
It looks like you don't have kernel module support. Is that so?
I turned this on.
Now I made an emerge --sync, and emerge --update --newuse --deep world
And this give me an update of gentoo-sources (3.10 I had to 3.12). So I'm going to compile the new kernel to see if it works :P
What does the following command prints:
find /lib/modules -name "*r816*"
I post it in a few secs :) Please wait I will try first compiling the new kernel.
Canek Peláez Valdés
Mar 9, 2014, 4:50:01 AM3/9/14
to
support, you need to do "make modules_install" so the modules get
installed into /lib/modules/${KERNEL_VERSION}.
Matti Nykyri
Mar 9, 2014, 5:20:01 AM3/9/14
to
On Mar 9, 2014, at 10:43, Canek Peláez Valdés <can...@gmail.com> wrote:
> On Sun, Mar 9, 2014 at 2:38 AM, Facundo Curti <facu....@gmail.com> wrote:
>> 2014-03-09 5:28 GMT-03:00 Canek Peláez Valdés <can...@gmail.com>:
>>
>>> On Sun, Mar 9, 2014 at 2:18 AM, Facundo Curti <facu....@gmail.com>
>>> wrote:
>>>
>>> [snip]
>>>
>>> First of all, you should not need to run any script. udev should
>>> handle everything by itself.
>>>
>>>> http://bpaste.net/show/186711/
>>>
>>> Second of all:
>>>
>>> could not open /proc/modules: No such file or directory
>>>
>>> How is that even possible? In the first .config you posted, you had
>>> CONFIG_MODULES unset, but I'm assuming you changed CONFIG_R8169 to 'm'
>>> by running make menuconfig and going into the correct option, and that
>>> you don't just edited your .config file. Right?
>>>
>>> Because if you edited your .config by hand, that *CANNOT* result in
>>> anything good, unless you know precisely what are you doing, and even
>>> then most people would not recommend it.
>>>
>> Yes, of course :) I used make menuconfig, and i put modules ON.
>>
>>> It looks like you don't have kernel module support. Is that so?
I suggest you to try r8168 module. The realtek RTL8111/8168 chip is buggy. The in-kernel module r8169 failed to work with the chip. When i used r8169 and booted to windows or the other way around the network card was hard locked. It required a complete power out for a minute to reset the card. With r8168 module there is no problems. The code is here:
> On Sun, Mar 9, 2014 at 2:38 AM, Facundo Curti <facu....@gmail.com> wrote:
>> 2014-03-09 5:28 GMT-03:00 Canek Peláez Valdés <can...@gmail.com>:
>>
>>> On Sun, Mar 9, 2014 at 2:18 AM, Facundo Curti <facu....@gmail.com>
>>> wrote:
>>>
>>> [snip]
>>>
>>> First of all, you should not need to run any script. udev should
>>> handle everything by itself.
>>>
>>>> http://bpaste.net/show/186711/
>>>
>>> Second of all:
>>>
>>> could not open /proc/modules: No such file or directory
>>>
>>> How is that even possible? In the first .config you posted, you had
>>> CONFIG_MODULES unset, but I'm assuming you changed CONFIG_R8169 to 'm'
>>> by running make menuconfig and going into the correct option, and that
>>> you don't just edited your .config file. Right?
>>>
>>> Because if you edited your .config by hand, that *CANNOT* result in
>>> anything good, unless you know precisely what are you doing, and even
>>> then most people would not recommend it.
>>>
>> Yes, of course :) I used make menuconfig, and i put modules ON.
>>
>>> It looks like you don't have kernel module support. Is that so?
r8168.googlecode.com/files/r8168-8.036.00.tar.gz
I have also a nice ebuild for convenience... But you may test the card without it.
-M
Facundo Curti
Mar 9, 2014, 5:40:01 AM3/9/14
to
I suggest you to try r8168 module. The realtek RTL8111/8168 chip is buggy. The in-kernel module r8169 failed to work with the chip. When i used r8169 and booted to windows or the other way around the network card was hard locked. It required a complete power out for a minute to reset the card. With r8168 module there is no problems. The code is here:
r8168.googlecode.com/files/r8168-8.036.00.tar.gz
Broken link :P
I've fixed it!! Finally! But i have to say it... I'm stupid!! The problem was that I was booting from the wrong kernel.
I was booting from "kernel-gentoo", and I was installing the new kernel as "kernel-version-gentoo". So, no matter how much changes I made, the kernel was always the same :P
Sorry for make lose your time, was a stupid mistake from me :/ Thank you for patience!
Matti Nykyri
Mar 9, 2014, 5:50:02 AM3/9/14
to
Stroller
Mar 9, 2014, 11:10:02 AM3/9/14
to
On Sun, 9 March 2014, at 4:28 am, Facundo Curti <facu....@gmail.com> wrote:
This dont show anything ._.Here my dmseg complete: bpaste.net/show/186667And my .config from kernel: http://bpaste.net/show/186668
Hi there,
I'm sorry you're getting all these messages unrelated to your actual problem, but could I also ask you to post in plain-text (not HTML) and not to use pastebin sites.
When sending files like your dmseg and .config files, if they're too long to copy and paste into the body of the message, please send them as attachments. If you name them dmesg.txt and config.txt then people will be able to read them by double-clicking in a gui mail client.
Most pastebin services expire old pastes periodically (not to mention that pastebin services are hardly profitable, and close down all the time) whereas these mailing list messages are archived in multiple places and are referenced for years.
If you attach these files as plain text then they'll be archived, where they may be of help to other people with the same problem in the future.
Stroller.
0 new messages