SliTaz GNU/Linux official and community documentation wiki.
.png

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
en:guides:xorg-xvesa [2010/06/20 18:25]
seawolf cleaned intro
en:guides:xorg-xvesa [2010/06/20 18:55]
seawolf updated review section
Line 23: Line 23:
 ===== Using Xorg & Vendor-Specific Drivers ===== ===== Using Xorg & Vendor-Specific Drivers =====
  
-When you are using SliTaz as your daily OS, it's recommended to setup your default xorg video driver. You will get a much better ​picture ​than using the xvesa driver or tinyX.+When you are using SliTaz as your main system, it's recommended to use Xorg over XVesa. You will get a much better ​display and performance ​than when using Xvesa tinyX.
  
-**If you have a AGP-Videocard** 
  
-Check with "​lspci"​ - if you find AGP, you should do this first:+=== AGP Cards === 
 + 
 +All AGP video cards need extra kernel modules to function under Xorg. Check if you have an AGP video card with //lspci//; if soinstall the necessary modules in the //​linux-agp//​ package before using Xorg: 
 <​code>​ <​code>​
 # tazpkg get-install linux-agp # tazpkg get-install linux-agp
-</​code> ​Then load the modules:+</​code>​ 
 + 
 +Load the modules ​using the SliTaz hardware detection tool: 
 <​code>#​ tazhw detect-pci</​code> ​ <​code>#​ tazhw detect-pci</​code> ​
  
-Then normally, you just run as root:+You can now use the SliTaz X configuration tool to detect your settings:
  
-<​code>#​ tazx</​code> ​And install your video driver from the list.+<​code>#​ tazx</​code>​
  
-- but sometimes this is not enough.+Select the appropriate driver for your video card from the list.
  
-**DRI / DRM Problem** 
  
