On Thu, Aug 08, 2019 at 10:23:15AM +0200, Sebastien Marie wrote:
>
> I will try to compare i386 and amd64 in r600_read_disabled_bios().
I didn't found any major difference between i386 and amd64. the values
below are the same for i386 and amd64.
- radeon_get_bios()
-
On Thu, Aug 08, 2019 at 06:57:57AM +0200, Sebastien Marie wrote:
> On Wed, Aug 07, 2019 at 11:12:57PM +0200, Mark Kettenis wrote:
> > > > Can you try to figure out where exactly reading the BIOS from the card
> > > > goes wrong?
> > >
> > > radeon_read_bios (called by r600_read_disabled_bios)
On Thu, Aug 08, 2019 at 09:42:49AM +0200, Sebastien Marie wrote:
> On Wed, Aug 07, 2019 at 07:47:43PM +0200, Matthieu Herrb wrote:
> > On Wed, Aug 07, 2019 at 11:32:09AM +0200, Matthieu Herrb wrote:
> > >
> > > I will also have a look on why did the extra built-in modes disapear.
> > > But I
On Wed, Aug 07, 2019 at 07:47:43PM +0200, Matthieu Herrb wrote:
> On Wed, Aug 07, 2019 at 11:32:09AM +0200, Matthieu Herrb wrote:
> >
> > I will also have a look on why did the extra built-in modes disapear.
> > But I think that if you can run a better driver than xf86-video-vesa,
> > it is
On Wed, Aug 07, 2019 at 11:12:57PM +0200, Mark Kettenis wrote:
> > > Can you try to figure out where exactly reading the BIOS from the card
> > > goes wrong?
> >
> > radeon_read_bios (called by r600_read_disabled_bios) returns something
> > good enough to pass some tests (bios signature check)
> Date: Wed, 7 Aug 2019 20:17:26 +0200
> From: Sebastien Marie
>
> On Wed, Aug 07, 2019 at 03:16:56PM +0200, Mark Kettenis wrote:
> > >
> > > I built a kernel with DRMDEBUG and put 0x in drm_debug variable.
> > >
> > > initializing kernel modesetting (RV610 0x1002:0x94C3 0x1028:0x0402
On Wed, Aug 07, 2019 at 03:16:56PM +0200, Mark Kettenis wrote:
> >
> > I built a kernel with DRMDEBUG and put 0x in drm_debug variable.
> >
> > initializing kernel modesetting (RV610 0x1002:0x94C3 0x1028:0x0402 0x00).
> > [drm] COMBIOS detected
> > drm:pid0:r600_init *ERROR* Expecting
On Wed, Aug 07, 2019 at 11:32:09AM +0200, Matthieu Herrb wrote:
>
> I will also have a look on why did the extra built-in modes disapear.
> But I think that if you can run a better driver than xf86-video-vesa,
> it is better.
Hi again,
I think I've found the problem.
It's caused by this commit:
> Date: Wed, 7 Aug 2019 14:52:50 +0200
> From: Sebastien Marie
>
> On Wed, Aug 07, 2019 at 11:20:59AM +0200, Mark Kettenis wrote:
> >
> > > I see no change in dmesg with my old state (Thu Jul 25 08:28:22 MDT
> > > 2019). I attached the current dmesg below (the radeondrm0 error and
> > > detach
On Wed, Aug 07, 2019 at 11:32:09AM +0200, Matthieu Herrb wrote:
> Hi,
>
> have you installed the radeon firmware package ? If not, that may
> explain why this machine cannot use KMS and the radeon X driver.
Yes.
# pkg_info radeondrm-firmware
Information for inst:radeondrm-firmware-20181218
On Wed, Aug 07, 2019 at 11:20:59AM +0200, Mark Kettenis wrote:
>
> > I see no change in dmesg with my old state (Thu Jul 25 08:28:22 MDT
> > 2019). I attached the current dmesg below (the radeondrm0 error and
> > detach was already present before).
> >
> > The system uses VESA driver.
>
> The
On Wed, Aug 07, 2019 at 09:21:28AM +0200, Sebastien Marie wrote:
> Hi,
>
> I upgraded an amd64 host with
> OpenBSD 6.5-current (GENERIC.MP) #174: Tue Aug 6 10:56:11 MDT 2019.
>
> The system starts xenodm using rcctl.
>
> With X Server 1.20.5, the maximum screen size is 720x400, whereas it
> Date: Wed, 7 Aug 2019 09:21:28 +0200
> From: Sebastien Marie
>
> Hi,
>
> I upgraded an amd64 host with
> OpenBSD 6.5-current (GENERIC.MP) #174: Tue Aug 6 10:56:11 MDT 2019.
>
> The system starts xenodm using rcctl.
>
> With X Server 1.20.5, the maximum screen size is 720x400, whereas
13 matches
Mail list logo
