View previous topic :: View next topic |
Author |
Message |
ex0 Tux's lil' helper

Joined: 10 Jul 2003 Posts: 110 Location: Australia
|
Posted: Sat Jul 12, 2003 8:26 am Post subject: Low res and bit depth |
|
|
Hey I'm having trouble getting a resolution higher than 640*480 in X, also a bit depth or whatever its called higher than 8bpp, if I set the bit thingy any higher than 8 I get an error and X won't start.
Also if I set the driver as radeon when configurating xfree86 I get errors too, so I just set it to the standard vga driver. I have a Radeon 9600 Pro...
I did emerge ati-drivers and then tried using the radeon driver etc and still got problems. Is there something else I have to do to install the drivers properly or anything?
can someone please help me with this?
Oh yeh 2 other small things, when I start up the kernal I notice a message saying my hard disk's dma is off and it will operate slowly or something. And I thoguht the password for root and su should be the same, but if I type su then enter the root password it says its incorrect, so I have to log out, then log back in as root every time I want root access. |
|
Back to top |
|
 |
floam Veteran

Joined: 27 Oct 2002 Posts: 1067 Location: Vancouver, WA USA
|
Posted: Sat Jul 12, 2003 8:51 am Post subject: |
|
|
I don't have a radeon card, but you need to include the dri stuff in the kernel I think. You may also need to emerge xfree-drm, or something. |
|
Back to top |
|
 |
shiba n00b

Joined: 27 May 2003 Posts: 14
|
Posted: Sat Jul 12, 2003 10:21 am Post subject: |
|
|
run fglrxconfig as root to setup your card using the new ati drivers.
hdparm can be used to turn dma on. if that dosen't work it might be disable in your systems bios
to be able to use su your use account needs to be in the wheel group. open up /etc/group and find the entry for wheel. add the user names at the end of the line it's on and it should work after you log back in. |
|
Back to top |
|
 |
searcher Apprentice


Joined: 13 Mar 2003 Posts: 175 Location: NL
|
Posted: Sat Jul 12, 2003 10:36 am Post subject: |
|
|
DMA should be set to "on" by default if you selected your motherboard and the option to do so in the kernel. If you get errors from hdparm not allowing to set dma you need to add support for you motherboard.
The low res might also be a result of a poorly configured XF86Config. Did you fill in the vertical and horizontal refresh timings for your monitor? If so, make sure they are correct for your monitor.
~searcher _________________ You are unique ... just like everyone else. |
|
Back to top |
|
 |
ex0 Tux's lil' helper

Joined: 10 Jul 2003 Posts: 110 Location: Australia
|
Posted: Sat Jul 12, 2003 3:30 pm Post subject: |
|
|
cheers for the help I'll try it now
yeh searcher I got the verticle and horizontal rates correct for my monitor... |
|
Back to top |
|
 |
ex0 Tux's lil' helper

Joined: 10 Jul 2003 Posts: 110 Location: Australia
|
Posted: Sat Jul 12, 2003 4:00 pm Post subject: |
|
|
ok I ran fglrxconfig and now when I start X or KDE the monitor just goes blank and stays like that... |
|
Back to top |
|
 |
ex0 Tux's lil' helper

Joined: 10 Jul 2003 Posts: 110 Location: Australia
|
Posted: Sat Jul 12, 2003 4:26 pm Post subject: |
|
|
went in and edited xf86config-4 so that it stated with 8bps, and then instead of freezing the system up with a black screen I just get an error, tried it with 16 and I get the error, went back to 24 and it goes to the black screen and stays there...
got su working thanks shiba....
oh yeh floam I got dri enabled in the kernel
this sucks! i just want x to work pleeeaaaase  |
|
Back to top |
|
 |
shiba n00b

Joined: 27 May 2003 Posts: 14
|
Posted: Sun Jul 13, 2003 2:22 am Post subject: |
|
|
do you have the dri module loaded or built into the kernel? I think I remember that those drivers won't start up if the module is loaded. do an lsmod and if their loaded do modprobe -r (can't remember the module name to take it out)
does it lock up hard(cant change numlock or anything) or does the screen just go black? |
|
Back to top |
|
 |
