LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Closed Thread
 
LinkBack Search this Thread
Old 09-20-2007, 09:11 PM   #571
hottdogg
Member
 
Registered: Aug 2004
Location: aisenodni
Distribution: slackware 64bit ,debian 64bit
Posts: 200

Rep: Reputation: 30

Quote:
Originally Posted by H_TeXMeX_H View Post
Did you follow all the instructions in this thread ? On the first page ?
Well, I don't recompile kernel. Must I ?
Cause I thought the default kernel is complete already.
I've checked .config file from Pat's 2.6.21.5 kernel source and it seems
what cwwilson721 wrote about the need of recompiling has already been done in the slack 12.0 2.6.21.5 kernel. But plz, CMIIW.
Tnx.
 
Old 09-20-2007, 10:06 PM   #572
cwwilson721
Senior Member
 
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Blog Entries: 1

Original Poster
Rep: Reputation: 65
OK...How about posting xorg.conf?
 
Old 09-21-2007, 09:41 AM   #573
kaz2100
Senior Member
 
Registered: Apr 2005
Location: Penguin land, with apple, no gates
Distribution: Debian testing woody(32) sarge etch lenny squeeze(+64) wheezy jessie
Posts: 1,397

Rep: Reputation: 81
For ATI Radeon user on x86

Hya,

With some i386 hardware, (I have not investigated yet.) ati-driver-installer-8.36.5-x86.x86_64.run looks like to run flawlessly, but when X is killed by ctl-alt-bkspace, kernel Ooops (at least 2.6.20). Normal exit won't Ooop. version 8.40.4 does not have problem.

Happy Penguins!

P.S. I am not sure if following is related.

Quote:
Originally Posted by toasty_ghosty View Post
I don't mean to hijack this thread but I followed the instructions (or so I thought) and somehow messed something up. When my computer boots in root boots fine with ATI Radeon drivers. Everything seems fine. But if I logoff and kill X then I lose my drivers and my screen shuts off. Sometimes my PC won't shutdown all the way, it shuts X down, but doesn't seem to shut it down any farther. And to make it worse, it won't boot in X on my other account(the non root account).
Any advice would be nice.
 
Old 09-23-2007, 05:43 PM   #574
toasty_ghosty
Member
 
Registered: Aug 2007
Posts: 69

Rep: Reputation: 15
Is there a way to almost undo what I have changed and start again?
 
Old 09-24-2007, 12:27 PM   #575
cwwilson721
Senior Member
 
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Blog Entries: 1

Original Poster
Rep: Reputation: 65
Quote:
Originally Posted by toasty_ghosty View Post
Is there a way to almost undo what I have changed and start again?
Yes, fairly easily. [code]rm /etc/x11/xorg.conf[\code]Then start all over.

I would first use the generic xorg.conf that xorgsetup makes, then copy it to another name, so when ATI does its 'voodoo', you would have a fallback, if needed.
 
Old 09-24-2007, 08:48 PM   #576
hottdogg
Member
 
Registered: Aug 2004
Location: aisenodni
Distribution: slackware 64bit ,debian 64bit
Posts: 200

Rep: Reputation: 30
Quote:
Originally Posted by cwwilson721 View Post
OK...How about posting xorg.conf?
i use diff to make shorter. I hope it's ok...tnx.
Code:
#diff -u  xorgconfslack12.bak xorg.conf
--- xorgconfslack12.bak	2007-09-20 10:03:52.000000000 +0700
+++ xorg.conf	2007-09-20 11:19:19.000000000 +0700
@@ -69,8 +69,9 @@
     Load        "freetype"
     #Load        "speedo"
 
-# This loads the GLX module
+# This loads the GLX module and DRI
     Load       "glx"
+    Load       "dri"
 
 EndSection
 
@@ -111,7 +112,7 @@
 # ModulePath can be used to set a search path for the X server modules.
 # The default path is shown here.
 
-#    ModulePath "/usr/lib/xorg/modules"
+    ModulePath "/usr/lib/xorg/modules"
 
 EndSection
 
@@ -398,9 +399,13 @@
 # Any number of graphics device sections may be present
 
 Section "Device"
-    Identifier  "VESA Framebuffer"
-    Driver      "vesa"
+    #Identifier  "VESA Framebuffer"
+    #Driver      "vesa"
     #VideoRam    4096
+    Identifier   "intel 810"
+    Driver    	 "intel"
+    VideoRam     32768
+    	    
     # Insert Clocks lines here if appropriate
 EndSection
 
@@ -414,7 +419,8 @@
 # option.
 Section "Screen"
     Identifier  "Screen 1"
-    Device      "VESA Framebuffer"
+    #Device      "VESA Framebuffer"
+    Device      "intel 810"
     Monitor     "My Monitor"
 
 # If your card can handle it, a higher default color depth (like 24 or 32)
@@ -483,3 +489,6 @@
 
 EndSection
 
+Section "DRI"
+	Mode 0666
+EndSection
 
Old 09-25-2007, 05:24 AM   #577
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266
Do read the first page of this thread thoroughly again:

the driver should be:

Code:
    Driver      "i810"
 
Old 09-26-2007, 05:06 AM   #578
hottdogg
Member
 
Registered: Aug 2004
Location: aisenodni
Distribution: slackware 64bit ,debian 64bit
Posts: 200

Rep: Reputation: 30
I had tried that also, still didn't work.
 
Old 11-03-2007, 11:11 PM   #579
cwwilson721
Senior Member
 
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Blog Entries: 1

Original Poster
Rep: Reputation: 65
Again, post xorg.conf, NOT the diff, 'cuz what may NOT have changed may be the issue
 
Old 11-08-2007, 03:20 PM   #580
alpha_hack
Member
 
Registered: Jul 2007
Location: Sofia, Bulgaria
Distribution: Slackware 13.1x86_64
Posts: 75

Rep: Reputation: 15
Question

Hi,

I've recently updated my slackware to version 12.
I'm having a problem with getting my X11 working....
Here is my hardware info:

Code:
00:00.0 Host bridge: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface (rev 03)
00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 82)
00:1f.0 ISA bridge: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 02)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 02)
01:03.0 CardBus bridge: O2 Micro, Inc. OZ601/6912/711E0 CardBus/SmartCardBus Controller
01:0a.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80)
01:0c.0 Ethernet controller: National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller
These are my loaded modules :
Code:
Module                  Size  Used by
i915                   20992  0 
drm                    72468  1 i915
snd_seq_oss            28160  0 
snd_seq_midi_event      6656  1 snd_seq_oss
snd_seq                42448  4 snd_seq_oss,snd_seq_midi_event
snd_seq_device          7692  2 snd_seq_oss,snd_seq
snd_pcm_oss            38560  0 
snd_mixer_oss          15488  1 snd_pcm_oss
sd_mod                 18448  0 
snd_intel8x0           31132  3 
snd_ac97_codec         90528  1 snd_intel8x0
ac97_bus                2304  1 snd_ac97_codec
snd_pcm                68616  4 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer              19716  3 snd_seq,snd_pcm
snd                    46564  13 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
soundcore               7264  1 snd
snd_page_alloc          9608  2 snd_intel8x0,snd_pcm
intel_agp              23068  1 
agpgart                31664  2 drm,intel_agp
pcmcia                 38572  0
And this is what I've set in my xorg.conf
Code:
Section "Module"
    Load        "dbe"   # Double buffer extension
    SubSection  "extmod"
      Option    "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection
    Load        "type1"
    Load        "freetype"
    #Load        "speedo"
    Load       "synaptics"
    Load       "glx"
    Load       "dri"
EndSection

Section "Device"
    Identifier  "Intel 810"
    Driver      "i810"
    VideoRam   65536
    Option      "XVideo"        "On"    
    Option     "MonitorLayout"  "LFP,CRT"
    Option     "DevicePresence" "On"
    
    
    #Driver      "vesa"
    #VideoRam    65536
    # Insert Clocks lines here if appropriate
EndSection



Section "Screen"
    Identifier  "Screen 1"
    Device      "Intel 810"
    Monitor     "My Monitor"

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.

#   DefaultDepth 8
#   DefaultDepth 16
   DefaultDepth 24
#   DefaultDepth 32

# "1024x768" is also a conservative usable default resolution.  If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)

    Subsection "Display"
        Depth       8
        Modes "1024x768" "800x600" "640x480"
        ViewPort 0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes "1024x768" "800x600" "640x480"
        ViewPort 0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes "1024x768" "800x600" "640x480"
        ViewPort 0 0
    EndSubsection
    Subsection "Display"
        Depth       32
        Modes "1024x768" "800x600" "640x480"
        ViewPort 0 0
    EndSubsection

EndSection



Section "DRI"      
     Group "video"      
     Mode   0666
EndSection


When I start my slackware, agppart detects my correct 845G chipset.
But when I enter my username and pass, and startx after that, the log says:

