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: <gnats-bugs%netbsd.org@localhost>
Cc: <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:13:13 +0200

 This is a multipart message in MIME format.
 
 ------------44546-1689927193415-1
 Content-Transfer-Encoding: quoted-printable
 Content-Type: text/plain; charset=UTF-8
 
 Thanks to you as well. No, I could never get the USB pen drive with 9.3 to =
 boot, so that I could install. The boot process freezes at:
 
 [9.3707708] root device:
 
 On July 20, 2023 at 11:55:02 pm +02:00, Taylor R Campbell <riastradh@netbsd=
 .org> wrote:
 
 > The following reply was made to PR port-amd64/57532; it has been noted by=
  GNATS.
 >=20
 > From: Taylor R Campbell <riastradh%NetBSD.org@localhost>
 > To: <<brian%durant.dk@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 1=
 0
 > BETA amd64 install.
 > Date: Thu, 20 Jul 2023 21:51:44 +0000
 >=20
 > 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.
 > 
 
 
 ------------44546-1689927193415-1
 Content-Type: multipart/related; boundary="----------44546-1689927193415-2"
 
 ------------44546-1689927193415-2
 Content-Transfer-Encoding: quoted-printable
 Content-Type: text/html; charset=UTF-8
 
 <div>Thanks to you as well. No, I could never get the USB pen drive with 9.=
 3 to boot, so that I could install. The boot process freezes at:<br></div><=
 div><br></div><div>[9.3707708] root device:<br></div><div><br></div><div>On=
  July 20, 2023 at 11:55:02 pm +02:00, Taylor R Campbell &lt;riastradh@netbs=
 d.org> wrote:<br></div><blockquote type=3D"cite"><div class=3D"oneComWebmai=
 l-mail"><div class=3D"oneComWebmail-body"><div>The following reply was made=
  to PR port-amd64/57532; it has been noted by GNATS.<br></div><div><br></di=
 v><div>From: Taylor R Campbell &lt;riastradh%NetBSD.org@localhost><br></div><div>To: =
 &lt;<a href=3D"mailto:brian%durant.dk@localhost";>brian%durant.dk@localhost</a>><br></div><div>C=
 c: &lt;<a href=3D"mailto:gnats-bugs%netbsd.org@localhost";>gnats-bugs%netbsd.org@localhost</a>>,=
  &lt;<a href=3D"mailto:port-amd64-maintainer%netbsd.org@localhost";>port-amd64-maintai=
 ner%netbsd.org@localhost</a>>,<br></div><div> &lt;<a href=3D"mailto:gnats-admin@netbs=
 d.org">gnats-admin%netbsd.org@localhost</a>>, &lt;<a href=3D"mailto:netbsd-bugs@netbs=
 d.org">netbsd-bugs%netbsd.org@localhost</a>><br></div><div>Subject: Re: port-amd64/57=
 532: Incorrect resolution after latest NetBSD 10<br></div><div> BETA amd64 =
 install.<br></div><div>Date: Thu, 20 Jul 2023 21:51:44 +0000<br></div><div>=
 <br></div><div>Thanks!<br></div><div><br></div><div>Did it have the correct=
  resolution in NetBSD 9?<br></div><div><br></div><div>Two things here:<br><=
 /div><div><br></div><div>1. This is probably an amdgpu device.  Unfortunate=
 ly, the amdgpu<br></div><div>driver is still experimental and not really re=
 ady.  You can try it<br></div><div>by loading it in boot.cfg with the line =
 `load=3Damdgpu', or with the<br></div><div>command `load amdgpu' on one of =
 the `menu=3D...' lines, but be<br></div><div>prepared for crashes -- I sugg=
 est you create two menu lines, one<br></div><div>with amdgpu and one withou=
 t, so after the one with crashes, you can<br></div><div>boot into the one w=
 ithout 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><d=
 iv>configuration with the `gop' command at the boot loader.  Type<br></div>=
 <div>plain `gop' at the bootloader prompt to list the available modes;<br><=
 /div><div>type `gop N' to select mode number N in the list.<br></div></div>=
 </div></blockquote><div><br></div>
 
 ------------44546-1689927193415-2--
 ------------44546-1689927193415-1--