Fedora 9 x64 wireless problem on HP DV6815nr
 

Wireless won't work!!!

I have a HP dv6815nr 64-bit. Installed Fedora 9 64-bit.

Have tried more things than can recall, none have worked.

Output of lspci:

Output of lsusb:

Output of iwconfig:
Output of ifconfig:
NOTE: There used to be a "pan0" entry that did not have an IP - everything was zero pretty much. I did something and it disappeared.

Output of cat /etc/network/interfaces:

Output of cat /etc/resolv.conf:
Hopefully that is everything you need to know to help me! TIA.

Madwifi.org
 

I have the same laptop and got it working on Kubuntu 32-bit.
It does not seem to work on 64-bit :(
Just download this file: madwifi-nr-r3366+ar5007.tar.gz and follow the instructions. Good luck

I forgot: look at madwifi.org !!! TICKET 1679!!!

Or try this:

wget http://snapshots.madwifi.org/special...+ar5007.tar.gz

tar xfz madwifi-nr-r3366+ar5007.tar.gz

cd madwifi-nr-r3366+ar5007

make

sudo make install

sudo modprobe ath_pci
sudo reboot

Still struggling..
 

Thanks both of you for the responses.

I tried a few more things and decided to ditch 64-bit Fedora 9 - it just would NOT work.

I just finished installed Fedora 9 32-bit.

I downloaded the patched version (for the Atheros 5007 chipset) of the madwifi tar file and installed it using your instructions (make install, modprobe ath_pci, reboot), although I did have to issue the command:

yum install kernel-devel

first in order to get modprobe to work.

I have my wireless switch on the front of my laptop in the left position (I only mention this because with my previous HP laptop, the ON position for wireless was the opposite).

I left click on the internet connection icon next to my user name on the top toolbar and it recognizes my wireless connection, but when I click it to try to connect it attempts to connect then says

"Disconnected The network connection has been disconnected."

even though it never successfully connected.

I am completely at a loss as to what the problem is now.

Thanks in advance for any help.

oh crap, one step back...
 

I did:
/sbin/modprobe wlan_scan_sta

to try and fix the problem. Then I rebooted. Now, no wireless connections are showing up, although I still have my wired connection.

Also, after installing madwifi, I got a kernel bug warning upon reboot. Got it again after second reboot. Not sure what is causing it but perhaps it is related to my no wifi problem...

Try to set the switch to the right position. That is the side my switch has to stand and we have the same notebook!!! Notice that the led stays red and does not turn blue as the windows driver does!

if I type ifconfig as root I get the following output:
=====================================
root@linux-laptop:/home/robvr# ifconfig
ath0 Link encap:Ethernet HWaddr 00:1f:3a:56:09:e0
inet addr:10.0.0.4 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::21f:3aff:fe56:9e0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4268 errors:0 dropped:0 overruns:0 frame:0
TX packets:2217 errors:2 dropped:2 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4396014 (4.1 MB) TX bytes:326346 (318.6 KB)

eth0 Link encap:Ethernet HWaddr 00:1e:68:27:c3:53
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:220 Base address:0x6000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wifi0 Link encap:UNSPEC HWaddr 00-1F-3A-56-09-E0-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29342 errors:0 dropped:0 overruns:0 frame:1206
TX packets:2688 errors:0 dropped:2 overruns:0 carrier:0
collisions:0 txqueuelen:195
RX bytes:6389084 (6.0 MB) TX bytes:443894 (433.4 KB)
Interrupt:21
=============================

after installing madwifi you should get ath0 and wifi0.
I tried it both under Opensuse and Kubuntu and both times it works

Good luck

My output to ifconfig....
 

Here is my output to ifconfig. Maddwifi appears to have worked..

ath0 Link encap:Ethernet HWaddr 00:1F:3A:B9:A4:90
inet6 addr: fe80::21f:3aff:feb9:a490/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth0 Link encap:Ethernet HWaddr 00:1E:68:52:00:4E
inet addr:192.168.0.7 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::21e:68ff:fe52:4e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:19187 errors:0 dropped:0 overruns:0 frame:0
TX packets:14049 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:10146130 (9.6 MiB) TX bytes:2594428 (2.4 MiB)
Interrupt:20 Base address:0x8000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1876 errors:0 dropped:0 overruns:0 frame:0
TX packets:1876 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:114470 (111.7 KiB) TX bytes:114470 (111.7 KiB)

wifi0 Link encap:UNSPEC HWaddr 00-1F-3A-B9-A4-90-F4-AF-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6723 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:0 (0.0 b) TX bytes:309258 (302.0 KiB)
Interrupt:19

Hey! I just got connected to wifi! I did move the switch to the RIGHT. Oh my god it is finally working! Thank you!

Hopefully it doesn't do the constant disconnect thing some other people are experiencing...

Are you sure it is working via the wireless adapter?
I see no IP address for ath0 in your output?

I just got wifi working on my dv6815nr machine using Kubuntu Hardy Heron x64. This thread was key for me, thanks.

The trick was to use a different madwifi snapshot http://snapshots.madwifi.org/madwifi...0080604.tar.gz

I found another thread that was helpful getting the nvidia drivers installed: http://ubuntuforums.org/showpost.php...71&postcount=6

Good luck to all.

Thanks for the post!
 

Thanks for posting. It is good to know what the alternative to Fedora is. If I didn't get it working w/ Fedora 32 bit I was going to switch to Ubuntu.

But, I got it to work w/ Fedora 32 bit using the patched madwifi driver (someone made a version w/ the patch already included which is what I used). Two problems though:

1) I get a kernel error every time I boot up; it's a little alarming. Not sure what is causing this, but it doesn't affect my day to day usage of the computer which mainly is just surfing the internet.

2) If I let the computer go to sleep or move physical locations (where old network is no longer active) without shutting down first, I need to reboot in order to get the wireless working again. Also not sure why that is.

Once I do get on, I don't get dropped.

So all in all, it works pretty good. As far as I know it still doesn't work with Fedora x64 though.

Has anyone out there got the abc.com/tbs.com network television video players to work with Linux? This is my next challenge - not sure how far I'll get.

So for me, 32-bit Kubuntu worked with the madwifi snapshot linked to by Rijen (http://snapshots.madwifi.org/special...+ar5007.tar.gz), but 64-bit worked with the one I linked to (http://snapshots.madwifi.org/madwifi...0080604.tar.gz). I'd say there's a fair chance 64-bit Fedora would work with that one too.

New driver available
 

There is a new driver for 32+64bit
http://madwifi.org/ticket/1192

Installed it (OpenSuse 11.0 and Kubuntu 8.04 both 32bits) and it works fine

Ahh Thanks Rijen for posting this! My wireless has been dysfunctional for a while and this is probably the solution. Thanks.

Remember that you have to link in (modprobe) the madwifi module after every kernel update. Maybe that was the reason your wireless seemed to stop working.