installing d-link dwl-g510 in fedora core 4--problems

[dleon 0]

The x86_64 is for a 64 bit processor. Most likely, if you aren't sure, you have a 32 bit processor(i386). If you don't know, check online w/ the model of your CPU.

[OldUncleDick 0]

OK performed the following. What does it tell us?

 

[dick@localhost /]$ /sbin/modinfo ath_pci

filename: /lib/modules/2.6.13-1.1532_FC4/updates/net/ath_pci.ko

parm: xchanmode:Enable/disable extended channel mode

parm: outdoor:Enable/disable outdoor use

parm: countrycode:Override default country code

parmtype: xchanmode:int

parmtype: outdoor:int

parmtype: countrycode:int

license: Dual BSD/GPL

description: Support for Atheros 802.11 wireless LAN cards.

author: Errno Consulting, Sam Leffler

parm: ifname:Interface name prefix (default: ath)

parmtype: ifname:charp

srcversion: 10AFF40770E3A7E9826DCCC

alias: pci:v0000168Cd0000001Asv*sd*bc*sc*i*

alias: pci:v0000168Cd00000019sv*sd*bc*sc*i*

alias: pci:v0000168Cd00000018sv*sd*bc*sc*i*

alias: pci:v0000168Cd00000017sv*sd*bc*sc*i*

alias: pci:v0000168Cd00000016sv*sd*bc*sc*i*

alias: pci:v0000168Cd00000015sv*sd*bc*sc*i*

alias: pci:v0000168Cd00001014sv*sd*bc*sc*i*

alias: pci:v000010B7d00000013sv*sd*bc*sc*i*

alias: pci:v0000A727d00000013sv*sd*bc*sc*i*

alias: pci:v0000168Cd00000013sv*sd*bc*sc*i*

alias: pci:v0000168Cd00000012sv*sd*bc*sc*i*

alias: pci:v0000168Cd00000007sv*sd*bc*sc*i*

depends: ath_hal,wlan,ath_rate_sample

vermagic: 2.6.13-1.1532_FC4 gcc-4.0

 

[OldUncleDick 0]

I do note that the "filename: /lib/modules/2.6.13-1.1532_FC4/updates/net/ath_pci.ko" are the same as my kernel version when I did the "modinfo." I am sure it is a 32-bit processor. I must have grabbed the wrong driver in the rpm list.

[danleff 0]

I just installed FC4 on my sata drive and also installed madwifi.

 

I am posting from my wireless card now.

 

Give me a little bit and I will post a link to my web page article.

 

What I essentually found is that you need the kernel source installed. You are also probably correct, you downloaded the wrong package(s) and downloaded only one of the two packages needed.

 

You can install the kernel sources from up2date.

 

Try uninstalling your current version by doing as root user, in a console;

 

rpm -e madwifi

 

You need both the madwifi-0.9.6.0-18.rhfc4.at.i386.rpm and the madwifi-kmdl-2.6.13-1.1532_FC4-0.9.6.0-18.rhfc4.at.i686.rpm packages.

 

The package that you have is for 64 bit processors, if that is what you have (madwifi-kmdl-2.6.13-1.1532_FC4-0.9.6.0-18.rhfc4.at.x86_64.rpm.

 

I'll try to write a little how-to.

 

 

[danleff 0]

Here is a rough draft of how I did it.

 

The important thing to note, is that you need both packages;

 

madwifi-kmdl-2.6.13-1.1532_FC4-0.9.6.0-18.rhfc4.at.i686.rpm

madwifi-0.9.6.0-18.rhfc4.at.i386.rpm

[Heffo_J 0]

Thank you all. I have spent weeks and weeks trying to get my D-Link G650 working and this thread and the thorough instructions from the moderator have been very helpful. Moth other forums I have visited have not taken the trouble to explain all the detail.

 

Thank you, thank you.

 

John

[OldUncleDick 0]

danleff,

 

Thank you for posting a most useful report. I have beeen off-line a few days...and will try the suggested steps asap.

 

Again, thank you.

 

rlm

[OldUncleDick 0]

Y'know, it seems like there is a trap in every step. I tried the steps you posted in your link, and stumbled on what everyone (but me, apparently) understands as "you will also need to pre-install the corutils package before using yum, before doing the actual installation."

 

OK. WTF does "pre-install the corutils" mean?

[OldUncleDick 0]

OK. Made a little progress. Madwifi apparently installed. response from /sbin/iwconfig:

[dick@localhost /]$ /sbin/iwconfig

lo no wireless extensions.

 

eth0 no wireless extensions.

 

Warning: Driver for device ath0 has been compiled with version 18

of Wireless Extension, while this program supports up to version 17.

Some things may be broken...

 

ath0 IEEE 802.11 ESSID:"" Nickname:"localhost.localdomain"

Mode:Managed Frequency:2.427 GHz Access Point: 00:00:00:00:00:00

Bit Rate:1 Mb/s Tx-Power:18 dBm Sensitivity=0/3

Retry:off RTS thr:off Fragment thr:off

Power Management:off

Link Quality=0/94 Signal level=-95 dBm Noise level=-95 dBm

Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0

Tx excessive retries:0 Invalid misc:0 Missed beacon:0

 

sit0 no wireless extensions.

------------------------

When try to activate ath0, get: Error for wireless request "Set Bit Rate" (8B20) :

SET failed on device ath0 ; Invalid argument.

 

 

Any ideas?

[danleff 0]

OK, your almost there. You are using a router?

 

If so, is the router using WEP and do you know the essid of the router?

 

What command are you suing to bring up the card? ifup, dhclient?

 

Type in a terminal window;

 

/sbin/iwlist wlan0 scan

 

...and post the results. I'm going to amend my article with more instructions.

 

[OldUncleDick 0]

Using a router--yes. Router using WEP and I entered that key (10 digit). ESSID is entered.

Results:

[dick@localhost ~]$ /sbin/iwlist wlan0 scan

wlan0 Interface doesn't support scanning.

[danleff 0]

Oops! To many late night posts, or early am ones.

 

Try;

 

/sbin/iwlist ath0 scan

 

How are you adding the values for the essid and WEP key?

 

/sbin/iwconfig ath0 mode managed key xxxxxxxxx channel 6 essid <your essid value>

 

Where xxxxxxxxxx is the WEP key and <your essid value> is actually the essid name.

 

Then see if you get an access point by running iwconfig ath0.

 

If yes (there are numerical/letter values for the access point) then...

 

Once you do that, how are you trying to bring up the card?

 

ifup ath0?

 

dhclient ath0?

[OldUncleDick 0]

[dick@localhost ~]$ /sbin/iwlist ath0 scan

ath0 Interface doesn't support scanning.

 

Ideas? I went as root and nothing changed. Curious.

[OldUncleDick 0]

OK. Back after the holiday. Reinstalled Fedora 4 and am running version 2.6.14.1.1637_FC4. Have downloaded the needed madwifi files per your white paper. Now the install for 1.9.6.0-18 fails for lack of key. This is a new problem. ideas? thx.

[danleff 0]

Assuming that you are using the same source for the files, run the following as root user in a console;

 

rpm --import http://atrpms.net/RPM-GPG-KEY.atrpms

 

This assumes that you have a working internet connection without the wireless.

 

Then try installing the packages.

[zparihar 0]

Hey guys,

 

Which package does wlanconfig belong too?

 

I'm using Fedora Core 4.

 

 

I've already downloaded

 

Madwifi and the appropriate kernel module for my kernel from Livna.org via yum.

 

I wanted to run these steps - by dleon:

 

6. Type wlanconfig ath0 create wlandev wifi0 wlanmode sta

7. Type iwconfig ath0 essid ANY

8. Type ifconfig ath0 up

9. Type dhclient

 

 

but couldn't find wlanconfig... did a 'locate wlanconfig' and did a find / -name wlanconfig

 

I know its not in my comp.

 

already did 'modprobe ath_pci' and its loaded (lsmod)

 

Anyone know where i can find 'wlanconfig'?

 

 

Thanks,

 

Zubin

[Heffo_J 0]

Here is the simple way I got my card Athros chipped card to work in FC4:

 

1) check the current kernel details in terminal by running "uname -a". Write down what is shown.

 

2) Go to ATrpm (http://atrpms.net/dist/fc4/madwifi/) in Firefox 1.07 (or later) and download madwifi-0.9.6.0-18.rhfc4.at.i386.rpm by clicking on the link (I'm not running a 64bit processor). When this is run in the Firefox download manager you get the option to "open with" and in the drop down box "install packages (default)". Hit OK. This will install this rpm. Do this before you proceed to the next step.

 

3) Now search the ATrpm Fedora driver list (http://atrpms.net/dist/fc4/madwifi/) and make sure you get the correct rpm to match your kernel details you wrote down in Step 1) above. In my case "uname -a" told me that my kernal is 2.6.14-1.1644_FC4. I do not have a 64bit processor running so I selected this rpm: madwifi-kmdl-2.6.14-1.1644_FC4-0.9.6.0-18.rhfc4.at.i686.rpm. Make sure you click on the "madwifi-kmdl-" rpm that matches both your your processor and kernel.

 

4) Click on the correct rpm as described in 3) above and Firefox will offer to install it. Click OK.

 

5) Reboot your computer.

 

6) Go to Desktop in your FC4 top panel. Select "System settings" then "Network". Type in your root password when asked and you will be taken to graphic menu that will list your network cards. In my case my laptop has an ethernet card and the wireless card. Until I installed Madwifi as described above the wireless card was not listed.

 

7) The wireless card is now listed under "Devices", in my case under the ethernet card. Check the box to the left next of the wireless card and press the "Activate" button.

 

8) When you go to leave the network menu you will be asked to save the new settings. Press OK. You're almost there.

 

9) Your card will still not be working. Restart your computer.

 

10) Bingo! It works.

 

I hope this helps others. I'm no geek but *I* got it to work. (With a lot of help from the replies in this thread above).

 

Regards

John

[OldUncleDick 0]

OK. Here is what I get when I try to activate ath0:

 

Error for wireless request "Set Bit Rate" (8B20) :

SET failed on device ath0 ; Invalid argument.

 

Determining IP information for ath0...

 

...and the determine fails. Am I close yet?

[gu3st 0]

I too am trying to install this same card, I have the H/W version B1 and the F/Ware is 2.11 (apparently supported). I've tryed many ideas, using yum and building source packages and was going to use a few RPM's if I could find the correct one/had all dependencys. Can someone give me a super-laymans terms guide on how-to do this. I'm currently (temporarily) connecting thru an iBook using Connection Sharing (wired)

[gu3st 0]

Solved, used an above guide that tells to use the i686 and the i386 RPM's, rebooted and it worked

[danleff 0]

Good job! Just as an aside, I just installed Linspire 5 on my wife's system, after she got a load of virus infections off a mailing list that she is on. This exact same card worked out of the box using DSL. I forgot that she had this card in her system!

 

A new Linux convert!

 

Clearly, the new distro versions that are coming out are making progress with wireless cards.

[euphorikdesigns 0]

Hey I have a question. I configured my D-link DWL-650 card and it works with ndiswrapper, but it has a problem finding my router. Gives me the error when I enter dmesg:

wlan0: no IPv6 routers present

I'm using FC4, the light on the card blinks, the kernels updated, and it's a D-Link AirPlus Xtreme G Wireless Router. If someone could help that would be great!

[danleff 0]

That error is common and does not have anything to do with your router. Ignore this for now.

 

When you say that your kernel is updated, do you mean that you updated the kernel before or after installing ndiswrapper? If after, this will not work. you need to reconfigure ndiswrapper for the new kernel.

 

If before, is the kernel source installed?

 

What you look for in dmesg, is if the card is up during boot. You will see an id for the card and some text saying that the card is working.

 

Do you have ndiswrapper running as a module on boot?

 

Do you have your essid and wep key (if you have one) configured, so the card can connect to the router?

 

Taks a look at the ndiswrapper Fedora page for specific instructions.

 

Also, take a look at my page on the subject.

 

 

[euphorikdesigns 0]

The source is installed and this was before I installed anything. I found out the problem is setting the ESSID

iwconfig wlan0 essid ''

I can connect to my network when using

iwconfig wlan0 mode ad-hoc

 

wlan0 IEEE 802.11b ESSID:""

Mode:Ad-Hoc Frequency:2.412 GHz Cell: 00:00:00:00:00:00

Bit Rate:11 Mb/s Tx-Power:20 dBm Sensitivity=0/3

RTS thr:2432 B Fragment thr:2432 B

Encryption key:off

Power Management:off

Link Quality:0 Signal level:0 Noise level:0

Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0

Tx excessive retries:0 Invalid misc:0 Missed beacon:0

 

Also I can't get it to boot on startup.

 

Thanks for helping.

[danleff 0]

Good! You found that you needed to set the essid.

 

Quote:

Also I can't get it to boot on startup.

 

I found the same thing. Fedora is quirky about this. I had to set a small script file to use to invoke the card and it's settings, as I could not get it to come up at boot. Then, you can make a small icon to bring up the card. It was a hit and miss thing.

 

See my example here.