NetBSD Problem Report #52454

From www@NetBSD.org  Wed Aug  2 13:50:37 2017
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (verified OK))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 376267A179
	for <gnats-bugs@gnats.NetBSD.org>; Wed,  2 Aug 2017 13:50:37 +0000 (UTC)
Message-Id: <20170802135036.84CC77A288@mollari.NetBSD.org>
Date: Wed,  2 Aug 2017 13:50:36 +0000 (UTC)
From: feodor@logd.fr
Reply-To: feodor@logd.fr
To: gnats-bugs@NetBSD.org
Subject: wsconsctl font size manipulation on amd64 arch
X-Send-Pr-Version: www-1.0

>Number:         52454
>Category:       port-amd64
>Synopsis:       wsconsctl font size manipulation on amd64 arch
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    port-amd64-maintainer
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Wed Aug 02 13:55:00 +0000 2017
>Last-Modified:  Tue Aug 15 14:25:00 +0000 2017
>Originator:     feodor
>Release:        7.1
>Organization:
logd.fr
>Environment:
netBSD 7.1 NetBSD 7.1 (GENERIC.201703111743Z) amd64
>Description:
So, i've found this issue : there is visibly no way to change the getty console font with wsconsctl on NetBSD 7.1 amd64 arch. Knowing that wsconsctl is a tool made for that (among other)

This is not really ergonomic to use the basic font, especially on a virtual machine or something like that (on all smalls displays).
>How-To-Repeat:
Just try to change the font with something like that :
wsfontload -N myfont  font.file
wsconsctl -dw font=myfont

(fonts are located in /usr/share/wscons/fonts)
>Fix:
I've found nothing to fixe it except to use NetBSD 7.1 i386. The tool is pefectly working on this arch.

>Audit-Trail:
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: port-amd64/52454: wsconsctl font size manipulation on amd64 arch
Date: Wed, 2 Aug 2017 16:21:15 +0200

 Please provide the dmesg output (or /var/run/dmesg.boot) of the machine
 where it is not working. This depends on the console driver (or framebuffer)
 used, so we need more details.

 Martin

From: feodor <feodor@logd.fr>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: port-amd64/52454: wsconsctl font size manipulation on amd64
 arch
Date: Wed, 2 Aug 2017 17:01:13 +0200

 On Wed,  2 Aug 2017 14:25:00 +0000 (UTC)
 Martin Husemann <martin@duskware.de> wrote:

 > The following reply was made to PR port-amd64/52454; it has been
 > noted by GNATS.
 > 
 > From: Martin Husemann <martin@duskware.de>
 > To: gnats-bugs@NetBSD.org
 > Cc: 
 > Subject: Re: port-amd64/52454: wsconsctl font size manipulation on
 > amd64 arch Date: Wed, 2 Aug 2017 16:21:15 +0200
 > 
 >  Please provide the dmesg output (or /var/run/dmesg.boot) of the
 > machine where it is not working. This depends on the console driver
 > (or framebuffer) used, so we need more details.
 >  
 >  Martin
 >  

 This is really a different frambuffer between amd64 and i386 arch ? In
 that case, why ? My two tests are on the same virtual machine.


 Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004,
 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016,
 2017 The NetBSD Foundation, Inc.  All rights reserved.
 Copyright (c) 1982, 1986, 1989, 1991, 1993
     The Regents of the University of California.  All rights reserved.

 NetBSD 7.1 (GENERIC.201703111743Z)
 total memory = 255 MB
 avail memory = 230 MB
 kern.module.path=/stand/amd64/7.1/modules
 timecounter: Timecounters tick every 10.000 msec
 timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
 innotek GmbH VirtualBox (1.2)
 mainbus0 (root)
 ACPI: RSDP 0xe0000 000024 (v02 VBOX  )
 ACPI: XSDT 0xfff0030 00003C (v01 VBOX   VBOXXSDT 00000001 ASL  00000061)
 ACPI: FACP 0xfff00f0 0000F4 (v04 VBOX   VBOXFACP 00000001 ASL  00000061)
 ACPI: DSDT 0xfff0470 001BF1 (v01 VBOX   VBOXBIOS 00000002 INTL 20140926)
 ACPI: FACS 0xfff0200 000040
 ACPI: APIC 0xfff0240 000054 (v02 VBOX   VBOXAPIC 00000001 ASL  00000061)
 ACPI: SSDT 0xfff02a0 0001CC (v01 VBOX   VBOXCPUT 00000002 INTL 20140926)
 ACPI: All ACPI Tables successfully acquired
 ioapic0 at mainbus0 apid 1: pa 0xfec00000, version 0x11, 24 pins
 cpu0 at mainbus0 apid 0: Intel(R) Core(TM) i5-4460  CPU @ 3.20GHz, id
 0x306c3 acpi0 at mainbus0: Intel ACPICA 20131218
 acpi0: X/RSDT: OemId <VBOX  ,VBOXXSDT,00000001>, AslId <ASL ,00000061>
 acpi0: SCI interrupting at int 9
 timecounter: Timecounter "ACPI-Safe" frequency 3579545 Hz quality 900
 pckbc1 at acpi0 (PS2K, PNP0303) (kbd port): io 0x60,0x64 irq 1
 pckbc2 at acpi0 (PS2M, PNP0F03) (aux port): irq 12
 LPT (PNP0400) at acpi0 not configured
 attimer1 at acpi0 (TIMR, PNP0100): io 0x40-0x43,0x50-0x53
 acpivga0 at acpi0 (GFX0): ACPI Display Adapter
 acpiout0 at acpivga0 (VGA, 0x0100): ACPI Display Output Device
 acpivga0: connected output devices:
 acpivga0:   0x0100 (acpiout0): VGA Analog Monitor, index 0, port 0,
 head 0 acpiacad0 at acpi0 (AC, ACPI0003-0): ACPI AC Adapter
 ACPI: Enabled 2 GPEs in block 00 to 07
 ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_]
 (20131218/hwxface-646) ACPI Exception: AE_NOT_FOUND, While evaluating
 Sleep State [\_S2_] (20131218/hwxface-646) ACPI Exception:
 AE_NOT_FOUND, While evaluating Sleep State [\_S3_]
 (20131218/hwxface-646) ACPI Exception: AE_NOT_FOUND, While evaluating
 Sleep State [\_S4_] (20131218/hwxface-646) pckbd0 at pckbc1 (kbd slot)
 pckbc1: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard
 pms0 at pckbc1 (aux slot)
 pckbc1: using irq 12 for aux slot
 wsmouse0 at pms0 mux 0
 pci0 at mainbus0 bus 0: configuration mode 1
 pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
 pchb0 at pci0 dev 0 function 0: vendor 0x8086 product 0x1237 (rev. 0x02)
 pcib0 at pci0 dev 1 function 0: vendor 0x8086 product 0x7000 (rev. 0x00)
 piixide0 at pci0 dev 1 function 1: Intel 82371AB IDE controller (PIIX4)
 (rev. 0x01) piixide0: bus-master DMA support present
 piixide0: primary channel configured to compatibility mode
 piixide0: primary channel interrupting at ioapic0 pin 14
 atabus0 at piixide0 channel 0
 piixide0: secondary channel configured to compatibility mode
 piixide0: secondary channel interrupting at ioapic0 pin 15
 atabus1 at piixide0 channel 1
 genfb0 at pci0 dev 2 function 0: vendor 0x80ee product 0xbeef (rev.
 0x00) genfb0: framebuffer at 0xe0000000, size 1024x768, depth 8, stride
 1024 wsdisplay0 at genfb0 kbdmux 1: console (default, vt100 emulation),
 using wskbd0 wsmux1: connecting to wsdisplay0
 drm at genfb0 not configured
 wm0 at pci0 dev 3 function 0: Intel i82540EM 1000BASE-T Ethernet (rev.
 0x02) wm0: interrupting at ioapic0 pin 19
 wm0: 32-bit 33MHz PCI bus
 wm0: 64 words (6 address bits) MicroWire EEPROM
 wm0: Ethernet address 08:00:27:a5:84:da
 wm0: MDIC read timed out: phy 0 reg 1
 makphy0 at wm0 phy 1: Marvell 88E1011 Gigabit PHY, rev. 4
 makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 vendor 0x80ee product 0xcafe (miscellaneous system) at pci0 dev 4
 function 0 not configured auich0 at pci0 dev 5 function 0: i82801AA
 (ICH) AC-97 Audio auich0: interrupting at ioapic0 pin 21
 auich0: ac97: SigmaTel STAC9700 codec; no 3D stereo
 auich0: ac97: ext id 0x809<AC97_23,VRM,VRA>
 ohci0 at pci0 dev 6 function 0: vendor 0x106b product 0x003f (rev. 0x00)
 ohci0: interrupting at ioapic0 pin 22
 ohci0: OHCI version 1.0
 usb0 at ohci0: USB revision 1.0
 piixpm0 at pci0 dev 7 function 0: vendor 0x8086 product 0x7113 (rev.
 0x08) piixpm0: SMBus disabled
 isa0 at pcib0
 pcppi0 at isa0 port 0x61
 midi0 at pcppi0: PC speaker
 sysbeep0 at pcppi0
 attimer1: attached to pcppi0
 acpicpu0 at cpu0: ACPI CPU
 acpicpu0: C1: HLT, lat   0 us, pow     0 mW
 timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
 acpiacad0: AC adapter online.
 auich0: measured ac97 link rate at 52363 Hz, will use 52000 Hz
 audio0 at auich0: full duplex, playback, capture, mmap, independent
 IPsec: Initialized Security Association Processing.
 uhub0 at usb0: vendor 0x106b OHCI root hub, class 9/0, rev 1.00/1.00,
 addr 1 uhub0: 8 ports with 8 removable, self powered
 wd0 at atabus0 drive 0
 wd0: <VBOX HARDDISK>
 wd0: drive supports 128-sector PIO transfers, LBA addressing
 wd0: 5120 MB, 10402 cyl, 16 head, 63 sec, 512 bytes/sect x 10485760
 sectors wd0: 32-bit data port
 wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
 wd0(piixide0:0:0): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33) (using
 DMA) atapibus0 at atabus1: 2 targets
 cd0 at atapibus0 drive 0: <VBOX CD-ROM, VB2-01700376, 1.0> cdrom
 removable cd0: 32-bit data port
 cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
 cd0(piixide0:1:0): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33) (using
 DMA) Kernelized RAIDframe activated
 pad0: outputs: 44100Hz, 16-bit, stereo
 audio1 at pad0: half duplex, playback, capture
 boot device: wd0
 root on wd0a dumps on wd0b
 root file system type: ffs
 wsdisplay0: screen 1 added (default, vt100 emulation)
 wsdisplay0: screen 2 added (default, vt100 emulation)
 wsdisplay0: screen 3 added (default, vt100 emulation)
 wsdisplay0: screen 4 added (default, vt100 emulation)

From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc: feodor@logd.fr
Subject: Re: port-amd64/52454: wsconsctl font size manipulation on amd64 arch
Date: Thu, 3 Aug 2017 10:05:46 +0200

 On Wed, Aug 02, 2017 at 04:35:01PM +0000, feodor wrote:
 >  This is really a different frambuffer between amd64 and i386 arch ? In
 >  that case, why ?

 No, not usually - but something goes wrong somewhere and so far we have
 no idea what and where. Fontload failure may be driver specific, so
 different drivers for console would be an easy explanation for the
 difference.

 > My two tests are on the same virtual machine.

 You did not mention that before (or I overlooked it).

 >  genfb0 at pci0 dev 2 function 0: vendor 0x80ee product 0xbeef (rev.
 >  0x00) genfb0: framebuffer at 0xe0000000, size 1024x768, depth 8, stride
 >  1024 wsdisplay0 at genfb0 kbdmux 1: console (default, vt100 emulation),
 >  using wskbd0 wsmux1: connecting to wsdisplay0
 >  drm at genfb0 not configured

 Is this part the same when booting i386?

 Martin

From: feodor <feodor@logd.fr>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: port-amd64/52454: wsconsctl font size manipulation on amd64
 arch
Date: Sun, 6 Aug 2017 08:43:08 +0200

 On Thu,  3 Aug 2017 08:10:01 +0000 (UTC)
 Martin Husemann <martin@duskware.de> wrote:

 > The following reply was made to PR port-amd64/52454; it has been
 > noted by GNATS.
 > 
 > From: Martin Husemann <martin@duskware.de>
 > To: gnats-bugs@NetBSD.org
 > Cc: feodor@logd.fr
 > Subject: Re: port-amd64/52454: wsconsctl font size manipulation on
 > amd64 arch Date: Thu, 3 Aug 2017 10:05:46 +0200
 > 
 >  On Wed, Aug 02, 2017 at 04:35:01PM +0000, feodor wrote:
 >  >  This is really a different frambuffer between amd64 and i386
 >  > arch ? In that case, why ?
 >  
 >  No, not usually - but something goes wrong somewhere and so far we
 > have no idea what and where. Fontload failure may be driver specific,
 > so different drivers for console would be an easy explanation for the
 >  difference.
 >  
 >  > My two tests are on the same virtual machine.
 >  
 >  You did not mention that before (or I overlooked it).

 Yes forgot this detail, my bad.

 >  >  genfb0 at pci0 dev 2 function 0: vendor 0x80ee product 0xbeef
 >  > (rev. 0x00) genfb0: framebuffer at 0xe0000000, size 1024x768,
 >  > depth 8, stride 1024 wsdisplay0 at genfb0 kbdmux 1: console
 >  > (default, vt100 emulation), using wskbd0 wsmux1: connecting to
 >  > wsdisplay0 drm at genfb0 not configured
 >  
 >  Is this part the same when booting i386?

 So, what you ask :

 genfb0 at pci0 dev 2 function 0: vendor 0x80ee product 0xbeef (rev.
 0x00) genfb0: framebuffer at 0xe0000000, size 1024x768, depth 8, stride
 1024 wsdisplay0 at genfb0 kbdmux 1: console (default, vt100 emulation),
 using wskbd0 wsmux1: connecting to wsdisplay0
 drm at genfb0 not configured

 If i see well, this is the same report.

 >  Martin
 >  

 Sorry for the delay, not simple every week.
 I will reply faster next time.

 feodor

From: feodor <feodor@logd.fr>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: port-amd64/52454: wsconsctl font size manipulation on amd64
 arch
Date: Tue, 15 Aug 2017 15:59:53 +0200

 Hello here !

 So, nothing new ?

From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: port-amd64/52454: wsconsctl font size manipulation on amd64 arch
Date: Tue, 15 Aug 2017 16:23:13 +0200

 It works for me in -current (with vesa/genfb on amd64), and I guess it
 would work in NetBSD 8 beta as well.

 Martin

Home	PR Database Search