From Fedora Project Wiki

(drop the file removal workaround)
(use module parameter)
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{QA/Test_Case
{{Testcase_video_suspend|driver=radeon|module=radeon}}
|description=This test case tests whether suspend / resume works successfully with the Radeon video driver, with kernel mode setting enabled. You must be using a card supported by the Radeon video driver. Your system must be capable of suspending and resuming normally (for instance, it worked in previous Fedora releases).
[[Category:Package_xorg-x11-drv-ati_core_test_cases]]
|actions=
# Ensure the 'nomodeset' kernel parameter is not enabled in your bootloader configuration (unless you need it for basic X operation to suceed)
# Ensure the file /etc/X11/xorg.conf does not exist, or is a known-good configuration file that uses the 'radeon' driver
# Shut your system down entirely, then start it up again
# Suspend the system (for e.g. left click the battery icon and click 'suspend')
# Resume the system
|results=
# The system should come back with the display correct and at the correct resolution, backlight active, etc.
}}
[[Category:Radeon_Test_Cases]]

Latest revision as of 14:44, 10 January 2011

Description

This test case tests whether suspend / resume works successfully with the radeon video driver, with kernel mode setting enabled. You must be using a card supported by the radeon video driver. Your system must be capable of suspending and resuming normally (for instance, it worked in previous Fedora releases, or works if you boot to runlevel 3: otherwise please file a bug against the kernel).

Setup

  1. Ensure the nomodeset and radeon.modeset=0 kernel parameters are not set in your bootloader configuration
    • You can see your current kernel options by running cat /proc/cmdline
  2. Ensure the file /etc/X11/xorg.conf does not exist, or is a valid file that uses the radeon driver
  3. Shut your system down entirely, then start it up again
  4. If using a live image to test, ignore the above steps and simply boot the system from the live image with default options

How to test

  1. If the system has backlight control keys, test them and check if they work
  2. Suspend the system (for example open the system menu, then hold down Alt and click the button that looks like a 'Pause' symbol; or on a laptop, you can close the lid. If no manual Suspend operation is available, you can run pm-suspend as root at a console)
  3. Resume the system
  4. If the system has backlight control keys, test them and check if they work again
Try with all display connectors
If your system has multiple display connectors, and you have the appropriate displays and cables/adapters, it is good to test again with different combinations of displays connected and ensure all connected displays work correctly on resume.

Expected Results

  1. The system should come back with the display correct and at the correct resolution, backlight active, etc.
  2. If the system has brightness control keys, and they work to control the backlight before suspending, they should also work afterwards