Code:
(EE) intel(0): detecting sil164
(EE) intel(0): Unable to read from DVOI2C_E Slave 112.
(EE) intel(0): Unable to read from DVOI2C_E Slave 236.
(EE) AIGLX: Screen 0 is not DRI capable
And nothing is been displayed ... Could somebody give me a hand with this ?

Thanks in advance!

Best wishes,
Steve
 
Old 11-11-2007, 08:18 PM   #581
cronicded
LQ Newbie
 
Registered: Sep 2006
Posts: 14

Rep: Reputation: 0
Quote:
Originally Posted by alpha_hack View Post
Hi,

I've recently updated my slackware to version 12.
I'm having a problem with getting my X11 working....
Here is my hardware info:

And this is what I've set in my xorg.conf
...

When I start my slackware, agppart detects my correct 845G chipset.
But when I enter my username and pass, and startx after that, the log says:

Code:
(EE) intel(0): detecting sil164
(EE) intel(0): Unable to read from DVOI2C_E Slave 112.
(EE) intel(0): Unable to read from DVOI2C_E Slave 236.
(EE) AIGLX: Screen 0 is not DRI capable
And nothing is been displayed ... Could somebody give me a hand with this ?

Thanks in advance!

Best wishes,
Steve

It looks to me like you've defined 'Screen 1' but are using Screen0 for X. Change the Screen selection in the Serverlayout section to look similar:
Code:
 
Section "ServerLayout"
  ...
  Screen "Screen1"
  ...
EndSection
Note you did not include your full xorg.conf config so I cannot be sure what your ServerLayout section defines.

Last edited by cronicded; 11-11-2007 at 08:55 PM. Reason: space / excessive quote
 
Old 11-15-2007, 01:21 AM   #582
alpha_hack
Member
 
Registered: Jul 2007
Location: Sofia, Bulgaria
Distribution: Slackware 13.1x86_64
Posts: 75

Rep: Reputation: 15
Quote:
Originally Posted by cronicded View Post
It looks to me like you've defined 'Screen 1' but are using Screen0 for X. Change the Screen selection in the Serverlayout section to look similar:
Code:
 
Section "ServerLayout"
  ...
  Screen "Screen1"
  ...
EndSection
Note you did not include your full xorg.conf config so I cannot be sure what your ServerLayout section defines.
Hi again !
So this is my full xorg.conf

Code:
# File generated by xf86config.
#
# 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.
# **********************************************************************
# NOTE:  This is a NEW IMPROVED version of XF86Config-fbdev that uses the vesa
# driver instead of the fbdev driver.  Thanks to Kenneth Fanyo who pointed
# this out to me. :)
# This XF86Config file is designed for use with the VESA framebuffer.
# This generic interface should work with nearly all video cards
# (although not every card will support every resolution).
# With the new driver, it should no longer be required to have frame buffer
# support in the kernel, or to run it on the console.
#
# Enjoy! :)
# -- volkerdi@slackware.com
#
# **********************************************************************
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************
# **********************************************************************
# Server flags section.
# **********************************************************************
# **********************************************************************
# Input devices
# **********************************************************************
# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
##Section "InputDevice"
# Identifier and driver
##    Identifier	"Mouse1"
##    Driver	"mouse"
# On platforms where PnP mouse detection is supported the following
# protocol setting can be used when using a newer PnP mouse:
#    Option     "Protocol"      "Auto"
# The available mouse protocols types that you can set below are:
#    Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2
#    Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2
#    MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse
#    ThinkingMouse ThinkingMousePS/2 Xqueue
##    Option "Protocol"    "PS/2"
# The mouse device.  The device is normally set to /dev/mouse,
# which is usually a symbolic link to the real device.
##    Option "Device"      "/dev/mouse"
#   Option "Device"      "/dev/psaux"
#   Option "Device"      "/dev/ttyS0"
#   Option "Device"      "/dev/ttyS1"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
#    Option "Protocol"	"Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
#    Option "BaudRate"		"9600"
#    Option "SampleRate"	"150"
# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
#    Option "Emulate3Buttons"
#    Option "Emulate3Timeout"    "50"
# ChordMiddle is an option for some 3-button Logitech mice
#    Option "ChordMiddle"
##EndSection
# Some examples of extended input devices
# Section "InputDevice"
#    Identifier "spaceball"
#    Driver     "magellan"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball2"
#    Driver     "spaceorb"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen0"
#    Driver     "microtouch"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "1412"
#    Option     "MaxX"          "15184"
#    Option     "MinY"          "15372"
#    Option     "MaxY"          "1230"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen1"
#    Driver     "elo2300"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "231"
#    Option     "MaxX"          "3868"
#    Option     "MinY"          "3858"
#    Option     "MaxY"          "272"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonThreshold"       "17"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
# **********************************************************************
# Screen sections
# **********************************************************************
# 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.
# **********************************************************************
# ServerLayout sections.
# **********************************************************************
# 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
# 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.  In this example, screen 2 is located to the
# right of screen 1.
# 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".
	Identifier     "Simple Layout"
	Screen      0  "Screen 1" 0 0
	InputDevice    "Mouse1" "AlwaysCore"
	InputDevice    "Keyboard1" "CoreKeyboard"
