--- Aaron Griffin <[EMAIL PROTECTED]> wrote:

> On 1/31/06, James Rayner <[EMAIL PROTECTED]> wrote:
> > Thats unfortunately the way ndiswrapper works.
> Some drivers work with
> > it others dont. I tried three different windows
> drivers with this
> > wireless network card, each with varying results
> and stability.
> 
> I have to side with James here.  If ndiswrapper
> segfaults, it's not
> due to an SMP kernel, even though the ndiswrapper
> devs will tell you
> so.  I have two machines which use ndiswrapper for
> wireless.  The
> first one works perfectly, and has worked perfectly
> for over a year
> (except for v1.5, which messed up everyone). 
> Another machine has
> never been able to work with ndiswrapper... I can
> connect and get an
> IP and ping things just fine, but as soon as I begin
> downloading
> anything (pacman -Sy) it immediately segfaults the
> kernel.  I have
> tried with SMP and non-SMP kernels.
> 
> It's just the way ndiswrapper works.  If a company
> does not support
> native linux drivers, don't support them.  If you
> have the capability,
> do not use ndiswrapper.  It's a hack.  That's the
> point.
> 
> _______________________________________________
> arch mailing list
> [email protected]
> http://www.archlinux.org/mailman/listinfo/arch
> 
I get a panic as soon as I do an ifconfig on wlan0.
What you say is true, however SiS have a mention of a
Linux SDK for this chip it appears to be invisible, or
vaporware. My problems arise because my r8180 pcmcia
card is unstable on recent kernels so I borowed the
D-link from the desktop and that means I try to get
ndiswrapper going. I will search for other drivers,
that can make a big difference.


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch

Reply via email to