LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 02-02-2005, 10:42 PM   #1
soylentgreen
Member
 
Registered: Sep 2004
Location: old village
Distribution: android, BSD, CentOS, Ubuntu
Posts: 221

Rep: Reputation: 30
knoppix is smarter than i am


OK.. ive tried for like.. weeks, seriously.. ive read just about everything and im missing something.

i cant get the phreakin rage 128 to do direct rendering.

knoppix did.

so..
i was wondering if i could copy parts ov the config files over to the slackware part to get direct rendering on?
i have my slackware 10 2.6.7 machine with Xorg and all that.. and i think knoppix is Xfree

or should i give up slackware and run a knoppix live cd all the time.. <- just kidding

really, tho.. can anyone help me out? i can post the files how i have them.. i can post the knoppix config files..

thanks
 
Old 02-03-2005, 08:06 AM   #2
dave_starsky
Member
 
Registered: Oct 2003
Location: UK, Manchester
Distribution: Gentoo (2.6.10-r4) & Ubuntu
Posts: 145

Rep: Reputation: 16
You can probably just copy the /etc/X11/xorg.conf over from Knoppix to Slackware, back your Slack one up first just in case
 
Old 02-03-2005, 08:29 AM   #3
Texicle
Member
 
Registered: Oct 2002
Location: Northern Ontario, Canada
Distribution: Slackware 10.0
Posts: 789

Rep: Reputation: 30
I've never used Knoppix, but I'm under the assumption that it uses the floppy only and doesn't store any settings you give it. If it does, then it should be quite easy to fix. If it doesn't, you might want to figure out a way to save the settings to disk.

Also, on knoppix, if you're using XFree, you might want to make sure that it's not /etc/X11/XF86config instead of /etc/X11/xorg.conf.

First, while in Slack, back up the original (just in case):

cp /etc/X11/xorg.conf /etc/X11/xorg.conf.old

Then, if XF86config is the proper file name do this:

cp /<whatever you named your floppy drive>/path/to/etc/X11/XF86config /etc/X11/xorg.conf

That should do you fine. You might want to double check the newly created xorg.conf that it has your monitor refresh rates and what not set up correctly.
 
Old 02-03-2005, 01:07 PM   #4
soylentgreen
Member
 
Registered: Sep 2004
Location: old village
Distribution: android, BSD, CentOS, Ubuntu
Posts: 221

Original Poster
Rep: Reputation: 30
i'll try it out and let you know.

it just makes me feel stupid that a CDROM knows more about my machine than i do.

sweet.. thanks
 
Old 02-03-2005, 01:15 PM   #5
soylentgreen
Member
 
Registered: Sep 2004
Location: old village
Distribution: android, BSD, CentOS, Ubuntu
Posts: 221

Original Poster
Rep: Reputation: 30
one more question.

is XF86config the same thing as xorg.conf?
like.. they are the same file w/ the same info?

so they can have the exact same info wheter its for XFree86 or Xorg.. right?
 
Old 02-03-2005, 09:23 PM   #6
soylentgreen
Member
 
Registered: Sep 2004
Location: old village
Distribution: android, BSD, CentOS, Ubuntu
Posts: 221

Original Poster
Rep: Reputation: 30
that did NOT work.

i feel like Temptus...

