Announcement

Collapse
No announcement yet.

Problem: Black screen when I reboot after driver install

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Problem: Black screen when I reboot after driver install

    I have a problem trying to use the latest ATI Catalist driver in Red Hat Linux Enterprise 5.1. I've installed the driver and configured the Xorg, but when I restart the system, it stops in a black screen and the system gets locked. I have followed step by step all the instructions and the ati web page, and I have also checked if the driver is ok (when i try the module using "modprobe fglrx" I don't find any problem), so I don't have any idea where the problem can be...
    Jordi

    PS:I've tried with different versions of the catalist driver (from 8.3 to 8.6) and I have the same problem with all of them



    Here's my configuration:
    DELL OptiPlex 755 Minitower (Nseries)
    Intel? Core? 2 Duo Processor E6550 (2.33GHz, 4M, VT, 1333MHz FSB),
    4GB DDR2 Non-ECC SDRAM,667MHz, (2 DIMM)
    256MB ATI Radeon 2400 XT
    --------------------------------------------------------------------------------------------------------
    01:00.0 VGA compatible controller: ATI Technologies Inc Radeon HD 2400 XT
    --------------------------------------------------------------------------------------------------------
    Linux aaa.bbb.cc 2.6.18-92.1.6.el5 #1 SMP Fri Jun 20 02:36:06 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
    --------------------------------------------------------------------------------------------------------
    Created directory fglrx-install.JY3688
    Verifying archive integrity... All good.
    Uncompressing ATI Proprietary Linux
    ==================================================
    ATI Technologies Linux Driver Installer/Packager
    ==================================================
    Detected configuration:
    Architecture: x86_64 (64-bit)
    X Server: X.Org 7.1 and later releases 64-bit
    loki_setup: directory: (null)
    Removing temporary directory: fglrx-install.JY3688

    --------------------------------------------------------------------------------------------------------
    In the messages file I can see that the driver is loaded correctly...
    messages.1:Jun 27 16:40:09 siurana kernel: fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
    messages.1:Jun 27 16:40:09 siurana kernel: [fglrx] vendor: 1002 device: 94c1 count: 1
    messages.1:Jun 27 16:40:09 siurana kernel: [fglrx] Maximum main memory to use for locked dma buffers: 3665 MBytes.
    messages.1:Jun 27 16:40:09 siurana kernel: [fglrx] PAT is enabled successfully!
    messages.1:Jun 27 16:40:09 siurana kernel: [fglrx] module loaded - fglrx 8.50.3 [Jun 2 2008] with 1 minors
    messages.1:Jun 27 16:40:26 siurana kernel: [fglrx] Reserved FB block: Shared offset:0, size:1000000
    messages.1:Jun 27 16:40:26 siurana kernel: [fglrx] Reserved FB block: Unshared offset:ff7b000, size:80000
    messages.1:Jun 27 16:40:26 siurana kernel: [fglrx] Reserved FB block: Unshared offset:fffc000, size:4000


    --------------------------------------------------------------------------------------------------------
    # Xorg configuration created by system-config-display

    Section "ServerLayout"
    Identifier "Multihead layout"
    Screen 0 "aticonfig-Screen[0]-0" 0 0
    InputDevice "Keyboard0" "CoreKeyboard"
    Option "Xinerama" "off"
    Option "Clone" "on"
    EndSection

    Section "Files"
    EndSection

    Section "Module"
    EndSection

    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    Option "XkbModel" "pc105"
    Option "XkbLayout" "us"
    EndSection

    Section "Monitor"

    ### Comment all HorizSync and VertSync values to use DDC:
    ### Comment all HorizSync and VertSync values to use DDC:
    Identifier "Monitor1"
    VendorName "Monitor Vendor"
    ModelName "LCD Panel 1280x1024"
    HorizSync 31.5 - 64.0
    VertRefresh 56.0 - 65.0
    Option "dpms"
    EndSection

    Section "Monitor"

    ### Comment all HorizSync and VertSync values to use DDC:
    Identifier "Monitor1"
    VendorName "Monitor Vendor"
    ModelName "LCD Panel 1600x1200"
    HorizSync 31.5 - 74.7
    VertRefresh 56.0 - 65.0
    Option "dpms"
    EndSection

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

    Section "Device"
    Identifier "Videocard0"
    Driver "radeon_tp"
    EndSection

    Section "Device"
    Identifier "Videocard1"
    Driver "radeon_tp"
    VendorName "Videocard Vendor"
    BoardName "ATI Technologies Inc Radeon HD 2400 XT"
    BusID "PCI:1:0:0"
    Screen 1
    EndSection

    Section "Device"
    Identifier "aticonfig-Device[0]-0"
    Driver "fglrx"
    BusID "PCI:1:0:0"
    EndSection

    Section "Screen"
    Identifier "Screen0"
    Device "Videocard0"
    DefaultDepth 24
    SubSection "Display"
    Viewport 0 0
    Depth 24
    Modes "1280x1024" "1280x960" "1280x800" "1152x864" "1024x768" "800x600" "640x480"
    EndSubSection
    EndSection

    Section "Screen"
    Identifier "Screen1"
    Device "Videocard1"
    Monitor "Monitor1"
    DefaultDepth 24
    SubSection "Display"
    Viewport 0 0
    Depth 24
    Modes "1280x1024"
    EndSubSection
    EndSection

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

  • #2
    I?ve beeninvestigating a little bit more and seems that the problem could be related with having 4Gb of RAM. I've been trying to disable the mmtr but the system still does block when it tries to load the Xwindows

    Comment


    • #3
      I have the same problem when I have at least 4GB of RAM in my system. It is a BIOS issue or a Linux kernel issue, fglrx is only one of many things affected. I also had corruption reading CDs or my USB flash drive. Try taking out a stick of RAM to see if that fixes the problem. If that is the case, you can work on fixing the MTRR issues.

      Comment


      • #4
        Originally posted by Chris Clearwater View Post
        ...If that is the case, you can work on fixing the MTRR issues.
        This is a handy post if you are not sure how to mess with the mtrr.

        Comment

        Working...
        X