Neither work well with N environments, even with channels tuned.   
Just to say that the age is showing through.

James

On Sep 23, 2007, at 10:32 AM, Garrett D'Amore wrote:

> Is your pcwl really cardbus?  Or is it 16-bit PCMCIA?
>
> The pcwl driver suffers from a bug that affects all PCI connected  
> chips, and, quite likely, would affect cardbus (32-bit) but not  
> impact 16-bit pcmcia.
>
> The pcwl driver needs a lot of work, but I have back-burnered that  
> effort into oblivion.  Maybe I should revive it.
>
> The pcan driver is, IMO, in better shape in this regard.
>
>    -- Garrett
>
> James Cornell wrote:
>> I have an IBM Thinkpad T30 with a Cisco Mini-PCI 350 series  
>> adapter  and a cardbus Lucent Orinoco WaveLan (Both 802.11b) that  
>> I am running  with OpenSolaris Developer Edition 04/07 (NV62 I  
>> believe) which seem  to be dropping connection when ifconfig iface  
>> dhcp is ran.  I have a  D-Link DI-624 802.11G router reset to  
>> factory settings with no  security, and I am using wificonfig -i  
>> iface connect dlink to connect  to the access point "dlink".  I  
>> have flashed the firmware on the 350  back to the recommended  
>> revision stated on the wlan page for  OpenSolaris by using the bin  
>> file and ACU on Windows.  Both adapters  are dropping connection  
>> and will not work with static or dhcp.  Oh,  and I was able to  
>> cause a kernel panic by removing the WaveLan from  the PCMCIA  
>> slot.  The kernel module for pcwl seems to get stuck and  is not  
>> removable with modunload -i id, even after I push the device   
>> down.  I am using the kernel modules bundled with OpenSolaris,  
>> not  the ones from the project page, although I have these too.   
>> Even if I  need to use a newer version of the drivers, I'm sure  
>> that it  disconnecting from the access point shouldn't be  
>> happening to both,  even with the stock drivers provided by the  
>> distribution.  Any ideas  what's wrong?  PS: Having WEP on makes  
>> no difference, setting the  keyindex, wepkey, and essid parameters  
>> still result in it  disconnecting with dhcp, and even after  
>> flushing routes and  statically configuring, neither work.
>>
>> James Cornell
>> Carcinogenic Studios
>> http://www.carcinogenic-studios.com
>> _______________________________________________
>> laptop-discuss mailing list
>> laptop-discuss at opensolaris.org
>>
>


Reply via email to