LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Problem installing Kyro Power VR drivers (https://www.linuxquestions.org/questions/slackware-14/problem-installing-kyro-power-vr-drivers-92493/)

ricocchet 09-13-2003 06:59 PM

Problem installing Kyro Power VR drivers
 
Hi there guys.
****Damn Newbie Alert*****
I have just installed Slackware 9 after removing it four times in favour of Winblows!
But something kept pulling me back!! ;-) I had tried JAMD,Mandrake and RedHat......But i liked Slackware!.
Now i know its not the easiest for newbies, but im willing to get stuck in and study hard to learn the ins and outs of it.....

Everything is running lovely, everything apart from Gfx Card.....A Kyro II card. I have downloaded the source from powervr.com ....the source tgz, as i understand rpms arent good to use with Slackware if you can help it?

Anyway im using 2.4.20 kernel, and didnt have the kernel source installed....so i downloaded the kernel source (2.4.20) and popped it in /usr/src/ and un tarred and set up a symbolic link to Linux folder.....so i take it thats all installed?....seems to have worked fine.

Right i then follow the instructions in the readme for the powervr drivers and all seems super until i type "make install"......here is the log of what happens....

make install
cc -O2 -DMODULE -DMODVERSIONS -include /usr/src/linux-2.4.20/include/linux/modversions.h -D__KERNEL__ -I/usr/src/linux-2.4.20/include -DLINUX -DGCC_IA32 -DSUPPORT_AGP -Idrm -DHA VE_VMA=0 -c -o hostfunc.o hostfunc.c
hostfunc.c: /usr/src/linux-2.4.20/include/linux/modversions.h: No such file or directory
make: *** [hostfunc.o] Error 1

If im right is it the modversions.h file that is missing? in the folder?

I have a modsetver.h file....but not the one mentioned?
Can anyone please help......as once ive installed the gfx card properly i can then go about reading some tutorials and stuff and get to grips with this great distro.......and forget about windows forever!!:p

Opps My apologies I have just done a search and am reading about the same problem mentioned in another thread ...APOLOGIES! :rolleyes:

EDIT....
That was to do with a Debian Distro......
I have changed a line in the make file.....to the modsetver.h and it seemed to let the install carry on successfully.....would that be ok?
Youll have to excuse my rambling but im very new to this fantastic new OS!

If anyone can tell me what to do next and how to select the kyro card to work in X it would be much appreciated.......
Failing that i suppose i will have to buy a new gfx card with inbuilt support....but would really love to get this working and im also learning all the time fiddling!!

ricocchet 09-13-2003 08:22 PM

Here is the log after i renamed the file....

make install
mkdir -p /lib/modules/`uname -r`/kernel/drivers/char/drm
install -m 0444 powervr.o /lib/modules/`uname -r`/kernel/drivers/char/drm
install -m 0755 lib{PVR2D,PVR2OS,PVRMMAP,SGL2,SGLMID7B}.so /usr/lib
install -m 0444 powervr_drv.o /usr/X11R6/lib/modules/drivers
install -m 0444 powervr_dri.so /usr/X11R6/lib/modules/dri
install -m 0444 XF86KyroSampleConfig /etc/X11
install -m 0644 powervr_kyro.ini /etc
ln -fs /usr/lib/libPVR2D.so /usr/X11R6/lib/modules/drivers
mkdir -p /usr/share/doc/powervr
install -m 0444 README LICENSE.TXT /usr/share/doc/powervr
/sbin/depmod
/sbin/ldconfig
/sbin/modprobe powervr
Warning: loading /lib/modules/2.4.20/kernel/drivers/char/drm/powervr.o will taint the kernel: no license
See http://www.tux.org/lkml/#export-tainted for information about tainted modules
Module powervr loaded, with warnings

Does that look as tho it has worked?

Can someone help me config my X config file please?
It would be much appreciated....I feel like im nearly there with this kyro card!!

Rodrin 09-14-2003 12:13 AM

It certainly does look as though it worked.

One word of advice about the kernel source. The source that you get from kernel.org (or another site that contains the generic source) may not match exactly what was used to build the Slackware kernel unless you follow exactly the method Patrick documents about the steps he took for his kernel (which is usually the generic kernel with selected patches from kernel developers rather than any patches of his own). I am not suggesting you follow his steps. Instead I am suggesting that you do one of two things. I would recommend that at first you use the kernel that comes with Slack and download the official Slackware kernel source package from one of the Slack mirror sites (under Slackware-9.0/Slackware/k/kernel-source-2.4.20-noarch-5.tgz in this case). Alternatively, you can download generic kernel source like you did and then compile a kernel for your machine yourself.

Sorry I did not post any help for configuration before. I was not paying close enough attention to that part of the post. There is no driver, apparently, included with XFree86 for that chipset. So, if you don't already have a generically working XF86Config file, I would recommend running xf86config (as root, of course) and selecting all the correct settings for your setup except the video card/driver setting. For that you could select "vga" and then edit the XF86Config file that you made afterwards, replacing the Driver "vga" line with a Driver "powervr" line.

ricocchet 09-14-2003 12:14 PM

Thanks Rodrin that has made pefect sense and has helped me a great deal.
Thanks for helping out.....I must say for once im really getting engrossed into Linux, ive tried many distros in the past but have always removed them because i didnt give them a chance, it just goes to show if you have patience and determination to learn and study something...you can come on leaps and bounds!
Im really enjoying Slackware, learning soo much after only 3 days of having it installed.

Many many thanks

Im not at home on my linux box at moment, so i cant try configuring xfree and config file yet....im on a Winblows Laptop.....as soon as im ready and know a bit more I will put Slackware on this Laptop.....But hey thats another story!!

Many Thanks.....
I let you know how i get on later:)

ricocchet 09-15-2003 07:23 AM

No joy im afraid Rodrin

I changed the Details in the xf86config file, and tried to restart X but all i got was blank screen....

You could see the Gfx card was somehow trying to work BUT the monitor went into powersave mode and i needed to reboot ;-(

I have been reading through the PowerVR driver readme file and looking at the installation instructions for Red Hat and Mandrake users, just to get a idea of what to do next......and i have seen a few lines about a symbolic link...?? please see below

6) Check that there is a symlink from /etc/X11/X to
/usr/X11R6/bin/XFree86 (there may already be a symlink from
/etc/X11/X, this should be removed) i.e

if [ -e /etc/X11/X ]; then rm -f /etc/X11/X; fi;
ln -s /usr/X11R6/bin/XFree86 /etc/X11/X

Note: On some systems the link to X may be somewhere else, to
/usr/X11R6/bin/X for instance, but otherwise the procedure is
the same. The path variable for the X startup process should be
examined to see where the link to X may be.

X is not in "/etc/X11/X" on my version of slackware!...how do i find out where X is on Slackware? do a search for it? or can u point me to the correct location?
What is the purpose of this Symbolic Link and why is it needed to install graphics drivers?

Sorry for asking all the questions, im just itching to get this gfx installed!!

Many Thanks
Rick

ricocchet 09-15-2003 08:11 AM

I have seen a agp option in the modules.rc file...im just wondering if i need to uncomment this?

## AGP (Accelerated Graphics Port) GART support ###
# This module takes care of programming the GART (part of your motherboard's
# chipset that handles gathering data from memory and passing it to the
# card) and enables faster AGP transfers. The AGP GART module is required
# to use AGP features of your 3D rendering video card. You'll need this to
# use XFree86's direct rendering support, for example.
#/sbin/modprobe agpgart

anyone any ideas?:)

Rodrin 09-15-2003 11:04 PM

Sorry I didn't get back sooner. If I had not been so busy today at work I might have answered then.

In answer to your last question first: Since the instructions did not mention it, it would seem that you should not need this module to make the card work, but you may need it to take advantage of the full power of the card. I would first try to get the card working, and then see if you could improve performance by loading this module.

I noticed before when I didn't have a chance to answer that you had posted your XF86Config file. I saw that you had two "Device" sections in the file and the file was set to use the "vesa" one. You have to put a "Device" section in, or change one of the existing ones, for the Kyro card and then set X to use that section at the end of the file. I also noticed in the README instructions that you need to identify the bus ID of your card in its Device section to get it to work correctly. There are instructions for this in the README. They basically amount to checking the line for the device from an lspci listing. So you can either run lspci (easiest as root because its in root's path) and just look for the line that applies to your video card, or you can grep for the line that applies to your video card as is suggested in the instructions. The first part of the line will be the bus ID in a format like 01:00.0. You need to put whatever yours comes out to in a line that has the number before the colon, then a colon, then the whole part of the second number, then another colon, then the decimal part of the second number, like this, for example:

BusID "PCI:1:0:0"

