I thought that something as trivial as a syntax error was certainly caused by
some Python version mismatch (default Python version on Trusty being 2.7).
So I tried to launch the package configuration again (dpkg --configure solaar)
in a shell where I had forced default Python version to 3.4, but
** Description changed:
OS version: Ubuntu 14.04.6 LTS, Trusty Tahr
OS flavor: Ubuntu Studio
Package versions exhibiting error:
1.0.5~ubuntu14.04.1
1.0.6~ubuntu14.04.1
Scenario:
Error first occurred when I tried to install solaar packag
Public bug reported:
OS version: Ubuntu 14.04.6 LTS, Trusty Tahr
OS flavor: Ubuntu Studio
Package versions exhibiting error:
1.0.5~ubuntu14.04.1
1.0.6~ubuntu14.04.1
Scenario:
Error first occurred when I tried to install solaar package a few weeks ago, to
drive my n
First of all, it's really sad that this bug is more than one year old, with
thousands of people affected (including on LTS releases), and we still don't
see any official Canonical communication AFAIK !
It's also a mystery why this bug can apparently take so many different
forms. In my case, I do
Public bug reported:
Distro: Ubuntu Studio 14.04
term.log excerpt:
...
run-parts: executing /etc/kernel/postinst.d/dkms 3.13.0-44-lowlatency
/boot/vmlinuz-3.13.0-44-lowlatency
Error! Bad return status for module build on kernel: 3.13.0-44-lowlatency
(x86_64)
Consult /var/lib/dkms/nvidia-331/331
Public bug reported:
I configured an md RAID1 array to host users' data (intent is to mount
formatted RAID volume at /home at boot).
I first simply rebooted the machine to see if array was starting, and it was,
but was always getting a /dev/md127 pointer instead of the /dev/md0 I had
configure
** Package changed: linux-lowlatency (Ubuntu) => pm-utils (Ubuntu)
** Description changed:
Distro : Ubuntu Studio 12.10 (low latency kernel)
M/B : Tyan Thunder S2915 (not S2915-E)
CPU : AMD Opteron Dual-core 2212 (frequency steps from 1 to 2GHz)
BIOS version : v3.0 (last version for this
** Tags removed: kernel-bug
** Tags added: kernel-power
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1319618
Title:
pm-utils hook unable to restore previous CPU state when resuming from
suspend
After some testing, I found that the cause of this issue lies within pm-
utils' hook "94cpufreq" (see below excerpts from pm-suspend.log).
Until kernel 3.5.0-48 ("3.5.0-48-lowlatency #49-Ubuntu SMP PREEMPT Tue Mar 18
22:34:24 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux"), everything was running fine
** Summary changed:
- CPU frequency stuck to highest value after resuming from suspend
+ pm-utils hook unable to restore previous CPU state when resuming from suspend
** Tags added: kernel-bug pm-utils
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
** Tags added: powernow-k8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1319618
Title:
CPU frequency stuck to highest value after resuming from suspend
To manage notifications about this bug go to
I must compare suspend/resume and system logs between both versions of
kernel, but my best bet is it's a consequence of powernow-k8 update that
came with fix-pack release v3.5.7.32 (bug #1295768).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
** Description changed:
Distro : Ubuntu Studio 12.10 (low latency kernel)
M/B : Tyan Thunder S2915 (not S2915-E)
CPU : AMD Opteron Dual-core 2212 (frequency steps from 1 to 2GHz)
+ BIOS version : v3.0 (last version for this M/B)
BIOS config : NUMA + IOMMU + Memory whole translation are act
Public bug reported:
Distro : Ubuntu Studio 12.10 (low latency kernel)
M/B : Tyan Thunder S2915 (not S2915-E)
CPU : AMD Opteron Dual-core 2212 (frequency steps from 1 to 2GHz)
BIOS config : NUMA + IOMMU + Memory whole translation are activated
Kernel boot options : /boot/vmlinuz-3.5.0-49-lowlatenc
Just in case it might help someone else, here's a wrapup of the final
status for my issues.
Intent : migrate from "Ubuntu Studio x64 10.10" to "Ubuntu Studio x64
12.10" (both installed, on distinct HDDs)
System specs : Tyan s2915 (non-E) motherboard, Tyan BIOS v3.00, MCP55
Pro chipset, dual Opter
Thanks very much Joe for keeping us posted on that bug.
I created the udev rule and it seems to work.
I say "seems to work" because I actually found I was having 2 different
problems at the same time :
1- this sata_nv bug
2- a vendor tuned (and bugged) firmware on my Ubuntu 12.10 boot disk (HP
V
Reading again the first posts from this thread, seems I made a mistake
posting my comment here.
Maxim Tikhonov could get udev to trigger /lib/udev/hdparm manually, but
not during boot sequence.
My problem was actually that of bug #222458 : a bug in hdparm-functions
that prevented it to "recognize
Problem detected on Ubuntu Studio x64 12.10 and reproduced under Studio
x64 10.10 (both OSes running on same machine - two different hard
drives).
Slightly the same situation as jdblair above (need to disable write cache on a
disk at boot/resume time), except two differences :
- classic hard
Last security updates from Ubuntu turned kernel to version
3.5.0-23-lowlatency => no change in behavior, still can't suspend.
To add some more frustration, HP's firmware upgrade tools won't work :
message is "unsupported drive" although my drive has the exact reference
covered by the upgrade :-[
Joe, I think we're clearly dealing with the same bug as yours #48951.
>From what I've found on people having this same problem :
-> Joe's bug #48951 on the kernel tracker (+ the various contributors on it)
-> here : http://forums.fedoraforum.org/showthread.php?t=283005
-> here : https://bugs.arch
** Attachment added: "ubuntu_studio_12.10_kern3.5.0-21_suspend_FAIL.log"
https://bugs.launchpad.net/ubuntu/+bug/1065840/+attachment/3491600/+files/ubuntu_studio_12.10_kern3.5.0-21_suspend_FAIL.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Hi all,
ill, if you type
ls -al /sys/block
in a terminal, you should get a list of symlinks referencing all block devices
registered on your machine.
>From which you find the bus addresses of your actual hard drives (for example
>on my machine) :
lrwxrwxrwx 1 root root 0 2013-01-19 19:43 sde
Exact same problem here with freshly installed Ubuntu Studio 12.10.
Installed all 169 updates + new kernel right after install from dvd => version
is now :
Linux version 3.5.0-21-lowlatency (buildd@allspice) (gcc version 4.7.2
(Ubuntu/Linaro 4.7.2-2ubuntu1) ) #19-Ubuntu SMP PREEMPT Tue Dec 18
18:
23 matches
Mail list logo
