You are here: welcome » dcore » xorg-video_driver_packages

Differences

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

--- dcore:xorg-video_driver_packages [2016/06/09 17:41] – [dCore Graphic Servers and Drivers] nitram
+++ dcore:xorg-video_driver_packages [2016/12/26 11:05] (current) – [Hardware-specific settings] sm8ps
@@ Line 5: / Line 5: @@
 ==== dCore Xvesa Installation ====
-[[http://www.xfree86.org/4.6.0/Xvesa.1.html|Xvesa]] is still available and is included in some dCorePlus-*.iso downloads but will slowly be phased out. To install //Xvesa// run ''sce-import -b Xvesa'' (capital x). Xvesa should not be confused with X.org's 'xorg-vesa' driver. Xvesa, also known as tiny X server, is a lighter, older alternative to X.org. As the Xvesa link indicates, an Xvesa server should only be used in trusted environments.
+The [[http://www.xfree86.org/4.6.0/Xvesa.1.html|Xvesa]] graphic server, also known as the tiny X server, and it's associated VESA driver is included in some dCorePlus-*.iso downloads but will slowly be phased out. To install //Xvesa// run ''sce-import -b Xvesa'' (capital x). Xvesa should not be confused with X.org's 'xorg-vesa' driver. The Xvesa server is a lighter, older alternative to X.org. As the Xvesa link indicates, it should only be used in trusted environments.
 Similar to running Xvesa in Tiny Core, specific boot codes may be used to set desired screen resolution. For reference, review [[http://wiki.tinycorelinux.net/wiki:boot_codes_explained|boot codes explained]] and [[http://wiki.tinycorelinux.net/wiki:boot_options|Tiny Core boot codes, especially vga=*]]. Reboot and test system graphics.
-It should be noted that 1024x768 appears to be the maximum resolution available. Some Window Managers or Desktop Environments may no longer work with Xvesa. For example, FLWM worked fine but LXDE did not work at all. Ensure Xvesa, Xprogs and the preferred Window Manager is listed in sceboot.lst, but not any of the xorg-* extensions.
+Noted 1024x768 appears to be the maximum resolution available and some Window Managers or Desktop Environments no longer work with Xvesa. For example, FLWM worked fine but LXDE did not work at all. Ensure Xvesa, Xprogs and the preferred Window Manager is listed in sceboot.lst, but not any of the xorg-* extensions.
 Upon first run if graphic resolution is poor, press Ctrl-Alt-Delete to exit to TTY, run ''xsetup.sh'', choose desired screen resolution and  mouse, enter ''startx'' to restart Xvesa session. If the scroll mouse does not work, try appending ',5' (comma five) in the first ~/.xsession line, as below. If Xvesa resolution is still not adequate or it does not work with the desired Window Manager, remove Xvesa and install either xorg-all or a more specific xorg-* extension.
@@ Line 17: / Line 17: @@
 ==== dCore Xorg-all Driver Installation ====
-The //xorg-all// extension is convenient for initial system setup, especially if uncertain regarding graphic hardware. The driver must be installed to load onboot and a system reboot after installation is required for proper testing.
+All xorg-* drivers are based on [[https://www.x.org/wiki/|X.org]]. The xorg-all extension is convenient for initial system setup if uncertain regarding graphic hardware. The driver must be installed to load onboot and a system reboot after installation is required for proper testing.
   *Install the //xorg-all// graphic driver by running the ''sce-import -b xorg-all'' command.
@@ Line 23: / Line 23: @@
 ==== dCore Xorg-<specific> Driver Installation ====
-Basic steps to identify hardware and install the correct video driver. The driver must be installed to load onboot and a system reboot after installation is required for proper testing.
+As most systems require only a single graphic driver (eg. Intel, NVidia), installation of the specific driver vs xorg-all is preferred if familiar with the graphic hardware. The driver must be installed to load onboot and a system reboot after installation is required for proper testing. Basic steps to identify hardware and install the correct video driver:
   *Import and load either [[https://packages.debian.org/jessie/pciutils|'pciutils']], [[https://packages.debian.org/jessie/hwinfo|'hwinfo']] or [[https://packages.debian.org/jessie/lshw|'lshw']].
@@ Line 37: / Line 37: @@
 ==== dCore Graphic Notes ====
-Additional notes that may help set up a graphic system:
+Additional notes that may help set up a graphic system. Setting up graphics in dCore is similar to getting graphics running from most any other minimal Linux installation. As such a large variety of hardware is available and packages vary between dCore flavours (ie. older/newer Debian vs Ubuntu packages), internet searching for missing packages or configuration may sometimes be required. Post on the forum if unable to get dCore graphics running properly.
   *The extension being installed may contain video drivers plus additional data. For example, //xserver-xorg-video-intel// also contains the packages //xserver-xorg-video-////vesa// and //xserver-xorg-////input-{////all,////wacom,mouse,vmmouse,synaptics}//.
-  *Extensions to identify hardware, such as //pciutils//, can be removed when no longer required.
   *The //Xprogs// extension is now a [[http://forum.tinycorelinux.net/index.php/topic,18384.msg112091.html#msg112091|dependency of any xorg-* extension]].
-  *Although most hardware should not require old school configuration, an xorg.conf file may be needed to achieve the desired resolution, desired colour depth or to enable graphic driver options. See the [[http://wiki.tinycorelinux.net/dcore:xorg-video_driver_packages?&#dcore_xorgconf_example|dCore xorg.conf example]] below.
+  *Extensions to identify hardware, such as //pciutils//, can be removed when no longer required.
+  *Review this [[http://wiki.tinycorelinux.net/dcore:faq#help_i_followed_the_documentation_but_can_t_boot_into_graphics|dCore graphics FAQ]] entry if unable to get graphics running.
+  *Review /var/log/Xorg.0.log for hints after a failed ''startx'' attempt.
+  *If system boots into graphics but not desired resolution, run ''xrandr'' to determine available default resolutions. If the desired resolution is available, test enter the appropriate resolution (eg. ''xrandr -s 1280x800''). If adequate then add this is an ~/.X.d/ entry. If a monitor resolution other than an available default ''xrandr'' output is desired, additional xrandr commands will be required or consider using an xorg.conf file (see below). Helpful ''xrandr'' links: [[ftp://www.x.org/pub/X11R7.5/doc/man/man1/xrandr.1.html|xrandr man page]], [[https://pkg-xorg.alioth.debian.org/howto/use-xrandr.html|xrandr guide]].
+  *Although not typically required an xorg.conf file may be needed to get graphics, achieve desired resolution and colour depth or enable graphic driver options. For example, an old Intel i810 graphic system required the [[http://wiki.tinycorelinux.net/dcore:xorg-video_driver_packages?&#dcore_xorgconf_example|dCore xorg.conf example]] file below, including the "DRI" "FALSE" entry, to obtain any graphics in dCore-xenial.
+  *To exit graphics when tweaking monitor resolution or xorg.conf configuration, run ''exittc'' or select //Exit// from a supported Window Manager, then select //Exit to Prompt//. This will exit Xorg and the Window Manager and return to a TTY. Enter ''startx'' to restart graphics and Window Manager.
+  *Various software to test and benchmark graphic performance can be imported from the respective Debian/Ubuntu repository, such as GtkPerf, mesa-utils (provides glxgears) and nvidia-detect (requires loading Bash). This may help to identify problems and deficiencies. For example, a failed attempt to run ''glxgears'' on the Intel i810 system mentioned above required loading //libgl1-mesa-swx11// in addition to //xorg-intel// and //graphics-3.16.6-tinycore//.
 ==== dCore xorg.conf Example ====
@@ Line 47: / Line 53: @@
   *Create an /etc/X11/xorg.conf file
-  *Add this full pathway to /opt/.filetool.lst for persistence: etc/X11/xorg.conf
+  *Add this entry to /opt/.filetool.lst: etc/X11/xorg.conf
+  *Run ''backup'' command to backup system.
+  *Run ''sudo reboot'' command to reboot.
-Example xorg.conf file for an old Intel i810 system:
+==== Hardware-specific settings ====
+=== Intel i810 ===
+xorg.conf file for an old Intel i810 graphics system in dCore-xenial:
 <code>
 Section "Monitor"
-	Identifier   "Monitor0"
+	Identifier     "Monitor0"
-	HorizSync       28.0 - 96.0
+	HorizSync      28.0 - 96.0
-  	VertRefresh     50.0 - 75.0
+  	VertRefresh    50.0 - 75.0
     	Option         "DPMS"
 EndSection
@@ Line 64: / Line 75: @@
         ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
         ### [arg]: arg optional
-        #Option     "NoAccel"            	# [<bool>]
+        #Option     "NoAccel"   "true"         	# [<bool>]
         #Option     "SWcursor"           	# [<bool>]
         #Option     "ColorKey"           	# <i>
-        #Option     "CacheLines"         	# <i>
+        #Option     "CacheLines"          	# <i>
         #Option     "Dac6Bit"            	# [<bool>]
-        #Option     "DRI"                	# [<bool>]
+        Option      "DRI"  	"false"         # [<bool>]
         #Option     "NoDDC"              	# [<bool>]
         #Option     "ShowCache"          	# [<bool>]
@@ Line 76: / Line 87: @@
 	Identifier  "Card0"
 	Driver      "intel"
+	BusID       "PCI:0:1:0"
 EndSection
 Section "Screen"
-	Identifier "Screen0"
+	Identifier   "Screen0"
-	Device     "Card0"
+	Device       "Card0"
-	Monitor    "Monitor0"
+	Monitor      "Monitor0"
-	DefaultDepth    16
+	DefaultDepth 16
 	SubSection "Display"
 		Depth 16
-		Modes "1152x864"
+		#Modes "1024x768"
+		Modes  "1280x800"
 	EndSubSection
 EndSection
 </code>
+=== Intel 855GM ===
+Various issues with this card could be overcome by adding "acpi_backlight=vendor" to the boot stanza. See the respective [[http://forum.tinycorelinux.net/index.php/topic,20061.msg128654.html#msg128654|forum thread]] for additional information and pointers.
 **[[http://wiki.tinycorelinux.net/dcore:welcome|> Return to the dCore Wiki Welcome page]]**

Differences

Search

Navigation

Print/export

Tools

QR Code