Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Nils Breunese <breun@xs...> - 2005-03-13 23:15:46
First of all, thanks so much for creating ndiswrapper! Without it I
wouldn't have been able to use my wireless card, an Asus WL-138G PCI
card which has the Marvell Libertas chipset. I'm currently using
ndiswrapper 1.1rc1 on a Fedora Core 3 system.
I use 'make rpm' to build my own rpms and modprobing ndiswrapper after
logging in using a standard Fedora kernel (a 4K stacks kernel!) works
fine for me. However, if I add ndiswrapper to modprobe.conf my systems
hangs when modprobing ndiswrapper during the startup sequence most of
the time. Sometimes it does work though. My current setup doesn't
automatically modprobe ndiswrapper, I do this manually after logging in,
I find this works just fine every time.
Sadly ndiswrapper 1.1rc2 and later (I tried rc2, rc3 and the final
release) don't work for me. Today I built rpms from the final release.
Modprobing ndiswrapper seems to work, but then when I start an app that
uses the internet connection my system hangs. Any reason why ndiswrapper
might have stopped working for me after 1.1rc1? For now I will stick
with 1.1rc1, I just hope it keeps working for me (also with future
It is a known issue (see Bug reports). However, to fix this, debug
trace (see wiki Bugs page) showing what causes the crash and the oops
trace itself are needed. If someone with this chipset can provide the
trace, it would help. Use latest snapshot/CVS.
On Monday 14 March 2005 03:18, Giridhar Pemmasani wrote:
> It is a known issue (see Bug reports). However, to fix this, debug
> trace (see wiki Bugs page) showing what causes the crash and the oops
> trace itself are needed. If someone with this chipset can provide the
> trace, it would help. Use latest snapshot/CVS.
I don't know if this is the same error but here are my logs.
This is with today's snapshot.
I also had problems with the 1.1 release version oopsing the kernel, but i
can't reproduce that anymore.