tech-x11 archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
X vs serial console?
I don't know whether this is kernel or X11. There are things pointing
each way.
At work, I've got 9.1 on an amd64 machine. When I boot it normally -
console on screen/keyboard - X works fine.
But I'm having an issue. The machine is rebooting on me, sometimes,
and I don't know whether it's some kind of quasi-spontaneous hard-reset
or whether it's a panic. But, with X on the console, I can't tell
whether there's a panic or not.
So, I booted it with serial console. But now, X doesn't seem to work.
There are a number of curious things involved.
Upon resetting, I drop to the boot prompt and tell it "consdev com2".
(The application uses com0 and com1, and the machine has six serial
ports.) I get the usual boot prompt on the serial port:
>> NetBSD/x86 BIOS Boot, Revision 5.11 (Sun Oct 18 19:24:30 UTC 2020) (from NetBSD 9.1)
>> Memory: 625/2209792 k
>
and, when I type, it appears to work normally. Thus, I'm ruling out,
at least tentatively, issues with the serial console infrastructure.
So I tell it
> boot
and it boots. I have a full log of the boot-time messages, in case
there's something someone wants to know from them that I don't quote
below.
At this point - ie, after booting - the monitor connected to the video
output is displaying black, but the colour of the monitor's telltale
indicates it's getting a video signal.
So, I ssh in and start X. I start it with my usual script
#! /bin/sh
exec xinit /home/mouse/X/x-client -- /usr/X11R7/bin/X -retro -tst -depth 8 -cc 3 -listen tcp
where the x-client script is
#! /bin/sh
xterm -geometry 160x50
With video console, starting it that way gives me the root weave with
an xterm in the upper-left 2/3 to 3/4 of the screen (the monitor is
1280x1024). With serial console, the video screen keeps displaying the
same black it has been since boot, still with the telltale saying it's
got a video signal. But X is running; I can connect to it with
xdpyinfo and xrandr and it all looks normal. The only unusual thing is
that I'm getting nothing but black on the monitor.
There is one curious thing: if I disconnect the monitor (DE-15 ("VGA")
connection), the monitor, not surprisingly, goes into its "no signal"
mode, but if I plug it back in, it _doesn't_ return to its "I've got
signal" state. xrandr's claims about what's connected do not change;
at each of those three times (after startup, when disconnected, and
once reconnected) it still claims DP1, DP2, HDMI1, HDMI2, HDMI3, and
VIRTUAL1 disconnected and DP3 connected with a reasonable-looking suite
of supported resolutions. In terms of back-panel hardware, it has one
DE15 and two HDMI connectors. Based on RandR clone values, I think DPx
and HDMIx go together in some sense, for each x in <1,2,3>.
In the window in which I ssh in and run the first script above, I see
two differences: the serial-console version has two extra lines.
Diffing typescript files,
--- typescript.video 2021-02-09 12:12:42.530182718 -0500
+++ typescript.serial 2021-02-09 12:08:16.660786940 -0500
@@ -1,4 +1,4 @@
-Script started on Tue Feb 9 12:12:31 2021
+Script started on Tue Feb 9 12:05:53 2021
X.Org X Server 1.20.5
@@ -13,7 +13,8 @@
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
-(==) Log file: "/var/log/Xorg.0.log", Time: Tue Feb 9 12:12:32 2021
+(==) Log file: "/var/log/Xorg.0.log", Time: Tue Feb 9 12:05:54 2021
+failed to open /dev/ttyE0: Device not configured
(==) Using default built-in configuration (39 lines)
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Error: Couldn't lookup keysym
@@ -21,11 +22,12 @@
> Error: Couldn't lookup keysym
> Symbol interpretation ignored
Errors from xkbcomp are not fatal to the X server
+xinit: XFree86_VT property unexpectedly has 0 items instead of 1
^Cxinit: connection to X server lost
-xterm: fatal IO error 35 (Resource temporarily unavailable) or KillClient on X server ":0"
-waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.
+waiting for X server to shut down xterm: fatal IO error 35 (Resource temporarily unavailable) or KillClient on X server ":0"
+(II) Server terminated successfully (0). Closing log file.
xinit: unexpected signal 2
Obviously, the timestamp differences can be ignored. I'm not sure
whether /dev/ttyE0 failing is to be expected and whether it's relevant;
based on what ctl-alt-Fn gives me, X runs on ttyE4 rather than ttyE0 in
the video-console case anyway. I don't know what to make of the
XFree86_VT message. Because someone "helpfully" decided I wanted some
kind of number in brackets on each line of Xorg.0.log, it's
inconvenient to diff them. Using :1,$s/^[[][ 0-9.]*[]] in vi on each
file and diffing the results, I get
--- z.video Tue Feb 9 12:25:47 2021
+++ z.serial Tue Feb 9 12:25:58 2021
@@ -11,8 +11,8 @@
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
- (==) Log file: "/var/log/Xorg.0.log", Time: Tue Feb 9 12:17:17 2021
- (II) Loader magic: 0xee88ea60
+ (==) Log file: "/var/log/Xorg.0.log", Time: Tue Feb 9 12:20:59 2021
+ (II) Loader magic: 0xc488ea60
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 24.0
@@ -150,8 +150,7 @@
(II) modesetting: Driver for Modesetting Kernel Drivers: kms
(II) VESA: driver for VESA chipsets: vesa
(II) wsfb: driver for wsdisplay framebuffer: wsfb
- (--) Using wscons driver on /dev/ttyE4 in pcvt compatibility mode (version 3.32)
- (--) using VT number 5
+ (--) Using wscons driver
(II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20151010
(WW) Falling back to old probe method for modesetting
(WW) Falling back to old probe method for wsfb
@@ -258,8 +257,6 @@
(**) Option "XkbModel" "pc105"
(**) Option "XkbLayout" "us"
(II) XINPUT: Adding extended input device "<default keyboard>" (type: KEYBOARD, id 7)
- (II) intel(0): switch to mode 1280x1024@60.0 on DP3 using pipe 0, position (0, 0), rotation normal, reflection none
- (II) intel(0): switch to mode 1280x1024@60.0 on DP3 using pipe 0, position (0, 0), rotation normal, reflection none
(II) UnloadModule: "kbd"
(II) UnloadModule: "mouse"
(II) Server terminated successfully (0). Closing log file.
There are some fascinating differences in the boot-time autoconf
messages as well. A few of them do not surprise me; most of them do.
Again, because someone "helpfully" decided I wanted numbers in brackets
at the beginning of the lines in one of these, I had to
:1,$s/^[[][ 0-9.]*[]] that one in order to get a meaningful diff.
I've also manually replaced some thousands of characters of bootloader
twirler and kernel size numbers with [twirler]. It does occur to me
that the captures come from different places - the video file comes
from /var/run/dmesg.boot whereas the serial file comes from capturing
serial console output - but I don't know whether that explains any of
this. (If it does, I'd call it a bug - that would, at the very least,
violate POLA for me. But that there is the big difference of the
[ numbers] appearing in one but not the other leads me to suspect there
could be deeper differences too. And some of these are things I have
trouble blaming on console device, such as the cpu0 frequency lines.)
--- z.video 2021-02-09 12:30:53.000000000 -0500
+++ z.serial 2021-02-09 12:32:58.000000000 -0500
@@ -1,3 +1,9 @@
+>> NetBSD/x86 BIOS Boot, Revision 5.11 (Sun Oct 18 19:24:30 UTC 2020) (from NetBSD 9.1)
+>> Memory: 625/2209792 k
+> boot
+command(s): rndseed /var/db/entropy-file;boot
+default boot twice, skipping...
+[twirler]Loading /var/db/entropy-file
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017,
2018, 2019, 2020 The NetBSD Foundation, Inc. All rights reserved.
@@ -10,11 +16,7 @@
avail memory = 3862 MB
cpu_rng: RDSEED
rnd: seeded with 256 bits
-timecounter: Timecounters tick every 1.000 msec
-Kernelized RAIDframe activated
running cgd selftest aes-xts-256 aes-xts-512 done
-timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
-AAEON BOXER-6839 (V1.0)
mainbus0 (root)
ACPI: RSDP 0x00000000000F05B0 000024 (v02 ALASKA)
ACPI: XSDT 0x000000008C8660B0 0000DC (v01 ALASKA A M I 01072009 AMI 00010013)
@@ -44,11 +46,8 @@
ACPI: DMAR 0x000000008C898448 0000A8 (v01 INTEL KBL 00000001 INTL 00000001)
ACPI: ASF! 0x000000008C8984F0 0000A0 (v32 INTEL HCG 00000001 TFSM 000F4240)
ACPI: 11 ACPI AML tables successfully acquired and loaded
-ioapic0 at mainbus0 apid 2: pa 0xfec00000, version 0x20, 120 pins
+ioapic0 at mainbus0 apid 2
cpu0 at mainbus0 apid 0
-cpu0: CPU base freq 3400000000 Hz
-cpu0: CPU max freq 3400000000 Hz
-cpu0: TSC freq CPUID 3408000000 Hz
cpu0: Intel(R) Core(TM) i3-7101TE CPU @ 3.40GHz, id 0x906e9
cpu0: package 0, core 0, smt 0
cpu1 at mainbus0 apid 2
@@ -61,17 +60,12 @@
cpu3: Intel(R) Core(TM) i3-7101TE CPU @ 3.40GHz, id 0x906e9
cpu3: package 0, core 1, smt 1
acpi0 at mainbus0: Intel ACPICA 20190405
-acpi0: X/RSDT: OemId <ALASKA, A M I ,01072009>, AslId <AMI ,00010013>
-acpi0: MCFG: segment 0, bus 0-255, address 0x00000000e0000000
ACPI: Dynamic OEM Table Load:
-ACPI: SSDT 0xFFFF832F7A1B8808 0006F6 (v02 PmRef Cpu0Ist 00003000 INTL 20160422)
+ACPI: SSDT 0xFFFF887243BB8808 0006F6 (v02 PmRef Cpu0Ist 00003000 INTL 20160422)
ACPI: Dynamic OEM Table Load:
-ACPI: SSDT 0xFFFF832F7A1A9008 00065C (v02 PmRef ApIst 00003000 INTL 20160422)
-acpi0: SCI interrupting at int 9
+ACPI: SSDT 0xFFFF887243BA9008 00065C (v02 PmRef ApIst 00003000 INTL 20160422)
acpi0: fixed power button present
-timecounter: Timecounter "ACPI-Fast" frequency 3579545 Hz quality 1000
hpet0 at acpi0: high precision event timer (mem 0xfed00000-0xfed00400)
-timecounter: Timecounter "hpet0" frequency 24000000 Hz quality 2000
acpiec0 at acpi0 (H_EC, PNP0C09-1): not present
acpivga0 at acpi0 (GFX0): ACPI Display Adapter
acpiout0 at acpivga0 (DD01, 0x0100): ACPI Display Output Device
@@ -90,10 +84,7 @@
acpiout13 at acpivga0 (DD0E, 0x000e): ACPI Display Output Device
acpiout14 at acpivga0 (DD0F, 0x000f): ACPI Display Output Device
acpiout15 at acpivga0 (DD1F, 0x0400): ACPI Display Output Device
-acpiout15: brightness levels: [0-100]
acpiout16 at acpivga0 (SKC0, 0xca00): ACPI Display Output Device
-acpivga0: connected output devices:
-acpivga0: 0x0400 (acpiout15): Unknown Output Device, head 0
SIO2 (PNP0C02) at acpi0 not configured
SIO1 (PNP0C02) at acpi0 not configured
com0 at acpi0 (UAR1, PNP0501-1): io 0x3f8-0x3ff irq 4
@@ -101,7 +92,8 @@
com1 at acpi0 (UAR2, PNP0501-2): io 0x2f8-0x2ff irq 3
com1: ns16550a, working fifo
com2 at acpi0 (UAR3, PNP0501-3): io 0x3e8-0x3ef irq 11
-com2: ns16550a, working fifo
+com: ns16550a, working fifo
+com2: console
com3 at acpi0 (UAR4, PNP0501-4): io 0x2e8-0x2ef irq 11
com3: ns16550a, working fifo
com4 at acpi0 (UAR5, PNP0501-5): io 0x2d0-0x2d7 irq 11
@@ -125,23 +117,18 @@
acpitz0: active cooling level 2: 50.0C
acpitz0: active cooling level 3: 45.0C
acpitz0: active cooling level 4: 40.0C
-acpitz0: levels: critical 119.0 C
acpitz1 at acpi0 (TZ01)
-acpitz1: levels: critical 119.0 C, passive cooling
ACPI: Enabled 4 GPEs in block 00 to 7F
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 8086 product 590f (rev. 0x05)
i915drmkms0 at pci0 dev 2 function 0: vendor 8086 product 5912 (rev. 0x04)
xhci0 at pci0 dev 20 function 0: vendor 8086 product a12f (rev. 0x31)
xhci0: interrupting at msi0 vec 0
-xhci0: xHCI version 1.0
usb0 at xhci0: USB revision 3.0
usb1 at xhci0: USB revision 2.0
vendor 8086 product a131 (miscellaneous DASP, revision 0x31) at pci0 dev 20 function 2 not configured
vendor 8086 product a13a (miscellaneous communications, revision 0x31) at pci0 dev 22 function 0 not configured
ahcisata0 at pci0 dev 23 function 0: vendor 8086 product a102 (rev. 0x31)
-ahcisata0: 64-bit DMA
ahcisata0: AHCI revision 1.31, 4 ports, 32 slots, CAP 0xe734ff43<EMS,PSC,SSC,PMD,SAM,ISS=0x3=Gen3,SCLO,SAL,SALP,SSNTF,SNCQ,S64A>
ahcisata0: interrupting at msi1 vec 0
atabus0 at ahcisata0 channel 0
@@ -151,70 +138,55 @@
ppb0 at pci0 dev 28 function 0: vendor 8086 product a110 (rev. 0xf1)
ppb0: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x1 @ 8.0GT/s
pci1 at ppb0 bus 1
-pci1: i/o space, memory space enabled, rd/line, wr/inv ok
ppb1 at pci0 dev 28 function 3: vendor 8086 product a113 (rev. 0xf1)
ppb1: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x1 @ 8.0GT/s
ppb1: link is x1 @ 2.5GT/s
pci2 at ppb1 bus 2
-pci2: i/o space, memory space enabled, rd/line, wr/inv ok
wm0 at pci2 dev 0 function 0: I210-T1 Ethernet Server Adapter (rev. 0x03)
wm0: for TX and RX interrupting at msix2 vec 0 affinity to 0
wm0: for TX and RX interrupting at msix2 vec 1 affinity to 1
wm0: for TX and RX interrupting at msix2 vec 2 affinity to 2
wm0: for TX and RX interrupting at msix2 vec 3 affinity to 3
wm0: for LINK interrupting at msix2 vec 4
-wm0: PCI-Express bus
-wm0: 64 words iNVM, version 0.6
wm0: Ethernet address 00:07:32:4a:70:ca
wm0: Copper
-wm0: 0x4c614420<INVM,IOH_VALID,PCIE,NEWQUEUE,WOL,EEE,PLLWA,CLSEMWA,CRC_STRIP>
makphy0 at wm0 phy 1: I210 10/100/1000 media interface, rev. 0
makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
ppb2 at pci0 dev 28 function 4: vendor 8086 product a114 (rev. 0xf1)
ppb2: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x4 @ 8.0GT/s
ppb2: link is x1 @ 2.5GT/s
pci3 at ppb2 bus 3
-pci3: i/o space, memory space enabled, rd/line, wr/inv ok
puc0 at pci3 dev 0 function 0: Oxford Semiconductor OXPCIe952 LPT (lpt)
lpt2 at puc0 port 0: ioaddr 0xd010, interrupting at ioapic0 pin 16
ppb3 at pci0 dev 29 function 0: vendor 8086 product a118 (rev. 0xf1)
ppb3: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x1 @ 8.0GT/s
pci4 at ppb3 bus 4
-pci4: i/o space, memory space enabled, rd/line, wr/inv ok
ppb4 at pci0 dev 29 function 3: vendor 8086 product a11b (rev. 0xf1)
ppb4: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x1 @ 8.0GT/s
ppb4: link is x1 @ 2.5GT/s
pci5 at ppb4 bus 5
-pci5: i/o space, memory space enabled, rd/line, wr/inv ok
wm1 at pci5 dev 0 function 0: I210-T1 Ethernet Server Adapter (rev. 0x03)
wm1: for TX and RX interrupting at msix3 vec 0 affinity to 0
wm1: for TX and RX interrupting at msix3 vec 1 affinity to 1
wm1: for TX and RX interrupting at msix3 vec 2 affinity to 2
wm1: for TX and RX interrupting at msix3 vec 3 affinity to 3
wm1: for LINK interrupting at msix3 vec 4
-wm1: PCI-Express bus
-wm1: 64 words iNVM, version 0.6
wm1: Ethernet address 00:07:32:4a:70:cb
wm1: Copper
-wm1: 0x4c614420<INVM,IOH_VALID,PCIE,NEWQUEUE,WOL,EEE,PLLWA,CLSEMWA,CRC_STRIP>
makphy1 at wm1 phy 1: I210 10/100/1000 media interface, rev. 0
makphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
ppb5 at pci0 dev 29 function 4: vendor 8086 product a11c (rev. 0xf1)
ppb5: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x1 @ 8.0GT/s
ppb5: link is x1 @ 2.5GT/s
pci6 at ppb5 bus 6
-pci6: i/o space, memory space enabled, rd/line, wr/inv ok
wm2 at pci6 dev 0 function 0: I210-T1 Ethernet Server Adapter (rev. 0x03)
wm2: for TX and RX interrupting at msix4 vec 0 affinity to 0
wm2: for TX and RX interrupting at msix4 vec 1 affinity to 1
wm2: for TX and RX interrupting at msix4 vec 2 affinity to 2
wm2: for TX and RX interrupting at msix4 vec 3 affinity to 3
wm2: for LINK interrupting at msix4 vec 4
-wm2: PCI-Express bus
-wm2: 64 words iNVM, version 0.6
wm2: Ethernet address 00:07:32:4a:70:cc
wm2: Copper
-wm2: 0x4c614420<INVM,IOH_VALID,PCIE,NEWQUEUE,WOL,EEE,PLLWA,CLSEMWA,CRC_STRIP>
makphy2 at wm2 phy 1: I210 10/100/1000 media interface, rev. 0
makphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
pcib0 at pci0 dev 31 function 0: vendor 8086 product a146 (rev. 0x31)
@@ -245,58 +217,24 @@
sysbeep0 at pcppi0
attimer1: attached to pcppi0
acpicpu0 at cpu0: ACPI CPU
-acpicpu0: C1: HLT, lat 0 us, pow 0 mW
-acpicpu0: P0: FFH, lat 10 us, pow 35000 mW, 3400 MHz
-acpicpu0: P1: FFH, lat 10 us, pow 32154 mW, 3200 MHz
-acpicpu0: P2: FFH, lat 10 us, pow 30770 mW, 3100 MHz
-acpicpu0: P3: FFH, lat 10 us, pow 28078 mW, 2900 MHz
-acpicpu0: P4: FFH, lat 10 us, pow 25492 mW, 2700 MHz
-acpicpu0: P5: FFH, lat 10 us, pow 23000 mW, 2500 MHz
-acpicpu0: P6: FFH, lat 10 us, pow 21791 mW, 2400 MHz
-acpicpu0: P7: FFH, lat 10 us, pow 19448 mW, 2200 MHz
-acpicpu0: P8: FFH, lat 10 us, pow 17196 mW, 2000 MHz
-acpicpu0: P9: FFH, lat 10 us, pow 15038 mW, 1800 MHz
-acpicpu0: P10: FFH, lat 10 us, pow 14282 mW, 1700 MHz
-acpicpu0: P11: FFH, lat 10 us, pow 12253 mW, 1500 MHz
-acpicpu0: P12: FFH, lat 10 us, pow 10313 mW, 1300 MHz
-acpicpu0: P13: FFH, lat 10 us, pow 8463 mW, 1100 MHz
-acpicpu0: P14: FFH, lat 10 us, pow 7569 mW, 1000 MHz
-acpicpu0: P15: FFH, lat 10 us, pow 5846 mW, 800 MHz
-coretemp0 at cpu0: thermal sensor, 1 C resolution, Tjmax=88
+coretemp0 at cpu0: thermal sensor, 1 C resolution
acpicpu1 at cpu1: ACPI CPU
-coretemp1 at cpu1: thermal sensor, 1 C resolution, Tjmax=88
+coretemp1 at cpu1: thermal sensor, 1 C resolution
acpicpu2 at cpu2: ACPI CPU
acpicpu3 at cpu3: ACPI CPU
-timecounter: Timecounter "clockinterrupt" frequency 8000 Hz quality 0
-cpu1: CPU base freq 3400000000 Hz
-cpu1: CPU max freq 3400000000 Hz
-cpu1: TSC freq CPUID 3408000000 Hz
-cpu2: CPU base freq 3400000000 Hz
-cpu2: CPU max freq 3400000000 Hz
-cpu2: TSC freq CPUID 3408000000 Hz
-cpu3: CPU base freq 3400000000 Hz
-cpu3: CPU max freq 3400000000 Hz
-cpu3: TSC freq CPUID 3408000000 Hz
-timecounter: Timecounter "TSC" frequency 3408000000 Hz quality 3000
uhub0 at usb0: NetBSD (0000) xHCI root hub (0000), class 9/0, rev 3.00/1.00, addr 0
-uhub0: 10 ports with 10 removable, self powered
uhub1 at usb1: NetBSD (0000) xHCI root hub (0000), class 9/0, rev 2.00/1.00, addr 0
-uhub1: 16 ports with 16 removable, self powered
-IPsec: Initialized Security Association Processing.
ahcisata0 port 1: device present, speed: 3.0Gb/s
-ahcisata0 port 3: PHY offline
ahcisata0 port 0: PHY offline
ahcisata0 port 2: PHY offline
+ahcisata0 port 3: PHY offline
uhidev0 at uhub1 port 1 configuration 1 interface 0
uhidev0: Gaming KB (0x258a) Gaming KB (0x1006), rev 1.10/1.05, addr 1, iclass 3/1
-ukbd0 at uhidev0
wd0 at atabus1 drive 0
wd0: <WDC WD1600BEVT-00A23T0>
-wd0: drive supports 16-sector PIO transfers, LBA48 addressing
wd0: 149 GB, 310101 cyl, 16 head, 63 sec, 512 bytes/sect x 312581808 sectors
-wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133), WRITE DMA FUA, NCQ (32 tags) w/PRIO
-wd0(ahcisata0:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA), NCQ (31 tags) w/PRIO
-wskbd0 at ukbd0: console keyboard
+ukbd0 at uhidev0
+wskbd0 at ukbd0 mux 1
uhidev1 at uhub1 port 1 configuration 1 interface 1
uhidev1: Gaming KB (0x258a) Gaming KB (0x1006), rev 1.10/1.05, addr 1, iclass 3/1
uhidev1: 8 report ids
@@ -304,7 +242,7 @@
uhid1 at uhidev1 reportid 2: input=2, output=0, feature=0
uhid2 at uhidev1 reportid 5: input=0, output=0, feature=5
ukbd1 at uhidev1 reportid 6
-ukbd1: autoconfiguration error: attach failed, key code size != 8
+ukbd1: attach failed, key code size != 8
ukbd2 at uhidev1 reportid 7
wskbd1 at ukbd2 mux 1
ukbd3 at uhidev1 reportid 8
@@ -328,13 +266,7 @@
kern error: [drm:(/sys/external/bsd/drm2/dist/drm/i915/i915_gem.c:5417)i915_gem_init_hw] *ERROR* Failed to initialize GuC, error -5 (ignored)
kern info: [drm] GMBUS [i915 gmbus dpd] timed out, falling back to bit banging on pin 6
intelfb0 at i915drmkms0
-intelfb0: framebuffer at 0xffff8380676fc000, size 1280x1024, depth 32, stride 5120
-wsdisplay0 at intelfb0 kbdmux 1: console (default, vt100 emulation), using wskbd0
-wsmux1: connecting to wsdisplay0
-wskbd1: connecting to wsdisplay0
-wskbd2: connecting to wsdisplay0
+kern error: [drm:(/sys/external/bsd/drm2/dist/drm/i915/intel_fifo_underrun.c:363)intel_cpu_fifo_underrun_irq_handler] *ERROR* CPU pipe A FIFO underrun
+warning: /sys/external/bsd/drm2/dist/drm/drm_irq.c:1510: vblank wait timed out on crtc 0
+wsdisplay0 at intelfb0 kbdmux 1
kern info: [drm] RC6 on
-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)
So, what am I doing wrong here? Is the answer just "trying to use X on
non-console video", or is there more to it? Surely I can't be the only
person who wants to see console output when X has the screen hijacked.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML mouse%rodents-montreal.org@localhost
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
Home |
Main Index |
Thread Index |
Old Index