Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 21

Thread: [SOLVED] Ndiswrapper + Marvell chipset cannot connect in 8.10

  1. #11
    Join Date
    Jan 2009
    Beans
    3

    Re: [SOLVED] Ndiswrapper + Marvell chipset cannot connect in 8.10

    First, sorry for the time I was offline.

    So, there's go my lists

    #ifconfig
    Code:
    eth0      Link encap:Ethernet  Endereço de HW 00:1a:92:9e:aa:3d  
              UP BROADCAST MULTICAST  MTU:1500  Métrica:1
              pacotes RX:0 erros:0 descartados:0 excesso:0 quadro:0
              Pacotes TX:0 erros:0 descartados:0 excesso:0 portadora:0
              colisões:0 txqueuelen:1000 
              RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
              IRQ:23 Endereço de E/S:0x4000 
    
    lo        Link encap:Loopback Local  
              inet end.: 127.0.0.1  Masc:255.0.0.0
              endereço inet6: ::1/128 Escopo:Máquina
              UP LOOPBACK RUNNING  MTU:16436  Métrica:1
              pacotes RX:245 erros:0 descartados:0 excesso:0 quadro:0
              Pacotes TX:245 erros:0 descartados:0 excesso:0 portadora:0
              colisões:0 txqueuelen:0 
              RX bytes:15440 (15.4 KB) TX bytes:15440 (15.4 KB)
    
    wlan0     Link encap:Ethernet  Endereço de HW 00:03:2f:3c:5e:73  
              inet end.: 10.1.1.8  Bcast:10.255.255.255  Masc:255.0.0.0
              endereço inet6: fe80::203:2fff:fe3c:5e73/64 Escopo:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Métrica:1
              pacotes RX:0 erros:0 descartados:0 excesso:0 quadro:0
              Pacotes TX:36 erros:0 descartados:0 excesso:0 portadora:0
              colisões:0 txqueuelen:1000 
              RX bytes:0 (0.0 B) TX bytes:4552 (4.5 KB)
              IRQ:17 Memória:f9fe0000-f9ff0000
    #iwconfig
    Code:
    wlan0     IEEE 802.11g  ESSID:"GUEDES"  
              Mode:Managed  Frequency:2.437 GHz  Access Point: 00:17:9A:45:01:0F   
              Bit Rate=1 Mb/s   Sensitivity=-200 dBm  
              RTS thr=2346 B   Fragment thr=2346 B   
              Power Management:off
              Link Quality:42/100  Signal level:-69 dBm  Noise level:-96 dBm
              Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
              Tx excessive retries:0  Invalid misc:0   Missed beacon:0
    #ndiswrapper -l
    Code:
    mrv8335 : driver installed
    	device (11AB:1FAA) present
    #lsmod | grep ndiswrapper
    Code:
    ndiswrapper           196380  0 
    usbcore               148848  7 usb_storage,libusual,ndiswrapper,usblp,uhci_hcd,ehci_hcd
    #dmesg | grep -ie wlan0 -ie ndiswrapper

    Code:
    [   19.864827] ndiswrapper version 1.53 loaded (smp=yes, preempt=no)
    [   19.972070] ndiswrapper: driver mrv8335 (TRENDnet,08/22/2005,3.2.1.3) loaded
    [   19.972452] ndiswrapper 0000:00:09.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    [   19.975244] ndiswrapper: using IRQ 17
    [   20.242668] wlan0: ethernet device 00:03:2f:3c:5e:73 using NDIS driver: mrv8335, version: 0x3020002, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 11AB:1FAA.5.conf
    [   20.242697] wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
    [   20.257720] usbcore: registered new interface driver ndiswrapper
    [  125.012018] wlan0: no IPv6 routers present
    The strange in my case is that I can't configure my network... It seems connect, but I can't surf into the web.

    Here, the connection is by one fixed IP, and in trough the router D-Link is distributed by DHCP for other machines in this Network.

    The most strange is when I atribute an IP, it connects but it cant take a Adress :

    #syslog.conf
    Code:
    Jan 16 13:46:58 truncatus syslogd 1.5.0#2ubuntu6: restart.
    Jan 16 13:46:58 truncatus anacron[5090]: Job `cron.daily' terminated
    Jan 16 13:46:58 truncatus anacron[5090]: Normal exit (1 job run)
    Jan 16 13:49:05 truncatus NetworkManager: <info>  Activation (wlan0) starting connection 'Auto GUEDES' 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  (wlan0): device state change: 3 -> 4 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started... 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting... 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  (wlan0): device state change: 4 -> 5 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  Activation (wlan0/wireless): access point 'Auto GUEDES' has security, but secrets are required. 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  (wlan0): device state change: 5 -> 6 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete. 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started... 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  (wlan0): device state change: 6 -> 4 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting... 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  (wlan0): device state change: 4 -> 5 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  Activation (wlan0/wireless): connection 'Auto GUEDES' has security, and secrets exist.  No new secrets needed. 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  Config: added 'ssid' value 'GUEDES' 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  Config: added 'scan_ssid' value '1' 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  Config: added 'key_mgmt' value 'NONE' 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  Config: added 'auth_alg' value 'OPEN' 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  Config: added 'wep_key0' value '<omitted>' 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  Config: added 'wep_key1' value '<omitted>' 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  Config: added 'wep_tx_keyidx' value '0' 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete. 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  Config: set interface ap_scan to 1 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  (wlan0): supplicant connection state change: 2 -> 0 
    Jan 16 13:49:05 truncatus NetworkManager: <info>  (wlan0): supplicant connection state change: 0 -> 2 
    Jan 16 13:49:10 truncatus NetworkManager: <info>  (wlan0): device state change: 5 -> 3 
    Jan 16 13:49:10 truncatus NetworkManager: <info>  (wlan0): deactivating device (reason: 0). 
    Jan 16 13:49:10 truncatus NetworkManager: <info>  Activation (wlan0) starting connection 'Auto GUEDES' 
    Jan 16 13:49:10 truncatus NetworkManager: <info>  (wlan0): device state change: 3 -> 4 
    Jan 16 13:49:10 truncatus NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... 
    Jan 16 13:49:10 truncatus NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started... 
    Jan 16 13:49:10 truncatus NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... 
    Jan 16 13:49:10 truncatus NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. 
    Jan 16 13:49:10 truncatus NetworkManager: <info>  (wlan0): supplicant connection state change: 2 -> 0 
    Jan 16 13:49:10 truncatus NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting... 
    Jan 16 13:49:10 truncatus NetworkManager: <info>  (wlan0): device state change: 4 -> 5 
    Jan 16 13:49:10 truncatus NetworkManager: <info>  Activation (wlan0/wireless): connection 'Auto GUEDES' has security, and secrets exist.  No new secrets needed. 
    Jan 16 13:49:10 truncatus NetworkManager: <info>  Config: added 'ssid' value 'GUEDES' 
    Jan 16 13:49:10 truncatus NetworkManager: <info>  Config: added 'scan_ssid' value '1' 
    Jan 16 13:49:10 truncatus NetworkManager: <info>  Config: added 'key_mgmt' value 'NONE' 
    Jan 16 13:49:10 truncatus NetworkManager: <info>  Config: added 'auth_alg' value 'OPEN' 
    Jan 16 13:49:10 truncatus NetworkManager: <info>  Config: added 'wep_key0' value '<omitted>' 
    Jan 16 13:49:10 truncatus NetworkManager: <info>  Config: added 'wep_key1' value '<omitted>' 
    Jan 16 13:49:10 truncatus NetworkManager: <info>  Config: added 'wep_tx_keyidx' value '0' 
    Jan 16 13:49:10 truncatus NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete. 
    Jan 16 13:49:10 truncatus NetworkManager: <info>  Config: set interface ap_scan to 1 
    Jan 16 13:49:10 truncatus NetworkManager: <info>  (wlan0): supplicant connection state change: 0 -> 2 
    Jan 16 13:49:12 truncatus NetworkManager: <info>  (wlan0): supplicant connection state change: 2 -> 0 
    Jan 16 13:49:17 truncatus NetworkManager: <info>  (wlan0): supplicant connection state change: 0 -> 3 
    Jan 16 13:49:17 truncatus NetworkManager: <info>  (wlan0): supplicant connection state change: 3 -> 4 
    Jan 16 13:49:17 truncatus NetworkManager: <info>  (wlan0): supplicant connection state change: 4 -> 7 
    Jan 16 13:49:17 truncatus NetworkManager: <info>  Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'GUEDES'. 
    Jan 16 13:49:17 truncatus NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled. 
    Jan 16 13:49:17 truncatus NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) started... 
    Jan 16 13:49:17 truncatus NetworkManager: <info>  (wlan0): device state change: 5 -> 7 
    Jan 16 13:49:17 truncatus NetworkManager: <info>  Activation (wlan0) Beginning DHCP transaction. 
    Jan 16 13:49:17 truncatus dhclient: Internet Systems Consortium DHCP Client V3.1.1
    Jan 16 13:49:17 truncatus dhclient: Copyright 2004-2008 Internet Systems Consortium.
    Jan 16 13:49:17 truncatus dhclient: All rights reserved.
    Jan 16 13:49:17 truncatus dhclient: For info, please visit http://www.isc.org/sw/dhcp/
    Jan 16 13:49:17 truncatus dhclient: 
    Jan 16 13:49:17 truncatus NetworkManager: <info>  dhclient started with pid 7157 
    Jan 16 13:49:17 truncatus NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. 
    Jan 16 13:49:17 truncatus NetworkManager: <info>  DHCP: device wlan0 state changed normal exit -> preinit 
    Jan 16 13:49:17 truncatus dhclient: Listening on LPF/wlan0/00:03:2f:3c:5e:73
    Jan 16 13:49:17 truncatus dhclient: Sending on   LPF/wlan0/00:03:2f:3c:5e:73
    Jan 16 13:49:17 truncatus dhclient: Sending on   Socket/fallback
    Jan 16 13:49:21 truncatus dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
    Jan 16 13:49:28 truncatus dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
    Jan 16 13:49:38 truncatus dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
    Jan 16 13:49:48 truncatus dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
    Jan 16 13:50:02 truncatus NetworkManager: <info>  Device 'wlan0' DHCP transaction took too long (>45s), stopping it. 
    Jan 16 13:50:02 truncatus NetworkManager: <info>  wlan0: canceled DHCP transaction, dhcp client pid 7157 
    Jan 16 13:50:02 truncatus NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) scheduled... 
    Jan 16 13:50:02 truncatus NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) started... 
    Jan 16 13:50:02 truncatus NetworkManager: <info>  Activation (wlan0/wireless): could not get IP configuration for connection 'Auto GUEDES'. 
    Jan 16 13:50:02 truncatus NetworkManager: <info>  (wlan0): device state change: 7 -> 6 
    Jan 16 13:50:02 truncatus NetworkManager: <info>  Activation (wlan0/wireless): asking for new secrets 
    Jan 16 13:50:02 truncatus NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) complete. 
    Jan 16 13:50:11 truncatus NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... 
    Jan 16 13:50:11 truncatus NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started... 
    Jan 16 13:50:11 truncatus NetworkManager: <info>  (wlan0): device state change: 6 -> 4 
    Jan 16 13:50:11 truncatus NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... 
    Jan 16 13:50:11 truncatus NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. 
    Jan 16 13:50:11 truncatus NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting... 
    Jan 16 13:50:11 truncatus NetworkManager: <info>  (wlan0): device state change: 4 -> 5 
    Jan 16 13:50:11 truncatus NetworkManager: <info>  Activation (wlan0/wireless): connection 'Auto GUEDES' has security, and secrets exist.  No new secrets needed. 
    Jan 16 13:50:11 truncatus NetworkManager: <info>  Config: added 'ssid' value 'GUEDES' 
    Jan 16 13:50:11 truncatus NetworkManager: <info>  Config: added 'scan_ssid' value '1' 
    Jan 16 13:50:11 truncatus NetworkManager: <info>  Config: added 'key_mgmt' value 'NONE' 
    Jan 16 13:50:11 truncatus NetworkManager: <info>  Config: added 'auth_alg' value 'OPEN' 
    Jan 16 13:50:11 truncatus NetworkManager: <info>  Config: added 'wep_key0' value '<omitted>' 
    Jan 16 13:50:11 truncatus NetworkManager: <info>  Config: added 'wep_key1' value '<omitted>' 
    Jan 16 13:50:11 truncatus NetworkManager: <info>  Config: added 'wep_tx_keyidx' value '0' 
    Jan 16 13:50:11 truncatus NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete. 
    Jan 16 13:50:15 truncatus NetworkManager: <info>  Config: set interface ap_scan to 1 
    Jan 16 13:50:15 truncatus NetworkManager: <info>  (wlan0): supplicant connection state change: 7 -> 0 
    Jan 16 13:50:15 truncatus NetworkManager: <info>  (wlan0): supplicant connection state change: 0 -> 2 
    Jan 16 13:50:17 truncatus NetworkManager: <info>  (wlan0): supplicant connection state change: 2 -> 0 
    Jan 16 13:50:22 truncatus NetworkManager: <info>  (wlan0): supplicant connection state change: 0 -> 3 
    Jan 16 13:50:22 truncatus NetworkManager: <info>  (wlan0): supplicant connection state change: 3 -> 0 
    Jan 16 13:50:22 truncatus NetworkManager: <info>  (wlan0): supplicant connection state change: 0 -> 4 
    Jan 16 13:50:22 truncatus NetworkManager: <info>  (wlan0): supplicant connection state change: 4 -> 7 
    Jan 16 13:50:22 truncatus NetworkManager: <info>  Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'GUEDES'. 
    Jan 16 13:50:22 truncatus NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled. 
    Jan 16 13:50:22 truncatus NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) started... 
    Jan 16 13:50:22 truncatus NetworkManager: <info>  (wlan0): device state change: 5 -> 7 
    Jan 16 13:50:22 truncatus NetworkManager: <info>  Activation (wlan0) Beginning DHCP transaction. 
    Jan 16 13:50:22 truncatus dhclient: Internet Systems Consortium DHCP Client V3.1.1
    Jan 16 13:50:22 truncatus dhclient: Copyright 2004-2008 Internet Systems Consortium.
    Jan 16 13:50:22 truncatus dhclient: All rights reserved.
    Jan 16 13:50:22 truncatus dhclient: For info, please visit http://www.isc.org/sw/dhcp/
    Jan 16 13:50:22 truncatus dhclient: 
    Jan 16 13:50:22 truncatus NetworkManager: <info>  dhclient started with pid 7205 
    Jan 16 13:50:22 truncatus NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. 
    Jan 16 13:50:22 truncatus NetworkManager: <info>  DHCP: device wlan0 state changed normal exit -> preinit 
    Jan 16 13:50:22 truncatus dhclient: Listening on LPF/wlan0/00:03:2f:3c:5e:73
    Jan 16 13:50:22 truncatus dhclient: Sending on   LPF/wlan0/00:03:2f:3c:5e:73
    Jan 16 13:50:22 truncatus dhclient: Sending on   Socket/fallback
    Jan 16 13:50:22 truncatus dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
    Jan 16 13:50:26 truncatus dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
    Jan 16 13:50:33 truncatus dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
    Jan 16 13:50:48 truncatus dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
    Jan 16 13:51:04 truncatus dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
    Jan 16 13:51:07 truncatus NetworkManager: <info>  Device 'wlan0' DHCP transaction took too long (>45s), stopping it. 
    Jan 16 13:51:07 truncatus NetworkManager: <info>  wlan0: canceled DHCP transaction, dhcp client pid 7205 
    Jan 16 13:51:07 truncatus NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) scheduled...
    And when I let the wireless configuration to atributes an IP by DHCP it can't connect.

    The sam results is given by the command
    #dhclient wlan0

    Thank you for all.

  2. #12
    Join Date
    Jan 2009
    Location
    Melbourne, Australia
    Beans
    1
    Distro
    Ubuntu 8.10 Intrepid Ibex

    Talking Re: [SOLVED] Ndiswrapper + Marvell chipset cannot connect in 8.10

    For anyone struggling with a Netgear WG511v2 card with the Marvell chipset (made in China) - give the drivers a go that are posted in this thread.

    I was about to throw the card through the window & as a last resort I tried the drivers posted here - the card suddenly came to life. What a pleasant surprise!

  3. #13
    Join Date
    Jan 2009
    Beans
    3

    Re: [SOLVED] Ndiswrapper + Marvell chipset cannot connect in 8.10

    Hi stustustu123.

    Could you tell us how you did all the process to put up your marvell card?

    I`m her getting connection too,but I can`t surf into the web.

    post us your

    #ndiswrapper -l

    Thank you all.

  4. #14
    Join Date
    Jan 2008
    Beans
    6

    Re: [SOLVED] Ndiswrapper + Marvell chipset cannot connect in 8.10

    Thanks so much for your driver. I was so upset about the wireless not working and then i found this thread. You saved me from insanity. LOL.

  5. #15
    Join Date
    May 2009
    Beans
    1

    Re: [SOLVED] Ndiswrapper + Marvell chipset cannot connect in 8.10

    Thank you for posting that driver caljohnsmith, another success story here. That driver made WPA work again, either manually through wpa_supplicant or with Network manager. Here is my setup in case someone experiences the same issues.

    Kubuntu 9.04
    Kernel 2.6.28-11-generic
    ndiswrapper-common and ndiswrapper-utils-1.9 at version 1.53-2ubuntu1

    Relevant output of lspci -vvv :
    02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88w8335 [Libertas] 802.11b/g Wireless (rev 03)
    Subsystem: Marvell Technology Group Ltd. 88w8335 [Libertas] 802.11b/g Wireless
    Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 64
    Interrupt: pin A routed to IRQ 17
    Region 0: Memory at 34000000 (32-bit, non-prefetchable) [size=64K]
    Region 1: Memory at 34010000 (32-bit, non-prefetchable) [size=64K]
    Capabilities: <access denied>
    Kernel driver in use: ndiswrapper

  6. #16
    Join Date
    Aug 2009
    Beans
    2

    Thumbs down Re: [SOLVED] Ndiswrapper + Marvell chipset cannot connect in 8.10

    @caljohnsmith:

    Thanks for posting those drivers. Fixed my issue as well.

    73 de AI8W

  7. #17
    Join Date
    May 2006
    Location
    México, D.F.
    Beans
    17
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Ndiswrapper + Marvell chipset cannot connect in 8.10

    Thank you for posting THE functional Marvel driver. Mine, which came with the Windows disc, didn't worked. Thanks again,

    Celita

  8. #18
    Join Date
    Jan 2010
    Beans
    3

    Re: [SOLVED] Ndiswrapper + Marvell chipset cannot connect in 8.10

    More than one year after the solution of this little Marvell wi-fi problem, another head banger to thank warmly caljohnsmith for the driver that works !

    Now I can deploy Ubuntu 9.04 in my little company in Addis Ababa, Ethiopia, and stop using Winbug.

    Thanks a lot guys.

  9. #19
    Join Date
    Mar 2010
    Beans
    1

    Re: [SOLVED] Ndiswrapper + Marvell chipset cannot connect in 8.10

    I can't believe how much of my life has been wasted trying to get this wifi card to work- mine was in the guise of a Linksys WPC54G Ver 5. I feel like downloading 20 copies of those drivers posted in this thread and stashing them in various places. Stupid I know. Thanks again

  10. #20
    Join Date
    Jul 2012
    Beans
    4

    Re: [SOLVED] Ndiswrapper + Marvell chipset cannot connect in 8.10

    thanks to for the 8335 driver

    cameo Model: WLG-1101 11g wireless lan
    for me

Page 2 of 3 FirstFirst 123 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

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