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

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

On July 21, 2023 at 2:05:02 pm +02:00, Taylor R Campbell <riastradh%netbsd.org@localhost> wrote:

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

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 10

BETA amd64 install.

Date: Fri, 21 Jul 2023 12:00:19 +0000

Date: Fri, 21 Jul 2023 13:57:34 +0200

From: "Brian Durant" <brian%durant.dk@localhost>

=20

On July 21, 2023 at 1:31:32 pm +02:00, Taylor R Campbell <riastradh@netbs=

d.org> wrote:

=20

1. Was that with or without loading amdgpu?

Without. Not sure of the syntax for adding your suggestion to boot.cfg. I=

tried the following, but it doesn't seem to have and effect on the resolut=

ion:

menu=3DBoot AMDGPU:load=3Damdpgu;boot

Sorry, the syntax is different at the top level and in a menu command.

In the menu command (and at the bootloader prompt) it takes a space,

not an equals sign:

menu=3DBoot AMDGPU:load amdgpu;boot

I have now been running my computer for four hours without a single crash, in what I am assuming is with the amdgpu driver loaded. The only thing that I know that I did to arrive at this state, was to boot with my malformed boot.cfg line, then reboot to the boot prompt, first inputting "gop", then "gop 0", and then "boot". I both tried to view videos (without sound, as I don't know how to get my Behringer USB sound card working with uaudio), viewed various websites, installed software on the command line, in other words everything that I could think of. Not a single twitch or crash...