i see this pretty thing on my computer where everything works.. and i didn't have to do anything..
even tho i've been using slackware for several years now.. i'm tempted to go toward debian..
i just want things to work.. (and the only thing that doesn't work really is Direct Rendering.)
but knoppix even turns the monitor off (instead ov just blanking the screen) after a period ov inactivity...

what exactly do you have to load in order for Direct Rendering to work?

in knoppix, the glx part lists:
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
OpenGL renderer string: Mesa DRI Rage128 20020221 AGP 1x x86/MMX/SSE
OpenGL version string: 1.2 Mesa 4.0.4

how do i get this working under slackware?
 
Old 02-04-2005, 03:09 AM   #7
Shade
Senior Member
 
Registered: Mar 2003
Location: Burke, VA
Distribution: RHEL, Slackware, Ubuntu, Fedora
Posts: 1,418
Blog Entries: 1

Rep: Reputation: 46
Well, what are the errors you're getting when you use Knoppix' config file? That will help us get it sorted out...

--Shade
 
Old 02-04-2005, 01:02 PM   #8
soylentgreen
Member
 
Registered: Sep 2004
Location: old village
Distribution: android, BSD, CentOS, Ubuntu
Posts: 221

Original Poster
Rep: Reputation: 30
here is what i get when i do a startx:

Release Date: 18 December 2003
X Protocol Version 11, Revision 0, Release 6.7
Build Operating System: Linux 2.4.26 i686 [ELF]
Current Operating System: Linux halo 2.6.7 #1 Wed Jun 16 16:23:03 PDT 2004 i686
Build Date: 05 June 2004
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 Feb 4 13:58:21 2005
(==) Using config file: "/etc/X11/xorg.conf"
Parse warning on line 33 of section Keyboard in file /etc/X11/xorg.conf
Ignoring obsolete keyword "LeftAlt".
Parse error on line 33 of section Keyboard in file /etc/X11/xorg.conf
"Meta" is not a valid keyword in this section.
(EE) Problem parsing the config file
(EE) Error parsing the config file

Fatal server error:
no screens found

Please consult the The X.Org Foundation support
at http://wiki.X.Org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.


XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.



-----------------------------------------------------------------------------------------------------
sorry for the huge post.. but here is my 'knoppix' config, followed by my 'xorg.conf'

knoppix xorg.conf (from XF86, is it going to cause problems cause it thinks its from XFree?)
Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "/usr/X11R6/lib/X11/fonts/misc:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/misc"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo"
FontPath "/usr/X11R6/lib/X11/fonts/PEX"
# Additional fonts: Locale, Gimp, TTF...
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic"
# FontPath "/usr/X11R6/lib/X11/fonts/latin2/75dpi"
# FontPath "/usr/X11R6/lib/X11/fonts/latin2/100dpi"
# True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
FontPath "/usr/X11R6/lib/X11/fonts/Type1"
FontPath "/usr/share/fonts/ttf/western"
FontPath "/usr/share/fonts/ttf/decoratives"
FontPath "/usr/share/fonts/truetype"
FontPath "/usr/share/fonts/truetype/openoffice"
FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
FontPath "/usr/share/fonts/latex-ttf-fonts"
FontPath "/usr/X11R6/lib/X11/fonts/defoma/CID"
FontPath "/usr/X11R6/lib/X11/fonts/defoma/TrueType"
EndSection

Section "ServerFlags"
EndSection

Section "Keyboard"
Protocol "Standard"
AutoRepeat 500 5
LeftAlt Meta
RightAlt Meta
ScrollLock Compose
RightCtl Control
# This is just the default keymap for X.
# May be changed with the KDE international keyboard tool.
XkbModel "pc105"
XkbLayout "us"

# XkbOptions "ctrl:swapcaps"
# XkbKeycodes "xfree86"
# XkbTypes "default"
# XkbCompat "default"
# XkbSymbols "us(pc101)"
# XkbGeometry "pc"
# XkbRules "xfree86"
# XkbModel "pc101"
# XkbLayout "us"
EndSection

Section "Pointer"
Protocol "PS/2"
Device "/dev/mouse"
Emulate3Buttons
Emulate3Timeout 70
EndSection

# Auto-generated by mkxf86config

Section "Monitor"
Identifier "Monitor0"
VendorName "HWP"
ModelName "HWP04ea"
HorizSync 30 - 54 # DDC-probed
VertRefresh 50 - 100 # DDC-probed
# These are the DDC-probed settings reported by your monitor.
# 1024x768, 75.0Hz; hfreq=60.02, vfreq=75.03
ModeLine "1024x768" 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
# 800x600, 85.0Hz; hfreq=53.67, vfreq=85.06
ModeLine "800x600" 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync
# 800x600, 60.0Hz; hfreq=37.88, vfreq=60.32
ModeLine "800x600" 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync
# 640x480, 85.0Hz; hfreq=43.27, vfreq=85.01
ModeLine "640x480" 36.00 640 696 752 832 480 481 484 509 -hsync -vsync
# 640x480, 75.0Hz; hfreq=37.50, vfreq=75.00
ModeLine "640x480" 31.50 640 656 720 840 480 481 484 500 -hsync -vsync
# 640x480, 60.0Hz; hfreq=31.47, vfreq=59.94
ModeLine "640x480" 25.17 640 648 744 784 480 482 484 509 -hsync -vsync
# Extended modelines with GTF timings
# 640x480 @ 100.00 Hz (GTF) hsync: 50.90 kHz; pclk: 43.16 MHz
ModeLine "640x480" 43.16 640 680 744 848 480 481 484 509 -HSync +Vsync
# 768x576 @ 60.00 Hz (GTF) hsync: 35.82 kHz; pclk: 34.96 MHz
ModeLine "768x576" 34.96 768 792 872 976 576 577 580 597 -HSync +Vsync
# 768x576 @ 72.00 Hz (GTF) hsync: 43.27 kHz; pclk: 42.93 MHz
ModeLine "768x576" 42.93 768 800 880 992 576 577 580 601 -HSync +Vsync
# 768x576 @ 75.00 Hz (GTF) hsync: 45.15 kHz; pclk: 45.51 MHz
ModeLine "768x576" 45.51 768 808 888 1008 576 577 580 602 -HSync +Vsync
# 768x576 @ 85.00 Hz (GTF) hsync: 51.42 kHz; pclk: 51.84 MHz
ModeLine "768x576" 51.84 768 808 888 1008 576 577 580 605 -HSync +Vsync
# 768x576 @ 100.00 Hz (GTF) hsync: 61.10 kHz; pclk: 62.57 MHz
ModeLine "768x576" 62.57 768 816 896 1024 576 577 580 611 -HSync +Vsync
# 800x600 @ 100.00 Hz (GTF) hsync: 63.60 kHz; pclk: 68.18 MHz
ModeLine "800x600" 68.18 800 848 936 1072 600 601 604 636 -HSync +Vsync
# 1024x768 @ 100.00 Hz (GTF) hsync: 81.40 kHz; pclk: 113.31 MHz
ModeLine "1024x768" 113.31 1024 1096 1208 1392 768 769 772 814 -HSync +Vsync
# 1152x864 @ 60.00 Hz (GTF) hsync: 53.70 kHz; pclk: 81.62 MHz
ModeLine "1152x864" 81.62 1152 1216 1336 1520 864 865 868 895 -HSync +Vsync
# 1152x864 @ 85.00 Hz (GTF) hsync: 77.10 kHz; pclk: 119.65 MHz
ModeLine "1152x864" 119.65 1152 1224 1352 1552 864 865 868 907 -HSync +Vsync
# 1152x864 @ 100.00 Hz (GTF) hsync: 91.50 kHz; pclk: 143.47 MHz
ModeLine "1152x864" 143.47 1152 1232 1360 1568 864 865 868 915 -HSync +Vsync
# 1280x960 @ 72.00 Hz (GTF) hsync: 72.07 kHz; pclk: 124.54 MHz
ModeLine "1280x960" 124.54 1280 1368 1504 1728 960 961 964 1001 -HSync +Vsync
# 1280x960 @ 75.00 Hz (GTF) hsync: 75.15 kHz; pclk: 129.86 MHz
ModeLine "1280x960" 129.86 1280 1368 1504 1728 960 961 964 1002 -HSync +Vsync
# 1280x960 @ 100.00 Hz (GTF) hsync: 101.70 kHz; pclk: 178.99 MHz
ModeLine "1280x960" 178.99 1280 1376 1520 1760 960 961 964 1017 -HSync +Vsync
# 1280x1024 @ 100.00 Hz (GTF) hsync: 108.50 kHz; pclk: 190.96 MHz
ModeLine "1280x1024" 190.96 1280 1376 1520 1760 1024 1025 1028 1085 -HSync +Vsync
# 1400x1050 @ 60.00 Hz (GTF) hsync: 65.22 kHz; pclk: 122.61 MHz
ModeLine "1400x1050" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -HSync +Vsync
# 1400x1050 @ 72.00 Hz (GTF) hsync: 78.77 kHz; pclk: 149.34 MHz
ModeLine "1400x1050" 149.34 1400 1496 1648 1896 1050 1051 1054 1094 -HSync +Vsync
# 1400x1050 @ 75.00 Hz (GTF) hsync: 82.20 kHz; pclk: 155.85 MHz
ModeLine "1400x1050" 155.85 1400 1496 1648 1896 1050 1051 1054 1096 -HSync +Vsync
# 1400x1050 @ 85.00 Hz (GTF) hsync: 93.76 kHz; pclk: 179.26 MHz
ModeLine "1400x1050" 179.26 1400 1504 1656 1912 1050 1051 1054 1103 -HSync +Vsync
# 1400x1050 @ 100.00 Hz (GTF) hsync: 111.20 kHz; pclk: 214.39 MHz
ModeLine "1400x1050" 214.39 1400 1512 1664 1928 1050 1051 1054 1112 -HSync +Vsync
# 1600x1200 @ 100.00 Hz (GTF) hsync: 127.10 kHz; pclk: 280.64 MHz
ModeLine "1600x1200" 280.64 1600 1728 1904 2208 1200 1201 1204 1271 -HSync +Vsync
EndSection

Section "Device"
Identifier "My Video Card"
VendorName "Unknown"
BoardName "Unknown"
# TextClockFreq 22.175
EndSection

Section "Device"
Identifier "fbdev"
VendorName "Unknown"
BoardName "Unknown"
EndSection


# Standard Server
Section "Screen"
Driver "svga"
Device "My Video Card"
Monitor "Monitor0"
Subsection "Display"
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection

# Accel. Server(s)
Section "Screen"
Driver "accel"
Device "My Video Card"
Monitor "Monitor0"
Subsection "Display"
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection

# Fallback
Section "Screen"
Driver "vga16"
Device "My Video Card"
Monitor "Monitor0"
Subsection "Display"
Modes "1024x768" "800x600" "640x480"
EndSubsection
EndSection

Section "Screen"
Driver "fbdev"
Device "fbdev"
Monitor "Monitor0"
SubSection "Display"
Depth 32
Modes "default"
EndSubSection
SubSection "Display"
Depth 24
Modes "default"
EndSubSection
SubSection "Display"
Depth 16
Modes "default"
EndSubSection
SubSection "Display"
Depth 15
Modes "default"
EndSubSection
SubSection "Display"
Depth 8
Modes "default"
EndSubSection
EndSection


_________________________________________________________________
the 'other' xorg.conf (which brings up X, but no Direct Rendering)
Section "Module"

### Hacked
Load "ddc" # no idea what it does
Load "GLcore"


# This loads the DBE extension module.

# Load "dbe" # Double buffer extension

#### More Hacked
Load "dri" # you really think i know?
Load "drm"
Load "extmod"
# 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
Load "glx"
Load "GLcore"
Load "bitmap"
# This loads the font modules
#
#
Load "speedo"
Load "type1"
Load "freetype"
Load "record"
Load "ati"
# This loads the GLX module

# Load "dri"

EndSection

Section "DRI"
Group "video"
Mode 0666
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).
#

FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/"

# ModulePath can be used to set a search path for the X server modules.
# 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><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.

# Option "DontVTSwitch"

# 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 "DontZoom"

# 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).

# Option "AllowNonLocalModInDev"

# Set the basic blanking screen saver timeout.

# Option "blank time" "10" # 10 minutes

# Set the DPMS timeouts. These are set here because they are global
# rather than screen-specific. These settings alone don't enable DPMS.
# It is enabled per-screen (or per-monitor), and even then only when
# the driver supports it.

# Option "standby time" "20"
# Option "suspend time" "30"
# Option "off time" "60"

# On some platform the server needs to estimate the sizes of PCI
# memory and pio ranges. This is done by assuming that PCI ranges
# don't overlap. Some broken BIOSes tend to set ranges of inactive
# devices wrong. Here one can adjust how aggressive the assumptions
# should be. Default is 0.

# Option "EstimateSizesAggresively" "0"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

Identifier "Keyboard1"
Driver "Keyboard"
# 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" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""

EndSection


# **********************************************************************
# 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" "IMPS/2"

# 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"
Option "ZAxisMapping" "4 5"
# 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

Section "Monitor"

Identifier "My 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 31.5 - 50.0

# 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.

VertRefresh 40-90

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

Section "Device"
Identifier "RAGE 128"
Driver "r128"
#VideoRam 4096
# Insert Clocks lines here if appropriate
EndSection

# **********************************************************************
# 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.
Section "Screen"
Identifier "Screen 1"
Device "RAGE 128"
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"
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 32
Modes "1024x768" "800x600" "640x480"
EndSubsection

EndSection

Last edited by soylentgreen; 02-04-2005 at 01:16 PM.
 
Old 02-04-2005, 01:17 PM   #9
soylentgreen
Member
 
Registered: Sep 2004
Location: old village
Distribution: android, BSD, CentOS, Ubuntu
Posts: 221

Original Poster
Rep: Reputation: 30
i also have the dmesg output from knoppix, as well as the glxinfo from knoppix.. if those would help.

please and thank you!
 
Old 02-04-2005, 01:34 PM   #10
eelsnaudras
Newbie
 
Registered: Apr 2004
Location: Manchester, England
Distribution: slack current, debian testing
Posts: 9

Rep: Reputation: 0
Try renaming the xfree file xorg.conf...

I've had success with just what you're trying to do by simply copying the contents of the XF86 file generated by knoppix into the xorg file in slack.

Last edited by eelsnaudras; 02-04-2005 at 01:39 PM.
 
Old 02-04-2005, 01:44 PM   #11
soylentgreen
Member
 
Registered: Sep 2004
Location: old village
Distribution: android, BSD, CentOS, Ubuntu
Posts: 221

