with the comments on the "wrong" kernel I had a different scramble
pattern in comment #16 but then just like in #31, comment #17 actually
suspended the laptop with the same pattern of flicker it "normally" does
after resuming from a suspend.
--
You received this bug notification because you are a
of all of those suspend attempts, the only one that triggered the
scrambled flickering display was the one where it actually suspended:
comment #31.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1
Xorg.0.log.old
** Attachment added: "Xorg.0.log.old"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588740/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpa
Xorg.0.log
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588739/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/15
done for now
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1552417
Title:
[X1100] Flickering after resume from RAM
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
step 7
platform
just like before, no real suspend, no screen issues. Issued shell
command and when it finished (screen lit up again) and chose Suspend
from gear menu with same result
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/45887
step 9
core
same as before ; no real suspend. shell command then Suspend from gear
menu
launchpad is reporting a timeout error so I"m having trouble attaching dmesg
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588735/+files/dmesg.
step 6
devices
just like before, shell command did not fully suspend, and neither did choosing
Suspend from Gear menu, but I did both.
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588725/+files/dmesg.txt
--
You received this bug
step 10
none
laptop did go into suspend using shell command and I resumed by pressing
keys on the keyboard.
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588736/+files/dmesg.txt
--
You received this bug notification because you a
step 11
suspend stats
** Attachment added: "suspend_stats.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588737/+files/suspend_stats.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://
step 5
freezer
laptop did not suspend using the shell command so I also chose the
Suspend command from the Gear menu, which triggered a partial suspend
and self-resume (screen went black but power light did not go out and
fan did not stop and screen did not get scrambled)
** Attachment added: "d
step 8
processors
just like before, no real suspend, no screen issues. Issued shell
command and when it finished chose Suspend from gear menu
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588727/+files/dmesg.txt
--
You received th
merle@AcerA5100:~$ uname -a
Linux AcerA5100 4.5.0-040500rc6-generic #201602281230 SMP Sun Feb 28 17:33:02
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Step 4 wakeup
** Attachment added: "wakeup"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588712/+files/wakeup
--
Yo
I see now; I should use the http://kernel.ubuntu.com/~kernel-
ppa/mainline/?C=N;O=D link and I should ignore the
http://people.canonical.com/~kernel/info/kernel-version-map.html
SO I just got back and I will download http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.5-rc6-wily/
--
You received t
Yes I followed that link, which identified the mainline kernel 4.4.3 as
the one for xenial. Please tell me which kernel I should have installed.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/15524
/var/log/Xorg.0.log.old
** Attachment added: "Xorg.0.log.old"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588451/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.
/var/log/Xorg.0.log (step 12)
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588450/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.la
done for now
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1552417
Title:
[X1100] Flickering after resume from RAM
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
echo none (step 10)
This time entering the sudo sh -c "sync && echo 1 > /sys/power/pm_trace
&& pm-suspend"
command DID actually suspend the laptop, and I resumed the laptop by
pressing a key on the keyboard.
Now the screen is scrambled as it "normally" does after a suspend.
** Attachment added
stats (step 11)
** Attachment added: "stats.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588449/+files/stats.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs
core (step 9)
this time, while the laptop never seemed to go into suspend, the display
is scrambled (I am entering this via vnc). The scramble is in a
different pattern (more consistent than the usual post-suspend scramble)
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+s
processors (stop 8)
the laptop still did not actually suspend (the screen blanks and
restores but suspend never happens)
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588442/+files/dmesg.txt
--
You received this bug notification b
echo platform (step 7)
the laptop still did not suspend
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588441/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg i
this time I tried issuing the command then choosing Suspend from the
menu then pressing power and choosing suspend from the graphical suspend
button and then I tried holding down the lid switch for many seconds
the laptop will not go into suspend.
** Attachment added: "dmesg.txt"
https://bug
echo devices (step 6)
the laptop is still not going into suspend
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588440/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
second attempt at step 5
the laptop never actually suspended after issuing
sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"
so I chose Suspend from the gear menu and the screen blanked briefly and
still did not suspend
** Attachment added: "second attempt"
https://bugs.launch
step 5
** Attachment added: "dmesg step 5"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588423/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/15524
oops sorry I need to redo step 5
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1552417
Title:
[X1100] Flickering after resume from RAM
To manage notifications about this bug go to:
https://bug
step 4 wakeup file
** Attachment added: "wakeup file step 4"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552417/+attachment/4588422/+files/wakeup
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad
Installed xenial from a recent daily image
consulted https://wiki.ubuntu.com/Kernel/MainlineBuilds
and selected kernel 4.4.3
Installed kernel using these 3 packages
linux-headers-4.4.3-040403_4.4.3-040403.201602251634_all.deb
linux-headers-4.4.3-040403-generic_4.4.3-040403.201602251634_amd64.
Installed xenial from a recent daily image
consulted https://wiki.ubuntu.com/Kernel/MainlineBuilds
and selected kernel 4.4.3
Installed kernel using these 3 packages
linux-headers-4.4.3-040403_4.4.3-040403.201602251634_all.deb
linux-headers-4.4.3-040403-generic_4.4.3-040403.201602251634_amd64.
I believe I can do this, however it will take quite a bit more
preparation and effort (because of the radeon Xpress 1100 bug I cannot
use the display on this laptop after any successful resume from suspend)
I am also testing from a live image with no persistent storage, so I
will need to do someth
I just booted from today's (02 March 2016) xenial-desktop-amd64.iso. I
had trouble getting the machine to suspend, but once it did and resumed
from suspend, it showed the same flickering screen behavior.
If you need an apport bug collection or any other data from this image,
it should work. Let me
Public bug reported:
Same defect as old Bug #318325
same hardware as Bug #1333697
System : Ubuntu 15.10 "wily"
GPU : ATI express X1100
Video driver : radeon
Steps to reproduce :
- choose suspend
- resume from ram
=> the screen will flicker while CPU activity is not high
workaround :
- launch a
I have the same hardware as reported in Bug #1333697
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/318325
Title:
[X1100] flickering after resume from ram
To manage notifications about this bug
I can confirm the bug still exists in Trusty, and I just tried a Wily
live image and it exists there, too. The affected hardware is getting a
bit old but still seems to work fine with Ubuntu in all other ways.
As I am not Id2ndR should I run apport-collect on a new bug and mark it
as a duplicate o
I just checked the user account, and I get some sort of crash in
blueman-applet. This laptop has no physical bluetooth hardware installed
(though it has a switch and presumably an empty socket inside). For
whatever reason gnome's Startup Applications app lists blueman-applet as
the sole startup app
The brand sticker on this Acer Aspire 5100-3949 laptop says "Radeon Xpress
1100" and lspci says:
...
01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS482
[Radeon Xpress 200M]
...
I believe it's using the (sub-optimal but mostly functional) open-source radeon
driver.
Al
*** This bug is a duplicate of bug 318325 ***
https://bugs.launchpad.net/bugs/318325
oops -- did I remove this from ubuntu-x-swat by making it a duplicate?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
htt
*** This bug is a duplicate of bug 318325 ***
https://bugs.launchpad.net/bugs/318325
** This bug has been marked a duplicate of bug 318325
[X1100] flickering after resume from ram
* You can subscribe to bug 318325 by following this link:
https://bugs.launchpad.net/ubuntu/+source/xserver-
*** This bug is a duplicate of bug 318325 ***
https://bugs.launchpad.net/bugs/318325
same as Bug #318325 ?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
https://bugs.launchpad.net/bugs/605225
Title:
ret
*** This bug is a duplicate of bug 318325 ***
https://bugs.launchpad.net/bugs/318325
** This bug has been marked a duplicate of bug 318325
[X1100] flickering after resume from ram
* You can subscribe to bug 318325 by following this link:
https://bugs.launchpad.net/ubuntu/+source/xserver-
activated the xorg-edgers PPA, and found that with KMS disabled, xorg
segfaults and will not operate at all, and I could not even use any
console terminals. Fortunately I had installed sshd so I could ssh in
via the network and remove /etc/modprobe.d/radeon-kms.conf
--
You received this bug notif
On this Acer Aspire 5100 I just tried the following:
-- disabled KMS using # echo options radeon modeset=0 >
/etc/modprobe.d/radeon-kms.conf
but disabling KMS had no noticeable effect on flicker.
-- tried vesa driver by creating an xorg.conf
The vesa driver came up in low
I noticed upstream http://bugs.freedesktop.org/show_bug.cgi?id=20478
asked whether it's a problem with a newer version of the driver or with
KMS so I am trying to learn how to figure this out. I believe the xorg-
edgers PPA tested the newer version but until now I wasn't aware of KMS
at all.
I hav
Tried the xorg-edgers PPA and it did not apparently affect this bug; the
screen still flickers after suspend.
HOWEVER as a side note, Unity works with the newer xorg.
--
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xserver-xorg-driver-ati.
New install of Maverick UNE to a new (to me) Acer Aspire 5100-3949. Ran
into this bug, and going through the workarounds. So far the only
workaround that "works" is the one in Bug #576181 (keep the processor
busy with a bash script). Yuck. Especially if you're on battery.
Just tried the Ubuntu-X P
I downloaded an iso of the daily build for Saturday-- Ubuntu 9.10
"Karmic Koala" - Alpha i386 (20090829.2). I booted the iso "live" from a
USB stick and I did not see the reported behavior. Yay!
For a complete test I also copied an iso of the 9.04 "Jaunty Jackelope"
to a USB stick and booted it in
I changed the summary to better reflect my current understanding.
--
full resolution on ATI Radeon X300 card requires tweaking
https://bugs.launchpad.net/bugs/370103
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
you are right; not sure what I had done, but I just removed the radeonhd
driver and it still works. I'm not sure what I did to fix it, either. I
am changing the description. Besides installing radeonhd, all I did was
work with the Display Settings tool and log in and out several times.
For whatever
50 matches
Mail list logo