-[[http://​www.bitwiz.org.uk/​s/​how-dri-and-drm-work.html|DRI / DRM]] SliTaz ​3.0 has a file in a wrong place - /dev/dri should be a directory and not a file. And to get DRI workingwe have to add tux to the group video:+=== DRI / DRM Problem === 
 + 
 +Sometimes, the auto-detection is not enough. Cards that require ​[[http://​www.bitwiz.org.uk/​s/​how-dri-and-drm-work.html|DRI / DRM]] are supported under SliTaz, but v3 has a couple of bugs! The file ///dev/dri// should be a directory and not a file and, to get DRI working ​correctly, ​we have to add tux to the group video or modify permissions in the Xorg configuration file:
  
 <​code>​ <​code>​
Line 50: Line 56:
 # addgroup tux video # addgroup tux video
 </​code>​ </​code>​
-The module ​drm is not loaded by tazhwyou have to do it manually:+ 
 +The //drm// module ​is not loaded by //tazhw// so you have to do it manually:
 <​code>#​ modprobe drm</​code>​ <​code>#​ modprobe drm</​code>​
  
-**Load ​modules ​persistently**+<note tip>​All ​modules, which are loaded by tazhw and yourself to make your changes permanent, have to be added to the SliTaz Control Box under Initialization in "Load Modules"​. </​note>​
  
-Please note that all modules, which are loaded by tazhw and yourself to make your changes permanent, have to be added to the SliTaz Control Box under Initialization in "Load modules"​. 
  
-**Change your xorg.conf**+=== Intel cards ===
  
-Normally X will start, but perhaps not with the correct resolutionSee the tips at the end of this page or sometimes search the net for the xorg.conf for your card and your monitor - or use another LiveCD and copy the working conf file to SliTaz.+The xorg-xf86-video-vesa 2.0.0 driver has a lot of trouble with Intel chipsFor exmaple, on a 82945GM chipset it does not display 1280x1024 ​and 1024x768, but 1600x1200 is not a problem.
  
-**Restart ​X**+Use "​tazx"​ to select the intel driver, then "tazhw detect-pci",​ solve the dri problem and load drm and restart ​- normally that's it (perhaps you must change your xorg.conf too).
  
-Use the normal shutdown button and select on SliTaz Desktop logout ​the button Logout X session.+Some users may need to add the "​intel_agp"​ module to the xorg.conf file:
  
-Check the /​var/​log/​Xorg.0.log to see if you get any essential (WW)- warnings or (EE) - errorsWhen you installed mesa-demos you can test if rendering is working: +<​code>​ 
-<​code>​glxinfo | grep render</​code>​+Section "​Module"​ 
 +        ​... 
 + Load  "​intel_agp"​ 
 + ... 
 +EndSection 
 +</​code>​
  
 +for the driver to work.
  
-=== Intel cards ===+Depending on the hardware, the //​mode-setting//​ feature must be turned on or off. To turn it off append one of the following to the //kernel// line in the GRUB boot-loader configuration:​
  
-The xorg-xf86-video-vesa 2.0.0 driver has a lot of trouble with intel chips - e.g. on my 82945GM Chipset it does not display 1280x1024 and 1024x768, but 1600x1200 is not a problem.+  *  //​nomodeset//​ 
 +  *  //i810.modeset=0// 
 +  *  //i915.modeset=0//
  
-Use "​tazx"​ to select the intel driver, then "tazhw detect-pci"solve the dri problem and load drm and restart X - normally that's it (perhaps you must change your xorg.conf).+If mode-setting is off by default and should instead be turned onappend one of the following:
  
-Some users may need to add the "​intel_agp"​ module to the xorg.conf file: +  *  //modeset// 
-<​code>​Section "​Module"​ +  ​* ​ //i810.modeset=1// 
-        ..+  ​*  ​//i915.modeset=1//
- Load  "​intel_agp"​ +
-EndSection<​/code> +
-for the driver to work.+
  
 === Trident cards === === Trident cards ===
Line 86: Line 97:
 Use "​tazx"​ to select the trident driver, install mesa-dri-trident Use "​tazx"​ to select the trident driver, install mesa-dri-trident
 <​code>#​ tazpkg get-install mesa-dri-trident</​code>​and restart X <​code>#​ tazpkg get-install mesa-dri-trident</​code>​and restart X
 +
  
 === nVidia cards === === nVidia cards ===
 +
 Slitaz provides automatic configuration for nvidia cards. ​ Slitaz provides automatic configuration for nvidia cards. ​
 For free nvidia drivers, do: For free nvidia drivers, do:
Line 127: Line 140:
 <​code>#​ sed -i '​s/​vesa/​nv/'​ /​etc/​X11/​xorg.conf <​code>#​ sed -i '​s/​vesa/​nv/'​ /​etc/​X11/​xorg.conf
 </​code>​ </​code>​
 +
  
 === ATI cards === === ATI cards ===
Line 153: Line 167:
 <​code>#​ sed -i '​s/​vesa/​radeon/'​ /​etc/​X11/​xorg.conf <​code>#​ sed -i '​s/​vesa/​radeon/'​ /​etc/​X11/​xorg.conf
 </​code>​ </​code>​
 +
 +
 +=== Modifying the Xorg Configuration ===
 +
 +Normally Xorg will start successfully,​ but perhaps not with the correct resolution. See the tips at the end of this page or sometimes search the Internet for the xorg.conf for your card and your monitor - or use another LiveCD and copy the working configuration file to SliTaz.
 +
  
 ===== Configuring X ===== ===== Configuring X =====
  
-This is how we can get a 1024x768 resolution: if your display is stuck at low resolutionsay 800x600just add edit "​Modes"​ in step 2b below.+While X will do it's bets to auto-configure itself for your graphics card set-up, sometimes it needs tweak. Its configuration file///​etc/​X11/​xorg.conf//​is the place to customise the configuration. The best example of this is switching drivers or adding resolutions it doesn'​t detect. 
  
-I edited the following sections in xorg.conf (/​etc/​X11/​xorg.conf):​+=== Adding Resolutions ===
  
-1) Include HorizSync and VertRefresh ​ in section "Monitor"+  - Include ​//HorizSync// and //VertRefresh// (refresh timings) ​in the //Monitor// section:
 <​code>​ <​code>​
 Section "​Monitor"​ Section "​Monitor"​
Line 171: Line 192:
 </​code>​ </​code>​
  
-2a) In Section "Screen"; added Default Depth+  - Include a //​DefaultDepth//​ in the //Screen// section:
  
 <​code>​ <​code>​
Line 178: Line 199:
  Device ​    "​Card0"​  Device ​    "​Card0"​
  Monitor ​   "​Monitor0"​  Monitor ​   "​Monitor0"​
- DefaultDepth 24+** DefaultDepth 24 **
 </​code>​ </​code>​
  
-2b) In Sub-section ​Display: ​added "​Modes"​+  ​Add an extra //Mode// to the line in the //Display// sub-section: 
 <​code>​ <​code>​
    ​SubSection "​Display"​    ​SubSection "​Display"​
Line 190: Line 212:
 </​code>​ </​code>​
  
-3) Also, added default ​Slitaz ​Font path in Section ​Files+  - Also, add the default Font paths in the //Files// section: 
 <​code>​ <​code>​
 Section "​Files"​ Section "​Files"​
Line 204: Line 227:
 </​code>​ </​code>​
  
-You can use xrandr to identify your monitor(s) ​[[http://wiki.debian.org/XStrikeForce/HowToRandR12|Debian RandR 1.2 Wiki]]+  *  If you have DRI/DRM enabled, it may be easier to change its permission so all users can use it, rather than adding each to the //video// group. Append the following section: 
 + 
 +<​code>​ 
 +Section "​DRI"​ 
 +        Mode 0666 
 +EndSection 
 +</​code>​ 
 + 
 + 
 +<note tip>You can use xrandr to identify your monitor(s). This utility is in the //xorg-xrandr// package:
  
 <​code>#​ tazpkg get-install xorg-xrandr</​code>​ <​code>#​ tazpkg get-install xorg-xrandr</​code>​
  
 +See the [[http://​wiki.debian.org/​XStrikeForce/​HowToRandR12|Debian RandR 1.2 Wiki]] for more information.
 +</​note>​
  
-===== XVesa ISO (TinyX) ===== 
  
-You can download the slitaz-3.0-xvesa.iso here: [[http://​mirror.slitaz.org/​iso/​3.0/​flavors/​slitaz-3.0-xvesa.iso|SliTaz-3.0-xvesa.iso]]+=== Restarting Xorg ===
  
-It boots on nearly all computers and laptops, but you can only display a 4:3 resolution. To find out which resolutions are possible with your card, type:+For changes to take effect, you need to restart Xorg. This can be done by logging out of your session and back in again. Choose //Logout// from the Menu and select the //Logout X session// button. If you see the Slim log-in manager, Xorg has restarted successfully! 
 + 
 + 
 +===== Using XVesa and Generic Drivers (TinyX) ===== 
 + 
 +The [[http://​mirror.slitaz.org/​iso/​3.0/​flavors/​slitaz-3.0-xvesa.iso|SliTaz-3.0-xvesa.iso]] uses the XVesa system instead of Xorg, which offers a more generic driver at the cost of performance. ​It boots on nearly all computers and laptops, but can only display a 4:3 resolution. 
 + 
 +To find out which resolutions are possible with your card, type:
  
 <​code>​Xvesa -listmodes</​code> ​ <​code>​Xvesa -listmodes</​code> ​
-Here's a selection of resolutions for my Intel Atom Board:+ 
 +Here's a selection of resolutions for an example ​Intel Atom Board:
  
 <​code>​VBE version 3.0 (Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS) <​code>​VBE version 3.0 (Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS)
Line 227: Line 268:
 0x0115: 800x600x24 TrueColor [8:​8:​8:​8]</​code>​ 0x0115: 800x600x24 TrueColor [8:​8:​8:​8]</​code>​
  
-So widescreen resolutions cannot be displayed with the slitaz-3.0-xvesa.iso.+This output shows widescreen resolutions cannot be displayed with XVesa.
  
-If X does not start with the default SliTaz.iso (falls back to slim), you could use the xvesa.iso ​to install your default ​xorg driver. ​Because when you are asked for your resolution at boot, you can scroll down the window and find the possibility ​to install your xorg.driver before ​is started. ​But don't use "​tazx"​ and "tazhw setup ati or nv" on the xvesa.iso ​to install your xorg driverbecause you will end up with a black screen.+If X does not start with the default SliTaz ​ISO, you could use the XVesa ISO to install your default ​Xorg driver. ​When you are asked for your resolution at boot-time, scroll down the window and find the option ​to install your Xorg driver ​//before// XVesa is started. ​However, ​don't use "​tazx"​ and "tazhw setup ati or nv" on the XVesa ISO to install your Xorg driver because you will end up with a blank and confused ​screen!
  
  
Line 240: Line 281:
 |Problems| add a [[http://​forum.slitaz.org|forum post link]]| |Problems| add a [[http://​forum.slitaz.org|forum post link]]|
 |:::     | OR add a [[http://​labs.slitaz.org/​issues |lab issue tracker link ]]| |:::     | OR add a [[http://​labs.slitaz.org/​issues |lab issue tracker link ]]|
-|How to Improve| ​How about other xorg-cards? | +|How to Improve| ​Extra config. for other cards? | 
-|::: | More details or references ​on Xorg.conf  |+|::: | More details ​on or references ​to xorg.conf  |
  
 \\ \\
 ---- ----
 +
 
en/guides/xorg-xvesa.txt · Last modified: 2010/09/12 15:49 by linea