On Friday, May 10, 2024 4:28:32 PM PDT you wrote:
> On Fri, 10 May 2024, Stephen Medina wrote:
> >> [ 1.014923] genfb0: framebuffer at 0xf100, size 1024x768, depth
> >> 32,
> >> stride 4096
> >>
> >> and this tells us the resolution of the display.
> >
> > 1024 x 768
> >
> > [...]
> >
RVP wrote:
On Fri, 10 May 2024, Stephen Medina wrote:
[ 1.014923] genfb0: framebuffer at 0xf100, size 1024x768,
depth 32,
stride 4096
and this tells us the resolution of the display.
1024 x 768
[...]
So I have 48 rows and 128 columns, despite the quite low res monitor
used on
On Fri, 10 May 2024, Stephen Medina wrote:
[ 1.014923] genfb0: framebuffer at 0xf100, size 1024x768, depth 32,
stride 4096
and this tells us the resolution of the display.
1024 x 768
[...]
So I have 48 rows and 128 columns, despite the quite low res monitor
used on that console.
On Thursday, May 9, 2024 11:35:03 PM PDT you wrote:
> On Thu, May 09, 2024 at 03:14:54PM -0700, Stephen Medina wrote:
> > Hello,
> >
> > I was in the middle of my first install, about to partition my
> > drive, when sysint terminated with the error "screen too
> > narrow for menu". I am using one
On Thu, May 09, 2024 at 03:14:54PM -0700, Stephen Medina wrote:
> Hello,
>
> I was in the middle of my first install, about to partition my
> drive, when sysint terminated with the error "screen too
> narrow for menu". I am using one of those old square LCD
> monitors. Is there a way around
Hello,
I was in the middle of my first install, about to partition my
drive, when sysint terminated with the error "screen too
narrow for menu". I am using one of those old square LCD
monitors. Is there a way around this?
-Stephen
