Bugzilla – Bug 130533
SCPM disappears, then locks upon re-enabled
Last modified: 2006-02-09 16:41:31 UTC
After successfully setting up SCPM to switch between 3 profiles, things worked normally for a while. I set up the ndiswrapper for the wireless interface prior to getting SCPM enabled and running. One day when the wireless card locked up the host, I rebooted the machine and my SCPM settings were gone. I attempted to re-enable SCPM, and it just hung, 0% for many minutes (an hour or so), and I had to kill the process to get it to quit. Thinking that this was some legacy leftover thing from doing an OS upgrade instead of a clean install, I nuked and paved the system. I've had it running well again for about a week, and the exact same thing has happened again. Please help me make this work, as I need this laptop!!! Thanks!!
Created attachment 55344 [details] y2log for scpm dying
SCPM and ndiswrapper are Joachim's.
Did the crash occur while switching a profile or during normal operation?
The system seems to crash when switching profiles. After which all of the SCPM data was no longer found. THen when trying to set it up again, when I enable SCPM, it never starts to enable, just sits at "0%" complete.
Does 'scpm recover' help?
This is what I see: # scpm recover SCPM: scdb not available
Could you run 'scpm -d recover' and attach /var/log/scpm afterwards?
Created attachment 55532 [details] /var/log/scpm
It seems there is no database at all. Do you have anything in directory /var/lib/scpm/scdb?
linux:/var/lib/scpm/scdb # ls -l total 0 drwxr-xr-x 2 root root 20 2005-09-12 18:12 . drwxr-xr-x 7 root root 108 2005-10-25 08:40 .. -rw-r--r-- 1 root root 122575 2005-10-25 08:16 scdb.db
Ok, the file is there. Maybe it got corrupted by the crash. Could you e-mail it to me?
Conclusion of database check: The crash seems to have caused a filesystem corruption and destroyed the file. Is there a kernel oops of the crash in /var/log/messages? Could you attach 'hwinfo --netcard'?
Created attachment 55611 [details] hwinfo
You have a Broadcom WLAN card, so you're unfortunately stuck to ndiswrapper. It may be worth a try to use another version of the Windows driver. If that doesn't help, you could also try a newer ndiswrapper version.
FYI: The kernel-of-the-day (ftp://ftp.suse.com/pub/projects/kernel/kotd/i386/HEAD/...) has a newer ndiswrapper version, just in case you want to give it a try and don't dare to compile it yourself.
Closing as WONTFIX. Hope you had success with a newer ndiswrapper. :)