Thread: [Ndiswrapper-general] 1.1rc3 available
Status: Beta
Brought to you by:
pgiri
From: Giridhar P. <gi...@lm...> - 2005-02-26 19:36:19
|
1.1rc3 is now available for testing. Barring any show stoppers, this will be released as 1.1, so give it a try. -- Giri |
From: Jonathan B. <be...@gm...> - 2005-02-26 21:50:48
|
On Sat, 26 Feb 2005 14:35:46 -0500, Giridhar Pemmasani <gi...@lm...> wrote: > > 1.1rc3 is now available for testing. Barring any show stoppers, this will be > released as 1.1, so give it a try. > > -- > Giri Hi Giri, Thanks for your work, but this is still a no-go for me. I've tried with my latest kernel 2.6.10-1.766_FC3 and with a custom 760_FC3 built without CONFIG_DEBUG_SPINLOCK and ndiswrapper 1.1.rc3 causes a kernel oops in both cases. Attached are netconsole traces of the oops. I tried setting up a static IP in case something was strange with dhclient and it still didn't work. I get the oops after trying to set the IP: iwconfig wlan0 key open `cat key.txt` ifconfig wlan0 up ifconfig wlan0 192.168.0.100 # kernel oops On the 760 kernel without the spinlock thing I got a little further once. I brought eth0 down and was able to set a static IP and ping my router, but was not able to get out to the internet. I think I brought eth0 back up to compare, I don't remember exactly what I did, but it ended up with an oops. I have not been able to do that again. Karl Vogel suggested that I try kernel 2.6.11-rc3-mm2, so I downloaded the vanila kernel sources for 2.6.10 to try and see, but it isn't clear to me which patches I must apply in which order to which sources to get it to 11-rc3-mm2. Could someone give me some help here or point me to a site that shows what I must do. I tried just applying the 2.6.11-rc3-mm2 patch to the 2.6.10 sources, but it was not applying cleanly (some files it wanted to patch were not there and then there was some other message about a regressive (? I think that was the term) patch, at which point I decided to stop). Let me know what else I can do to try and help you track this down. I just starts to get a little tedious and slightly unnerving to have to hard reset my laptop every few minutes. Jonathan |
From: Giridhar P. <gi...@lm...> - 2005-02-26 22:03:55
|
Since I don't have amd64, I can't figure out what is wrong based on that info. As Karl suggested, you could try a kernel that he uses. I am going to commit a patch to clean up spinlocks (yes, yet another rewrite, but this time it will be much simpler and hopefully clean), that _may_ solve this problem, but no guarantees. This will be after 1.1 released though. -- Giri |
From: Frank Z. <fz...@au...> - 2005-03-02 18:49:20
|
Hi Giri, > Since I don't have amd64, I can't figure out what is wrong based on that > info. As Karl suggested, you could try a kernel that he uses. > > I am going to commit a patch to clean up spinlocks (yes, yet another rewrite, > but this time it will be much simpler and hopefully clean), that _may_ solve > this problem, but no guarantees. This will be after 1.1 released though. This patch works for me. It fixes all the interrupts related crashes I used to see. I have transfered a few gigabytes with no problem while before a simple ping would crash the host. config: compaq r3240us, suse 9.2 x86_64 (stock 2.6.10 kernel) with broadcom 4306 and 11mbs router. Thanks, Frank. |
From: Giridhar P. <gi...@lm...> - 2005-03-02 19:06:53
|
Please indicate when you got the CVS or snapshot and what patch you tried. Since things keep changing, sometimes hectically, unless you identify what code base you tried, it would be difficult to know what works. This time I assume that you tried latest cvs/snapshot. Contrary to my earlier comment, I did indeed commit the new spinlock implementation for 1.1, as the new implementation should solve any spinlock related crashes (without having hardware to test, it is difficult to know if crashes are due to spinlocks or other parts). I will prepare 1.1rc4 so people can test that and confirm if that works or not. Hopefully 1.1rc4 is the last rc for 1.1 -- Giri |
From: James S. <Sha...@ea...> - 2005-02-27 01:11:11
|
> I brought eth0 down and was able to set a static IP and ping my > router, but was not able to get out to the internet. Is this by chance one of those via motherboards? If you've got alsa setup for a via82xx chipset, you might also try bringing down the soundcard as well as eth0. And rmmod'ing the modules that correspond with them. /etc/init.d/alsasound stop ifconfig eth0 down rmmod 8139too rmmod mii rmmod snd-page-alloc rmmod rtc That's what I've got to do on my sony vaio laptop with a via motherboard/sound/usb in order to get my usb working somewhat reliably. It might help/work for your wireless as well. If not please ignore. I really wish via would get on the ball and help clear the air about their stuff. Until then I'm steering clear of anything via. You might also try a 2.4.x kernel as it appears to play better with at least my via motherboard. At least kernels >= 2.4.23. The 2.6 series seems to have stopped being useable since 2.6.7. You might also try some kernel parms. acpi=on apm=off pci=noacpi - James |
From: Ian M. <im...@gm...> - 2005-02-27 01:55:45
|
I just want to say it works great for me running latest 2.6.10 kernel from FC3, Linksys WPM54G with Broadcom 4306 chipset, WPA supplicant 0.38. Thanks for the great work on keeping us connected!! Regards, Ian On Sat, 26 Feb 2005 14:35:46 -0500, Giridhar Pemmasani <gi...@lm...> wrote: > > 1.1rc3 is now available for testing. Barring any show stoppers, this will be > released as 1.1, so give it a try. > > -- > Giri > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Ndiswrapper-general mailing list > Ndi...@li... > https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general > |
From: Jonathan B. <be...@gm...> - 2005-02-27 02:39:34
|
On Sun, 27 Feb 2005 14:55:34 +1300, Ian McDonald <im...@gm...> wrote: > I just want to say it works great for me running latest 2.6.10 kernel > from FC3, Linksys WPM54G with Broadcom 4306 chipset, WPA supplicant > 0.38. > > Thanks for the great work on keeping us connected!! > > Regards, > > Ian Hi Ian, Are you running 32-bit or 64-bit FC3? Jonathan |
From: Ian M. <im...@gm...> - 2005-02-27 02:54:53
|
32 bit On Sat, 26 Feb 2005 20:39:27 -0600, Jonathan Berry <be...@gm...> wrote: > On Sun, 27 Feb 2005 14:55:34 +1300, Ian McDonald <im...@gm...> wrote: > > I just want to say it works great for me running latest 2.6.10 kernel > > from FC3, Linksys WPM54G with Broadcom 4306 chipset, WPA supplicant > > 0.38. > > > > Thanks for the great work on keeping us connected!! > > > > Regards, > > > > Ian > > Hi Ian, > Are you running 32-bit or 64-bit FC3? > > Jonathan > |
From: Jonathan B. <be...@gm...> - 2005-02-27 02:57:10
|
On Sat, 26 Feb 2005 19:10:02 -0600, James Shatto <Sha...@ea...> wrote: > > I brought eth0 down and was able to set a static IP and ping my > > router, but was not able to get out to the internet. > > Is this by chance one of those via motherboards? No, it's an nForce3 motherboard, sorry :). > If you've got alsa setup for a via82xx chipset, you might also try bringing down the soundcard as well as eth0. And rmmod'ing the modules that correspond with them. At first that sounded familiar, but upon investigating some of the webpages of people who have similar laptops, I believe it uses the intel8x0 driver. I'm in Windows so I cannot check directly without rebooting. > /etc/init.d/alsasound stop > ifconfig eth0 down > rmmod 8139too > rmmod mii > rmmod snd-page-alloc > rmmod rtc I do use the 8139too network driver for my LAN card. Perhaps something to try, but that seems rather inconvinient just to use the wireless card. The thing is, I can get version 1.0 to work just fine for me, so it must be something that has changed in ndiswrapper since then that is causing problems. If only there wasn't a bad memory leak in 1.0, I would be happy :). > That's what I've got to do on my sony vaio laptop with a via motherboard/sound/usb in order to get my usb working somewhat reliably. It might help/work for your wireless as well. If not please ignore. > > I really wish via would get on the ball and help clear the air about their stuff. Until then I'm steering clear of anything via. My desktop has a VIA KT400 chipset and seems to do fairly well. I did have a lot of trouble with nVidia's drivers for the longest time, but that was before I was really into Linux. I really like what nVidia is doing with their nForce chipsets, though, so I'll probably go with that when it comes time to upgrade my desktop again. > You might also try a 2.4.x kernel as it appears to play better with at least my via motherboard. At least kernels >= 2.4.23. The 2.6 series seems to have stopped being useable since 2.6.7. You might also try some kernel parms. acpi=on apm=off pci=noacpi I'm afraid that none of these are options for me. 2.6 seems to have much better support for x86_64 and FC3 uses many things (udev comes to mind) that I think are only on 2.6 series. I need ACPI for CPU frequency scaling, and I don't think this laptop even has APM. > - James Thanks anyway, Jonathan |
From: Ian M. <im...@gm...> - 2005-02-27 03:05:03
|
> I do use the 8139too network driver for my LAN card. Perhaps > something to try, but that seems rather inconvinient just to use the > wireless card. The thing is, I can get version 1.0 to work just fine > for me, so it must be something that has changed in ndiswrapper since > then that is causing problems. If only there wasn't a bad memory leak > in 1.0, I would be happy :). > If I was you then I would start trying all the versions to find out where it broke - take nightly CVS snapshots if necessary and then you should be able to find the broken code or the general area reasonaly quickly.... Start in the middle between 1.0 and 1.1rc3 and then work back or forwards as relevant.... |
From: Jim C. <jc...@di...> - 2005-03-01 16:30:03
|
Giridhar Pemmasani wrote: >1.1rc3 is now available for testing. Barring any show stoppers, this will be >released as 1.1, so give it a try. > > > works for me, on 2.6.10, on 2 different belkin/realtek 8180 cards (pci, pcmcia) using realtek's driver (version 173) both cards are already on wiki as successful w earlier versions. thanks. |
From: Jonathan B. <be...@gm...> - 2005-03-02 16:00:09
|
On Tue, 01 Mar 2005 02:55:26 -0500, Giridhar Pemmasani <gi...@lm...> wrote: > > The following patch against latest cvs should work I think. If it > doesn't, I don't think I can do much to solve this problem. I need to > know if this works or not soon to decide if this will go into 1.1 or > not. > > -- > Giri Well, I wasn't sure exactly what to apply your patch to, so I checked out CVS yesterday, which seemed like maybe it already had the patch applied, and that didn't work. I checked out CVS again today, and it seems to be working! I did a diff on the current nightly, and it is the same as that. I'm very cautiously using my network right now : ). It just finished copying a 600 MB iso with apparently no probelms. I'm trying it again the other way now. It seems to be working great! I'd say, barring any disasters elsewhere, this is ready to go 1.1. I'll let the R3000 group know so they can also begin testing. This is a hot topic there. Thanks for all your work, and sorry I haven't been more help. Jonathan |
From: Frank Z. <fz...@au...> - 2005-03-02 19:18:42
|
Giridhar Pemmasani wrote: > Please indicate when you got the CVS or snapshot and what patch you > tried. Since things keep changing, sometimes hectically, unless you identify > what code base you tried, it would be difficult to know what works. This time > I assume that you tried latest cvs/snapshot. This was from the current CVS tree, with no change. The most recent committed patch has the following entry: 2005-03-01 18:46 pgiri * driver/wrapper.c: In alloc_packet, initialize all sg elements only when use_sg_dma is set. > Contrary to my earlier comment, I did indeed commit the new spinlock > implementation for 1.1, as the new implementation should solve any spinlock > related crashes (without having hardware to test, it is difficult to know if > crashes are due to spinlocks or other parts). I will prepare 1.1rc4 so people > can test that and confirm if that works or not. Hopefully 1.1rc4 is the last > rc for 1.1 > All the crashes I saw were spinlock/irql level related. They were also very close to the oops other r3000 owners posted. I tried this new version because I saw you had committed some spinlock work. Frank. |
From: Giridhar P. <gi...@lm...> - 2005-03-02 19:36:27
|
On Wed, 02 Mar 2005 13:18:34 -0600, Frank Zago <fz...@au...> said: Frank> 2005-03-01 18:46 pgiri Frank> * driver/wrapper.c: In alloc_packet, initialize all sg elements Frank> only when use_sg_dma is set. Ok, thanks. By then new spinlock implementation was already committed, so you tested with that. Although, I just noticed a bug with spinlocks in couple of functions; it is fixed in latest snapshot. Presumably your driver doesn't use the functions that had this bug. I will prepare 1.1rc4 later today. -- Giri |