Re: port-amd64/57532: Incorrect resolution after latest NetBSD 10 BETA amd64 install.

["Brian Durant" <brian%durant.dk@localhost>]

The following reply was made to PR port-amd64/57532; it has been noted by GNATS.

From: "Brian Durant" <brian%durant.dk@localhost>
To: "Taylor R Campbell" <riastradh%netbsd.org@localhost>
Cc: <gnats-bugs%netbsd.org@localhost>, <port-amd64-maintainer%netbsd.org@localhost>,
 <gnats-admin%netbsd.org@localhost>, <netbsd-bugs%netbsd.org@localhost>
Subject: Re: port-amd64/57532: Incorrect resolution after latest NetBSD 10
 BETA amd64 install.
Date: Fri, 21 Jul 2023 10:26:32 +0200

 This is a multipart message in MIME format.
 
 ------------630-1689927992714-1
 Content-Transfer-Encoding: quoted-printable
 Content-Type: text/plain; charset=UTF-8
 
 Both "gop 0" and "gop 5" work for me. Unfortunately, halfway through the bo=
 ot process, the resolution changes to a larger resolution than what I have =
 without using the "gop" command...
 
 On July 20, 2023 at 11:51:44 pm +02:00, Taylor R Campbell <riastradh@netbsd=
 .org> wrote:
 
 > Thanks!
 >=20
 > Did it have the correct resolution in NetBSD 9?
 >=20
 > Two things here:
 >=20
 > 1. This is probably an amdgpu device. Unfortunately, the amdgpu
 > driver is still experimental and not really ready. You can try it
 > by loading it in boot.cfg with the line `load=3Damdgpu', or with the
 > command `load amdgpu' on one of the `menu=3D...' lines, but be
 > prepared for crashes -- I suggest you create two menu lines, one
 > with amdgpu and one without, so after the one with crashes, you can
 > boot into the one without and savecore or dmesg to diagnose it.
 >=20
 > 2. As a stop-gap measure, you can select the EFI graphics output
 > configuration with the `gop' command at the boot loader. Type
 > plain `gop' at the bootloader prompt to list the available modes;
 > type `gop N' to select mode number N in the list.
 > 
 
 ------------630-1689927992714-1
 Content-Type: multipart/related; boundary="----------630-1689927992714-2"
 
 ------------630-1689927992714-2
 Content-Transfer-Encoding: quoted-printable
 Content-Type: text/html; charset=UTF-8
 
 <div>Both "gop 0" and "gop 5" work for me. Unfortunately, halfway through t=
 he boot process, the resolution changes to a larger resolution than what I =
 have without using the "gop" command...<br></div><div><br></div><div>On Jul=
 y 20, 2023 at 11:51:44 pm +02:00, Taylor R Campbell &lt;riastradh%netbsd.or@localhost=
 g> wrote:<br></div><blockquote type=3D"cite"><div class=3D"oneComWebmail-ma=
 il"><div class=3D"oneComWebmail-body"><div>Thanks!<br></div><div><br></div>=
 <div>Did it have the correct resolution in NetBSD 9?<br></div><div><br></di=
 v><div>Two things here:<br></div><div><br></div><div>1. This is probably an=
  amdgpu device.  Unfortunately, the amdgpu<br></div><div>driver is still ex=
 perimental and not really ready.  You can try it<br></div><div>by loading i=
 t in boot.cfg with the line `load=3Damdgpu', or with the<br></div><div>comm=
 and `load amdgpu' on one of the `menu=3D...' lines, but be<br></div><div>pr=
 epared for crashes -- I suggest you create two menu lines, one<br></div><di=
 v>with amdgpu and one without, so after the one with crashes, you can<br></=
 div><div>boot into the one without and savecore or dmesg to diagnose it.<br=
 ></div><div><br></div><div>2. As a stop-gap measure, you can select the EFI=
  graphics output<br></div><div>configuration with the `gop' command at the =
 boot loader.  Type<br></div><div>plain `gop' at the bootloader prompt to li=
 st the available modes;<br></div><div>type `gop N' to select mode number N =
 in the list.<br></div></div></div></blockquote>
 
 ------------630-1689927992714-2--
 ------------630-1689927992714-1--