Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: X will not start with fglrx but will with vesa

  1. #11
    Join Date
    Nov 2007
    Posts
    17

    Default

    Quote Originally Posted by givemesugarr View Post
    what does your Xorg.0.log say?!
    Quote:
    Originally Posted by Compxpert View Post
    Try: cat /var/log/xorg.0.log | grep "(EE)"

    Tell me what that gives you if I'm right I think you also have the PreInitDAL problem.
    I wish. I removed the current log and then tried to start X. It didn't recreate the log.
    When i try to startx with fglrx as the driver, nothing is logged and no log gets created.

    here is my my Xorg.0.log when it works as vesa though.
    http://docs.google.com/Doc?id=ddqg3848_39gq5kw3cf

    sorry if i misunderstood you, i kind of figured you'd only want to see the log of fglrx and not vesa.

  2. #12
    Join Date
    Jun 2007
    Posts
    406

    Default

    Quote Originally Posted by agentc0re View Post
    When i try to startx with fglrx as the driver, nothing is logged and no log gets created.

    here is my my Xorg.0.log when it works as vesa though.
    http://docs.google.com/Doc?id=ddqg3848_39gq5kw3cf

    sorry if i misunderstood you, i kind of figured you'd only want to see the log of fglrx and not vesa.
    wow... it's the first time i get to hear that no log is generated. if it's so then what's the error reported by startx after it fails?

  3. #13
    Join Date
    Nov 2007
    Posts
    17

    Default

    So i have been searching the forums like crazy and came across a thread that someone said they had fixed their issue by lowering their bios agp from 256 to 128. i tried that and, now it works. X starts using fglrx.

    No, (EE)'s in the log but i did get a few warnings

    Code:
    (WW) fglrx(0): Option "DRI" is not used
    (WW) fglrx(0): Option "HWCursor" is not used
    (WW) fglrx(0): Option "RenderAccel" is not used
    (WW) fglrx(0): Option "CalcAlgorithm" is not used
    and
    Code:
    (WW) AIGLX: 3D driver claims to not support visual 0x23
    (WW) AIGLX: 3D driver claims to not support visual 0x24
    (WW) AIGLX: 3D driver claims to not support visual 0x25
    (WW) AIGLX: 3D driver claims to not support visual 0x26
    (WW) AIGLX: 3D driver claims to not support visual 0x27
    (WW) AIGLX: 3D driver claims to not support visual 0x28
    (WW) AIGLX: 3D driver claims to not support visual 0x29
    (WW) AIGLX: 3D driver claims to not support visual 0x2a
    (WW) AIGLX: 3D driver claims to not support visual 0x2b
    (WW) AIGLX: 3D driver claims to not support visual 0x2c
    (WW) AIGLX: 3D driver claims to not support visual 0x2d
    (WW) AIGLX: 3D driver claims to not support visual 0x2e
    (WW) AIGLX: 3D driver claims to not support visual 0x2f
    (WW) AIGLX: 3D driver claims to not support visual 0x30
    (WW) AIGLX: 3D driver claims to not support visual 0x31
    (WW) AIGLX: 3D driver claims to not support visual 0x32
    (WW) AIGLX: 3D driver claims to not support visual 0x33
    (WW) AIGLX: 3D driver claims to not support visual 0x34
    (WW) AIGLX: 3D driver claims to not support visual 0x35
    (WW) AIGLX: 3D driver claims to not support visual 0x36
    (WW) AIGLX: 3D driver claims to not support visual 0x37
    (WW) AIGLX: 3D driver claims to not support visual 0x38
    (WW) AIGLX: 3D driver claims to not support visual 0x39
    (WW) AIGLX: 3D driver claims to not support visual 0x3a
    (WW) AIGLX: 3D driver claims to not support visual 0x3b
    (WW) AIGLX: 3D driver claims to not support visual 0x3c
    (WW) AIGLX: 3D driver claims to not support visual 0x3d
    (WW) AIGLX: 3D driver claims to not support visual 0x3e
    (WW) AIGLX: 3D driver claims to not support visual 0x3f
    (WW) AIGLX: 3D driver claims to not support visual 0x40
    (WW) AIGLX: 3D driver claims to not support visual 0x41
    (WW) AIGLX: 3D driver claims to not support visual 0x42
    (WW) AIGLX: 3D driver claims to not support visual 0x43
    (WW) AIGLX: 3D driver claims to not support visual 0x44
    (WW) AIGLX: 3D driver claims to not support visual 0x45
    (WW) AIGLX: 3D driver claims to not support visual 0x46
    (WW) AIGLX: 3D driver claims to not support visual 0x47
    (WW) AIGLX: 3D driver claims to not support visual 0x48
    (WW) AIGLX: 3D driver claims to not support visual 0x49
    (WW) AIGLX: 3D driver claims to not support visual 0x4a
    (WW) AIGLX: 3D driver claims to not support visual 0x4b
    (WW) AIGLX: 3D driver claims to not support visual 0x4c
    (WW) AIGLX: 3D driver claims to not support visual 0x4d
    (WW) AIGLX: 3D driver claims to not support visual 0x4e
    (WW) AIGLX: 3D driver claims to not support visual 0x4f
    (WW) AIGLX: 3D driver claims to not support visual 0x50
    (WW) AIGLX: 3D driver claims to not support visual 0x51
    (WW) AIGLX: 3D driver claims to not support visual 0x52
    (WW) AIGLX: 3D driver claims to not support visual 0x53
    (WW) AIGLX: 3D driver claims to not support visual 0x54
    (WW) AIGLX: 3D driver claims to not support visual 0x55
    (WW) AIGLX: 3D driver claims to not support visual 0x56
    (WW) AIGLX: 3D driver claims to not support visual 0x57
    (WW) AIGLX: 3D driver claims to not support visual 0x58
    (WW) AIGLX: 3D driver claims to not support visual 0x59
    (WW) AIGLX: 3D driver claims to not support visual 0x5a
    (WW) AIGLX: 3D driver claims to not support visual 0x5b
    (WW) AIGLX: 3D driver claims to not support visual 0x5c
    (WW) AIGLX: 3D driver claims to not support visual 0x5d
    (WW) AIGLX: 3D driver claims to not support visual 0x5e
    (WW) AIGLX: 3D driver claims to not support visual 0x5f
    (WW) AIGLX: 3D driver claims to not support visual 0x60
    (WW) AIGLX: 3D driver claims to not support visual 0x61
    (WW) AIGLX: 3D driver claims to not support visual 0x62
    (WW) AIGLX: 3D driver claims to not support visual 0x63
    (WW) AIGLX: 3D driver claims to not support visual 0x64
    (WW) AIGLX: 3D driver claims to not support visual 0x65
    (WW) AIGLX: 3D driver claims to not support visual 0x66
    (WW) AIGLX: 3D driver claims to not support visual 0x67
    (WW) AIGLX: 3D driver claims to not support visual 0x68
    (WW) AIGLX: 3D driver claims to not support visual 0x69
    (WW) AIGLX: 3D driver claims to not support visual 0x6a
    (WW) AIGLX: 3D driver claims to not support visual 0x6b
    (WW) AIGLX: 3D driver claims to not support visual 0x6c
    (WW) AIGLX: 3D driver claims to not support visual 0x6d
    (WW) AIGLX: 3D driver claims to not support visual 0x6e
    (WW) AIGLX: 3D driver claims to not support visual 0x6f
    (WW) AIGLX: 3D driver claims to not support visual 0x70
    (WW) AIGLX: 3D driver claims to not support visual 0x71
    (WW) AIGLX: 3D driver claims to not support visual 0x72
    (II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/fglrx_dri.so

  4. #14
    Join Date
    Jun 2007
    Posts
    406

    Default

    Quote Originally Posted by agentc0re View Post
    So i have been searching the forums like crazy and came across a thread that someone said they had fixed their issue by lowering their bios agp from 256 to 128. i tried that and, now it works. X starts using fglrx.

    No, (EE)'s in the log but i did get a few warnings

    Code:
    (WW) fglrx(0): Option "DRI" is not used
    (WW) fglrx(0): Option "HWCursor" is not used
    (WW) fglrx(0): Option "RenderAccel" is not used
    (WW) fglrx(0): Option "CalcAlgorithm" is not used
    and
    Code:
    (WW) AIGLX: 3D driver claims to not support visual 0x23
    (WW) AIGLX: 3D driver claims to not support visual 0x24
    (WW) AIGLX: 3D driver claims to not support visual 0x25
    (WW) AIGLX: 3D driver claims to not support visual 0x26
    (WW) AIGLX: 3D driver claims to not support visual 0x27
    (WW) AIGLX: 3D driver claims to not support visual 0x28
    (WW) AIGLX: 3D driver claims to not support visual 0x29
    (WW) AIGLX: 3D driver claims to not support visual 0x2a
    (WW) AIGLX: 3D driver claims to not support visual 0x2b
    (WW) AIGLX: 3D driver claims to not support visual 0x2c
    (WW) AIGLX: 3D driver claims to not support visual 0x2d
    (WW) AIGLX: 3D driver claims to not support visual 0x2e
    (WW) AIGLX: 3D driver claims to not support visual 0x2f
    (WW) AIGLX: 3D driver claims to not support visual 0x30
    (WW) AIGLX: 3D driver claims to not support visual 0x31
    (WW) AIGLX: 3D driver claims to not support visual 0x32
    (WW) AIGLX: 3D driver claims to not support visual 0x33
    (WW) AIGLX: 3D driver claims to not support visual 0x34
    (WW) AIGLX: 3D driver claims to not support visual 0x35
    (WW) AIGLX: 3D driver claims to not support visual 0x36
    (WW) AIGLX: 3D driver claims to not support visual 0x37
    (WW) AIGLX: 3D driver claims to not support visual 0x38
    (WW) AIGLX: 3D driver claims to not support visual 0x39
    (WW) AIGLX: 3D driver claims to not support visual 0x3a
    (WW) AIGLX: 3D driver claims to not support visual 0x3b
    (WW) AIGLX: 3D driver claims to not support visual 0x3c
    (WW) AIGLX: 3D driver claims to not support visual 0x3d
    (WW) AIGLX: 3D driver claims to not support visual 0x3e
    (WW) AIGLX: 3D driver claims to not support visual 0x3f
    (WW) AIGLX: 3D driver claims to not support visual 0x40
    (WW) AIGLX: 3D driver claims to not support visual 0x41
    (WW) AIGLX: 3D driver claims to not support visual 0x42
    (WW) AIGLX: 3D driver claims to not support visual 0x43
    (WW) AIGLX: 3D driver claims to not support visual 0x44
    (WW) AIGLX: 3D driver claims to not support visual 0x45
    (WW) AIGLX: 3D driver claims to not support visual 0x46
    (WW) AIGLX: 3D driver claims to not support visual 0x47
    (WW) AIGLX: 3D driver claims to not support visual 0x48
    (WW) AIGLX: 3D driver claims to not support visual 0x49
    (WW) AIGLX: 3D driver claims to not support visual 0x4a
    (WW) AIGLX: 3D driver claims to not support visual 0x4b
    (WW) AIGLX: 3D driver claims to not support visual 0x4c
    (WW) AIGLX: 3D driver claims to not support visual 0x4d
    (WW) AIGLX: 3D driver claims to not support visual 0x4e
    (WW) AIGLX: 3D driver claims to not support visual 0x4f
    (WW) AIGLX: 3D driver claims to not support visual 0x50
    (WW) AIGLX: 3D driver claims to not support visual 0x51
    (WW) AIGLX: 3D driver claims to not support visual 0x52
    (WW) AIGLX: 3D driver claims to not support visual 0x53
    (WW) AIGLX: 3D driver claims to not support visual 0x54
    (WW) AIGLX: 3D driver claims to not support visual 0x55
    (WW) AIGLX: 3D driver claims to not support visual 0x56
    (WW) AIGLX: 3D driver claims to not support visual 0x57
    (WW) AIGLX: 3D driver claims to not support visual 0x58
    (WW) AIGLX: 3D driver claims to not support visual 0x59
    (WW) AIGLX: 3D driver claims to not support visual 0x5a
    (WW) AIGLX: 3D driver claims to not support visual 0x5b
    (WW) AIGLX: 3D driver claims to not support visual 0x5c
    (WW) AIGLX: 3D driver claims to not support visual 0x5d
    (WW) AIGLX: 3D driver claims to not support visual 0x5e
    (WW) AIGLX: 3D driver claims to not support visual 0x5f
    (WW) AIGLX: 3D driver claims to not support visual 0x60
    (WW) AIGLX: 3D driver claims to not support visual 0x61
    (WW) AIGLX: 3D driver claims to not support visual 0x62
    (WW) AIGLX: 3D driver claims to not support visual 0x63
    (WW) AIGLX: 3D driver claims to not support visual 0x64
    (WW) AIGLX: 3D driver claims to not support visual 0x65
    (WW) AIGLX: 3D driver claims to not support visual 0x66
    (WW) AIGLX: 3D driver claims to not support visual 0x67
    (WW) AIGLX: 3D driver claims to not support visual 0x68
    (WW) AIGLX: 3D driver claims to not support visual 0x69
    (WW) AIGLX: 3D driver claims to not support visual 0x6a
    (WW) AIGLX: 3D driver claims to not support visual 0x6b
    (WW) AIGLX: 3D driver claims to not support visual 0x6c
    (WW) AIGLX: 3D driver claims to not support visual 0x6d
    (WW) AIGLX: 3D driver claims to not support visual 0x6e
    (WW) AIGLX: 3D driver claims to not support visual 0x6f
    (WW) AIGLX: 3D driver claims to not support visual 0x70
    (WW) AIGLX: 3D driver claims to not support visual 0x71
    (WW) AIGLX: 3D driver claims to not support visual 0x72
    (II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/fglrx_dri.so
    so in the end the log wasn't generated because xorg wouldn't even be started. it seems that setting the agp aperture = to the one that fglrx detects doesn't work. i think that this a pretty nasty bug....
    these warnings are normal; the first ones are unused options, while the others are unsupported aiglx features. they get on anyone who uses aiglx.

  5. #15
    Join Date
    Nov 2007
    Posts
    17

    Default

    Quote Originally Posted by givemesugarr View Post
    wow... it's the first time i get to hear that no log is generated. if it's so then what's the error reported by startx after it fails?
    I wouldn't get anything. I would let it sit for about 10 min before i was forced to do a restart. Before that i was just starring at a blank screen.

    Im happy that it's working though, even if i don't get my full 1680x1050 resolution. I can already see an improvement within KDE.

    On a side note, I was wondering if you could shed some light on a few of the xorg.conf options you gave to me. or at least point me to the right man page where i can read about it.

    Code:
    Section "Modes"
      Identifier "Modes[1]"
    EndSection
    Code:
            UseModes     "Modes[0]"
            Option       "CalcAlgorithm" "XServerPool"
    My guess is that it auto finds all the modes you can display and chooses the most compatible?? If thats true then do i need my modes section in the Screen section?

  6. #16
    Join Date
    Nov 2007
    Posts
    17

    Default

    Quote Originally Posted by givemesugarr View Post
    so in the end the log wasn't generated because xorg wouldn't even be started. it seems that setting the agp aperture = to the one that fglrx detects doesn't work. i think that this a pretty nasty bug....
    these warnings are normal; the first ones are unused options, while the others are unsupported aiglx features. they get on anyone who uses aiglx.
    I'm posting the bug report now.

  7. #17
    Join Date
    Jun 2007
    Posts
    406

    Default

    Quote Originally Posted by agentc0re View Post
    I wouldn't get anything. I would let it sit for about 10 min before i was forced to do a restart. Before that i was just starring at a blank screen.

    Im happy that it's working though, even if i don't get my full 1680x1050 resolution. I can already see an improvement within KDE.

    On a side note, I was wondering if you could shed some light on a few of the xorg.conf options you gave to me. or at least point me to the right man page where i can read about it.

    Code:
    Section "Modes"
      Identifier "Modes[1]"
    EndSection
    Code:
            UseModes     "Modes[0]"
            Option       "CalcAlgorithm" "XServerPool"
    My guess is that it auto finds all the modes you can display and chooses the most compatible?? If thats true then do i need my modes section in the Screen section?
    the modes section is used to define personal modelines and for specifying complete modelines. for example the following is a modeline:

    Code:
    Modeline "1280x800"  83.46  1280 1344 1480 1680  800 801 804 828  -HSync +Vsync
    the modeline indicates everything about a screen mode: - first it sets the resolution
    - then there is the horizontal refresh rate (the following 4 numbers)
    - then the vertical one
    - in the end the type of refresh
    you could also specify non standard screen modes like 7:4 or any other stuff that passes by your mind with it.

    the screen section instead sets the possible modes for the various types of color bit.

    as for the calcalgorithm, for what i know, that option is used to tell xorg how to apply the modelines and shouldn't be read if you don't use them. more specifically, if you take a look into your xorg log you'll find that that option isn't used. for what i know it's not documented and behaves different if you specify different types of options (checkdesktopgeometry for example would always check for a display connected and use only the modes that apply to the geometry of the monitor or "UseFrameBufferTiming" is used when using fb devices). it should be deprecated now since everything is read from edid, but i have it there and it doesn't do any harm. also it should be useful, as the modes section if you want to connect the board to an external tv that isn't a new lcd or that transmits a wrong edid to the board.
    let's just say that a usual person who uses an lcd monitor won't need these options.
    well, if someone knows more about these options and wants to contribute is welcome to answer.

Posting Permissions

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