Original Poster
Rep: Reputation: 30
alas, tho i have done that..
when i did that, startx did not load, and got the error at the top ov my more recent post. (post #8)

is it possible to determine what i need to put in my xorg.conf based on the dmesg / glxinfo output?
 
Old 02-04-2005, 07:40 PM   #12
gd2shoe
Member
 
Registered: Jun 2004
Location: Northern CA
Distribution: Debian
Posts: 835

Rep: Reputation: 49
Quote:
Originally posted by soylentgreen

....

(==) Log file: "/var/log/Xorg.0.log", Time: Fri Feb 4 13:58:21 2005
(==) Using config file: "/etc/X11/xorg.conf"
Parse warning on line 33 of section Keyboard in file /etc/X11/xorg.conf
Ignoring obsolete keyword "LeftAlt".
Parse error on line 33 of section Keyboard in file /etc/X11/xorg.conf
"Meta" is not a valid keyword in this section.
(EE) Problem parsing the config file
(EE) Error parsing the config file

....
Note: It's having trouble with the "section Keyboard". This error has nothing to do with your display. You should be able to use your orriginal file to fix this problem.

Specifically, it doesn't like "LeftAlt" and "Meta".
 
Old 02-04-2005, 07:48 PM   #13
gd2shoe
Member
 
Registered: Jun 2004
Location: Northern CA
Distribution: Debian
Posts: 835

Rep: Reputation: 49
Oh, and just in case you aren't familiar with the word "parse", it means for a computer to break a file up into bits that it can process. As it's breaking up the file for information it is hitting spots that it just doesn't like. This isn't to say "misconfigured", it just really doesn't like the combination of letters/words.

There are some differences between XFree86 and Xorg. The config file is basically the same, but I have heard of a few problem differences. You may be able to get the xf86 file to work in Xorg, but you might need to just use parts of it.
 
Old 02-04-2005, 07:53 PM   #14
keefaz
Senior Member
 
Registered: Mar 2004
Distribution: Slackware
Posts: 4,282

Rep: Reputation: 66
Try Mod1 instead of Meta and Alt_L instead of LeftAlt, see if it works...
 
Old 08-05-2005, 01:35 PM   #15
NoeticRapture
LQ Newbie
 
Registered: Mar 2005
Location: NY
Distribution: Slackware
Posts: 25

Rep: Reputation: 15
Incase you somehow still haven't gotten it resolved...

Looking things up for myself. came across your old post and it doesn't look as though you ever found a solution -- not that I'm a guru by any means, mind you, but I had to spend a couple months putzing around to get my HW acceleration working myself... I'm not familiar with Knoppix, but being a LiveCD (?) it probably boots it's own kernel, so I wouldn't expect replacing your config file would do the trick (somehow direct rendering with a number of cards seems to have gotten 'broken' in the 2.6 kernels). BTW, I believe the keyboard driver changed in XOrg to "kbd" as opposed to whatever the old value was, if just changing the config file automagically fixes it, change the XFree config file's driver to kbd and it should work in XOrg.
Try installing the atifglx (think that's it) package from linuxpackages, or if you're so inclined, download it from the ATI website and compile it yourself. I believe the Rage128 cards are supported in the official driver, but ATI's Linux support is the worst you'll probably ever have to deal with.
I managed to get my RadeonIGP320 fully working with DRI's driver - ATI's was useless for my notebook; if my memory's inaccurate and yours isn't supported by the manufacturer either, try DRI.
Hope you fixed it 6+ months ago, but if not, maybe that'll be of use to you. Good luck
 
  


Reply


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
i got knoppix on cd and it rocks when booted! wut can i do to install knoppix on HD? kublador Linux - Distributions 4 12-12-2005 04:08 PM
KNOPPIX 3.8.1 Problem with knoppix-installer Wireless-G-DSL Debian 4 04-13-2005 05:03 PM
Could not open /home/knoppix Reason: /home/knoppix is not a file. slacard Debian 3 09-16-2004 08:36 AM
How does one remove the custom KNOPPIX graphics from a KNOPPIX HD Install? apache363 Linux - Distributions 2 03-29-2004 05:08 AM
Bill gates is smarter than Linus Torvalds gatso General 6 10-12-2003 09:06 AM


All times are GMT -5. The time now is 05:10 PM.

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