LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This 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.

Notices

Reply
 
Search this Thread
Old 01-04-2010, 05:37 PM   #1
exvor
Senior Member
 
Registered: Jul 2004
Location: Phoenix, Arizona
Distribution: LFS-Version SVN-20091202, Arch 2009.08
Posts: 1,496

Rep: Reputation: 68
Conky and wl.ko


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?
 
Old 01-05-2010, 02:19 PM   #2
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,791
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
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.......
 
1 members found this post helpful.
Old 01-05-2010, 10:30 PM   #3
exvor
Senior Member
 
Registered: Jul 2004
Location: Phoenix, Arizona
Distribution: LFS-Version SVN-20091202, Arch 2009.08
Posts: 1,496

Original Poster
Rep: Reputation: 68
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
 
Old 01-06-2010, 08:26 AM   #4
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,791
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
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.
 
Old 01-06-2010, 04:24 PM   #5
exvor
Senior Member
 
Registered: Jul 2004
Location: Phoenix, Arizona
Distribution: LFS-Version SVN-20091202, Arch 2009.08
Posts: 1,496

Original Poster
Rep: Reputation: 68
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>
 
Old 01-06-2010, 05:18 PM   #6
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,791
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
What kernel are you trying to compile against? I know they had a problem with 2.6.29, but I thought they had it fixed.
 
Old 01-06-2010, 08:39 PM   #7
exvor
Senior Member
 
Registered: Jul 2004
Location: Phoenix, Arizona
Distribution: LFS-Version SVN-20091202, Arch 2009.08
Posts: 1,496

Original Poster
Rep: Reputation: 68
Like the one that was released here a few days ago 2.6.32.3. 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.

Last edited by exvor; 01-06-2010 at 08:42 PM.
 
Old 01-07-2010, 08:28 AM   #8
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,791
Blog Entries: 1

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
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.

Quote:
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.
 
Old 01-07-2010, 08:16 PM   #9
exvor
Senior Member
 
Registered: Jul 2004
Location: Phoenix, Arizona
Distribution: LFS-Version SVN-20091202, Arch 2009.08
Posts: 1,496

Original Poster
Rep: Reputation: 68
Yeah the patch file would just be to add a include to one of the source files. Its a very minimal change but kinda hard to track down if you don't know anything about c or programming.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
conky question: passing conky-variable to shell-script zlin50 Linux - Software 2 12-29-2012 07:47 PM
Help with Conky Smitty67 Slackware 24 07-12-2009 05:30 PM
Need Help with Conky slickhare Linux - Newbie 7 05-06-2009 03:15 AM
Conky on Suse 10.0 - *** buffer overflow detected *** conky terminated Slidex Linux - Software 1 03-17-2006 12:50 PM
conky help ahh_dee Linux - Software 2 10-28-2005 02:40 PM


All times are GMT -5. The time now is 09:33 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration