You are not logged in.
Pages: 1
Hey Guys,
I downloaded and compiled the kernel 3.7.5 from kernel.org . All functionalities are working fine except two. I have listed them below
1) In conky, the wireless network strength option does display the % in number but as unk% . I checked conky forums and they have stated the problem is not with conky but with the kernel. This is not a show-stopper but I would like to know.
2) getcap functionality is not available. I use ext4 filesystem throughout and have disabled ext2,ext3 in the kernel config. My ext4 config below
CONFIG_EXT4_FS=y
CONFIG_EXT4_USE_FOR_EXT23=y
CONFIG_EXT4_FS_XATTR=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
I have enabled extended attributes for ext4 in the kernel. Please let me know where I am going wrong.
Offline
re: conky, are you talking about this:
${wireless_link_qual_perc <yourwirelessnetworknamehere>}
I laugh, yet the joke is on me
Offline
Yes, but in my conky the property is like this
${wireless_link_qual_perc wlan0}%
I mucked up the kernel config. will try your suggestion once I bring the kernel up
Offline
I just want to make sure of something. You haven't switched over to the new naming convention for network interfaces? The conky command is working fine with me, and I'm using 3.7.5 also. My wireless interface is now named wlp2s0. What does "ip link" show you?
I laugh, yet the joke is on me
Offline
Sorry, I was away for some days. I have not switched over to any new naming conventions(that I am aware of).I downloaded the kernel and compiled it. that's it. But here is the result of ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: sit0: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT
link/sit 0.0.0.0 brd 0.0.0.0
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT qlen 1000
link/ether 68:5d:43:2e:38:3f brd ff:ff:ff:ff:ff:ff
Offline
1. Probably you didn't select
networking -> wireless -> cfg80211 -> wireless extension compatibility
Offline
That did the trick , Thank you.
I just have another doubt though. The arch kernel has a lot of modules, but the one I compiled has no modules. I am just wondering, for example the ethernet driver was loaded as r8169 module but in my custom kernel, I have included it directly in the kernel. Is this the correct approach or is the arch kernel way the correct one ?
Offline
Either way is fine. By building what you need into the kernel, you don't have to have an initrd anymore, which can be nice, and you don't have all of the modules you don't need taking up drive space. Beyond that, it doesn't really matter.
The Arch kernel is built that way to be generic. It will load what it needs for whatever hardware it's running on.
Last edited by Scimmia (2013-02-21 16:28:54)
Offline
Pages: 1