Public bug reported:
On first boot, the touchscreen works. After reboot it doesn't. Reboot
again and it works. Reboot again and it doesn't work. And so on. I have
discovered a workaround, which is to run "echo 1 >
/sys/bus/pci/devices/\:00\:15.1/remove" before rebooting. With a
script
Confirmed workaround: adding intel_idle.max_cstate=0 to kernel boot
parameters works for me (N210 Plus) with latest Maverick Kernel
(2.6.35-24-generic).
Thanks, Daniel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same here with a Samsung NP-N210 Plus, BIOS version 01KY. Kernel 2.6.34
(as advised in #75 above) fixes this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/640100
Title:
Maverick fails to wake up
3410T here as well, but I had to implement the fix under Maverick. Did you
upgrade from Lucid with the fix applied? May be it carried through.
On 11 October 2010 21:48, Chris Wilson 405...@bugs.launchpad.net
wrote:
I can confirm that this problem is no longer affecting my Acer Timeline
3410T
Many, many thanks.
I can confirm that the fix works on 3410T with Bios 1.10
Darrell
--
resume from suspend doesn't work (powers off instead) for various Acer Timeline
laptops
https://bugs.launchpad.net/bugs/405120
You received this bug notification because you are a member of Ubuntu
Bugs,
3410T, Bios 1.14, Kernel 2.6.31-11-generic (64 bit) - suspend still does
not work
--
resume from suspend doesn't work (powers off instead) for Acer Timeline
3810t/3410t
https://bugs.launchpad.net/bugs/405120
You received this bug notification because you are a member of Ubuntu
Bugs, which is
In my request to Acer, I told them that the same problem with the 4810T
has been reported to have been solved after a BIOS update, so hopefully
I have pointed them in the right direction. Still, I think that
experience tells us that when there is an incompatibility between Linux
and a hardware
I've submitted a problem report on the Acer UK website. I'm sure the
official response will be that they do not support Linux (true of
course), Suspend does work under Vista.
--
resume from suspend doesn't work (powers off instead) for Acer Timeline
3810t/3410t
A quick note to confirm that the bug is still present under Kernel
2.6.31-10
--
resume from suspend doesn't work (powers off instead) for Acer Timeline
3810t/3410t
https://bugs.launchpad.net/bugs/405120
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 405120 ***
https://bugs.launchpad.net/bugs/405120
Public bug reported:
Duplicate of Bug #405120, submitted to make available the automatically-
gathered crash information. This is with the latest (at time of crash)
kernel 2.6.31-9.
ProblemType: KernelOops
*** This bug is a duplicate of bug 405120 ***
https://bugs.launchpad.net/bugs/405120
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/31252328/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/31252329/AplayDevices.txt
** Attachment
See bug #423320 for the automatically-gathered crash report info, Aspire
3410T under Kernel 2.6.31-9, Karmic, Bios updated to version 1.10. By
the way, the 3810T/3410T bios update from the Acer website sets the
model name to Acer Project replacing the original Aspire 3410T or
Aspire 3810T.
--
*** This bug is a duplicate of bug 405120 ***
https://bugs.launchpad.net/bugs/405120
** This bug has been marked a duplicate of bug 405120
resume from suspend doesn't work (powers off instead) for Acer Timeline
3810t/3410t
--
[Acer Aspire 3410] suspend/resume failure
I've changed the title of the bug to include the Aspire 3410T machine as
well. As this machine shares its BIOS code with the 3810T, it is very
likely to be the exact same problem. I would like to add that I'm ready
and waiting to perform any tests required by the developers in tracing
and fixing
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/30704721/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/30704722/AplayDevices.txt
** Attachment added: BootDmesg.gz
http://launchpadlibrarian.net/30704723/BootDmesg.gz
** Attachment
Public bug reported:
Acer Aspire 3410T - Suspend from the menu seemed to work (although it
took a good few seconds). Attempted resume by pressing space bar -
screen backlight flashed on and off, then computer immediately powered
off. I have seen similar reports for the Aspire 3810T, most likely
Here is an extract from my messages file, from starting a drm-enabled X
session to the necessary hard reset after the resume failure. Drm
debugging was switched on and I also have an enormous syslog if that
would be of any help.
Darrell
** Attachment added: messages
Tormod, yes, it certainly seemed messed up to me as well, but I thought
I would leave diagnosis to the expert :). The syslog/debug logs I have,
full of dri debug messages also have some screwed up parts. So, what is
the verdict so far - that using the current dri with the RC410 card
corrupts
I should add, that from the timing of the garbage debug messages, the
memory corruption (if that's what it is) is taking place during the
suspend processing, not the attempted resume.
--
[RC410] Xpress 200M hangs when resuming from suspend with DRI
https://bugs.launchpad.net/bugs/305301
You
Exactly the same here as it was for Giancaldo: backtrace using screen
impossible as networking does not return.
I also enabled drm debug during a suspend/attempted-resume cycle. There
are no messages in kern.log or syslog from drm after suspend until the
machine is hard-rebooted.
--
[RC410]
I can confirm that this behaviour persists under kernel 2.6.30rc3.
--
[RC410] Xpress 200M hangs when resuming from suspend with DRI
https://bugs.launchpad.net/bugs/305301
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
After further testing I can confirm that the machine resumes correctly
when DRI is disabled, but only if it has been rebooted after running X
with DRI enabled. Disabling DRI in xorg.conf and then restarting X is
not enough. My previous test without DRI must have been with no reboot
after disabling
** Attachment added: Xorg.0.log.radeon-no-dri-after-reboot
http://launchpadlibrarian.net/26041476/Xorg.0.log.radeon-no-dri-after-reboot
--
[RC410][FUJITSU SIEMENS AMILO Li 1718] suspend/resume failure
https://bugs.launchpad.net/bugs/353035
You received this bug notification because you are a
** Attachment added: Xorg.0.log.radeon-no-dri-no-reboot
http://launchpadlibrarian.net/26041430/Xorg.0.log.radeon-no-dri-no-reboot
--
[RC410][FUJITSU SIEMENS AMILO Li 1718] suspend/resume failure
https://bugs.launchpad.net/bugs/353035
You received this bug notification because you are a
*** This bug is a duplicate of bug 305301 ***
https://bugs.launchpad.net/bugs/305301
Ok, but should bug 305301 then be marked as affecting xserver-xorg-
video-ati?
--
[RC410][FUJITSU SIEMENS AMILO Li 1718] suspend/resume failure
https://bugs.launchpad.net/bugs/353035
You received this bug
** Also affects: xserver-xorg-driver-ati (Ubuntu)
Importance: Undecided
Status: New
--
[FUJITSU SIEMENS AMILO Li 1718] suspend/resume failure
https://bugs.launchpad.net/bugs/353035
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm now running Jaunty final, and suspend/resume now works when forcing
use of the vesa driver by using an xorg.conf:
Section Device
Identifier Configured Video Device
Driver vesa
EndSection
Therefore the problem would seem to be in the xserver-xorg-driver-ati package,
so I've added this bug to
I should also add that I have experimented with pm-suspend quirks
without success.
--
[FUJITSU SIEMENS AMILO Li 1718] suspend/resume failure
https://bugs.launchpad.net/bugs/353035
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
--
[FUJITSU SIEMENS AMILO Li 1718] suspend/resume failure
https://bugs.launchpad.net/bugs/353035
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This would seem to be an xorg-server problem rather than kernel (see
notes above). All packages up to date as at 23:00 BST 22nd April, the
problem still exists. I found a similar sounding bug at freedesktop.org,
http://bugs.freedesktop.org/show_bug.cgi?id=19581 but this is different
in that it
Sorry, addendum to above:
3. The failure to resume still occurs when using the vesa instead of the
radeon X driver.
--
[FUJITSU SIEMENS AMILO Li 1718] suspend/resume failure
https://bugs.launchpad.net/bugs/353035
You received this bug notification because you are a member of Ubuntu
Bugs, which
Further information:
1. I have followed the instructions at
https://wiki.ubuntu.com/DebuggingKernelSuspend, log attached.
2. Observed after attempted resume: power and wireless leds come on,
suspend led goes off. Screen backlight is switched on (there is a
flashing underscore cursor at the top
More information:
pm-suspend from a virtual terminal while X is running results in the same
failure to resume. However, pm-suspend from a virtual terminal when X is not
running results in a successful resume.
--
[FUJITSU SIEMENS AMILO Li 1718] suspend/resume failure
Public bug reported:
Suspend to RAM appears OK, kernel oops on resume. Standard 9.04 Beta
install, except I manually added /etc/modprobe.d/acerhk.conf: options
acerhk force_series=6805 autowlan=1 and added acerhk to /etc/modules
to enable the wireless radio on/off hotkey on this machine (ref bug
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/24624749/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/24624750/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/24624751/Dependencies.txt
**
I should add that this behaviour is the same under intrepid when using
the free ati driver, but suspend/resume works when using the fglrx
driver in intrepid. I cannot test the fglrx driver in Jaunty as it
causes a system freeze on starting X. Besides I would prefer to use the
free driver.
--
36 matches
Mail list logo
