No Dothan centrino speed step in Feisty Beta

Bug #98552 reported by Maxrom
6
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I reported a problem with speed step on my Dothan 1.8ghz centrino laptop in bug 90744 that was rejected, suggesting that the Dothan cpu tables are not in the upstream linux kernel. That was for Feisty H5, but the problem still persists in the recently released Feisty Beta.

For 7.04 to be usable for Dothan based laptops, this needs to be resolved, but I need advice on how to notify the maintainers of this, to ensure the final version will have this included.

This bug prevents Dothan hardware from running 7.04 acceptably.

description: updated
Revision history for this message
Djembe (djemberob) wrote :

I had the same issue, but got it fixed by changing from the default 2.6.20-14-generic kernel to the 2.6.20-14-386 version. Speedstep is now working fine both plugged in and unplugged! :)

Revision history for this message
medo (mhalawah) wrote :

Well using 386 is not a solution. We need to get 2.6.20-14-generic fixed. My laptop has 1.5G centrino and missing the speed step

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Now that the 7.10 Gutsy Gibbon release of Ubuntu is out, we were wondering if you can still reproduce this issue. Could you please download and try the new version of Ubuntu from http://www.ubuntu.com/getubuntu/download and report back your results. If the issue is still present in the new release, please attach the following information:

* uname -a > uname-a.log
* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

Please be sure to attach each file as a separate attachment. For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

Changed in linux-source-2.6.20:
status: New → Incomplete
Revision history for this message
wolfger (wolfger) wrote :

5 months with no reply. We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux-source-2.6.20:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.