Wireless adapter for compaq presario CQ40-616TU

sravuri · #1 13th December 2009, 02:00 PM

Hi,
Can you please provide me if there is a link to download wireless adapter for CQ40-616TU in fedora. I am able to work with basic ethernet i.e. wireline connection. In case wireless device my system fedora is not detecting the wireless device at all.

Thanks,
Suman

bbfuller · #2 13th December 2009, 02:39 PM

Hello sravuri

Welcome to the forum.

I think you are saying that you have a CQ40-616TU wireless adapter and want to get the drivers for it.

If that is so, it's the parts inside the adapter that will determine what we have to do.

If you run the command:

Code:

lspci

in a terminal window if it is a pci device, or:

Code:

lsusb

if it is USB and paste back the result, we'll see what is to be done.

sravuri · #3 13th December 2009, 02:54 PM

Thank you very much for the quick help.

Please see the command output below

[sravuri@localhost /]$ lsusb
Bus 006 Device 002: ID 15d9:0a37 Unknown Mouse
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 03f0:171d Hewlett-Packard Wireless (Bluetooth + WLAN) Interface [Integrated Module]
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 174f:5216 Syntek
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

bbfuller · #4 13th December 2009, 03:31 PM

Hello sravuri

The information we needed from that output is:

Quote:

03f0:171d

That's the manufacturers identity number for the device. Doing a google search on those numbers leads me to believe that it contains a broadcom 4310 device.

That's not an uncommon device and has been made to work using ndiswrapper.

Don't rush into that though. There is an easy way to do ndiswrapper for Fedora - well, perhaps not easy, but easier than the other ways.

Before we get into that though, I'd like to be as sure as I can that we are working in the right direction.

You will need a Windows XP driver for this device, if you have it on disk that is fine, if you haven't you should try looking on the HP web site for one. What we will need are the <some name>.inf and <same name.sys> files to work with ndiswrapper.
Let me know what files you find as they will help to assure us that we are approaching this correctly.

Usually, for broadcom cards they are bcmwl5.inf and sys, but sometimes bcmwl6.

The problem will be that yours is a dual purpose device, Bluetooth and WLAN. I've not seen anyone using one of these report success and it may be that ndiswrapper will not recognise a dual purpose device, or that its driver will be different and ndiswrapper will not be able to extract the parts it requires from it.

sravuri · #5 14th December 2009, 08:48 AM

Hi bbfuller,
I found wireless drivers for windows xp in HP site. Executable name is sp45222.exe. As it is windows executable, I was not not able to open that to see the content.

In some third party sites another there are seperate drivers for broadcom and intel. For broad com driver name is sp39912.exe.

I don't know whether this information helps you or not. Please let me know if I need to dig some more.

Thanks,
Suman

bbfuller · #6 14th December 2009, 09:18 AM

Hello Suman

The next thing to do is to see if we can extract whatever is in those exe files.

Sometimes those are what is called "self extracting executables". That is, you double click on them in Windows and they extract the files to a folder before offering to install them. Often you can interrupt that process when the install starts and get the files you need from where they have been extracted.

It might be worth trying that if we can't get at them in Linux.

The first thing to try though, is to put one of those files in a folder where there isn't too much other material.

Let's say on my machine, with a user of 'bbfuller' I might put it in the Downloads folder. Watch out in what follows, in Linux the location 'downloads' would be a completely different location to 'Downloads'.

So from a command line use:

Code:

cd /home/bbfuller/Downloads

adjust your command of course for name and location and then:

Code:

unzip -a sp45222.exe -d driver/

On some exe files that will extract the contents into a new folder called 'driver' in whichever folder you are working in.

Give it a try with both of those exe's and let me know what you find.

Bernard

sravuri · #7 14th December 2009, 10:38 AM

Hi Bernard,
I tried to unzip the file, but it did not help much.

[sravuri@localhost Download]$ unzip -a sp45222.exe -d driver
Archive: sp45222.exe
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of sp45222.exe or
sp45222.exe.zip, and cannot find sp45222.exe.ZIP, period.

