LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   Using the Atheros wireless driver (https://www.linuxquestions.org/questions/linux-hardware-18/using-the-atheros-wireless-driver-593047/)

elliott678 12-27-2007 04:00 PM

Yes, you need root privileges to do that. It doesn't matter where you extract the driver.

apche93 12-28-2007 01:10 AM

Quote:

Originally Posted by elliott678 (Post 3003271)
Yes, you need root privileges to do that. It doesn't matter where you extract the driver.

here is what ive done (w/ root priveleges):

after extracting the downloaded 32-bit xp driver,

1. ndiswrapper ~/xp32/net5416.inf
Code:

installing net5416 ...
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64
forcing parameter MapRegisters from 256 to 64

2. ndiswrapper -l
Code:

net5416 : driver installed
        device (168C:001C) present (alternate driver: ath_pci)

3. modprobe ndiswrapper- nothing happens. it just skips to the next command...


Can you tell me what if anything went wrong?

elliott678 12-28-2007 05:40 AM

Did you blacklist the ath_pci driver so it isn't trying to load? What version of ndiswrapper are you running (ndiswrapper -v)?

Also, 168C:001C does tell me that it really is a 5007EG, so ndiswrapper is your only hope.

apche93 12-28-2007 09:55 AM

Quote:

Originally Posted by elliott678 (Post 3003734)
Did you blacklist the ath_pci driver so it isn't trying to load? What version of ndiswrapper are you running (ndiswrapper -v)?

Also, 168C:001C does tell me that it really is a 5007EG, so ndiswrapper is your only hope.


ndiswrapper -v
Code:

utils version: 1.9
driver filename:      /lib/modules/2.6.22-14-generic/ubuntu/misc/ndiswrapper/ndiswrapper.ko
version:        1.45
vermagic:      2.6.22-14-generic SMP mod_unload 586

wut do u mean by blacklisting it? and how?

elliott678 12-28-2007 10:24 AM

Blacklisting a driver keeps it from loading. I believe you blacklist drivers in Ubuntu by adding an entry to /etc/modprobe.d/blacklist, try adding something like this:
Code:

blacklist ath_pci
blacklist ath_hal


apche93 12-28-2007 01:32 PM

Quote:

Originally Posted by elliott678 (Post 3003938)
Blacklisting a driver keeps it from loading. I believe you blacklist drivers in Ubuntu by adding an entry to /etc/modprobe.d/blacklist, try adding something like this:
Code:

blacklist ath_pci
blacklist ath_hal


yes, i think its in my blacklist. here look:
Code:

# This file lists those modules which we don't want to be loaded by
# alias expansion, usually so some other driver will be loaded for the
# device instead.

# evbug is a debug tool that should be loaded explicitly
blacklist evbug

# these drivers are very simple, the HID drivers are usually preferred
blacklist usbmouse
blacklist usbkbd

# replaced by e100
blacklist eepro100

# replaced by tulip
blacklist de4x5

# causes no end of confusion by creating unexpected network interfaces
blacklist eth1394

# snd_intel8x0m can interfere with snd_intel8x0, doesn't seem to support much
# hardware on its own (Ubuntu bug #2011, #6810)
blacklist snd_intel8x0m

# causes failure to suspend on HP compaq nc6000 (Ubuntu: #10306)
blacklist i2c_i801
blacklist bcm43xx
blacklist bcm43xx
blacklist bcm43xx
blacklist bcm43xx
blacklist bcm43xx
blacklist ath_hal
blacklist ath_pci

see the blacklisting is in there. so still why isnt it working?

elliott678 12-28-2007 01:36 PM

What have you tried to get the wireless connection to start after the module was loaded? Does the wlan0 interface show up in 'ifconfig -a'?

apche93 12-28-2007 02:29 PM

Quote:

Originally Posted by elliott678 (Post 3004069)
What have you tried to get the wireless connection to start after the module was loaded? Does the wlan0 interface show up in 'ifconfig -a'?

no, it doesnt. ive typed in modprobe ndiswrapper as root though.

apche93 12-28-2007 02:29 PM

i only have eth0 and lo

elliott678 12-28-2007 02:59 PM

I think I left something out, remove the module then run 'ndiswrapper -m' then reload the module. I didn't have to do this on my system, but apparently it is necessary on Ubuntu.

apche93 12-28-2007 03:29 PM

Quote:

Originally Posted by elliott678 (Post 3004140)
I think I left something out, remove the module then run 'ndiswrapper -m' then reload the module. I didn't have to do this on my system, but apparently it is necessary on Ubuntu.

yea, after i remove the net5416.inf thing from the windows wirless menu (ndisgtk).
i typed in ndiswrapper -m into terminal i get:
Code:

module configuration already contains alias directive
im pretty sure i did remove the *.inf file i previously installed. wuts wrong?

elliott678 12-28-2007 03:34 PM

I'm not sure what is wrong, I'm not familiar with Ubuntu or ndisgtk. The steps I listed are exactly what I did to make it work for me.

apche93 12-29-2007 11:43 AM

Quote:

Originally Posted by elliott678 (Post 3004173)
I'm not sure what is wrong, I'm not familiar with Ubuntu or ndisgtk. The steps I listed are exactly what I did to make it work for me.

So, am i just left hopeless?


All times are GMT -5. The time now is 05:16 PM.