Find the answer to your Linux question:
Results 1 to 10 of 10
i have been trying to get this to work for the past couple of days and i think i have ran out of stuff to read ndiswrapper -l says that ...
  1. #1
    Just Joined!
    Join Date
    Aug 2009
    Posts
    7

    help, wireless, wpn111, ndiswrapper

    i have been trying to get this to work for the past couple of days and i think i have ran out of stuff to read
    ndiswrapper -l says that the driver is installed
    lsusb finds it but says no firmware
    !! any ideas?
    i dont have internet on that computer so have been running back and forth with my usb drive trying to figure this out lol

  2. #2
    tpl
    tpl is offline
    Linux User
    Join Date
    Jan 2007
    Location
    cleveland
    Posts
    452
    the sun is new every day (heraclitus)

  3. #3
    Linux Guru waterhead's Avatar
    Join Date
    Jul 2004
    Location
    Franklin, Wisconsin
    Posts
    4,577
    Off the top of my head, it sounds like you may have two drivers loading for the wireless. NDISwrapper is rarely needed, as there usually are native Linux drivers for wireless cards.

    To help, we will need more detailed information. Read through the post linked to below. It describes the info needed, and how to find it.

    Wireless Setup - Start Here
    Paul

    Please do not send Private Messages to me with requests for help. I will not reply.

  4. #4
    Just Joined!
    Join Date
    Aug 2009
    Posts
    7
    tried that page already... there arent native drivers for the wpn111 hence the work, i still dont get it tho, i just got ndisgtk installed and it says device present for the driver installed, but now Could not find a network configuration tool.' , tried the managed=true fix from another forum but that didnt work, im so lost

  5. #5
    Linux Guru waterhead's Avatar
    Join Date
    Jul 2004
    Location
    Franklin, Wisconsin
    Posts
    4,577
    Post the info that I requested!
    Paul

    Please do not send Private Messages to me with requests for help. I will not reply.

  6. #6
    Just Joined!
    Join Date
    Aug 2009
    Posts
    7
    allright, 1 min

  7. #7
    Just Joined!
    Join Date
    Aug 2009
    Posts
    7
    DOH

    omg.. im an idiot... atleast i learned abit in the process
    the entire problem, i had it hooked up to a usb hub that i dont have extra power going to... in dmesg it said 1 usb not used because inssuficiant power
    anyway... it works... thanks for your time

  8. #8
    Linux Guru waterhead's Avatar
    Join Date
    Jul 2004
    Location
    Franklin, Wisconsin
    Posts
    4,577
    I guess we will never know what chipset it has, and what Linux driver can be used for it.

    I believe that it uses a Ralink chip, and there are Linux drivers for Ralink wireless cards.

    You can still post the info, if you want.
    Paul

    Please do not send Private Messages to me with requests for help. I will not reply.

  9. #9
    Just Joined!
    Join Date
    Aug 2009
    Posts
    7
    ran your wirelesssetup file: heres the info
    Code:
    ============ lspci ============
    00:00.0 Host bridge [0600]: Intel Corporation 440LX/EX - 82443LX/EX Host bridge [8086:7180] (rev 03)
    	Kernel driver in use: agpgart-intel
    	Kernel modules: intel-agp
    00:01.0 PCI bridge [0604]: Intel Corporation 440LX/EX - 82443LX/EX AGP bridge [8086:7181] (rev 03)
    	Kernel modules: shpchp
    00:14.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] (rev 02)
    00:14.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01)
    	Kernel driver in use: ata_piix
    00:14.2 USB Controller [0c03]: Intel Corporation 82371AB/EB/MB PIIX4 USB [8086:7112] (rev 01)
    	Kernel driver in use: uhci_hcd
    00:14.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 02)
    	Kernel modules: i2c-piix4
    01:00.0 VGA compatible controller [0300]: ATI Technologies Inc 3D Rage LT Pro AGP-133 [1002:4c42] (rev dc)
    	Kernel modules: atyfb
    
    ============ lsusb ============
    Bus 001 Device 005: ID 154b:0016 PNY 
    Bus 001 Device 004: ID 045e:0039 Microsoft Corp. IntelliMouse Optical
    Bus 001 Device 003: ID 0451:2046 Texas Instruments, Inc. TUSB2046 Hub
    Bus 001 Device 002: ID 1385:5f01 Netgear, Inc WPN111 (no firmware)
    Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    
    ============ lsmod ============
    Module                  Size  Used by
    nls_iso8859_1          12032  1 
    nls_cp437              13696  1 
    vfat                   18816  1 
    fat                    58272  1 vfat
    binfmt_misc            16776  1 
    ppdev                  15620  0 
    bridge                 56340  0 
    stp                    10500  1 bridge
    bnep                   20224  2 
    lp                     17156  0 
    parport                42220  2 ppdev,lp
    psmouse                61972  0 
    pcspkr                 10496  0 
    serio_raw              13316  0 
    i2c_piix4              18448  0 
    ndiswrapper           193436  0 
    intel_agp              34108  1 
    shpchp                 40212  0 
    agpgart                42696  1 intel_agp
    usbhid                 42336  0 
    usb_storage            82880  1 
    fbcon                  46112  0 
    tileblit               10752  1 fbcon
    font                   16384  1 fbcon
    bitblit                13824  1 fbcon
    softcursor              9984  1 bitblit
    
    ============ dmesg-firmware ============
    
    ============ kernel version ============
    2.6.28-11-generic

  10. #10
    Linux Guru waterhead's Avatar
    Join Date
    Jul 2004
    Location
    Franklin, Wisconsin
    Posts
    4,577
    Thanks for indulging me!

    I see that Netgear disguises the device with their own ID:
    Code:
    1385:5f01 Netgear, Inc WPN111 (no firmware)
    This makes it tougher to figure out the chipset. You would have to disassemble the thing to investigate. No, don't do that!

    Some Googling tells me that this may have an Atheros chipset, so existing Atheros drivers could possibly work with it. It is not recognized as an Atheros based device, so those drivers are not loading.

    Since it is working with NDISwrapper, then that is good enough.

    Thanks again for the info,
    enjoy!
    Paul

    Please do not send Private Messages to me with requests for help. I will not reply.

Posting Permissions

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