[Bug 363868] Re: BIOS does not provide ACPI _PSS objects in a way that Linux understands, Foxconn A7GM-S 2.0
@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 - from the BIOS main screen. What can be a problem is when you have enabled customized CPU frequency/voltage settings in your BIOS, because the powernow-k8 will undo these settings. This is often more harmful than leaving them be and you cannot avoid powernow-k8 doing so because since 9.04 it is built-in in the kernel... -- BIOS does not provide ACPI _PSS objects in a way that Linux understands, Foxconn A7GM-S 2.0 https://bugs.launchpad.net/bugs/363868 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 382220] Re: powernow-K8:BIOS error - no PSB or ACPI_PSS objects
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 => Invalid -- powernow-K8:BIOS error - no PSB or ACPI_PSS objects https://bugs.launchpad.net/bugs/382220 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 364156] Re: powernow-k8: BIOS does not provide ACPI -PSS objects in a way that Linux understands
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 platform individually. I noticed only one dmidecode.txt, so I wasn't aware of additional platforms. Maybe you can post me the details on the other platforms to my email address, it's probably of no use to keep discussing this here, but maybe I can be of any assistance to you... -- powernow-k8: BIOS does not provide ACPI -PSS objects in a way that Linux understands https://bugs.launchpad.net/bugs/364156 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 364156] Re: powernow-k8: BIOS does not provide ACPI -PSS objects in a way that Linux understands
@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 for this warning: 1) Your BIOS is not configured to support C 'n' Q 2) Your BIOS is incomplete 3) You are using a different (newer) CPU than the ones your motherboard supports For Lenovo I know they offers _incomplete_ ACPI information, you will have to override your ACPI data by using a custom DSDT. You should be able to find some howto's on the Internet, I don't have the full details... But either way, these bug reports do not apply to any software in Ubuntu, except that you cannot use a customized powernow-k8 driver because this module is built into the kernel image... -- powernow-k8: BIOS does not provide ACPI -PSS objects in a way that Linux understands https://bugs.launchpad.net/bugs/364156 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 382220] Re: powernow-K8:BIOS error - no PSB or ACPI_PSS objects
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 you you cannot find such an option, you may have an option "AM2 Boost" instead, please disable that (only if there is no C 'n' Q option)... -- powernow-K8:BIOS error - no PSB or ACPI_PSS objects https://bugs.launchpad.net/bugs/382220 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 364156] Re: powernow-k8: BIOS does not provide ACPI -PSS objects in a way that Linux understands
@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, please disable that (only if there is no C 'n' Q option)... "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 disabled, so it's doing exactly what is requested. Please verify that C 'n' Q has indeed been disabled in the BIOS, and then determine what you want. If you don't want Cool 'n' Quiet you can ignore this message (powernow-k8 has been built-in in the kernel so you cannot prevent this message from being displayed). -- powernow-k8: BIOS does not provide ACPI -PSS objects in a way that Linux understands https://bugs.launchpad.net/bugs/364156 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 347002] Re: AMD 6000+ Cool'n'Quiet does not work (ACPI)
"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 disabled, so it's doing exactly what is requested. Please verify that C 'n' Q has indeed been disabled in the BIOS, and then determine what you want. If you don't want Cool 'n' Quiet you can ignore this message (powernow-k8 has been built-in in the kernel so you cannot prevent this message from being displayed). (To enable, go into your BIOS and go to "Advanced" => "CPU Configuration" => "Cool 'n' Quiet" and set it to "Enabled") -- AMD 6000+ Cool'n'Quiet does not work (ACPI) https://bugs.launchpad.net/bugs/347002 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 363868] Re: BIOS does not provide ACPI _PSS objects in a way that Linux understands, Foxconn A7GM-S 2.0
"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 disabled, so it's doing exactly what is requested. Please verify if C'n Q has indeed been disabled in the BIOS, and then determine what you want. If you don't want C'n Q you can ignore this message (powernow-k8 has been built-in in the kernel so you cannot prevent this message from being displayed). -- BIOS does not provide ACPI _PSS objects in a way that Linux understands, Foxconn A7GM-S 2.0 https://bugs.launchpad.net/bugs/363868 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 382220] Re: powernow-K8:BIOS error - no PSB or ACPI_PSS objects
"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 exactly what is requested. Please verify if C'n Q has indeed been disabled in the BIOS, and then determine what you want. If you don't want C'n Q you can ignore this message (powernow-k8 has been built-in in the kernel so you cannot prevent this message from being displayed). -- powernow-K8:BIOS error - no PSB or ACPI_PSS objects https://bugs.launchpad.net/bugs/382220 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398109] Re: powernow-k8: Your BIOS does not provide ACPI _PSS objects in a way that Linux understands
@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 just tells that the kernel will not use CPUFREQ powernow-k8 support because Cool 'n Quiet has been disabled, so it's doing exactly what is requested. Unfortunately the Ubuntu people chose to built-in the powernow-k8 module, so there's no way to prevent powernow-k8 from being loaded, what may be exactly what you want... ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- powernow-k8: Your BIOS does not provide ACPI _PSS objects in a way that Linux understands https://bugs.launchpad.net/bugs/398109 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 355232] Re: acpi-cpufreq/powernow-k8 should not be built-in into the kernel image
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 built-in. So that "major reason" is invalid. Actually, it can only get better than what we are now at (some cpu's are supported by both speedstep and acpi-cpufreq, and there isn't a best one in all situations and the acpi-cpufreq driver actually tries to support any processor, but fortunately it can't). It's not all "code that is raw assembler and ... know the precise magic". Every current processor (Intel, AMD and VIA) has its northbridge integrated, so all you have to do is look at the PCI ids, you can even get udev to it automatically (and decide what's best for some corner cases). About your "key point", please point me one processor that comes with their lowest frequency enabled?! In contrary, a lot of AMD systems are actually better of without cpufreq support, because their "Black Edition" often has a higher multiplier enabled in the BIOS than what the vanilla powernow-k8 driver supports. So after loading the powernow-k8 driver, you will never get back that higher frequency setting. (By the way, all applicable cpufreq drivers are written completely in C.) -- acpi-cpufreq/powernow-k8 should not be built-in into the kernel image https://bugs.launchpad.net/bugs/355232 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 327587] Re: frequency scaling does not work on Athlon X2
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 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 355232] Re: acpi-cpufreq/powernow-k8 should not be built-in into the kernel image
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 355232] Re: acpi-cpufreq/powernow-k8 should not be built-in into the kernel image
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 to guess by grepping through /proc. The kernel drivers themselves can adequately determine whether they should be used, building them into the kernel will automatically select the right one. These aren't something you would want to unload either, you would instead simply change the governor. rtg - Added debian/abi/2.6.28-8.23/modules.ignore to accomodate the missing modules. Signed-off-by: Scott James Remnant Signed-off-by: Tim Gardner - First of all, the kernel does not (and simply cannot) always adequately determine which one is the best driver to use for someones hardware (especially when choosing between speedstep-centrino and cpufreq-acpi). And even if it does, so would lets-modprobe-just-about-any-driver do. - They are something you would want to unload in realistic situations, especially since: * Some people prefer NOT to have a cpufreq driver, that's why it is a config option in the first place. There are systems known to consistently trigger a "pending-bit stuck" when using the powernow-k8 driver. * AFAIK the Ubuntu team wants to achieve a faster boottime, not slower. Compiling in all drivers slow down booting noticeably. You don't need them to boot either, so they can be postponed until a bit later. * Newer processors may not be supported until a new kernel is distributed, unless a custom module can be loaded. This is true for AMD 0xf family processors with more than 1 low power state. Also for all Black Edition AMD processors, the powernow-k8 driver does not support using their unlocked multiplier and probably never will because AMD doesn't want that feature in their powernow-k8 driver. The Linux-PHC project provides such drivers that can be installed/maintained by the DKMS. * You may want to use a modified module, that enables undervolting, to maximize their battery life or reduce extreme heat by reducing the processor's power consumption. The Linux-PHC project provides such drivers. There is a large audience that uses them... -- acpi-cpufreq/powernow-k8 should not be built-in into the kernel image https://bugs.launchpad.net/bugs/355232 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188739] Re: AMD turion does not have support for c states
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 see the idle time in powertop on any system without tickless, but that's in general). I think you're missing the point. It does not save any additional power, it just adds performance counters for it. -- AMD turion does not have support for c states https://bugs.launchpad.net/bugs/188739 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 327587] Re: frequency scaling does not work on Athlon X2
** 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 358364] Re: slider does not scale along when zooming in
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 358364] [NEW] slider does not scale along when zooming in
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. when you zoom in 4x, the slider will only allow you to slide over the upper 1/4 part. I haven't verified yet if this is solved in r107, otherwise I'll also file the bug on code.google.com 1.) Release version: Description: Ubuntu jaunty (development branch) Release: 9.04 2.) Package version: pybootchartgui: Installed: 0+r102-2 Candidate: 0+r102-2 Version table: *** 0+r102-2 0 500 http://nl.archive.ubuntu.com jaunty/universe Packages 100 /var/lib/dpkg/status ** Affects: pybootchartgui (Ubuntu) Importance: Undecided Status: New -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 343215] Re: pybootchartgui crashed with ValueError in get_proc_state()
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 is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 355232] Re: acpi-cpufreq is not a module anymore
+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 never required to boot a system! There are probably over 1000 Ubuntu users that are actively using PHC modules to lower their systems power consumption or even to unlock more cpu scaling frequencies... So please solve this issue ASAP. ** Summary changed: - acpi-cpufreq is not a module anymore + acpi-cpufreq/powernow-k8 should not be built-in into the kernel image -- acpi-cpufreq/powernow-k8 should not be built-in into the kernel image https://bugs.launchpad.net/bugs/355232 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 353699] Re: pybootchartgui lacks a dependency on python-gtk2
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.) -- pybootchartgui lacks a dependency on python-gtk2 https://bugs.launchpad.net/bugs/353699 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 353699] [NEW] pybootchartgui lacks a dependency on python-gtk2
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: pybootchartgui: Installed: 0+r102-2 Candidate: 0+r102-2 Version table: *** 0+r102-2 0 500 http://nl.archive.ubuntu.com jaunty/universe Packages 100 /var/lib/dpkg/status ** Affects: pybootchartgui (Ubuntu) Importance: Undecided Status: New -- pybootchartgui lacks a dependency on python-gtk2 https://bugs.launchpad.net/bugs/353699 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 46384] Re: powernow-k8 doesn't get all fid/vid for AMD Turion ML37
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. To be able to use the unofficial fids you will have to use the Linux-PHC AMD driver with "direct_transitions" by me ;-) or something similar. You will then have 13 different fids (800 to 2000 with 100MHz steps) to choose from. -- powernow-k8 doesn't get all fid/vid for AMD Turion ML37 https://bugs.launchpad.net/bugs/46384 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs . -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 46384] Re: powernow-k8 doesn't get all fid/vid for AMD Turion ML37
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 Turion ML37 https://bugs.launchpad.net/bugs/46384 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs . -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 111375] Re: No powernow support on Athlon 64 (amd64)
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 powernow support on Athlon 64 (amd64) https://bugs.launchpad.net/bugs/111375 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 231534] Re: Hardy x64 on AMD Turion not CPU scaling properly
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 information for Linux frequency scaling to work (if it isn't defined in another way). I just meant that Windows 2000 won't work either if neither are present in your BIOS (ACPI) information. The Aspire 30xx and Aspire 50xx indeed seem to be alike (and I know for certain 302x and 502x are in fact identical) and there may be a Ferrari notebook that is identical as well, except for its casing. However, I wouldn't know which one is. But the Ferrari's are better and longer supported. At tuxmobile.org no-one mentions any difficulty with the frequency- scaling of this notebook. Have you tried other Linux distributions/live- CD's? I suspect the Turion is just not supported by the BIOS. -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 231534] Re: Hardy x64 on AMD Turion not CPU scaling properly
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) phc-k8 driver and I think I can adapt the phc-k8 driver somewhere in the future to "guess" a powerstate table, without any ACPI usage whatsoever. I may need your help for testing it when it's ready... Maybe (then) I'll even succeed in getting it merged into the vanilla Linux kernel.) -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 231534] Re: Hardy x64 on AMD Turion not CPU scaling properly
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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 231534] Re: Hardy x64 on AMD Turion not CPU scaling properly
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, perhaps your manufacturer has already released a fix. If not, you could request them to do that. Also, perhaps there's a custom ACPI "DSDT" for your system available for Linux that provides a PSB or _PSS table. There are some HOWTO's available that will help you do that. It could also be that a BIOS option is blocking the PSB or _PSS objects, something in the line of "intelligent power managment" or so. My Asrock motherboard has such an option, I don't remember what it is called. (I'm not immediately switching the status of this bugreport to "Invalid" as I will wait for your feedback first) As for all the noise in this bugreport, please fill in your own bug reports... -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 327587] Re: frequency scaling does not work on Athlon X2
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 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 46384] Re: powernow-k8 doesn't get all fid/vid for AMD Turion ML37
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. To be able to use the unofficial fids you will have to use the Linux-PHC AMD driver with "direct_transitions" by me ;-) or something similar. You will then have 13 different fids (800 to 2000 with 100MHz steps) to choose from. -- powernow-k8 doesn't get all fid/vid for AMD Turion ML37 https://bugs.launchpad.net/bugs/46384 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 46384] Re: powernow-k8 doesn't get all fid/vid for AMD Turion ML37
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 Turion ML37 https://bugs.launchpad.net/bugs/46384 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 317238] Re: dkms does not remove module config lines it adds
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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 317238] [NEW] dkms does not remove module config lines it adds
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
100 /var/lib/dpkg/status
On an "ADD" event, dkms installs "MODULES_CONF" lines into /etc/modprobe.d/dkms
However, it does not remove these on an "REMOVE" event, because the dkms script
lacks a reference to /etc/modprobe.d/dkms.
The following snippets from /usr/sbin/dkms says it all:
--8<--
function moduleconfig_add ()
{
# $1 = kernel version
local temp_dir_name=`mktemp -d $tmp_location/dkms.XX`
modconfig_files=""
[ -e /etc/modprobe.d/dkms ] && modconfig_files="/etc/modprobe.d/dkms"
[ -e /etc/modules.conf ] && modconfig_files="/etc/modules.conf"
[ -e /etc/modprobe.conf ] && modconfig_files="$modconfig_files /etc/modprobe
.conf"
--8<--
--8<--
function moduleconfig_remove ()
{
# $1 = kernel version
local temp_dir_name=`mktemp -d $tmp_location/dkms.XX`
modconfig_files=""
[ -e /etc/modules.conf ] && modconfig_files="/etc/modules.conf"
[ -e /etc/modprobe.conf ] && modconfig_files="$modconfig_files
/etc/modprobe.conf"
--8<--
As you can see, the moduleconfig_remove function doesn't do anything
with /etc/modprobe.d/dkms at all.
By the way, if /etc/modules.conf exists, dkms is also completely forgotten
about. I guess that for both functions, the following should be the best
replacement code:
[ -e /etc/modprobe.d/dkms ] && modconfig_files="/etc/modprobe.d/dkms"
[ -e /etc/modules.conf ] && modconfig_files="$modconfig_files
/etc/modules.conf"
[ -e /etc/modprobe.conf ] && modconfig_files="$modconfig_files
/etc/modprobe.conf"
** Affects: dkms (Ubuntu)
Importance: Undecided
Status: New
--
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 mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70858] Re: Readahead should start in the background
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188739] Re: AMD turion does not have support for c states
(@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 the patch and determined/confirmed the importance of this issue and submitted this to the vanilla kernel tree... -- AMD turion does not have support for c states https://bugs.launchpad.net/bugs/188739 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211553] Re: wxPython isn't on path in hardy beta
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 not have the problem. Clean hardy (live-CD) apt-get install python-wxgtk2.8 then many package installs does not have the problem. Good enough for me. ** Changed in: wxwidgets2.8 (Ubuntu Hardy) Status: Incomplete => Invalid -- wxPython isn't on path in hardy beta https://bugs.launchpad.net/bugs/211553 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211553] Re: wxPython isn't on path in hardy beta
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 you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211553] Re: wxPython isn't on path in hardy beta
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 install. When I say clean, I mean clean: out of the box, direct from a 8.04 live CD installed and apt-get install python-wxgtk2.8. - Please unpack the .deb, e.g. from http://packages.ubuntu.com/hardy/python-wxgtk2.8, you will see there that it's simply not there, "postinst": update-alternatives --install /usr/lib/wx/python/wx.pth wx.pth \ /usr/lib/wx/python/wx2.8.pth28 Now YOU point me where it is linking /usr/lib/python2.5/site- packages/wx.pth to something. By the way, postinst is using "/bin/sh" as shell, which for me is /bin/dash, but that does not seem related. -- wxPython isn't on path in hardy beta https://bugs.launchpad.net/bugs/211553 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 282676] Re: update notifier doesn't list how many packages needs updating
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 needs updating https://bugs.launchpad.net/bugs/282676 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211553] Re: wxPython isn't on path in hardy beta
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 best to use the wxWidgets repository for hardy: deb http://apt.wxwidgets.org/ hardy-wx main -- wxPython isn't on path in hardy beta https://bugs.launchpad.net/bugs/211553 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 109197] Re: kde-guidance-powermanager: support "conservative" CPUFreq gouvernor
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 https://bugs.launchpad.net/bugs/109197 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 109197] Re: kde-guidance-powermanager: support "conservative" CPUFreq gouvernor
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. -- kde-guidance-powermanager: support "conservative" CPUFreq gouvernor https://bugs.launchpad.net/bugs/109197 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 109197] Re: kde-guidance-powermanager: support "conservative" CPUFreq gouvernor
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 performance. At least when I filed the bug, either ondemand, userspace, performance or powersave was the cpufreq policy for "dynamic" in that order. -- kde-guidance-powermanager: support "conservative" CPUFreq gouvernor https://bugs.launchpad.net/bugs/109197 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 271132] Re: python2.5 crashed with TypeError in _()
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279869] Re: When setting the system language from language chooser: python2.5 crashed with TypeError in _()
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 chooser: python2.5 crashed with TypeError in _() https://bugs.launchpad.net/bugs/279869 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 131830] Re: local-premount resume script(s) too fast for LVM
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 is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 131830] Re: local-premount resume script(s) too fast for LVM
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 131830] Re: local-premount resume script(s) too fast for LVM
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 -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 254954] Re: bootchart.jar crashes on generated bootchart.tgz
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 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 266971] Re: [PATCH] qt-language-selector crashes during startup in certain locales
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] qt-language-selector crashes during startup in certain locales https://bugs.launchpad.net/bugs/266971 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 177263] Re: forced load of examples/modules: documentation fix
** 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 266971] Re: [PATCH] qt-language-selector crashes during startup in certain locales
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 https://bugs.launchpad.net/bugs/266971 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 269064] Re: python2.5 crashed with UnicodeEncodeError in onPushButtonOk()
*** 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 crashes during startup in certain locales -- python2.5 crashed with UnicodeEncodeError in onPushButtonOk() https://bugs.launchpad.net/bugs/269064 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 272405] Re: qt-language-selector error
*** 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 crashes during startup in certain locales -- qt-language-selector error https://bugs.launchpad.net/bugs/272405 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 276806] Re: python2.5 crashed with UnicodeEncodeError in onPushButtonOk()
*** 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 crashes during startup in certain locales -- python2.5 crashed with UnicodeEncodeError in onPushButtonOk() https://bugs.launchpad.net/bugs/276806 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278473] Re: python2.5 crashed with UnicodeEncodeError in onPushButtonOk()
*** 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() https://bugs.launchpad.net/bugs/278473 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 272405] Re: qt-language-selector error
*** 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 bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278473] Re: python2.5 crashed with UnicodeEncodeError in onPushButtonOk()
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 272405] Re: qt-language-selector error
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 272405] Re: qt-language-selector error
** 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 -- qt-language-selector error https://bugs.launchpad.net/bugs/272405 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 272405] Re: qt-language-selector error
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 248577] Re: avahi-daemon uses 32 bit legacy capabilities on AMD64
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 248577] Re: avahi-daemon uses 32 bit legacy capabilities on AMD64
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 capabilities on AMD64 https://bugs.launchpad.net/bugs/248577 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 248577] Re: avahi-daemon uses 32 bit legacy capabilities on AMD64
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 been nice, e.g. the reason why this was done... :( -- avahi-daemon uses 32 bit legacy capabilities on AMD64 https://bugs.launchpad.net/bugs/248577 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 248577] Re: avahi-daemon uses 32 bit legacy capabilities on AMD64
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 or not. IMHO, it would be best to switch to libcap2 before the final intrepid release for the most important packages (for the AMD64 platform). IMHO, the most important packages still built against libcap1: - avahi-daemon - pulseaudio*, libpulse0 - ntpdate -- avahi-daemon uses 32 bit legacy capabilities on AMD64 https://bugs.launchpad.net/bugs/248577 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 254954] Re: bootchart.jar crashes on generated bootchart.tgz
** 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 254954] Re: bootchart.jar crashes on generated bootchart.tgz
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 254954] [NEW] bootchart.jar crashes on generated bootchart.tgz
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 The bug: --- In /etc/init.d/stop-bootchart the line: /usr/bin/java -jar /usr/share/bootchart/bootchart.jar sometimes crashes with the following message: Parsing /var/log/bootchart.tgz Exception in thread "main" java.lang.NullPointerException at org.bootchart.parser.linux.ProcStatParser.parseLog(Unknown Source) at org.bootchart.Main.render(Unknown Source) at org.bootchart.Main.main(Unknown Source) Analysis: --- I have traced this back to bootchart.jar actually having problems parsing the log files in /var/log/bootchart.tgz where each time this occurs, one of the three files lacks a complete record. The last line of such a file allways contains an uptime entry and is not followed by the content of either /proc/stat, /proc/diskstats, proc/*/stat of that moment. It seems that the shell function "stop_bootchart()" in /etc/init.d/stop- bootchart sometimes has a timing issue, where it kills the bootchart logging right after the uptime is inserted in the log. On my Via C3 500MHz system, this situation seems to occur regularly, whereas on my workstation this happened only three or four times in the last couple of months. Proposed solution: I'd like to propose a patch for /usr/share/initramfs-tools/scripts/init-top/bootchart which basicly turns: sed -e "s/ [0-9].*//;s/\.//" < /proc/uptime cat /proc/stat into: sed -e "s/ [0-9].*//;s/\.//" < /proc/uptime | cat - /proc/stat With this change I haven't had any bootchart generation failures whatsoever. ** Affects: bootchart (Ubuntu) Importance: Undecided Status: New -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 248577] Re: avahi-daemon uses 32 bit legacy capabilities on AMD64
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, etc.) ** Changed in: libcap (Ubuntu) Sourcepackagename: avahi => libcap -- avahi-daemon uses 32 bit legacy capabilities on AMD64 https://bugs.launchpad.net/bugs/248577 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211553] Re: wxPython isn't on path in hardy beta
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*. -- wxPython isn't on path in hardy beta https://bugs.launchpad.net/bugs/211553 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211553] Re: wxPython isn't on path in hardy beta
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211553] Re: wxPython isn't on path in hardy beta
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... -- wxPython isn't on path in hardy beta https://bugs.launchpad.net/bugs/211553 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 204186] Re: remove svg to png conversion for bootchart
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 https://bugs.launchpad.net/bugs/204186 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 84376] Re: Long delay before KDM starts
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 installing from the Kubuntu Gutsy live-CD. I don't have the machine available right now for a bootchart/lspci dump, but it wouldn't add much... But you're probably addressing the bug reporter -which is not me- anyway ;-) -- Long delay before KDM starts https://bugs.launchpad.net/bugs/84376 You received this bug notification because you are a member of Kubuntu Team, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
