Thread: [Ndiswrapper-general] WUSB54G improvements
Status: Beta
Brought to you by:
pgiri
From: Jan K. <jan...@we...> - 2004-10-20 16:35:36
Attachments:
smime.p7s
|
Hi all, some users and the developer himself were suffering from various, more or less sporadic problems of Linksys WUSB54G devices (maybe other Prism54-based as well, like Netgear WG121). A few days ago, I discovered that an originally required but now likely unneeded device reset during startup was the source - at least on my systems. I replaced it with a short delay, and everything seems to be fine now. I would like to invite any USB device user to verify if this change improved anything AND didn't break other devices. Please grab the latest cvs version (see http://ndiswrapper.sourceforge.net/wiki/index.php/Installation), give it a try, and report any problems. Thanks, Jan NOTE: The changes do not effect non-USB devices in any way! |
From: Hugo V. <hu...@bo...> - 2004-10-20 18:18:23
|
Hi Jan, It doesn't seem to work for me. When connecting the AP is detected but it can't connect. I'm using WEP, that maybe an issue. When I do a iwpriv wlan0 ndis_reset and restart the net.wlan0 script, the AP is found and wlan0 works as it should. I'll fiddle around with it some more. My box is a pvr with mythtv on it and it only turns on when recording or updating tv schedules or when I want it to. I'm currently on ndiswrapper 0.10, which seems to be the most stable situation for me. All newer versions crash more often when initializing. Oh and ofcourse no ehci-hcd for me :) Hugo Jan Kiszka wrote: > Hi all, > > some users and the developer himself were suffering from various, more > or less sporadic problems of Linksys WUSB54G devices (maybe other > Prism54-based as well, like Netgear WG121). > > A few days ago, I discovered that an originally required but now likely > unneeded device reset during startup was the source - at least on my > systems. I replaced it with a short delay, and everything seems to be > fine now. > > I would like to invite any USB device user to verify if this change > improved anything AND didn't break other devices. Please grab the latest > cvs version (see > http://ndiswrapper.sourceforge.net/wiki/index.php/Installation), give it > a try, and report any problems. > > Thanks, > Jan > > > NOTE: The changes do not effect non-USB devices in any way! |
From: Jan K. <jan...@we...> - 2004-10-21 07:02:21
Attachments:
smime.p7s
|
Hugo Visser wrote: > Hi Jan, > > It doesn't seem to work for me. When connecting the AP is detected but > it can't connect. I'm using WEP, that maybe an issue. When I do a iwpriv Well, WEP is no problem in my case, I just didn't tried WPA yet. > wlan0 ndis_reset and restart the net.wlan0 script, the AP is found and > wlan0 works as it should. > Maybe it is just some remaining startup issue. E.g., the delay I inserted at the point the reset used to happen had to be 3 s on my via box while 1 s was already enough on my notebook. Try to increase it in wrapper.c, ndis_init_one_usb() (don't have the line number at hand). There is also one remaining issue I still have to catch with a watchdog script: the driver forgets all its settings after disassociating. Maybe it already does it during certain setup phases. What is the output of iwconfig after the first unsuccessful connection attempt? I'm planning dig again in this area later. > I'll fiddle around with it some more. My box is a pvr with mythtv on it > and it only turns on when recording or updating tv schedules or when I > want it to. I'm currently on ndiswrapper 0.10, which seems to be the > most stable situation for me. All newer versions crash more often when > initializing. Oh and ofcourse no ehci-hcd for me :) > Please try the full program: ehci-hcd and long-term tests after getting the driver to run (with explicite reset or whatever). For me, also some rare hangups dissapeared (uptime is currently 2 days), likely due to improvements Giri recently added. Jan |
From: Hugo V. <jo...@sc...> - 2004-10-28 18:38:25
|
Okay, I finally found some time to continue testing. I've added the iwpriv wlan0 ndis_reset to the startup scripts and that does the trick. I'm running yesterdays cvs now. I did have to revert this change http://cvs.sourceforge.net/viewcvs.py/ndiswrapper/ndiswrapper/driver/wrapper.c?r1=1.284&r2=1.285 or else it gave me an error (invalid ioctl). All seems pretty stable now. I still have to test with ehci-hcd. If I run into any issues with that I'll report back :) Hugo Jan Kiszka wrote: > Hugo Visser wrote: > >> Hi Jan, >> >> It doesn't seem to work for me. When connecting the AP is detected but >> it can't connect. I'm using WEP, that maybe an issue. When I do a iwpriv > > > Well, WEP is no problem in my case, I just didn't tried WPA yet. > >> wlan0 ndis_reset and restart the net.wlan0 script, the AP is found and >> wlan0 works as it should. >> > > Maybe it is just some remaining startup issue. E.g., the delay I > inserted at the point the reset used to happen had to be 3 s on my via > box while 1 s was already enough on my notebook. Try to increase it in > wrapper.c, ndis_init_one_usb() (don't have the line number at hand). > > There is also one remaining issue I still have to catch with a watchdog > script: the driver forgets all its settings after disassociating. Maybe > it already does it during certain setup phases. What is the output of > iwconfig after the first unsuccessful connection attempt? I'm planning > dig again in this area later. > >> I'll fiddle around with it some more. My box is a pvr with mythtv on >> it and it only turns on when recording or updating tv schedules or >> when I want it to. I'm currently on ndiswrapper 0.10, which seems to >> be the most stable situation for me. All newer versions crash more >> often when initializing. Oh and ofcourse no ehci-hcd for me :) >> > > Please try the full program: ehci-hcd and long-term tests after getting > the driver to run (with explicite reset or whatever). For me, also some > rare hangups dissapeared (uptime is currently 2 days), likely due to > improvements Giri recently added. > > Jan |
From: Jan K. <jan...@we...> - 2004-10-28 19:33:38
Attachments:
smime.p7s
|
Hugo Visser wrote: > Okay, I finally found some time to continue testing. I've added the > iwpriv wlan0 ndis_reset to the startup scripts and that does the trick. > I'm running yesterdays cvs now. I did have to revert this change > http://cvs.sourceforge.net/viewcvs.py/ndiswrapper/ndiswrapper/driver/wrapper.c?r1=1.284&r2=1.285 > or else it gave me an error (invalid ioctl). > This indicates that there is still something wrong with ndiswrapper for your setup. I both do not need the reset and the extended delay anymore to get it running on my via epia system with ehci-hcd. Actually, doing this reset was the reason for my crashes - strange. Did you try to extend the delay in ndis_init_one_usb (5*HZ or more)? > All seems pretty stable now. I still have to test with ehci-hcd. If I > run into any issues with that I'll report back :) > Looking forward to hearing your test results. Jan |
From: Hugo V. <jo...@sc...> - 2004-10-28 20:59:28
|
Hm strange. I've tried to extend the delay up to 15*HZ but I still get the same result. The AP is found but "cannot connect". Only after the iwpriv (if I change that part to 30*HZ again) it works...How can I check what's different before and after the ndis_reset? What is usefull output? I'm using a gentoo script for wireless setup, maybe that's doing strange things behind the scenes. I'll test with manual setup. I tried to load ehci-hcd with the cvs version but it crashed on start up. I still don't rule out an irq conflict with ehci. I ran windows on the box and pvr recording hung when the linksys was connected. Sometimes windows hung too... Hugo Jan Kiszka wrote: > Hugo Visser wrote: > >> Okay, I finally found some time to continue testing. I've added the >> iwpriv wlan0 ndis_reset to the startup scripts and that does the >> trick. I'm running yesterdays cvs now. I did have to revert this >> change >> http://cvs.sourceforge.net/viewcvs.py/ndiswrapper/ndiswrapper/driver/wrapper.c?r1=1.284&r2=1.285 >> or else it gave me an error (invalid ioctl). >> > > This indicates that there is still something wrong with ndiswrapper for > your setup. I both do not need the reset and the extended delay anymore > to get it running on my via epia system with ehci-hcd. Actually, doing > this reset was the reason for my crashes - strange. > > Did you try to extend the delay in ndis_init_one_usb (5*HZ or more)? > >> All seems pretty stable now. I still have to test with ehci-hcd. If I >> run into any issues with that I'll report back :) >> > > Looking forward to hearing your test results. > > Jan |
From: Jan K. <jan...@we...> - 2004-10-29 06:46:20
Attachments:
smime.p7s
|
Hugo Visser wrote: > Hm strange. I've tried to extend the delay up to 15*HZ but I still get > the same result. The AP is found but "cannot connect". > > Only after the iwpriv (if I change that part to 30*HZ again) it > works...How can I check what's different before and after the > ndis_reset? What is usefull output? > You may set the debug level to 3, but be warned, this produces a lot of messages and may even change the behaviour of the driver, i.e. it may simply work then. That was my experience and made it very hard to track down the problem. > I'm using a gentoo script for wireless setup, maybe that's doing strange > things behind the scenes. I'll test with manual setup. I tried to load > ehci-hcd with the cvs version but it crashed on start up. > Same here, try to set DEBUG=3 and watch what happens. In case your crash doesn't allow the system to write out the log, you may redirect it to a serial port. See linux/Documentation/serial-console.txt. > I still don't rule out an irq conflict with ehci. I ran windows on the > box and pvr recording hung when the linksys was connected. Sometimes > windows hung too... > Oh, if even Windows tend to crash, then there might be a real hardware problem or some bug in the Linksys driver. This make things much more difficult... @All WUSB54G user: Does anybody else tried latest ndiswrapper? Any problems discovered or any improvements? Jan |