From this we can see that hardware and kernel reports right figures when
unplugging the powercord:
tarmo@tarmo-hpmini ~ $ cat /proc/acpi/battery/BAT1/info
present: yes
design capacity: 2600 mWh
last full capacity: 2383 mWh
battery technology: non-rechargeable
Same problem here with maverick and hp2133. Using recording application like
gnome-sound-recorder or skype pulseaudio process eats all available cpu time
(cpu usage 100%) and the sound is stuttering. tsched=0 helps a bit (pulseaudio
not taking all available cpu), but pulseaudio eats still 30%
Enhanced version of patch for lucid. In most cases should show the remaining
time also. Downside is small delay in responding unplug event. Should not
have any effect on systems not affected by this bug i.e. should be suitable as
a common correction for lucid.
** Attachment added: patch2
Here is patched .deb package for lucid version of upower (0.9.1-1). It adds a
sanity check of data and small delay for machines with bios not updating uevent
data instantly. I can't take any responsibility of the quality or correctness,
but if someone having this bug is willing to give it a
** Attachment added: upower patch for lucid
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/531190/+attachment/1825825/+files/patch.upower0.9.1-1_up-device-supply.c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks David for the link. Building debian package was easier than I thought.
0.9.8 didn't work for me (hp2133). My earlier idea helped a little, but didn't
fully solve the issue. But I did some more research and I suppose I found the
core problem. This is basically a timing issue. If you
** Attachment added: patch for natty version (upower0.9.8-1build1)
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/531190/+attachment/1825845/+files/patch.upower0.9.8-1build1_up-device-supply.c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sorry for the previous post. I didn't fully realize how the system works. But
back to the problem itself. I took a look about figures kernel reports in
sysfs. Looks like current_now is always same figure as power_now, meaning
current_now is insane, but power_now is reasonable. I'm on
Hi all,
Just wandered why so critical bug like this has been open so long. People
here are talking, but there isn't anyone listening. Looks like the system
goes like this:
This is reported to ubuntu
Ubuntu forwards this to debian
debian forwards this to FreeDesktop
Every movement takes
HP 2133 and Lucid. Is there any progress?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/531190
Title:
upower (devkit-power) reporting bad data when AC cable is unplugged
--
ubuntu-bugs mailing
Did some more testing. alsa 1.0.23 works great. With arecord and aplay no
problems at all. This was a pulse-audio problem. Solved this by modifying
/etc/pulse/daemon.conf. Assume problem was caused by latency in this kind of
low end system. Looks like this a very common problem in
** Package changed: alsa-driver (Ubuntu) = pulseaudio (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/614316
Title:
VT1708/A (hp2133) output crackling
--
ubuntu-bugs mailing list
udated to alsa 1.0.23. Here are testing results using ubuntu voice recorder
and latest alsa driver:
- no need for options snd-hda-intel position_fix=1
- no cracling in output
- volume in sound recording is low even with recording level set to maximum
- strange echo in recordings, words are
Public bug reported:
Via VT1708/A (hp2133) sound didn't work at all after installing 10.04. (The
same card works fine with ubuntu 9.04.). Hardware disappears from sound
settings after a while. As a workaround for this I added following into the
/etc/modprobe.d/alsa-base.conf:
options
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/53162400/AlsaDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/53162401/BootDmesg.txt
** Attachment added: Card0.Amixer.values.txt
This happens nowadays randomly and very seldom. This is a apport log from the
last error. getting this was a bit difficult because online reporting is
difficult when you have a problem in network;). Couldn't do server upgrade
because of dependencies.
** Attachment added:
Thanks for your answer. Last time this happened my son was testing kvm running
windows server in the same server. Do you think this could be caused by kvm
windows server and host ubuntu server accessing same network interface? Using
windows server in the same server propably caused heavy
Public bug reported:
Forcedeth driver hangs about once per month. All the network traffic is ceased
until cold reboot. System is connected to netgear gigabit switch.
$ lsb_release -rd
Description:Ubuntu 9.10
Release:9.10
$ uname -a
Linux serveri 2.6.31-16-server #53-Ubuntu SMP
** Attachment added: lspci-vnvn.log
http://launchpadlibrarian.net/44002054/lspci-vnvn.log
--
forcedeth driver hang/freeze
https://bugs.launchpad.net/bugs/562081
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
dmesg log after cold reboot
** Attachment added: dmesg.log
http://launchpadlibrarian.net/44005797/dmesg.log
--
forcedeth driver hang/freeze
https://bugs.launchpad.net/bugs/562081
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
/var/log/messages.1
** Attachment added: /var/log/messages
http://launchpadlibrarian.net/44006672/messages.1
--
forcedeth driver hang/freeze
https://bugs.launchpad.net/bugs/562081
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: xorg
When xorg fails to detect display, it forces to use 640x480. This happens even
if xorg.conf contains relevant information for the display. If the recognition
fails, it should consider using xorg.conf information.
The quick solution:
user
** Attachment added: xorg.log
http://launchpadlibrarian.net/20578564/Xorg.0.log
--
xorg automatic display detection not working
https://bugs.launchpad.net/bugs/309734
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
23 matches
Mail list logo