EndSection

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.
# 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).
# 
# ModulePath can be used to set a search path for the X server modules.
# The default path is shown here.
#    ModulePath "/usr/lib/xorg/modules"
	RgbPath      "/usr/share/X11/rgb"
	FontPath     "/usr/share/fonts/local/"
	FontPath     "/usr/share/fonts/misc/"
	FontPath     "/usr/share/fonts/OTF/"
	FontPath     "/usr/share/fonts/TTF/"
	FontPath     "/usr/share/fonts/Type1/"
	FontPath     "/usr/share/fonts/CID/"
	FontPath     "/usr/share/fonts/Speedo/"
	FontPath     "/usr/share/fonts/75dpi/:unscaled"
	FontPath     "/usr/share/fonts/100dpi/:unscaled"
	FontPath     "/usr/share/fonts/75dpi/"
	FontPath     "/usr/share/fonts/100dpi/"
	FontPath     "/usr/share/fonts/cyrillic/"
EndSection

Section "Module"

# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the font modules
	Load  "dbe"  	# Double buffer extension
	SubSection "extmod"
		Option	    "omit xfree86-dga"   # don't initialise the DGA extension
	EndSubSection
	Load  "type1"
	Load  "freetype"
    #Load        "speedo"
	Load  "synaptics"
# This loads the GLX module
	Load  "glx"
	Load  "dri"
EndSection

Section "InputDevice"

# 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"
# Set the keyboard auto repeat parameters.  Not all platforms implement
# this.
#    Option     "AutoRepeat"    "500 5"
# Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)).
#    Option     "Xleds" "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
#    Option     "XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a European
# keyboard, you will probably want to use one of:
#
#    Option     "XkbModel"      "pc102"
#    Option     "XkbModel"      "pc105"
#
# If you have a Microsoft Natural keyboard, you can use:
#
#    Option     "XkbModel"      "microsoft"
#
# If you have a US "windows" keyboard you will want:
#
#    Option     "XkbModel"      "pc104"
#
# 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 X.Org
#
#    Option     "XkbRules"      "xorg"
#    Option     "XkbModel"      "pc105"
#    Option     "XkbLayout"     "us"
#    Option     "XkbVariant"    ""
#    Option     "XkbOptions"    ""
	Identifier  "Keyboard1"
	Driver      "kbd"
EndSection

Section "InputDevice"
	Identifier  "Mouse1"
	Driver      "synaptics"
	Option	    "Device" "/dev/psaux"
	Option	    "Protocol" "auto-dev"
	Option	    "LeftEdge" "1700"
	Option	    "RightEdge" "5300"
	Option	    "TopEdge" "1700"
	Option	    "BottomEdge" "4200"
	Option	    "FingerLow" "25"
	Option	    "FingerHigh" "30"
	Option	    "MaxTapTime" "180"
	Option	    "MaxTapMove" "220"
	Option	    "VertScrollDelta" "100"
	Option	    "MinSpeed" "0.09"
	Option	    "MaxSpeed" "0.18"
	Option	    "AccelFactor" "0.0015"
	Option	    "SHMConfig" "on"
EndSection

Section "Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
#    HorizSync	30-64         # multisync
#    HorizSync	31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync	15-25, 30-50  # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
 ### Comment all HorizSync and VertRefresh values to use DDC:
	Identifier   "My Monitor"
 ### Comment all HorizSync and VertRefresh values to use DDC:
	HorizSync    31.5 - 50.0
	VertRefresh  40.0 - 90.0
EndSection

Section "Device"
    Identifier  "Intel 810"
    Driver      "i810"
    #Driver	"intel"
    VideoRam	65536
    Option      "XVideo"        "On"    
    #Option	"MonitorLayout"  "LFP,CRT"
    #Option	"DevicePresence" "On"
    #VideoRam    65536
EndSection

