You are not logged in.
Hi.
My Asus laptop can't resume form suspend properly. The screen is black but the computer is running. I've seen https://bbs.archlinux.org/viewtopic.php?id=157579&p=2 ; changing the brightness does not help.
Also : https://bbs.archlinux.org/viewtopic.php?id=170008 ; Doesn't seem to be related since I have a 64bit installation. Google suggests adding acpi_backlight=vendor to able to increase the brightness after resuming from suspend, but that command breaks other things on my system. There's also a workaround using xbacklight but I'm looking for a fix.
It's not DE related, but on KDE, it sometime breaks one of my USB ports, and I have to shutdown - reboot - shutdown to get it to work again.
kernel 3.11.2, x86-64, using the ATI driver, early KMS, acpi_osi=Linux; uefi installation
cat /etc/fstab
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda2
UUID=af948ed2-5323-4198-bba3-c75b2f7a073e / ext4 rw,relatime,data=ordered 0 1
# /dev/sda3
UUID=595df887-6801-4024-a9df-60ac7787a668 /home ext4 rw,relatime,data=ordered 0 2
# /dev/sda1
UUID=033C-3291 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
lsusb
Bus 004 Device 003: ID 04f2:b23b Chicony Electronics Co., Ltd
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 046d:c066 Logitech, Inc.
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet K-2024 Multimedia Keyboard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Any thoughts? The Xorg conf file looks clean
Edit
I've managed to get before/after dmesg logs. So, the system works but it looks like the LCD is not powered thus trying to increase the brightness doesn't work not even with acpi_backlight=vendor
dmesg
Before: http://pastebin.com/DnGQZktR
After: http://pastebin.com/q0eFKmZy
Last edited by archie0 (2013-09-30 07:05:02)
Offline
It seems to be an old bug that affects newer AMD A-series CPUs.
https://bugs.freedesktop.org/show_bug.cgi?id=43829
https://bugs.archlinux.org/task/37078
Offline