| View previous topic :: View next topic |
| Author |
Message |
sumedha
n00b
Joined: 04 Jan 2005
Posts: 12
|
 Posted: Sun Jan 30, 2005 7:08 pm Post subject: ATI AMD64 blank display problem, 3d Accleration [SOLVED] |
 |
|
I emerged ati-drivers and ran fglrxconfig . I renamed the /etc/X11/XF86Config-4 file to /etc/X11/xorg.cong . I changed the Keyboard driver to "kbd". I set Option "UseInternalAGPGART" "no". I have agpgart module.
Now, when I issue the command startx, I get a blank screen. The computer doesn't respond to my keyboard inputs. I have to turn off the power and on again.
What could I do?
Note:
I have:
AMD64 Athlon 3000+
ATI radeon 9600
ASUS K8NE Deluxe Motherboard
Last edited by sumedha on Tue Feb 01, 2005 3:20 am; edited 1 time in total |
|
| Back to top |
|
 |
Sm1
Apprentice
Joined: 02 Dec 2003
Posts: 251
Location: Ames, IA
|
| Posted: Sun Jan 30, 2005 7:14 pm Post subject: |
|
|
when you made the agpgart module did you enable both the agp options? agp-amd64 i think is the other one, but I know there are two agp options that need to be enabled, at least with my board.
Or you can just enable IOMMU and it will build the agp into the kernel |
|
| Back to top |
|
|
sumedha
n00b
Joined: 04 Jan 2005
Posts: 12
|
| Posted: Sun Jan 30, 2005 7:19 pm Post subject: |
|
|
I get these options :
<M> /dev/agpgart (AGP Support)
│ │ <M> AMD Opteron/Athlon64 on-CPU GART support
│ │ < > Intel i865 chipset support
I disabled IOMMU as the /dev/agpgart options were not accessible with it enabled. |
|
| Back to top |
|
|
Sm1
Apprentice
Joined: 02 Dec 2003
Posts: 251
Location: Ames, IA
|
| Posted: Sun Jan 30, 2005 8:04 pm Post subject: |
|
|
Those are the two modules that you need. Did you modprobe the modules before loading X? If not then modprobe each of them.
If this still doesnt work, I made a post a week or two ago about a patch that you can apply to the ati driver to use the internal GART, which is what I do.
https://forums.gentoo.org/viewtopic.php?t=282953&highlight= |
|
| Back to top |
|
|
Apewall
Apprentice
Joined: 01 Dec 2004
Posts: 248
Location: USA
|
| Posted: Sun Jan 30, 2005 10:11 pm Post subject: |
|
|
I'm having the same problem, I added the agpgart to my modules and it loads fine, but the other one i don't even know the module name, could be that for me:P
_________________
Posting for dummies |
|
| Back to top |
|
|
SnippyHolloW
n00b
Joined: 22 Jan 2005
Posts: 29
Location: Grenoble (France)
|
| Posted: Sun Jan 30, 2005 11:28 pm Post subject: |
|
|
I got a black screen too, AMD64 3200+ with 9700pro, i configure X11 with lcd 1280x1024@60hz and the startx gives me a black screen ... i tried 4 diff config but ... if someone got an idea, not that i dislike console mode but ... 
_________________
Play with the best, Die like the rest ... on linux :] |
|
| Back to top |
|
|
Apewall
Apprentice
Joined: 01 Dec 2004
Posts: 248
Location: USA
|
| Posted: Mon Jan 31, 2005 1:34 am Post subject: |
|
|
What are you adding to the module loader?
_________________
Posting for dummies |
|
| Back to top |
|
|
Sm1
Apprentice
Joined: 02 Dec 2003
Posts: 251
Location: Ames, IA
|
| Posted: Mon Jan 31, 2005 2:33 am Post subject: |
|
|
| Apewall wrote: | | What are you adding to the module loader? |
To find out, look in your /lib/modules/(KERNELVERSION)/kernel/drivers/ in the char folder i believe will have your loadable modules. |
|
| Back to top |
|
|
Apewall
Apprentice
Joined: 01 Dec 2004
Posts: 248
Location: USA
|
| Posted: Mon Jan 31, 2005 2:37 am Post subject: |
|
|
| Code: |
# /etc/modules.autoload.d/kernel-2.6: kernel modules to load when system boots.# $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/modules.autoload.d/kernel-2.$#
# Note that this file is for 2.6 kernels.
#
# Add the names of modules that you'd like to load when the system
# starts into this file, one per line. Comments begin with # and
# are ignored. Read man modules.autoload for additional details.
# For example:
# 3c59x
agpgart
amd64-agp
usbhid
ehci-hcd
uhci-hcd
sk98lin
|
This is what I'm using right now.
_________________
Posting for dummies |
|
| Back to top |
|
|
netpro256
n00b
Joined: 23 Sep 2004
Posts: 21
|
| Posted: Mon Jan 31, 2005 3:04 am Post subject: |
|
|
This has been occupying the better part of my afternoon, but I finally got it working (Athlon64/Radeon 9800/Asus K8V/Kernel 2.6.9).
First, configure the kernel like sumedha suggests:
| Quote: | | Code: | <M> /dev/agpgart (AGP Support)
│ │ <M> AMD Opteron/Athlon64 on-CPU GART support
│ │ < > Intel i865 chipset support |
I disabled IOMMU as the /dev/agpgart options were not accessible with it enabled. |
These must be built as modules and NOT compiled in. Rebuild the kernel and reboot to it.
| Code: | | make && make modules_install |
Then, emerge the ATI drivers. I had to upgrade xorg-x11 to 6.8.0-rc4 first because the previous install (rc3) was blocking ati-drivers.
| Code: | | ACCEPT_KEYWORDS="~amd64" emerge ati-drivers |
Not sure if this step is necessary, but it didn't hurt anything:
Lastly, run fglrxconfig to reconfigure X. On the last step, it will ask if you want to use the AGPGART module provided by the kernel instead of relying on fglrx. Choose YES.
| Code: | ==============================================================================
Advanced OS Settings
==============================================================================
External AGPGART module:
It is possible (but not recommended) to turn off the usage of
built-in agp support of the provided fglrx kernel module and
use the external AGP GART module (agpgart.o) of the Linux kernel.
If you want to use the external module then ensure that it loads
prior to the drivers full startup. In order to manually load the
external agpgart module execute this on the commandline (as root):
/sbin/insmod agpgart
or alternatively configure your system to auto load the module.
Do you want to use the external AGP GART module (y/n)? [n] y |
After this step, confirm the write to /etc/X11/XF86Config-4. I found out I also needed to edit this generated file and manually replace the keyboard driver with "kbd". Next, replace your current xorg.conf with this new config:
| Code: | cd /etc/X11/
mv XF86Config-4 xorg.conf |
Now for the moment of truth:
If all goes well you should be greeted by your regular X window manager. The following modules should be automatically loaded for you:
- agpgart
- amd64-agp
- fglrx |
|
| Back to top |
|
|
Sm1
Apprentice
Joined: 02 Dec 2003
Posts: 251
Location: Ames, IA
|
| Posted: Mon Jan 31, 2005 3:53 am Post subject: |
|
|
| netpro256 wrote: |
- agpgart
- amd64-agp
- fglrx |
amd64-agp..... that is the last one I was talking about. If after followin that process, you are still black screening, modprobe those before X and check dmesg for any errors. |
|
| Back to top |
|
|
sumedha
n00b
Joined: 04 Jan 2005
Posts: 12
|
| Posted: Mon Jan 31, 2005 4:52 am Post subject: dmesg |
|
|
I still get a blank screen with keyboard and mouse not responding. This is the output of my dmesg. I don't find any errors. Please have a look at it.
http://www.geocities.com/sumedhaswamy/dmesg.txt
Thanks. |
|
| Back to top |
|
|
Sm1
Apprentice
Joined: 02 Dec 2003
Posts: 251
Location: Ames, IA
|
| Posted: Mon Jan 31, 2005 12:05 pm Post subject: |
|
|
That dmesg looks pretty clean to me, lets see now. I would say maybe your radeon framebuffer, but I am using one and it seems to work fine. You could try turning off the bootsplash though for a boot.
Also when X freezes, does it make a log file at all, more importantly, are there any errors it is showing about fglrx? |
|
| Back to top |
|
|
sumedha
n00b
Joined: 04 Jan 2005
Posts: 12
|
| Posted: Mon Jan 31, 2005 4:41 pm Post subject: 3D Accleration |
|
|
I checked the log and found out the a font was not being found. I added the appropriate entries and issued "startx". X started. But, I am still unable to get 3D accleration. The output of glxinfo is :
| Quote: | name of display: :0.0
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't find RGB GLX visual
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
----------------------------------------------------------------------
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
0x21 24 tc 1 0 0 c . . 0 0 0 0 0 0 0 0 0 0 0 0 0 None
Xlib: extension "GLX" missing on display ":0.0".
Xlib: extension "GLX" missing on display ":0.0".
0x22 24 dc 1 0 0 c . . 0 0 0 0 0 0 0 0 0 0 0 0 0 None
Segmentation fault
|
The /var/log/Xorg.0.log has this interesting information :
| Quote: | (II) fglrx(0): UMM area: 0xd0501000 (size=0x07aff000)
(II) fglrx(0): driver needs XFree86 version: 4.3.x
(WW) fglrx(0): could not detect XFree86 version (query_status=-3)
(WW) fglrx(0): ***********************************************
(WW) fglrx(0): * DRI initialization failed! *
(WW) fglrx(0): * (maybe driver kernel module missing or bad) *
(WW) fglrx(0): * 2D acceleraton available (MMIO) *
(WW) fglrx(0): * no 3D acceleration available *
(WW) fglrx(0): ********************************************* *
(II) fglrx(0): FBADPhys: 0xd0000000 FBMappedSize: 0x08000000
(II) fglrx(0): FBMM initialized for area (0,0)-(1024,8191)
(II) fglrx(0): FBMM auto alloc for area (0,0)-(1024,768) (front color buffer - assumption)
(==) fglrx(0): Backing store disabled
(==) fglrx(0): Silken mouse enabled
(II) fglrx(0): Using hardware cursor (scanline 768)
(II) fglrx(0): Largest offscreen area available: 1024 x 7419
(**) Option "dpms"
(**) fglrx(0): DPMS enabled
|
Is there something I can do? |
|
| Back to top |
|
|
Apewall
Apprentice
Joined: 01 Dec 2004
Posts: 248
Location: USA
|
| Posted: Tue Feb 01, 2005 3:02 am Post subject: |
|
|
what solved it for me is when it asks if you would like to use external AGPGART choose YES, no doesn't work, and wont boot up.
After selecting yes everything seems to be working correctly, I've only ran glxgears and i'm getting 5000fps so I'll let you guys know if it works well in ut2004 if i can get it running.
I'm not sure why you have to select yes to external AGPGART.
_________________
Posting for dummies |
|
| Back to top |
|
|
sumedha
n00b
Joined: 04 Jan 2005
Posts: 12
|
| Posted: Tue Feb 01, 2005 3:17 am Post subject: It works! |
|
|
Finall, I got the ATI Drivers working!
I followed the directions given at : https://forums.gentoo.org/viewtopic.php?t=250647&start=310
I used the version of drivers directly in the portage.
My xorg.conf looks like this :
| Quote: |
# File: XF86Config-4
# File generated by fglrxconfig (C) ATI Research, a substitute for xf86config.
# **********************************************************************
# 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"
# RgbPath "/usr/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/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/Type1/"
# FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/local/"
# FontPath "/usr/share/fonts/Speedo/"
# FontPath "/usr/share/fonts/TrueType/"
# FontPath "/usr/share/fonts/freefont/"
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/lib64/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 "kbd"
# 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" "pc104"
Option "XkbLayout" "us"
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 30-70
VertRefresh 50-120
Option "DPMS"
# === mode lines based on GTF ===
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"
# ### generic DRI settings ###
# === disable PnP Monitor ===
#Option "NoDDC"
# === disable/enable XAA/DRI ===
Option "no_accel" "no"
Option "no_dri" "no"
# === misc DRI settings ===
Option "mtrr" "off" # disable DRI mtrr mapper, driver has its own code for mtrr
# ### FireGL DDX driver module specific settings ###
# === Screen Management ===
Option "DesktopSetup" "0x00000000"
Option "MonitorLayout" "AUTO, AUTO"
Option "IgnoreEDID" "off"
Option "HSync2" "unspecified"
Option "VRefresh2" "unspecified"
Option "ScreenOverlap" "0"
# === TV-out Management ===
Option "NoTV" "yes"
Option "TVStandard" "NTSC-M"
Option "TVHSizeAdj" "0"
Option "TVVSizeAdj" "0"
Option "TVHPosAdj" "0"
Option "TVVPosAdj" "0"
Option "TVHStartAdj" "0"
Option "TVColorAdj" "0"
Option "GammaCorrectionI" "0x00000000"
Option "GammaCorrectionII" "0x00000000"
# === OpenGL specific profiles/settings ===
Option "Capabilities" "0x00000000"
# === 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" "off"
# === Center Mode (Laptops only) ===
Option "CenterMode" "off"
# === Pseudo Color Visuals (8-bit visuals) ===
Option "PseudoColorVisuals" "off"
# === QBS Management ===
Option "Stereo" "off"
Option "StereoSyncEnable" "1"
# === FSAA Management ===
Option "FSAAEnable" "no"
Option "FSAAScale" "1"
Option "FSAADisableGamma" "no"
Option "FSAACustomizeMSPos" "no"
Option "FSAAMSPosX0" "0.000000"
Option "FSAAMSPosY0" "0.000000"
Option "FSAAMSPosX1" "0.000000"
Option "FSAAMSPosY1" "0.000000"
Option "FSAAMSPosX2" "0.000000"
Option "FSAAMSPosY2" "0.000000"
Option "FSAAMSPosX3" "0.000000"
Option "FSAAMSPosY3" "0.000000"
Option "FSAAMSPosX4" "0.000000"
Option "FSAAMSPosY4" "0.000000"
Option "FSAAMSPosX5" "0.000000"
Option "FSAAMSPosY5" "0.000000"
# === Misc Options ===
Option "UseFastTLS" "0"
Option "BlockSignalsOnLock" "on"
Option "UseInternalAGPGART" "no"
Option "ForceGenericCPU" "no"
BusID "PCI:1:0:0" # vendor=1002, device=4151
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 "1024x768" "800x600" "640x480"
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 ###
|
|
|
| Back to top |
|
|
sumedha
n00b
Joined: 04 Jan 2005
Posts: 12
|
| Posted: Tue Feb 01, 2005 3:22 am Post subject: Thanks. |
|
|
| I've edited the subject of this post so that it gets reflected better in searches. Thanks a lot Forum for your help! |
|
| Back to top |
|
|
Apewall
Apprentice
Joined: 01 Dec 2004
Posts: 248
Location: USA
|
| Posted: Tue Feb 01, 2005 4:04 am Post subject: |
|
|
| Quote: | Option "UseInternalAGPGART" "no"
|
_________________
Posting for dummies |
|
| Back to top |
|
|
|
Gentoo on AMD64