Section "Screen"

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.
#   DefaultDepth 8
#   DefaultDepth 16
#   DefaultDepth 32
# "1024x768" is also a conservative usable default resolution.  If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)
	Identifier "Screen 1"
	Device     "Intel 810"
	Monitor    "My Monitor"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     8
		Modes    "1024x768" "800x600" "640x480"
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     16
		Modes    "1024x768" "800x600" "640x480"
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     24
		Modes    "1024x768" "800x600" "640x480"
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     32
		Modes    "1024x768" "800x600" "640x480"
	EndSubSection
EndSection

Section "DRI"
	Group        "video"
	Mode         0666
EndSection

BTW:
Code:
(EE) intel(0): detecting sil164
This seems to be an error that is showed if you have chip-set i845... I don't know if it's a driver bug or it's coming from X11 ...

Last edited by alpha_hack; 11-15-2007 at 03:12 AM.
 
Old 11-23-2007, 03:00 AM   #583
SIGHUP
LQ Newbie
 
Registered: Oct 2006
Location: San Diego, CA
Posts: 5

Rep: Reputation: 0
Thank you soooo much I followed the tutorial to the word and I got these results on my ibm t42p 2.10GHZ FireGL T2 2GB RAM
@ 1400X1250

root@darkstar:~# fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI MOBILITY FIRE GL T2/T2e
OpenGL version string: 2.0.6747 (8.40.4)

root@cx796776-mobile:~# glxgears

default small window
9623 frames in 5.0 seconds = 1924.441 FPS

switch to full screen
1879 frames in 5.0 seconds = 375.732 FPS

back to small window
9327 frames in 5.0 seconds = 1865.319 FPS

again to full screen
724 frames in 5.0 seconds = 144.751 FPS

small window again
4101 frames in 5.0 seconds = 820.133 FPS

small window
9636 frames in 5.0 seconds = 1927.045 FPS

partially behind console
12543 frames in 5.0 seconds = 2508.560 FPS

fully hidden behind console
15094 frames in 5.0 seconds = 3018.706 FPS


Tada! BIG THANKS!!! I had to experiment with some settings, I had a few crashes, but other than that for now its fine.
 
Old 11-23-2007, 11:13 AM   #584
perry
Member
 
Registered: Sep 2003
Location: USA & Canada
Distribution: Slackware 12.0
Posts: 978

Rep: Reputation: 30
Quote:
Originally Posted by SIGHUP View Post
Thank you soooo much I followed the tutorial to the word and I got these results on my ibm t42p 2.10GHZ FireGL T2 2GB RAM
@ 1400X1250

root@darkstar:~# fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI MOBILITY FIRE GL T2/T2e
OpenGL version string: 2.0.6747 (8.40.4)

root@cx796776-mobile:~# glxgears

default small window
9623 frames in 5.0 seconds = 1924.441 FPS

switch to full screen
1879 frames in 5.0 seconds = 375.732 FPS

back to small window
9327 frames in 5.0 seconds = 1865.319 FPS

again to full screen
724 frames in 5.0 seconds = 144.751 FPS

small window again
4101 frames in 5.0 seconds = 820.133 FPS

small window
9636 frames in 5.0 seconds = 1927.045 FPS

partially behind console
12543 frames in 5.0 seconds = 2508.560 FPS

fully hidden behind console
15094 frames in 5.0 seconds = 3018.706 FPS


Tada! BIG THANKS!!! I had to experiment with some settings, I had a few crashes, but other than that for now its fine.
it's really a rush to the head when you can figure something out for yourself. especially when its something like hardware graphics acceleration. if your doing 3000 fps on 1400x1250 your doing real good

cheers

- perry
 
Old 11-23-2007, 01:18 PM   #585
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266
Quote:
default small window
9623 frames in 5.0 seconds = 1924.441 FPS
This is the true fps. Yet, glxgears is NOT a benchmark ! See how much you get when playing games, that's what's important.
 
  


Closed Thread

Tags
3d, acceleration, ati, enabling, fglrx, glx, intel, nvidia, s3, savage, slackware, via, video, x11, xorg


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
enabling hardware acceleration PennyroyalFrog Linux - Newbie 5 02-26-2010 11:21 AM
xorg-x11 7.0 and exa acceleration jtshaw Linux - Software 0 12-19-2005 07:42 AM
3d acceleration and X11 bspus Linux - Newbie 3 09-06-2005 06:05 AM
Problem Enabling 3D Hardware acceleration. mir_sheely Linux - Hardware 0 06-14-2004 12:37 PM
Audigy Sound card and enabling 3D acceleration for GeoForce3 ti 500 heavyarmor4ever Linux - Newbie 1 01-03-2003 09:27 PM


All times are GMT -5. The time now is 08:47 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration