X will not start with fglrx but will with vesa

[agentc0re]

uname -a
Linux 2.6.21.5-smp #2 SMP Tue Jun 19 14:58:11 CDT 2007 i686 AMD Athlon(tm) 64 Processor 3400+ AuthenticAMD GNU/Linux

Video card i have is the X1950pro AGP 512mb (Sapphire)
My monitors are 2005fpw dell 20.1" widescreen that support 1650x1080 (i have 2)

when i ran the ati installer, i did it as root and in runlevel 3 @ CLI. all my tests so far have been under root as well until i can figure out what is going on.

My bios is set to 256mb agp aperture.

7.11 did work (well work i mean, X started) 7.12 does not. When i changed driver from fglrx to vesa, X does start so i don't think it's my xorg.

xorg.conf

Section "ServerLayout"
Identifier "Simple Layout"
Screen 0 "aticonfig-Screen[0]" 0 0
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection

Section "Files"
RgbPath "/usr/share/X11/rgb"
FontPath "/usr/share/fonts/local/"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/OTF/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/Speedo/"
FontPath "/usr/share/fonts/75dpi/:unscaled"
FontPath "/usr/share/fonts/100dpi/:unscaled"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/cyrillic/"
EndSection

Section "Module"
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "type1"
Load "freetype"
#Load "speedo"
Load "glx"
Load "dri"
EndSection

Section "InputDevice"
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
Identifier "Keyboard1"
Driver "kbd"
EndSection

Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "PS/2"
Option "Device" "/dev/mouse"
EndSection

Section "Monitor"
Identifier "aticonfig-Monitor[0]"
Option "DPMS" "true"
EndSection

Section "Monitor"
Identifier "aticonfig-Monitor[1]"
Option "DPMS" "true"
EndSection

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

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

Section "Screen"
Identifier "aticonfig-Screen[0]"
Device "aticonfig-Device[0]"
Monitor "aticonfig-Monitor[0]"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 24
Modes "1650x1080" "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 32
Modes "1024x768" "800x600" "640x480"
EndSubsection

EndSection

Section "Screen"
Identifier "aticonfig-Screen[1]"
Device "aticonfig-Device[1]"
Monitor "aticonfig-Monitor[1]"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 24
Modes "1650x1080" "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 32
Modes "1024x768" "800x600" "640x480"
EndSubsection

EndSection


Am i missing something here that would stop X from starting? Weird thing too is that nothing gets logged as far as why it just sit's and hangs on starting X.

lsmod | grep fglrx
fglrx 1489004 0
agpgart 31432 2 fglrx,amd64_agp

lspci | grep ATI
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon X1950 Pro (Primary) (PCIE)
01:00.1 Display controller: ATI Technologies Inc Radeon X1950 Pro (Secondary) (PCIE)

[Dandel]

since i do not know which distribution you have, i'll haft to guess at config file locations, but if it's debian/ubuntu this should work...

does the following file exist?

/etc/X11/xorg.conf.original

if that file exists, copy it over your xorg config file.
otherwise, reinstall the xorg server, using your package manager.

[agentc0re]

since i do not know which distribution you have, i'll haft to guess at config file locations, but if it's debian/ubuntu this should work...

Sorry, I use Slackware 12


does the following file exist?

/etc/X11/xorg.conf.original

if that file exists, copy it over your xorg config file.
otherwise, reinstall the xorg server, using your package manager.

I tried that just now, and same thing as i described before. vesa works fine. when i try to change the driver in the xorg.conf from vesa to fglrx, X just hangs on starting up. I have also tried to run aticonfig --initial and i still have the same problem.
i'll post my xorg.conf.original.

http://docs.google.com/Doc?id=ddqg3848_38d3gx48f7

It was took long because of all the examples, so there's the link. the first xorg.conf is basically the original just with all that shit taken out and the second device section added.

[givemesugarr]

uname -a
Linux 2.6.21.5-smp #2 SMP Tue Jun 19 14:58:11 CDT 2007 i686 AMD Athlon(tm) 64 Processor 3400+ AuthenticAMD GNU/Linux

Video card i have is the X1950pro AGP 512mb (Sapphire)
My monitors are 2005fpw dell 20.1" widescreen that support 1650x1080 (i have 2)

when i ran the ati installer, i did it as root and in runlevel 3 @ CLI. all my tests so far have been under root as well until i can figure out what is going on.

My bios is set to 256mb agp aperture.

7.11 did work (well work i mean, X started) 7.12 does not. When i changed driver from fglrx to vesa, X does start so i don't think it's my xorg.


well, vesa is supported by all cards for what i know. for example when the hd series wasn't supported officially in fglrx these boards would run vesa to start xorg. so normally, putting vesa as driver should make your board work. the problem would have been if vesa wouldn't work. as for the resolution, your should not work anymore on 7.12. so i guess that it's best for you to keep on going with the 7.11.


xorg.conf

Section "ServerLayout"
Identifier "Simple Layout"
Screen 0 "aticonfig-Screen[0]" 0 0
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard[0]" "CoreKeyboard"
EndSection





Section "Module"
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "type1"
Load "freetype"
#Load "speedo"
Load "glx"
Load "dri"
EndSection


is the extmod option needed?! i don't have it and works without it. try removing all the subsection extmod and insert Load "extmod" in its place.
also set the following


Section "InputDevice"
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
Identifier "Keyboard1"
Driver "kbd"
EndSection


to

Section "InputDevice"
Driver "kbd"
Identifier "Keyboard[0]"
Option "Protocol" "Standard"
Option "XkbLayout" "us"
Option "XkbModel" "pc105"
Option "XkbRules" "xorg"
EndSection


also add the following:

Section "Modes"
Identifier "Modes[0]"
EndSection

Section "Modes"
Identifier "Modes[1]"
EndSection

Section "ServerFlags"
Option "AllowMouseOpenFail" "on"
Option "IgnoreABI" "on"
Option "AIGLX" "off"
EndSection

(if you want aiglx then set to on the option).
and substitute the monitor sections with the following:


Section "Monitor"
Identifier "aticonfig-Monitor[0]"
Option "DPMS" "true"
UseModes "Modes[0]"
Option "CalcAlgorithm" "XServerPool"
EndSection

Section "Monitor"
Identifier "aticonfig-Monitor[1]"
Option "DPMS" "true"
UseModes "Modes[1]"
Option "CalcAlgorithm" "XServerPool"
EndSection



and the device sections with:

Section "Device"
Identifier "aticonfig-Device[0]"
Driver "fglrx"
BusID "PCI:1:0:0"
Option "BusType" "AGP"
Option "BlockSignalsOnLock" "on"
Option "Capabilities" "0x00000000"
Option "CapabilitiesEx" "0x00000000"
Option "CenterMode" "off"
Option "DRI" "true"
Option "ForceGenericCPU" "no"
Option "HWCursor" "On"
Option "KernelModuleParm" "locked-userpages=0"
Option "mtrr" "off"
Option "no_accel" "no"
Option "no_dri" "no"
Option "OpenGLOverlay" "off"
Option "PseudoColorVisuals" "off"
Option "RenderAccel" "true"
Option "ScreenOverlap" "0"
Option "Stereo" "off"
Option "StereoSyncEnable" "1"
Option "UseFastTLS" "0"
Option "UseInternalAGPGART" "no"
Option "VideoOverlay" "on"
Option "XAANoOffscreenPixmaps" "true"
EndSection

Section "Device"
Identifier "aticonfig-Device[1]"
Driver "fglrx"
BusID "PCI:1:0:1"
Screen 1
Option "BusType" "AGP"
Option "BlockSignalsOnLock" "on"
Option "Capabilities" "0x00000000"
Option "CapabilitiesEx" "0x00000000"
Option "CenterMode" "off"
Option "DRI" "true"
Option "ForceGenericCPU" "no"
Option "HWCursor" "On"
Option "KernelModuleParm" "locked-userpages=0"
Option "mtrr" "off"
Option "no_accel" "no"
Option "no_dri" "no"
Option "OpenGLOverlay" "off"
Option "PseudoColorVisuals" "off"
Option "RenderAccel" "true"
Option "ScreenOverlap" "0"
Option "Stereo" "off"
Option "StereoSyncEnable" "1"
Option "UseFastTLS" "0"
Option "UseInternalAGPGART" "no"
Option "VideoOverlay" "on"
Option "XAANoOffscreenPixmaps" "true"
EndSection


