Note: The system does not hang. I can ssh into the system and execute commands successfully.
Also, external displays work fine. I have currently attached the laptop to a HDMI display, and the laptop continues to send video output to the HDMI display. So, I can continue to use it that way. It is only the LVDS panel that does not display anything. Here are the steps I have taken to try and fix the problem so far: Tried troubleshooting steps here: https://wiki.archlinux.org/index.php/Backlight to no avail. acpi_osi kernel parameter - BIOS may query the OS to find out which OS it is (Windows, Linux, etc.) and appropriately disable/enable certain features to ensure compatibility. When BIOS asks Linux if it is a Linux system, by default Linux ignores the query (so that all features are exposed). acpi_osi allows users to override that behaviour. The value for acpi_osi will be given to the BIOS by Linux when BIOS queries the OS. Tried following kernel parameters: video.use_native_nacklight=1 acpi_osi=Linux acpi_backlight=vendor acpi_backlight=legacy systemd.restore_state=0 acpi_osi=Linux acpi_osi=Windows Did not affect outcome. Tried using pm-suspend with following quirks: quirk-radeon-off quirk-dpms-on quirk-s3-bios quirk-vbe-post quirk-dpms-suspend quirk-s3-mode Did not affect outcome. Stored following code in /etc/pm/sleep.d/00displaywakeup : #!/bin/sh # case "$1" in suspend) ;; resume) sleep 5 vbetool dpms off vbetool dpms on ;; *) exit $NA ;; esac Did not affect outcome. Executed: radeontool light on Did not affect outcome. - Sandeep On Thu, Mar 27, 2014 at 8:34 PM, Sandeep <sandy.8925 at gmail.com> wrote: > I am currently facing a problem on my laptop (an ASUS K53TA). The LVDS > display is blank (no backlight) after suspending and resuming. > > On Windows, using AMD's Catalyst driver the display is still active after > suspend and resume, so the problem occurs only in Linux. > > I am running Arch Linux 64 bit , with Linux kernel 3.13.6. I have filed a > bug report already: https://bugs.freedesktop.org/show_bug.cgi?id=42960 > > I have faced this problem since Linux kernel 3.2 , so as far as I know it > is not a regression. > > I had used AMD's Catalyst drivers for some time, and the same problem had > occurred with those drivers as well, but the problem was fixed in later > versions of the Catalyst driver. > > I want to figure out why this problem occurs and find a permanent fix. > > Could someone please tell me if the GPU driver is the only code > responsible for bringing up the display, or are other parts of the kernel > involved as well? How would I begin to debug this issue? > > Thanks in advance, > Sandeep > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140327/8d357554/attachment-0001.html>