(It's possible this isn't really necessary, but it certainly won't hurt anything)

You asked about another part of the instructions where it asks you to make a symbolic link to XFree86 in your /etc/X11 directory. It seems doubtful to me that this is actually necessary, but again, it won't hurt anything if you do it. Just run

ln -s /usr/X11R6/bin/XFree86 /etc/X11/X

This has to be done as root.

You should also remember to uncomment or add lines to load the GLcore, dri, and glx modules in your XF86Config file and put in a section for DRI that reads like this:

Section "DRI"
Mode 0666
End Section


I suspect that the major cause of this not coming up before was the driver was not linked to the device section that the XF86Config file was actually using, but I did not see your XF86Config file as it was at the time, so I can not be certain.

ricocchet 09-16-2003 05:29 AM

Many Many Thanks Rodrin for helping me with this, it is MUCH appreciated ;-)

Right i have now set up the symbolic link u and edited the xf86config file.

take a look, any comments on what is incorrect would be most appreciated.

I was worried about posting the config file because of the size but here we are.

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

# **********************************************************************
# 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 "speedo"
# Load "freetype"
# Load "xtt"

# This loads the GLX module
Load "glx"
# This loads the DRI module
Load "dri"

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/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
# FontPath "/usr/X11R6/lib/X11/fonts/TrueType/"
# FontPath "/usr/X11R6/lib/X11/fonts/freefont/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"

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

# Option "AllowNonLocalModInDev"

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"

Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"

# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"

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

# Option "XkbDisable"

Option "XkbRules" "xfree86"
Option "XkbModel" "pc101"
Option "XkbLayout" "gb"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto"
Option "Device" "/dev/mouse"

# Mouse-speed setting for PS/2 mouse.

# Option "Resolution" "256"

# 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


# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the XF86Config man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# 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 "dell15tx"

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

# 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 50-120

EndSection


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

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"

# 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 "powervr"
# 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
# intalled.

BusID "PCI:1:0:0"

# VideoRam 256

# Clocks 25.2 28.3

EndSection

# Device configured by xf86config:

Section "Device"
Identifier "kyro"
Driver "vesa"
#VideoRam 65536
# 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 "kyro"
Monitor "dell16tx"
DefaultDepth 16

Subsection "Display"
Depth 8
Modes "1024x768" "800x600"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "800x600"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768" "800x600"
ViewPort 0 0
EndSubsection
EndSection

# **********************************************************************
# 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
Identifier "Simple 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. In this example, screen 2 is located to the
# right of screen 1.

Screen "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".

InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"

EndSection

# Section "DRI"
Mode 0666
# EndSection

I see you mentioned the GLCore module in your post i dont seem to have any reference to this in my xf86config file?

Another quick question.....why do i have two device sections for gfx and how do i select which one X uses? i take it the second one is the one to use that says configure by xf86config?

Many thanks

Rick

ricocchet 09-16-2003 05:42 AM

Ahh..that said screen not founbd and gave me a error......so what i did next was use the second device settings which look like the ones x needs and looks for?
I also added the PCI Bus details.....

I can see exactly where my mistakes where on the above config file.

This one looks ok to me,...and the gfx card does try to work...BUT as its trying to initialize.....all i get is a blank screen and monitor goes into power save mode......the only way i can get back into anything is to do a hard reboot....

So close but yet so far Rodrin :)
Is it because i dont have the GLCore module mentioned in the config file?
Have a look and see if you can see where im going wrong?

# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# **********************************************************************

# **********************************************************************
# 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 "speedo"
# Load "freetype"
# Load "xtt"

# This loads the GLX module
Load "glx"
# This loads the DRI module
Load "dri"

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/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
# FontPath "/usr/X11R6/lib/X11/fonts/TrueType/"
# FontPath "/usr/X11R6/lib/X11/fonts/freefont/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"

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

# Option "AllowNonLocalModInDev"

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"

Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"

# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"

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

# Option "XkbDisable"

Option "XkbRules" "xfree86"
Option "XkbModel" "pc101"
Option "XkbLayout" "gb"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto"
Option "Device" "/dev/mouse"

# Mouse-speed setting for PS/2 mouse.

# Option "Resolution" "256"

# 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


# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the XF86Config man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# 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 "dell16tx"

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

# 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 50-120

EndSection


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

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"

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

# BusID "PCI:1:0:0"

# VideoRam 256

# Clocks 25.2 28.3

EndSection

# Device configured by xf86config:

Section "Device"
Identifier "kyro"
Driver "powervr"
BusID "PCI:1:0:0"
#VideoRam 65536
# 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 "kyro"
Monitor "dell16tx"
DefaultDepth 16

Subsection "Display"
Depth 8
Modes "1024x768" "800x600"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "800x600"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768" "800x600"
ViewPort 0 0
EndSubsection
EndSection

# **********************************************************************
# 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
Identifier "Simple 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. In this example, screen 2 is located to the
# right of screen 1.

Screen "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".

InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"

EndSection

Section "DRI"
Mode 0666
EndSection

I must say this is a great way to learn Linux....ive learnt a hell of a lot tinkering about with xf86config file....already and ive only been using slackware for about a week!

Ill say it again Thankyou for Being patient and helping Rodrick:)

Rodrin 09-16-2003 08:49 AM

Well you did fix everything that was obviously wrong with the first file. Now there is nothing that jumps out as a problem, so we have to look at more subtle possibilities. You definitely should have in the Modules Section (right where the Load "glx" and Load "dri" statements are) another line that says
Load "GLcore"

Another possible problem would be that the refresh rates for you monitor are incorrect, but I would not expect that considering the other things that you have correct in the file. You could double check on them. However, it looks like you have spaces around the hyphen in the HorizSync range, but it's hard to be sure in this font from the machine I am on right now. If you do, that could be a problem.

It is also possible that you do need to load the agpgart module, since this is a DRI device, even though the instructions did not mention this (it's possible the distribution takes care of that on the distributions these instructions cover).

One thing I forgot to mention when I first posted this. You are sure of the BusID of your device, right? It is most likely correct for an AGP device (that's why I used it as an example), but there are no guarantees if you did not actually look it up yourself. You probably did this. I just wanted to make sure.

That's all I can think of immediately, but look at these and then we'll go from there.

ricocchet 09-16-2003 06:47 PM

Hi Rodrin
Thanks for replying so quickly ;-)

Yes my monitor refresh rates are correct and i did delete the spaces in the range.
The PCI location is correct as i did a "lspci" command and got it that way.
Ive added the GLCore command also and ive even tried moving the DRI part around as well....but no joy at all ;-(

This is the final xf86config that i was using this still didnt work, strange.....i thought it may be the refresh rates but i got the ranges from the manufacturers website, ive also tried standard monitor settings as well!

I also have another kyro card a 32meg one...which uses same drivers so i tried that....and same problem ;-(

What I might do is a reformat because being a newbie i may have messed something up.....and while im doing that i will try a different monitor....but it should work on this one really..ooh well.
I may even try Mandrake just to see if I can get the card working on that.....but I wont be staying with Mandrake as I think its slow and bloated compared to Slackware...
I might just buy another Card......can u suggest a good one thats supported in Slackware

Any more suggestions would be much appreciated!
Heres my last config file

# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# **********************************************************************

# **********************************************************************
# 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
Load "GLcore" # OpenGL support

# 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 "speedo"
# Load "freetype"
# Load "xtt"

# This loads the GLX module
Load "glx"
# This loads the DRI module
Load "dri"

EndSection

Section "DRI"
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/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
# FontPath "/usr/X11R6/lib/X11/fonts/TrueType/"
# FontPath "/usr/X11R6/lib/X11/fonts/freefont/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"

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

# Option "AllowNonLocalModInDev"

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"

Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"

# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"

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

# Option "XkbDisable"

Option "XkbRules" "xfree86"
Option "XkbModel" "pc101"
Option "XkbLayout" "gb"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto"
Option "Device" "/dev/mouse"

# Mouse-speed setting for PS/2 mouse.

# Option "Resolution" "256"

# 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


# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the XF86Config man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# 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 "dell16tx"

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

# 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 50-120

EndSection


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

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"

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

# BusID "PCI:1:0:0"

# VideoRam 256

# Clocks 25.2 28.3

EndSection

# Device configured by xf86config:

Section "Device"
Identifier "KYRO"
Driver "powervr"
BusID "PCI:1:00:0"
BoardName "Unknown"
# Option "HWCursor" "0"
# Option "NoAccel" "1"
VideoRam 65536
# 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 "KYRO"
Monitor "dell16tx"
DefaultDepth 16

Subsection "Display"
Depth 8
Modes "1024x768" "800x600"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "800x600"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768" "800x600"
ViewPort 0 0
EndSubsection
EndSection

# **********************************************************************
# 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
Identifier "Simple 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. In this example, screen 2 is located to the
# right of screen 1.

Screen "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".

InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"

EndSection

ricocchet 09-16-2003 06:52 PM

Here is the Kyro Config file as well that is in the X directory along with the xf86config file....
I will try editing this file and using this one...but to be honest i dont think it will be much different to the one i already have..

# XFree86 4.0 configuration generated by Xconfigurator

Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

## Red Hat font server configuration
##
#Section "Files"
# FontPath "unix/:7100"
#EndSection

## Mandrake font server configuration
##
#Section "Files"
# FontPath "unix/:-1"
#EndSection

# Module loading section

Section "Module"
Load "dbe" # Double-buffering
Load "GLcore" # OpenGL support
Load "dri" # Direct rendering infrastructure
Load "glx" # OpenGL X protocol interface
Load "extmod" # Misc. required extensions
# Load "v4l" # Video4Linux
# Load "pex5" # PHIGS for X 3D environment (obsolete)
# Load "record" # X event recorder
# Load "xie" # X Image Extension (obsolete)
# You only need the following two modules if you do not use xfs.
# Load "freetype" # TrueType font handler
# Load "type1" # Adobe Type 1 font handler
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbLayout" "uk"
EndSection

## IntelliMouse on a PS/2 Port
##
#Section "InputDevice"
# Identifier "Mouse0"
# Driver "mouse"
# Option "Protocol" "IMPS/2"
# Option "Device" "/dev/psaux"
# Option "Buttons" "5"
# Option "ZAxisMapping" "4 5"
#EndSection

## 2 Button mouse on a PS/2 Port
##
#Section "InputDevice"
# Identifier "Mouse0"
# Driver "mouse"
# Option "Protocol" "PS/2"
# Option "Device" "/dev/psaux"
#EndSection

Section "Monitor"
Identifier "My Monitor"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 31.5 - 95.0
VertRefresh 50-120
# HorizSync 31.5 - 57.0
# VertRefresh 50-70
# Option "dpms"
EndSection

Section "Device"
BusID "PCI:1:0:0"
Identifier "KYRO"
Driver "powervr"
BoardName "Unknown"
# Option "HWCursor" "0"
# Option "NoAccel" "1"
EndSection

Section "Screen"
Identifier "Screen0"
Device "KYRO"
Monitor "My Monitor"
# Set your desired default color depth here (16 or 24)
DefaultDepth 16
Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubSection
Subsection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "DRI"
Mode 0666
EndSection

Rodrin 09-16-2003 10:08 PM

Well it won't hurt to check out the sample script with your modifications. Just save the one you have now if you decide to try it. That only leaves one of my questions unanswered. Did you ever try loading the agpgart module in rc.modules as you asked about once before? You could even check this out by loading it manually before you uncomment it in the rc.modules script. Just type in
modprobe agpgart
as root. Then, if it loads successfully, try to run startx and see if that makes any difference. You also should look at the log for X (/var/log/XFree86.log), to see if it can give you a clue to the problem. Another thing that I should have mentioned before is that you may be able to get out of X when you get a blank screen by hitting Ctrl-Alt-Backspace (I realized I left out the Alt at first, sorry). This problem does act like a frequency/resolution problem because instead of X crashing, you are just losing your display. This normally indicates either that X is locking up (which would not mean a frequency/resolution problem), or it is running with no errors but you just can't see it (which would point to that type of problem).

If you do decide to get another card there are many that you won't have a problem getting working. If you are really concerned about 3D performance for games and high performance in general, you will probably want to look at an nVidia or ATI card. If you decide to go with ATI, just check out the support for the specific card you are looking at. I've always used nVidia cards with Linux at home, so I'm more familiar with that setup.

ricocchet 09-17-2003 03:39 PM

Hi Rodrick
Thanks for all your help but i think we are not gonna win this one!! ;-)

I will update soon as ive done a fresh install from scratch....not that i think it will help much !!

I have installed Mandrake on my laptop, but i dont like it at all.....too sloow and bloated.....and too many wizards...even tho im a newbie and dont know much at moment i prefer to learn the hard way even if it does take a long while......rather than have all these wizards do everything for you!! so SLACKWARE is here to STAY!!

My next job is to get acpi working on laptop!
But that fun is to come a bit later!! after ive done a lot more reading etc!

Lok3 12-16-2003 12:52 PM

You got it working? As there's no update I thought I could check, since I'm running Slackware and I got mine Kyro 2-based gfx working. I've got it working in Slackware 8.1, 9.0 and 9.1... =) Drop me a msg. =)


All times are GMT -5. The time now is 06:48 PM.