Then copied this executable to window. I am able to see the files in the executable. I copied them into my fedora machine. Please see below. It has three files. I was able to open one file.

sravuri@localhost sp45222]$ l
total 7260
-r-xr-xr-x. 1 sravuri sravuri 2178 2009-09-01 12:21 Setup.ini
-r-xr-xr-x. 1 sravuri sravuri 1500856 2009-09-01 13:10 Setup.exe
-r-xr-xr-x. 1 sravuri sravuri 5925376 2009-09-01 13:11 hpqwa.msi
[sravuri@localhost sp45222]$ cat Setup.ini
��[GeneralOptions]
ProductCode=1032:{1061DF04-CF33-40B0-8360-D07C9BBEB122} 1040:{1061DF04-CF33-40B0-8360-D07C9BBEB122} 1033:{1061DF04-CF33-40B0-8360-D07C9BBEB122} 1041:{1061DF04-CF33-40B0-8360-D07C9BBEB122} 1049:{1061DF04-CF33-40B0-8360-D07C9BBEB122} 1042:{1061DF04-CF33-40B0-8360-D07C9BBEB122} 3082:{1061DF04-CF33-40B0-8360-D07C9BBEB122} 1035:{1061DF04-CF33-40B0-8360-D07C9BBEB122} 1043:{1061DF04-CF33-40B0-8360-D07C9BBEB122} 1051:{1061DF04-CF33-40B0-8360-D07C9BBEB122} 1028:{1061DF04-CF33-40B0-8360-D07C9BBEB122} 1036:{1061DF04-CF33-40B0-8360-D07C9BBEB122} 1044:{1061DF04-CF33-40B0-8360-D07C9BBEB122} 1060:{1061DF04-CF33-40B0-8360-D07C9BBEB122} 2052:{1061DF04-CF33-40B0-8360-D07C9BBEB122} 1029:{1061DF04-CF33-40B0-8360-D07C9BBEB122} 1045:{1061DF04-CF33-40B0-8360-D07C9BBEB122} 1053:{1061DF04-CF33-40B0-8360-D07C9BBEB122} 1030:{1061DF04-CF33-40B0-8360-D07C9BBEB122} 1038:{1061DF04-CF33-40B0-8360-D07C9BBEB122} 1046:{1061DF04-CF33-40B0-8360-D07C9BBEB122} 2070:{1061DF04-CF33-40B0-8360-D07C9BBEB122} 1031:{1061DF04-CF33-40B0-8360-D07C9BBEB122} 1055:{1061DF04-CF33-40B0-8360-D07C9BBEB122}

Thanks,
Suman

bbfuller · #8 14th December 2009, 08:47 PM

Hello Suman

We won't get anywhere with the files from the sp45222.exe file. That's a Microsoft installer file (msi) when it is unzipped.

Does the file sp39912.exe extract in the same way?

If it does then I suggest that the only possibility left is to look on the internet, possibly even on the broadcom site, and look for a driver for the 4310 chipset that has the component parts visible or will extract to reveal them.

Even then we may not get anywhere. It depends then if the driver will recognise what is in your device when it is integrated with the bluetooth device.

Looking through some of my past notes, I see that I talked to someone else about a stand alone 4310 and we eventually used this driver:

Quote:

Code:

http://ftp.us.dell.com/network/Dell_multi-device_A17_R174291.exe

If you need to use it then put it into a folder somewhere, from the command line 'cd' into that folder and use the command:

Code:

unzip -a Dell_multi-device_A17_R174291.exe -d driver/

That website address still downloads the driver here.

Bernard

sravuri · #9 16th December 2009, 03:44 AM

Hi Bernard,
I apologize that I have taken you in wrong direction. When I was doing little more investigation I found the following details.

02:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01)
Subsystem: Hewlett-Packard Company Device [103c:1508]
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at d8500000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>

Actually this was the name of device that was given in device list. I am trying to install wireless drivers as per the link below.

http://www.fedoraguide.info/index.ph...reless_Drivers

Please let me know whether I am going in correction direction as per broadcom installation. Thanks for your help on this.

Thanks,
Suman

