> On Dec 14, 2018, at 5:41 PM, Andy Bradford
> <amb-sendok-1547419284.nibdcnmplmbgdjjlh...@bradfords.org> wrote:
>
> Thus said Allan Streib on Wed, 12 Dec 2018 14:09:06 -0500:
>
>> Still having this issue on -current as of Dec10.
>> machdep.allowaperture=2 does get me past this, but am seeing
>> weird behavior, some regions of screens/terminals not painting or
>> refreshing.
>
> As far as I'm aware no progress has been made. It seems to be having a
> problem reading the ATOM BIOS and I haven't yet figured out a way to
> dump out what it is reading to disk so it can be analyzed. Maybe some of
> the commands from the other thread on bugs@ will lead to additional
> information.
Try previous releases of OpenBSD/amd64 to check if radeondrm ever worked for
you on amd64. I wouldn’t check any version older than 6.1, but if any of the
previous releases work that could give some more clues about where the problem
could be.
Also would be interesting to uncomment DRMDEBUG and show full dmesg under both
i386 and amd64 using -current releases. ie.
https://github.com/openbsd/src/blob/master/sys/dev/pci/drm/drmP.h#L40
If you diff the dmesgs is there any other difference besides what’s already
been reported?
>
> Another alternative, if you can, is to use i386 instead of amd64. I
> found that on i386 it does correctly detect the ATOM BIOS.
>
> Andy
> --
> TAI64 timestamp: 400000005c1431b9
>
>
