Go Back   openSUSE Forums > Archives > SF Archives > ARCHIVES - Network/Internet > ARCHIVES - Wireless Networking
Forums FAQ Members List Search Today's Posts Mark Forums Read


ARCHIVES - Wireless Networking Questions specific to wireless networking using SUSE Linux

 
Page 1 of 2 1 2
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 14-May-2008, 17:03
johnTD
Guest
 
Posts: n/a
Default

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.
  #2 (permalink)  
Old 14-May-2008, 17:33
oldcpu
Guest
 
Posts: n/a
Default

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
  #3 (permalink)  
Old 14-May-2008, 17:50
johnTD
Guest
 
Posts: n/a
Default

Quote:
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
[/b]

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?
  #4 (permalink)  
Old 15-May-2008, 00:02
oldcpu
Guest
 
Posts: n/a
Default

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.
  #5 (permalink)  
Old 15-May-2008, 18:14
johnTD
Guest
 
Posts: n/a
Default

Anyone else out there have any ideas?
  #6 (permalink)  
Old 15-May-2008, 23:40
oldcpu
Guest
 
Posts: n/a
Default

Quote:
Anyone else out there have any ideas?[/b]
Did you try the madwifi on the below (and above) URL (that I passed to you above)? Did also you try recompiling madwifi with the patch I referenced in an above post? I can NOT tell from reading, re-reading, and re-reading your posts again as to what you tried after my post. Apologies if I am beating a dead horse, but sometimes a succinct summary advising what you tried, helps in obtaining recommendations. Again, that URL for some madwifi rpms (possibly with the patch) is:
http://download.opensuse.org/repositories/.../openSUSE_10.3/

... and again, you could always try compiling the patch in yourself.
  #7 (permalink)  
Old 16-May-2008, 10:57
johnTD
Guest
 
Posts: n/a
Default

Quote:
Did you try the madwifi on the below (and above) URL (that I passed to you above)? Did also you try recompiling madwifi with the patch I referenced in an above post? I can NOT tell from reading, re-reading, and re-reading your posts again as to what you tried after my post. Apologies if I am beating a dead horse, but sometimes a succinct summary advising what you tried, helps in obtaining recommendations. Again, that URL for some madwifi rpms (possibly with the patch) is:
http://download.opensuse.org/reposit...openSUSE_10.3/

... and again, you could always try compiling the patch in yourself.
[/b]
Thanks oldcpu for the help, I'm trying to install the schmolle1980 stuff but it gives me messages that I don't know what to do with:

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.
  #8 (permalink)  
Old 16-May-2008, 11:14
oldcpu
Guest
 
Posts: n/a
Default

Quote:
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[/b]
The problem is the madwifi-kmp-default you are trying to install is built for a 2.6.22.5 kernel, and you have a 2.6.22.17 kernel. Hence that rpm will not work. You need to install an rpm for your 2.6.22.17 kernel.

Try going here instead:
Code:
http://download.opensuse.org/repositories/home:/schmolle1980/openSUSE_10.3_update/
... ie ... http://download.opensuse.org/repositories/...SE_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.
  #9 (permalink)  
Old 16-May-2008, 12:00
johnTD
Guest
 
Posts: n/a
Default

Quote:
The problem is the madwifi-kmp-default you are trying to install is built for a 2.6.22.5 kernel, and you have a 2.6.22.17 kernel. Hence that rpm will not work. You need to install an rpm for your 2.6.22.17 kernel.

Try going here instead:
Code:
http://download.opensuse.org/repositories/home:/schmolle1980/openSUSE_10.3_update/
... ie ... http://download.opensuse.org/reposit...E_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.
[/b]

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
  #10 (permalink)  
Old 16-May-2008, 14:29
oldcpu
Guest
 
Posts: n/a
Default

Quote:
after I type modprobe ath_pci it doesn't return anything.[/b]
If you wish to see if the kernel module ath_pci is loaded, simply type:
<span style="font-family:Courier New">lsmod | grep ath</span>

Quote:
Under hardware information, a driver shows up there: Listing Active: Yes modprobe Yes modules modprobe ath_pci (ndiswrapper never listed drivers here)[/b]
Thats good, but its still very possible the rpm does not address the bug. ...

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.
 
Page 1 of 2 1 2

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




 

Search Engine Friendly URLs by vBSEO 3.3.0 RC2