Installation and configuration of the NVIDIA Accelerated Linux Driver Set on a notebook is the same as for any desktop environment, with a few minor exceptions, listed below.
Starting with the 1.0-2802 release, information about the internal flat panel for use in initializing the display is by default generated on the fly from data stored in the video BIOS. This can be disabled by setting the "SoftEDIDs" kernel option to 0. If "SoftEDIDs" is turned off, then hardcoded data will be chosen from a table, based on the value of the "Mobile" kernel option.
The "Mobile" kernel option can be set to any of the following values:
| Value | Meaning |
|---|---|
| 0xFFFFFFFF | let the kernel module autodetect the correct value |
| 1 | Dell notebooks |
| 2 | non-Compal Toshiba notebooks |
| 3 | all other notebooks |
| 4 | Compal Toshiba notebooks |
| 5 | Gateway notebooks |
Again, the "Mobile" kernel option is only needed if SoftEDIDs is disabled; when it is used, it is usually safest to let the kernel module autodetect the correct value (this is the default behavior).
If you need to alter either of these options, you may do so in any of the following ways:
editing os-registry.c in the usr/src/nv/ directory of the
.run file.
setting the value on the modprobe command line (e.g.:
modprobe nvidia NVreg_SoftEDIDs=0
NVreg_Mobile=3)
adding an "options" line to your module configuration file,
usually /etc/modules.conf (e.g.:
options nvidia
NVreg_Mobile=5)
In this section we discuss additional functionality associated with notebook configuration.
All mobile NVIDIA GPUs support TwinView. TwinView on a notebook can be configured in the same way as on a desktop computer (refer to Chapter 13, Configuring TwinView ); note that in a TwinView configuration using the notebook's internal flat panel and an external CRT, the CRT is the primary display device (specify its HorizSync and VertRefresh in the Monitor section of your X config file) and the flat panel is the secondary display device (specify its HorizSync and VertRefresh through the SecondMonitorHorizSync and SecondMonitorVertRefresh options).
The "UseEdidFreqs" X config option is enabled by default, so normally you should not need to specify the "SecondMonitorHorizSync" and "SecondMonitorVertRefresh" options. See the description of the UseEdidFreqs option in Appendix B, X Config Options for details).
Besides TwinView, mobile NVIDIA GPUs also have the capacity to react to an LCD/CRT hot key event, toggling between each of the connected display devices and each possible combination of the connected display devices (note that only 2 display devices may be active at a time). TwinView as configured in your X config file and hot key functionality are mutually exclusive -- if you enable TwinView in your X config file, then the NVIDIA X driver will ignore LCD/CRT hot key events.
Another important aspect of hot key functionality is that you can dynamically connect and remove display devices to/from your notebook and use the hot key to activate and deactivate them without restarting X.
When X is started, or when a change is detected in the list of connected display devices, a new hot key sequence list is constructed -- this lists which display devices will be used with each hot key event. When a hot key event occurs, the next hot key state in the sequence is chosen. Each mode requested in the X config file is validated against each display device's constraints, and the resulting modes are made available for that display device. If multiple display devices are to be active at once, then the modes from each display device are paired together; if an exact match (same resolution) cannot be found, then the closest fit is found, and the display device with the smaller resolution is panned within the resolution of the other display device.
When switching away from X to a virtual terminal, the VGA console will always be restored to the display device on which it was present when X was started. Similarly, when switching back into X, the same display device configuration will be used as when you switched away, regardless of what LCD/CRT hot key activity occurred while the virtual terminal was active.
Some users have had difficulty programming a 1400x1050 mode (the native resolution of some notebook LCDs). In version 4.0.3, XFree86 added several 1400x1050 modes to its database of default modes, but if you are using an older version of XFree86, the following ModeLine may be useful:
# -- 1400x1050 --
# 1400x1050 @ 60Hz, 65.8 kHz hsync
Modeline "1400x1050" 129 1400 1464 1656 1960
1050 1051 1054 1100 +HSync +VSync
There are a few known issues associated with notebooks:
LCD/CRT hot key switching is not currently functioning on any Toshiba notebook, with the exception of the Toshiba Satellite 3000 series.
TwinView on Satellite 2800 series Toshiba notebooks is not currently functioning.
The video overlay only works on the first display device on which you started X. For example, if you start X on the internal LCD, run a video application that uses the video overlay (uses the "Video Overlay" adapter advertised through the XV extension), and then hot key switch to add a second display device, the video will not appear on the second display device. To work around this, you can either configure the video application to use the "Video Blitter" adapter advertised through the XV extension (this is always available), or hot key switch to the display device on which you want to use the video overlay *before* starting X.