| 1 | DisplayLink Driver for CentOS |
| 2 | ============================= |
| 3 | |
| 4 | |
| 5 | Description |
| 6 | =========== |
| 7 | |
| 8 | This software should be installed into a CentOS 5.3 system. The supplied xorg.conf |
| 9 | assumes an Intel based graphics system, but there are also examples for Nvidia. |
| 10 | |
| 11 | |
| 12 | Installation |
| 13 | ============ |
| 14 | |
| 15 | Full installation |
| 16 | ----------------- |
| 17 | |
| 18 | The following steps should be taken to install the driver package: |
| 19 | |
| 20 | 1. Copy the existing xorg.conf file |
| 21 | |
| 22 | 1.1. $ sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.old |
| 23 | |
| 24 | 2. Install the driver package: |
| 25 | |
| 26 | 2.1. plug in the DisplayLink device |
| 27 | 2.2. build and install the FBDisplaylink driver |
| 28 | 2.3. build and install the XorgDisplaylink software |
| 29 | |
| 30 | 3. $ sudo /sbin/depmod -a |
| 31 | |
| 32 | At this point the screen attached to the DisplayLink device should go red |
| 33 | indicating that the FBDisplaylink kernel driver has loaded. |
| 34 | |
| 35 | 4. Edit the new xorg.conf to select the display configuration: |
| 36 | |
| 37 | 4.1. $ sudo emacs /etc/X11/xorg.conf |
| 38 | |
| 39 | At the bottom of this file are the following configration statements: |
| 40 | |
| 41 | |
| 42 | ############################################################## |
| 43 | # |
| 44 | # Screen layout |
| 45 | # |
| 46 | Section "ServerLayout" |
| 47 | Identifier "Multihead nvidia" |
| 48 | Screen 0 "nvidiaPrimaryScreen" Absolute 0 0 |
| 49 | Screen 1 "DLScreen" RightOf "nvidiaPrimaryScreen" |
| 50 | Option "Xinerama" "true" |
| 51 | EndSection |
| 52 | |
| 53 | Section "ServerLayout" |
| 54 | Identifier "Multihead nvidia cloned" |
| 55 | Screen 0 "nvidiaPrimaryScreen" Absolute 0 0 |
| 56 | Screen 1 "DLScreen" RightOf "nvidiaPrimaryScreen" |
| 57 | Option "Clone" "on" |
| 58 | Option "Xinerama" "false" |
| 59 | EndSection |
| 60 | |
| 61 | Section "ServerLayout" |
| 62 | Identifier "Multihead intel" |
| 63 | Screen 0 "intelPrimaryScreen" Absolute 0 0 |
| 64 | Screen 1 "DLScreen" RightOf "intelPrimaryScreen" |
| 65 | Option "Xinerama" "true" |
| 66 | EndSection |
| 67 | |
| 68 | Section "ServerLayout" |
| 69 | Identifier "Multihead intel cloned" |
| 70 | Screen 0 "intelPrimaryScreen" Absolute 0 0 |
| 71 | Screen 1 "DLScreen" RightOf "intelPrimaryScreen" |
| 72 | Option "Clone" "on" |
| 73 | Option "Xinerama" "false" |
| 74 | EndSection |
| 75 | |
| 76 | ############################################################## |
| 77 | # |
| 78 | # Screen layout selection |
| 79 | # |
| 80 | Section "ServerFlags" |
| 81 | Option "DefaultServerLayout" "Multihead intel" |
| 82 | EndSection |
| 83 | |
| 84 | |
| 85 | These config lines define 4 different screen configurations two for an nvidia |
| 86 | primary display adapter and two for an Intel primary diplay adapter. |
| 87 | |
| 88 | 1. Multihead nvidia |
| 89 | 2. Multihead Intel |
| 90 | |
| 91 | Both screens are configured to appear as a single desktop. Windows can be |
| 92 | moved between the screens. |
| 93 | |
| 94 | 3. Multihead Nvidia cloned |
| 95 | 4. Multihead Intel cloned |
| 96 | |
| 97 | The screens act as seperate screens each with their own toolbars. |
| 98 | |
| 99 | The Display layout to use is selcted by the line: |
| 100 | |
| 101 | Option "DefaultServerLayout" "Multihead intel" |
| 102 | |
| 103 | Here configuration 2 above is selected. To select a different layout replace |
| 104 | the text with the name of the layout, e.g. |
| 105 | |
| 106 | Option "DefaultServerLayout" "Multihead nvidia" |
| 107 | |
| 108 | 5. Load the X display driver |
| 109 | |
| 110 | |
| 111 | No Hotplug Support for DislpayLink device |
| 112 | ========================================= |
| 113 | |
| 114 | X windows does not autosense the presence of a new display adapter. To make |
| 115 | use of the new DisplayLink adapter we have just installed we need to restart |
| 116 | the X server. This can be achieved in two ways. |
| 117 | |
| 118 | 1. Reboot |
| 119 | |
| 120 | or: |
| 121 | |
| 122 | 2. Logout and login again |
| 123 | |
| 124 | |
| 125 | Troubleshooting |
| 126 | =============== |
| 127 | |
| 128 | CentOS is fairly primative in its handling of a broken xorg.conf file. If you |
| 129 | do break the configuration and end up with a black screen you need to boot to |
| 130 | a console from which you can edit the xorg.conf file. This is achieved by the |
| 131 | following: |
| 132 | |
| 133 | 1. Reboot the pc but do not allow it to boot as we need to edit the kernel |
| 134 | parameters. |
| 135 | |
| 136 | 2. Press 'e' to allow you to edit the boot configuration |
| 137 | |
| 138 | 3. Edit the line beginning with kernel by adding a 3 at the rightmost end |
| 139 | This final parameter is not processed by the kernel but is handed to the |
| 140 | first process started. Which in our case is init.exe. This process controls |
| 141 | which programmes are started. Level 3 is console mode. |
| 142 | |
| 143 | 4. Press 'b' to boot with the edited boot commands |
| 144 | |
| 145 | 5. Login as root and edit xorg.conf |
| 146 | |
| 147 | 6. start the x server. There are two otions here: |
| 148 | |
| 149 | 6.1. # /sbin/shutdown -r now <- this will reboot |
| 150 | |
| 151 | 6.2. # /sbin/telinit 5 <- this should instruct init to move to |
| 152 | level 5 which amongst other things starts |
| 153 | X. I have fould with CentOS that this |
| 154 | command is sometimes ignored in which case |
| 155 | option 6.1 is required. you need to be root |
| 156 | to issue this command. |
| 157 | |
| 158 | The edited boot configuration is not permanant and will be forgotten. |
| 159 | |
| 160 | |
| 161 | Caveats |
| 162 | ======= |
| 163 | |
| 164 | The following caveats should be noted: |
| 165 | |
| 166 | * Displays are not cloned at present as X is unable to clone between |
| 167 | different adapters. |
| 168 | |
| 169 | * Driver only runs in a 16 bpp colour depth. |
| 170 | |
| 171 | * No USB hot-plugging support. The monitor can be hot plugged but the USB |
| 172 | device cannot. You should boot the system with the DisplayLink device |
| 173 | already connected to the USB bus. |
| 174 | |
| 175 | * Primary display is assumed to be the capable of being driven by either the |
| 176 | OSS "nv" or "i810" Xorg display drivers - most popular monitors should be |
| 177 | fine with this. |
| 178 | |
| 179 | -- Endurance Technology, 15th Apr 2010 |
| 180 |