http://bugzilla.novell.com/show_bug.cgi?id=569663 http://bugzilla.novell.com/show_bug.cgi?id=569663#c5 Daniel Morris <danielm@ecoscentric.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|danielm@ecoscentric.com | --- Comment #5 from Daniel Morris <danielm@ecoscentric.com> 2010-01-15 11:05:59 UTC --- None of this works in a straightforward manner! But does in the end ;-) Or more specifically, I erased all copies of ndiswrapper* from the machine with zypper, and just for kicks did a reboot. # uname -a Linux mach 2.6.31.8-0.1-desktop #1 SMP PREEMPT 2009-12-15 23:55:40 +0100 i686 i686 i386 GNU/Linux # zypper in ndiswrapper Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW packages are going to be installed: kernel-default-base ndiswrapper ndiswrapper-kmp-default As you may notice/infer, that dependency is wrong, as it installs /lib/modules/2.6.31.5-0.1-default/updates/ndiswrapper.ko from ndiswrapper-kmp-default even though I'm running the desktop kernel. Manually symlinking into 2.6.31.8-0.1-desktop & depmod'ing, yields:- # modprobe ndiswrapper FATAL: Error inserting ndiswrapper (/lib/modules/2.6.31.8-0.1-desktop/updates/ndiswrapper.ko): Invalid module format So I manually removed the symlink, # zypper in ndiswrapper-kmp-desktop and modprobe succeeded. Happy days (more so, 'cos the cable guys have rewired me and I no longer need to use ndiswrapper to kludge M$ drivers). Just in case anyone is searching for this, I'm really impressed that the ndiswrapper solution actually works, even having WPA2 support from my cheapie ebuyer Tenda WA-T1, which was only bought "just in case" as it was effectively free as it brought an order up to the free shipping level. I 'll try to submit this to the ndiswrapper database as it says WPA2 doesn't work. # ndiswrapper -l netmw225 : driver installed device (1286:1FAB) present Configuration was simple entering the WPA2 key using NetworkManager within KDE-4.3.1. Going back to the bug description, I suppose the post-install script works out that the modules installed don't match the running kernel and thus skipped creating a symlink, a workaround is documented above and I'll leave the report for a developer/maintainer to decide how best to resolve/close. Thanks Marcus & Michal for your help. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.