SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
- creating symlink
- recreating module dependency list
- trying a sample load of the kernel module
FATAL: Error inserting fglrx (/lib/modules/2.6.7/kernel/drivers/char/drm/fglrx.ko): Operation not permitted
failed.
Why? What does it mean?
EDIT:
Ok, I might have figured my own problem out. I built me a new kernel w/ module unloading, agpgart support built in, my via apg whats-the-word as a module, drm built in and the kernels radeon driver as a module.
Now it at least seems to have installed ok.
Yet to figure out how to test it tho.
Last edited by purplemooseman; 08-05-2004 at 03:35 AM.
Hi Guys, in fact this is my first post in this forum but I think I will be sending much more soon. So quickly to the subject.
I installed slackware distro 10.0 with 2.4.26 kernel.
I did an X -configure and it recognized my ATI mobility radeon 9600 pro turbo (on a dell inspiron 8600 laptop) immediatelly. In the x.org it created it put the "ati" driver. I also checked another x.org file from a gentoo installation. Check it out:
# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"
Load "dbe" # Double buffer extension
# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************
# 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
Subsection "Display"
Depth 24
Virtual 1920 1200
ViewPort 0 0 # initial origin if mode is smaller than desktop
EndSubsection
EndSection
When you start X you should use the command option -- -dpi 100 to avoid huge font in some menus. If you like nice fonts a good place to start on tweaking information would be the font de-uglification howto.
--------------------
PLEASE NOTE THAT IN THE DEVICE SECTION MY DRIVER IS "ati" AND THIS FILE IS FOR THE LAPTOP LCD SCREEN.
All the rest is the same
The server was started perfectly.
I am even wondering why do you need that freaking ati module ????!!!!!
Have you tried with the included "ati" one ???
I don't think it requires a patch, I've got it working on mine. Just a little wierdness runing make.sh
Quote:
ATI module generator V 2.0
==========================
initializing...
make.sh: line 630: /proc/version: Permission denied
make.sh: line 631: /proc/version: Permission denied
cleaning...
patching 'highmem.h'...
skipping patch for 'drmP.h', not needed
skipping patch for 'drm_os_linux.h', not needed
assuming new VMA API since we do have kernel 2.6.x...
doing Makefile based build for kernel 2.6.x and higher
make -C /lib/modules/2.6.7/build SUBDIRS=/lib/modules/fglrx/build_mod/2.6.x modules
make[1]: Entering directory `/usr/src/linux-2.6.7'
Building modules, stage 2.
MODPOST
make[1]: Leaving directory `/usr/src/linux-2.6.7'
build succeeded with return value 0
duplicating results into driver repository...
done.
==============================
You must change your working directory to /lib/modules/fglrx
and then call ./make_install.sh in order to install the built module.
==============================
According to the ATi release notes you shouldn't need the patch as the issues with the 2.6.6 kernel and above has been resolved. I got the same error as well so hopefully it will still work.
Well mine did not like it at all during the make_install.sh run it keeps giving me a fatal error due to a bad address while trying to install into the drivers section.
rpm -U --replacepkgs --nodeps '//fglrx.rpm';echo RESULT=$?
*** Trying to install a precompiled kernel module.
- creating symlink
- recreating module dependency list
- trying a sample load of the kernel module
FATAL: Error inserting fglrx (/lib/modules/2.6.7/kernel/drivers/char/drm/fglrx.ko): Bad address
failed.
*** Found kernel module build environment, generating kernel module now.
ATI module generator V 2.0
==========================
initializing...
make.sh: line 630: /proc/version: Permission denied
make.sh: line 631: /proc/version: Permission denied
cleaning...
patching 'highmem.h'...
skipping patch for 'drmP.h', not needed
skipping patch for 'drm_os_linux.h', not needed
assuming new VMA API since we do have kernel 2.6.x...
doing Makefile based build for kernel 2.6.x and higher
make -C /lib/modules/2.6.7/build SUBDIRS=/lib/modules/fglrx/build_mod/2.6.x modules
make[1]: Entering directory `/usr/src/linux-2.6.7'
Building modules, stage 2.
MODPOST
make[1]: Leaving directory `/usr/src/linux-2.6.7'
build succeeded with return value 0
duplicating results into driver repository...
done.
==============================
- creating symlink
- recreating module dependency list
- trying a sample load of the kernel module
FATAL: Error inserting fglrx (/lib/modules/2.6.7/kernel/drivers/char/drm/fglrx.ko): Bad address
failed.
*** Warning ***
The QT based control panel application did not load in any version.
===
ATI display drivers successfully installed
please run 'fglrxconfig' now
===
RESULT=0
For all of you that are using the NForce2 Chipset, ATI Radeon 9800 Pro, and Slackware 10 with Kernel 2.4.26, this is what you have to do to get your drivers working correctly.
2. run the command: "rpm2tgz fglrx-4.3.0-3.11.1.i386.rpm" to create the corresponding slackpack file
3. run pkgtool to install the "fglrx-4.3.0-3.11.1.i386.tgz" package in the directory in which it was created
4. update your database: "updatedb"
5. switch to the directory that the package was installed in. cd /lib/modules/fglrx/build_mod
6. type "sh make.sh" to build the module
7. type "cd .."
8. type "sh make_install.sh" to install the module. *Note, you may get a warning that it may taint the kernel and that fglrx was loaded with warnings. THIS IS OKAY.
9. Reboot the system to ensure that all moduels are loaded
10. type: "fglrxconfig" to configure your system During this process, I chose the defaults for everything except to load XFree86-drm and to use the external agp-gart modules. When you get to those parts DO NOT choose the defaults.
11. switch to the directory : "/etc/X11"
12. rename the current "xorg.conf" file to "xorg.conf-backup" and rename the "XF86Config-4" file to "xorg.conf"
* Note, it is a good idea to still keep a XF86Config-4 file ... I did.
13. start the XServer: "startx" to see if it works....
14. run "glxgears" in a consol ... your framerate will be about 600 per 5 seconds.
15. Reboot the system
16. Start the XServer: "startx"
17. run "glxgears" in a consol - Your frame rate should be about 13000 frames per 5 sec.
18. To ensure that the fgl is working, run "fgl_glxgears" in a consol and if it does work you are done.
hope this helps you all.
Specs.
P.S. if you get this message when you type in "fgl_glxgears"...
FGLTexMgr: open of shared memory object failed (Function not implemented)
__FGLTexMgrCreateObject: __FGLTexMgrSHMmalloc failed!!!
you need to do the following...
1.) "pico /etc/fstab" and add the following line... and save it.
"tmpfs /dev/shm tmpfs defaults 0 0"
2.) then mount the drive.... "mount /dev/shm"
3.) now try the fgl_glxgears and it should work.
Processor - AMD 2700+
Motherboard - Gigabyte GA-7N400Pro 2
Memory - 1 Gig PC3200 (512MBx2 Dual Channel
Video - ATI 9800 Pro (128 MB)
Distro - Slackware 10
Kernel - 2.4.26
GUI - KDE
You should not be to supprised as this guide is the flawless version to follow. God knows how many times I have hose the Xorg.conf file using that damn question and answere input.
To test if your new drivers work just goto your screensaver configuration for kde and see if you get like 700FPS in 3D gears. This is the guide to follow for ATI and Slackware 10.0,
1. Make sure you CD to any directory where the files you are instally or working with are
2. Make sure the files you are working with are executable, such as the ATI tgz file mentioned in this "how to"
Step by step and take your time because this works!
Wow that many people like my guide? and did I hear flawless? Well it did take me some time to write but I did it for the Linux Community and because of the troubles I have had myself I know how frustrating things can be
Originally posted by gamelord2 For all of you that are using the NForce2 Chipset, ATI Radeon 9800 Pro, and Slackware 10 with Kernel 2.4.26, this is what you have to do to get your drivers working correctly.
2. run the command: "rpm2tgz fglrx-4.3.0-3.11.1.i386.rpm" to create the corresponding slackpack file
3. run pkgtool to install the "fglrx-4.3.0-3.11.1.i386.tgz" package in the directory in which it was created
4. update your database: "updatedb"
5. switch to the directory that the package was installed in. cd /lib/modules/fglrx/build_mod
6. type "sh make.sh" to build the module
7. type "cd .."
8. type "sh make_install.sh" to install the module. *Note, you may get a warning that it may taint the kernel and that fglrx was loaded with warnings. THIS IS OKAY.
9. Reboot the system to ensure that all moduels are loaded
10. type: "fglrxconfig" to configure your system During this process, I chose the defaults for everything except to load XFree86-drm and to use the external agp-gart modules. When you get to those parts DO NOT choose the defaults.
11. switch to the directory : "/etc/X11"
12. rename the current "xorg.conf" file to "xorg.conf-backup" and rename the "XF86Config-4" file to "xorg.conf"
* Note, it is a good idea to still keep a XF86Config-4 file ... I did.
13. start the XServer: "startx" to see if it works....
14. run "glxgears" in a consol ... your framerate will be about 600 per 5 seconds.
15. Reboot the system
16. Start the XServer: "startx"
17. run "glxgears" in a consol - Your frame rate should be about 13000 frames per 5 sec.
18. To ensure that the fgl is working, run "fgl_glxgears" in a consol and if it does work you are done.
hope this helps you all.
Specs.
Processor - AMD 2700+
Motherboard - Gigabyte GA-7N400Pro 2
Memory - 1 Gig PC3200 (512MBx2 Dual Channel
Video - ATI 9800 Pro (128 MB)
Distro - Slackware 10
Kernel - 2.4.26
GUI - KDE
Thank you Thank you. That was by far the easiest thing that I have had to do in Linux. I just switched to Slackware 10 from Fedora Core 2. The ATI install for Fedora is a bit of a pain and you have to patch it to get it to work. It even gave me my scroll on my mouse. In glxgears, I am averaging 2870 FPS and fgl_glxgears, I am averaging 565 FPS. I am planning to try to tweak a little more speed out of it, but for now. I am quite happy. Thanks!
hi,
i am running slack 10, xorg, nforce2 chipset and have a ati 9500pro. i did everything mentioned in the guide and it worked fine. i ran all commands as root and the drivers installed properly. iam running kernel version 2.6.6 so i skipped over the patches. i used fglrxconfig and chose "yes" for the agpgart external module then i renamed the file fglrxconfig makes to xorg.conf and rebooted. after rebooting kde started which was a big surprise cause i've tried installing the drivers before and failed miserably. the problem is that i dont think iam getting any hardware acceleration. when i run glxgears i get 100fps for 5 seconds (not full screen) which is actually less than what i used to get before i installed the drivers (around 250).
the output for glxinfo looks like this. i see that direct rendering is still set to "no" whats going on?
root@SlackBox:~# glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: No
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_EXT_import_context, GLX_SGI_make_current_read, GLX_SGIS_multisample
client glx vendor string: ATI
client glx version string: 1.3
client glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context,
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_ATI_pixel_format_float,
GLX_ATI_render_texture
GLX extensions:
GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating,
GLX_EXT_import_context
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.4 Mesa 5.0.2)
OpenGL extensions:
GL_ARB_imaging, GL_ARB_multitexture, GL_ARB_texture_border_clamp,
GL_ARB_texture_cube_map, GL_ARB_texture_env_add,
GL_ARB_texture_env_combine, GL_ARB_texture_env_dot3,
GL_ARB_transpose_matrix, GL_EXT_abgr, GL_EXT_blend_color,
GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_texture_env_add,
GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3,
GL_EXT_texture_lod_bias
glu version: 1.3
glu extensions:
GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess
visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav
id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat
----------------------------------------------------------------------
0x23 24 tc 0 24 0 r y . 8 8 8 0 0 16 0 0 0 0 0 1 0 None
0x24 24 tc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 0 1 0 None
0x25 24 tc 0 32 0 r y . 8 8 8 8 0 16 8 16 16 16 16 1 0 None
0x26 24 tc 0 32 0 r . . 8 8 8 8 0 16 8 16 16 16 16 1 0 None
0x27 24 dc 0 24 0 r y . 8 8 8 0 0 16 0 0 0 0 0 1 0 None
0x28 24 dc 0 24 0 r y . 8 8 8 0 0 16 8 16 16 16 0 1 0 None
0x29 24 dc 0 32 0 r y . 8 8 8 8 0 16 8 16 16 16 16 1 0 None
0x2a 24 dc 0 32 0 r . . 8 8 8 8 0 16 8 16 16 16 16 1 0 None
this is what my xorg.conf looks like
# 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).
#
# The module search path. The default path is shown here.
# ModulePath "/usr/X11R6/lib/modules"
EndSection
# **********************************************************************
# Server flags section.
# **********************************************************************
Section "ServerFlags"
# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
# Option "NoTrapSignals"
# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.
# Option "Dont Zoom"
# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.
# Option "DisableVidModeExtension"
# Uncomment this to enable the use of a non-local xvidtune client.
# Option "AllowNonLocalXvidtune"
# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.
# Option "DisableModInDev"
# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).
Identifier "Keyboard1"
Driver "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"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for XFree86
# Option "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# installed.
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen0"
Device "ATI Graphics Adapter"
Monitor "Monitor0"
DefaultDepth 24
#Option "backingstore"
Subsection "Display"
Depth 24
Modes "1280x1024"
ViewPort 0 0 # initial origin if mode is smaller than desktop
# Virtual 1280 1024
EndSubsection
EndSection
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
Section "ServerLayout"
# The Identifier line must be present
Identifier "Server Layout"
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.
Screen "Screen0"
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.