> -----Original Message-----
> From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf
> Of Stuart Henderson
> Sent: Saturday, June 25, 2022 6:21 AM
> On 2022-06-24, Ted Wynnychenko <ted....@comcast.net> wrote:
> > Hello
> > When there is a boot.conf file present in /etc with only the
> following:
> >> stty com0 115200
> >
>
> So in this case the serial output during boot is only coming from a
> serial-port redirector in the bios, the "stty com0 115200" probably
> doesn't change anything, and the serial output in multiuser is via
> init / /etc/ttys
>
> > Now, if I change boot.conf to direct output to the serial terminal
> with:
> >> stty com0 115200
> >> set tty com0
> >
> So far that is expected, OpenBSD doesn't support dual serial+glass
> console
>
> > Then, the three wsconsctl error messages appear, and it ends with a
> login
> > prompt on the serial console (tty0) ONLY.
> >
> > The screen and keyboard for ttyC0 are dead. There is no login
> prompt, and
> > the keyboard is not functional.
>
> Assuming ttys is setup to run a login on ttyC0 that is not expected
>
>
> Can you try kernels between known-good and known-bad (or maybe you have
> something in /var/log/messages*gz) and look for when this started
> appearing?
>
Unfortunately, I have not checked the ttyC0 display in a long time.
When I was updating to current, I also did not specifically check for a
login prompt on ttyC0 BEFORE the update to current.
However, I think that I did notice that there was no login prompt when I
plugged in the display, just before it switched to the bios pages.
My last update was in July 2021.
> A diff of dmesg between serial and non-serial boots might give some
> clues
>
> This maybe implicated:
>
> >> vga1 at pci3 dev 3 function 0 "Matrox MGA G200eW" rev 0x0a
> >> wsdisplay at vga1 not configured
>
I booted in three configurations.
With the boot.conf NOT including "set tty com0" AND a monitor and keyboard
attached, dmesg shows:
109,110c110
< wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
< wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
136c136
< wskbd0 at pckbd0: console keyboard, using wsdisplay0
148d147
< wskbd1: connecting to wsdisplay0
153d151
< wskbd2: connecting to wsdisplay0
With boot.conf including "set tty com0" AND a monitor and keyboard attached,
dmesg shows:
62a63
> com0: console
109,110c110
> wsdisplay at vga1 not configured
136c136
> wskbd0 at pckbd0 mux 1
When boot.conf including "set tty com0" and without a monitor or keyboard,
the dmesg is the same as the "serial" dmesg with them connected, except for
missing information about the keyboard:
144,152d143
< uhidev0 at uhub3 port 1 configuration 1 interface 0 "Primax Electronics
USB Keyboard" rev 2.00/1.00 addr 3
< uhidev0: iclass 3/1
< ukbd0 at uhidev0: 8 variable keys, 6 key codes
< wskbd1 at ukbd0 mux 1
< uhidev1 at uhub3 port 1 configuration 1 interface 1 "Primax Electronics
USB Keyboard" rev 2.00/1.00 addr 3
< uhidev1: iclass 3/0, 2 report ids
< ucc0 at uhidev1 reportid 1: 24 usages, 13 keys, enum
< wskbd2 at ucc0 mux 1
< uhid0 at uhidev1 reportid 2: input=1, output=0, feature=0
I don't know what this means. It seems that when boot.conf redirects to the
com0 console, the vga connection does not get configured by OpenBSD on boot.
That would explain why no login prompt is presented there later by init,
even though the terminal is defined in ttys.
Although it has been a few years, I feel certain that a login prompt was
displayed on both the serial line and ttyC0 when I originally redirected
output with "set tty com0" in boot.conf.
I am pretty sure my detail orientated personality would have immediately
flagged the discrepancy from what was documented if it had not, and I would
have brought up the issue way back then.
Thanks
Ted
>
>
> >> -----Original Message-----
> >> From: Ted Wynnychenko
> >> Sent: Thursday, June 23, 2022 5:19 PM
> >> To: misc@openbsd.org
> >> Subject: No login prompt on console ttyC0 after boot
> >>
> >> Hello
> >>
> >> I have been following current since 5.6, and had been pretty good
> about
> >> updates until this last year (issues not related).
> >>
> >> Anyway, I asked about updating, found some suggestions that it would
> >> work,
> >> and decided to blaze ahead. And, it basically worked.
> >> I have a few things to clean up, but overall the update to current
> from
> >> my
> >> last update in July 2021 went well.
> >>
> >> However, in planning for this, I decided to hook up a monitor and
> >> keyboard
> >> directly, as I have basically just used a serial console ever since
> I
> >> first installed the systems at 5.6.
> >>
> >> Unfortunately, I did not look at the monitor before updating to
> current
> >> (OpenBSD 7.1-current (GENERIC.MP) #587: Fri Jun 17 08:49:40 MDT 2022
> -
> >> full DMESG below), but after the update I found that there is no
> login
> >> prompt on the monitor (ttyC0), and the keyboard does not do anything
> (I
> >> cannot ALT-CTRL-F2 to change to another virtual console.
> >>
> >> I don't know when this happened, since I haven't attached a
> >> monitor/keyboard in a very long time.
> >> But, now that I know, I am trying to fix it, but can't seem to
> >> understand
> >> why/how to do so.
> >>
> >> When the machine boots, the monitor and keyboard work, and I can
> access
> >> the bios pages and make changes.
> >>
> >> Then, if I allow the boot to start, I get the "switching to com0"
> >> message,
> >> and that's it.
> >>
> >> When the boot is complete, I can access the system using a serial
> >> console
> >> (tty00) or ssh, but the direct monitor shows nothing after
> "switching
> >> to
> >> com0," and the keyboard does nothing.
> >>
> >> The /etc/boot.conf file correctly routes things to the serial
> console:
> >> stty com0 115200
> >> set tty com0
> >>
> >> I have not changed /etc/ttys in a long time:
> >> #
> >> # $OpenBSD: ttys,v 1.2 2008/01/09 17:39:42 miod Exp $
> >> #
> >> # name getty type status
> >> comments
> >> #
> >> console "/usr/libexec/getty std.9600" vt220 off secure
> >> ttyC0 "/usr/libexec/getty std.9600" vt220 on secure
> >> ttyC1 "/usr/libexec/getty std.9600" vt220 on secure
> >> ttyC2 "/usr/libexec/getty std.9600" vt220 on secure
> >> ttyC3 "/usr/libexec/getty std.9600" vt220 on secure
> >> ttyC4 "/usr/libexec/getty std.9600" vt220 off secure
> >> ttyC5 "/usr/libexec/getty std.9600" vt220 on secure
> >> ttyC6 "/usr/libexec/getty std.9600" vt220 off secure
> >> ttyC7 "/usr/libexec/getty std.9600" vt220 off secure
> >> ttyC8 "/usr/libexec/getty std.9600" vt220 off secure
> >> ttyC9 "/usr/libexec/getty std.9600" vt220 off secure
> >> ttyCa "/usr/libexec/getty std.9600" vt220 off secure
> >> ttyCb "/usr/libexec/getty std.9600" vt220 off secure
> >> tty00 "/usr/libexec/getty autologin" vt220 on secure
> >> tty01 "/usr/libexec/getty std.9600" unknown off
> >> tty02 "/usr/libexec/getty std.9600" unknown off
> >> tty03 "/usr/libexec/getty std.9600" unknown off
> >> tty04 "/usr/libexec/getty std.9600" unknown off
> >> tty05 "/usr/libexec/getty std.9600" unknown off
> >> tty06 "/usr/libexec/getty std.9600" unknown off
> >> tty07 "/usr/libexec/getty std.9600" unknown off
> >> ....
> >>
> >>
> >> I also noticed these errors in DMESG-S:
> >> ...
> >> /dev/sd2g (be3bcca0ef32a6bd.g): file system is clean; not checking
> >> wsconsctl: /dev/ttyC0: Device not configured
> >> wsconsctl: /dev/ttyC0: Device not configured
> >> wsconsctl: /dev/ttyC0: Device not configured
> >> pf enabled
> >> ...
> >>
> >> The wsconsctl.conf file has also not been changed in a long time,
> and
> >> only
> >> had three things enabled:
> >>
> >> display.vblank=on # enable vertical sync blank for
> screen
> >> burner
> >> display.screen_off=60000 # set screen burner timeout to 60
> >> seconds
> >> display.kbdact=on # restore on keyboard input
> >>
> >> If I comment out the three parameters above, then "Device not
> >> configured"
> >> messages disappear, but there is still no login prompt on the ttyC0
> >> monitor, and the keyboard still does not appear to function (I still
> >> cannot change virtual consoles).
> >>
> >> As far as I can tell, there should be a login prompt on ttyC0, but
> >> there
> >> is not.
> >> What am I missing? (Or, what did I miss when following current
> since
> >> 5.6
> >> that may have changed?)
> >>
> >> Thanks
> >> Ted
> >>
> >>
> >>
> >>
> >> DMESG:
> >>
> >> OpenBSD 7.1-current (GENERIC.MP) #587: Fri Jun 17 08:49:40 MDT 2022
> >>
> >> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> >> real mem = 4249260032 (4052MB)
> >> avail mem = 4103114752 (3913MB)
> >> random: good seed from bootblocks
> >> mpath0 at root
> >> scsibus0 at mpath0: 256 targets
> >> mainbus0 at root
> >> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb5a0 (55 entries)
> >> bios0: vendor American Megatrends Inc. version "2.3a" date
> 01/06/2021
> >> bios0: Supermicro X9SCL/X9SCM
> >> acpi0 at bios0: ACPI 5.0
> >> acpi0: sleep states S0 S1 S4 S5
> >> acpi0: tables DSDT FACP APIC FPDT MCFG HPET SSDT SSDT SSDT SPCR EINJ
> >> ERST
> >> HEST BERT
> >> acpi0: wakeup devices UAR1(S4) UAR2(S4) P0P1(S4) USB1(S4) USB2(S4)
> >> USB3(S4) USB4(S4) USB5(S4) USB6(S4) USB7(S4) RP01(S4) PXSX(S4)
> RP02(S4)
> >> PXSX(S4) RP03(S4) PXSX(S4) [...]
> >> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> >> acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
> >> cpu0 at mainbus0: apid 0 (boot processor)
> >> cpu0: Intel(R) Core(TM) i3-3220T CPU @ 2.80GHz, 2800.47 MHz, 06-3a-
> 09
> >> cpu0:
> >>
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36
> >> ,CF
> >>
> LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,D
> >> S-C
> >>
> PL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,
> >> XSA
> >>
> VE,AVX,F16C,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,
> >> IBR
> >> S,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
> >> cpu0: 256KB 64b/line 8-way L2 cache
> >> cpu0: smt 0, core 0, package 0
> >> mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
> >> cpu0: apic clock running at 100MHz
> >> cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE
> >> cpu1 at mainbus0: apid 2 (application processor)
> >> cpu1: Intel(R) Core(TM) i3-3220T CPU @ 2.80GHz, 2800.04 MHz, 06-3a-
> 09
> >> cpu1:
> >>
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36
> >> ,CF
> >>
> LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,D
> >> S-C
> >>
> PL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,
> >> XSA
> >>
> VE,AVX,F16C,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,
> >> IBR
> >> S,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
> >> cpu1: 256KB 64b/line 8-way L2 cache
> >> cpu1: smt 0, core 1, package 0
> >> cpu2 at mainbus0: apid 1 (application processor)
> >> cpu2: Intel(R) Core(TM) i3-3220T CPU @ 2.80GHz, 2800.03 MHz, 06-3a-
> 09
> >> cpu2:
> >>
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36
> >> ,CF
> >>
> LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,D
> >> S-C
> >>
> PL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,
> >> XSA
> >>
> VE,AVX,F16C,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,
> >> IBR
> >> S,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
> >> cpu2: 256KB 64b/line 8-way L2 cache
> >> cpu2: smt 1, core 0, package 0
> >> cpu3 at mainbus0: apid 3 (application processor)
> >> cpu3: Intel(R) Core(TM) i3-3220T CPU @ 2.80GHz, 2800.03 MHz, 06-3a-
> 09
> >> cpu3:
> >>
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36
> >> ,CF
> >>
> LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,D
> >> S-C
> >>
> PL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,DEADLINE,
> >> XSA
> >>
> VE,AVX,F16C,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,MD_CLEAR,
> >> IBR
> >> S,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN
> >> cpu3: 256KB 64b/line 8-way L2 cache
> >> cpu3: smt 1, core 1, package 0
> >> ioapic0 at mainbus0: apid 2 pa 0xfec00000, version 20, 24 pins
> >> acpimcfg0 at acpi0
> >> acpimcfg0: addr 0xe0000000, bus 0-255
> >> acpihpet0 at acpi0: 14318179 Hz
> >> acpiprt0 at acpi0: bus 0 (PCI0)
> >> acpiprt1 at acpi0: bus 3 (P0P1)
> >> acpiprt2 at acpi0: bus 1 (RP01)
> >> acpiprt3 at acpi0: bus -1 (RP02)
> >> acpiprt4 at acpi0: bus -1 (RP03)
> >> acpiprt5 at acpi0: bus -1 (RP04)
> >> acpiprt6 at acpi0: bus 2 (RP05)
> >> acpiprt7 at acpi0: bus -1 (RP06)
> >> acpiprt8 at acpi0: bus -1 (RP07)
> >> acpiprt9 at acpi0: bus -1 (RP08)
> >> acpiprt10 at acpi0: bus -1 (PEG0)
> >> acpiprt11 at acpi0: bus -1 (PEG1)
> >> acpiprt12 at acpi0: bus -1 (PEG2)
> >> acpiprt13 at acpi0: bus -1 (PEG3)
> >> acpiec0 at acpi0: not present
> >> acpipci0 at acpi0 PCI0: 0x00000010 0x00000011 0x00000000
> >> acpicmos0 at acpi0
> >> com0 at acpi0 UAR1 addr 0x3f8/0x8 irq 4: ns16550a, 16 byte fifo
> >> com0: console
> >> com1 at acpi0 UAR2 addr 0x2f8/0x8 irq 3: ns16550a, 16 byte fifo
> >> acpibtn0 at acpi0: PWRB
> >> "PNP0C0B" at acpi0 not configured
> >> "PNP0C0B" at acpi0 not configured
> >> "PNP0C0B" at acpi0 not configured
> >> "PNP0C0B" at acpi0 not configured
> >> "PNP0C0B" at acpi0 not configured
> >> acpicpu0 at acpi0: C3(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS
> >> acpicpu1 at acpi0: C3(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS
> >> acpicpu2 at acpi0: C3(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS
> >> acpicpu3 at acpi0: C3(350@80 mwait.1@0x20), C1(1000@1 mwait.1), PSS
> >> acpipwrres0 at acpi0: FN00, resource for FAN0
> >> acpipwrres1 at acpi0: FN01, resource for FAN1
> >> acpipwrres2 at acpi0: FN02, resource for FAN2
> >> acpipwrres3 at acpi0: FN03, resource for FAN3
> >> acpipwrres4 at acpi0: FN04, resource for FAN4
> >> acpitz0 at acpi0: critical temperature is 92 degC
> >> acpitz1 at acpi0: critical temperature is 92 degC
> >> acpivideo0 at acpi0: GFX0
> >> acpivout0 at acpivideo0: DD01
> >> acpivout1 at acpivideo0: DD02
> >> acpivout2 at acpivideo0: DD03
> >> acpivout3 at acpivideo0: DD04
> >> acpivout4 at acpivideo0: DD05
> >> acpivout5 at acpivideo0: DD06
> >> acpivout6 at acpivideo0: DD07
> >> acpivout7 at acpivideo0: DD08
> >> cpu0: using VERW MDS workaround (except on vmm entry)
> >> cpu0: Enhanced SpeedStep 2800 MHz: speeds: 2800, 2700, 2600, 2500,
> >> 2400,
> >> 2300, 2200, 2100, 2000, 1900, 1800, 1700, 1600 MHz
> >> pci0 at mainbus0 bus 0
> >> pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09
> >> em0 at pci0 dev 25 function 0 "Intel 82579LM" rev 0x05: msi, address
> >> 00:25:90:da:2c:e3
> >> ehci0 at pci0 dev 26 function 0 "Intel 6 Series USB" rev 0x05: apic
> 2
> >> int
> >> 16
> >> usb0 at ehci0: USB revision 2.0
> >> uhub0 at usb0 configuration 1 interface 0 "Intel EHCI root hub" rev
> >> 2.00/1.00 addr 1
> >> ppb0 at pci0 dev 28 function 0 "Intel 6 Series PCIE" rev 0xb5: msi
> >> pci1 at ppb0 bus 1
> >> ppb1 at pci0 dev 28 function 4 "Intel 6 Series PCIE" rev 0xb5: msi
> >> pci2 at ppb1 bus 2
> >> em1 at pci2 dev 0 function 0 "Intel 82574L" rev 0x00: msi, address
> >> 00:25:90:da:2c:e2
> >> ehci1 at pci0 dev 29 function 0 "Intel 6 Series USB" rev 0x05: apic
> 2
> >> int
> >> 23
> >> usb1 at ehci1: USB revision 2.0
> >> uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev
> >> 2.00/1.00 addr 1
> >> ppb2 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0xa5
> >> pci3 at ppb2 bus 3
> >> vga1 at pci3 dev 3 function 0 "Matrox MGA G200eW" rev 0x0a
> >> wsdisplay at vga1 not configured
> >> pcib0 at pci0 dev 31 function 0 "Intel C202 LPC" rev 0x05
> >> ahci0 at pci0 dev 31 function 2 "Intel 6 Series AHCI" rev 0x05: msi,
> >> AHCI
> >> 1.3
> >> ahci0: port 0: 3.0Gb/s
> >> ahci0: port 1: 3.0Gb/s
> >> ahci0: port 2: 1.5Gb/s
> >> scsibus1 at ahci0: 32 targets
> >> sd0 at scsibus1 targ 0 lun 0: <ATA, INTEL SSDSA2BW16, 4PC1>
> >> naa.5001517959543ebf
> >> sd0: 152627MB, 512 bytes/sector, 312581808 sectors, thin
> >> sd1 at scsibus1 targ 1 lun 0: <ATA, INTEL SSDSA2BW16, 4PC1>
> >> naa.50015178f35d5f6f
> >> sd1: 152627MB, 512 bytes/sector, 312581808 sectors, thin
> >> cd0 at scsibus1 targ 2 lun 0: <TEAC, DVD-ROM DV-28SW, D.2C>
> removable
> >> ichiic0 at pci0 dev 31 function 3 "Intel 6 Series SMBus" rev 0x05:
> apic
> >> 2
> >> int 18
> >> iic0 at ichiic0
> >> sdtemp0 at iic0 addr 0x19: stts2002
> >> sdtemp1 at iic0 addr 0x1b: mcp98243
> >> spdmem0 at iic0 addr 0x51: 2GB DDR3 SDRAM ECC PC3-10600 with thermal
> >> sensor
> >> spdmem1 at iic0 addr 0x53: 2GB DDR3 SDRAM ECC PC3-10600 with thermal
> >> sensor
> >> isa0 at pcib0
> >> isadma0 at isa0
> >> pckbc0 at isa0 port 0x60/5 irq 1 irq 12
> >> pckbd0 at pckbc0 (kbd slot)
> >> wskbd0 at pckbd0 mux 1
> >> pcppi0 at isa0 port 0x61
> >> spkr0 at pcppi0
> >> wbsio0 at isa0 port 0x2e/2: NCT6776F rev 0x33
> >> lm1 at wbsio0 port 0xa30/8: NCT6776F
> >> vmm0 at mainbus0: VMX/EPT
> >> uhub2 at uhub0 port 1 configuration 1 interface 0 "Intel Rate
> Matching
> >> Hub" rev 2.00/0.00 addr 2
> >> uhub3 at uhub1 port 1 configuration 1 interface 0 "Intel Rate
> Matching
> >> Hub" rev 2.00/0.00 addr 2
> >> uhidev0 at uhub3 port 1 configuration 1 interface 0 "Dell Dell USB
> >> Keyboard" rev 1.10/3.06 addr 3
> >> uhidev0: iclass 3/1
> >> ukbd0 at uhidev0: 8 variable keys, 6 key codes
> >> wskbd1 at ukbd0 mux 1
> >> vscsi0 at root
> >> scsibus2 at vscsi0: 256 targets
> >> softraid0 at root
> >> scsibus3 at softraid0: 256 targets
> >> sd2 at scsibus3 targ 1 lun 0: <OPENBSD, SR RAID 1, 006>
> >> sd2: 142388MB, 512 bytes/sector, 291611352 sectors
> >> root on sd0a (3c411dc68c2af2bf.a) swap on sd0b dump on sd0b
> >
> >
> >
>
>
> --
> Please keep replies on the mailing list.