the problem you might have is that you could also encounter some issues with both the monitors connected so try seeing what happens when you disconnect one of them and comment out the lines for the second monitor.
the other problem that you have is that your board is detected as pcie (old fglrx problem) and this could have you play around a little with the agpgart. the bustype option should have fglrx detect the board as an agp one and enable the agpgart and dri as it should by default, but the wrong bus type might have provoked some problem.
if everyhing goes fine then you can play around with big desktop options and similar stuff.
the next time look into the /var/log/Xorg.0.log after a black screen to see what error has occured. it could help out seeing if there was something wrong.
if you encounter problems post the xorg.0.log and we'll try figuring out the problem and how to best set-up also the monitors (the section lacks the refresh rates and the screen dimensions).

since i do not know which distribution you have, i'll haft to guess at config file locations, but if it's debian/ubuntu this should work...

does the following file exist?

/etc/X11/xorg.conf.original

if that file exists, copy it over your xorg config file.
otherwise, reinstall the xorg server, using your package manager.

this file should not be loaded. the one that is loaded by xorg is /etc/X11/xorg.conf and should be the same on all the distributions. the other xorg.conf.whatever files are just backup created by distro setting programs.
also, don't reinstall xorg!!!! is useless. when problems get out because of misconfigurations then they would be fixed after setting the configuration to the right one. also if you use gentoo the reinstall of the xorg packages would take quite some time.
remember that this is not windows on which when a program doesn't work you just reinstall it. usually in linux you first verify the configs and after setting them right if there's no other way of fixing things then you might consider reinstalling the package.

[liqor_mortis]

Just a minor point, you have 1650x1080 in the modes section. Shouldn't that be 1680x1050? I don't know if that would affect the xorg start though.

[Compxpert]

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.

[agentc0re]

Just a minor point, you have 1650x1080 in the modes section. Shouldn't that be 1680x1050? I don't know if that would affect the xorg start though.

Thank you for pointing that out. I always switch those two numbers for some reason.

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.

this file should not be loaded. the one that is loaded by xorg is /etc/X11/xorg.conf and should be the same on all the distributions. the other xorg.conf.whatever files are just backup created by distro setting programs.
also, don't reinstall xorg!!!! is useless. when problems get out because of misconfigurations then they would be fixed after setting the configuration to the right one. also if you use gentoo the reinstall of the xorg packages would take quite some time.
remember that this is not windows on which when a program doesn't work you just reinstall it. usually in linux you first verify the configs and after setting them right if there's no other way of fixing things then you might consider reinstalling the package.

I think he ment cp the xorg.conf.orig to xorg.conf to start from a fresh start or at least thats how i took it. However my xorg.conf was pretty much scratch to begin with.
I would also never reinstall the package, i know better than that :) However, i do appreciate the help offered Dandel.

I just made the changes to my xorg.conf, im going to try and restart X and see what happens. i'll post back with my results! :)

Thanks so far.

[agentc0re]

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.

[agentc0re]

Here is the current xorg.conf. i added a few things, just DRI and stuff at the end.

I tried unplugging one of the monitors and X still will not start. Maybe it has something to do with the fact they are reconnized as PCI-E even though they are AGP? i do know that the chipset is a PCI-E using the Realto chip to convert it to agp (i could be wrong but i think thats how it works) could that be why it says PCI-E too?

Section "ServerLayout"
Identifier "Simple Layout"
Screen 0 "aticonfig-Screen[0]" 0 0
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard[0]" "CoreKeyboard"
EndSection

Section "Files"
RgbPath "/usr/share/X11/rgb"
FontPath "/usr/share/fonts/local/"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/OTF/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/Speedo/"
FontPath "/usr/share/fonts/75dpi/:unscaled"
FontPath "/usr/share/fonts/100dpi/:unscaled"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/cyrillic/"
EndSection

Section "Module"
Load "dbe" # Double buffer extension
Load "type1"
Load "freetype"
Load "glx"
Load "dri"
EndSection

Section "Modes"
Identifier "Modes[0]"
EndSection

Section "Modes"
Identifier "Modes[1]"
EndSection

Section "ServerFlags"
Option "AllowMouseOpenFail" "on"
Option "IgnoreABI" "on"
Option "AIGLX" "on"
EndSection

