Find the answer to your Linux question:
Page 2 of 3 FirstFirst 1 2 3 LastLast
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?...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #11
    Linux Guru AlexK's Avatar
    Join Date
    Feb 2005
    Location
    Earth
    Posts
    3,379

    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?
    Life is complex, it has a real part and an imaginary part.

  2. #12
    Just 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.

  3. #13
    Just Joined!
    Join Date
    Dec 2006
    Posts
    18
    Also..

    # iwlist eth1 scan
    eth1 Interface doesn't support scanning : No such device

  4. $spacer_open
    $spacer_close
  5. #14
    Linux Guru AlexK's Avatar
    Join Date
    Feb 2005
    Location
    Earth
    Posts
    3,379
    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.

  6. #15
    Just Joined!
    Join Date
    Dec 2006
    Posts
    18
    Quote Originally Posted by AlexK
    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
    yep b44 is in there and I removed it. However, when I reboot it comes back...

    bcm43xx is in there too, not sure what it is.

  7. #16
    Just 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

  8. #17
    Linux Guru AlexK's Avatar
    Join Date
    Feb 2005
    Location
    Earth
    Posts
    3,379
    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.

  9. #18
    Just Joined!
    Join Date
    Dec 2006
    Posts
    18
    Quote Originally Posted by AlexK
    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
    Nothing shows up when I type the command. Is there a way to blacklist the native driver in SuSe like..

    http://209.85.165.104/search?q=cache...s&ct=clnk&cd=6

  10. #19
    Linux Guru AlexK's Avatar
    Join Date
    Feb 2005
    Location
    Earth
    Posts
    3,379
    try this
    Code:
    dmesg | grep -i bcm
    cat /var/log/messages | grep -i bcm
    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.
    Life is complex, it has a real part and an imaginary part.

  11. #20
    Just Joined!
    Join Date
    Dec 2006
    Posts
    18
    I do not have an /etc/modules.conf

Page 2 of 3 FirstFirst 1 2 3 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •