Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I was wondering if anyone has ever got conky working as far as displaying the essid and signal strenth correctly when using the wl hybrid driver? I add the correct stuff and compiled conky properly but it will not pull the data for some reason and I am not sure why. I would write a custom script to do it if I knew where the wireless data was stored, if at all in the /sys or /proc file systems. Any ideas?
For some weird reason, wl seems to restrict this information to root. If you run conky as root you can see it properly, but as a normal user you can't. Of course that raises the question of do you really want to be running conky with root permissions.......
Ahhh that would explain why when I run iwconfig as a normal user I get no data. I have a question however and that is this something specific to the wl driver and do other wireless drivers allow normal user access or is this something thats built into the wireless stuff?
And to answer your question I do not want conkey to run with root permissions. Although I seam to not mind having xscreensaver have suid hacks to get sonar to work. Funny how my security priorities are messed up :P
I have a question however and that is this something specific to the wl driver and do other wireless drivers allow normal user access or is this something thats built into the wireless stuff?
The wl driver is the first one I've run into that requires root access for this kind of information. The only generally hidden information I've seen is the encryption key. Normal users can't see it through iwconfig, but root can. That makes some sense from a security standpoint. But the SSID and signal strenght? I just chalk that up to Broadcom's general incompetence.
Lol cool. Ohh I need to make a new posting somewhere that says that the driver no longer will compile with newer kernels due to it missing an include in one of the files. namely the src/wl/sys/wl_linux.c needs the #include<linux/sched.h>
Like the one that was released here a few days ago 220.127.116.11. Its odd that it should throw an error too since I have not updated my gcc or anything. Putting in that include fixed the issue tho and it compiles and works fine. I am just unsure what I should do with that information. I could write a patch but I dunno if broadcom accepts them?
Hmm do you know when they resolved this issue cause the last updated date on there site was back in September and I thought that I had downloaded it after then. Again I may have gotten the one they haven't fixed yet. When I get home I will re download it and try to compile if it has the same problem ill let you guys know here. I just hope this will be helpful to someone out there trying to get it to work. Or at least someone who updates there kernel every time a new one comes out like me :P.
Hmm do you know when they resolved this issue cause the last updated date on there site was back in September and I thought that I had downloaded it after then.
I think you've got the latest then. Last time this happened there was a separate patch file that had to be applied to the "source". At some point they rolled that into the regular driver and the patch file disappeared. Given how poorly Broadcom treats Linux, I wouldn't be surprised if they need to issue another patch.
I just hope this will be helpful to someone out there trying to get it to work. Or at least someone who updates there kernel every time a new one comes out like me :P.
I can pretty much guarantee that anything you do to keep the wl driver working on newer kernels would be VERY welcome. Well, it would be welcomed by users, I'm not so sure about Broadcom. I'd be surprised if they accept patches, but then again I've never asked them. What I do know is that their Linux driver development proceeds at a glacial pace, if at all. I wish they would take the Intel approach and put their shim into the kernel and then distribute a separate blob for firmware. You never see Intel cards fail because of a kernel version change.