[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
Hi, i solved this situation installing linux-image-generic-lts-backports-natty in lucid: sudo add-apt-repository ppa:kernel-ppa/ppa (this command requires the package python-software-properties to be installed) sudo aptitude update sudo aptitude install linux-image-generic-lts-backport-natty linux-headers-generic-lts-backport-natty with kernel 2.6.37-12 this problem is not present, so you can use your touchpad normally and yo can scroll vertically. If you have the NVIDIA graphic card you have to install nvidia-current (260.19.06) and nvidia-current-modaliases (260.19.06) from maverick or natty packages suite. I hope this solution can be useful for people who doesn't like to rebuild kernel from sources. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550625 Title: Alps touchpad is recognized but synaptics clients and scrolling do not work -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 352987] Re: lm-sensors report incorrect values of CPU temparature
there is also the problem that others values too are wrong, like specified in bug 563114. As you can see values of +12V, -12V, etc are missing, and the problem are not tags but VALUES. Wha's the meaning of 4.08V in a computer? These values don't make sense!! This problems where not present in the package from karmic and jaunty. -- lm-sensors report incorrect values of CPU temparature https://bugs.launchpad.net/bugs/352987 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 352987] Re: lm-sensors report incorrect values of CPU temparature
there is also the problem that others values too are wrong, like specified in bug 563114. As you can see values of +12V, -12V, etc are missing, and the problem are not tags but VALUES. Wha's the meaning of 4.08V in a computer? These values don't make sense!! This problems where not present in the package from karmic and jaunty. -- lm-sensors report incorrect values of CPU temparature https://bugs.launchpad.net/bugs/352987 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 571707] Re: fsck progress stalls at boot, plymouthd/mountall eats CPU
i will post something more complete in late afternoon because i cannot connect to the desktop system now. laptop 32-bit: $ hwinfo --bios |grep Socket Socket: uFCPGA2 Socket Type: 0x04 (ZIF Socket) Socket Status: Populated Location: 0x00 (Internal, Not Socketed) $ hwinfo --gfxcard 22: PCI(AGP) 100.0: 0300 VGA compatible controller (VGA) [Created at pci.318] UDI: /org/freedesktop/Hal/devices/pci_1002_4e50 Unique ID: VCu0.PkvpIaxQqbF Parent ID: vSkL.oF7y00qHwA3 SysFS ID: /devices/pci:00/:00:01.0/:01:00.0 SysFS BusID: :01:00.0 Hardware Class: graphics card Model: ATI RV350 NP Vendor: pci 0x1002 ATI Technologies Inc Device: pci 0x4e50 RV350 NP SubVendor: pci 0x1025 Acer Incorporated [ALI] SubDevice: pci 0x005d Memory Range: 0xd800-0xdfff (rw,prefetchable) I/O Ports: 0x3000-0x3fff (rw) Memory Range: 0xd010-0xd010 (rw,non-prefetchable) Memory Range: 0xd012-0xd013 (ro,prefetchable,disabled) IRQ: 11 (116070 events) I/O Ports: 0x3c0-0x3df (rw) Module Alias: pci:v1002d4E50sv1025sd005Dbc03sc00i00 Driver Info #0: XFree86 v4 Server Module: radeon Driver Info #1: XFree86 v4 Server Module: radeon 3D Support: yes Extensions: dri Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #11 (PCI bridge) i have these problem the problem of fsck stall with both dri (KMS disabled) and dri2 desktop 64-bit: Core Duo Q9400 (socket 775) Ati Radeon 4870x2 (fglrx driver from ubuntu packages) I hope this could help for the moment... i'll post other informations about 64-bit system later -- fsck progress stalls at boot, plymouthd/mountall eats CPU https://bugs.launchpad.net/bugs/571707 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 571707] Re: fsck progress stalls at boot, plymouthd/mountall eats CPU
to letstrynl: hwinfo --gfxcard | grep Modules doesn't produce any output. do you mean hwinfo --gfxcard | grep Model?? desktop 32-bit bios: Socket: uFCPGA2 video: Model: ATI RV350 NP -- fsck progress stalls at boot, plymouthd/mountall eats CPU https://bugs.launchpad.net/bugs/571707 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 571707] Re: fsck progress stalls at boot, plymouthd/mountall eats CPU
only splash directive reproduces the bug. removing or not quiet directive doesn't change nothing in my case. quiet AND splash -- fsck stalls ONLY splash -- fsck stalls ONLY quiet -- all works fine NO both -- -- all works fine -- fsck progress stalls at boot, plymouthd/mountall eats CPU https://bugs.launchpad.net/bugs/571707 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
Re: [Bug 571707] Re: fsck progress stalls at boot, plymouthd/mountall eats CPU
hwinfo --bios | grep Socket requires root permission to produce the output. Fabio Marzocca try using sudo hwinfo --bios | grep Socket -- fsck progress stalls at boot, plymouthd/mountall eats CPU https://bugs.launchpad.net/bugs/571707 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 571707] Re: fsck progress stalls at boot, plymouthd/mountall eats CPU
hwinfo --bios | grep Socket requires root permission to produce the output. try using sudo hwinfo --bios | grep Socket -- fsck progress stalls at boot, plymouthd/mountall eats CPU https://bugs.launchpad.net/bugs/571707 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 571707] Re: fsck progress stalls at boot, plymouthd/mountall eats CPU
** Description changed: PROBLEM When a disk check is performed, the progress stalls somewhere around 70% and will then take a very long time finishing the remaining percent (10 minutes or more). TEST CASE: (sudo aptitude install bootchart) sudo touch /forcefsck sudo reboot POSSIBLE WORKAROUNDS 1. Removing quiet and splash from the kernel boot line 2. When the progress has stalled, switch away from the splash screen using the left arrowkey (presumably any arrowkey works). * Both these approaches speeds up the boot process to ~1 minute instead. OBSERVATIONS The fsck message (...) non-contiguous (...) Which I assume indicates the end of the fsck, is printed in the Virtual Terminal (outside plymouth) at around 70% + ~10-20 seconds. Disk activity is null from this point on (presumed end of fsck above). Bootchart crashes if trying to catch the whole boot at once with plymouth (at least for my 1h boot). This problem seems to occur in both plymouthd and mountall, semi-simultaneously: If you are in the plymouth screen, plymouthd is the cpu-gobbler, if you switch away from it using the arrow keys, mountall instead takes over the cpu-eating. - # ORIGINAL REPORT Binary package hint: mountall On my system when fsck runs at boot plymouth % completion count goes up quickly (10 seconds) up to about 80% and then slows down considerably: the complete fsck of my 125GB HD, 30% full takes more than 5 minutes. While this goes on the text VTs are all completely blank: just a blinking cursor. An fsck from a recovery disk completes in ~10 seconds so it doesn't look like fsck just being slow. This slowdown was *not* happening on 2010-04-14 with the PPA described by this comment: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/554737/comments/25 The fix in the PPA is now in the mainline lucid but somewhere in between then and today (2010-04-29) something introduced this slowdown. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: mountall 2.14 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Thu Apr 29 15:38:56 2010 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta i386 (20100317.1) ProcEnviron: LANGUAGE=en_IE:en_GB:en PATH=(custom, user) LANG=en_IE.utf8 SHELL=/bin/bash SourcePackage: mountall -- fsck progress stalls at boot, plymouthd/mountall eats CPU https://bugs.launchpad.net/bugs/571707 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 571707] Re: fsck progress stalls at boot, plymouthd/mountall eats CPU
the installation on my desktop computer was a fresh install and it is NOT AFFECTED from this bug. the installation on my laptop is an upgrade from karmic and it is AFFECTED from this bug. all these two installations where done starting from release candidate and are now updated. could the bug be related to DISTRIBUTION UPGRADE (i.e. from karmic)? -- fsck progress stalls at boot, plymouthd/mountall eats CPU https://bugs.launchpad.net/bugs/571707 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 563114] [NEW] w83697hf-isa-0290 wrong voltage values and tags
Public bug reported: Binary package hint: lm-sensors 1) Linux pcl0 2.6.32-20-generic #30-Ubuntu SMP Mon Apr 12 15:19:41 UTC 2010 i686 GNU/Linux Ubuntu 10.04 (lucid) $ lsb_release -rd Description:Ubuntu lucid (development branch) Release:10.04 2) $ apt-cache policy lm-sensors lm-sensors: Installato: 1:3.1.2-2 Candidato: 1:3.1.2-2 Tabella versione: *** 1:3.1.2-2 0 500 http://it.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status 3) command sensors it's expected to report voltages for core, 3.3V, 5V, 12V, etc... something like this: $ sensors w83697hf-isa-0290 Adapter: ISA adapter VCore: +1.90 V (min = +0.00 V, max = +0.00 V) ALARM +3.3V: +3.38 V (min = +0.26 V, max = +0.06 V) ALARM +5V: +5.03 V (min = +0.00 V, max = +0.00 V) ALARM +12V: +11.37 V (min = +0.00 V, max = +0.49 V) ALARM -12V: +0.55 V (min = -14.91 V, max = -14.91 V) ALARM -5V: +1.79 V (min = -7.71 V, max = -7.71 V) ALARM V5SB: +5.56 V (min = +0.00 V, max = +0.00 V) ALARM VBat: +3.28 V (min = +0.00 V, max = +0.00 V) ALARM ... 4) when i execute sensors command i obtain the following answer: $ sensors acpitz-virtual-0 Adapter: Virtual device temp1:+0.0°C (crit = +60.0°C) w83697hf-isa-0290 Adapter: ISA adapter in0: +1.65 V (min = +3.66 V, max = +1.06 V) ALARM in2: +3.31 V (min = +3.87 V, max = +1.57 V) ALARM in3: +2.99 V (min = +2.61 V, max = +2.27 V) ALARM in4: +3.26 V (min = +2.51 V, max = +0.08 V) ALARM in5: +0.78 V (min = +0.10 V, max = +1.81 V) in6: +3.58 V (min = +1.87 V, max = +1.76 V) ALARM in7: +3.30 V (min = +2.93 V, max = +0.59 V) ALARM in8: +3.09 V (min = +3.95 V, max = +2.69 V) ALARM fan1: 1493 RPM (min = 2033 RPM, div = 8) ALARM fan2:992 RPM (min = 168750 RPM, div = 8) ALARM temp1: +26.0°C (high = -10.0°C, hyst = -100.0°C) ALARM sensor = thermistor temp2: -77.5°C (high = +120.0°C, hyst = +115.0°C) sensor = transistor beep_enable:enabled As you can see voltages seems to have abnormal values and tags are strange (in0, in2, in3, ecc...). I used this package in the past with ubuntu server 8.04 with 2.6.24 kernel and 9.10 with 2.6.31 kernel and all was functioning good. Thanks!! ** Affects: lm-sensors (Ubuntu) Importance: Undecided Status: New ** Tags: w83697hf w83697hf-isa-0290 -- w83697hf-isa-0290 wrong voltage values and tags https://bugs.launchpad.net/bugs/563114 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 563114] [NEW] w83697hf-isa-0290 wrong voltage values and tags
Public bug reported: Binary package hint: lm-sensors 1) Linux pcl0 2.6.32-20-generic #30-Ubuntu SMP Mon Apr 12 15:19:41 UTC 2010 i686 GNU/Linux Ubuntu 10.04 (lucid) $ lsb_release -rd Description:Ubuntu lucid (development branch) Release:10.04 2) $ apt-cache policy lm-sensors lm-sensors: Installato: 1:3.1.2-2 Candidato: 1:3.1.2-2 Tabella versione: *** 1:3.1.2-2 0 500 http://it.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status 3) command sensors it's expected to report voltages for core, 3.3V, 5V, 12V, etc... something like this: $ sensors w83697hf-isa-0290 Adapter: ISA adapter VCore: +1.90 V (min = +0.00 V, max = +0.00 V) ALARM +3.3V: +3.38 V (min = +0.26 V, max = +0.06 V) ALARM +5V: +5.03 V (min = +0.00 V, max = +0.00 V) ALARM +12V: +11.37 V (min = +0.00 V, max = +0.49 V) ALARM -12V: +0.55 V (min = -14.91 V, max = -14.91 V) ALARM -5V: +1.79 V (min = -7.71 V, max = -7.71 V) ALARM V5SB: +5.56 V (min = +0.00 V, max = +0.00 V) ALARM VBat: +3.28 V (min = +0.00 V, max = +0.00 V) ALARM ... 4) when i execute sensors command i obtain the following answer: $ sensors acpitz-virtual-0 Adapter: Virtual device temp1:+0.0°C (crit = +60.0°C) w83697hf-isa-0290 Adapter: ISA adapter in0: +1.65 V (min = +3.66 V, max = +1.06 V) ALARM in2: +3.31 V (min = +3.87 V, max = +1.57 V) ALARM in3: +2.99 V (min = +2.61 V, max = +2.27 V) ALARM in4: +3.26 V (min = +2.51 V, max = +0.08 V) ALARM in5: +0.78 V (min = +0.10 V, max = +1.81 V) in6: +3.58 V (min = +1.87 V, max = +1.76 V) ALARM in7: +3.30 V (min = +2.93 V, max = +0.59 V) ALARM in8: +3.09 V (min = +3.95 V, max = +2.69 V) ALARM fan1: 1493 RPM (min = 2033 RPM, div = 8) ALARM fan2:992 RPM (min = 168750 RPM, div = 8) ALARM temp1: +26.0°C (high = -10.0°C, hyst = -100.0°C) ALARM sensor = thermistor temp2: -77.5°C (high = +120.0°C, hyst = +115.0°C) sensor = transistor beep_enable:enabled As you can see voltages seems to have abnormal values and tags are strange (in0, in2, in3, ecc...). I used this package in the past with ubuntu server 8.04 with 2.6.24 kernel and 9.10 with 2.6.31 kernel and all was functioning good. Thanks!! ** Affects: lm-sensors (Ubuntu) Importance: Undecided Status: New ** Tags: w83697hf w83697hf-isa-0290 -- w83697hf-isa-0290 wrong voltage values and tags https://bugs.launchpad.net/bugs/563114 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
