Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
>> jerry writes: >>> I didn't have time yesterday to followup on this. You do >>> not use Wine to run a driver. >> >> yes, i know. the wine directory is just where the download >> put the stuff. i thought that i needed to run WG511v2.exe >> to get the .sys and .inf files but that didn't work. >> >>> Many times a Windows driver is distributed in a self >>> extracting archive. To run the driver under NDISWRAPPER, you >>> must first extract the Windows .sys and .inf files. Not sure >>> what chip that Netgear uses, but in the case of the Broadcom >>> chips, there is a native Linux driver, but that requires >>> that you install the firmware that must be extracted from >>> the .sys file. If I have the time today I'll take a look >>> online and see if I can help. >> >> in the ubuntu forums i found reference to a marvel driver >> supposedly suitable to my card, and downloaded these files: >>> >> mrv8335.cat >> mrv8335.inf >> MRV8335NT.sys >> MRV8335XP.sys >> >> and successfully installed them in ndiswrapper. ndiswrapper >> -l gives: >> >> mrv8335 : driver installed >> device (11AB:1FAA) present >> >> which looks good. dmesg shows the following: >> >> [ 20.592000] ndiswrapper: using IRQ 9$ >> [ 20.864000] wlan0: ethernet device 00:14:6c:75:56:ca using NDIS driver: mrv83 >> [ 20.864000] wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2 >> [ 20.864000] usbcore: registered new interface driver ndiswrapper$ >> [ 20.904000] ndiswrapper: changing interface name from 'wlan0' to 'wlan1'$ >> >> [ 29.520000] ADDRCONF(NETDEV_UP): wlan1: link is not ready >> >> i don't know how to get rid of this last message. route >> shows: >> >> Destination Gateway Genmask Flags Metric Ref Use Iface >> 192.168.0.0 * 255.255.255.0 U 0 0 0 wlan1 >> default netgear 0.0.0.0 UG 0 0 0 wlan1 >> >> and ifconfig: >> >> wlan1 Link encap:Ethernet HWaddr 00:14:6C:75:56:CA >> inet addr:192.168.0.22 Bcast:192.168.0.255 Mask:255.255.255.0 >> UP BROADCAST MULTICAST MTU:1500 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >> Interrupt:9 Memory:38010000-38020000 >> >> still, it doesn't work. > > Do you use a dynamic or static IP address. Also what does iwconfig say. > It looks like things are working.
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |