My Lenovo 3000 c200 doesn't work correctly in Ubuntu 7.10 (Wireless indicator and Switch and Heat Control)
Bug #160661 reported by
faqlcp
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux-source-2.6.22 (Ubuntu) |
Invalid
|
Undecided
|
Brian Murray | ||
Bug Description
Early, I upgrade my system from Feisty Fawn to Gutsy Gibbon and appear some problems.
First, the Wireless button and the indicator doesn't work properly. The Wireless indicator always is off and when I try to switch off the wireless (not with a toggle hotkey), then the indicator is always on. This is a minor problem, but, the next problem is serious.
I noticed an excessive overheating in my laptop (the sensor applet show a temp among 51 C and 61 C, and before upgrade, the sensor applet show a temp among 48 C and 51 C), and the fan speed doesn't change.
All of this problems solve if I suspend the laptop and restore newly, but sometimes the suspend process crash and I have to force the shutdown.
| description: | updated |
Revision history for this message
| Brian Murray (brian-murray) wrote | #1 |
Revision history for this message
| Brian Murray (brian-murray) wrote | #2 |
| Changed in linux-source-2.6.22: | |
| status: | Incomplete → Invalid |
Revision history for this message
| dpecile (dpecile) wrote | #3 |
Revision history for this message
| dpecile (dpecile) wrote | #4 |
Revision history for this message
| dpecile (dpecile) wrote | #5 |
Revision history for this message
| dpecile (dpecile) wrote | #6 |
To post a comment you must log in.
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include as attachments the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
4. Please run the command 'sudo dmidecode > dmidecode.log' and attach the resulting file 'dmidecode.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https:/