Bug#412228: xserver-xorg-video-ati: fails to start and nearly hangs machine

[Brice Goglin]

Mario Frasca wrote:
>> Also, you could eventually try with the "radeon" driver instead of ati,
>> it makes a difference, sometimes.
>>     
>
> well, it does make a difference, but not in positive sense.
> if I put the line:
>
>   Driver "radeon"
>
> I just get this in my log:
>
> (==) Log file: [...]
> (==) Using config file: [...]
> (EE) No devices detected.
>   

You have a r128 board. So "radeon" cannot help. I should have said
"r128" instead.

> Section "Module"
> 	Load	"bitmap"
> 	Load	"dbe"
> 	Load	"ddc"
> 	Load	"dri"
> 	Load	"extmod"
> 	Load	"freetype"
> 	Load	"glx"
> 	Load	"int10"
> 	#Load	"pex5"
> 	Load	"record"
> 	Load	"type1"
> 	Load	"vbe"
> 	#Load	"xie"
> EndSection
>   

Could you try without "dri" ?

> Section "Device"
> 	Identifier	"Generic Video Card"
> 	Driver		"ati"
> 	#Driver		"fbdev"
> 	BusID		"PCI:0:16:0"
> 	Option		"UseFBDev"	"true"
> 	#Option		"AGPMode" 	"4"
> EndSection
>   

Could you try without "UseFBDev" "true" ?

> Section "Monitor"
> 	Identifier	"Generic Monitor"
> 	HorizSync	59-63
> 	VertRefresh	43-95
> 	Option		"DPMS"
> # Modeline "1024x768" 80.50 1024 1060 1156 1348 768 781 784 820 +hsync +vsync
>   Modeline "1024x768" 80.50 1024 1052 1148 1348 768 777 780 812 +hsync +vsync
>   ModeLine "640x480" 49.9 640 653 717 832 480 481 484 514 +hsync +vsync
>   Modeline "800x600" 62.40 800 825 905 1040 600 601 604 632 +hsync +vsync 
> EndSection
>   

That's probably not causing your problem here, but do you really need
these Modeline, HorizSync and VertRefresh lines ?

> (II) Loading sub module "r128"
> (II) LoadModule: "r128"
> (II) Loading /usr/lib/xorg/modules/drivers/r128_drv.so
> (II) Module r128: vendor="X.Org Foundation"
> 	compiled for 7.1.1, module version = 4.1.0
> 	Module class: X.Org Video Driver
> 	ABI class: X.Org Video Driver, version 1.0
> (WW) ****INVALID IO ALLOCATION**** b: 0xf0000400 e: 0xf00004ff correcting
> (EE) end of block range 0xefffffff < begin 0xf0000000
>   

Not sure how bad this one is...

> (II) Attempted to read BIOS 64KB from /sys/bus/pci/devices/0000:00:10.0/rom: got 0KB
> (WW) R128(0): Video BIOS not detected in PCI space!
> (WW) R128(0): Attempting to read Video BIOS from legacy ISA space!
> (WW) R128(0): Video BIOS not found!
> (II) R128(0): Primary Display == Type 3
> (WW) R128(0): Can't determine panel dimensions, and none specified.
> 	Disabling programming of FP registers.
>   

Not sure either...

> (EE) R128(0): R128CCEWaitForIdle: (DEBUG) CCE idle took i = 1025
> (EE) R128(0): Idle timed out, resetting engine...
> (EE) R128(0): R128CCEWaitForIdle: (DEBUG) CCE idle took i = 1025
> (EE) R128(0): Idle timed out, resetting engine...
> (EE) R128(0): R128CCEWaitForIdle: (DEBUG) CCE idle took i = 1025
> (EE) R128(0): Idle timed out, resetting engine...
> (EE) R128(0): R128CCEWaitForIdle: (DEBUG) CCE idle took i = 1025
> (EE) R128(0): Idle timed out, resetting engine..

There are multiple reports about this in google, most of them are
related to iMac machines or so.

2 years ago, it was claimed to be related to DRI. Disabling it as I said
above could help.

Brice