Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm using gentoo-2.6.11-r6 since two weeks with standard vga adapter on 1280*1024 resolution. Since I'm becoming a more expierenced user (2 weeks.....;-) I want to explore the full potential of this OS. So my aim is to get everything right as it should be; installing the right driver for my video adapter Radeon X300 with a Dell 1704FTP monitor (VGA & DVI). Actually I want to use DVI because that picture is much better than VGA!
I have used the Gentoo ATI Radeon guide http://odin.prohosting.com/wedge01/g...adeon-faq.html but it still gives problems. After boot my KDE desktop starts in a low resolution (640*480), I can login, but than is shows the KDE startup window and it freezes. I can't see the kicker, it doesn't react on any mouse clicks, it just hangs.
If somebody needs my xorg.cong of course I can post it... I don't know what to do any more any suggestions?
File: xorg.conf
# File generated by fglrxconfig (C) ATI Research, a substitute for xf86config.
# Note by ATI: the below copyright notice is there for servicing possibly
# pending third party rights on the file format and the instance of this file.
#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#
# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# **********************************************************************
# **********************************************************************
# DRI Section
# **********************************************************************
Section "dri"
# Access to OpenGL ICD is allowed for all users:
Mode 0666
# Access to OpenGL ICD is restricted to a specific user group:
# Group 100 # users
# Mode 0660
EndSection
# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
# This loads the Type1 and FreeType font modules
Load "type1"
Load "freetype"
# This loads the GLX module
Load "glx" # libglx.a
Load "dri" # libdri.a
EndSection
# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
RgbPath "/usr/X11R6/lib/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#
# The module search path. The default path is shown here.
# ModulePath "/usr/X11R6/lib/modules"
EndSection
# **********************************************************************
# Server flags section.
# **********************************************************************
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
# Option "NoTrapSignals"
# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
# Option "Dont Zoom"
# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
# Option "DisableVidModeExtension"
# Uncomment this to enable the use of a non-local xvidtune client.
# Option "AllowNonLocalXvidtune"
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
# Option "DisableModInDev"
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
Identifier "Keyboard1"
Driver "kbd"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.
# Option "Protocol" "Xqueue"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for XFree86
# Option "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# installed.
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen0"
Device "ATI Graphics Adapter"
Monitor "Monitor0"
DefaultDepth 24
#Option "backingstore"
Subsection "Display"
Depth 24
Modes "800x600" "1024x768" "1152x864" "1280x960" "1280x1024"
ViewPort 0 0 # initial origin if mode is smaller than desktop
# Virtual 1280 1024
EndSubsection
EndSection
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
Section "ServerLayout"
# The Identifier line must be present
Identifier "Server Layout"
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.
Screen "Screen0"
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
Because I don't have X.log in that directory, I send you my xdm.log. This is the log file from the current working system; NOT using the Radeon ATI driver (fglrx).. If you need the log in case I use ATI driver, let me know? There is also a longer file called xorg.0.log, let me know if you need this one aswell?
---
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/tux_bl:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
X Window System Version 6.8.2
Release Date: 9 February 2005
X Protocol Version 11, Revision 0, Release 6.8.2
Build Operating System: Linux 2.6.11-gentoo-r3 i686 [ELF]
Current Operating System: Linux tux_bl 2.6.11-gentoo-r6 #5 Mon Apr 25 23:07:06 CEST 2005 i686
Build Date: 17 April 2005
Before reporting problems, check http://wiki.X.Org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Apr 27 07:17:35 2005
(==) Using config file: "/etc/X11/xorg.conf"
Using vt 7
Could not init font path element /usr/share/fonts/local, removing from list!
Could not init font path element /usr/share/fonts/default, removing from list!
sessions: SessionTypes=Xsession,kde-3.3.2,
Changing kdmrc in /usr/kde/3.3
Changing kdmrc in /usr
/etc/X11/xdm/Xsetup_0: line 25: cd: /usr/share/config/kdm: No such file or directory
xdm error (pid 5852): Trouble getting network interface configurationxdm error (pid 5852): Trouble getting network interface configurationSetClientVersion: 0 8
---
Distribution: K/Ubuntu 12.04/14.04, Scientific Linux 6.3/6.4, Android-x86, Pretty much all distros at one point...
Posts: 1,799
Rep:
You not only have to install the ATI drivers, but you also have to make a manual edit to your x-windows config file...
Look for the same issue with Dell laptops on google (for instance the D810). The X300 identifies as another card by most systems... so there are some manual things that you have to do.
It apparently IS possible to get full 3D acceleration on the X300 chipset,... it's just not real easy to do.
Guys, have the feeling that we are getting closer to the problem.
Attached my xdm.log when problem occurs (so using the ATI driver enabled xorg.conf).
---
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/tux_bl:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
X Window System Version 6.8.2
Release Date: 9 February 2005
X Protocol Version 11, Revision 0, Release 6.8.2
Build Operating System: Linux 2.6.11-gentoo-r3 i686 [ELF]
Current Operating System: Linux tux_bl 2.6.11-gentoo-r6 #5 Mon Apr 25 23:07:06 CEST 2005 i686
Build Date: 17 April 2005
Before reporting problems, check http://wiki.X.Org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Apr 29 22:42:15 2005
(==) Using config file: "/etc/X11/xorg.conf"
Using vt 7
(WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found
Could not init font path element /usr/share/fonts/local, removing from list!
Could not init font path element /usr/share/fonts/default, removing from list!
sessions: SessionTypes=Xsession,kde-3.3.2,
Changing kdmrc in /usr/kde/3.3
Changing kdmrc in /usr
/etc/X11/xdm/Xsetup_0: line 25: cd: /usr/share/config/kdm: No such file or directory
xdm error (pid 5875): Trouble getting network interface configuration
xdm error (pid 5875): Trouble getting network interface configuration
SetClientVersion: 0 8
----
When I look in my PCI setup I find the following identified graphic devices;
BusID "PCI:1:0:0" --> Being identified as "VGA compatible controller; ATI Technologies Inc RV370 5B60 [Radeon X300 PCI]
BusID "PCI:1:0:1" --> Being identified as "VGA compatible controller; ATI Technologies Inc; unknown device 5B70
Because fglrx is refering to device PCI:1:0:1 with a warning, do I need to add a section for this device?
What is the real problem here?
1. the warning?
2. the font referals?
3. error around "no such file or directory"
4. xdm error(pid5875)
Oh, yeah.... I just looked again at my current standard VGA adapter settings. Guess what also quite some errors... Attached my xdm.log of the working KDE with standard VGA device.
---
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/tux_bl:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
X Window System Version 6.8.2
Release Date: 9 February 2005
X Protocol Version 11, Revision 0, Release 6.8.2
Build Operating System: Linux 2.6.11-gentoo-r3 i686 [ELF]
Current Operating System: Linux tux_bl 2.6.11-gentoo-r6 #5 Mon Apr 25 23:07:06 CEST 2005 i686
Build Date: 17 April 2005
Before reporting problems, check http://wiki.X.Org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Apr 29 22:50:13 2005
(==) Using config file: "/etc/X11/xorg.conf"
Using vt 7
Could not init font path element /usr/share/fonts/local, removing from list!
Could not init font path element /usr/share/fonts/default, removing from list!
sessions: SessionTypes=Xsession,kde-3.3.2,
Changing kdmrc in /usr/kde/3.3
Changing kdmrc in /usr
/etc/X11/xdm/Xsetup_0: line 25: cd: /usr/share/config/kdm: No such file or directory
xdm error (pid 5853): Trouble getting network interface configuration
xdm error (pid 5853): Trouble getting network interface configuration
SetClientVersion: 0 8
---
Looks to me that the only conclusion here is that the warning above is pointing at the problem?
Some additional info... looks like glx is not working neither?
---
fglrxinfo
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't find RGB GLX visual!
----
glxinfo
name of display: :0.0
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't find RGB GLX visual
visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav
id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat
----------------------------------------------------------------------
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
0x21 24 tc 1 0 0 c . . 0 0 0 0 0 0 0 0 0 0 0 0 0 None
----
Probably I need to fix this first and than looking at xorg.conf... can anybody give me some advise here?
Well, I'm no expert on graphics card configuration but I noticed that you have "800x600" listed as the first resolution option in the "Display" subsection of your "Screen" section. I believe X will use the first one by default - are you sure it was 600x480? You could try putting the resolution that matches your panel resolution first.
Also, you are definitely barking up the wrong tree with the xdm.log file. Xdm is just the display manager (what gives you the little box to type your username and password in when you log on). What you want for debugging is the xorg.0.log file.
Good luck in debugging this. I have a vested interest since I am thinking of buying a Thinkpad T43 that uses the X300. Thanks for being a guinea pig
After a new kernel (gentoo2.6.11-r6) compilation my AGP is working as well but I am still in shit.... The problem is that after the initial boot the system hangs with a complete black screen...
My xdm.log when problem occurs;
---
(WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found
FATAL: Error inserting fglrx (/lib/modules/2.6.11-gentoo-r6/video/fglrx.ko): Operation not permitted
[drm] failed to load kernel module "fglrx"
(EE) fglrx(0): DRIScreenInit failed!
---
My result of fglrxinfo;
---
Xlib: extension "XFree86-DRI" missing on display ":0.0".
display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)
---
My output of dmesg | grep agp;
---
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected an Intel 915G Chipset.
agpgart: Maximum main memory to use for agp memory: 816M
agpgart: AGP aperture is 256M @ 0x0
----
Help?
How can I switch to ATI OpenGL libraries (i have used opengl-update ati already)?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.