Results 1 to 10 of 10

Thread: SUSE 10.1, Asus WL-138g, wireless horror

  1. #1
    Athywren NNTP User

    Unhappy SUSE 10.1, Asus WL-138g, wireless horror

    Hi guys,

    I'm trying to set up a wireless connection on my linux box, I already read through the stickies (I hoped I might be able to get through this without having to directly ask for help ).
    My wireless card is an ASUS WL-138g, I would post the ids but the problem I'm having is that the card doesn't show up in the "lspci" or "lsusb" lists.
    I know the "My wireless doesn't work - a primer on what I should do next" sticky suggests that this means the card or motherboard is broken, but I know this is not the case as I'm dual booting with Windows XP and the wireless works fine there.

    I'm sure I'm missing something ridiculously basic but I can't think what. If anyone has any suggestions to help me introduce my os to my wireless, I'd be grateful for anything you can tell me.

    Cheers
    Athywren

  2. #2
    Join Date
    Jun 2008
    Location
    Sarasota
    Posts
    301

    Default Re: SUSE 10.1, Asus WL-138g, wireless horror

    When you google your card, the answer seems to be that it is USB, does NOT
    detect (as you say), and thus the only option is to use ndiswrapper:
    Asus Wl-138g With Suse Linux?

    [Ndiswrapper website is down right now, so I couldn't confirm.]
    Box1: MEPIS-8.5/sidux/openSUSE-11.3M6(broken-wifi/hiddenSSIDs)/XP(32-bit), nvidia 5200
    Lap1: antiX-8.5(KDE4.4.3)/MEPIS-8.5/Vista, Intel 945GM, builtin-wifi->Broadcom-4311(drv=wl)

  3. #3
    Athywren NNTP User

    Default Re: SUSE 10.1, Asus WL-138g, wireless horror

    So... I'm trying to fix a problem that doesn't technically exist? That would explain the trouble I've been having.
    I've got ndiswrapper installed and (for the first time ever for me!) working. I guess this mean I just need to double check the connection details. Thanks cookdav .

    Athywren

  4. #4
    Join Date
    Jun 2008
    Location
    Kansas City Area, Missouri, USA
    Posts
    7,235

    Default Re: SUSE 10.1, Asus WL-138g, wireless horror

    Athywren wrote:
    > So... I'm trying to fix a problem that doesn't technically exist? That
    > would explain the trouble I've been having.
    > I've got ndiswrapper installed and (for the first time ever for me!)
    > working. I guess this mean I just need to double check the connection
    > details. Thanks cookdav .


    Please go back and recheck your lspci/lsusb output. Your card must be
    there or ndiswrapper wouldn't be able to work. Those commands check
    the lowest level and do not depend on drivers. In fact, the results of
    such scans are the basis for selecting the driver to load.

    Larry

  5. #5
    Athywren NNTP User

    Default Re: SUSE 10.1, Asus WL-138g, wireless horror

    Ok, I'm looking for ASUS wlan hardware.
    When checking lspci I get:
    Code:
    00:00.0 Host bridge: VIA Technologies, Inc. VT8385 [K8T800 AGP] Host Bridge (rev 01)
    00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South]
    00:09.0 Ethernet controller: Marvell Technology Group Ltd. Marvell W8300 802.11 Adapter (rev 07)
    00:0a.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)
    00:0e.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10)
    00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
    00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE
    (rev 06)
    00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
    00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
    00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
    00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
    00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
    00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
    00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller
    (rev 60)
    00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 80)
    00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology
    Configuration
    00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
    00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
    00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
    01:00.0 VGA compatible controller: nVidia Corporation Unknown device 02e1 (rev a2)
    With lsusb I see:
    Code:
    Bus 004 Device 001: ID 0000:0000
    Bus 005 Device 001: ID 0000:0000
    Bus 003 Device 001: ID 0000:0000
    Bus 002 Device 003: ID 0763:2010 Midiman
    Bus 002 Device 001: ID 0000:0000
    Bus 001 Device 004: ID 03f0:2811 Hewlett-Packard PSC-2100
    Bus 001 Device 001: ID 0000:0000
    I know the device must be there somewhere, since ndiswrapper claims to see it:
    Code:
    mrv8k51         driver installed, hardware present
    but I'm seeing no evidence of it in those lookups, and as I mentioned earlier, I know that the card isn't broken since it works almost flawlessly when I boot WinXP... but with that said, I might go crazy and shuffle my pcis around and see what happens.

    Cheers for your input guys.

    Athywren

  6. #6
    Athywren NNTP User

    Default Re: SUSE 10.1, Asus WL-138g, wireless horror

    After changing pci slots, there is absolutely no difference in either the lspci or lsusb list, so... I'm basically lost and confused now. I know the card works because it works in windows, but linux won't even see the card, despite ndiswrapper's insistence that it's there. I'm just hoping there's some way to work around this (or teach linux to see the card maybe?).

    Athywren

  7. #7
    Join Date
    Jan 2008
    Location
    U.K East Anglia
    Posts
    2,581

    Default Re: SUSE 10.1, Asus WL-138g, wireless horror

    What does YaST - Hardware - Hardware Info show ?
    have you tried lspci -v ?

    Andy
    To be is to do = Immanuel Kant
    To do is to be = Descartes.
    Do be do be do = Frank Sinatra

    SuSE user since 7.0,Linux user since 1994

  8. #8
    Join Date
    Jun 2008
    Location
    Kansas City Area, Missouri, USA
    Posts
    7,235

    Default Re: SUSE 10.1, Asus WL-138g, wireless horror

    Athywren wrote:
    > Ok, I'm looking for ASUS wlan hardware.
    > When checking lspci I get:
    >
    > 00:09.0 Ethernet controller: Marvell Technology Group Ltd. Marvell W8300 802.11 Adapter (rev 07)


    This one is your wireless adapter. Please issue the command
    '/sbin/lspci -nnv' and post the first two lines for buss 00:09.0.
    From what I found searching for "Marvell W8300", I don't think there
    is a native driver, but the vendor and PCI IDs are what we need to
    check for sure.

    Larry



  9. #9
    Athywren NNTP User

    Default Re: SUSE 10.1, Asus WL-138g, wireless horror

    After checking lspci -v and the YaST hardware info, I'd guessed it was the Marvell W8300 802.11 device, the ids are 11ab:1fa6
    Stupid mistake on my part to start with; I was looking for ASUS etc with rather than the 802.11 part.

    I checked through the output from the dmesg|less command didn't show any sign of the device, though I'd booted with the acpi=off parameter as I'd read that it might help and that might be responsible (I don't know), is that likely to be a problem?

    Athywren

  10. #10
    Join Date
    Jun 2008
    Location
    Kansas City Area, Missouri, USA
    Posts
    7,235

    Default Re: SUSE 10.1, Asus WL-138g, wireless horror

    Athywren wrote:
    > After checking lspci -v and the YaST hardware info, I'd
    > guessed it was the Marvell W8300 802.11 device, the ids are *11ab:1fa6*
    > Stupid mistake on my part to start with; I was looking for ASUS etc
    > with rather than the 802.11 part.


    There are no drivers that recognize PCI ID 1fa6 in kernels as new as
    2.6.27-rc6, thus no driver claims it and it doesn't show up in dmesg.
    Ndiswrapper is your only choice.

    Larry

Tags for this Thread

Posting Permissions

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