puggy Bodhisattva


Joined: 28 Feb 2003 Posts: 1992 Location: Oxford, UK
|
Posted: Sun Jul 13, 2003 3:45 am Post subject: |
|
|
I had a problem with X where if I was using a framebuffer I couldn't get anything higher than 640x480, 8 bit. As soon as I started using fluxbox instead of X this went away. So disable the framebuffer if you are using it and see what ahppens.
Puggy _________________ Where there's open source , there's a way. |
|
Back to top |
|
 |
ex0 Tux's lil' helper

Joined: 10 Jul 2003 Posts: 110 Location: Australia
|
Posted: Sun Jul 13, 2003 9:48 am Post subject: |
|
|
I have dri built into the kernel, I don't understand the whole thing with modules, I did lsmod and it said I had none. I forgot to check if it locks up hard or not.
How do I disable framebuffer? Maybe I should try this flux box, is that an X alternative?
My motherboard is an A7V8X by the way, could it be some sort of AGP driver prolblem or something?
One other thing, when I boot into grub if I select "Gentoo Linux" it doesn't boot, I then have to edit it and add the line after the root line that says "kernel /bzImage" then if I press 'b' it boots, but I have to do this every time and can't work out how to get the second line to stay there... |
|
Back to top |
|
 |
ex0 Tux's lil' helper

Joined: 10 Jul 2003 Posts: 110 Location: Australia
|
Posted: Sun Jul 13, 2003 11:48 am Post subject: |
|
|
ok, I was pretty stupid, but the reason I was only getting a low res etc.. was because I was using the standard vga driver which only supports 640 resolution...
I changed to to vesa (not knowing what it is {and still not knowing}) and it working in 24 bit mode fine. If I use radeon or ATI drivers in the XF86config booting x fails. If I use the fglrxconfig instead of xf86config to config x, I get the black screen thingy.
I went on following ther installlation (from where I was up to after emerging kde) and changed the rc.conf do DISPLAYMANAGER=gdm and then did rc-update add xdm default. However now when I boot up it goes into the x boot thing (I assume thats xdm) and I don't know how to start kde. I can start kde by typing "kdm" in the text-based console but now I can't get into that I can only get into X and it doesn't work from there.
Also my mouse sensitivity is really low, how do I increase that, I have a usb mouse with a ps2 adapter thingy, I read something about if yo use a USB mouse it ajusts the sensitivty automatically or something.
This is really sucking, someone please help. |
|
Back to top |
|
 |
ex0 Tux's lil' helper

Joined: 10 Jul 2003 Posts: 110 Location: Australia
|
Posted: Sun Jul 13, 2003 12:50 pm Post subject: |
|
|
ok, I managed to get rid of the xdm thing by rc-update del xdm default, and now I can get back into kde temporarily til someone helps me with that...
I got another problem where I can't get the refresh rate higher than 60hz, which gives me a shocking headache, I need help on this one urgently (I tried in the x configurater thing in kde and it says its set to 85hz but I'm only getting 60) |
|
Back to top |
|
 |
shiba n00b

Joined: 27 May 2003 Posts: 14
|
Posted: Sun Jul 13, 2003 4:14 pm Post subject: |
|
|
The vesa drivers aren't going to support any accelleration at all, so if you want to play a game sometime you should try to get the ati drivers working.
when your selecting options in the kernel most stuff can be either built in or modules. Modules can be loader/unloaded while the system is out.
can you post your XF86config file? also, what error messages where you getting before you ran fglrxconfig?
do you have dpms enabled for your monitor(its in the monitor section)? it could be that the resolution xfree is trying to use dosen't ork with your monitor |
|
Back to top |
|
 |
ex0 Tux's lil' helper

Joined: 10 Jul 2003 Posts: 110 Location: Australia
|
Posted: Mon Jul 14, 2003 4:02 am Post subject: |
|
|
heres my XF86Config file...
# 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" "us"
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "PS/2"
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 "Mitsubishi Diamond Plus 93SB"
# 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 30-96
# 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-160
vendorname "[Mitsubishi Diamond Plus 93SB]"
modelname "[Mitsubishi Diamond Plus 93SB]"
ModeLine "1280x1024/85Hz" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +HSync +VSync
ModeLine "800x600/100Hz" 69.65 800 864 928 1088 600 604 610 640 -HSync -VSync
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:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# Device configured by xf86config:
Section "Device"
Identifier "Radeon 9600 Pro"
Driver "vesa"
#VideoRam 131072
# Insert Clocks lines here if appropriate
vendorname "Generic"
boardname "vesa"
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 "Radeon 9600 Pro"
Monitor "Mitsubishi Diamond Plus 93SB"
DefaultDepth 16
Subsection "Display"
Depth 8
Modes "800x600/100Hz" "1024x768" "800x600" "640x480"
ViewPort 0 0
Virtual 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "800x600/100Hz" "1024x768" "800x600" "640x480"
ViewPort 0 0
Virtual 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "800x600/100Hz" "1024x768" "800x600" "640x480"
ViewPort 0 0
Virtual 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
Section "InputDevice"
Identifier "Keyboard"
Option "XkbModel" "pc104"
Option "XkbLayout" "us"
Driver "keyboard"
EndSection
Section "InputDevice"
Identifier "Mouse"
Option "Protocol" "PS/2"
Option "Device" "/dev/psaux"
Driver "mouse"
Option "ZAxisMapping" "4 5"
EndSection
I'm not sure what you mean by what error messages were I getting before I ran fglxconfig, but after I ran it if I attempted to boot I just got a blank screen (numlock and capslock etc... would go on and off, but ctrl+alt+backspace ect... wouldn't do anything)
COuldn't find DPMS anywhere... |
|
Back to top |
|
 |
ex0 Tux's lil' helper

Joined: 10 Jul 2003 Posts: 110 Location: Australia
|
Posted: Mon Jul 14, 2003 4:45 am Post subject: |
|
|
I solved the problem of getting the incorrect resoltuion (you can see what the problem is if you look at the XF86Config file), I've worked out that I can't run x in any other refresh rate other than 60Hz (which I sort of knew before).
I tried configuring fglrxconfig again and I check the config file and I had DPMS enabled, so I turned it off (I wasn't sure if it was supposed to be on) then tried again but I got the same black screnn. Perhaps I am chosing other options incorrectly in the setup, I didn't enable buffer swaping, TLS method I left as the default and I didn't enable an external AGP Gart (I tried enabling that after loading the module into the kernel and it didnt help), is this correct?
Perhaps vesa drivers only support 60hz?
My monitor can run other refresh rates fine in windows and games, even in the konsole thingy when no GUI is activated its running at 70hz |
|
Back to top |
|
 |
puggy Bodhisattva


Joined: 28 Feb 2003 Posts: 1992 Location: Oxford, UK
|
Posted: Mon Jul 14, 2003 7:30 am Post subject: |
|
|
ex0 wrote: | I solved the problem of getting the incorrect resoltuion (you can see what the problem is if you look at the XF86Config file), I've worked out that I can't run x in any other refresh rate other than 60Hz (which I sort of knew before).
I tried configuring fglrxconfig again and I check the config file and I had DPMS enabled, so I turned it off (I wasn't sure if it was supposed to be on) then tried again but I got the same black screnn. Perhaps I am chosing other options incorrectly in the setup, I didn't enable buffer swaping, TLS method I left as the default and I didn't enable an external AGP Gart (I tried enabling that after loading the module into the kernel and it didnt help), is this correct?
Perhaps vesa drivers only support 60hz?
My monitor can run other refresh rates fine in windows and games, even in the konsole thingy when no GUI is activated its running at 70hz |
You want to install the ATI Radeon drivers. _________________ Where there's open source , there's a way. |
|
Back to top |
|
 |
ex0 Tux's lil' helper

Joined: 10 Jul 2003 Posts: 110 Location: Australia
|
Posted: Mon Jul 14, 2003 8:00 am Post subject: |
|
|
I have the ATI-Radeon drivers but I can't get them to work...
only driver I can get to work is vesa |
|
Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|