Re: Atmel-wlan-usb Digest, Vol 2, Issue 6

Thanks for the advice.  I will try the new drivers.
But,  I'd also like to be able to test the network
and bring it back up if its down.  Could I take
a look at your ifup/ifdown scripts?  I am more
familiar with Solaris, which has down and plumb 
options on the ifconfig command.  But,  Linux does
not appear to have a plumb option on ifconfig or
iwconfig.  How do you do it?

Also,  maybe after I unplumb the interface might take
care of the next option, but I can not rmmod usbvnetr.
I get an error saying its busy.

Thanks,

Mike

----------------------------------------------------------------------
> 
> Message: 1
> Date: Thu, 13 Nov 2003 23:00:28 -0500
> From: Dossy <dossy-Nz0poiq8MPVWk0Htik3J/[email protected]>
> Subject: Re: [Atmel-WLAN-USB] Restarting Wireless
> Link
> To: atmel-wlan-usb-ikZNBd7uB5wQUIZIPwn63sWURRETrGNnG9Ur7JDdleE@public.gmane.org
> Cc: [email protected]
> Message-ID: <20031114040028.GP12771-Nz0poiq8MPVWk0Htik3J/[email protected]>
> Content-Type: text/plain; charset=us-ascii
> 
> On 2003.11.10, Mike Smith <easygreenus-/[email protected]>
> wrote:
> > 
> > I am using a Linksys WUSB11 V2.6 on a system I
> keep running 24x7.  Its
> > running Redhat 8.0.  The link will stay up
> sometimes for 1, 2, or even
> > 3 weeks.  But,  for some reason,  it will loose
> its connection.  The
> > only way I've found to bring the wireless link
> back up is a reboot.
> > Its configured as eth0.  ifdown eth0 and ifup eth0
> have no effect.
> > /etc/init.d/network stop/start/reload has not
> effect.
> > 
> > How can I bring this link back up without
> rebooting?  
> > 
> > I'm running the April 16, 2003 version of the
> atmelwlandriver.  
> 
> I also have a WUSB11 V2.6 and was previously using
> the atmelwlandriver.
> I'd encountered the same problem: after some time,
> it would go dead.
> Bringing the link back here involved doing a
> ifdown/ifup combo -- my
> if{up,down} scripts unplumb the wireless interface
> and rmmod/insmod the
> usbvnetr module.
> 
> Back on October 22, I was able to get the at76c503
> driver working after
> patching the source to use the older 0.90.2-140
> firmware (the 1.101.0-84
> firmware didn't seem to turn the radio on for my
> particular WUSB11 V2.6
> -- my guess is there's a bug in that newer
> firmware).
> 
> The wireless link has been up consistently since
> October 22 and it's
> currently November 13 -- just over 3 weeks now.  If
> you're using the
> WUSB11 V2.6 and require reliability, I strongly
> suggest switching to the
> at76c503-rfmd driver.  If you find that your WUSB11
> V2.6 also doesn't
> seem to turn the radio on with the stock compile,
> try changing the
> #include to use the older firmware, changing:
> 
> #include "fw-rfmd-1.101.0-84.h"
> 
> to:
> 
> #include "fw-rfmd-0.90.2-140.h"
> 
> Works like a charm after that.
> 
> Good luck,
> 
> -- Dossy
> 
> -- 
> Dossy Shiobara                       mail:
> dossy-Nz0poiq8MPVWk0Htik3J/[email protected] 
> Panoptic Computer Network             web:
> http://www.panoptic.com/ 
>   "He realized the fastest way to change is to laugh
> at your own
>     folly -- then you can let go and quickly move
> on." (p. 70)
> 
> 
> ------------------------------

__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree