Re: FYI about console sizes

>> https://www.klos.com/~john/install_dmesg.txt
>
> I am confused - this is how it should look like [on a 80x24 char display]:
>
> and the variable string part is restricted, it is "%s (%s, %s)"
> with the first %s being the device name, the second (size) limited to 4 char,
> and the last %s in this case the model name from the 40 char atap_model
> field of struct ataparams:
>
> 	https://nxr.netbsd.org/xref/src/sys/dev/ata/atareg.h#310
>
> That can't overflow the available width.
>
> Or did I misunderstand you and some other device (not a wd*) caused it?

Here's the list when it works, using "userconf disable radeon" to get a 
denser font size:

https://www.klos.com/~john/disklist.jpg

That disk looks like this on a running system:

[ 12736.243100] umass0 at uhub5 port 1 configuration 1 interface 0
[ 12736.243100] umass0: Phison Electronics Corp. (0x13fe) USB DISK 2.0 (0x4300), rev 2.00/1.00, addr 2
[ 12736.243100] umass0: using SCSI over Bulk-Only
[ 12736.243100] scsibus0 at umass0: 2 targets, 1 lun per target
[ 12736.703101] sd0 at scsibus0 target 0 lun 0: <, USB DISK 2.0, PMAP> disk removable
[ 12736.753101] sd0: 3714 MB, 932 cyl, 255 head, 32 sec, 512 bytes/sect x 7606272 sectors
[ 12736.763099] sd0: GPT GUID: 5ad98a10-20a0-4931-a0b6-846498729bdc
[ 12736.763099] dk3 at sd0: "EFI system", 262144 blocks at 2048, type: msdos
[ 12736.763099] dk4 at sd0: "30d9ef0a-5c3f-495e-a294-997ba491d48d", 4341760 blocks at 264192, type: ffs

So it's the installer USB stick that's causing it. But from where does 
that bizarre string come from?

It may be worth noting that the entire 4 gig USB stick was zeroed before 
writing the installation image.

Ideas?

Thanks,
John