From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems
with (U)EFI boot
Date: Fri, 03 Aug 2012 18:49:14 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
Received: from culpepper.freedesktop.org (unknown [131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id 0A5FBA0F80
for ;
Fri, 3 Aug 2012 11:49:15 -0700 (PDT)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=26891
--- Comment #26 from David L. 2012-08-03 18:49:14 UTC ---
Created attachment 65100
--> https://bugs.freedesktop.org/attachment.cgi?id=65100
hacked-up radeon VFCT BIOS access patch
So the good news is that a VFCT ACPI table does indeed show up when I boot
under UEFI native mode on the HP EliteBook.
I hacked up some code to get the BIOS from there and it successfully brought up
the card and drove my DisplayPort screen. (hack patch attached)
The bad news is that the LVDS panel first went backlight-off, on starting X
started displaying flickering pixelgarbage and at some later point the entire
box locked up.
I'll go diff the BIOS images against each other, maybe the BIOS from VFCT is
corrupted...
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.