Section "InputDevice"
Driver "kbd"
Identifier "Keyboard[0]"
Option "Protocol" "Standard"
Option "XkbLayout" "us"
Option "XkbModel" "pc105"
Option "XkbRules" "xorg"
EndSection

Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "PS/2"
Option "Device" "/dev/mouse"
EndSection

Section "Monitor"
Identifier "aticonfig-Monitor[0]"
Option "DPMS" "true"
UseModes "Modes[0]"
Option "CalcAlgorithm" "XServerPool"
EndSection

Section "Monitor"
Identifier "aticonfig-Monitor[1]"
Option "DPMS" "true"
UseModes "Modes[1]"
Option "CalcAlgorithm" "XServerPool"
EndSection

Section "Device"
Identifier "aticonfig-Device[0]"
Driver "vesa"
BusID "PCI:1:0:0"
Option "BusType" "AGP"
Option "BlockSignalsOnLock" "on"
Option "Capabilities" "0x00000000"
Option "CapabilitiesEx" "0x00000000"
Option "CenterMode" "off"
Option "DRI" "true"
Option "ForceGenericCPU" "no"
Option "HWCursor" "On"
Option "KernelModuleParm" "locked-userpages=0"
Option "mtrr" "off"
Option "no_accel" "no"
Option "no_dri" "no"
Option "OpenGLOverlay" "off"
Option "PseudoColorVisuals" "off"
Option "RenderAccel" "true"
Option "ScreenOverlap" "0"
Option "Stereo" "off"
Option "StereoSyncEnable" "1"
Option "UseFastTLS" "0"
Option "UseInternalAGPGART" "no"
Option "VideoOverlay" "on"
Option "XAANoOffscreenPixmaps" "true"
EndSection

Section "Device"
Identifier "aticonfig-Device[1]"
Driver "vesa"
BusID "PCI:1:0:1"
Screen 1
Option "BusType" "AGP"
Option "BlockSignalsOnLock" "on"
Option "Capabilities" "0x00000000"
Option "CapabilitiesEx" "0x00000000"
Option "CenterMode" "off"
Option "DRI" "true"
Option "ForceGenericCPU" "no"
Option "HWCursor" "On"
Option "KernelModuleParm" "locked-userpages=0"
Option "mtrr" "off"
Option "no_accel" "no"
Option "no_dri" "no"
Option "OpenGLOverlay" "off"
Option "PseudoColorVisuals" "off"
Option "RenderAccel" "true"
Option "ScreenOverlap" "0"
Option "Stereo" "off"
Option "StereoSyncEnable" "1"
Option "UseFastTLS" "0"
Option "UseInternalAGPGART" "no"
Option "VideoOverlay" "on"
Option "XAANoOffscreenPixmaps" "true"
EndSection

Section "Screen"
Identifier "aticonfig-Screen[0]"
Device "aticonfig-Device[0]"
Monitor "aticonfig-Monitor[0]"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 24
Modes "1680x1050" "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 32
Modes "1024x768" "800x600" "640x480"
EndSubsection

EndSection

Section "Screen"
Identifier "aticonfig-Screen[1]"
Device "aticonfig-Device[1]"
Monitor "aticonfig-Monitor[1]"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 24
Modes "1680x1050" "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 32
Modes "1024x768" "800x600" "640x480"
EndSubsection

EndSection

Section "DRI"
Mode 0666
EndSection

Section "Extensions"
Option "XVideo" "Enable"
Option "DAMAGE" "true"
Option "RENDER" "true"
Option "Composite" "Enable"
EndSection

[givemesugarr]

Here is the current xorg.conf. i added a few things, just DRI and stuff at the end.

I tried unplugging one of the monitors and X still will not start. Maybe it has something to do with the fact they are reconnized as PCI-E even though they are AGP? i do know that the chipset is a PCI-E using the Realto chip to convert it to agp (i could be wrong but i think thats how it works) could that be why it says PCI-E too?


what does your Xorg.0.log say?!

[agentc0re]

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.

[givemesugarr]

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?

[agentc0re]

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

(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
(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

[givemesugarr]

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

(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
(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.

[agentc0re]

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.

Section "Modes"
Identifier "Modes[1]"
EndSection


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?

[agentc0re]

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.

[givemesugarr]

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.

Section "Modes"
Identifier "Modes[1]"
EndSection


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:

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.