[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #65 from Austin Lund  ---
Works for me in 3.9-rc6.

As stated above, you cannot use grub to load the firmware as the information is
only accessible before you exit the boot services in EFI.  The kernel must be
booted using EFI stub booting (that's where the code for getting the bios image
is).  I use rEFInd as this now automaigcally passes the initramfs location to
the kernel.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #65 from Austin Lund  ---
Works for me in 3.9-rc6.

As stated above, you cannot use grub to load the firmware as the information is
only accessible before you exit the boot services in EFI.  The kernel must be
booted using EFI stub booting (that's where the code for getting the bios image
is).  I use rEFInd as this now automaigcally passes the initramfs location to
the kernel.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #64 from Luca Barbato  ---
The system is a macbookpro 8.2 and it fails to find the bios as reported
before. Probably the problem is in the grub configuration or in the kernel,
anybody with a working system could point me to and example configuration?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #63 from Luca Barbato  ---
I tested today and the problem is still present. Which is your .config and how
are you loading the kernel?

I'm trying to load it using grub2.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #64 from Luca Barbato  ---
The system is a macbookpro 8.2 and it fails to find the bios as reported
before. Probably the problem is in the grub configuration or in the kernel,
anybody with a working system could point me to and example configuration?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #63 from Luca Barbato  ---
I tested today and the problem is still present. Which is your .config and how
are you loading the kernel?

I'm trying to load it using grub2.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

Alex Deucher  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #62 from Alex Deucher  ---
At this point these are all core kernel changes being discussed and have
nothing to do with the radeon driver.  Closing.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #61 from Ludovic Watteaux  ---
Work again on Linux 3.9.0-rc6 without patch.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

Alex Deucher  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--- Comment #62 from Alex Deucher  ---
At this point these are all core kernel changes being discussed and have
nothing to do with the radeon driver.  Closing.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #61 from Ludovic Watteaux  ---
Work again on Linux 3.9.0-rc6 without patch.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #60 from Austin Lund  ---
It does look like commit 547b52463 did introduce the problem (tho I didn't
finish bisecting).

The patch set does fix the issue for me.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #59 from Alex Deucher  ---
Possibly fixed by this patch set:
https://patchwork.kernel.org/patch/2344041/

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #58 from Austin Lund  ---
This still doesn't work for 3.9-rc5.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #60 from Austin Lund  ---
It does look like commit 547b52463 did introduce the problem (tho I didn't
finish bisecting).

The patch set does fix the issue for me.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #59 from Alex Deucher  ---
Possibly fixed by this patch set:
https://patchwork.kernel.org/patch/2344041/

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #58 from Austin Lund  ---
This still doesn't work for 3.9-rc5.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #57 from Austin Lund  ---
I can confirm on my machine (macbookpro8,2) that v3.9-rc4 doesn't work and
v3.9-rc3 does work.

Looking at the changes in drivers/gpu/drm/radeon between these two versions
doesn't reveal anything that stands out as the culprit.  Does anyone want to
bisect?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #57 from Austin Lund  ---
I can confirm on my machine (macbookpro8,2) that v3.9-rc4 doesn't work and
v3.9-rc3 does work.

Looking at the changes in drivers/gpu/drm/radeon between these two versions
doesn't reveal anything that stands out as the culprit.  Does anyone want to
bisect?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #56 from Ludovic Watteaux  ---
Same here Linux 3.9.0-rc4
[5.800732] [drm] Initialized drm 1.1.0 20060810
[5.835989] [drm] radeon kernel modesetting enabled.
[5.839889] [drm] initializing kernel modesetting (TURKS 0x1002:0x6741
0x106B:0x00E2).
[5.840512] [drm] register mmio base: 0xB080
[5.840520] [drm] register mmio size: 131072
[5.840667] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
[5.840687] [drm] radeon: finishing device.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #56 from Ludovic Watteaux  ---
Same here Linux 3.9.0-rc4
[5.800732] [drm] Initialized drm 1.1.0 20060810
[5.835989] [drm] radeon kernel modesetting enabled.
[5.839889] [drm] initializing kernel modesetting (TURKS 0x1002:0x6741
0x106B:0x00E2).
[5.840512] [drm] register mmio base: 0xB080
[5.840520] [drm] register mmio size: 131072
[5.840667] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
[5.840687] [drm] radeon: finishing device.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #55 from Benjamin Lee  ---
This has regressed some time after 3.9-rc2.  I haven't tried 3.9-rc3 but it is
definitely not working anymore in 3.9-rc4:

[2.603538] [drm] initializing kernel modesetting (TURKS 0x1002:0x6741
0x106B:0x00E2).
[2.603568] [drm] register mmio base: 0xB080
[2.603570] [drm] register mmio size: 131072
[2.603605] radeon :01:00.0: Invalid ROM contents
[2.603641] radeon :01:00.0: Invalid ROM contents
[2.603646] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
[2.603649] radeon :01:00.0: Fatal error during GPU init

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #55 from Benjamin Lee  ---
This has regressed some time after 3.9-rc2.  I haven't tried 3.9-rc3 but it is
definitely not working anymore in 3.9-rc4:

[2.603538] [drm] initializing kernel modesetting (TURKS 0x1002:0x6741
0x106B:0x00E2).
[2.603568] [drm] register mmio base: 0xB080
[2.603570] [drm] register mmio size: 131072
[2.603605] radeon :01:00.0: Invalid ROM contents
[2.603641] radeon :01:00.0: Invalid ROM contents
[2.603646] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
[2.603649] radeon :01:00.0: Fatal error during GPU init

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #54 from Austin Lund  ---
This does seem to be fixed in 3.8 series kernels.  I just tested 3.8-rc6 and
booted fine into radeondrmfb.  I could get the vgaswitcheroo to move between
the integrated and discrete, but I couldn't get the intel console to work (will
have to check my config).

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #54 from Austin Lund  ---
This does seem to be fixed in 3.8 series kernels.  I just tested 3.8-rc6 and
booted fine into radeondrmfb.  I could get the vgaswitcheroo to move between
the integrated and discrete, but I couldn't get the intel console to work (will
have to check my config).

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #53 from Benjamin Lee  ---
I can also confirm that Radeon KMS works on my MacBookPro8,2 with kernel
version 3.8-rc6 and EFI stub boot.  I also needed to add a device section to my
xorg.conf.

I don't see any video BIOS in /dev/mem so I guess it is loading from ACPI
instead.  Out of curiosity, I tried to load fglrx and it failed to find a valid
VBIOS so fglrx must not have the ACPI loading method.

blee at supra ~ $ sudo dd if=/dev/mem of=/dev/stdout bs=65536 skip=12 count=1
2>/dev/null | hexdump
000        
*
001

[2.589927] [drm] Initialized drm 1.1.0 20060810
[2.589966] [drm] radeon defaulting to kernel modesetting.
[2.589969] [drm] radeon kernel modesetting enabled.
[2.590189] [drm] initializing kernel modesetting (TURKS 0x1002:0x6741
0x106B
:0x00E2).
[2.590226] [drm] register mmio base: 0xB080
[2.590229] [drm] register mmio size: 131072
[2.590253] ATOM BIOS: Apple
[2.590264] [drm] GPU not posted. posting now...
[2.599466] radeon :01:00.0: VRAM: 1024M 0x -
0x3
FFF (1024M used)
[2.599472] radeon :01:00.0: GTT: 512M 0x4000 -
0x5FF
F
[2.604787] [drm] Detected VRAM RAM=1024M, BAR=256M
[2.604793] [drm] RAM width 128bits DDR
[2.604843] [TTM] Zone  kernel: Available graphics memory: 4042710 kiB
[2.604846] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[2.604849] [TTM] Initializing pool allocator
[2.604858] [TTM] Initializing DMA pool allocator
[2.604893] [drm] radeon: 1024M of VRAM memory ready
[2.604896] [drm] radeon: 512M of GTT memory ready.
[2.604917] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[2.604920] [drm] Driver supports precise vblank timestamp query.
[2.604982] radeon :01:00.0: irq 45 for MSI/MSI-X
[2.604993] radeon :01:00.0: radeon: using MSI.
[2.605028] [drm] radeon: irq initialized.
[2.605033] [drm] GART: num cpu pages 131072, num gpu pages 131072
[2.605463] [drm] probing gen 2 caps for device 8086:101 = 2/0
[2.605470] [drm] PCIE gen 2 link speeds already enabled
[2.605534] [drm] Loading TURKS Microcode

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #53 from Benjamin Lee  ---
I can also confirm that Radeon KMS works on my MacBookPro8,2 with kernel
version 3.8-rc6 and EFI stub boot.  I also needed to add a device section to my
xorg.conf.

I don't see any video BIOS in /dev/mem so I guess it is loading from ACPI
instead.  Out of curiosity, I tried to load fglrx and it failed to find a valid
VBIOS so fglrx must not have the ACPI loading method.

blee@supra ~ $ sudo dd if=/dev/mem of=/dev/stdout bs=65536 skip=12 count=1
2>/dev/null | hexdump
000        
*
001

