Re: XDG_RUNTIME_DIR
Thanks for all the encouragement. I've decided I don't need lyx running in NetBSD. I was getting farther into a rabbit-hole I didn't want to be in to begin with. If you know what I mean. And I'm sure you do. Thank you again to all. -- RSB
Re: nvmm doesn't work on "Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz"?
Did you 'modload nvmm' ? It doesn't get loaded automatically. On Sun, 25 Apr 2021 at 16:55, Rhialto wrote: > > Hi all, > > I've just bought a new computer with a "Intel(R) Core(TM) i5-9600K CPU @ > 3.70GHz" cpu. I have enabled VMX and VT-d in the "BIOS", but nvmm > doesn't seem to work on it. It's not reported in the kernel boot > messages; on my old computer it is. > > $ qemu-system-x86_64 -accel nvmm > qemu-system-x86_64: -accel nvmm: NVMM: Initialization failed, error=6 > qemu-system-x86_64: -accel nvmm: failed to initialize nvmm: Device not > configured > > This is what cpuctl says about the CPU; which details should I look at? > > bash-5.1$ cpuctl identify 0 > Cannot bind to target CPU. Output may not accurately describe the target. > Run as root to allow binding. > > cpu0: highest basic info 0016 > cpu0: highest extended info 8008 > cpu0: "Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz" > cpu0: Intel 7th or 8th gen Core (Kaby Lake, Coffee Lake) or Xeon E (Coffee > Lake) (686-class), 3696.00 MHz > cpu0: CPU base freq 37 Hz > cpu0: CPU max freq 46 Hz > cpu0: TSC freq CPUID 369600 Hz > cpu0: family 0x6 model 0x9e stepping 0xd (id 0x906ed) > cpu0: features > 0xbfebfbff > cpu0: features > 0xbfebfbff > cpu0: features 0xbfebfbff > cpu0: features1 0x7ffafbff > cpu0: features1 0x7ffafbff > cpu0: features1 0x7ffafbff > cpu0: features1 0x7ffafbff > cpu0: features2 0x2c100800 > cpu0: features3 0x121 > cpu0: features5 0x29c6fbf > cpu0: features5 0x29c6fbf > cpu0: features5 0x29c6fbf > cpu0: features6 0x4000 > cpu0: features7 0xbc000600 > cpu0: features7 0xbc000600 > cpu0: xsave features 0x1f > cpu0: xsave instructions 0xf > cpu0: xsave area size: current 832, maximum 1088, xgetbv enabled > cpu0: enabled xsave 0x7 > cpu0: I-cache 32KB 64B/line 8-way, D-cache 32KB 64B/line 8-way > cpu0: L2 cache 256KB 64B/line 4-way > cpu0: L3 cache 9MB 64B/line 12-way > cpu0: 64B prefetching > cpu0: ITLB 128 4KB entries 8-way, 2M/4M: 8 entries > cpu0: DTLB 64 4KB entries 4-way > cpu0: L2 STLB 1536 4KB entries 6-way > cpu0: L1 1GB page DTLB 4 1GB entries 4-way > cpu0: Initial APIC ID 6 > cpu0: Cluster/Package ID 0 > cpu0: Core ID 3 > cpu0: SMT ID 0 > cpu0: MONITOR/MWAIT extensions 0x3 > cpu0: monitor-line size 64 > cpu0: C1 substates 2 > cpu0: C2 substates 1 > cpu0: C3 substates 2 > cpu0: C4 substates 4 > cpu0: C5 substates 1 > cpu0: C6 substates 1 > cpu0: C7 substates 1 > cpu0: DSPM-eax 0x27f7 > cpu0: DSPM-eax 0x27f7 > cpu0: DSPM-ecx 0x1 > cpu0: SEF highest subleaf > cpu0: Power Management features: 0x100 > cpu0: Perfmon-eax 0x7300804 > cpu0: Perfmon-eax 0x7300804 > cpu0: Perfmon-edx 0x603 > cpu0: microcode version 0xd6, platform ID 1 > > > On my old computer, it is loke this, and the features with VM in them > look the same (VME, VMX). > > $ cpuctl identify 0 > Cannot bind to target CPU. Output may not accurately describe the target. > Run as root to allow binding. > > cpu0: highest basic info 000d > cpu0: highest extended info 8008 > cpu0: "Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz" > cpu0: Intel Xeon E3-12xx, 2nd gen i7, i5, i3 2xxx (686-class), 3292.74 MHz > cpu0: family 0x6 model 0x2a stepping 0x7 (id 0x206a7) > cpu0: features > 0xbfebfbff > cpu0: features > 0xbfebfbff > cpu0: features 0xbfebfbff > cpu0: features1 0x1d9ae3bf > cpu0: features1 0x1d9ae3bf > cpu0: features1 0x1d9ae3bf > cpu0: features2 0x28100800 > cpu0: features3 0x1 > cpu0: xsave features 0x7 > cpu0: xsave instructions 0x1 > cpu0: xsave area size: current 832, maximum 832, xgetbv enabled > cpu0: enabled xsave 0x7 > cpu0: I-cache 32KB 64B/line 8-way, D-cache 32KB 64B/line 8-way > cpu0: L2 cache 256KB 64B/line 8-way > cpu0: L3 cache 3MB 64B/line 12-way > cpu0: 64B prefetching > cpu0: ITLB 64 4KB entries 4-way, 2M/4M: 8 entries > cpu0: DTLB 64 4KB entries 4-way, 2M/4M: 32 entries (L0) > cpu0: L2 STLB 512 4KB entries 4-way > cpu0: Initial APIC ID 3 > cpu0: Cluster/Package ID 0 > cpu0: Core ID 1 > cpu0: SMT ID 1 > cpu0: MONITOR/MWAIT extensions 0x3 > cpu0: monitor-line size 64 > cpu0: C1 substates 2 > cpu0: C2 substates 1 > cpu0: C3 substates 1 > cpu0: DSPM-eax 0x75 > cpu0: DSPM-ecx 0x9 > cpu0: SEF highest subleaf > cpu0: Power Management features: 0x100 > cpu0: Perfmon-eax 0x7300403 > cpu0: Perfmon-eax 0x7300403 > cpu0: Perfmon-edx 0x603 > cpu0: microcode version 0x26, platform ID 1 > > -Olaf. > -- > ___ Q: "What's an anagram of Banach-Tarski?" -- Olaf "Rhialto" Seibert > \X/ A: "Banach-Tarski Banach-Tarski." -- rhialto at falu dot nl --
Re: xhci "device problem, disabling port 5"
rhia...@falu.nl (Rhialto) writes: >> sudo drvctl -r -a usbdevif uhub1 >>=20 >> should work. >It works in the sense that it doesn't give any error. But it has no >noticable effect either, unfortunately. No messages printed on the >console, visible via dmesg or /var/log/messages. It does not clear the error condition nor re-enable a port. I'm not sure if you can recover from that condition except by a reboot.
Re: xhci "device problem, disabling port 5"
Hello, On Sun, Apr 25, 2021 at 09:32:27PM +0200, Rhialto wrote: > On my new computer I often have trouble with USB sticks (I haven't tried > other devices yet). Sometimes it works, more often it doesn't. > I encounter this too. Have you tried: # drvctl -r umass0 to see if the reattachment succeeds? -- Thierry Laronde http://www.kergis.com/ http://kertex.kergis.com/ http://www.sbfa.fr/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
Re: xhci "device problem, disabling port 5"
On Sun 25 Apr 2021 at 20:39:10 -, Michael van Elst wrote: > rhia...@falu.nl (Rhialto) writes: > > >hexander$ sudo drvctl -r uhub1 > >drvctl: DRVRESCANBUS: Invalid argument > > A bus can have the notion of an "interface attribute" that you must > pass. uhub knows about "usbifif" for network interfaces and "usbdevif" > for other devices like umass. > > sudo drvctl -r -a usbdevif uhub1 > > should work. It works in the sense that it doesn't give any error. But it has no noticable effect either, unfortunately. No messages printed on the console, visible via dmesg or /var/log/messages. I noticed that it takes a fairly long time between inserting the usb stick and the error messages. I tried issuing the above drvctl command in between, but that made no difference. -Olaf. -- ___ Q: "What's an anagram of Banach-Tarski?" -- Olaf "Rhialto" Seibert \X/ A: "Banach-Tarski Banach-Tarski." -- rhialto at falu dot nl signature.asc Description: PGP signature
Re: xhci "device problem, disabling port 5"
rhia...@falu.nl (Rhialto) writes: >hexander$ sudo drvctl -r uhub1 >drvctl: DRVRESCANBUS: Invalid argument A bus can have the notion of an "interface attribute" that you must pass. uhub knows about "usbifif" for network interfaces and "usbdevif" for other devices like umass. sudo drvctl -r -a usbdevif uhub1 should work.
Re: xhci "device problem, disabling port 5"
On Sun 25 Apr 2021 at 21:49:41 +0200, tlaro...@polynum.com wrote: > I encounter this too. Have you tried: > > # drvctl -r umass0 > > to see if the reattachment succeeds? hexander$ sudo drvctl -r umass0 drvctl: DRVRESCANBUS: Device not configured Maybe that's not so surprising, it probably didn't get far enough in creating an umass0 to know about it. Then I tried a level up (umass0 should attach to uhub1): hexander$ sudo drvctl -r uhub1 drvctl: DRVRESCANBUS: Invalid argument which is somewhat interesting (what would be invalid here)? It knows about the name uhub1, since this works: hexander$ sudo drvctl -tl uhub1 uhidev0 ukbd0 wskbd0 uhidev1 uhidev2 ums0 wsmouse0 uhid0 -Olaf. -- ___ Q: "What's an anagram of Banach-Tarski?" -- Olaf "Rhialto" Seibert \X/ A: "Banach-Tarski Banach-Tarski." -- rhialto at falu dot nl signature.asc Description: PGP signature
Re: nVidia woes
On Sun, 25 Apr 2021 20:50:47 +0200 Rhialto wrote: > My solution is probably going to be: get a Radeon HD-5450 card. You can > still get them, amazingly enough, although they seem to cost twice what > I paid in 2013. If you want a slightly newer GPU core than "Cedar", "Bonaire" works too. Most of the Rx 200 series should work. For example the Radeon R7 260 works well, even on aarch64. I think it is one of the last supported radeon cores in the current drm2 codebase.
xhci "device problem, disabling port 5"
On my new computer I often have trouble with USB sticks (I haven't tried other devices yet). Sometimes it works, more often it doesn't. $ egrep 'uhub|usb|xhci' /var/run/dmesg.boot xhci0 at pci0 dev 20 function 0: Intel 300 Series USB 3.1 xHCI (rev. 0x10) xhci0: 64-bit DMA xhci0: interrupting at msi1 vec 0 xhci0: xHCI version 1.10 usb0 at xhci0: USB revision 3.1 usb1 at xhci0: USB revision 2.0 uhub0 at usb0: NetBSD (0x) xHCI root hub (0x), class 9/0, rev 3.00/1.00, addr 0 uhub0: 6 ports with 6 removable, self powered uhub1 at usb1: NetBSD (0x) xHCI root hub (0x), class 9/0, rev 2.00/1.00, addr 0 uhub1: 16 ports with 16 removable, self powered uhidev0 at uhub1 port 7 configuration 1 interface 0 uhidev1 at uhub1 port 7 configuration 1 interface 1 uhidev2 at uhub1 port 8 configuration 1 interface 0 This insertion of the usb stick works (NetBSD install image): [ 156.881103] umass0 at uhub1 port 6 configuration 1 interface 0 [ 156.881103] umass0: vendor 058f (0x058f) product 6387 (0x6387), rev 2.00/1.05, addr 3 [ 156.881103] umass0: using SCSI over Bulk-Only [ 156.881103] scsibus0 at umass0: 2 targets, 1 lun per target [ 156.881103] sd0 at scsibus0 target 0 lun 0: disk removable [ 156.881103] sd0: fabricating a geometry [ 156.881103] sd0: 15120 MB, 15120 cyl, 64 head, 32 sec, 512 bytes/sect x 30965760 sectors [ 156.891104] sd0: fabricating a geometry [ 156.891104] sd0: GPT GUID: 0ca9a3fc-4cf9-4d38-a0a1-811076df4a52 [ 156.901104] dk3 at sd0: "EFI system", 262144 blocks at 2048, type: msdos [ 156.901104] dk4 at sd0: "88e567bf-a221-4bff-80cf-663f634b9b53", 2908160 blocks at 264192, type: ffs [ 175.291099] dk4 at sd0 (88e567bf-a221-4bff-80cf-663f634b9b53) deleted [ 175.291099] dk3 at sd0 (EFI system) deleted [ 175.291099] sd0: detached [ 175.291099] scsibus0: detached [ 175.291099] umass0: detached [ 175.291099] umass0: at uhub1 port 6 (addr 3) disconnected The next attempts fail: [ 194.001094] uhub1: port 5, set config at addr 4 failed [ 194.001094] uhub1: autoconfiguration error: device problem, disabling port 5 [ 230.311084] uhub1: port 2, set config at addr 5 failed [ 230.311084] uhub1: autoconfiguration error: device problem, disabling port 2 [ 424.421031] uhub1: port 6, set config at addr 6 failed [ 424.421031] uhub1: autoconfiguration error: device problem, disabling port 6 Any ideas? This isn't workable... -Olaf. -- ___ Q: "What's an anagram of Banach-Tarski?" -- Olaf "Rhialto" Seibert \X/ A: "Banach-Tarski Banach-Tarski." -- rhialto at falu dot nl signature.asc Description: PGP signature
Re: nVidia woes
On Sun 25 Apr 2021 at 18:18:36 +0200, Rhialto wrote: > X recognizes the card and also mostly works. At least, until it doesn't. > After a while the graphics just freeze. You can still move the mouse > (that's probably a sprite) and login via the network. Note this error during autoconfiguration: [ 3.536673] nouveau0: autoconfiguration error: error: priv: HUB0: 086014 (1f70820c) This shows up in dmesg (using a current kernel from a few days ago): [ 910.790338] nouveau0: autoconfiguration error: error: fifo: write fault at 000242 engine 00 [GR] client 0f [GPC0/PROP_0] reason 02 [PTE] on channel 2 [003fe12000 user] [ 910.790338] nouveau0: autoconfiguration error: error: fifo: gr engine fault on channel 2, recovering... [ 910.790338] nouveau0: autoconfiguration error: error: gr: TRAP ch 2 [003fe12000 user] [ 910.790338] nouveau0: autoconfiguration error: error: gr: DISPATCH badf1201 [ 910.790338] nouveau0: autoconfiguration error: error: gr: ROP0 badf1201 badf1201 [ 910.790338] nouveau0: autoconfiguration error: error: gr: TRAP UNHANDLED b8df1200 [ 910.790338] nouveau0: autoconfiguration error: error: bus: MMIO read of FAULT at 085048 [ IBUS ] [ 910.790338] nouveau0: autoconfiguration error: error: priv: HUB0: 400500 00010001 (1b708201) [ 910.790338] nouveau0: autoconfiguration error: error: priv: ROP0: 410144 c000 (1f708210) and nothing extra in Xorg.0.log. My solution is probably going to be: get a Radeon HD-5450 card. You can still get them, amazingly enough, although they seem to cost twice what I paid in 2013. -Olaf. -- ___ Q: "What's an anagram of Banach-Tarski?" -- Olaf "Rhialto" Seibert \X/ A: "Banach-Tarski Banach-Tarski." -- rhialto at falu dot nl signature.asc Description: PGP signature
Re: nVidia woes
Here are the dmesg and the Xorg log file. [ 1.00] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, [ 1.00] 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, [ 1.00] 2018, 2019, 2020 The NetBSD Foundation, Inc. All rights reserved. [ 1.00] Copyright (c) 1982, 1986, 1989, 1991, 1993 [ 1.00] The Regents of the University of California. All rights reserved. [ 1.00] NetBSD 9.1 (GENERIC) #0: Sun Oct 18 19:24:30 UTC 2020 [ 1.00] mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC [ 1.00] total memory = 65453 MB [ 1.00] avail memory = 63530 MB [ 1.00] cpu_rng: RDSEED [ 1.00] rnd: seeded with 256 bits [ 1.00] timecounter: Timecounters tick every 10.000 msec [ 1.00] Kernelized RAIDframe activated [ 1.00] running cgd selftest aes-xts-256 aes-xts-512 done [ 1.00] timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100 [ 1.03] System manufacturer System Product Name (System Version) [ 1.03] mainbus0 (root) [ 1.03] ACPI: RSDP 0x000F05B0 24 (v02 ALASKA) [ 1.03] ACPI: XSDT 0x9E7B70B0 D4 (v01 ALASKA A M I 01072009 AMI 00010013) [ 1.03] ACPI: FACP 0x9E7F7708 000114 (v06 ALASKA A M I 01072009 AMI 00010013) [ 1.03] ACPI: DSDT 0x9E7B7218 0404ED (v02 ALASKA A M I 01072009 INTL 20160527) [ 1.03] ACPI: FACS 0x9EC52080 40 [ 1.03] ACPI: APIC 0x9E7F7820 A0 (v04 ALASKA A M I 01072009 AMI 00010013) [ 1.03] ACPI: FPDT 0x9E7F78C0 44 (v01 ALASKA A M I 01072009 AMI 00010013) [ 1.03] ACPI: FIDT 0x9E7F7908 9C (v01 ALASKA A M I 01072009 AMI 00010013) [ 1.03] ACPI: MCFG 0x9E7F79A8 3C (v01 ALASKA A M I 01072009 MSFT 0097) [ 1.03] ACPI: WSMT 0x9E808480 28 (v01 ALASKA A M I 01072009 AMI 00010013) [ 1.03] ACPI: SSDT 0x9E7F7A40 001B1C (v02 CpuRef CpuSsdt 3000 INTL 20160527) [ 1.03] ACPI: SSDT 0x9E7F9560 003099 (v02 SaSsdt SaSsdt 3000 INTL 20160527) [ 1.03] ACPI: SSDT 0x9E7FC600 00232B (v02 PegSsd PegSsdt 1000 INTL 20160527) [ 1.03] ACPI: HPET 0x9E7FE930 38 (v01 ALASKA A M I 0002 0113) [ 1.03] ACPI: SSDT 0x9E7FE968 000FAE (v02 ALASKA Ther_Rvp 1000 INTL 20160527) [ 1.03] ACPI: SSDT 0x9E7FF918 002FD0 (v02 INTEL xh_cfsd4 INTL 20160527) [ 1.03] ACPI: UEFI 0x9E8028E8 42 (v01 ALASKA A M I 0002 0113) [ 1.03] ACPI: LPIT 0x9E802930 94 (v01 ALASKA A M I 0002 0113) [ 1.03] ACPI: SSDT 0x9E8029C8 0027DE (v02 ALASKA PtidDevc 1000 INTL 20160527) [ 1.03] ACPI: SSDT 0x9E8051A8 0014E2 (v02 ALASKA TbtTypeC INTL 20160527) [ 1.03] ACPI: DBGP 0x9E806690 34 (v01 ALASKA A M I 0002 0113) [ 1.03] ACPI: DBG2 0x9E8066C8 54 (v00 ALASKA A M I 0002 0113) [ 1.03] ACPI: SSDT 0x9E806720 001B67 (v02 ALASKA UsbCTabl 1000 INTL 20160527) [ 1.03] ACPI: DMAR 0x9E808288 70 (v01 INTEL EDK2 0002 0113) [ 1.03] ACPI: SSDT 0x9E8082F8 000144 (v02 Intel ADebTabl 1000 INTL 20160527) [ 1.03] ACPI: WPBT 0x9E808440 3C (v01 ALASKA A M I 0001 ASUS 0001) [ 1.03] ACPI: 10 ACPI AML tables successfully acquired and loaded [ 1.03] ioapic0 at mainbus0 apid 2: pa 0xfec0, version 0x20, 120 pins [ 1.03] cpu0 at mainbus0 apid 0 [ 1.03] cpu0: CPU base freq 37 Hz [ 1.03] cpu0: CPU max freq 46 Hz [ 1.03] cpu0: TSC freq CPUID 369600 Hz [ 1.03] cpu0: Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz, id 0x906ed [ 1.03] cpu0: package 0, core 0, smt 0 [ 1.03] cpu1 at mainbus0 apid 2 [ 1.03] cpu1: Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz, id 0x906ed [ 1.03] cpu1: package 0, core 1, smt 0 [ 1.03] cpu2 at mainbus0 apid 4 [ 1.03] cpu2: Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz, id 0x906ed [ 1.03] cpu2: package 0, core 2, smt 0 [ 1.03] cpu3 at mainbus0 apid 6 [ 1.03] cpu3: Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz, id 0x906ed [ 1.03] cpu3: package 0, core 3, smt 0 [ 1.03] cpu4 at mainbus0 apid 8 [ 1.03] cpu4: Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz, id 0x906ed [ 1.03] cpu4: package 0, core 4, smt 0 [ 1.03] cpu5 at mainbus0 apid 10 [ 1.03] cpu5: Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz, id 0x906ed [ 1.03] cpu5: package 0, core 5, smt 0 [ 1.03] acpi0 at mainbus0: Intel ACPICA 20190405 [ 1.03]
nVidia woes
I recently got a new computer, and because the shop where I was putting it together didn't have a Radeon HD-5450 (which I know that works), instead I chose a "ASUS GeForce GT 710 Silent, 1024 MB GDDR5". This is apparently of the Kepler chipset generation, which we're supposedly supporting in the nouveau driver (the one we have is not the newest..) (sources: https://nouveau.freedesktop.org/CodeNames.html#NVE0 https://nouveau.freedesktop.org/FeatureMatrix.html ) I installed 9.1. This sort of... works... Booting it in BIOS mode at least. But during kernel configuration it sometimes has long pauses in it, like some time-out. There are also graphics artifacts in "text mode" (before I start X). Some parts of the text are not written on the screen, and/or there are short horizontal lines in empty space. X recognizes the card and also mostly works. At least, until it doesn't. After a while the graphics just freeze. You can still move the mouse (that's probably a sprite) and login via the network. It's tantalizingly close to actually working like this... -Olaf. -- ___ Q: "What's an anagram of Banach-Tarski?" -- Olaf "Rhialto" Seibert \X/ A: "Banach-Tarski Banach-Tarski." -- rhialto at falu dot nl signature.asc Description: PGP signature
nvmm doesn't work on "Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz"?
Hi all, I've just bought a new computer with a "Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz" cpu. I have enabled VMX and VT-d in the "BIOS", but nvmm doesn't seem to work on it. It's not reported in the kernel boot messages; on my old computer it is. $ qemu-system-x86_64 -accel nvmm qemu-system-x86_64: -accel nvmm: NVMM: Initialization failed, error=6 qemu-system-x86_64: -accel nvmm: failed to initialize nvmm: Device not configured This is what cpuctl says about the CPU; which details should I look at? bash-5.1$ cpuctl identify 0 Cannot bind to target CPU. Output may not accurately describe the target. Run as root to allow binding. cpu0: highest basic info 0016 cpu0: highest extended info 8008 cpu0: "Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz" cpu0: Intel 7th or 8th gen Core (Kaby Lake, Coffee Lake) or Xeon E (Coffee Lake) (686-class), 3696.00 MHz cpu0: CPU base freq 37 Hz cpu0: CPU max freq 46 Hz cpu0: TSC freq CPUID 369600 Hz cpu0: family 0x6 model 0x9e stepping 0xd (id 0x906ed) cpu0: features 0xbfebfbff cpu0: features 0xbfebfbff cpu0: features 0xbfebfbff cpu0: features1 0x7ffafbff cpu0: features1 0x7ffafbff cpu0: features1 0x7ffafbff cpu0: features1 0x7ffafbff cpu0: features2 0x2c100800 cpu0: features3 0x121 cpu0: features5 0x29c6fbf cpu0: features5 0x29c6fbf cpu0: features5 0x29c6fbf cpu0: features6 0x4000 cpu0: features7 0xbc000600 cpu0: features7 0xbc000600 cpu0: xsave features 0x1f cpu0: xsave instructions 0xf cpu0: xsave area size: current 832, maximum 1088, xgetbv enabled cpu0: enabled xsave 0x7 cpu0: I-cache 32KB 64B/line 8-way, D-cache 32KB 64B/line 8-way cpu0: L2 cache 256KB 64B/line 4-way cpu0: L3 cache 9MB 64B/line 12-way cpu0: 64B prefetching cpu0: ITLB 128 4KB entries 8-way, 2M/4M: 8 entries cpu0: DTLB 64 4KB entries 4-way cpu0: L2 STLB 1536 4KB entries 6-way cpu0: L1 1GB page DTLB 4 1GB entries 4-way cpu0: Initial APIC ID 6 cpu0: Cluster/Package ID 0 cpu0: Core ID 3 cpu0: SMT ID 0 cpu0: MONITOR/MWAIT extensions 0x3 cpu0: monitor-line size 64 cpu0: C1 substates 2 cpu0: C2 substates 1 cpu0: C3 substates 2 cpu0: C4 substates 4 cpu0: C5 substates 1 cpu0: C6 substates 1 cpu0: C7 substates 1 cpu0: DSPM-eax 0x27f7 cpu0: DSPM-eax 0x27f7 cpu0: DSPM-ecx 0x1 cpu0: SEF highest subleaf cpu0: Power Management features: 0x100 cpu0: Perfmon-eax 0x7300804 cpu0: Perfmon-eax 0x7300804 cpu0: Perfmon-edx 0x603 cpu0: microcode version 0xd6, platform ID 1 On my old computer, it is loke this, and the features with VM in them look the same (VME, VMX). $ cpuctl identify 0 Cannot bind to target CPU. Output may not accurately describe the target. Run as root to allow binding. cpu0: highest basic info 000d cpu0: highest extended info 8008 cpu0: "Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz" cpu0: Intel Xeon E3-12xx, 2nd gen i7, i5, i3 2xxx (686-class), 3292.74 MHz cpu0: family 0x6 model 0x2a stepping 0x7 (id 0x206a7) cpu0: features 0xbfebfbff cpu0: features 0xbfebfbff cpu0: features 0xbfebfbff cpu0: features1 0x1d9ae3bf cpu0: features1 0x1d9ae3bf cpu0: features1 0x1d9ae3bf cpu0: features2 0x28100800 cpu0: features3 0x1 cpu0: xsave features 0x7 cpu0: xsave instructions 0x1 cpu0: xsave area size: current 832, maximum 832, xgetbv enabled cpu0: enabled xsave 0x7 cpu0: I-cache 32KB 64B/line 8-way, D-cache 32KB 64B/line 8-way cpu0: L2 cache 256KB 64B/line 8-way cpu0: L3 cache 3MB 64B/line 12-way cpu0: 64B prefetching cpu0: ITLB 64 4KB entries 4-way, 2M/4M: 8 entries cpu0: DTLB 64 4KB entries 4-way, 2M/4M: 32 entries (L0) cpu0: L2 STLB 512 4KB entries 4-way cpu0: Initial APIC ID 3 cpu0: Cluster/Package ID 0 cpu0: Core ID 1 cpu0: SMT ID 1 cpu0: MONITOR/MWAIT extensions 0x3 cpu0: monitor-line size 64 cpu0: C1 substates 2 cpu0: C2 substates 1 cpu0: C3 substates 1 cpu0: DSPM-eax 0x75 cpu0: DSPM-ecx 0x9 cpu0: SEF highest subleaf cpu0: Power Management features: 0x100 cpu0: Perfmon-eax 0x7300403 cpu0: Perfmon-eax 0x7300403 cpu0: Perfmon-edx 0x603 cpu0: microcode version 0x26, platform ID 1 -Olaf. -- ___ Q: "What's an anagram of Banach-Tarski?" -- Olaf "Rhialto" Seibert \X/ A: "Banach-Tarski Banach-Tarski." -- rhialto at falu dot nl signature.asc Description: PGP signature
Re: XDG_RUNTIME_DIR
On Sat, 24 Apr 2021, Steffen Nurpmeso wrote:
If you run Linux you could also use the pam_xdg module i have
written. For example my /etc/pam.d/common-session is
session optional pam_xdg.so notroot
session requiredpam_unix.so quiet
and the stuff is as attached. It handles the other directories of
the standard as well.
This is, I presume, for Linux systems without systemd and pam_env.so?
Because, the vast thing that is systemd, takes care of mounting a /run
and creating user dirs. inside it; and pam_env.so can read
/etc/environment{,.d/*} and /etc/security/pam_env.conf files where you
can set these system-wide env. vars.
I haven't gone through your code in detail, but, I noticed these small
issues:
Line 40: a_RUNTIME_DIR_BASE_MODE should be mode 0700. All dirs. under
/run are set that way, I think.
Line 77: That ORing is a bit of an odd way to set that buffer size (if
that isn't a typo). Maybe comment is as such?
There should be a removal of the dirs. on the user's final session
logout, I think.
Thanks,
-RVP
Re: XDG_RUNTIME_DIR
On Sun, 25 Apr 2021, RVP wrote: And,... it worked flawlessly. My recommendation: install the binary package. :) Can you add lines like these to /etc/fstab if they're not already there? They're needed for some large, complex programs--and lyx seems to fit that category, now. kernfs /kern kernfs rw ptyfs /dev/pts ptyfs rw procfs /proc procfs rw tmpfs /var/shm tmpfs rw,-m1777,-sram%25 -RVP
Re: XDG_RUNTIME_DIR
On Sun, 25 Apr 2021, Bob Bernstein wrote: dbus is launching via standard rc.conf mechanism, with a 'starting dbus' message displayed during boot. Do you suppose I need the 'dbus-launch' statement in addition to that? Strictly speaking: no. Applications which need DBUS will launch a per-user instance of the daemon, once, when needed. You don't need to start one. I do it that way, in ~/.xinitrc, because I want it to _exit_ when I quit X. Else, it persists until I log out. I now have showing in 'env': XDG_RUNTIME_DIR=/tmp/runtime-bob Fine. There is also a XDG_CONFIG_HOME--defaulting to ~/.config and, fwiw: QTDIR=/usr/pkg/qt5 This is only needed for compiling, I think. AT THIS STAGE of the game, at least on launch from the command-line lyx is not just crashing and dumping core. 'ps' shows a running lyx process, but it doesn't seem able to reach the point whereat it would display itself. I have DISPLAY set in the env: DISPLAY=:0 Right, that last bit about setting DISPLAY worries me. You shouldn't need to set this at all, normally. What was it before you set it (i.e. in an xterm window)? As a test, I just installed lyx from the binary package: After installing what seemed like everything Knuth wrote going back to 1978, it installed itself fine. Running it produced a missing library (libmagic.so.6) error. That fixed (I'm on 9.99.81 which has libmagic.so.7), I unset all XDG-related env. vars (only 2); stopped running dbus-launch in .xinitrc; logged out; logged-in and ran lyx. And,... it worked flawlessly. My recommendation: install the binary package. :) -RVP
Re: NetBSD on bhyve on TrueNAS Core
> > userconf disable xhci* Thanks, that did the trick! I submitted a dmesg at https://dmesgd.nycbug.org/index.cgi?do=view=6024 :) > I mean, for the installation you will have to quickly go to the vnc > window, interrupt the boot to command line and enter 'boot -c'; then There is a trick for this: in the VNC settings, you can enable a checkbox that pauses the boot until you have connected to VNC. -- Benny
Re: NetBSD on bhyve on TrueNAS Core
On Sun, 25 Apr 2021 at 06:08, Thomas Mueller wrote: > > Excerpt from Chavdar Ivanov: > > > userconf disable xhci* > > > I mean, for the installation you will have to quickly go to the vnc > > window, interrupt the boot to command line and enter 'boot -c'; then > > > disable xhci > > quit > > > Then go through the installation as normal, GPT etc. After it > > finishes, go to the command line, mount your root dk (should be dk1) > > and add the above line to /boot.cfg . > > Chavdar > > I thought USB 3 with xhci was working on NetBSD. Have some bugs recently > arisen? It is bhyve what is crashing when xhci comes to be configured; otherwise xhci - on a real host - is working. I see my first NetBSD-current vm installation under FreeNAS to have had the same problem on the 5th of February this year - as is now. It is not clear therefore where the problem is, but I would say the virtualizer shouldn't crash when the guest has a problem of a kind - if it can't deal with the presented configuration, it should be able to gracefully quit. > > Bad enough that I have to disable athn; athn causes the boot to hang: maybe > fixed in more recent versions? > > Other question is whether an ext2fs would successfully copy to a partition on > a USB stick or hard drive. > > But it was "disable xhci" in your message that raised the alarm in me. > > Tom > --