bbfuller · #10 16th December 2009, 08:47 AM

Hello Suman

That howto is a little dated by now. It was designed for F11, but I suspect that the wireless parts for broadcom has been carried forward from F10.

Some things have changed.

In particular, there are three different versions of the 4312. The one you have, identified by:

Quote:

[14e4:4315]

is reckoned to be work in progress and may not work with the method listed in that howto.

The way listed below is reckoned to work with most 4312's and I hope it works with yours.

Quote:

To install the broadcom-wl rpm's from rpmfusion you need to know which kernel you are running.

Code:

uname -a

from a terminal will tell you that. My machine reports:

2.6.30.9-96.fc11.i686.PAE

Install the rpmfusion repository where drivers and programs that don't make it into the full Fedora distribution are made available.

In a terminal:

Code:

su -

The space and the minus sign are important. Without them you do not get full root control of your machine.

Then use the command:

Code:

rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm

With the repositories safely installed, use the command:

Code:

yum install kmod-wl-PAE

if the first command found a PAE kernel, if you do not have a PAE kernel use the command:

Code:

yum install kmod-wl

It should offer to install three files:

Quote:

kmod-wl-PAE-5.10.91.9.3-3.fc12.6.i686.rpm
kmod-wl-2.6.31.5-127.fc12.i686.PAE-5.10.91.9.3-3.fc12.6.i686.rpm
broadcom-wl-5.10.91.9.3-1.fc12.noarch.rpm

Those three if you specified the PAE kernel, the i586 version otherwise.

If it doesn't offer you the correct files cancel the installation and we'll think again.

That should get broadcom-wl installed.

At that stage, NetworkManager in the notification area of the panel to the left of the clock "may" begin to identify wireless networks when you left click on it.

If not, then in the same terminal window as you used above run:

Code:

service NetworkManager restart

That supposes you have an ordinary 32 bit install. If you have installed the 64 bit Fedora then the commands are the same as for the non-PAE kernel.

We may also need to blacklist the b43 module that is included in Fedora, but we'll worry about that if necessary.

Post back if you have any questions or problems.

Bernard

sravuri · #11 8th February 2010, 02:53 AM

I tried running "yum install kmod-wl-PAE", but I am getting some dependecy related issues.

###################################
[root@localhost ~]# yum install kmod-wl-PAE
Loaded plugins: refresh-packagekit
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package kmod-wl-PAE.i686 0:5.10.91.9-4.fc11.10 set to be updated
--> Processing Dependency: kmod-wl-2.6.30.10-105.2.13.fc11.i686.PAE >= 5.10.91.9-4.fc11.10 for package: kmod-wl-PAE-5.10.91.9-4.fc11.10.i686
--> Running transaction check
---> Package kmod-wl-2.6.30.10-105.2.13.fc11.i686.PAE.i686 0:5.10.91.9-4.fc11.10 set to be updated
--> Processing Dependency: kernel-uname-r = 2.6.30.10-105.2.13.fc11.i686.PAE for package: kmod-wl-2.6.30.10-105.2.13.fc11.i686.PAE-5.10.91.9-4.fc11.10.i686
--> Finished Dependency Resolution
kmod-wl-2.6.30.10-105.2.13.fc11.i686.PAE-5.10.91.9-4.fc11.10.i686 from rpmfusion-nonfree-updates has depsolving problems
--> Missing Dependency: kernel-uname-r = 2.6.30.10-105.2.13.fc11.i686.PAE is needed by package kmod-wl-2.6.30.10-105.2.13.fc11.i686.PAE-5.10.91.9-4.fc11.10.i686 (rpmfusion-nonfree-updates)
Error: Missing Dependency: kernel-uname-r = 2.6.30.10-105.2.13.fc11.i686.PAE is needed by package kmod-wl-2.6.30.10-105.2.13.fc11.i686.PAE-5.10.91.9-4.fc11.10.i686 (rpmfusion-nonfree-updates)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
#####################

Earlier my system was detecting wireless system, but yesterday I ran "yum update" to install softwares related to audio,vedio conferecning, then it is not working. Please help me to fix this problem.