| View previous topic :: View next topic |
| Author |
Message |
egency
n00b
Joined: 27 Feb 2015
Posts: 3
|
 Posted: Fri Feb 27, 2015 7:13 am Post subject: Acer Aspire One ZG5 networking issues vanilla kernel. |
 |
|
Hi all, I'm having some (rather perplexing) trouble with my kernel config. The kernel boots fine, however when trying to list eth0 or wlan0 ifconfig tells me device does not exist. I'm fairly certain that I have the correct settings though. The ethernet driver is R8169, and the wifi driver is ath5k (checked both against another system with functional networking).
I haven't done this in a while (4 years give or take  ) so I can't remember all the details that are needed (I do know that I'm forgetting a lot of them). The kernel version I'm using is 3.17, lspci -k (on the working system) gives me:
| Code: | 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
Subsystem: Acer Incorporated [ALI] Device 015b
Kernel driver in use: r8169
03:00.0 Ethernet controller: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01)
Subsystem: Foxconn International, Inc. Device e008
Kernel driver in use: ath5k |
I forgot to check lspci while booted into my Gentoo system. 
Lastly, I don't know whether it's relevant, but I'm compiling everything into my kernel rather than using modules. My kernel isn't going to change much over time and I'm not exactly going to be using it one other machines, so I decided that having everything in-kernel would be less messy. 
Anyways, thanks to everyone taking the time to read this. |
|
| Back to top |
|
 |
charles17
Advocate
Joined: 02 Mar 2008
Posts: 3685
|
| Posted: Fri Feb 27, 2015 7:21 am Post subject: Re: Acer Aspire One ZG5 networking issues vanilla kernel. |
|
|
| egency wrote: | | Lastly, I don't know whether it's relevant, but I'm compiling everything into my kernel rather than using modules. |
The device drivers might better be built as modules. |
|
| Back to top |
|
|
egency
n00b
Joined: 27 Feb 2015
Posts: 3
|
| Posted: Fri Feb 27, 2015 7:30 am Post subject: |
|
|
| Okay, I'll try that. Might I ask why though? As far as I understand it (which is not spectacularly far) there shouldn't be much of a difference between having them build as modules and having them compiled into the kernel. |
|
| Back to top |
|
|
charles17
Advocate
Joined: 02 Mar 2008
Posts: 3685
|
| Posted: Fri Feb 27, 2015 8:01 am Post subject: |
|
|
| egency wrote: | | Okay, I'll try that. Might I ask why though? |
You didn't read cite_note-5 on that page?
For your problem in general, dmesg will tell you almost all you need. Assuming 02:00.0 and 03:00.0 were your actual devices you might try | Quote: | | $ dmesg | grep -i 'network interface\|80211\|dhcpcd\|02:00.0\|03:00.0' |
|
|
| Back to top |
|
|
egency
n00b
Joined: 27 Feb 2015
Posts: 3
|
| Posted: Fri Feb 27, 2015 6:22 pm Post subject: |
|
|
I overlooked the cite note. Thanks for drawing my attention to it. I didn't know that and it's quite a useful and interesting bit of information. It would explain quite a lot of my problem. I'll check what dmesg outputs and be back thanks.
[EDIT]:
Okay so as per your advice I checked the dmesg output and it turns out that in fact the interfaces exist, but systemd (I don't remember installing it) has decided to rename them to weird things like enp2s0 and stuff. I have not done extensive testing yet so I don't know whether it is the only problem, but a quick test showed that ethernet works without troubles, have yet to set up the wifi.
This is the output from dmesg:
| Code: | [ 0.254525] pci 0000:02:00.0: [10ec:8136] type 00 class 0x020000
[ 0.254571] pci 0000:02:00.0: reg 0x10: [io 0x3000-0x30ff]
[ 0.254621] pci 0000:02:00.0: reg 0x18: [mem 0x51010000-0x51010fff 64bit pref]
[ 0.254653] pci 0000:02:00.0: reg 0x20: [mem 0x51000000-0x5100ffff 64bit pref]
[ 0.254675] pci 0000:02:00.0: reg 0x30: [mem 0xfffe0000-0xffffffff pref]
[ 0.254803] pci 0000:02:00.0: supports D1 D2
[ 0.254809] pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.257412] pci 0000:03:00.0: [168c:001c] type 00 class 0x020000
[ 0.257527] pci 0000:03:00.0: reg 0x10: [mem 0x55200000-0x5520ffff 64bit]
[ 0.258064] pci 0000:03:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
[ 0.287367] cfg80211: Calling CRDA to update world regulatory domain
[ 0.353773] pci 0000:02:00.0: can't claim BAR 6 [mem 0xfffe0000-0xffffffff pref]: no compatible bridge window
[ 0.354855] pci 0000:02:00.0: BAR 6: assigned [mem 0x56300000-0x5631ffff pref]
[ 1.230223] r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 1.233828] r8169 0000:02:00.0: irq 28 for MSI/MSI-X
[ 1.234405] r8169 0000:02:00.0 eth0: RTL8102e at 0xf800e000, 00:23:8b:14:5a:6b, XID 04a00000 IRQ 28
[ 1.237881] ath5k 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 1.241427] ath5k 0000:03:00.0: registered as 'phy0'
[ 1.802946] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 7.729600] r8169 0000:02:00.0 enp2s0: renamed from eth0
[ 7.735587] systemd-udevd[1281]: renamed network interface eth0 to enp2s0
[ 7.740639] ath5k 0000:03:00.0 wlp3s0: renamed from wlan0
[ 7.745523] systemd-udevd[1286]: renamed network interface wlan0 to wlp3s0
[ 242.265260] r8169 0000:02:00.0 enp2s0: link down
[ 242.265304] r8169 0000:02:00.0 enp2s0: link down
[ 243.919305] r8169 0000:02:00.0 enp2s0: link up |
and the relevant output from lspci -k:
| Code: | 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
Subsystem: Acer Incorporated [ALI] Device 015b
Kernel driver in use: r8169
03:00.0 Ethernet controller: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01)
Subsystem: Foxconn International, Inc. Device e008
Kernel driver in use: ath5k |
I'll have look into the ASPM thingy, I didn't enable any power management in the kernel as it was technically my testing build (I generally build a kernel first to do the basics like booting and networking and then build on that). But that doesn't seem to be a problem at present.
So my next question is why do I have systemd? If I understood the Gentoo book correctly systemd was optional and Gentoo natively uses OpenRC? I'll have a look at how to prevent the renaming of my devices since I vaguely remember seeing something like that in the networking section of the Gentoo Handbook.
Thank you very much charles17 for your input, and pointing out the thing about the reasons to build drivers as modules. It would have taken me weeks to figure this out without your help.  |
|
| Back to top |
|
|
charles17
Advocate
Joined: 02 Mar 2008
Posts: 3685
|
| Posted: Sat Feb 28, 2015 7:10 am Post subject: |
|
|
| egency wrote: | | Okay so as per your advice I checked the dmesg output and it turns out that in fact the interfaces exist, but systemd (I don't remember installing it) has decided to rename them to weird things |
Don't be confused. That message has nothing to do with systemd as it comes from udev.
You could (in most cases) simply ignore what names been given to the network interfaces and use dhcpcd as your network manager. |
|
| Back to top |
|
|
|
Kernel & Hardware
