QA:Testcase nouveau vt

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
Line 3: Line 3:
 
|actions=
 
|actions=
 
# Ensure the 'nomodeset' kernel parameter is not enabled in your bootloader configuration
 
# Ensure the 'nomodeset' kernel parameter is not enabled in your bootloader configuration
# Ensure the file /etc/X11/xorg.conf does not exist, or is a known-good configuration file that uses the 'intel' driver
+
# Ensure the file {{filename|/etc/X11/xorg.conf}} does not exist, or is a valid file that uses the ''nouveau'' driver. If you are using the live image, ignore this step
 
# Shut your system down entirely, then start it up again
 
# Shut your system down entirely, then start it up again
 
# Switch to a virtual console: ctrl-alt-F2
 
# Switch to a virtual console: ctrl-alt-F2

Revision as of 18:09, 10 September 2009

Description

This test case tests whether virtual terminal switching works successfully with the Nouveau video driver, with kernel mode setting enabled. You must be using a video adapter supported by the driver, and Rawhide.


How to test

  1. Ensure the 'nomodeset' kernel parameter is not enabled in your bootloader configuration
  2. Ensure the file /etc/X11/xorg.conf does not exist, or is a valid file that uses the nouveau driver. If you are using the live image, ignore this step
  3. Shut your system down entirely, then start it up again
  4. Switch to a virtual console: ctrl-alt-F2
  5. Log in to the console (as user root with no password, if you are using a live image to test), and run a test command
  6. Switch back to the graphical desktop: ctrl-alt-F1
  7. Switch back and forth again

Expected Results

  1. Switching between the graphical desktop and a virtual console should work correctly
  2. Both the virtual console and the graphical desktop should be displayed correctly, and this should work through repeated switches between the two
  3. If you are using the Test Day live CD image, you may see multiple xkb errors when switching back to the graphical desktop - this is a known issue, it does not need to be reported