Thank you - all ok here now.
--
[Jaunty] Error appearing at boot - cpufreq: No nForce2 chipset
https://bugs.launchpad.net/bugs/332170
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This bug was fixed in the package linux - 2.6.28-9.31
---
linux (2.6.28-9.31) jaunty; urgency=low
[ Andy Whitcroft ]
* SAUCE: cpufreq-nforce2: probe failures are not errors
- LP: #332170
* SAUCE: mmc: add MODALIAS linkage for MMC/SD devices
- LP: #30335
* remove
** Changed in: linux (Ubuntu)
Status: Confirmed = In Progress
--
[Jaunty] Error appearing at boot - cpufreq: No nForce2 chipset
https://bugs.launchpad.net/bugs/332170
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Change approved by the kernel-team and pushed to the repository. Will
be in the next upload.
** Changed in: linux (Ubuntu)
Status: In Progress = Fix Committed
--
[Jaunty] Error appearing at boot - cpufreq: No nForce2 chipset
https://bugs.launchpad.net/bugs/332170
You received this bug
Thank you.
--
[Jaunty] Error appearing at boot - cpufreq: No nForce2 chipset
https://bugs.launchpad.net/bugs/332170
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
[Jaunty] Error appearing at boot - cpufreq: No nForce2 chipset
https://bugs.launchpad.net/bugs/332170
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: linux (Ubuntu)
Status: In Progress = Incomplete
--
[Jaunty] Error appearing at boot - cpufreq: No nForce2 chipset
https://bugs.launchpad.net/bugs/332170
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I can confirm that solved the problem. Thanks!
On Wed, Feb 25, 2009 at 03:23, Andy Whitcroft a...@canonical.com wrote:
I have recreated the patch hinted at and applied it to the latest jaunty
kernel. If those who have seen these could confirm that this patch is
sufficient to suppress the
So can I.
Thanks
--
[Jaunty] Error appearing at boot - cpufreq: No nForce2 chipset
https://bugs.launchpad.net/bugs/332170
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I have recreated the patch hinted at and applied it to the latest jaunty
kernel. If those who have seen these could confirm that this patch is
sufficient to suppress the text and report back here. The kernels are
at the URL below:
http://people.ubuntu.com/~apw/lp332170-jaunty/
--
[Jaunty]
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Andy Whitcroft (apw)
Status: Triaged = In Progress
--
[Jaunty] Error appearing at boot - cpufreq: No nForce2 chipset
https://bugs.launchpad.net/bugs/332170
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- Error appearing at boot
+ [Jaunty] Error appearing at boot - cpufreq: No nForce2 chipset
** Tags added: regression-potential
--
[Jaunty] Error appearing at boot - cpufreq: No nForce2 chipset
https://bugs.launchpad.net/bugs/332170
You received this bug notification
Ok so that was a bit of a d'oh moment - if I
sudo cpufreq-selector -g performance
Then it fairly obviously works ok :)
I get current CPU frequency is 2.53 GHz.
BUT on reboot it reverts to the ondemand performance
Also not sure if this is of importance but grep -i nforce
/boot/config-`uname
I can confirm this bug, this has been around for around a week I guess.
--
[Jaunty] Error appearing at boot - cpufreq: No nForce2 chipset
https://bugs.launchpad.net/bugs/332170
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Confirmed on both i386 and amd64 since the cpu governor was set to
ondemand on boot. Also confirmed that setting the cpu goverenor to
performance fixes system slowdown.
Please, consider reverting the kernel configuration change.
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
Matthew Garrett tells me on IRC that this message is being printed by
the kernel as KERN_ERR rather than KERN_INFO which is why it is
appearing on the screen, and should be changed to KERN_INFO.
forestpixie, the slowness you are experiencing, while related to
cpufreq, is a different problem.
** Description changed:
- With one of the updates I got 19/2/09 I started to get this error
- shortly (1.44 secs) after grub starts the boot
+ After Jaunty updates on Feb 19, 2009, this message appears at boot:
cpufreq: No nForce2 chipset
- Rest of dmesg appears to be normal - but is
Oops, apparently it hasn't been pushed yet, but it has been accepted.
Setting back to Triaged.
** Changed in: linux (Ubuntu)
Status: Fix Committed = Triaged
--
[Jaunty] Error appearing at boot - cpufreq: No nForce2 chipset
https://bugs.launchpad.net/bugs/332170
You received this bug
A patch was accepted upstream and will be fixed in 2.6.30. Matthew
tells me that this fix can be backported easily.
** Changed in: linux (Ubuntu)
Status: Triaged = Fix Committed
--
[Jaunty] Error appearing at boot - cpufreq: No nForce2 chipset
https://bugs.launchpad.net/bugs/332170
You
19 matches
Mail list logo
