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
