Re: PowerMac G5 and KMS

On Thu, Mar 2, 2017 at 5:42 AM, Hiroo Ono (小野寛生)
<hiroo.ono+freebsd_at_gmail.com> wrote:
> I recently installed 12-current powerpc64 r313561 to a PowerMac G5
>  (it is dual processor, but I do not know its detail).
>
> When I try to load drm2.ko and radeonkms.ko,
> the screen turns into black and recovers, then the system locks.
> kldload command does not return, no response to keyboard input, etc.
>
> Is it possible to use KMS on FreeBSD/powerpc64?
>
> The log in /var/log/messages is
>
> after "kldload drm2",
>
> kernel: info: [drm] Initialized drm 1.1.0 20060810
>
> and then, after "kldload radeonkms",
>
> kernel: iic0: <I2C generic I/O> on iicbus0
> kernel: iic1: <I2C generic I/O> on iicbus1
> kernel: drmn0: <ATI Radeon AP 9600> on vgapci0
> kernel: info: [drm] RADEON_IS_AGP
> kernel: info: [drm] initializing kernel modesetting (RV350 0x1002:0x4150
> 0x1002:0x4150).
> kernel: info: [drm] register mmio base: 0x90000000
> kernel: info: [drm] register mmio size: 65536
> kernel: info: [drm] igp_read_bios_from_vram: ===> Try IGP's VRAM...
> kernel: info: [drm] igp_read_bios_from_vram: VRAM base address: 0x98000000
> kernel: info: [drm] igp_read_bios_from_vram: Map address:
> 0xc000000061412000 (262144 bytes)
> kernel: info: [drm] igp_read_bios_from_vram: Incorrect BIOS signature:
> 0x0000
> kernel: info: [drm] radeon_read_bios: ===> Try PCI Expansion ROM...
> kernel: info: [drm] radeon_read_bios: Map address: 0xc000000061412000
> (131072 bytes)
> kernel: info: [drm] radeon_read_bios: Incorrect BIOS signature: 0x2AFF
> kernel: info: [drm] legacy_read_disabled_bios: ===> Try disabled BIOS
> (legacy)...
> kernel: info: [drm] radeon_read_bios: ===> Try PCI Expansion ROM...
> kernel: info: [drm] radeon_read_bios: Map address: 0xc000000061412000
> (131072 bytes)
>
> As the system locks up here, I have to power it off forcibly.

Congratulations (?) you are quite possibly the first person to report
even attempting to use radeonkms on powerpc64.  Frankly, I'm not
surprised that it doesn't work for you.  Unfortunately, I don't have a
solution, or even a means to track it down.  Looking at the log
snippet, my first guess is there may need to be a provision added to
the driver for non-x86.  Do you know what card this is?

Adding a couple other lists with people who might have more insight.

If it can be made to work, I'd definitely want to get a Radeon card for my G5(s)

- Justin