[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: wireless on Debian



I just wrote a tutorial on how I got mine working.  It is a Broadcom 
Corporation Dell Wireless 1390 WLAN Mini-PCI Card, though and not a 
4318.  It may be a different way of going about it ie a patch that is 
necessary.  If you want a write up on the tutorial let me know- I can 
attach it on a reply.


On Fri, Mar 02, 2007 at 08:29:15PM -0800, Freddy Freeloader wrote:
> Hardware configurations sure makes a difference.  I just loaded the
> bcm43xx module and blacklisted ndiswrapper. My system became absolutely
> unusable for accomplishing anything.  The mouse cursor freezes
> intermittently, windows not maximized jump around on the desktop, and
> all the while cpu usage never goes beyond about 2%.  
> 
> I sure would like to see the configuations of anyone who can use the
> bcm43xx module with the broadcom 4318 chip and wpa_supplicant.  I'd much
> rather use the open source module than the Windows drivers, but it just
> seems to be impossible on my system.
> 
> On Fri, 2007-03-02 at 19:52 -0600, Mr Alk3 wrote:
> > I am using WEP encryption, but can set up WPA etc etc.  I did notice 
> > that when I was configuring the interface to connect to the WEP 
> > encrypted AP that it wasn't finding any of the WEP access point in the 
> > area.  I might have to change my AP to use WPA as I am seeing that most 
> > people are getting bcm43xx working with WPA and not WEP.  I could be 
> > wrong though.
> > 
> > On Sat, Mar 03, 2007 at 01:23:14AM +0100, pinniped wrote:
> > > 
> > > I know there's a section on how to set up wireless stuff in the Debian docs 
> > > but I can't find it at the moment.
> > > 
> > > Anyway, if you use PSK-TKIP, look here for an example:
> > > http://wiki.debian.org/Manual-Howto#head-6fdd87d329e68a583e5fde32c6b21e460e5541a5
> > > 
> > > If you use WPA-PSK (default on WinDos and therefore on most AP applicances) 
> > > then you also need the 'wpa supplicant' software -  with somne hardware, 
> > > everything needs to be done through that, but with other hardware things 
> > > are managed magically through the 'interfaces' file but you still need to 
> > > install the supplicant to generate a key using the wpa_passphrase tool. 
> > > for example, my entry in 'interfaces' looks something like this:
> > > 
> > > auto eth2  (yes, the driver calls it eth2 rather than wlan0)
> > > allow-hotplug eth2
> > > iface eth2 inet dhcp
> > > wpa-conf managed
> > > wpa-ssid goaway
> > > wpa-key-mgmt  WPA-PSK
> > > wpa-psk  blahbalhablhablahblahablhablah (the key)
> > > 
> > > To generate the key:
> > > wpa_passphrase SSID PASSPHRASE  -- so:
> > > wpa_passphrase goaway thisISthePASSphrase
> > > 
> > > 
> > > 
> > > -- 
> > > To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
> > > with a subject of "unsubscribe". Trouble? Contact 
> > > listmaster@lists.debian.org
> > > 
> > 
> > 
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-laptop-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 



Reply to: