Well it didn't really, but maybe you can help me make my games and 3D modeling appz catch fire under Mandrake 9.0?

My problem is that while the new Radeon 8500 driver I installed works, I can't get it to run at anything beyond true colour mode 65,000 16 bit. The correct setting should be 16 Million colour 32 bit. When I do a test of the graphical server configuration in mandrake control center I get an error message:

(EE) fglrx(0) Failed to allocate DRM buffer queue
(EE) fglrx(0) Failed to remove DRM signal handler.


(fglrx is the name of my ATI driver)

On a hunch (but not much of one) I go to control center and change my
monitor type from custom (as configured by the ATI xF86-4 configuration
utility) to Samsung Syncmaster 750s then test again: Then I get another error something along the lines of 'VGA driver cannot support 24 bit 16 Million colour mode, try adjusting some parameters'

I think the significant line here is VGA driver as if you look at my most recent Xf86Config-4 file (attached) you will note that in the device section my driver is listed as being 'VGA' and the chip set as generic.

I'm pretty sure it should at least list the name of my driver. Now herein lies the rub, because I have no idea how to complete this section. I do know later in the file my driver is listed as fglrx,(short for fire GL - something - Radeon - something) but in the ATI control panel it is given as a number. But then I'm not sure if it is meant to be either one of these or something entirely different.

Also 3D games, although they seem to run fast can only be run in a small 8 ins' x 8 ins' window and DVDs and VCDs only play back very very slowly.

So if anyone can suggest how this section should be completed, or if someone has some other suggestion why these errors might be happening, please feel free to let me know. I think piece by piece I am getting there and am learning more and more each day, so if I can just get my machine properly configured, I can really get on with learning the rest.

Once more thanks again for your help.

Q

PS

Does anyone know how to set Netscape 7.0 as my default browser so that it will launch system wide whenever I click on a link? I was able to do it with Mozilla, but after deleting my old Mozilla version and installing the latest one, I don't seem able to do this any more. (Also is there a way to block pop-ups in Netscape as there was in Mozilla -since they are basically the same?). I know this is very much an aside to the subject at hand, but if anyone can help it will be appreciated. (I opted for Netscape as no matter how many times I downloaded and tried to install Java VM it would always say the download file was corrupted).

Ps

