Hello! I have just installed Fedora Core 5, and I try to install video drivers for my ATI video card. First, I tried to install the ATI Proprietary driver, but without success. Then, I read that this driver isn't so good, and that there is a driver much better if I install the driver using yum.
I tried to install it with yum. My Kernel was updated, and it wrote that the driver was installed. After I rebooted my system, a very strange thing happened: I saw how Linux loaded everything, and just when I had to see to login window, the screen became black. But not black, as if it was off, but there was a "frame"(a little white) on the screen, and then I couldn't see anything. Even if tried to switch to CTRL+ALT+F1, or any other, I also coulndn't see anything. The same if I turned off X Server. The problem is that after I install it I can't do anything, and I just have to reinstall Linux...
I tried to install the original ATI drivers, and the yum driver a few times, and it doesn't word. (Although I have a feeling that yum works, and there is a problem that it doesn't show anything on the screen).
My system is AMD 3000+, 1GB RAM, and (the most important) ATI Radeon x1300 Pro.
I not that professional, so I just don't know what to do...
Any help will be appreciated!

Thanks in advance!

After installing it with yum I made another few steps. First, I've done: "setsebool -P allow_execmod=1", then I turned into init 3, and done "ati-fglrx-config-display enable". Then I entered: "aticonfig --initial "the path to xorg.conf", then "aticonfig --resolution=0,1024x768,800x600,640x480"
Then I turned into init 5. It seemed that the driver was installed. I even had the ATI control center... But when I entered fglrxinfo I received an error... And when I restarted my computer, again, I saw that black screen. (I guess it become black the moment the driver is loaded)

Maybe someone have an idea?

Whats does your xorg.conf / log look like?

What happens you comment out Load "glx"? Same thing?

Ok, when I commented "glx", the screen was still black, but when I pressed CTRL+ALT+F1, and then CTRL+ALT+F7 I saw the login screen.
My xorg.conf file looks like this:

# XFree86 4 configuration created by pyxf86config

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "aticonfig-Screen[0]" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"

# Multiple FontPath entries are allowed (they are concatenated together)
# By default, a font server independent of the X server is
# used to render fonts.
FontPath "unix/:7100"
EndSection

Section "Module"
Load "dbe"
Load "extmod"
Load "fbdevhw"
### Load "glx"
Load "record"
Load "freetype"
Load "type1"
Load "dri"
EndSection

Section "InputDevice"

# Specify 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 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"
# Or if you just want both to be control, use:
# Option "XkbOptions" "ctrl:nocaps"
#
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "yes"
EndSection

Section "Monitor"

### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
### Comment all HorizSync and VertSync values to use DDC:
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "F700B"
DisplaySize 330 250
HorizSync 30.0 - 71.0
VertRefresh 50.0 - 160.0
Option "dpms"
EndSection

Section "Monitor"
Identifier "aticonfig-Monitor[0]"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "vesa"
VendorName "Videocard vendor"
BoardName "ATI Technologies Inc Unknown device 7162"
EndSection

Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
Option "ForceMonitors" "crt1"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 16
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "Screen"
Identifier "aticonfig-Screen[0]"
Device "aticonfig-Device[0]"
Monitor "aticonfig-Monitor[0]"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "DRI"
Group 0
Mode 0666
EndSection

Still, it doesn't work... What does it mean that it if I commented "glx" I could see something? What is the glx module?

When I commented load DRI, I also could see somthing on the screen but only after changing to console, and then returning to graphics mode.
Another problem is that when I type fglrxinfo I get an error...

Another little question: When a blank screen appears, is there any way to load the vesa driver without installing Linux again?
Because every time I have this screen I have to reinstall Linux...

Maybe some has an idea what I can do?

I would be very thankful...

I got some bad news for you. First off, your card sucks and you could've gotten a better, more supported, Nvidia 6600 GT. Ati tricks you into believing their card is faster at first by having (more commonly looked at)higher clock speeds. But in fact they have half the pipelines.

http://www.neoseeker.com/Articles/Ha..._review/7.html

http://www.xbitlabs.com/articles/vid...-x1300_23.html

http://www.extremetech.com/article2/...1875352,00.asp
------------------------------------------------------------

This is an example of a similarly priced Ati vs Nvidia.

http://www.newegg.com/Product/Produc...82E16814129054

vs.

http://www.newegg.com/Product/Produc...82E16814141015



Secondly you have to edit your xorg file, probably. It seems you have some redundant devices that really don't do much for each other.

If you could delete this


Section "Device"
Identifier "Videocard0"
Driver "vesa"
VendorName "Videocard vendor"
BoardName "ATI Technologies Inc Unknown device 7162"
EndSection

And perhaps comment out this

Option "ForceMonitors" "crt1"

I told you to comment out glx because I've experienced your exact same problem before and on the same distro(64-bit) with the exact same card.
I was even desperate enough to install a completely different distro. I got a little bit further on Suse, in terms of the card actually pretending to work. But end results are the same.

X1300 is a crap card.

Ati seems to have bad rep with linux in general. Some people say they have no problems with Ati, its just the distro.. blah,blah. Well I bet they were'nt using this card. You've got the real creme de la crap here.

I will try that... But why should I comment it? X Server doesn't even look at the Device section of the vesa driver...
And what are glx and dri?

I got mines to work by commenting out Load extmod from xorg.conf the only problem is you have to ctrl+alt+F7 everytime you boot up

[QUOTE=YevgenyEfter]I will try that... But why should I comment it? X Server doesn't even look at the Device section of the vesa driver...

It never hurts to be sure. I know you're looking at this part here and going

Screen 0 "aticonfig-Screen[0]" 0 0

Hey wait that means Xorg is configured to load the ati screen and not something else. You're probably right on this one, but it reduces the complexity/clutter of your xorg file and allows you to approach the problem with better clarity and sanity of mind.




OpenGl and direct rendering. Used primarily for games and 3d modeling programs. Good luck on getting those to work, BTW, particulary with this card.

Do you have an ATI Radeon X1300 Pro card?

no I have the X1800XT

And do you have glx and dri support?

yes i do, the only thing I commented out with load extmod. i got full funtion of my video card.

# Xorg configuration created by system-config-display

Section "ServerLayout"
Identifier "single head configuration"
Screen 0 "aticonfig-Screen[0]" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"

# Multiple FontPath entries are allowed (they are concatenated together)
# By default, a font server independent of the X server is
# used to render fonts.
FontPath "unix/:7100"
EndSection

Section "Module"
Load "dbe"
#Load "extmod"
Load "fbdevhw"
Load "glx"
Load "record"
Load "freetype"
Load "type1"
Load "dri"
EndSection

Section "InputDevice"

# Specify 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 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"
# Or if you just want both to be control, use:
# Option "XkbOptions" "ctrl:nocaps"
#
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "yes"
EndSection

Section "Monitor"

### Comment all HorizSync and VertSync values to use DDC:
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Dell P793"
DisplaySize 320 240
HorizSync 30.0 - 96.0
VertRefresh 50.0 - 160.0
Option "dpms"
EndSection

Section "Monitor"
Identifier "aticonfig-Monitor[0]"
Option "VendorName" "ATI Proprietary Driver"
Option "ModelName" "Generic Autodetecting Monitor"
Option "DPMS" "true"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "vesa"
VendorName "Videocard vendor"
BoardName "ATI Technologies Inc Unknown device 7120"
EndSection

Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 16
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "Screen"
Identifier "aticonfig-Screen[0]"
Device "aticonfig-Device[0]"
Monitor "aticonfig-Monitor[0]"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Section "DRI"
Group 0
Mode 0666
EndSection