|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| ARCHIVES - Wireless Networking Questions specific to wireless networking using SUSE Linux |
|
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Hello there, brand new linux user here trying to get wireless working on openSuse 10.3 (64bit)
I have tried both the ndiswrapper and the madwifi approaches and appear to not get any error when going through all the steps for both methods. In windows my card shows up as AR5007 but openSuse shows it as AR5006EG. What ever I try i end up at the network screen with the dreaded "BusID : 0000:0300.0 Unable to configure the network card because the kernel device is not present" uname -r 2.6.22.17-0.1-default ifconfig and iwconfig only show eth0 and lo, never any wlan or anything else. No idea what I'm doing, but have learned a bunch in my weeklong persuit of a wireless linux laptop. If anyone could help me solve this riddle I'd be eternally grateful. |
|
|||
|
Its possible you may have encountered a known bug with the madwifi driver.
There is a bug report on the madwifi for the AR5007EG that it is falsely identified as an AR5006EG (reference 11/17/07 22:59:11 comment in http://madwifi.org/ticket/1192). The work around ticket for AR5007EG is here: http://madwifi.org/ticket/1679 (fix is for 32-bit only - unfortunately, last I looked, there was no 64-bit support). Its possible the "schmolle1980" URL: (http://download.opensuse.org/reposit.../openSUSE_10.3) has the bug fix incorporated. I don't know, and unless someone chimes in with the answer, you will have to explore and find this out for yourself. I don't know much about this myself. .... and before I forget, WELCOME to suseforums.net |
|
|||
|
Quote:
So without using madwifi theoretically I should be able to use dniswrapper to get it work correct? Any ideas on how to figure out what I'm doing wrong? Reinstall openSuse and start fresh? Currently i have it loaded up with madwifi, if I remove madwifi in the software management section of Yast, does that unload the drivers and any thing that madwifi might have done to openSuse? |
|
|||
|
Some one else will need to chime in wrt NDISwrapper and if it will work. I've never used it.
IMHO re-installing openSUSE will solve nothing, as the problem will still be there. Removing madwifi should cause no problems. Just try. If a bunch of other things are going to be removed (at the same time), you will be warned in advance and will be able to cancel the attempt. |
|
|||
|
Quote:
http://download.opensuse.org/repositories/.../openSUSE_10.3/ ... and again, you could always try compiling the patch in yourself. |
|
|||
|
Quote:
I'm going through Package Selector In YaST and choose madwifi (0.9.3.99) and madwifi-kmp-defualt(trunk_r3630_20080515_2,6,22,5_31) to install then I get this: No valid solution found with just resolvables of best architecture. O Make a solver run with All possibliites This would invalidate atom: kernel-default-2.6.22.17-0.1.x86_64 O delete kernel-default What do I do or am running something else wrong. Again thanks for the help, I've been bashing my head against this for a week. |
|
|||
|
Quote:
Try going here instead: Code:
http://download.opensuse.org/repositories/home:/schmolle1980/openSUSE_10.3_update/ I see you have a 64-bit kernel, and I recall when I read about the patch it did not support an x86_64 architecture. .... Maybe thats been rectified? Maybe it hasn't .... But you can always try. |
|
|||
|
Quote:
after I type modprobe ath_pci it doesn't return anything. Is it suppose to? Under hardware information, a driver shows up there: Listing Active: Yes modprobe Yes modules modprobe ath_pci (ndiswrapper never listed drivers here) But in the network manager I still can't configure the wireless card and ifconfig only shows eth0 and lo Thanks again for your help, today I learned kernels are important
|
|
|||
|
Quote:
<span style="font-family:Courier New">lsmod | grep ath</span> Quote:
It would be nice, if someone who has this working (ie an AR5007eg that is misidentified as an AR5006eg), chimed in with a suggestion. I'm suspicious that the rpm with the madwifi kernel module does not address the bug. |
|
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|