You are not logged in.

#1 2008-07-27 22:34:06

whaevr
Member
Registered: 2008-03-17
Posts: 182

Argh...

Alright for some strange reason I did tried to modprobe ndiswrapper one last time in pure frustration..and then I did iwconfig and got this!

lo        no wireless extensions.

eth0      no wireless extensions.

eth1      no wireless extensions.

wlan0     IEEE 802.11g  ESSID:off/any  
          Mode:Managed  Channel:0  Access Point: Not-Associated   
          Bit Rate:1 Mb/s   Sensitivity=-200 dBm  
          RTS thr=2346 B   Fragment thr=2346 B   
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

For some reason it loaded! The only thing I've done differently is install wicd and prevent the "network" daemon from loading (this is required for wicd) I'm not going to try and understand why it worked and just claim magic was involved yikes

Although for some reason wicd isn't picking up a wireless interface..going to load ndiswrapper at start and hopefully it will.

Edit:
Well that was a short lived victory...I booted up again hit iwconfig and got this:

lo        no wireless extensions.

eth0      no wireless extensions.

eth1      no wireless extensions.

tried modprobe ndiswrapper and then checked dmesg and saw this:

ndiswrapper version 1.52 loaded (smp=yes, preempt=yes)
ndiswrapper (link_pe_images:576): fixing KI_USER_SHARED_DATA address in the driver
ndiswrapper: driver wg311v3 (NETGEAR,02/22/2005,3.1.1.7) loaded
ndiswrapper: using IRQ 17
ndiswrapper (mp_init:216): couldn't initialize device: C0000001
ndiswrapper (pnp_start_device:439): Windows driver couldn't initialize the device (C0000001)
ndiswrapper (mp_halt:259): device ffff81009f9cd700 is not initialized - not halting
ndiswrapper: device eth%d removed
ndiswrapper: probe of 0000:01:07.0 failed with error -22
usbcore: registered new interface driver ndiswrapper

Good to know things are being consistent here...

Last edited by whaevr (2008-07-28 23:17:19)

Offline

#2 2008-07-27 23:21:01

iphitus
Forum Fellow
From: Melbourne, Australia
Registered: 2004-10-09
Posts: 4,927

Re: Argh...

Try a different windows driver, otherwise file a bug with ndiswrapper.

Also... this is the usb one, I'm fairly sure there's a native driver for this. Google
"marvell libertas wireless linux"

Offline

#3 2008-07-28 00:30:15

whaevr
Member
Registered: 2008-03-17
Posts: 182

Re: Argh...

I searched what you've mentioned and I can't find anything >.<

I don't have a clue why this isn't working I've tried various other suggestions and nothing seems to work. Once my system froze when I tried to do "modprobe ndiswrapper"

Hopefully someone else has another idea...in the mean time I'll be beating my head against a wall big_smile

K I went to the Ndiswrapper website and found this:

Card: Marvell 88W8335 - Libertas 802.11b/g Wireless (rev 03)

    *
      Chipset: Marvell 88W8335
    *
      pciid: 11ab:1faa (rev 03)
#
Other: Ndiswrapper 1.34, Recompiled kernel 2.6.18.3, without smp, with kernel debug and without 4kstacks. Debian Testing "Etch". WPA not tested.
#
Driver: http://skd.de/e_en/support/driver_searchresults.html?navanchor=&term=typ.treiber+produkt.SK-54C1&produkt=produkt.SK-54C1&typ=typ.treiber&system= (Used Windows x64 driver for 64-bit amd64 x86_64 Fedora 7.)

So does this mean I should recompile my kernel like the person above?

Last edited by whaevr (2008-07-28 12:02:25)

Offline

Board footer

Powered by FluxBB