If any package is related it should be the linux kernel package,
definitely not usplash. However, this is only a BIOS
capability/configuration issue, so I'm also changing the status to
invalid.
** Package changed: usplash (Ubuntu) = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New
@Darko:
What I meant was that not being able to install or run Ubuntu can not be caused
by this kernel warning, but if you want to avoid the warning you may have to
take a look at your BIOS. Gigabyte sometimes has hidden options that you can
uncover by pressing alt-F1 from the BIOS main screen.
@Tom Pringle: even though you get the same kernel warning (symptom), for
you this is a different situation, because you are using completely
different hardware (cause). That is also why I think similar bug reports
for different hardware should not be merged.
AFAIK, there can be three main causes
AFAIK, If you placed your DSDT.aml in /etc/initramfs-tools/ a kernel
change does not require any additional action... Only if you update your
BIOS you should generate a new DSDT based on the new BIOS.
On all 4 AMD platforms I can test on, I've never seen this problem. You
should look at each
@swordfish:
Option 2 is the way to go, that warning about the 8254 timer can be safely
ignored.
Your BIOS does not provide ACPI _PSS objects in a way that Linux
understands almost always means that Cool 'n Quiet has been disabled in
the BIOS. This kernel message also isn't really an error, it
powernow-K8:BIOS error - no PSB or ACPI_PSS objects almost always
means that Cool 'n Quiet has been disabled in the BIOS. This kernel
message also isn't really an error, it just tells that the kernel will
not use CPUFREQ powernow-k8 support because Cool 'n Quiet has been
disabled, so it's doing
Your BIOS does not provide ACPI _PSS objects in a way that Linux
understands almost always means that Cool 'n Quiet has been disabled in
the BIOS. This kernel message also isn't really an error, it just tells
that the kernel will not use CPUFREQ powernow-k8 support because Cool 'n
Quiet has been
Your BIOS does not provide ACPI _PSS objects in a way that Linux
understands almost always means that Cool 'n' Quiet has been disabled
in the BIOS. This kernel message also isn't really an error, it just
tells that the kernel will not use CPUFREQ powernow-k8 support because
Cool 'n Quiet has been
@Pyoverdine:
You should look in your BIOS at the CPU setting for something called Cool 'n'
Quit, Dynamic Clock or Frequency Scaling that should be Enabled. Do not
use Auto, because that may only work on Windows. If you you cannot find such
an option, you may have an option AM2 Boost instead,
I cannot access your motherboards manual without having to register, but
in your BIOS you should probably look at the CPU configuration setting
for something called Cool 'n' Quit, Dynamic Clock or Frequency
Scaling that should be Enabled. Do not use Auto, because that may
only work on Windows. If
First of all, such a kernel command-line option would be great... It
will be a nightmare to write it and maintain it though. Go ahead and try
to do it, please! I honestly would be thankful. I doubt it will be in
time for Lucid...
Loading all modules is what is already done, except the modules are
Your BIOS does not provide the necessary information for powernow-k8 to
be able to load. Apparently either your BIOS is broken or you have to
change your BIOS settings related to frequency scaling. Either way, this
is not a driver/kernel related error.
--
frequency scaling does not work on
For what it's worth, it is in commit
495f78bd6d8f7a5e35dd962031eb6e639d83e438, which IMHO should be reverted:
UBUNTU: Build in CPU Frequency scaling drivers
Selecting the right CPU Frequency scaling driver is complicated from
userspace, involing a nasty shell script that attempts
Tim Gardner is responsible for introducing this, assign him to this bug.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Tim Gardner (timg-tpi)
--
acpi-cpufreq/powernow-k8 should not be built-in into the kernel image
https://bugs.launchpad.net/bugs/355232
You received this bug
Works fine for me too...
--
slider does not scale along when zooming in
https://bugs.launchpad.net/bugs/358364
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: New = Incomplete
--
frequency scaling does not work on Athlon X2
https://bugs.launchpad.net/bugs/327587
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The patch is harmless, it only adds accounting for time in C1E, so that you can
see in powertop, that your system is actually idle for e.g. 95% of the time. It
does nothing besides that. C1E is supported just fine in a vanilla kernel, it
has nothing to do with tickless (except that you cannot
Public bug reported:
Binary package hint: pybootchartgui
When using pybootchartgui as GUI, the up/down slider does not get updated when
you zoom in with the mouse. Therefore, when you zoom in, you'll never be able
to see the bottom of the chart, because you cannot slide to that part. E.g.
I'm having this issue too. Can pybootchartgui be updated to revision 107
in time before the Jaunty final release?
--
pybootchartgui crashed with ValueError in get_proc_state()
https://bugs.launchpad.net/bugs/343215
You received this bug notification because you are a member of Ubuntu
Bugs, which
+1 as well...
To actually add some more reason: I own a AMD based system. Because
acpi-cpufreq is build into the kernel, loading it actually SLOWS DOWN
booting my system. The only drivers that should be considered to be
build in, are modules required to boot! acpi-cpufreq and powernow-k8 are
Public bug reported:
Binary package hint: pybootchartgui
The pybootchartgui package lacks a dependency on python-gtk2. It does
not run without it, so the dependency should be added.
1.) Release version:
Description:Ubuntu jaunty (development branch)
Release:9.04
2.) Package version:
Perhaps python-gtk2 should then be recommended...
(BTW, I'm very happy with this package. Now I can just install bootchart
on my embedded hardware and run pybootchartgui on my workstation for the
actual chart and I won't need to install java or rsvg as well on my
embedded system, which is great.)
This is defined behavior of the powernow-k8 driver in the stock vanilla
kernel. A different behavior will never (officially) be supported by
AMD.
** Changed in: linux (Ubuntu)
Sourcepackagename: powernowd = linux
Status: Confirmed = Invalid
--
powernow-k8 doesn't get all fid/vid for AMD
Officially, 2000, 1800, 1600 and 800MHz are the only fids supported by AMD for
Turions:
- only one low frequency = 1400MHz
- and the rest = 2 * (low frequency) - 2 starting at 1600MHz with steps of
200MHz to the designed maximum.
For both the ML32 and ML34, that would be 1800, 1600 and 800.
The Acer Aspire 3000WLCi doesn't seem to come with a Turion ML37, but
with a Sempron. Perhaps that's why your BIOS doesn't support it
properly? What BIOS version are you using, version 3A32? Perhaps you
can try the Vista BIOS as well.
Either PSB or _PSS is required to be present in your BIOS
By now, this is should be long fixed AFAIK. My Athlon64 X2 5200+ is
supported just fine in more recent kernels (= 2.6.22)
Feel free to reopen this bug if necessary, but I am certain this has
been fixed by now.
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Released
--
No
I can't seem to find what Acer you are using?! My Acer Aspire 5024WLMi
should be older, with a Turion ML-34, but its BIOS is fine. Remember
that either a PSB or _PSS object is required for Windows 2000 to work!
(Offtopic: I'm actually the writer of the Linux-PHC (Processor Hardware
Control)
Have you tried to load processor first, as it says? E.g.:
sudo modprobe processor sudo modprobe powernow-k8
Please send the output of dmesg after a fresh startup, that can
explain more about your system, especially the available ACPI data,
etcetera.
--
frequency scaling does not work on Athlon
As for the *original* bugreport, this dmesg output:
Jun 26 20:55:57 lappy kernel: [ 494.227246] powernow-k8: BIOS error - no
PSB or ACPI _PSS objects
Tells me that your BIOS is broken. This cannot be fixed by the Linux
kernel.
Please verify whether there is a more recent BIOS for your system,
This is definitely not powernowd related
** Changed in: powernowd (Ubuntu)
Status: New = Invalid
--
Hardy x64 on AMD Turion not CPU scaling properly
https://bugs.launchpad.net/bugs/231534
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Officially, 2000, 1800, 1600 and 800MHz are the only fids supported by AMD for
Turions:
- only one low frequency = 1400MHz
- and the rest = 2 * (low frequency) - 2 starting at 1600MHz with steps of
200MHz to the designed maximum.
For both the ML32 and ML34, that would be 1800, 1600 and 800.
This is defined behavior of the powernow-k8 driver in the stock vanilla
kernel. A different behavior will never (officially) be supported by
AMD.
** Changed in: linux (Ubuntu)
Sourcepackagename: powernowd = linux
Status: Confirmed = Invalid
--
powernow-k8 doesn't get all fid/vid for AMD
The bug is in the original and current dkms, I notified the dkms mailing
list.
--
dkms does not remove module config lines it adds
https://bugs.launchpad.net/bugs/317238
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Public bug reported:
Binary package hint: dkms
Description:Ubuntu 8.10
Release:8.10
Platform: amd64
dkms:
Installed: 2.0.20.4-0ubuntu2
Candidate: 2.0.20.4-0ubuntu2
Version table:
*** 2.0.20.4-0ubuntu2 0
500 http://nl.archive.ubuntu.com intrepid/main Packages
Interesting... Too bad ionice is in /usr/bin which automatically
qualifies it as unusable... (/usr may not be mounted yet)
--
Readahead should start in the background
https://bugs.launchpad.net/bugs/70858
You received this bug notification because you are a member of Ubuntu
Bugs, which is
(@jakub007)
I had to rework the patch to make it work on the kernel tree, but where did you
get this patch? I can't find it on the Linux kernel mailing-list, or even that
*anybody* knows about this outside launchpad?!
It would be nice if a Kernel developer looked at this first and agreed
with
Re-fixing? It has never been fixed for Ubuntu 8.04 Long Time Support and thus
wxWidgets apps still don't work out-of-the-box and still need the import
wxversion workaround... Apparently all Hardy supplied wxWidgets applications
are using this workaround, or else they would not work AFAIK. It is
Could you improve this bug report, e.g. add Ubuntu version, update-notifier-kde
version, etc.
Because last time I checked it did work on my Intrepid install...
** Changed in: update-notifier-kde (Ubuntu)
Status: Confirmed = Incomplete
--
update notifier doesn't list how many packages
Well, I'll try to be polite, but if you could actually take the time to read...
- This bug is not caused by the apt.wxwidgets.org version, it was solve by
using it, but that repository has nothing to do with this bug report!
- I get this problem when upgrading from gutsy, as well as a clean hardy
Changing to incomplete, will again reinstall 8.04 live CD to a clean VM
and post my findings
** Changed in: wxwidgets2.8 (Ubuntu Hardy)
Status: Invalid = Incomplete
--
wxPython isn't on path in hardy beta
https://bugs.launchpad.net/bugs/211553
You received this bug notification because
Upgrading from gutsy (live-CD based, with python-wxgtk2.8) to hardy seems to
does have the problem.
Clean hardy (live-CD) (many package installs) then apt-get install
python-wxgtk2.8 (no other installs before that) does somehow...
Clean hardy (live-CD) then apt-get install python-wxgtk2.8 does
The cpufreq developers disagree on that. And I strongly disagree on
that. On my notebook, 1000MHz is a lot faster that 800MHz, because it
makes the memory clock and access-time much faster. It's not just the
CPU that scales up.
But anyone should understand that conservative is still better that
The most important point of this bugreport was to get conservative
support into guidance-power-manager, not necessarily as the preferred-
over-ondemand one. But without ondemand, conservative should be the
alternative, not powersave as that is not a dynamic cpufreq policy at
all.
--
I was hesitating a bit, but apparently this bug has been fixed,
conservative is now considered a dynamic cpufreq policy.
** Changed in: guidance-power-manager (Ubuntu)
Status: Invalid = Fix Released
--
kde-guidance-powermanager: support conservative CPUFreq gouvernor
Besides 266971, there is another bug in QTLanguageSelector.py. Could you
confirm this patch solves it?
** Attachment added: fix for _ function in QTLanguageSelector.py
http://launchpadlibrarian.net/18322826/QtLanguageSelector.py.patch
--
When setting the system language from language
I committed a patch for this in duplicate bug #279869
--
python2.5 crashed with TypeError in _()
https://bugs.launchpad.net/bugs/271132
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I guess if it does, there obviously would be many other bugreports
describing the issue for gnome-language-selector as it has a larger
userbase. Of course, as a Kubuntu user, I don't use the gnome
equivalent. :-) And as you can see, this patch is just against
QtLanguageSelector.py...
--
[PATCH]
Then I'll change the status to Confirmed.
** Changed in: bootchart (Ubuntu)
Status: New = Confirmed
** Summary changed:
- bootchart.jar crashes on generated bootchart.tgz
+ [PATCH] bootchart.jar crashes on generated bootchart.tgz
--
[PATCH] bootchart.jar crashes on generated
This bug should be solved since initramfs-tools 0.92ubuntu1:
Merge from debian unstable, remaining changes:
...
* Loop for 5 seconds waiting for $suspend to show up, adjustable with the
resumedelay= command-line arg
...
** Changed in: initramfs-tools (Ubuntu)
Status: New = Fix Released
The fix (and previously the bug) is in initramfs-tools
** Changed in: lvm2 (Ubuntu)
Status: New = Fix Released
--
local-premount resume script(s) too fast for LVM
https://bugs.launchpad.net/bugs/131830
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The fix (and previously the bug) is in initramfs-tools
** Changed in: uswsusp (Ubuntu)
Status: New = Fix Released
--
local-premount resume script(s) too fast for LVM
https://bugs.launchpad.net/bugs/131830
You received this bug notification because you are a member of Ubuntu
Bugs, which
I already submitted a fix in a previously submitted bugreport:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/272405
--
python2.5 crashed with UnicodeEncodeError in onPushButtonOk()
https://bugs.launchpad.net/bugs/278473
You received this bug notification because you are a
*** This bug is a duplicate of bug 278473 ***
https://bugs.launchpad.net/bugs/278473
** This bug has been marked a duplicate of bug 278473
python2.5 crashed with UnicodeEncodeError in onPushButtonOk()
--
qt-language-selector error
https://bugs.launchpad.net/bugs/272405
You received this
*** This bug is a duplicate of bug 266971 ***
https://bugs.launchpad.net/bugs/266971
** This bug is no longer a duplicate of bug 278473
python2.5 crashed with UnicodeEncodeError in onPushButtonOk()
** This bug has been marked a duplicate of bug 266971
[PATCH] qt-language-selector
*** This bug is a duplicate of bug 266971 ***
https://bugs.launchpad.net/bugs/266971
** This bug is no longer a duplicate of bug 278473
python2.5 crashed with UnicodeEncodeError in onPushButtonOk()
** This bug has been marked a duplicate of bug 266971
[PATCH] qt-language-selector
*** This bug is a duplicate of bug 266971 ***
https://bugs.launchpad.net/bugs/266971
** This bug is no longer a duplicate of bug 278473
python2.5 crashed with UnicodeEncodeError in onPushButtonOk()
** This bug has been marked a duplicate of bug 266971
[PATCH] qt-language-selector
*** This bug is a duplicate of bug 266971 ***
https://bugs.launchpad.net/bugs/266971
** This bug has been marked a duplicate of bug 266971
[PATCH] qt-language-selector crashes during startup in certain locales
--
python2.5 crashed with UnicodeEncodeError in onPushButtonOk()
I actually came up with the same patch, not knowing about this bug ID
until using the harvest webapp (see bug #272405).
** Changed in: language-selector (Ubuntu)
Status: New = Confirmed
--
[PATCH] qt-language-selector crashes during startup in certain locales
** Changed in: initramfs-tools (Ubuntu)
Status: New = Confirmed
--
forced load of examples/modules: documentation fix
https://bugs.launchpad.net/bugs/177263
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I wrongfully assumed that after submitting a patch to solve a bug, the
status could be set to fix committed.
** Changed in: language-selector (Ubuntu)
Status: Fix Committed = Confirmed
--
qt-language-selector error
https://bugs.launchpad.net/bugs/272405
You received this bug notification
I suffer from this as well, it may be a problem for all locales?!
LANG=nl_NL.UTF-8 here...
To reproduce, execute from an X terminal:
LANG=nl_NL.UTF-8 sudo /usr/bin/qt-language-selector --mode select
--
qt-language-selector error
https://bugs.launchpad.net/bugs/272405
You received this bug
** Attachment added: Proposed patch for this problem and a problem when
actually selecting a language once this bug is solved
http://launchpadlibrarian.net/18134378/QtLanguageSelector.py.patch
** Changed in: language-selector (Ubuntu)
Status: New = Fix Committed
--
See also:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464712
Reverting this patch (as done by Jonathan Riddell) to allows possibly-insecure
use of v2 capabilities. See kernel/capability.c in the Linux source
for details (look for warn_deprecated_v2).
--
avahi-daemon uses 32 bit legacy
Assigning this bug to JR (responsible for breaking it again after this
was fixed... Please at least explain why.)
** Changed in: avahi (Ubuntu)
Assignee: (unassigned) = Jonathan Riddell (jr)
--
avahi-daemon uses 32 bit legacy capabilities on AMD64
https://bugs.launchpad.net/bugs/248577
You
Confirmed, I'm seeing this in alpha6 as well. And yes, avahi-daemon is build
against libcap1, not libcap2... :-(
It's important to note that 32-capabilities is using legacy kernel code that is
being phased out. So it's important to choose whether packages will be ported
to libcap2 for intrepid
Jonathan Riddell was responsible for this, see the avahi changelog:
8
avahi (0.6.23-2ubuntu2) intrepid; urgency=low
* Build against libcap-dev instead of libcap2-dev
-- Jonathan Riddell [EMAIL PROTECTED] Sun, 27 Jul 2008 19:26:13
+0100
8
A bit more information would have
Public bug reported:
Binary package hint: bootchart
Description:Ubuntu 8.04.1
Release:8.04
bootchart:
Installed: 0.9-0ubuntu7
Candidate: 0.9-0ubuntu7
Version table:
*** 0.9-0ubuntu7 0
500 http://nl.archive.ubuntu.com hardy/main Packages
100 /var/lib/dpkg/status
** Attachment added: Bootchart.tgz that fails
http://launchpadlibrarian.net/16560306/bootchart.tgz
--
bootchart.jar crashes on generated bootchart.tgz
https://bugs.launchpad.net/bugs/254954
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Here is my proposed patch:
** Attachment added: Fix for
/usr/share/initramfs-tools/scripts/init-top/bootchart
http://launchpadlibrarian.net/16560336/bootchart-failure.patch
--
bootchart.jar crashes on generated bootchart.tgz
https://bugs.launchpad.net/bugs/254954
You received this bug
FWIW, this is printed by kernels from 2.6.25 and is caused by 'libcap1'.
Version 2 of libcap solves this issue. (v2 uses 64bit capabilities
instead of 32bit on amd64 systems.)
Other packages that cause this kernel message are all the ones that link
to libcap1 (e.g. dhcp3-client, ntpdate, wodim,
Apparently it is shipped, but if you look closer, it does however point to
../../wx/python/wx.pth (from both /usr/lib/python2.[45]/site-packages/wx.pth).
This is an invalid path, there is no /usr/lib/wx/, not for my installation at
least.
So I am very curious why it would work for *anyone*.
--
It cannot be a gutsy version bug. Maybe an upgrade from gutsy to hardy
bug. I am using hardy and suffer from this problem since I upgraded. I
did not have it before...
--
wxPython isn't on path in hardy beta
https://bugs.launchpad.net/bugs/211553
You received this bug notification because you
I'm having the same problem on Hardy Heron (final), I was able to solve
it using:
sudo ln -snf /etc/alternatives/wx.pth /usr/lib/python2.5/site-packages/
sudo ln -snf /etc/alternatives/wx.pth /usr/lib/python2.4/site-packages/
So that should perhaps be in the python-wxgtk install scripts...
FWIW, I never intended it to be included for a stable release update.
However, if one would change the dependency on librsvg2-bin to
librsvg2-bin|imagemagick, it wouldn't invalidate the documentation, so
absolutely unsuitable seems a bit rush...
--
remove svg to png conversion for bootchart
The way I interpret this bug is that it must be a duplicate of bug 61711.
As mentioned in my earlier post, removing splash from the kernel parameters
helped for me, as did editing /etc/usplash.conf to the correct values (1280x800
instead of 1280x1024). The right values aren't being set when
75 matches
Mail list logo
