Date: Thu, 17 Jan 2019 16:57:45 -0800 From: Mel Pilgrim <list_freebsd@bluerosetech.com> To: CeDeROM <cederom@tlen.pl> Cc: "freebsd-questions@FreeBSD.org" <freebsd-questions@freebsd.org> Subject: Re: UEFI loader picking wrong native resolution, documented fixes don't work Message-ID: <0329d71e-60f5-3c49-f79c-a3f6d5f6e788@bluerosetech.com> In-Reply-To: <CAFYkXj=TUGLKz4fA_J7xHyYh8Q%2Bam6BX4M0JSGGQcBJMK0wiWQ@mail.gmail.com> References: <dd871ed1-e45b-3ea1-4794-1b4d02b633bb@bluerosetech.com> <CAFYkXj=TUGLKz4fA_J7xHyYh8Q%2Bam6BX4M0JSGGQcBJMK0wiWQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/17/2019 04:35, CeDeROM wrote: > I have noticed similar problems with my AMDGPU on AMD RADEON. > Setting hw.syscons.disable=1 in /boot/loader.conf and then loading > the graphics module from rc.conf helped.. I tried that as well, but its not a productive change: - The loader still goes to 1600x1200 for the boot menu - Once boot begins, the console is disabled entirely, including the remote console, which blanks and shows "No Signal" Without it I at least have the remote console. It seems like I might need to compile a custom version of loader to force the right resolution? This seems like such an obvious thing to be able to tune. The legacy console works, but I can't use it because the boot disks are NVMe.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0329d71e-60f5-3c49-f79c-a3f6d5f6e788>