[2.589927] [drm] Initialized drm 1.1.0 20060810
[2.589966] [drm] radeon defaulting to kernel modesetting.
[2.589969] [drm] radeon kernel modesetting enabled.
[2.590189] [drm] initializing kernel modesetting (TURKS 0x1002:0x6741
0x106B
:0x00E2).
[2.590226] [drm] register mmio base: 0xB080
[2.590229] [drm] register mmio size: 131072
[2.590253] ATOM BIOS: Apple
[2.590264] [drm] GPU not posted. posting now...
[2.599466] radeon :01:00.0: VRAM: 1024M 0x -
0x3
FFF (1024M used)
[2.599472] radeon :01:00.0: GTT: 512M 0x4000 -
0x5FF
F
[2.604787] [drm] Detected VRAM RAM=1024M, BAR=256M
[2.604793] [drm] RAM width 128bits DDR
[2.604843] [TTM] Zone  kernel: Available graphics memory: 4042710 kiB
[2.604846] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[2.604849] [TTM] Initializing pool allocator
[2.604858] [TTM] Initializing DMA pool allocator
[2.604893] [drm] radeon: 1024M of VRAM memory ready
[2.604896] [drm] radeon: 512M of GTT memory ready.
[2.604917] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[2.604920] [drm] Driver supports precise vblank timestamp query.
[2.604982] radeon :01:00.0: irq 45 for MSI/MSI-X
[2.604993] radeon :01:00.0: radeon: using MSI.
[2.605028] [drm] radeon: irq initialized.
[2.605033] [drm] GART: num cpu pages 131072, num gpu pages 131072
[2.605463] [drm] probing gen 2 caps for device 8086:101 = 2/0
[2.605470] [drm] PCIE gen 2 link speeds already enabled
[2.605534] [drm] Loading TURKS Microcode

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #52 from Alex Deucher  ---
(In reply to comment #51)
> Any other suggestions? Thanks.

You might ask on the dri-devel mailing list.  This is getting off topic for
this bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #51 from Anonymous Helper  ---
(In reply to comment #50) 
> You'll need to use vga-switcheroo to select the card you want to use.  Then
> you should be able to start X without any config and it will start on the
> one selected by vga-switcheroo.  Having two device sections as your config
> does will force X to try and start on both devices.

I tried without the BusID but all I got was a black screen. For some reason
when I switch to the intel GPU I get a black screen also, though it did work
when I booted from grub-efi earlier with the well documented outb commands to
disable AMD (no BIOS from EFI w/o efistub). Not sure if it's an issue with
vga-switcheroo, intel driver or something else.

I don't know if it's a problem, but both cards are powered on at boot. I can
switch back and forth between the GPUs (though it's tricky doing so blind when
on intel graphics).

Any other suggestions? Thanks.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #50 from Alex Deucher  ---
(In reply to comment #49)
> 
> Is the BusID line in the intel device section not needed? What is needed for
> X to automatically detect multiple GPUs properly and show some video output
> from the correct card?

You'll need to use vga-switcheroo to select the card you want to use.  Then you
should be able to start X without any config and it will start on the one
selected by vga-switcheroo.  Having two device sections as your config does
will force X to try and start on both devices.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #52 from Alex Deucher  ---
(In reply to comment #51)
> Any other suggestions? Thanks.

You might ask on the dri-devel mailing list.  This is getting off topic for
this bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #51 from Anonymous Helper  ---
(In reply to comment #50) 
> You'll need to use vga-switcheroo to select the card you want to use.  Then
> you should be able to start X without any config and it will start on the
> one selected by vga-switcheroo.  Having two device sections as your config
> does will force X to try and start on both devices.

I tried without the BusID but all I got was a black screen. For some reason
when I switch to the intel GPU I get a black screen also, though it did work
when I booted from grub-efi earlier with the well documented outb commands to
disable AMD (no BIOS from EFI w/o efistub). Not sure if it's an issue with
vga-switcheroo, intel driver or something else.

I don't know if it's a problem, but both cards are powered on at boot. I can
switch back and forth between the GPUs (though it's tricky doing so blind when
on intel graphics).

Any other suggestions? Thanks.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #50 from Alex Deucher  ---
(In reply to comment #49)
> 
> Is the BusID line in the intel device section not needed? What is needed for
> X to automatically detect multiple GPUs properly and show some video output
> from the correct card?

You'll need to use vga-switcheroo to select the card you want to use.  Then you
should be able to start X without any config and it will start on the one
selected by vga-switcheroo.  Having two device sections as your config does
will force X to try and start on both devices.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #49 from Anonymous Helper  ---
(In reply to comment #48)
> What do you mean by "make sure you add the PCI IDs to the xorg for both
> cards"?  The driver should autodetect the cards fine.  However for systems
> with multiple VGA cards, you may have to manually specify which ones you
> want to start X on.

Currently my xorg.conf.d directory contains the following config:

$ cat /etc/X11/xorg.conf.d/*
Section "Device"
Identifier "Radeon Graphics"
BusID "PCI:1:0:0"
EndSection
Section "Device"
Identifier "Intel Graphics"
BusID "PCI:0:2:0"
Driver "intel"
Option "AccelMethod" "sna"
#Option "AccelMethod" "uxa"
#Option "AccelMethod" "xaa"
EndSection

Is the BusID line in the intel device section not needed? What is needed for X
to automatically detect multiple GPUs properly and show some video output from
the correct card?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #49 from Anonymous Helper  ---
(In reply to comment #48)
> What do you mean by "make sure you add the PCI IDs to the xorg for both
> cards"?  The driver should autodetect the cards fine.  However for systems
> with multiple VGA cards, you may have to manually specify which ones you
> want to start X on.

Currently my xorg.conf.d directory contains the following config:

$ cat /etc/X11/xorg.conf.d/*
Section "Device"
Identifier "Radeon Graphics"
BusID "PCI:1:0:0"
EndSection
Section "Device"
Identifier "Intel Graphics"
BusID "PCI:0:2:0"
Driver "intel"
Option "AccelMethod" "sna"
#Option "AccelMethod" "uxa"
#Option "AccelMethod" "xaa"
EndSection

Is the BusID line in the intel device section not needed? What is needed for X
to automatically detect multiple GPUs properly and show some video output from
the correct card?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #48 from Alex Deucher  ---
(In reply to comment #46)
> Radeon now works for me on a MBP 8,2 booted from efistub in Linux 3.8.x.
> Can anyone else confirm this? You just need to make sure you add the PCI IDs
> to the xorg for both cards. Should Xorg detect them automatically? Is this
> another bug?

What do you mean by "make sure you add the PCI IDs to the xorg for both cards"?
 The driver should autodetect the cards fine.  However for systems with
multiple VGA cards, you may have to manually specify which ones you want to
start X on.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #48 from Alex Deucher  ---
(In reply to comment #46)
> Radeon now works for me on a MBP 8,2 booted from efistub in Linux 3.8.x.
> Can anyone else confirm this? You just need to make sure you add the PCI IDs
> to the xorg for both cards. Should Xorg detect them automatically? Is this
> another bug?

What do you mean by "make sure you add the PCI IDs to the xorg for both cards"?
 The driver should autodetect the cards fine.  However for systems with
multiple VGA cards, you may have to manually specify which ones you want to
start X on.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #47 from Bruno  ---
> Radeon now works for me on a MBP 8,2 booted from efistub in Linux 3.8.x.
> Can anyone else confirm this? You just need to make sure you add the PCI IDs
> to the xorg for both cards. Should Xorg detect them automatically? Is this
> another bug?

For nouveau on a MBA also booted via EFI stub I was told that "detection of
display by Xorg" happened through some magic bit set by first going through
efifb prior to native driver.

Without going through efifb Xorg didn't want to choose the available nVidia
GPU. (though linux console happily used the GPU).

Possibly the same applies to radeon.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #46 from Anonymous Helper  ---
Radeon now works for me on a MBP 8,2 booted from efistub in Linux 3.8.x.
Can anyone else confirm this? You just need to make sure you add the PCI IDs to
the xorg for both cards. Should Xorg detect them automatically? Is this another
bug?

Thank you!

Now we just need the IGP to show something onscreen when switching to it and it
will be perfect...

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #47 from Bruno  ---
> Radeon now works for me on a MBP 8,2 booted from efistub in Linux 3.8.x.
> Can anyone else confirm this? You just need to make sure you add the PCI IDs
> to the xorg for both cards. Should Xorg detect them automatically? Is this
> another bug?

For nouveau on a MBA also booted via EFI stub I was told that "detection of
display by Xorg" happened through some magic bit set by first going through
efifb prior to native driver.

Without going through efifb Xorg didn't want to choose the available nVidia
GPU. (though linux console happily used the GPU).

Possibly the same applies to radeon.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #46 from Anonymous Helper  ---
Radeon now works for me on a MBP 8,2 booted from efistub in Linux 3.8.x.
Can anyone else confirm this? You just need to make sure you add the PCI IDs to
the xorg for both cards. Should Xorg detect them automatically? Is this another
bug?

Thank you!

Now we just need the IGP to show something onscreen when switching to it and it
will be perfect...

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #45 from Alex Deucher  ---
(In reply to comment #44)

> 
> Good news, the radeon card is recognised with an EFI stub boot only !
> 
> But the screens stay black !! (lcd panel and hdmi) ..., X is started because
> I heard lightdm ubuntu sound, but all are black, no X and no console frame
> buffer.

It looks like you have a hybrid system with both an integrated GPU and a
discrete GPU.  You'll need to switch the mux to switch between the two GPUs
(the integrated is probably selected by default).  Apple has their own
proprietary mux and I'm not sure how well it's supported in Linux.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

luckylud at free.fr changed:

   What|Removed |Added

 CC||luckylud at free.fr

--- Comment #44 from luckylud at free.fr ---
(In reply to comment #43)
> Seems to be my bad.  I've got some extra patches that aren't in 3.6 to make
> this EFI stub booting thing work (not that the actual graphics switching
> works for me at the moment).  They can be downloaded here:
> 
> http://people.canonical.com/~sforshee/apple-gmux-patches/
> 
> However, I've been just rebasing them in my git tree for a while so I don't
> know if they cleanly apply.

Hi, 

My Hardware : macbook pro 8.2
OS: Ubuntu 12.04

I've tested on linux 3.6.2 with patchs 0002 to 0008 only, the others one are
already included in 3.6.2

Linux EFI stub boot with the following options :

[0.00] Kernel Command line: vmlinuz-3.6.2.efi root=UUID= ro
add_efi_memmap i915.lvds_channel_mode=2 i915.modeset=1 radeon.modeset=1
elevator=noop vt.handoff=7 initrd=EFI\gmux\initrd.img-3.6.2


Good news, the radeon card is recognised with an EFI stub boot only !

But the screens stay black !! (lcd panel and hdmi) ..., X is started because I
heard lightdm ubuntu sound, but all are black, no X and no console frame
buffer.


grep drm /var/log/dmesg.0

[2.657608] [drm] Initialized drm 1.1.0 20060810
[2.714673] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[2.714678] [drm] Driver supports precise vblank timestamp query.
[2.716738] [drm:intel_panel_setup_backlight] *ERROR* Failed to get maximum
backlight value
[2.759521] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[2.850547] [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit
banging on pin 2
[2.875632] fbcon: inteldrmfb (fb0) is primary device
[3.038809] fb0: inteldrmfb frame buffer device
[3.038829] drm: registered panic notifier
[3.187709] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor
0
[5.529949] [drm] radeon kernel modesetting enabled.
[5.530228] [drm] initializing kernel modesetting (TURKS 0x1002:0x6741
0x106B:0x00E2).
[5.530299] [drm] register mmio base: 0xB080
[5.530301] [drm] register mmio size: 131072
[5.530343] [drm] GPU not posted. posting now...
[5.545249] [drm] Detected VRAM RAM=1024M, BAR=256M
[5.545252] [drm] RAM width 128bits DDR
[5.545356] [drm] radeon: 1024M of VRAM memory ready
[5.545358] [drm] radeon: 512M of GTT memory ready.
[5.545378] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[5.545380] [drm] Driver supports precise vblank timestamp query.
[5.545512] [drm] radeon: irq initialized.
[5.545516] [drm] GART: num cpu pages 131072, num gpu pages 131072
[5.545871] [drm] probing gen 2 caps for device 8086:101 = 2/0
[5.545874] [drm] enabling PCIE gen 2 link speeds, disable with
radeon.pcie_gen2=0
[5.545959] [drm] Loading TURKS Microcode
[5.765427] [drm] PCIE GART of 512M enabled (table at 0x0004).
[5.787353] [drm] ring test on 0 succeeded in 2 usecs
[5.787761] [drm] ib test on ring 0 succeeded in 0 usecs
[5.790458] [drm] Radeon Display Connectors
[5.790462] [drm] Connector 0:
[5.790464] [drm]   LVDS-2
[5.790467] [drm]   DDC: 0x6470 0x6470 0x6474 0x6474 0x6478 0x6478 0x647c
0x647c
[5.790469] [drm]   Encoders:
[5.790471] [drm] LCD1: INTERNAL_UNIPHY
[5.790473] [drm] Connector 1:
[5.790475] [drm]   DP-2
[5.790476] [drm]   HPD1
[5.790479] [drm]   DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c
0x643c
[5.790481] [drm]   Encoders:
[5.790482] [drm] DFP1: INTERNAL_UNIPHY1
[5.790484] [drm] Connector 2:
[5.790486] [drm]   DP-3
[5.790487] [drm]   HPD2
[5.790490] [drm]   DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c
0x644c
[5.790491] [drm]   Encoders:
[5.790493] [drm] DFP2: INTERNAL_UNIPHY1
[5.790495] [drm] Connector 3:
[5.790497] [drm]   DP-4
[5.790498] [drm]   HPD3
[5.790501] [drm]   DDC: 0x6450 0x6450 0x6454 0x6454 0x6458 0x6458 0x645c
0x645c
[5.790503] [drm]   Encoders:
[5.790505] [drm] DFP3: INTERNAL_UNIPHY2
[5.790649] [drm] Special thermal controller config
[5.793123] [drm] radeon: power management initialized
[6.213991] [drm] fb mappable at 0x90142000
[6.213993] [drm] vram apper at 0x9000
[6.213994] [drm] size 8294400
[6.213996] [drm] fb depth is 24
[6.213997] [drm]pitch is 7680
[6.214080] fb1: radeondrmfb frame buffer device
[6.214085] [drm] Initialized radeon 2.24.0 20080528 for :01:00.0 on
minor 1


grep vga_switcheroo /var/log/dmesg.0
[4.279348] vga_switcheroo: enabled

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #45 from Alex Deucher  ---
(In reply to comment #44)

> 
> Good news, the radeon card is recognised with an EFI stub boot only !
> 
> But the screens stay black !! (lcd panel and hdmi) ..., X is started because
> I heard lightdm ubuntu sound, but all are black, no X and no console frame
> buffer.

It looks like you have a hybrid system with both an integrated GPU and a
discrete GPU.  You'll need to switch the mux to switch between the two GPUs
(the integrated is probably selected by default).  Apple has their own
proprietary mux and I'm not sure how well it's supported in Linux.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

lucky...@free.fr changed:

   What|Removed |Added

 CC||lucky...@free.fr

--- Comment #44 from lucky...@free.fr ---
(In reply to comment #43)
> Seems to be my bad.  I've got some extra patches that aren't in 3.6 to make
> this EFI stub booting thing work (not that the actual graphics switching
> works for me at the moment).  They can be downloaded here:
> 
> http://people.canonical.com/~sforshee/apple-gmux-patches/
> 
> However, I've been just rebasing them in my git tree for a while so I don't
> know if they cleanly apply.

Hi, 

My Hardware : macbook pro 8.2
OS: Ubuntu 12.04

I've tested on linux 3.6.2 with patchs 0002 to 0008 only, the others one are
already included in 3.6.2

Linux EFI stub boot with the following options :

[0.00] Kernel Command line: vmlinuz-3.6.2.efi root=UUID= ro
add_efi_memmap i915.lvds_channel_mode=2 i915.modeset=1 radeon.modeset=1
elevator=noop vt.handoff=7 initrd=EFI\gmux\initrd.img-3.6.2


Good news, the radeon card is recognised with an EFI stub boot only !

But the screens stay black !! (lcd panel and hdmi) ..., X is started because I
heard lightdm ubuntu sound, but all are black, no X and no console frame
buffer.


grep drm /var/log/dmesg.0

[2.657608] [drm] Initialized drm 1.1.0 20060810
[2.714673] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[2.714678] [drm] Driver supports precise vblank timestamp query.
[2.716738] [drm:intel_panel_setup_backlight] *ERROR* Failed to get maximum
backlight value
[2.759521] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[2.850547] [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit
banging on pin 2
[2.875632] fbcon: inteldrmfb (fb0) is primary device
[3.038809] fb0: inteldrmfb frame buffer device
[3.038829] drm: registered panic notifier
[3.187709] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor
0
[5.529949] [drm] radeon kernel modesetting enabled.
[5.530228] [drm] initializing kernel modesetting (TURKS 0x1002:0x6741
0x106B:0x00E2).
[5.530299] [drm] register mmio base: 0xB080
[5.530301] [drm] register mmio size: 131072
[5.530343] [drm] GPU not posted. posting now...
[5.545249] [drm] Detected VRAM RAM=1024M, BAR=256M
[5.545252] [drm] RAM width 128bits DDR
[5.545356] [drm] radeon: 1024M of VRAM memory ready
[5.545358] [drm] radeon: 512M of GTT memory ready.
[5.545378] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[5.545380] [drm] Driver supports precise vblank timestamp query.
[5.545512] [drm] radeon: irq initialized.
[5.545516] [drm] GART: num cpu pages 131072, num gpu pages 131072
[5.545871] [drm] probing gen 2 caps for device 8086:101 = 2/0
[5.545874] [drm] enabling PCIE gen 2 link speeds, disable with
radeon.pcie_gen2=0
[5.545959] [drm] Loading TURKS Microcode
[5.765427] [drm] PCIE GART of 512M enabled (table at 0x0004).
[5.787353] [drm] ring test on 0 succeeded in 2 usecs
[5.787761] [drm] ib test on ring 0 succeeded in 0 usecs
[5.790458] [drm] Radeon Display Connectors
[5.790462] [drm] Connector 0:
[5.790464] [drm]   LVDS-2
[5.790467] [drm]   DDC: 0x6470 0x6470 0x6474 0x6474 0x6478 0x6478 0x647c
0x647c
[5.790469] [drm]   Encoders:
[5.790471] [drm] LCD1: INTERNAL_UNIPHY
[5.790473] [drm] Connector 1:
[5.790475] [drm]   DP-2
[5.790476] [drm]   HPD1
[5.790479] [drm]   DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c
0x643c
[5.790481] [drm]   Encoders:
[5.790482] [drm] DFP1: INTERNAL_UNIPHY1
[5.790484] [drm] Connector 2:
[5.790486] [drm]   DP-3
[5.790487] [drm]   HPD2
[5.790490] [drm]   DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c
0x644c
[5.790491] [drm]   Encoders:
[5.790493] [drm] DFP2: INTERNAL_UNIPHY1
[5.790495] [drm] Connector 3:
[5.790497] [drm]   DP-4
[5.790498] [drm]   HPD3
[5.790501] [drm]   DDC: 0x6450 0x6450 0x6454 0x6454 0x6458 0x6458 0x645c
0x645c
[5.790503] [drm]   Encoders:
[5.790505] [drm] DFP3: INTERNAL_UNIPHY2
[5.790649] [drm] Special thermal controller config
[5.793123] [drm] radeon: power management initialized
[6.213991] [drm] fb mappable at 0x90142000
[6.213993] [drm] vram apper at 0x9000
[6.213994] [drm] size 8294400
[6.213996] [drm] fb depth is 24
[6.213997] [drm]pitch is 7680
[6.214080] fb1: radeondrmfb frame buffer device
[6.214085] [drm] Initialized radeon 2.24.0 20080528 for :01:00.0 on
minor 1


grep vga_switcheroo /var/log/dmesg.0
[4.279348] vga_switcheroo: enabled

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesk

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #43 from Austin Lund  ---
Seems to be my bad.  I've got some extra patches that aren't in 3.6 to make
this EFI stub booting thing work (not that the actual graphics switching works
for me at the moment).  They can be downloaded here:

http://people.canonical.com/~sforshee/apple-gmux-patches/

However, I've been just rebasing them in my git tree for a while so I don't
know if they cleanly apply.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL: 

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #43 from Austin Lund  ---
Seems to be my bad.  I've got some extra patches that aren't in 3.6 to make
this EFI stub booting thing work (not that the actual graphics switching works
for me at the moment).  They can be downloaded here:

http://people.canonical.com/~sforshee/apple-gmux-patches/

However, I've been just rebasing them in my git tree for a while so I don't
know if they cleanly apply.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #42 from Steve Smith  2012-09-18 07:02:43 
UTC ---
Created attachment 67314
  --> https://bugs.freedesktop.org/attachment.cgi?id=67314
EFI stub boot, 3.6-rc6

This doesn't work for me either, using EFI stub booting direct from Refind.
dmesg attached. Some additional details:

* MacBook Pro 8,3
* Arch Linux
* Kernel 3.6rc6
* Kernel command-line: vmlinuz-linux-mainline-3.x.efi
root=/dev/disk/by-label/Root ro add_efi_memmap radeon.modeset=1 i915.modeset=1
i915.lvds_channel_mode=2 initrd=\EFI\arch\initramfs-linux-mainline-3.x.img 

Relevent log lines:

[5.146024] vga_switcheroo: enabled
[5.146064] radeon :01:00.0: Invalid ROM contents
[5.146127] radeon :01:00.0: Invalid ROM contents
[5.146156] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
[5.146190] radeon :01:00.0: Fatal error during GPU init
[5.146221] [drm] radeon: finishing device.
[5.146222] [TTM] Memory type 2 has not been initialized
[5.147271] vga_switcheroo: disabled
[5.147416] radeon: probe of :01:00.0 failed with error -22

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #41 from Austin Lund  2012-09-18 05:55:27 
UTC ---
(In reply to comment #40)
> (In reply to comment #39)
> > From what I've been told, you need to boot using the EFI stub method and 
> > not a
> > boot-loader.  Also, you may need to pass some kernel options (eg initrd) so 
> > the
> > easiest way to do this is from within an EFI shell.
> Do you have any more details on that? I'd like to try it!

Make sure you have CONFIG_EFI and CONFIG_EFI_STUB set for your kernel.

Put the kernel image in a filesystem that can be read by the EFI firmware or
has a driver for it.

Boot into the EFI shell.  I do this via rEFIt.

cd to the location of the kernel then execute it by typing it's name.  Kernel
parameters can be listed after the kernel name.

> > How are you booting the kernel?
> linux /boot/vmlinuz root=/dev/sda3
> I have never needed an initrd, all required modules are built in...

OK.  So you haven't actually said, but you must be booting via Grub either in
EFI mode or BIOS compatiability mode.  Neither of those will work in extracting
the AtomBIOS from the configurations.  It needs to be done before calling
ExitBootServices() in EFI mode and Grub isn't set up to do anything this
tricky.  Hence you have to use the inbuilt kernel loader in the EFI stub code.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #42 from Steve Smith  2012-09-18 07:02:43 UTC 
---
Created attachment 67314
  --> https://bugs.freedesktop.org/attachment.cgi?id=67314
EFI stub boot, 3.6-rc6

This doesn't work for me either, using EFI stub booting direct from Refind.
dmesg attached. Some additional details:

* MacBook Pro 8,3
* Arch Linux
* Kernel 3.6rc6
* Kernel command-line: vmlinuz-linux-mainline-3.x.efi
root=/dev/disk/by-label/Root ro add_efi_memmap radeon.modeset=1 i915.modeset=1
i915.lvds_channel_mode=2 initrd=\EFI\arch\initramfs-linux-mainline-3.x.img 

Relevent log lines:

[5.146024] vga_switcheroo: enabled
[5.146064] radeon :01:00.0: Invalid ROM contents
[5.146127] radeon :01:00.0: Invalid ROM contents
[5.146156] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
[5.146190] radeon :01:00.0: Fatal error during GPU init
[5.146221] [drm] radeon: finishing device.
[5.146222] [TTM] Memory type 2 has not been initialized
[5.147271] vga_switcheroo: disabled
[5.147416] radeon: probe of :01:00.0 failed with error -22

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #41 from Austin Lund  2012-09-18 05:55:27 
UTC ---
(In reply to comment #40)
> (In reply to comment #39)
> > From what I've been told, you need to boot using the EFI stub method and 
> > not a
> > boot-loader.  Also, you may need to pass some kernel options (eg initrd) so 
> > the
> > easiest way to do this is from within an EFI shell.
> Do you have any more details on that? I'd like to try it!

Make sure you have CONFIG_EFI and CONFIG_EFI_STUB set for your kernel.

Put the kernel image in a filesystem that can be read by the EFI firmware or
has a driver for it.

Boot into the EFI shell.  I do this via rEFIt.

cd to the location of the kernel then execute it by typing it's name.  Kernel
parameters can be listed after the kernel name.

> > How are you booting the kernel?
> linux /boot/vmlinuz root=/dev/sda3
> I have never needed an initrd, all required modules are built in...

OK.  So you haven't actually said, but you must be booting via Grub either in
EFI mode or BIOS compatiability mode.  Neither of those will work in extracting
the AtomBIOS from the configurations.  It needs to be done before calling
ExitBootServices() in EFI mode and Grub isn't set up to do anything this
tricky.  Hence you have to use the inbuilt kernel loader in the EFI stub code.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

Moritz Schlarb  changed:

   What|Removed |Added

 CC||moschlar at metalabs.de

--- Comment #40 from Moritz Schlarb  2012-09-17 
06:23:27 UTC ---
(In reply to comment #39)
> From what I've been told, you need to boot using the EFI stub method and not a
> boot-loader.  Also, you may need to pass some kernel options (eg initrd) so 
> the
> easiest way to do this is from within an EFI shell.
Do you have any more details on that? I'd like to try it!
> How are you booting the kernel?
linux /boot/vmlinuz root=/dev/sda3
I have never needed an initrd, all required modules are built in...

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

Moritz Schlarb  changed:

   What|Removed |Added

 CC||mosch...@metalabs.de

--- Comment #40 from Moritz Schlarb  2012-09-17 06:23:27 
UTC ---
(In reply to comment #39)
> From what I've been told, you need to boot using the EFI stub method and not a
> boot-loader.  Also, you may need to pass some kernel options (eg initrd) so 
> the
> easiest way to do this is from within an EFI shell.
Do you have any more details on that? I'd like to try it!
> How are you booting the kernel?
linux /boot/vmlinuz root=/dev/sda3
I have never needed an initrd, all required modules are built in...

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #39 from Austin Lund  2012-09-16 22:19:23 
UTC ---
(In reply to comment #38)
> Created attachment 67258 [details]
> dmesg output from failing loading of radeon driver in 3.6.0_rc3
> 
> I tried with kernel 3.6.0_rc3 (using the Gentoo Linux ebuild
> sys-kernel/git-sources-3.6_rc3) but that doesn't change anything...
> Maybe someone can use the attached dmesg log for some useful information.
> (This is without using any changes to GRUB, but when I load vbios.bin and
> int10.bin the behaviour doesn't change)

>From what I've been told, you need to boot using the EFI stub method and not a
boot-loader.  Also, you may need to pass some kernel options (eg initrd) so the
easiest way to do this is from within an EFI shell.

How are you booting the kernel?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

Ch?-Thanh Christopher Nguy?n  changed:

   What|Removed |Added

  Attachment #67258|application/octet-stream|text/plain
  mime type||

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #38 from Moritz Schlarb  2012-09-16 
21:43:50 UTC ---
Created attachment 67258
  --> https://bugs.freedesktop.org/attachment.cgi?id=67258
dmesg output from failing loading of radeon driver in 3.6.0_rc3

I tried with kernel 3.6.0_rc3 (using the Gentoo Linux ebuild
sys-kernel/git-sources-3.6_rc3) but that doesn't change anything...
Maybe someone can use the attached dmesg log for some useful information.
(This is without using any changes to GRUB, but when I load vbios.bin and
int10.bin the behaviour doesn't change)

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #39 from Austin Lund  2012-09-16 22:19:23 
UTC ---
(In reply to comment #38)
> Created attachment 67258 [details]
> dmesg output from failing loading of radeon driver in 3.6.0_rc3
> 
> I tried with kernel 3.6.0_rc3 (using the Gentoo Linux ebuild
> sys-kernel/git-sources-3.6_rc3) but that doesn't change anything...
> Maybe someone can use the attached dmesg log for some useful information.
> (This is without using any changes to GRUB, but when I load vbios.bin and
> int10.bin the behaviour doesn't change)

>From what I've been told, you need to boot using the EFI stub method and not a
boot-loader.  Also, you may need to pass some kernel options (eg initrd) so the
easiest way to do this is from within an EFI shell.

How are you booting the kernel?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

Chí-Thanh Christopher Nguyễn  changed:

   What|Removed |Added

  Attachment #67258|application/octet-stream|text/plain
  mime type||

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #38 from Moritz Schlarb  2012-09-16 21:43:50 
UTC ---
Created attachment 67258
  --> https://bugs.freedesktop.org/attachment.cgi?id=67258
dmesg output from failing loading of radeon driver in 3.6.0_rc3

I tried with kernel 3.6.0_rc3 (using the Gentoo Linux ebuild
sys-kernel/git-sources-3.6_rc3) but that doesn't change anything...
Maybe someone can use the attached dmesg log for some useful information.
(This is without using any changes to GRUB, but when I load vbios.bin and
int10.bin the behaviour doesn't change)

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

Florian Mickler  changed:

   What|Removed |Added

 CC||florian at mickler.org

--- Comment #37 from Florian Mickler  2012-09-05 
20:39:27 UTC ---
A patch referencing this bug report has been merged in Linux v3.6-rc3:

commit 268ba0a99f89a84dc5eb312470896113d0709c74
Author: David Lamparter 
Date:   Thu Aug 16 15:45:20 2012 -0400

drm/radeon: implement ACPI VFCT vbios fetch (v3)

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

Florian Mickler  changed:

   What|Removed |Added

 CC||flor...@mickler.org

--- Comment #37 from Florian Mickler  2012-09-05 20:39:27 
UTC ---
A patch referencing this bug report has been merged in Linux v3.6-rc3:

commit 268ba0a99f89a84dc5eb312470896113d0709c74
Author: David Lamparter 
Date:   Thu Aug 16 15:45:20 2012 -0400

drm/radeon: implement ACPI VFCT vbios fetch (v3)

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #36 from Stefan D?singer  2012-08-30 
17:39:59 UTC ---
My guess would be that they simply store it in the driver, i.e. similarly to
what my hack does. Considering that they have hardware and software under full
control I don't see why they want a video bios that's separate from the driver.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #35 from Alex Deucher  2012-08-30 14:25:55 UTC 
---
(In reply to comment #34)
> Alex,
> Please see the DSDT table from a Macbook Pro booted in EFI mode. Maybe it will
> give you some ideas for extracting the VBIOS.

Sorry, I'm not really much of an ACPI or Mac expert.  I don't see anything
relevant.  IIRC, the vbios on macs is only available in boot services so it's
likely gone by the time the OS is loaded.  You'd probably need the boot loader
to grab it and store a copy somewhere so the OS can access it when it loads. 
I'm not sure how Apple does it.  Someone more familiar with Macs may have some
ideas.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #36 from Stefan Dösinger  2012-08-30 
17:39:59 UTC ---
My guess would be that they simply store it in the driver, i.e. similarly to
what my hack does. Considering that they have hardware and software under full
control I don't see why they want a video bios that's separate from the driver.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #35 from Alex Deucher  2012-08-30 14:25:55 UTC ---
(In reply to comment #34)
> Alex,
> Please see the DSDT table from a Macbook Pro booted in EFI mode. Maybe it will
> give you some ideas for extracting the VBIOS.

Sorry, I'm not really much of an ACPI or Mac expert.  I don't see anything
relevant.  IIRC, the vbios on macs is only available in boot services so it's
likely gone by the time the OS is loaded.  You'd probably need the boot loader
to grab it and store a copy somewhere so the OS can access it when it loads. 
I'm not sure how Apple does it.  Someone more familiar with Macs may have some
ideas.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #34 from Anonymous Helper  2012-08-30 
01:48:07 UTC ---
Created attachment 66308
  --> https://bugs.freedesktop.org/attachment.cgi?id=66308
DSDT table from Macbook Pro 8,2 (EFI boot)

Alex,
Please see the DSDT table from a Macbook Pro booted in EFI mode. Maybe it will
give you some ideas for extracting the VBIOS.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #34 from Anonymous Helper  2012-08-30 
01:48:07 UTC ---
Created attachment 66308
  --> https://bugs.freedesktop.org/attachment.cgi?id=66308
DSDT table from Macbook Pro 8,2 (EFI boot)

Alex,
Please see the DSDT table from a Macbook Pro booted in EFI mode. Maybe it will
give you some ideas for extracting the VBIOS.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

headwall  changed:

   What|Removed |Added

 CC||hedvall at gmail.com

--- Comment #33 from headwall  2012-08-12 17:52:10 UTC ---
I tried the VFCT patch on a Mac Pro 1,1, and it gives me a kernel panic. I
can't really give any details on it because the screen output is garbled. The
previous patch with adding the video ROM to the kernel works, but without X
support.

Should the VFCT table show up in /sys/firmware/acpi/tables? If so, the Mac
doesn't support this method. Does anyone know what Darwin/OSX does to get the
ROM?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

headwall  changed:

   What|Removed |Added

 CC||hedv...@gmail.com

--- Comment #33 from headwall  2012-08-12 17:52:10 UTC ---
I tried the VFCT patch on a Mac Pro 1,1, and it gives me a kernel panic. I
can't really give any details on it because the screen output is garbled. The
previous patch with adding the video ROM to the kernel works, but without X
support.

Should the VFCT table show up in /sys/firmware/acpi/tables? If so, the Mac
doesn't support this method. Does anyone know what Darwin/OSX does to get the
ROM?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #32 from Alex Deucher  2012-08-09 21:10:43 UTC 
---
Created attachment 65357
  --> https://bugs.freedesktop.org/attachment.cgi?id=65357
VFCT patch

Hi David,  I took the liberty of cleaning up your UEFI VFCT patch.  I'd like to
get it into the next drm fixes pull in the next day or so.  If you are ok with
it or would like anything changed, please let me know.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #32 from Alex Deucher  2012-08-09 21:10:43 UTC ---
Created attachment 65357
  --> https://bugs.freedesktop.org/attachment.cgi?id=65357
VFCT patch

Hi David,  I took the liberty of cleaning up your UEFI VFCT patch.  I'd like to
get it into the next drm fixes pull in the next day or so.  If you are ok with
it or would like anything changed, please let me know.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #31 from David L.  
2012-08-03 23:21:21 UTC ---
(In reply to comment #30)
> (In reply to comment #29)
> > Is the lvds console display shifted if you don't connect any external 
> > monitor ?
> 
> So far I only got the LVDS to display anything by connecting the DP monitor, 
> so
> I don't really know.  I didn't try much there... I'll try some other magic
> incantations/plug sequences tomorrow, maybe there's a sequence to get 
> LVDS-only
> with it actually showing something.
> 
> Starting X while the LVDS is off works fine, reenabling it.

Correction: I just had a hard freeze after an hour or so of X use.

Since I need to get some things done, I've booted in hybrid UEFI mode now with
only the brightness patch applied.  The LVDS-blank-after-insmod issue is gone,
so it's not the backlight control I guess.

Also, interestingly, the power consumption of the laptop was considerably lower
under UEFI native mode (24W) vs. UEFI hybrid mode (29W).  Could be either the
CRTC programming patch or something completely unrelated.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #30 from David L.  
2012-08-03 22:54:12 UTC ---
(In reply to comment #29)
> Is the lvds console display shifted if you don't connect any external monitor 
> ?

So far I only got the LVDS to display anything by connecting the DP monitor, so
I don't really know.  I didn't try much there... I'll try some other magic
incantations/plug sequences tomorrow, maybe there's a sequence to get LVDS-only
with it actually showing something.

Starting X while the LVDS is off works fine, reenabling it.

Also, the "LVDS off" state after loading the module has the backlight off too,
maybe it's a bug in the brightness control and there is content but I just
don't see it...

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #29 from Jerome Glisse  2012-08-03 
22:05:53 UTC ---
Is the lvds console display shifted if you don't connect any external monitor ?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #28 from David L.  
2012-08-03 21:17:10 UTC ---
(In reply to comment #27)
> > 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.
> 
> You probably need this patch:
> http://lists.freedesktop.org/archives/dri-devel/2012-July/025567.html

After both patches, that indeed fixes things as soon as X is started, but the
console is still broken.  After loading the module, the panel just switches
off, though the console is still usable.  Plugging my DisplayPort screen in
also reenables the LVDS panel, although the image is wrapped around by around
100 pixels. (Left part of my prompt is on the right of the screen.)  
Wraparound might be related to the different resolution for the ext display;
the external screen only shows the nonwrapping part of the image (and is
therefore missing the first characters of the prompt).  Either way that's a
separate bug...


Apart from the above, I now have working graphics (including 3D) on an UEFI
native booted HP EliteBook.  I'll clean up my hack VFCT patch and send it to
dri-devel.


P.S.: The laptop also needs your backlight control patch, thanks a zillion for
that - you wouldn't believe how nuts that was driving me.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #27 from Alex Deucher  2012-08-03 19:23:34 UTC 
---
(In reply to comment #26)
> Created attachment 65100 [details] [review]
> 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)
> 

Excellent.

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

You probably need this patch:
http://lists.freedesktop.org/archives/dri-devel/2012-July/025567.html

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@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.

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #25 from Alex Deucher  2012-08-03 17:26:03 UTC 
---
(In reply to comment #24)
> Should this already work on 3.4.7 and should I file a separate report about
> ACPI VFCT being broken or is that future tense/upcoming?

Support for fetching the vbios from VFCT still needs to be implemented.

> 
> Also, in hybrid boot mode at least, acpidump gives me no hits for VFCT (just
> tried acpidump | grep VFCT, that should show something shouldn't it?) Will try
> under native UEFI in a minute...

I'm not too familiar with ACPI and UEFI unfortunately.  It's part of the GOP
stuff for UEFI.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #24 from David L.  
2012-08-03 17:12:52 UTC ---
(In reply to comment #23)
> On UEFI systems the vbios should be accessible via the ACPI VFCT.  See the
> bottom of atombios.h for struct definitions.  Macs do their own thing so I
> don't know if this will work on them or not.

Should this already work on 3.4.7 and should I file a separate report about
ACPI VFCT being broken or is that future tense/upcoming?

Also, in hybrid boot mode at least, acpidump gives me no hits for VFCT (just
tried acpidump | grep VFCT, that should show something shouldn't it?) Will try
under native UEFI in a minute...

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #23 from Alex Deucher  2012-08-03 16:33:04 UTC 
---
On UEFI systems the vbios should be accessible via the ACPI VFCT.  See the
bottom of atombios.h for struct definitions.  Macs do their own thing so I
don't know if this will work on them or not.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #31 from David L.  2012-08-03 
23:21:21 UTC ---
(In reply to comment #30)
> (In reply to comment #29)
> > Is the lvds console display shifted if you don't connect any external 
> > monitor ?
> 
> So far I only got the LVDS to display anything by connecting the DP monitor, 
> so
> I don't really know.  I didn't try much there... I'll try some other magic
> incantations/plug sequences tomorrow, maybe there's a sequence to get 
> LVDS-only
> with it actually showing something.
> 
> Starting X while the LVDS is off works fine, reenabling it.

Correction: I just had a hard freeze after an hour or so of X use.

Since I need to get some things done, I've booted in hybrid UEFI mode now with
only the brightness patch applied.  The LVDS-blank-after-insmod issue is gone,
so it's not the backlight control I guess.

Also, interestingly, the power consumption of the laptop was considerably lower
under UEFI native mode (24W) vs. UEFI hybrid mode (29W).  Could be either the
CRTC programming patch or something completely unrelated.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-dae...@freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

David L.  changed:

   What|Removed |Added

 CC||equinox-freedesktopbugs at dia
   ||c24.net
Summary|Radeon KMS on Macs with EFI |Radeon KMS fails with
   |boot|inaccessible AtomBIOS on
   ||systems with (U)EFI boot

--- Comment #22 from David L.  
2012-08-03 16:12:27 UTC ---
Exact same issue appears on an HP EliteBook 8470p if you select "native UEFI"
as boot method in setup.  Legacy and hybrid boot options work fine.

Changing bug title since this is not a Mac-specific issue, although it is more
severe on Macs without the legacy/hybrid options easily accessible.

It seems that the driver either cannot rely on the AtomBIOS being accessible,
or we need to add code to enable the mapping with some PCI hacks?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #30 from David L.  2012-08-03 
22:54:12 UTC ---
(In reply to comment #29)
> Is the lvds console display shifted if you don't connect any external monitor 
> ?

So far I only got the LVDS to display anything by connecting the DP monitor, so
I don't really know.  I didn't try much there... I'll try some other magic
incantations/plug sequences tomorrow, maybe there's a sequence to get LVDS-only
with it actually showing something.

Starting X while the LVDS is off works fine, reenabling it.

Also, the "LVDS off" state after loading the module has the backlight off too,
maybe it's a bug in the brightness control and there is content but I just
don't see it...

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #29 from Jerome Glisse  2012-08-03 22:05:53 
UTC ---
Is the lvds console display shifted if you don't connect any external monitor ?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #28 from David L.  2012-08-03 
21:17:10 UTC ---
(In reply to comment #27)
> > 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.
> 
> You probably need this patch:
> http://lists.freedesktop.org/archives/dri-devel/2012-July/025567.html

After both patches, that indeed fixes things as soon as X is started, but the
console is still broken.  After loading the module, the panel just switches
off, though the console is still usable.  Plugging my DisplayPort screen in
also reenables the LVDS panel, although the image is wrapped around by around
100 pixels. (Left part of my prompt is on the right of the screen.)  
Wraparound might be related to the different resolution for the ext display;
the external screen only shows the nonwrapping part of the image (and is
therefore missing the first characters of the prompt).  Either way that's a
separate bug...


Apart from the above, I now have working graphics (including 3D) on an UEFI
native booted HP EliteBook.  I'll clean up my hack VFCT patch and send it to
dri-devel.


P.S.: The laptop also needs your backlight control patch, thanks a zillion for
that - you wouldn't believe how nuts that was driving me.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #27 from Alex Deucher  2012-08-03 19:23:34 UTC ---
(In reply to comment #26)
> Created attachment 65100 [details] [review]
> 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)
> 

Excellent.

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

You probably need this patch:
http://lists.freedesktop.org/archives/dri-devel/2012-July/025567.html

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

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.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #25 from Alex Deucher  2012-08-03 17:26:03 UTC ---
(In reply to comment #24)
> Should this already work on 3.4.7 and should I file a separate report about
> ACPI VFCT being broken or is that future tense/upcoming?

Support for fetching the vbios from VFCT still needs to be implemented.

> 
> Also, in hybrid boot mode at least, acpidump gives me no hits for VFCT (just
> tried acpidump | grep VFCT, that should show something shouldn't it?) Will try
> under native UEFI in a minute...

I'm not too familiar with ACPI and UEFI unfortunately.  It's part of the GOP
stuff for UEFI.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #24 from David L.  2012-08-03 
17:12:52 UTC ---
(In reply to comment #23)
> On UEFI systems the vbios should be accessible via the ACPI VFCT.  See the
> bottom of atombios.h for struct definitions.  Macs do their own thing so I
> don't know if this will work on them or not.

Should this already work on 3.4.7 and should I file a separate report about
ACPI VFCT being broken or is that future tense/upcoming?

Also, in hybrid boot mode at least, acpidump gives me no hits for VFCT (just
tried acpidump | grep VFCT, that should show something shouldn't it?) Will try
under native UEFI in a minute...

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

--- Comment #23 from Alex Deucher  2012-08-03 16:33:04 UTC ---
On UEFI systems the vbios should be accessible via the ACPI VFCT.  See the
bottom of atombios.h for struct definitions.  Macs do their own thing so I
don't know if this will work on them or not.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 26891] Radeon KMS fails with inaccessible AtomBIOS on systems with (U)EFI boot

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=26891

David L.  changed:

   What|Removed |Added

 CC||equinox-freedesktopbugs@dia
   ||c24.net
Summary|Radeon KMS on Macs with EFI |Radeon KMS fails with
   |boot|inaccessible AtomBIOS on
   ||systems with (U)EFI boot

--- Comment #22 from David L.  2012-08-03 
16:12:27 UTC ---
Exact same issue appears on an HP EliteBook 8470p if you select "native UEFI"
as boot method in setup.  Legacy and hybrid boot options work fine.

Changing bug title since this is not a Mac-specific issue, although it is more
severe on Macs without the legacy/hybrid options easily accessible.

It seems that the driver either cannot rely on the AtomBIOS being accessible,
or we need to add code to enable the mapping with some PCI hacks?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel