Hi there i just installed Mandrake 9.2 and am in need of some help. When i boot up my computer GRUB starts and i chose Linux. Then a Blue screen comes up and it says that its booting the system. After the progress gets to about 85% the screen starts to freak out flashing and the screen then goes to a black screen that askes for a local host login. I type root then my password. Then type startx and and i comes up with a error and will not start the linux desktop. I have not installed any drivers. I do have a ATI 9600xt card. What do i do. I an a newbie to linux and want to learn more about it. I can use any help possible. Step by step is better for me since i have never used linux before. Any suggestions are appreciated. Also i have tryed the XFdrake thing and still nothing. Thanks for your time.

I feel you got wrong screen settings.

When you installed it you were asked to verify your configuration at the end of install process.
If you have chosen wrong screen, you might have that problem.

Make sure you have selected a correct screen (normally it should be auto detected though).
If your model isn't listed, select a generic screen. MAKE SURE you select correct resolution (1024x768 etc.)!

N.B. My AOC flat panel isn't listed in 9.1 so I selected a generic flat panel 1024x768.

This should help.

Another reason might be in the corrupt CDs. You need three CDs and you should better install it not from within Windows. Just slide the CD into your CD-ROm and reboot.

If nothing helps, check the Mandrake forum on this site, and/or compatibility list.

well my screen size i have set to 1280 by 1024. So should i use XFdrake to change the settings????? The CDs ARE find i know that because i installed them on another computer weeks ago and that computer works fine.

Yes, you can try XFdrake. Be careful though. Make sure you select all settings right (resolution, horisontal and vertical frequencies etc. -- see your screen specs.)
I am not good at XFdrake, so when I had a similar problem I found it easier to reinstall and make sure I verify the settings at the end of the install process.
Before you do so, though, check that your screen and video card are all right for Linux. There is that hardware compatibility problem, which hit sometimes here or there because hardware vendors think only about M$.

OK i tryed all of the Xfdrake settings and then tryed test. And it came up with an error. So i got out of it and got into lynx and went to www.ati.com and dl the drivers for the 9600 series. It is a rpm file. I saved it under root. When i type in /root/ati.rpm and hit enter it says acess denied. What can i do. I know that its the driver for my viedo card. Mandrake doesnot have a slection for radeon 9600xt????? What can i do to install the drivers from ati site. the .rpm file?????

Radeon 9600 it should have...
Before you install anything under linux you should become super-user. Did you type su before trying to install the rpm?

Anyway, it looks strange. Shouldn't be that hard with the hardware you got.
Please, post whatever messages you get here so that we can help you better.

The main errors that i get are:
(WW) RADEON: No Matching Device section for instance (BusID PCI: 3:0:1) found
(EE) No devices detected

then it also says:
Fatal Server Error
no screens found

I really am stumped and am wanting to try out linux. I finally got the drivers
downloaded from ati.com and they are in the /root/ dir. It is an .rpm file.
How would i go about installing this?????
Would i type /root/ati.rpm???????
I can use any information that comes in thank you all for your time.

RPM-files aren't executables as in windoze, to install an rpm type:

$> rpm -iv /root/ati.rpm

In linux filenames (actually, almost everything) is case sensitive, so ATI.rpm isn't the same as ati.rpm. You have to be root as well to install those drivers.
As Linuxfond said, those drivers should already be included. You will also probably have to edit your /etc/X11/XF86Config-4 file, I am sure this explanation will be available on the site where you've got your drivers.

Good luck,
elluva

In the meantime, you could try the generic 'vesa' driver. Your x-windows will be usable until you get the ati drivers working.

I don't know what's up exactly, but I had exactly the same problem some time ago. Probably it is hardware problem.
I fixed it by reinstalling the whole thing giving default answers at all steps, except for x server confguration. There my screen wasn't chosen correctly and I told the install program which screen I have. Good luck.

Learning isn't always easy, but it always pays off.

Slackware doesn't ask anything when installing about your settings, but has a generic file that always works . Past the text below in a file and then perform:

$> cp /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.backup
$> cp <filename> /etc/X11/XF86Config-4

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

# NOTE: This is a NEW IMPROVED version of XF86Config-fbdev that uses the vesa
# driver instead of the fbdev driver. Thanks to Kenneth Fanyo who pointed
# this out to me.

# This XF86Config file is designed for use with the VESA framebuffer.
# This generic interface should work with nearly all video cards
# (although not every card will support every resolution).

# With the new driver, it should no longer be required to have frame buffer
# support in the kernel, or to run it on the console.
#
# Enjoy!
# -- volkerdi@slackware.com
#

# **********************************************************************
# 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 font modules
Load "type1"
Load "freetype"
Load "speedo"

# This loads the GLX module
Load "glx"

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/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/"

# ModulePath can be used to set a search path for the X server modules.
# 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 "DontZoom"

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

# Set the basic blanking screen saver timeout.

# Option "blank time" "10" # 10 minutes

# Set the DPMS timeouts. These are set here because they are global
# rather than screen-specific. These settings alone don't enable DPMS.
# It is enabled per-screen (or per-monitor), and even then only when
# the driver supports it.

# Option "standby time" "20"
# Option "suspend time" "30"
# Option "off time" "60"

# On some platform the server needs to estimate the sizes of PCI
# memory and pio ranges. This is done by assuming that PCI ranges
# don't overlap. Some broken BIOSes tend to set ranges of inactive
# devices wrong. Here one can adjust how aggressive the assumptions
# should be. Default is 0.

# Option "EstimateSizesAggresively" "0"

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"

# Set the keyboard auto repeat parameters. Not all platforms implement
# this.

# Option "AutoRepeat" "500 5"

# Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)).

# Option "Xleds" "1 2 3"

# To disable the XKEYBOARD extension, uncomment XkbDisable.

# Option "XkbDisable"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a European
# keyboard, you will probably want to use one of:
#
# Option "XkbModel" "pc102"
# Option "XkbModel" "pc105"
#
# If you have a Microsoft Natural keyboard, you can use:
#
# Option "XkbModel" "microsoft"
#
# If you have a US "windows" keyboard you will want:
#
# Option "XkbModel" "pc104"
#
# 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" ""

EndSection


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

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"

# On platforms where PnP mouse detection is supported the following
# protocol setting can be used when using a newer PnP mouse:

# Option "Protocol" "Auto"

# The available mouse protocols types that you can set below are:
# Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2
# Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2
# MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse
# ThinkingMouse ThinkingMousePS/2 Xqueue
Option "Protocol" "PS/2"

# The mouse device. The device is normally set to /dev/mouse,
# which is usually a symbolic link to the real device.

Option "Device" "/dev/mouse"
# Option "Device" "/dev/psaux"
# Option "Device" "/dev/ttyS0"
# Option "Device" "/dev/ttyS1"

# 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

# Some examples of extended input devices

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

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

HorizSync 31.5 - 50.0

# 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 40-90

EndSection


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

# Any number of graphics device sections may be present

Section "Device"
Identifier "VESA Framebuffer"
Driver "vesa"
#VideoRam 4096
# Insert Clocks lines here if appropriate
EndSection

# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "VESA Framebuffer"
Monitor "My Monitor"

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.

# DefaultDepth 8
# DefaultDepth 16
DefaultDepth 24
# DefaultDepth 32

# "1024x768" is also a conservative usable default resolution. If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)

Subsection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 32
Modes "1024x768" "800x600" "640x480"
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

--End Of File--

It is possible that you'll have to alter some settings about your mouse device, but that are problems for later on, first try running 'startx' after you've copied this. I can mail the file as well if you give me your email-adress.

no a easier way is just to re-install mandrake (well not quite). Put your mandrake disk in a go through the istallation process. This time up-grade insead on installing. It will be quite quick from here you you will end up with the summary of your computer hardware. You will see your video and how it is set up. Change this and the driver above in the list and test. I couldn't run any higher than 800x600 so keep the res down, enough so you can see it
Once you can boot into x with any old resolution install ati drivers and you can cusomise video settings

yes, ok this will be easy and fast... but what will he learn? Don't always take the easy (read: dumb-ass) road, try to learn why there were problems. When you solve them you will feel great you solved it instead of just (fake-)upgraded the system. Then you will learn how Linux works and then maybe you will be able to solve a problem when a (fake-)upgrade doesn't work.

I am aware of it, I did as well when I started learning, but it is not the right way! Linux isn't windoze...

Using commands is what makes Linux fun, to me. It's not an OS for Windows users, believe me. Most Windows users cower at having to type a command to get something installed or working properly. And don't reinstall unless something is corrupt.

Anywho, lemme get off that rant and onto the subject. I have an ATI 9600 (can't remember if it's and SE or what), and I'm having the same problem. I had trouble during the install when it tested the video settings. I tried reinstalling, thinking it was just an installation error, but when I read the error again, it looked like XFree86 was looking for a different kernel version - 2.4.18-xx compared to the 2.4.22-10mdk that came with my distro. Could that be the conflict?

Or will installing the latest ATI driver fix it? Or should I just play with the settings within bash? BTW, what is the command to adjust the display settings?

What kind of an install was your driver? Could it be source, or a source rpm?
Those often need the kernel header files, if I am right, run 'urpmi -y kernel-source', you'll get 2 options. Choose the running kernel and try again installing your drivers...

CTL-ALT-[KEYPAD+|KEYPAD-] toggles your display setting once you're in X.

Another thing you could try is '/usr/X11R6/bin/X -configure' this generates a configuration file, just replace /etc/X11/XF86Config-4 with the one you generated.
(Actually I forgot to mention that once you've installed the drivers X should detect them by running this command, oops...)

Try it and post the results here...