NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: install/59485: sysinst unusable on smaller framebuffer resolutions





El 25/6/25 a las 1:05, uwe%stderr.spb.ru@localhost escribió:
Number:         59485
Category:       install
Synopsis:       sysinst unusable on smaller framebuffer resolutions
Confidential:   no
Severity:       serious
Priority:       medium
Responsible:    install-manager
State:          open
Class:          sw-bug
Submitter-Id:   net
Arrival-Date:   Tue Jun 24 23:05:00 +0000 2025
Originator:     Valery Ushakov
Release:        NetBSD 10.1
Organization:
Environment:
Description:
I was trying to install netbsd on an old intel mac mini.  Since x86
doesn't have the usual comforts of a serial console, like most
civilized machines, I had to use a monitor.  I don't have much space
on my table, but luckily I have a cute little 10" monitor that can do
1024x768, so I am using that when I need a monitor for something.

NetBSD install USB boots and attaches intelfb0 and uses it with the
8x16 font for kernel messages.  When it comes to the userland though,
it switches to a font twice as large, b/c of proliferation of hi-res
displays, but at 1024x768 it's only 64x24 terminal and that is not
enough for larger sysinst menus (e.g. paritioning), so sysinst fails
eventually, when you reach one of those.

How-To-Repeat:
Try to use sysinst on a lower resolution monitor.
Fix:
May be hi-res workaround in the driver should not be applied if the
resulting terminal will be less than 80 columns?

One can always drop to the shell prompt and do

     wsconsctl -dw font=...

and use either that 8x16 font or may be use appropriately sized
Terminus, so that you get large enough characters, but still at least
80 columns.  So it's not insurmountable for someone familiar with
NetBSD.  But potentially quite confusing to someone new.


Hi,

Just to share my experience.

The Kingston 250 GB SSD in my little (and rather slow) Acer Aspire One (Atom N455) died after just 3 years and 3 months of relatively light use (what a crappy drive).

I was updating to 2026Q1 under NetBSD 11.0_RC6 when the kernel started printing lots of disk errors (in green messages), and the system became unresponsive. I rebooted and ran fsck. I tried the update again, and before long the same errors appeared. After another reboot, the SSD had completely died — even the BIOS could no longer detect it.

I tried to resurrect the drive using the power-cycle method, but after several attempts I had no luck: one hour powered on with tape covering the data pins, then power off for 30 seconds, and repeat... I do not know if it is a silly thing, but I tried it.

Since I don't think it makes sense to spend money on a new SSD (they cost about twice as is cost before), I reinstalled the original hard drive that came with the laptop.

I booted the RC6 installer, and sysinst showed the same error about the large font and the limited number of screen columns.

I solved it with:

wsconsctl -dw font=Boldface

if I remember correctly.

It's a bit tricky for newcomers. For someone trying NetBSD for the first time, this could easily be the point where they give up if they aren't persistent enough.

Thanks,
Ramiro









Home | Main Index | Thread Index | Old Index