Changes between Version 3 and Version 4 of Troubleshooting


Ignore:
Timestamp:
Dec 12, 2012, 12:16:43 AM (12 years ago)
Author:
David Azarewicz
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Troubleshooting

    v3 v4  
    33== Custom Resolutions ==
    44
    5 The custom resolution feature is experimental.  If you have problems with the custom resolution feature, the PanoUtil.exe program can be used to
    6 control the custom resolution functions. If you happen to boot to a resolution that cannot be displayed, you can type CTL-ALT-DEL to activate the CAD handler and go to a command prompt to execute these commands.
     5The custom resolution feature is experimental and may not work in all cases. The custom resolution feature works by patching the video BIOS. Newer Intel BIOS and ATI/ATOM BIOS are supported. Nvidia BIOS support is coming soon.
     6
     7By default, the Panorama driver will query the display resolution and timing (EDID) via the Display Data Channel (DDC).
     8If this succeeds, the Panorama driver will automatically convert the 1600x1200 entry in the list of available
     9resolutions that are displayed in the Screen Object settings to the native display resolution.
     10You can then select the desired resolution from the list. This is the best method of operation since the exact timings that are
     11provided by the display are used.
     12
     13If you have problems with the custom resolution feature, the !PanoUtil.exe program can be used to control the custom resolution functions.
     14If you happen to boot to a resolution that cannot be displayed, you can type CTL-ALT-DEL to activate the
     15CAD handler and go to a command prompt to execute these commands.
    716
    817To reset all the custom resolution settings to the default and set the PM resolution to 800x600:
     
    5665}}}
    57665. Attach the LOG file to your ticket.
     67
     68== Systems Running the Debug Kernel Might Get an Unexpected Trace Interrupt ==
     69
     70The video BIOS in some systems will sometimes generate an unexpected trace interrupt when the system is running the debug Kernel. You can simply disable the trace interrupt handling using the "vc 1" kernel debugger command.  Systems running the retail kernel are not affected.