[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#443570: xserver-xorg-video-ati: Old version in experimental...



On Sat, Sep 22, 2007 at 05:55:20PM +0200, Brice Goglin wrote:

> Can you try removing (or commenting out) some lines in xorg.conf as
> explained below?

Sorry about the mailbomb...

> HorizSync and the whole Mode subsection.
> All "Modes" line.

Changing these without changing anything else had no effect.

> > (WW) ****INVALID IO ALLOCATION**** b: 0xf0000400 e: 0xf00004ff correcting
> > (EE) end of block range 0xefffffff < begin 0xf0000000

> I don't like that. We've seen this several times but I never understood
> what caused it.

It's always happened on this system as far as I can remember.  My money
would be on the firmware being silly when initialising but that's just a
guess.

> That's the main problem, the driver does not detect your monitor at all.
> How is your monitor plugged?

It's on a DVI connection.  The machine is a Mac Mini:

processor	: 0
cpu		: 7447A, altivec supported
clock		: 1499.999994MHz
revision	: 0.2 (pvr 8003 0102)
bogomips	: 82.94
timebase	: 41600571
platform	: PowerMac
machine		: PowerMac10,2
motherboard	: PowerMac10,2 MacRISC3 Power Macintosh 
detected as	: 287 (Unknown Intrepid-based)
pmac flags	: 00000000
L2 cache	: 512K unified
pmac-generation	: NewWorld

(I'd suggest including /proc/cpuinfo in your bug script for PowerPC
since it gives an exact model).

> Driver 6.7.192 has a new option for Mac machines (to be added to the
> Device section). From the manpage:
>        Option "MacModel" "string"
>               Used to specify Mac models for connector tables and
> quirks.  Only valid on PowerPC.
>               ibook                -- ibooks
>               powerbook-duallink   -- Powerbooks with dual link DVI
>               powerbook            -- Powerbooks with single link DVI
>               The default value is undefined.

> Can you try playing with it?

I tried all of these modes.  They all appeared to produce identical
results, correctly identifying the resolution of my screen with no modes
specified but putting the monitor into power saving mode as per my
original report.  They all think it's on the LVDS port and that the port
reported as the DVI port is disconnected.

-- 
"You grabbed my hand and we fell into it, like a daydream - or a fever."




Reply to: