|
Bugzilla – Full Text Bug Listing |
| Summary: | SCPM disappears, then locks upon re-enabled | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Wade Winright <wade.winright> |
| Component: | YaST2 | Assignee: | Joachim Gleissner <joachim.gleissner> |
| Status: | RESOLVED WONTFIX | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Major | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | SuSE Linux 10.0 | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | |||
| Bug Blocks: | 143273 | ||
| Attachments: |
y2log for scpm dying
/var/log/scpm hwinfo |
||
|
Description
Wade Winright
2005-10-25 16:50:51 UTC
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. :) |