From: Mario M. <mar...@ht...> - 2003-08-28 11:19:20
|
Hi, On 2003.08.26 18:57, Sven Riedel wrote: > On Tue, Aug 26, 2003 at 03:53:19PM +0200, Andreas Mohr wrote: > > On Mon, Aug 25, 2003 at 05:34:23PM +0200, Sven Riedel wrote: > > > On Mon, Aug 25, 2003 at 04:09:45PM +0200, Mario Mikocevic wrote: > > > > ps > > > > it's 0.1h > > > As of today it is, yes. And 0.1h seems to fix the ping bug (I can nmap > > > my access point now without having to reboot to get good pings back), > > > while introducing a slightly different bug - the card can only associate > > > with the AP roughly 50% of the time. When it doesn't find it, a complete > > > ifdown wlan0; rmmod acx100_pci; insmod acx100_pci; ifup wlan0 > > > cycle can get it to do a proper rescan and then (usually) finds it. > > Yup, I know :-\ > > But why rmmod?? A simple ifdown/ifup should fix this, too. > I've had a couple of instances where a ifup/ifdown cycle didn't help > any. rmmod/insmod did help though. Maybe it was just random chance that > made it work just at that point in time. So I was convinced that > ifup/ifdown didn't (always) help. > > > Not to mention even a simple iwconfig wlan0 essid <myessid>... > Ok, I've got to believe the developers with this one :) Ok, after few days of playing with 0.1h I came to conclusion that on 1 of 5 rate I can _successfully_ connect to AP after loading module so there must be something else involved too (that's why I asked for detailed instructions because I thought _I_ was doing something wrong). This is 650+ w/ thinkpad r40. ps I had a one _very_ scary moment, one rmmod hanged hard, even reset button did not help, I tried ejecting card and presto, linux was back alive _BUT_ 650+ was _dead_ that day ! Not even winxp wanted to work with it. Tried all sorts of things, nothing. The next day card worked fine again. **puzzled** -- Mario Mikocevic (Mozgy) mozgy at hinet dot hr It's never too late to have a good childhood! The older you are, the better the toys! My favourite FUBAR ... |