Page 1 of 2 12 LastLast
Results 1 to 10 of 27

Thread: HELP!!! FGLRX causing screen hardlocks

Hybrid View

  1. #1
    Join Date
    Jun 2007
    Posts
    69

    Unhappy HELP!!! FGLRX causing screen hardlocks

    My problem is unique, and no one has been of any help so far. I have tried posting in fedora forum as well as other linux forums. I own a MSI X1800 XT (Model RX1800XT-VT-2D-512E) 512 MB graphics card. Versions upto 8.32.5 of fglrx run without a hitch on it. Versions from 8.33.6 onwards always result in a black screen upon reboot, and the system hangs. I cant even press Ctrl+Alt+F4/F1 etc. to get in to the console. I have tried all versions till the latest 8.37.6. The problem is not unique to fedora alone, as the same problem creeps up even if I use OpenSuse, Ubuntu or any other distro. The problem is newer kernels require newer fglrx versions, and so I am unable to get hardware acceleration in any of the new kernel ( 2.6.19 onwards) based distros.

    My configuration is as follows:

    AMD Athlon 64 3200+ Venice
    Gigabyte GA-K8N51-GMF9 Motherboard (Nforce 430/Geforce 6100)
    1 GB DDR400 RAM
    MSI X1800XT 512 MB graphics
    Cooler master 600W PSU
    Samsung Syncmaster 793s 17" CRT display
    OS: Fedora core 6 x86, Ubuntu Feisty fawn x64

    I have tried doing the following:-

    1. Manually running the .run file, building rpms/debs with the --Fedora/FC6 option and then editing xorg.conf and disabling composite extension to get DRI.
    2. Downloading pre-built kernel modules from livna using yum
    3. Using apt to download restricted drivers in ubuntu feisty fawn

    All drivers from 8.33.6 to 8.37.6 just cause the same problem on restart. The xorg.0.log shows some DRM module error. Please help me.

    Regards,

    Karthik Ramgopal
    India

  2. #2

    Default

    You should check the /var/log for kernel logs. I think fglrx may have caused a kernel panic.

    That's probably the only thing I can surmise from this.

  3. #3
    Join Date
    Jun 2007
    Location
    .ro/.ca
    Posts
    232

    Default

    It may be that your X Server crashes without restoring your display. It should return to the console even though you can't see it, so try for example "shutdown -r now" or ssh from a different computer. You may also want to try "RSEISUB" (hold alt+sysrq while typing rseisub) if your kernel is compiled with Magic SysRq support (which, as far as I know, doesn't work after a kernel panic).

    Even is this is not the case, you'll have to post your whole Xorg.log, and check that syslog like niniendowarrior said.
    Last edited by Xipeos; 06-20-2007 at 02:32 AM.

  4. #4
    Join Date
    Jun 2007
    Posts
    69

    Default

    here i am attaching part of my xorg log where the error occurs.. its on ubuntu 7.04 with the apt restricted fglrx drivers... and yes i hav tried ssh/telnet/ftp etc.. the computer does not respond at all and the connection times out..

    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is -1, (No such device or address)
    drmOpenDevice: open result is -1, (No such device or address)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 7, (OK)
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 7, (OK)
    drmGetBusid returned ''

    please help..

    regards,

    Karthik

  5. #5
    Join Date
    Jun 2007
    Location
    .ro/.ca
    Posts
    232

    Default

    Quote Originally Posted by karthikrg View Post
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is -1, (No such device or address)
    drmOpenDevice: open result is -1, (No such device or address)
    drmOpenDevice: Open failed
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 7, (OK)
    drmOpenDevice: node name is /dev/dri/card0
    drmOpenDevice: open result is 7, (OK)
    drmGetBusid returned ''
    That's not an error, just DRM pooling all ports for a video card (noticed that it says OK?)

    I doubt anyone can help you unless you give more info (as before, post or check the logs yourself). Try "grep EE Xorg.log" for errors or WW for warnings (credits to lenrek).
    Last edited by Xipeos; 06-20-2007 at 04:47 AM.

  6. #6
    Join Date
    Jun 2007
    Posts
    69

    Default

    But there is no option to attach files.. []

    I have tarred my xorg.conf as well as xorg.0.log as one file. The problem is how to send it 2 u?

  7. #7

    Default

    Quote Originally Posted by Xipeos View Post
    ... Try "grep EE Xorg.log" for errors or WW for warnings (credits to lenrek).
    LOL...

    If we do

    Code:
    # head -20 /var/log/Xorg.0.log
     Window System Version 6.9.0
    Release Date: 21 December 2005
    X Protocol Version 11, Revision 0, Release 6.9
    Build Operating System: Linux 2.6.18.8-smp i686 [ELF] 
    Current Operating System: Linux virgo 2.6.22-rc4 #1 Wed Jun 6 12:09:39 SGT 2007 i686
    Build Date: 19 April 2007
            Before reporting problems, check http://wiki.X.Org
            to make sure that you have the latest version.
    Module Loader present
    Markers: (--) probed, (**) from config file, (==) default setting,
            (++) from command line, (!!) notice, (II) informational,
            (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jun 20 11:50:06 2007
    (==) Using config file: "/etc/X11/xorg.conf"
    (==) ServerLayout "X.org Configured"
    (**) |-->Screen "aticonfig-Screen[0]" (0)
    (**) |   |-->Monitor "Monitor0"
    (**) |   |-->Device "Card0"
    (**) |-->Input Device "Mouse0"
    The "Markers" information already stated there. I don't think I can claim credits for that...

  8. #8
    Join Date
    Jun 2007
    Posts
    69

    Default

    http://pastebin.com/932446 --> xorg.conf
    http://pastebin.com/932444 --> xorg.0.log

    Links to the conf files.

    Regards,
    Karthik

  9. #9
    Join Date
    Jun 2007
    Posts
    69

    Default

    http://ati.cchtml.com/show_bug.cgi?id=567

    I believe that a similar problem has already been filed on ATI bugzilla and is open since long.

  10. #10

    Default

    Wow... The first complaint was at Jan2007. We are now in mid June2007. It is still not fix yet...

    That just shows of how good is ATI supporting Linux...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •