Arch Linux

Hiperi0n

Member

Registered: 2008-06-17

Posts: 49

TTYs go dark after testing X with xf86-video-ati

TTYs go dark after testing X with xf86-video-ati driver. When I press ctrl-alt-bckspace to return to tty, everything is extremely dark. I am using a CRT monitor but the problem is not the brightness, the colors are like very off. That doesn't happen with the vesa driver. I have a Radeon 7000 64mb, and AFAIK I should be using the free ati driver. I am following the beginner's guide to configure arch, but I am stuck at that point. I could ignore it but I think the ati driver is the only one that gives me 1024x768 @ 85hz (best for my poor eyes), and enable acceleration.

Any idea? Should I go on with ati driver? I am concerned that I might not be able to see clearly TTY should I need to quit X...

This is my xorg.conf:

Section "ServerLayout"
    Identifier     "X.org Configured"
    Screen      0  "Screen0" 0 0
    InputDevice    "Mouse0" "CorePointer"
    InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
    RgbPath      "/usr/share/X11/rgb"
    ModulePath   "/usr/lib/xorg/modules"
    FontPath     "/usr/share/fonts/misc"
    FontPath     "/usr/share/fonts/100dpi:unscaled"
    FontPath     "/usr/share/fonts/75dpi:unscaled"
    FontPath     "/usr/share/fonts/TTF"
    FontPath     "/usr/share/fonts/Type1"
EndSection

Section "Module"
    Load  "record"
    Load  "glx"
    Load  "extmod"
    Load  "dbe"
    Load  "xtrap"
    Load  "GLcore"
    Load  "dri"
    Load  "freetype"
EndSection

Section "InputDevice"
    Identifier  "Keyboard0"
    Driver      "kbd"
EndSection

Section "InputDevice"
    Identifier  "Mouse0"
    Driver      "mouse"
    Option        "Protocol" "auto"
    Option        "Device" "/dev/input/mice"
    Option        "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
    Identifier   "Monitor0"
    VendorName   "Monitor Vendor"
    ModelName    "Monitor Model"
EndSection

Section "Device"
        ### Available Driver options are:-
        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
        ### [arg]: arg optional
        #Option     "ShadowFB"               # [<bool>]
        #Option     "DefaultRefresh"         # [<bool>]
        #Option     "ModeSetClearScreen"     # [<bool>]
    Identifier  "Card0"
    Driver      "vesa"
    VendorName  "ATI Technologies Inc"
    BoardName   "Radeon RV100 QY [Radeon 7000/VE]"
    BusID       "PCI:1:0:0"
EndSection

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

Section "Extensions"
    Option "Composite" "Enable"
EndSection

portwolf

Member

Registered: 2008-09-09

Posts: 9

Re: TTYs go dark after testing X with xf86-video-ati

I have the same problems here! I am using the opensource drivers too, and i have to say thats really annoying does anyone know how to fix this?

jerryluc

Member

From: Norway

Registered: 2008-05-20

Posts: 95

Re: TTYs go dark after testing X with xf86-video-ati

BUMP

I have the same problem.

PS: is "bump" the right thing to say?

Lux Perpetua

Member

From: The Local Group

Registered: 2009-02-22

Posts: 69

Re: TTYs go dark after testing X with xf86-video-ati

1. Dumb question: you've tried degaussing your monitors, right?

2. The xorg.conf posted by the OP (> 8 months ago) seems to use the vesa driver, not xf86-video-ati as the OP claims. To use the open source ati driver, the "Device" section should have the line

        Driver      "radeon"

(not "vesa"). I have no idea whether this applies to the more recent posters, since they didn't say anything specific.

3. Regarding "bump," I don't think it really matters what you call it as long as you give specific details about the problem (which you didn't ).