Bug 2159

Summary:	Black screen with ati rage mobility on Dell Inspiron 7500
Product:	xorg	Reporter:	David Yerger <davidy>
Component:	Driver/mach64	Assignee:	Xorg Project Team <xorg-team>
Status:	RESOLVED INVALID	QA Contact:
Severity:	critical
Priority:	high	CC:	erik.andren, mcumings
Version:	6.8.1
Hardware:	x86 (IA32)
OS:	OpenBSD
Whiteboard:
i915 platform:		i915 features:
Bug Depends on:	1109
Bug Blocks:

Description David Yerger 2004-12-27 09:18:13 UTC

Same as bug #1109, but on OpenBSD.

No workaround on this platform that I know of exists, unlike for Linux and FreeBSD.

I'm throwing this in because it looked to me that either the bug wasn't fixed
(just a workaround suggested for the Linux platform) or it was fixed for Radeon
(bug #1881), but that wouldn't help me because the chip in an Inspiron 7500 is
an ATi Rage Mobility P.

I can test any patches you suggest, or if you think there may be a section in
the Mach64 driver similar to the radeon driver patched in bug #1881 I can look
for it and patch accordingly.

Thanks

Comment 1 David Yerger 2005-01-23 14:51:00 UTC

I tried to debug this a bit, but I'm having trouble - 

I get "exceeds panel dimensions" for *every* resolution in Xorg.0.log, reason
being MODE_PANEL is being thrown in xf86ValidateModes().

Which leads me to believe that for some reason, xf86ValidateModes() 
or more specifically xf86InitialCheckModeForDriver(), line 1620
somehow forgot that the panel size was 1400x1050.

Now, that message apparently would originate ATIValidMode() in ativalid.c, line
103 or 109 as far as I can tell, but when I try to get what it thinks the panel
resolution is at that point with some ErrorF()s, id doesn't seem to be making
its way into the driver.

So, maybe ATIValidMode() isn't being compiled into the driver?

Found some info that suggests that missing/wrong video BIOS information may be
the culprit, please see  http://mgalug.org/suse/9.2.

I'd be more than happy to try anything you'd suggest.

Comment 2 David Yerger 2005-01-26 11:59:06 UTC

This MIGHT be the same bug as bug #591 per Marc La France, see
http://www.spinics.net/lists/xfree86/msg09134.html, but I tried
hand-hacking ativga.c per XFree86 CHANGELOG 133, didn't seem to help.  I didn't
make World, just atimisc_drv.o.  Maybe I'll try that later.

Comment 3 Mike Cumings 2005-01-27 10:02:58 UTC

I'm also experiencing this problem on Linux.  The workarounds that I've
been able to find via Google all seem to be ineffective (aside from switching
to the VESA driver, whcih only gets me to 1280x1024).  I can also provide
system access and test runs if desired.

Comment 4 David Yerger 2005-02-10 10:28:52 UTC

Maybe also see changelog 312 for XFree86 CVS, http://www.mail-archive.com/cvs-
commit@xfree86.org/msg04183.html

Couldn't compile the XFree86 4.4.99.901 snapshot on OpenBSD, so I can't say
whether this is the same bug or not.

Comment 5 David Yerger 2005-02-21 11:20:27 UTC

Was able to compile XFree86 4.4.99.901 last night, and the problem was fixed,
so it must have been fixed by changelog 312 or (changelog 133 and changelog 312).

The patch for changelog 312 was pretty small, I will probably try to 
port it over and send a diff in the next two weeks or so if nobody
else beats me to it.

Comment 6 Chris Lee 2005-07-03 19:26:27 UTC

There is a patch attached to bug #1109, can you see if that fixes the issue 
for you?

Comment 7 David Yerger 2005-07-15 01:31:02 UTC

Hard drive this was on blew up, so I don't have OpenBSD on that system any
more but I intend to, so I'll let you know

Thanks

Comment 8 Erik Andren 2006-04-03 02:52:18 UTC

Have you been able to test this issue yet?

Comment 9 Erik Andren 2006-04-27 07:10:22 UTC

Closing this due to the lack of activity. If the problem still persits, please
reopen.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.