Thread: [Ndiswrapper-general] 1.0rc3 availabel (with AMD64 support)
Status: Beta
Brought to you by:
pgiri
From: Giridhar P. <gi...@lm...> - 2005-01-18 00:37:38
|
1.0rc3 is now available. It now supports AMD64 (in 64-bit). Only Broadcom has been tested with this. WEP works fine. However, wpa_supplicant seems to crash, so WPA doesn't work (yet). Another useful feature is that ndiswrapper now loads a driver/device only when necessary. So you can install as many drivers as you may ever use and ndiswrapper will load a driver only when you insert a card. This is also useful for some drivers that install many devices (e.g., Centrino). NOTE: This version changes .conf files installed by Windows drivers. So you must reinstall Windows drivers; otherwise ndiswrapper won't work. You can do this by "ndiswrapper -e <driver>" and install the driver again. -- Giri |
From: Giridhar P. <gi...@lm...> - 2005-01-18 02:36:36
|
I forgot to mention: Karl Vogel did amazing work with stubs to call Linux functions from Windows and vice versa as the parameters are passed differently in Windows and Linux with amd64. Without his work, this wouldn't have been possible. Thanks Karl, Giri |
From: Jonathan B. <be...@gm...> - 2005-01-19 16:46:40
|
On Mon, 17 Jan 2005 21:36:07 -0500, Giridhar Pemmasani <gi...@lm...> wrote: > I forgot to mention: > > Karl Vogel did amazing work with stubs to call Linux functions from > Windows and vice versa as the parameters are passed differently in > Windows and Linux with amd64. Without his work, this wouldn't have > been possible. > > Thanks Karl, > > Giri Way to go! It now works with x86_64! Had it working with 128-bit WEP and everything. Great work Giri and Karl. I haven't been able to get it to work with a stock FC3 kernel, but it worked great with one that I custom compiled to not have CONFIG_DEBUG_SPINLOCK. I'm thinking that is the problem, since I've tried it on the stock kernel of the same version. I'll try compiling the latest kernel without this flag to make sure it works with the latest kernel. I just sent a bugzilla report asking for the removal of the CONFIG_DEBUG_SPINLOCK option from the Fedora kernels. We'll see what happens. Great work anyway. I look forward to using my wireless again! Jonathan |
From: Lorenzo M. <lor...@gm...> - 2005-01-18 20:48:50
|
> 1.0rc3 is now available. It now supports AMD64 (in 64-bit). Only > Broadcom has been tested with this. WEP works fine. However, > wpa_supplicant seems to crash, so WPA doesn't work (yet). As I (wrongly) wrote in another thread, I have problems with this version. it doesn't set the SSID using iwconfig wlan0 essid maxxer the module loads fine, the interface is fine and you can set the ip, I can set mode managed or mode ad-hoc, but I can't set the ssid! all the times I tried it worked only once, just right after setting ad-hoc mode. but then I repeated and it didn't work! :( I'm using netbc564 driver for a broadcom 4306 card. maxxer |
From: Lorenzo M. <lor...@gm...> - 2005-01-18 20:49:24
|
> I'm using netbc564 driver for a broadcom 4306 card. I forgot to say I'm on a 64bit system, with Debian unstable. cheers |
From: Karl V. <kar...@se...> - 2005-01-19 08:38:11
|
Lorenzo Milesi <lor...@gm...> wrote in news:29c...@ma...: > the module loads fine, the interface is fine and you can set the ip, I > can set mode managed or mode ad-hoc, but I can't set the ssid! > all the times I tried it worked only once, just right after setting > ad-hoc mode. but then I repeated and it didn't work! :( Try compiling with 'make DEBUG=2' to get some more logging. I've only tried 'mode managed' on my system. Worked without problems for unencrypted, WEP and WPA. I take it that 'iwlist scan' shows your network? > I'm using netbc564 driver for a broadcom 4306 card. Which is the driver I use on my system. |
From: Lorenzo M. <lor...@gm...> - 2005-01-19 08:53:26
|
> Try compiling with 'make DEBUG=2' to get some more logging. I did with debug=3 but nothing more appeared > I've only tried 'mode managed' on my system. Worked without problems for > unencrypted, WEP and WPA. Even in "managed" I can't change the essid. > I take it that 'iwlist scan' shows your network? Actually I don't have an AP to test. I will asap. I will also try downloading "official" snapshot instead of the cvs, maybe something changes. cheers maxxer |
From: Lorenzo M. <lor...@gm...> - 2005-01-19 15:06:05
|
I downloaded CVS right now, and tried again. > Try compiling with 'make DEBUG=2' to get some more logging. done, DEBUG=3 btw in dmesg nor in messages I see anything strange but load messages. > I take it that 'iwlist scan' shows your network? I tried doing so, with an external PCMCIA card in ad-hoc, and it shows me the card!! But still it doesn't set the ssid. |
From: Jonathan B. <be...@gm...> - 2005-01-19 16:15:44
|
On Tue, 18 Jan 2005 21:48:39 +0100, Lorenzo Milesi <lor...@gm...> wrote: [snip] > it doesn't set the SSID using > iwconfig wlan0 essid maxxer > > the module loads fine, the interface is fine and you can set the ip, I > can set mode managed or mode ad-hoc, but I can't set the ssid! > all the times I tried it worked only once, just right after setting > ad-hoc mode. but then I repeated and it didn't work! :( I saw this too. After issuing the above command to set the SSID, try this command and see what happens: iwconfig wlan0 essid on After that, mine worked just fine. Also, I think once I had to switch the security from restricted to open to see the SSID set: iwconfig wlan0 key open Just some things to try. They worked for me. > I'm using netbc564 driver for a broadcom 4306 card. > > maxxer Jonathan |
From: Lorenzo M. <lor...@gm...> - 2005-01-20 12:03:26
|
> I saw this too. After issuing the above command to set the SSID, try > this command and see what happens: > iwconfig wlan0 essid on > After that, mine worked just fine. Also, I think once I had to switch > the security from restricted to open to see the SSID set: No way. no changes. > iwconfig wlan0 key open this gives me an error: Error for wireless request "Set Encode" (8B2A) : SET failed on device wlan0 ; Invalid argument. iwconfig wlan0 key off gives no error message, but still no changes. I can't set the essid. :( |