[driverloader] 64 bit DriverLoader on Pavilion zv5340us laptop running SuSE9.2 (x86_64)

Eric Herget eherget at bellsouth.net
Tue Jan 11 00:16:23 EST 2005

Thanks for all the responses.  I have gotten it to work.

Because the behavior of the wireless button above the keyboard on 32 bit 
Windows XP was for the button light to be on when wireless was turned 
on, I was expecting similar behavior.  I downloaded the public beta of 
Win XP 64 bit version and then loaded the 64bit Broadcom driver linked 
from the linuxant site on it.  In this case, the button light only turns 
on (well, flickers actually) when data is being transmitted/received.

So back in 64bit linux, and in a location where multiple access points 
broadcast their essid, I found that after pressing the button once I 
could get a list of servers/APs from the 'iwlist scan' command.  Once I 
had configured the wlan0 device to match my AP (which now broadcasts its 
essid), I could successfully connect.  The button light only comes on 
(flickers) as data is being transmitted/received.

A little more fiddling and setting the device activation to "if device 
present" now seems to bring the wireless lan up automatically if I'm 
within range of the configured access point - no pressing the button.

At this point it appears that the 64 bit driver just has different 
behavior with respect to the wireless lan button.  As you suggested, it 
may be a HP specific version of the broadcom driver on Win XP 32 bit 
which causes the button light to be on solid when turned on.


Linuxant support (Jonathan) wrote:
> Hi,
> please take a look at this web page :
> http://rfswitch.sourceforge.net/?page=laptop_matrix
> it is possible that you will find a Linux driver for your wireless 
> button and information on how to use it.
> It is also possible that you will have to wait for the HP specific 
> version of the Broadcom driver to obtain support for the wireless button.
> Regards,
> Jonathan
> Technical specialist / Linuxant
> www.linuxant.com
> support at linuxant.com
> eherget at bellsouth.net wrote:
>> I've got SuSE 9.2 (64bit) installed on a HP Pavilion zv5340us notebook 
>> - Athlon 64  3400+.  I've installed DriverLoader 2.23 and the 64 bit 
>> broadcom driver linked from the Linuxant website.  Everything appears 
>> to be installed correctly  - iwconfig and dldrconfig --info shows 
>> wlan0, etc.
>> The Pavilion zv5340us laptop has a button on it above the keyboard 
>> that turns on and off the wireless networking.  When it is turned on, 
>> the button has a blue light turned on behind it to show that wireless 
>> is turned on.  The problem I think I'm having is that I am unable to 
>> "turn on" the wireless networking with this button.
>> To shed some more light on the issue... For grins and giggles, I had 
>> previously installed the 32 bit SuSE 9.1 distribution on the laptop.  
>> In 32 bit mode, I was able to use ndiswrapper and some NDIS driver and 
>> could turn wireless networking on and off with the button above the 
>> keyboard.  In this case, however, I was unable to successfully 
>> configure the wireless network.  I didn't spend any time digging into 
>> why as I wasn't gonna run 32 bit linux on this laptop.  This driver I 
>> used in this case was the bcmwl5 driver, as I recall - don't recall 
>> what version, however.
>> So I'm looking for help resolving the issue with getting the 64 bit 
>> bcmwl564 driver working under DriverLoader on this particular laptop.  
>> Since I can't "turn on" the wireless networking with the button above 
>> the keyboard, but I do see the wlan0 device recognized, I am guessing 
>> that the button turns on and off the transmit/receive functionality of 
>> the wireless card to save battery drainage but that the rest of the 
>> wireless card is active since the device gets recognized and 
>> DriverLoader gets loaded.
>> I should probably mention that I am running SuSE9.2 with the kernel 
>> upgraded to the latest available from SuSE's update site - 
>> 2.6.8-24.10-default for x86_64.  I did try dl'ing the 2.6.10 kernel 
>> from kernel.org and compiling it using the same options as the 
>> 2.6.8-24.10 kernel, but the behavior is identical.
>> Any ideas?
>> Thanks in advance,
>> Eric
>> _______________________________________________
>> driverloader mailing list
>> driverloader at lists.linuxant.com
>> https://www.linuxant.com/mailman/listinfo/driverloader
> _______________________________________________
> driverloader mailing list
> driverloader at lists.linuxant.com
> https://www.linuxant.com/mailman/listinfo/driverloader

More information about the driverloader mailing list