OK folks,

Same results on a 3rd box with 5.6 release.

This machine's dmesg below, if that's of any relevance.

On 2015-04-10 Fri 14:12 PM |, Craig Skinner wrote:
> 
> 2 x i386 boxes, each with 2 serial cables cross connected from com1 to
> com0 on his neighbour. Normally used without monitor, nor keyboard.
> 
> When ssh'ing, colours work fine (man pages, vim, mutt, lynx, etc.)
> 
> After connecting a spare VGA CRT monitor & logging in locally, there
> were no colours. But when I rebooted with the monitor & keyboard
> connected, colours were back.
> 
> When I connect the monitor & keyboard to the other box & reboot over the
> serial line, then replug the monitor back into the origianl box, colours
> are gone, until I reboot it with the monitor connected (even though the
> boot output is over com0 to the other machine).
> 
> Setup:
> 
> $ uname -srvm
> OpenBSD 5.6 GENERIC#274 i386
> 
> 
> $ cat /etc/boot.conf
> stty com0 9600
> set tty com0
> 
> 
> $ ls -l /etc/boot.conf
> -r--r--r--  1 root  wheel  28 Aug 25  2007 /etc/boot.conf
> 
> 
> $ grep ^ttyC /etc/ttys | grep on$
> ttyC0 "/usr/libexec/getty std.9600"   pccon           on
> ttyC1 "/usr/libexec/getty std.9600"   pccon           on
> ttyC2 "/usr/libexec/getty std.9600"   pccon           on
> ttyC3 "/usr/libexec/getty std.9600"   pccon           on
> 
> 
> $ grep -v ^# /etc/wsconsctl.conf
> keyboard.encoding=uk          # Use United Kingdom keyboard encoding
> display.vblank=on             # Enable vertical sync blank for screen burner
> display.screen_off=300000     # Set screen burner timeout to 5 minutes
> display.msact=off             # Disable screen unburn with mouse
> display.kbdact=on             # Restore screen on keyboard input
> display.outact=off            # Restore screen on display output
> 
> 
> $ printenv TERM
> pccon
> 
> 
> $ tput colors
> 8
> 
> 
> Any ideas on how to have console colours when connecting a monitor after
> booting?
> 


OpenBSD 5.6 (GENERIC) #274: Fri Aug  8 00:05:13 MDT 2014
    dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel Pentium II ("GenuineIntel" 686-class, 512KB L2 cache) 349 MHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PSE36,MMX,FXSR,PERF
real mem  = 133644288 (127MB)
avail mem = 119042048 (113MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 07/19/99, BIOS32 rev. 0 @ 0xfd861, SMBIOS 
rev. 2.1 @ 0xf7d95 (32 entries)
bios0: vendor IBM version "PDKT27AUS" date 07/19/99
bios0: IBM 6275500
acpi0 at bios0: rev 0
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP
acpi0: wakeup devices PCI0(S5) PS2K(S1) PS2M(S1) COM1(S5) COM2(S5) USB0(S1)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpiprt0 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0
bios0: ROM list: 0xc0000/0x8000
cpu0 at mainbus0: (uniprocessor)
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x03
intelagp0 at pchb0
agp0 at intelagp0: aperture at 0xec000000, size 0x4000000
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x03
pci1 at ppb0 bus 1
vga1 at pci1 dev 1 function 0 "S3 Trio3D AGP" rev 0x01
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
piixpcib0 at pci0 dev 2 function 0 "Intel 82371AB PIIX4 ISA" rev 0x02
pciide0 at pci0 dev 2 function 1 "Intel 82371AB IDE" rev 0x01: DMA, channel 0 
wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0: <Maxtor 90320D2>
wd0: 16-sector PIO, LBA, 3079MB, 6306048 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
pciide0: channel 1 ignored (disabled)
uhci0 at pci0 dev 2 function 2 "Intel 82371AB USB" rev 0x01: irq 10
piixpm0 at pci0 dev 2 function 3 "Intel 82371AB Power" rev 0x02: SMI
iic0 at piixpm0
spdmem0 at iic0 addr 0x50: 32MB SDRAM non-parity PC100CL3
spdmem1 at iic0 addr 0x51: 32MB SDRAM non-parity PC100CL3
spdmem2 at iic0 addr 0x52: 64MB SDRAM non-parity PC100CL3
spdmem3 at iic0 addr 0x55: 1GB DDR2 SDRAM PC2-5000CL4
xl0 at pci0 dev 16 function 0 "3Com 3c905B 100Base-TX" rev 0x64: irq 15, 
address 00:50:04:62:35:f8
bmtphy0 at xl0 phy 24: 3C905B internal PHY, rev. 0
xl1 at pci0 dev 18 function 0 "3Com 3c905B 100Base-TX" rev 0x30: irq 11, 
address 00:10:5a:f1:9d:b1
exphy0 at xl1 phy 24: 3Com internal media interface
isa0 at piixpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
usb0 at uhci0: USB revision 1.0
uhub0 at usb0 "Intel UHCI root hub" rev 1.00/1.00 addr 1
vscsi0 at root
scsibus1 at vscsi0: 256 targets
softraid0 at root
scsibus2 at softraid0: 256 targets
root on wd0a (868fd5d94428712f.a) swap on wd0b dump on wd0b

-- 
You can do this in a number of ways.  IBM chose to do all of them.
Why do you find that funny?
                -- D. Taylor, Computer Science 350, University of Washington

Reply via email to