I will post my XfreeConfig file in the next post. (Pity I can't attach it) Oh welll

# File: XF86Config-4
# File generated by fglrxconfig (C) ATI Research, a substitute for xf86config.

# Note by ATI: the below copyright notice is there for servicing possibly
# pending third party rights on the file format and the instance of this file.
#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#

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

# **********************************************************************
# DRI Section
# **********************************************************************
Section "dri"
# Access to OpenGL ICD is allowed for all users:
Mode 0666
# Access to OpenGL ICD is restricted to a specific user group:
# Group 100 # users
# Mode 0660
EndSection

# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

Load "dbe" # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection

# This loads the Type1 and FreeType font modules
Load "type1"
Load "freetype"

# This loads the GLX module
Load "glx" # libglx.a
Load "dri" # libdri.a

EndSection

# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.

RgbPath "/usr/X11R6/lib/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#

# 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/Speedo/"
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><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" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/mouse"

# 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 "Monitor0"
HorizSync 31.5 - 64.3
VertRefresh 50 - 70
EndSection


Section "Monitor"
Identifier "Monitor1"
HorizSync 31.5 - 64.3
VertRefresh 50 - 70
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
# installed.

# BusID "PCI:0:10:0"

# VideoRam 256

# Clocks 25.2 28.3

EndSection

# === ATI device section ===

Section "Device"
Identifier "ATI Graphics Adapter"
Driver "fglrx"
# === disable PnP Monitor ===
#Option "NoDDC"
# === disable/enable XAA/DRI ===
Option "no_accel" "no"
Option "no_dri" "no"
# === Fire GL DDX driver module specific settings ===
# === Screen Management ===
Option "DesktopSetup" "0x00000100"
Option "Display2" "1"
Option "HSync2" "31.5 - 64.3"
Option "VRefresh2" "50 - 70"
Option "GammaCorrectionI" "0x00000000"
Option "GammaCorrectionII" "0x00000000"
# === OpenGL specific profiles/settings ===
Option "Capabilities" "0x00008800"
# === Video Overlay for the Xv extension ===
Option "VideoOverlay" "on"
# === OpenGL Overlay ===
# Note: When OpenGL Overlay is enabled, Video Overlay
# will be disabled automatically
Option "OpenGLOverlay" "on"
BusID "PCI:1:2:8" # vendor=1002, device=514c
Screen 0
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 "Screen0"
Device "ATI Graphics Adapter"
Monitor "Monitor0"
DefaultDepth 24
#Option "backingstore"

Subsection "Display"
Depth 24
Modes "1280x1024"
ViewPort 0 0 # initial origin if mode is smaller than desktop
# Virtual 1280 1024
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 "Server Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.

Screen "Screen0"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

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

EndSection

### EOF ###

Sorry it took me a while to post my config file, but I had to boot out of Linux and into XP just so I could cut and paste all that text here (there's no way I'm typing it). Its a bit crazy that its often impossible to cut and paste between applications in Linux - it seems like a very basic funtionality - and I don't understand why it is so difficult, or why Linux developers don't impliment it. Same as right clicking on an application to create a desktop shortcut... (I do know how to do this, but it is much more time consuming). These are all things I miss when using Linux. Oh well at least its not MS, maybe they will get there one day.

Q

cut n paste

select text

put cursor where you want pasted.

click middle mouse button, or left and right at same time.

Its a bit crazy that its often impossible to cut and paste between applications in Linux - it seems like a very basic funtionality -

/# Its a bit crazy that its often impossible to cut and paste between applications in Linux - it seems like a very basic funtionality -
bash2: Its: command not found
/#

i used linux for years before i knew that. acid_kewpie
told me.


there is no real "system wide" set of file associations
in a linux desktop. some people wish there were,
some don't. but, as it is the "clicking on" stuff is only valid
in the settings for whatever you are "clicking on" with
such as konqueror, or nautilus. In your case i would
probably just cheat, and make a link to netscape
called mozilla.

...but you can copy and paste from the console window straight into post reply window on this page
Ctrl+C copy
Ctrl+V paste

it works for me

Mmm... a little off topic perhaps, my main worry is really my video. But for those who don't wish there was a system wide cut and paste functionality, surely the answer is simple... They wouldn't have to use it, no one would force them... I don't see it, would they really pefer to continually rewrite long reams of text between one application and another? Are they sadomasochists or something?

Anyhoo the main point is the video, so if anyone has any clue on this, please let me know...

Regards,

Q

there is system wide cut n paste, not
system wide click n run file associations.

to cut ( copy) and paste, you don't have to click a
word called copy or a word called paste.
you can select text, by highlighting it, like you were
about to copy or cut it, then you go to where you
want to paste it to, and click the middle mouse
button. instant copy n paste.

Oh yes so there is... its a tad fiddly though... particularly if you want to copy from somewhere and paste over the top of some existing text. To do this you would noramally highlight the existing text and paste your new test over the top of it, but do this in Linux and you just reproduce the undersired text you just highlighted and want to paste over.

Anyway this really is a side issue. I would really really appreciate help on the video if anyone can offer it...

Regards,

Q

Use lsmod to find out what modules are loaded.
The fglrx module will never load if another drm module is present either built-in the kernel or loaded as a module.
So if in the past you used the "radeon" module and it's set to load through /etc/modules[.conf] or some rc.* script at boot, that could be what's causing it.
If lsmod does list the radeon module, just
modprobe -r radeon
modprobe -v fglrx
...and startx

If it works, find out what file loads "radeon" and replace by fglrx.

...and if you middle-clic your cursor before the first letter of an existing text, you'll paste the new text "before", if that's what you meant by "on top", if not , you'll need The Gimp to create layers

Erm thanks but you do know that this thread is almost a year old?

Since then I have learned enough about Linux to install both Gentoo and Linux from Scratch. So I possibly know a little more than I did then.

Kind regards - and many thanks for answering my question after all this time.

Q

i was looking at that email, with absolutely no recollection of answering
anything to do with a Radeon, and then i saw that it was 2002.
i thought somebody must really be digging through old stuff, then i
remembered that often at the bottom of the screen when it shows similar
posts, that some of them can be really old, and that was probably how
untamed came across it. if you don't notice the year though, it might
look only a few days old.

i was just thinking it might be funny if they aged posts by putting a little
man's head in the upper right who grew a beard that got longer and longer
the older the post was.

Oops! I'm so sorry, I got here through a link I believe, saw 12-17 but never paid attention to ...2002. LOL

Lol... NP...

Q

ahhh man...

I opened this thread to read some cool story about a box bursting in flames because a coke was spilled on it or something...

I got duped by the subject...