Results 11 to 20 of 28
strange....
could you post the results from these commands:
Code:
lsmod
lspci
If you deleted the hardware config in Yast, why not try recreating it?...
- 01-01-2007 #11
strange....
could you post the results from these commands:
If you deleted the hardware config in Yast, why not try recreating it?Code:lsmod lspci
Life is complex, it has a real part and an imaginary part.
- 01-03-2007 #12Just Joined!
- Join Date
- Dec 2006
- Posts
- 18
I recreated a hardware profile for "Wireless Network" using this tutorial
http://nextgen.no-ip.org/~andrew/lin...#IsThisThingOn
After I set it up, I rebooted and found that my wireless card was once again listed in the nic list. So I deleted the old "Wireless" and changed the module name in the recognized one to "ndiswrapper"... not really sure what i'm doing
lsmod spits out a lot but ndiswrapper is listed (let me know if you want anything else specific)...
ndiswrapper 185876 0
lspci spits out a lot too, but here is my card...
02:03.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
Currently when I iwconfig I get...
eth1 IEEE 802.11b/g ESSID:"" Nickname:"Broadcom 4318"
Mode: Managed Access Point: Invalid
etc.....
Why do I get a blank ESSID and an invalid access point even though I set these up in YAST? The ESSID should at least be what I set it up as. Also, is it going to hurt anything having the interface called eth1 instead of wlan0? I found a couple tutorials that said this could be a problem (but no solutions on how to fix the problem with suse distro.)
Thanks for helping.
- 01-03-2007 #13Just Joined!
- Join Date
- Dec 2006
- Posts
- 18
Also..
# iwlist eth1 scan
eth1 Interface doesn't support scanning : No such device
- 01-03-2007 #14
I still think there may be a conflict with the drivers i.e. ndiswrapper and b44. In output from lsmod, look for something like b44 or b44win, if it is there, use rmmod to remove it i.e. execute: rmmod b44
Also try this:
Code:iwconfig eth1 essid my_ssid
Life is complex, it has a real part and an imaginary part.
- 01-03-2007 #15Just Joined!
- Join Date
- Dec 2006
- Posts
- 18
yep b44 is in there and I removed it. However, when I reboot it comes back...
Originally Posted by AlexK
bcm43xx is in there too, not sure what it is.
- 01-04-2007 #16Just Joined!
- Join Date
- Dec 2006
- Posts
- 18
also...
# iwconfig eth1 essid my_essid
Error for wireless request "Set ESSID" (8B1A)
SET failed on device eth1 : No such device
- 01-05-2007 #17
From google, the bcm43xx is the wireless card, b44 is a wired ethernet card. Try rmmodding bcm43xx also, could you post the result from this command (for curiosity and incase ndiswrapper doesn't work):
Code:dmesg | grep bcm
Life is complex, it has a real part and an imaginary part.
- 01-05-2007 #18Just Joined!
- Join Date
- Dec 2006
- Posts
- 18
Nothing shows up when I type the command. Is there a way to blacklist the native driver in SuSe like..
Originally Posted by AlexK
http://209.85.165.104/search?q=cache...s&ct=clnk&cd=6
- 01-06-2007 #19
try this
as for preventing modules from loading, look in /etc/modules.conf for bcm43xx, then put a # infront of any lines which contain bcm43xx. The # comments out the line thus making the system skip over it during boot.Code:dmesg | grep -i bcm cat /var/log/messages | grep -i bcm
Life is complex, it has a real part and an imaginary part.
- 01-06-2007 #20Just Joined!
- Join Date
- Dec 2006
- Posts
- 18
I do not have an /etc/modules.conf


Reply With Quote
