[nSLUG] Re: X freeze, clock weirdness: Connected? Cause?

Donald Teed donald.teed at gmail.com
Wed Jun 1 19:00:43 ADT 2005

Don't forget to try a CMOS reset.  Your motherboard
manual will cover how that is done.

I've seen a few cases where a Asus P2B
or P3B was having strange problems detecting drives
or booting up, and there was better behaviour
after a CMOS reset.

You also mentioned that you have a wireless
card.  If that is being supported by ndiswrapper,
it's the end of the story.  That is a flaky
driver.  The developer doesn't know how
to include kernel stack dump capture code
(the answer I got was: "that would require
reading"), and so when there is a crash with
ndiswrapper module, you will just get a freeze.
The lock ups from ndiswrapper go back
many versions - the lack of useful
diagnostics is helping to perpetuate this


More information about the nSLUG mailing list