Re: sysint crash
64 columns On Fri, May 10, 2024 at 2:35 AM Martin Husemann 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 of those old square LCD > > monitors. Is there a way around this? > > Tell us more about the machine this happened on. Sysinst requires at least > 80 columns and 24 rows (which seems reasonable). If your architecture's > kernel does not come with fonts to allow for that, we need to add them. > > What is the resolution of your display and what kernel are you booting? > > You can boot the installer, exit installation and use e.g. > > dmesg | more > > to find more details. An example for on of my machines would be: > > [ 1.00] NetBSD 10.0_STABLE (EMMAS) #7: Sun Apr 28 16:05:18 CEST > 2024 > [ 1.00] mar...@seven-days-to-the-wolves.aprisoft.de: > /work/src-10/sys/arch/amd64/compile/EMMAS > > this lines tell us architecture and kernel used. > > [ 1.014923] genfb0: framebuffer at 0xf100, size 1024x768, depth > 32, stride 4096 > > and this tells us the resolution of the display. > > You can check the text resolution by > > stty -a > > which for me outputs: > > speed 9600 baud; 48 rows; 128 columns; queue = 2048; line = termios; > lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl > -echoprt -altwerase -noflsh -tostop -flusho pendin -nokerninfo > -extproc > iflags: -istrip icrnl -inlcr -igncr ixon -ixoff ixany imaxbel -ignbrk > brkint -inpck -ignpar -parmrk > oflags: opost onlcr -ocrnl -oxtabs -onocr -onlret > cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -mdmbuf > -cdtrcts > cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = ; > eol2 = ; erase = ^?; intr = ^C; kill = ^U; lnext = ^V; > min = 1; quit = ^\; reprint = ^R; start = ^Q; status = ^T; > stop = ^S; susp = ^Z; time = 0; werase = ^W; > > > So I have 48 rows and 128 columns, despite the quite low res monitor > used on that console. > > Martin > -- Identity is Fleeting // Speak the Truth you Know in your Heart
Re: sysint crash
man yall gotaa have a straight CLI option for the install or something.. i know you are moving towards something, but i really like simple On Fri, May 10, 2024 at 2:22 AM 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 this? > > -Stephen > > -- Identity is Fleeting // Speak the Truth you Know in your Heart
Re: sysint crash
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 > > > > [...] > > > >> So I have 48 rows and 128 columns, despite the quite low res monitor > >> used on that console. > > > > I get 24 rows and 64 columns! Too low it seems. Do I need a different > > monitor? > In some cases, the kernel picks the wrong font size. Try a smaller one: > > https://mail-index.netbsd.org/netbsd-users/2024/04/11/msg030909.html > > -RVP Yeap, this did it: wsconsctl -dw font=Boldface It loaded a smaller font and sysint was able to continue. Thanks.
Re: sysint crash
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 that console. I get 24 rows and 64 columns! Too low it seems. Do I need a different monitor? In some cases, the kernel picks the wrong font size. Try a smaller one: https://mail-index.netbsd.org/netbsd-users/2024/04/11/msg030909.html -RVP How he can change it from the level of system installer ?!
Re: sysint crash
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. I get 24 rows and 64 columns! Too low it seems. Do I need a different monitor? In some cases, the kernel picks the wrong font size. Try a smaller one: https://mail-index.netbsd.org/netbsd-users/2024/04/11/msg030909.html -RVP
Re: sysint crash
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 of those old square LCD > > monitors. Is there a way around this? > > Tell us more about the machine this happened on. Sysinst requires at least > 80 columns and 24 rows (which seems reasonable). If your architecture's > kernel does not come with fonts to allow for that, we need to add them. > > What is the resolution of your display and what kernel are you booting? > > You can boot the installer, exit installation and use e.g. > > dmesg | more > > to find more details. An example for on of my machines would be: > > [ 1.00] NetBSD 10.0_STABLE (EMMAS) #7: Sun Apr 28 16:05:18 CEST 2024 > [ 1.00] > mar...@seven-days-to-the-wolves.aprisoft.de:/work/src-10/sys/arch/amd64/com > pile/EMMAS > > this lines tell us architecture and kernel used. amd64 GENERIC > [ 1.014923] genfb0: framebuffer at 0xf100, size 1024x768, depth 32, > stride 4096 > > and this tells us the resolution of the display. 1024 x 768 > You can check the text resolution by > > stty -a > > which for me outputs: > > speed 9600 baud; 48 rows; 128 columns; queue = 2048; line = termios; > lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl > -echoprt -altwerase -noflsh -tostop -flusho pendin -nokerninfo > -extproc > iflags: -istrip icrnl -inlcr -igncr ixon -ixoff ixany imaxbel -ignbrk > brkint -inpck -ignpar -parmrk > oflags: opost onlcr -ocrnl -oxtabs -onocr -onlret > cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -mdmbuf > -cdtrcts > cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = ; > eol2 = ; erase = ^?; intr = ^C; kill = ^U; lnext = ^V; > min = 1; quit = ^\; reprint = ^R; start = ^Q; status = ^T; > stop = ^S; susp = ^Z; time = 0; werase = ^W; > > > So I have 48 rows and 128 columns, despite the quite low res monitor > used on that console. I get 24 rows and 64 columns! Too low it seems. Do I need a different monitor? > Martin
Re: sysint crash
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 this? Tell us more about the machine this happened on. Sysinst requires at least 80 columns and 24 rows (which seems reasonable). If your architecture's kernel does not come with fonts to allow for that, we need to add them. What is the resolution of your display and what kernel are you booting? You can boot the installer, exit installation and use e.g. dmesg | more to find more details. An example for on of my machines would be: [ 1.00] NetBSD 10.0_STABLE (EMMAS) #7: Sun Apr 28 16:05:18 CEST 2024 [ 1.00] mar...@seven-days-to-the-wolves.aprisoft.de:/work/src-10/sys/arch/amd64/compile/EMMAS this lines tell us architecture and kernel used. [ 1.014923] genfb0: framebuffer at 0xf100, size 1024x768, depth 32, stride 4096 and this tells us the resolution of the display. You can check the text resolution by stty -a which for me outputs: speed 9600 baud; 48 rows; 128 columns; queue = 2048; line = termios; lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl -echoprt -altwerase -noflsh -tostop -flusho pendin -nokerninfo -extproc iflags: -istrip icrnl -inlcr -igncr ixon -ixoff ixany imaxbel -ignbrk brkint -inpck -ignpar -parmrk oflags: opost onlcr -ocrnl -oxtabs -onocr -onlret cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -mdmbuf -cdtrcts cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = ; eol2 = ; erase = ^?; intr = ^C; kill = ^U; lnext = ^V; min = 1; quit = ^\; reprint = ^R; start = ^Q; status = ^T; stop = ^S; susp = ^Z; time = 0; werase = ^W; So I have 48 rows and 128 columns, despite the quite low res monitor used on that console. Martin
sysint crash
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
