openbsd-current on yandex cloud

[Mikhail]

I'm trying to start openbsd on yandex cloud, it starts fine, but hangs
in the boot process.

I tried

boot -d
w db_console 1
c
ctrl-alt-esc

But the keypress doesn't bring me into debugger.

Any recommendations on how to debug this stuff?

Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2023 OpenBSD. All rights reserved.  https://www.OpenBSD.org

OpenBSD 7.4-current (GENERIC) #1353: Fri Oct 20 09:50:25 MDT 2023
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 2130558976 (2031MB)
avail mem = 2046406656 (1951MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf5780 (10 entries)
bios0: vendor SeaBIOS version "1.16.1-1" date 04/01/2014
bios0: Yandex xeon-gold-6338
acpi0 at bios0: ACPI 3.0
acpi0: sleep states S3 S4 S5
acpi0: tables DSDT FACP APIC HPET SRAT MCFG
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel Xeon Processor (Icelake), 1995.43 MHz, 06-6a-00
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,MD_CLEAR,IBRS,IBPB,STIBP,SSBD,ARAT,IBRS_ALL,SKIP_L1DFL,MDS_NO,IF_PSCHANGE,XSAVEOPT,XSAVEC,XGETBV1
cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 4MB 64b/line 
16-way L2 cache, 16MB 64b/line 16-way L3 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 1000MHz
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 0 pa 0xfec0, version 11, 24 pins
acpihpet0 at acpi0: 1 Hz
acpimcfg0 at acpi0
acpimcfg0: addr 0xb000, bus 0-255
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 137 (PC89)
acpiprt2 at acpi0: bus 128 (PC80)
"ACPI0006" at acpi0 not configured
acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001
acpicmos0 at acpi0
com0 at acpi0 COM1 addr 0x3f8/0x8 irq 4: ns16550a, 16 byte fifo
com0: console
com1 at acpi0 COM2 addr 0x2f8/0x8 irq 3: ns16550a, 16 byte fifo
com2 at acpi0 COM3 addr 0x3e8/0x8 irq 6: ns16550a, 16 byte fifo
com3 at acpi0 COM4 addr 0x2e8/0x8 irq 7: ns16550a, 16 byte fifo
"PNP0A06" at acpi0 not configured
"PNP0A06" at acpi0 not configured
"QEMU0002" at acpi0 not configured
"ACPI0010" at acpi0 not configured
acpipci1 at acpi0 PC89: 0x 0x0011 0x0001
acpipci2 at acpi0 PC80: 0x 0x0011 0x0001
acpicpu0 at acpi0: C1(@1 halt!)
pvbus0 at mainbus0: KVM
pvclock0 at pvbus0
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82G33 Host" rev 0x00
vga1 at pci0 dev 1 function 0 "Bochs VGA" rev 0x02
wsdisplay at vga1 not configured
ehci0 at pci0 dev 2 function 0 "Intel 82801DB USB" rev 0x10: apic 0 int 21
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
pchb1 at pci0 dev 3 function 0 vendor "Red Hat", unknown product 0x000b rev 0x00
pchb2 at pci0 dev 4 function 0 vendor "Red Hat", unknown product 0x000b rev 0x00
pcib0 at pci0 dev 31 function 0 "Intel 82801IB LPC" rev 0x02
ichiic0 at pci0 dev 31 function 3 "Intel 82801I SMBus" rev 0x02: apic 0 int 16
iic0 at ichiic0
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
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
pci1 at mainbus0 bus 137
ppb0 at pci1 dev 0 function 0 vendor "Red Hat", unknown product 0x000c rev 
0x00: apic 0 int 11
pci2 at ppb0 bus 138
virtio0 at pci2 dev 0 function 0 "Qumranet Virtio Network" rev 0x00
vio0 at virtio0: address d0:0d:17:f6:1c:cf
virtio0: msix per-VQ
ppb1 at pci1 dev 1 function 0 vendor "Red Hat", unknown product 0x000c rev 
0x00: apic 0 int 10
pci3 at ppb1 bus 139
ppb2 at pci1 dev 2 function 0 vendor "Red Hat", unknown product 0x000c rev 
0x00: apic 0 int 10
pci4 at ppb2 bus 140
ppb3 at pci1 dev 3 function 0 vendor "Red Hat", unknown product 0x000c rev 
0x00: apic 0 int 11
pci5 at ppb3 bus 141
ppb4 at pci1 dev 4 function 0 vendor "Red Hat", unknown product 0x000c rev 
0x00: apic 0 int 11
pci6 at ppb4 bus 142
ppb5 at pci1 dev 5 function 0 vendor "Red Hat", unknown product 0x000c rev 
0x00: apic 0 int 10
pci7 at ppb5 bus 143
ppb6 at pci1 dev 6 function 0 vendor "Red Hat", unknown product 0x000c rev 
0x00: apic 0 int 10
pci8 at ppb6 bus 144
ppb7 at pci1 dev 7 function 0 vendor "Red Hat", unknown product 0x000c rev 
0x00: apic 0 int 11
pci9 at ppb7 bus 145
pci10 at mainbus0 bus 128
ppb8 at pci10 dev 0 function 0 vendor "Red 

OpenBSD-current boot stuck at efi0 entry

[Mihai Popescu]

I was trying to install OpenBSD-current from snapshots, UEFI mode boot
and GPT disk - the install went fine, but the boot after installation
remains stuck at efi0 entry listing. I have to use the switch off
button to exit from this.
The install and boot works if I use Legacy mode boot with MBR disk.
Here is the sequence i got with UEFI mode now

[ using 3299768 bytes of bsd ELF symbol table ]
OpenBSD 7.2-current (GENERIC.MP) #819: Thu Oct 27 20:41:32 MDT 2022
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 7711522816 (7354MB)
avail mem = 7460280672 (7114MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe86ed (64 entries)
bios0: vendor Hewlett-Packard version "K06 v02.77" date 03/22/2018
bios0: Hewlett-Packard HP Compaq Pro 6305 SFF
efi0 at bios0: UEFI 2.3.1
efi0: American Megatrends rev 0x4028d
>>> boot sequence stuck here <<<

I was using this computer with boot in UEFI mode and GPT disk a few
months ago and things went fine. I don't think I have a dmesg from
then, but if I recall the efi0 was not there or was labeled as not
configured.

The dmesg from Legacy mode and MBR disk, now:

OpenBSD 7.2-current (GENERIC.MP) #819: Thu Oct 27 20:41:32 MDT 2022
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 7711543296 (7354MB)
avail mem = 7460421632 (7114MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe86ed (64 entries)
bios0: vendor Hewlett-Packard version "K06 v02.77" date 03/22/2018
bios0: Hewlett-Packard HP Compaq Pro 6305 SFF
acpi0 at bios0: ACPI 5.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT MCFG HPET SSDT MSDM TCPA IVRS SSDT SSDT CRAT
acpi0: wakeup devices SBAZ(S4) PS2K(S3) PS2M(S3) P0PC(S4) PE20(S4)
PE21(S4) PE22(S4) BNIC(S4) PE23(S4) BR12(S4) BR14(S4) OHC1(S3)
EHC1(S3) OHC2(S3) EHC2(S3) OHC3(S3) [...]
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 16 (boot processor)
cpu0: AMD A8-5500B APU with Radeon(tm) HD Graphics, 3194.15 MHz, 15-10-01
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,TCE,NODEID,TBM,TOPEXT,CPCTR,ITSC,BMI1,IBPB
cpu0: 16KB 64b/line 4-way D-cache, 64KB 64b/line 2-way I-cache, 2MB
64b/line 16-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, IBE
cpu1 at mainbus0: apid 17 (application processor)
cpu1: AMD A8-5500B APU with Radeon(tm) HD Graphics, 3194.05 MHz, 15-10-01
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,TCE,NODEID,TBM,TOPEXT,CPCTR,ITSC,BMI1,IBPB
cpu1: 16KB 64b/line 4-way D-cache, 64KB 64b/line 2-way I-cache, 2MB
64b/line 16-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 18 (application processor)
cpu2: AMD A8-5500B APU with Radeon(tm) HD Graphics, 3194.05 MHz, 15-10-01
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,TCE,NODEID,TBM,TOPEXT,CPCTR,ITSC,BMI1,IBPB
cpu2: 16KB 64b/line 4-way D-cache, 64KB 64b/line 2-way I-cache, 2MB
64b/line 16-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 19 (application processor)
cpu3: AMD A8-5500B APU with Radeon(tm) HD Graphics, 3194.05 MHz, 15-10-01
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,TCE,NODEID,TBM,TOPEXT,CPCTR,ITSC,BMI1,IBPB
cpu3: 16KB 64b/line 4-way D-cache, 64KB 64b/line 2-way I-cache, 2MB
64b/line 16-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 5 pa 0xfec0, version 21, 24 pins
acpimcfg0 at acpi0
acpimcfg0: addr 0xf000, bus 0-63
acpihpet0 at acpi0: 14318180 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (BR13)
acpiprt2 at acpi0: bus -1 (BR15)
acpiprt3 at acpi0: bus -1 (BR16)
acpiprt4 at acpi0: bus -1 (BR17)
acpiprt5 at acpi0: bus 1 (P0PC)
acpiprt6 at acpi0: bus 2 

OpenBSD-current freeze at boot on efi0

[Mihai Popescu]

Hello,

I did an OpenBSD-current installation from snapshots on a computer I
use to run OpenBSD a few months ago. I used UEFI boot with GPT disk
format since it was working fine in the past. I was able to boot the
installer, the setup completed fine, but the boot process was stuck at
efi0: device entry. This was not in the old dmesg ... or maybe was
something like not configured. It appears now with some bios data
filled in.

I switched to legacy bios, MBR disk and all is good.

-current dmesg legacy bios and MBR-

OpenBSD 7.2-current (RAMDISK_CD) #726: Sat Oct  1 22:52:56 MDT 2022
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
real mem = 7711543296 (7354MB)
avail mem = 7473811456 (7127MB)
random: good seed from bootblocks
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe86ed (64 entries)
bios0: vendor Hewlett-Packard version "K06 v02.77" date 03/22/2018
bios0: Hewlett-Packard HP Compaq Pro 6305 SFF
acpi0 at bios0: ACPI 5.0
acpi0: tables DSDT FACP APIC FPDT MCFG HPET SSDT MSDM TCPA IVRS SSDT SSDT CRAT
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 16 (boot processor)
cpu0: AMD A8-5500B APU with Radeon(tm) HD Graphics, 3194.43 MHz, 15-10-01
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,XOP,SKINIT,WDT,FMA4,TCE,NODEID,TBM,TOPEXT,CPCTR,ITSC,BMI1,IBPB
cpu0: 16KB 64b/line 4-way D-cache, 64KB 64b/line 2-way I-cache, 2MB
64b/line 16-way L2 cache
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, IBE
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 5 pa 0xfec0, version 21, 24 pins
acpihpet0 at acpi0: 14318180 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (BR13)
acpiprt2 at acpi0: bus -1 (BR15)
acpiprt3 at acpi0: bus -1 (BR16)
acpiprt4 at acpi0: bus -1 (BR17)
acpiprt5 at acpi0: bus 1 (P0PC)
acpiprt6 at acpi0: bus 2 (PE20)
acpiprt7 at acpi0: bus -1 (PE21)
acpiprt8 at acpi0: bus 3 (PE22)
acpiprt9 at acpi0: bus -1 (PE23)
acpiprt10 at acpi0: bus -1 (BR12)
acpiprt11 at acpi0: bus -1 (BR14)
acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001
acpicmos0 at acpi0
com0 at acpi0 UAR1 addr 0x3f8/0x8 irq 4: ns16550a, 16 byte fifo
com1 at acpi0 UAR2 addr 0x2f8/0x8 irq 3: ns16550a, 16 byte fifo
"IFX0102" at acpi0 not configured
"PNP0C0C" at acpi0 not configured
"PNP0C14" at acpi0 not configured
acpicpu at acpi0 not configured
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "AMD 15/1xh Host" rev 0x00
"AMD 15/1xh IOMMU" rev 0x00 at pci0 dev 0 function 2 not configured
vga1 at pci0 dev 1 function 0 "ATI Radeon HD 7560D" rev 0x00
wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation)
vendor "ATI", unknown product 0x9902 (class multimedia subclass
hdaudio, rev 0x00) at pci0 dev 1 function 1 not configured
xhci0 at pci0 dev 16 function 0 "AMD Hudson-2 xHCI" rev 0x03: msi, xHCI 0.96
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 configuration 1 interface 0 "AMD xHCI root hub" rev
3.00/1.00 addr 1
xhci1 at pci0 dev 16 function 1 "AMD Hudson-2 xHCI" rev 0x03: msi, xHCI 0.96
usb1 at xhci1: USB revision 3.0
uhub1 at usb1 configuration 1 interface 0 "AMD xHCI root hub" rev
3.00/1.00 addr 1
ahci0 at pci0 dev 17 function 0 "AMD Hudson-2 SATA" rev 0x40: msi, AHCI 1.3
ahci0: port 0: 6.0Gb/s
ahci0: port 2: 1.5Gb/s
scsibus0 at ahci0: 32 targets
sd0 at scsibus0 targ 0 lun 0:  naa.5000c5006520feaf
sd0: 238475MB, 512 bytes/sector, 488397168 sectors
cd0 at scsibus0 targ 2 lun 0:  removable
ohci0 at pci0 dev 18 function 0 "AMD Hudson-2 USB" rev 0x11: apic 5
int 18, version 1.0, legacy support
ehci0 at pci0 dev 18 function 2 "AMD Hudson-2 USB2" rev 0x11: apic 5 int 17
usb2 at ehci0: USB revision 2.0
uhub2 at usb2 configuration 1 interface 0 "AMD EHCI root hub" rev
2.00/1.00 addr 1
ohci1 at pci0 dev 19 function 0 "AMD Hudson-2 USB" rev 0x11: apic 5
int 18, version 1.0, legacy support
ehci1 at pci0 dev 19 function 2 "AMD Hudson-2 USB2" rev 0x11: apic 5 int 17
usb3 at ehci1: USB revision 2.0
uhub3 at usb3 configuration 1 interface 0 "AMD EHCI root hub" rev
2.00/1.00 addr 1
"AMD Hudson-2 SMBus" rev 0x14 at pci0 dev 20 function 0 not configured
"AMD Hudson-2 HD Audio" rev 0x01 at pci0 dev 20 function 2 not configured
"AMD Hudson-2 LPC" rev 0x11 at pci0 dev 20 function 3 not configured
ppb0 at pci0 dev 20 function 4 "AMD Hudson-2 PCI" rev 0x40
pci1 at ppb0 bus 1
ohci2 at pci0 dev 20 function 5 "AMD Hudson-2 USB" rev 0x11: apic 5
int 18, version 1.0, legacy support
ppb1 at pci0 dev 21 function 0 "AMD Hudson-2 PCI

Encrypted home + hibernate: drives states? [ OpenBSD -current ]

[martin mag]

Hello!

My current partition setup is as follows (one SSD Disk, using -current
default kernel )
sd0a   100G RAID  == bioctl -c C -k sd1a ==> a=/
  b=swap

.  .

 p=/home (for sysupgrade to

 work without troubles)
sd0d   350G RAID  == bioctl -c C -C noauto -k sd1d ==>   a=/home/mmartin

(BTW, I use duids but for the sake of readers, using dev label here)

* Decryption of sd0a is done automatically at boot time => Perfect

* Decryption of sd0d (not automatically decrypted, see -C noauto),
is done with a modified rc script (just after wsconsctl), but it could be
done in /etc/rc.local (I just don't want to leave my keydisk too long
on my computer, personal preference ... debatable for sure).

I can run suspend (zzz) without any issue (but as I'm using FDE, I prefer not to
use it as encryption would be useless) and hibernate (ZZZ) seem to work
perfectly fine. The only problem I have is understanding in what state is
my sd0d partition.

sd0a is the encrypted root partition, automatically handled by the OS so when
waking from an hibernate state, the usb key needs to be inserted =>
When in hibernate mode, I assume sd0a is encrypted then .. right?

Now, as sd0d is handled manually (in /etc/rc or /etc/rc.local), I
don't really get in
which state it is when in hibernate mode. It doesn't seem to be
encrypted because
the usb key is not needed at wakeup time (or is it?.. but some key is
stored within the
image that is dumped to swap?. My first thought was that unmount /
detaching bioctl
should happen AFTER the system image is dumped to swap (so this cannot be
handled in /etc/apm/* files ... right?).
At the same time, I don't understand HOW it could not be encrypted as
powering off
the laptop (hibernate behaviour) will force bioctl to detach => hence
keep the drive
encrypted while powered off .. right?
Because of that, is there a high risk of getting corrupted data when
waking the laptop
up from hibernate state?

Last thing: If my /home/mmartin partition is not on the same drive or
partition as root,
should I avoid using hibernate if my laptop needs to be securely
powered-off? (swap
is on the encrypted drive sd0a (encrypted twice then but I read on
this mailing list that
the overhead is so low that everyone should do that if using FDE) so
is no factor
for a security breach)

Thank you very much!

PS: I use the -C noauto for my home partition because, IRL, I have a
small password
encrypted partition on the keydisk that, when decrypted, contains the key to
decrypt my home partition. (so automatic decryption is not going to
work for me).

Re: [OpenBSD -current] Change event timer in main loop with kqueue

[Visa Hankala]

Moving to tech@.

On Fri, Feb 26, 2021 at 09:42:07PM +0100, martin mag wrote:
> I've been trying to use kqueue for the last couple of day but I keep
> having an issue with EVFILT_TIMER filter. (I'm running Openbsd
> -current)
> 
> Right now, I'm trying to do the following:
> 1) Initilialize a timer event @ 200ms, periodically.
> 2) Inside the main event loop => If this event is retrieved, print
> elapsed time since last one
> 3) After 2 iterations, MODIFY the timer event to 1000ms and continue the loop
> 4) Code stops after 4 iterations as pb arise after the first timer
> change @ iteration 2.
> 
> Reading the manpages kqueue(2), one sees that:
> ** ) An event is uniquely defined by the pair (ident, filter) ==>
> in the example below (TIMER1, EVFILT_TIMER)
> **)  "" Re-adding an existing event will modify the parameters of
> the original event, and not result in a duplicate entry. "" => So
> re-adding the event (TIMER1, EVFILT_TIMER) with a modified field
> 'data' should update the timer from 200ms to 1000ms.
> 
> => Apparently, timer is updated, but not in the way I expected.

The kernel does not reschedule the timer when the user changes the
timeout period. The new period will take effect only after the current
period has expired. This is not explained in the manual page, though.

With the recent kqueue changes, it is straightforward to make the kernel
modify an existing timer. I think the clearest behaviour is to reset the
timer completely when it is modified. If there are pending events, they
should be cancelled because they do not necessarily correspond to the
new settings.

When f_modify and f_process are present in kqread_filtops, filt_timer
is not used. filt_timerexpire() activates timer knotes directly using
knote_activate() instead of KNOTE().

However, the current behaviour has been around so long that one can
argue that it is an actual feature. BSDs are not consistent with this,
though. FreeBSD resets the timer immediately, whereas NetBSD and
DragonFly BSD apply the new period after expiry.

I guess the resetting is harmless in most cases but might wreak havoc
at least with software that keeps poking its timers before expiry.

Index: lib/libc/sys/kqueue.2
===
RCS file: src/lib/libc/sys/kqueue.2,v
retrieving revision 1.43
diff -u -p -r1.43 kqueue.2
--- lib/libc/sys/kqueue.2   14 Nov 2020 10:16:15 -  1.43
+++ lib/libc/sys/kqueue.2   27 Feb 2021 12:54:27 -
@@ -468,6 +468,11 @@ contains the number of times the timeout
 This filter automatically sets the
 .Dv EV_CLEAR
 flag internally.
+.Pp
+If an existing timer is re-added, the existing timer and related pending events
+will be cancelled.
+The timer will be re-started using the timeout period
+.Fa data .
 .It Dv EVFILT_DEVICE
 Takes a descriptor as the identifier and the events to watch for in
 .Fa fflags ,
Index: sys/kern/kern_event.c
===
RCS file: src/sys/kern/kern_event.c,v
retrieving revision 1.161
diff -u -p -r1.161 kern_event.c
--- sys/kern/kern_event.c   24 Feb 2021 14:59:52 -  1.161
+++ sys/kern/kern_event.c   27 Feb 2021 12:54:27 -
@@ -135,7 +135,8 @@ int filt_fileattach(struct knote *kn);
 void   filt_timerexpire(void *knx);
 intfilt_timerattach(struct knote *kn);
 void   filt_timerdetach(struct knote *kn);
-intfilt_timer(struct knote *kn, long hint);
+intfilt_timermodify(struct kevent *kev, struct knote *kn);
+intfilt_timerprocess(struct knote *kn, struct kevent *kev);
 void   filt_seltruedetach(struct knote *kn);
 
 const struct filterops kqread_filtops = {
@@ -163,7 +164,9 @@ const struct filterops timer_filtops = {
.f_flags= 0,
.f_attach   = filt_timerattach,
.f_detach   = filt_timerdetach,
-   .f_event= filt_timer,
+   .f_event= NULL,
+   .f_modify   = filt_timermodify,
+   .f_process  = filt_timerprocess,
 };
 
 struct pool knote_pool;
@@ -444,15 +447,48 @@ filt_timerdetach(struct knote *kn)
struct timeout *to;
 
to = (struct timeout *)kn->kn_hook;
-   timeout_del(to);
+   timeout_del_barrier(to);
free(to, M_KEVENT, sizeof(*to));
kq_ntimeouts--;
 }
 
 int
-filt_timer(struct knote *kn, long hint)
+filt_timermodify(struct kevent *kev, struct knote *kn)
+{
+   struct timeout *to = kn->kn_hook;
+   int s;
+
+   /* Reset the timer. Any pending events are discarded. */
+
+   timeout_del_barrier(to);
+
+   s = splhigh();
+   if (kn->kn_status & KN_QUEUED)
+   knote_dequeue(kn);
+   kn->kn_status &= ~KN_ACTIVE;
+   splx(s);
+
+   kn->kn_data = 0;
+   knote_modify(kev, kn);
+   /* Reinit timeout to invoke tick adjustment again. */
+   timeout_set(to, filt_tim

[OpenBSD -current] Change event timer in main loop with kqueue

[martin mag]

Hello everyone!

I've been trying to use kqueue for the last couple of day but I keep
having an issue with EVFILT_TIMER filter. (I'm running Openbsd
-current)

Right now, I'm trying to do the following:
1) Initilialize a timer event @ 200ms, periodically.
2) Inside the main event loop => If this event is retrieved, print
elapsed time since last one
3) After 2 iterations, MODIFY the timer event to 1000ms and continue the loop
4) Code stops after 4 iterations as pb arise after the first timer
change @ iteration 2.

Reading the manpages kqueue(2), one sees that:
** ) An event is uniquely defined by the pair (ident, filter) ==>
in the example below (TIMER1, EVFILT_TIMER)
**)  "" Re-adding an existing event will modify the parameters of
the original event, and not result in a duplicate entry. "" => So
re-adding the event (TIMER1, EVFILT_TIMER) with a modified field
'data' should update the timer from 200ms to 1000ms.

=> Apparently, timer is updated, but not in the way I expected. See
below an example.

Here is the C program. I removed every 'error-checker' intentionally
as this is just a basic test:

#include 
#include 
#include 
#include 
#define TIMER1 202

int main(){
int kq=0, nev=0;
struct kevent evlist, chlist;
struct timespec start, stop, elapsed;

/* Initialize the queue */
kq = kqueue();
/* Register event to the queue */
EV_SET(, TIMER1, EVFILT_TIMER, EV_ADD | EV_ENABLE, 0, 200, 0);
kevent(kq, , 1, NULL, 0, NULL);

for (int i=0; i<4; i++){
clock_gettitme(CLOCK_MONOTONIC, );
nev = kevent(kq, NULL, 0, , 1, NULL);
printf("Iteration %d => nb events=%d\n", i+1, nev);
if (evlist.ident == TIMER1){
clock_gettime(CLOCK_MONOTONIC, );
timespecsub(, , );
printf("Time elapsed since previous iteration: %lld.%09lds\n",
   (long long) elapsed.tv_sec, (long long)
elapsed.tv_nsec);

/* > MODIFY TIMER <== */
if( (i+1)%2 == 0){
printf("Adjusting timer event ...\n");
EV_SET(, TIMER1, EVFILT_TIMER, EV_ADD |
EV_ENABLE, 0, 1000, 0);
/* I also tried this:   chlist.data = 1000;  but same
problem arise*/
/* Register modification within the queue */
kevent(kq, , 1, NULL, 0, NULL);
printf("Next event should happen %dms later", chlist.data);
  } /* End i%4 == 0

 } /* End evlist.ident == TIMER1 */

} /* End for loop */

return EXIT_SUCCESS;
}

*** Compiled with gcc-8.4.0
# egcc -o test_kqueue test_kqueue.c

*** OUTPUT of above program
Iteration 1 => nb events=1
Time elapsed since previous event:0.203417468s
==

Iteration 2 => nb events=1
Time elapsed since previous event:0.199534100s
Adjusting timer event 
Next event in 1000ms<< ===
This is where TIMER is changed

<< ===  and  kqueue is updated
==

Iteration 3 => nb events=1
Time elapsed since previous event:0.199848328<< === Problem here:

   << It should be ~1s not 0.2s (initial timer)
==

Iteration 4 => nb events=1
Time elapsed since previous event:0.999884957s   << === Now it's OK
Adjusting timer event 
Next event in 1000ms
==
*** END OF OUTPUT

So what I expected from my program was that Iteration 3 would be
retrieved 1second after iteration 2. But here, it is retrieved 0.2s
after only. This is AS IF the change wasn't taken into account yet
...? The expected behaviour is seen at iteration 4.

I'm pretty sure I'm not understanding correctly what happens but I
cannot figure out where I'm wrong in my example.

I did another test modifying the event timer (line 31 in program) in loop with:
TEST 1: (Added EV_ONESHOT)
  EV_SET(, TIMER1, EVFILT_TIMER, EV_ADD | EV_ENABLE |
EV_ONESHOT, 0, 1000, 0);   ===>> ONESHOT does not seem to be taken
into account as the event keeps beeing retrieved 1s apart. (the
expected behavior would that that only one event should be triggered
after this modification)

TEST 2 (Disabling event to see if it happens instantly or if it is
"delayed" as in the previous examples)
The ONLY change that work as expected is EV_DISABLE, which stops
events from being retrieved after iteration 2.

Could any one help me figure out what I'm doing wrong and how I can
manage modifying an existing timer event?

Thanks a lot!

PS: This is not a copy/paste program as I'm not sending the message
from the same PC. I hope I didn't do any typos rewritting
everything...

OpenBSD -current not booting on Dell M4800

[jpeg]

Hello,
I've sent some bug reports about this, but maybe that wasn't the best
place to post it. When upgrading to a snapshot with sysupgrade and 
rebooting, the display hangs as openbsd loads wdisplay0, and
xenodm nor X will start. I don't think wdisplay loads at all. This 
happens on amd64 with the multiprocessor kernel, but not with the 
single processor one. I did not notice anything out of the ordinary
during the upgrade. Anyone might be able to help?

Latest bug report with Xorg.log, dmesg, and acpi is here:
https://marc.info/?l=openbsd-bugs=160575016004118=2

Re: Any idea/suggestion for old Cisco router to be use running OpenBSD current for WG?

[Pedro Caetano]

The hardware is good.

After an AC incident, I've had some of those cavium nics melt the cpu
thermal paste, dripping all over the mainboard. (this nics are inserted
into a riser card, facing down the mainboard)

The machine kept running!




A quarta, 24/06/2020, 21:12, Pierre Emeriaud 
escreveu:

> Le mer. 24 juin 2020 à 13:01, Stuart Henderson  a
> écrit :
> >
> > On 2020-06-23, Daniel Ouellet  wrote:
> > > OpenBSD does run on some old Cisco routers, it's been done before. Sure
> > > it's not officially supported nor does it support all the various
> > > interfaces but it's known to work on some.
>
> Not a router per se, but my home gateway is a Cisco ACE 4710 appliance
> running 6.6, with multiple rdomains, tinc vpns, bgp full ipv6 table
> and a couple of nics, and a 4GB cf as harddisk.
>
> > > I am trying to dig up a dmesg showing it too.
>
> https://dmesgd.nycbug.org/index.cgi?do=view=4760
>
> > > Here is an example using the4 old Cisco IDS-4215
> > >
> > >
> https://komlositech.wordpress.com/2018/12/30/revive-a-cisco-ids-into-a-capable-openbsd-firewall/
> > >
> > > I was just curious as to what stage it might be now.
> >
> > That's just someone reusing janky old hardware that is being thrown out,
> > there is no particular effort to support it on the OpenBSD side.
>
> My hardware is really ancient compared to modern servers:
> $ sysctl hw.model
> hw.model=Intel(R) Pentium(R) 4 CPU 3.40GHz
>
> It draws power for sure, much more than an APU or similar, but I like it :)
>
> The install was straightforward, install on the CF from another host
> w/ qemu, plug, boot, done.
>
> > > May be Juniper instead as Juniper is based on FreeBSD anyway and it's
> an
> > > over price PC with specialize network cards. (; Ok more then that, but
> > > you get the picture I think.
> >
> > they're devices with network forwarding ASICs that happen to use a
> > FreeBSD system as the control plane (and are moving to Linux now but
> > I digress).. networking on the control plane is really limited and
> > only meant for management, beyond that you need to interface with
> > the special hardware.
>
> The Cisco ACE4710 had a specialized nic, a cavium (octeon?), running
> linux on a mips cpu, to offload all the heavy lifting. I removed it
> and never tried to use it.
>
> I also tried to install 5.sth on a nokia IP 710 firewall, that didn't
> go that well because of some pci & acpi issues iirc, and overall it
> was less interesting because of the huge form factor, and the
> linecards beeing proprietary.
>
>

Re: Any idea/suggestion for old Cisco router to be use running OpenBSD current for WG?

[Pierre Emeriaud]

Le mer. 24 juin 2020 à 13:01, Stuart Henderson  a écrit :
>
> On 2020-06-23, Daniel Ouellet  wrote:
> > OpenBSD does run on some old Cisco routers, it's been done before. Sure
> > it's not officially supported nor does it support all the various
> > interfaces but it's known to work on some.

Not a router per se, but my home gateway is a Cisco ACE 4710 appliance
running 6.6, with multiple rdomains, tinc vpns, bgp full ipv6 table
and a couple of nics, and a 4GB cf as harddisk.

> > I am trying to dig up a dmesg showing it too.

https://dmesgd.nycbug.org/index.cgi?do=view=4760

> > Here is an example using the4 old Cisco IDS-4215
> >
> > https://komlositech.wordpress.com/2018/12/30/revive-a-cisco-ids-into-a-capable-openbsd-firewall/
> >
> > I was just curious as to what stage it might be now.
>
> That's just someone reusing janky old hardware that is being thrown out,
> there is no particular effort to support it on the OpenBSD side.

My hardware is really ancient compared to modern servers:
$ sysctl hw.model
hw.model=Intel(R) Pentium(R) 4 CPU 3.40GHz

It draws power for sure, much more than an APU or similar, but I like it :)

The install was straightforward, install on the CF from another host
w/ qemu, plug, boot, done.

> > May be Juniper instead as Juniper is based on FreeBSD anyway and it's an
> > over price PC with specialize network cards. (; Ok more then that, but
> > you get the picture I think.
>
> they're devices with network forwarding ASICs that happen to use a
> FreeBSD system as the control plane (and are moving to Linux now but
> I digress).. networking on the control plane is really limited and
> only meant for management, beyond that you need to interface with
> the special hardware.

The Cisco ACE4710 had a specialized nic, a cavium (octeon?), running
linux on a mips cpu, to offload all the heavy lifting. I removed it
and never tried to use it.

I also tried to install 5.sth on a nokia IP 710 firewall, that didn't
go that well because of some pci & acpi issues iirc, and overall it
was less interesting because of the huge form factor, and the
linecards beeing proprietary.

Re: Any idea/suggestion for old Cisco router to be use running OpenBSD current for WG?

[Kaya Saman]

On 6/24/20 11:58 AM, Stuart Henderson wrote:

On 2020-06-23, Daniel Ouellet  wrote:

Have a look through https://www.supermicro.com/en/products/embedded/servers /
https://www.supermicro.com/en/products/embedded/rackmount and you'll find
quite a few things that give the perception "solid custom network device"
rather than either "repurposed server" or "cisco junk, well past it's
sell-by date, <$100 on ebay" - things like these

https://www.supermicro.com/en/products/system/1U/1019/SYS-1019D-FRN8TP.cfm
https://www.supermicro.com/en/products/system/1U/5019/SYS-5019D-4C-FN8TP.cfm

(some equipment from other vendors will fit the bill too, but supermicro is
a lot easier to buy from than portwell etc).



I agree totally here with Stuart! In the past I have built a router 
using a SuperMicro 4U chassis with Xeon E5 cpu.



https://www.supermicro.com/en/products/chassis/4U/842/SC842TQC-668B


Originally OpenBSD didn't support the RAID controller so I used the root 
backup cron dd script. Everything else was fine however, and it's 
performance has been incredible with the only downtime being during 
maintenance periods -> transitioning to new version of 'Current'.


Consequently it is tied to a Cisco router :-)

That is really only to bridge the VDSL2 line to Ethernet - 
https://tools.ietf.org/html/rfc1483



Another option depending on availability could be Jetway -

http://www.jetwayipc.com/product-category/emb-board-en/embedded-x86-en/mini-itx-en/

https://www.jetwaycomputer.com/


Example (yes they do look like vendor based network equipment and not 
rack mount servers): 
https://www.jetwaycomputer.com/1U-Rackmount-Barebones.html



One common place for their availability is the Mini-ITX store: 
https://www.mini-itx.com/store/category?type=motherboard=1=4GB-or-more=from-1=from-1=price=1



I don't have experience with them in general but if OpenBSD works well 
on them they could become a really big game changer.



Regards,


Kaya

Re: Any idea/suggestion for old Cisco router to be use running OpenBSD current for WG?

[Stuart Henderson]

On 2020-06-23, Daniel Ouellet  wrote:
> OpenBSD does run on some old Cisco routers, it's been done before. Sure
> it's not officially supported nor does it support all the various
> interfaces but it's known to work on some.
>
> I am trying to dig up a dmesg showing it too.
>
> Plus Cisco have some firewall type of device that are over price PC that
> can run OpenBSD.
>
> Here is an example using the4 old Cisco IDS-4215
>
> https://komlositech.wordpress.com/2018/12/30/revive-a-cisco-ids-into-a-capable-openbsd-firewall/
>
> I was just curious as to what stage it might be now.

That's just someone reusing janky old hardware that is being thrown out,
there is no particular effort to support it on the OpenBSD side.

> I am not saying it make sense to do really power wise for sure.
>
> May be Juniper instead as Juniper is based on FreeBSD anyway and it's an
> over price PC with specialize network cards. (; Ok more then that, but
> you get the picture I think.

they're devices with network forwarding ASICs that happen to use a
FreeBSD system as the control plane (and are moving to Linux now but
I digress).. networking on the control plane is really limited and
only meant for management, beyond that you need to interface with
the special hardware.

>> On Tue, Jun 23, 2020 at 5:03 PM Daniel Ouellet  wrote:
>>>
>>> I also know there was effort and some Cisco router can run OpenBSD very
>>> well, however I have no clue as to any of this stand now.

Not really "effort" or "very well" ;)

>>> I don't have a problem to use APU type or other Ubiquit for small
>>> OpenBSD router, but I wonder about using Cisco instead. The only reason
>>> is for may be more stability, most likely less performance for sure, but
>>> less change to have corrupted reboot on power lost, etc.

That is nonsense, "corrupted reboot on power lost" isn't down to the
hardware, it's OS/configuration - running OpenBSD on such hardware won't
help unless you make a custom system that avoids live writes to the
storage devices or at least reduce the risk with sync mounts etc
(see recent misc@ thread).

>>> And sadly for some customers having what they see as computer as router
>>> don't make them fell good,

Now that is true ...

>>>but seeing a Cisco box kind of wipe out the
>>> impression.

paint the chassis blue-green and put a sticker on it? ;)

>>> I am not saying it's justify, but perception is sometime
>>> everything, but if I have my say in it I want all my routers to be
>>> OpenBSD as much as I can where the needs is not to multiple Gb in speed.
>>>
>>> So, any suggestion or updates as to what's now available and hopefully
>>> in use now.

Have a look through https://www.supermicro.com/en/products/embedded/servers /
https://www.supermicro.com/en/products/embedded/rackmount and you'll find
quite a few things that give the perception "solid custom network device"
rather than either "repurposed server" or "cisco junk, well past it's
sell-by date, <$100 on ebay" - things like these

https://www.supermicro.com/en/products/system/1U/1019/SYS-1019D-FRN8TP.cfm
https://www.supermicro.com/en/products/system/1U/5019/SYS-5019D-4C-FN8TP.cfm

(some equipment from other vendors will fit the bill too, but supermicro is
a lot easier to buy from than portwell etc).

>>> I just have no clue if wireguard needs to be run, what can be achieve as
>>> the CPU in all Cisco device is always under power, we all know that.

Wireguard performance is pretty good even on relatively weak CPUs but the
20-year-old Celeron in that Cisco thing is ... well ... let's just say it's
going to struggle to forward at 100Mb/s *without* encryption.

Re: Any idea/suggestion for old Cisco router to be use running OpenBSD current for WG?

[Kaya Saman]

Actually you reminded me about the Cisco Voice appliances which are 
basically PC servers. If I recall correctly they ran a Linux kernel too.


Unfortunately I never got to play around with the capabilities of one 
but you might have some luck with something like that. Of course it 
wouldn't be running Call Manager ;-)


- hang on... my memory is slowly coming back (it's been over 10 years 
lol), CCM used to also be available as a VM which could be run on 
VMware. Maybe the dedicated appliance would be a good choice of hardware 
to run OpenBSD on?


The ASA appliances may also be x86 based which could make them a 
candidate but with large price tags for new ones I'm not sure if anyone 
has tried doing anything crazy with them.



A quick google for the Unified Communication System came up with this:

https://www.google.com/search?q=cisco+call+manager+server=ALeKk03xeYq4NLgIyiUGtaNmoUnR3iaXnQ:1592950661912=lnms=isch=X=2ahUKEwi_7OPS-5jqAhUpTxUIHRbnCOkQ_AUoAXoECA0QAw=1918=955#imgrc=yRjG43cRTHU1nM


You might be really lucky with one of those devices! Hopefully someone 
with more experience will chime in and confirm.



Regards,


Kaya


On 2020-06-23 23:03, Daniel Ouellet wrote:

OpenBSD does run on some old Cisco routers, it's been done before. Sure
it's not officially supported nor does it support all the various
interfaces but it's known to work on some.

I am trying to dig up a dmesg showing it too.

Plus Cisco have some firewall type of device that are over price PC that
can run OpenBSD.

Here is an example using the4 old Cisco IDS-4215

https://komlositech.wordpress.com/2018/12/30/revive-a-cisco-ids-into-a-capable-openbsd-firewall/

I was just curious as to what stage it might be now.

I am not saying it make sense to do really power wise for sure.

May be Juniper instead as Juniper is based on FreeBSD anyway and it's an
over price PC with specialize network cards. (; Ok more then that, but
you get the picture I think.

I was just curious as to what it may be running on these days?

Could be Cisco routers, Cisco IDS, Cisco firewall, unless I am mistaken
they also have servers or used too anyway, and why not Juniper gear?

In short any box that appear to be Cisco or Juniper but that have
something different under the hood.

And yes, this is stupid if you look only at what you get compare to
other better choices.

I am not doing it for best performance, but for fell comfortable.

Call it marketing bullshit, because that's exactly what it is! (;

Daniel


On 6/23/20 12:37 PM, Kaya Saman wrote:

Hi, I totally understand the position you're in and sympathize.

I've never heard of Cisco routers being able to run OpenBSD though IOS
is based on BSD as far as I'm aware.

Not a direct solution to your use case but you could always run a
small mini-itx or SBC system behind the Cisco router. You could put it
as a firewall solution and have the OBSD box doing all the major
routing, vlans, firewall (pf) etc... while the Cisco could just simply
forward information between the private and public IP ranges. Or if
using dial-in then you can bridge the OBSD and Cisco then use OBSD as
the PPPoE device

It is one suggestion in any case though it might not be the most ideal.

Regards,

Kaya

On Tue, Jun 23, 2020 at 5:03 PM Daniel Ouellet  wrote:

Hi,

This might be a bit weird question, but I saw the wireguard being put in
the kernel in the last few days and I am very existed abut it oppose to
use the package on it and even today there was more on it.

Many thanks for this!!!

I also know there was effort and some Cisco router can run OpenBSD very
well, however I have no clue as to any of this stand now.

I don't have a problem to use APU type or other Ubiquit for small
OpenBSD router, but I wonder about using Cisco instead. The only reason
is for may be more stability, most likely less performance for sure, but
less change to have corrupted reboot on power lost, etc.

And sadly for some customers having what they see as computer as router
don't make them fell good, but seeing a Cisco box kind of wipe out the
impression. I am not saying it's justify, but perception is sometime
everything, but if I have my say in it I want all my routers to be
OpenBSD as much as I can where the needs is not to multiple Gb in speed.

So, any suggestion or updates as to what's now available and hopefully
in use now.

I really don't care for any special model, or even Juniper, as long as I
can put OpenBSD on it.

So any feedback as to where it's stand now and what's usable in a
reliable way would be greatly appreciated.

And yes I know I may well get better performance in some cases with a
small APU device then a Cisco one, but that's for what we all know may
not be logical to be used, but for sadly how some clients may fell, not
knowing any better.

I guess you can see that as some people do security by obstruction, but
we al know it's not more secure, this is routing by obstruction I guess
and may be less performant, but achieve comfort 

Re: Any idea/suggestion for old Cisco router to be use running OpenBSD current for WG?

[Daniel Ouellet]

OpenBSD does run on some old Cisco routers, it's been done before. Sure
it's not officially supported nor does it support all the various
interfaces but it's known to work on some.

I am trying to dig up a dmesg showing it too.

Plus Cisco have some firewall type of device that are over price PC that
can run OpenBSD.

Here is an example using the4 old Cisco IDS-4215

https://komlositech.wordpress.com/2018/12/30/revive-a-cisco-ids-into-a-capable-openbsd-firewall/

I was just curious as to what stage it might be now.

I am not saying it make sense to do really power wise for sure.

May be Juniper instead as Juniper is based on FreeBSD anyway and it's an
over price PC with specialize network cards. (; Ok more then that, but
you get the picture I think.

I was just curious as to what it may be running on these days?

Could be Cisco routers, Cisco IDS, Cisco firewall, unless I am mistaken
they also have servers or used too anyway, and why not Juniper gear?

In short any box that appear to be Cisco or Juniper but that have
something different under the hood.

And yes, this is stupid if you look only at what you get compare to
other better choices.

I am not doing it for best performance, but for fell comfortable.

Call it marketing bullshit, because that's exactly what it is! (;

Daniel


On 6/23/20 12:37 PM, Kaya Saman wrote:
> Hi, I totally understand the position you're in and sympathize.
> 
> I've never heard of Cisco routers being able to run OpenBSD though IOS
> is based on BSD as far as I'm aware.
> 
> Not a direct solution to your use case but you could always run a
> small mini-itx or SBC system behind the Cisco router. You could put it
> as a firewall solution and have the OBSD box doing all the major
> routing, vlans, firewall (pf) etc... while the Cisco could just simply
> forward information between the private and public IP ranges. Or if
> using dial-in then you can bridge the OBSD and Cisco then use OBSD as
> the PPPoE device
> 
> It is one suggestion in any case though it might not be the most ideal.
> 
> Regards,
> 
> Kaya
> 
> On Tue, Jun 23, 2020 at 5:03 PM Daniel Ouellet  wrote:
>>
>> Hi,
>>
>> This might be a bit weird question, but I saw the wireguard being put in
>> the kernel in the last few days and I am very existed abut it oppose to
>> use the package on it and even today there was more on it.
>>
>> Many thanks for this!!!
>>
>> I also know there was effort and some Cisco router can run OpenBSD very
>> well, however I have no clue as to any of this stand now.
>>
>> I don't have a problem to use APU type or other Ubiquit for small
>> OpenBSD router, but I wonder about using Cisco instead. The only reason
>> is for may be more stability, most likely less performance for sure, but
>> less change to have corrupted reboot on power lost, etc.
>>
>> And sadly for some customers having what they see as computer as router
>> don't make them fell good, but seeing a Cisco box kind of wipe out the
>> impression. I am not saying it's justify, but perception is sometime
>> everything, but if I have my say in it I want all my routers to be
>> OpenBSD as much as I can where the needs is not to multiple Gb in speed.
>>
>> So, any suggestion or updates as to what's now available and hopefully
>> in use now.
>>
>> I really don't care for any special model, or even Juniper, as long as I
>> can put OpenBSD on it.
>>
>> So any feedback as to where it's stand now and what's usable in a
>> reliable way would be greatly appreciated.
>>
>> And yes I know I may well get better performance in some cases with a
>> small APU device then a Cisco one, but that's for what we all know may
>> not be logical to be used, but for sadly how some clients may fell, not
>> knowing any better.
>>
>> I guess you can see that as some people do security by obstruction, but
>> we al know it's not more secure, this is routing by obstruction I guess
>> and may be less performant, but achieve comfort obstruction confidence.
>>
>> I just have no clue if wireguard needs to be run, what can be achieve as
>> the CPU in all Cisco device is always under power, we all know that.
>>
>> This may not go anywhere, however I liked to look even if for nothing
>> else then just being fun to do if that can't even be usable.
>>
>> Many thanks for your time and feedback.
>>
>> Daniel
>>
>> PS; And yes, that's most likely stupid I know. Sometime what's used is
>> not always what make sense for other reason that are stupid.
>>
> 

Re: Any idea/suggestion for old Cisco router to be use running OpenBSD current for WG?

[Daniel Ouellet]

Thanks

I have run Edge router for a very long time, but that doesn't fit the
marketing bullshit needed. (;

I run my first one as far back as 2015.

https://marc.info/?l=openbsd-misc=144747982003992=2

And the new Ubiquiti most likely would have better performance compare
to many old cisco box possibly running OpenBSD.

That's sadly not the goal here.


On 6/23/20 1:40 PM, Jordan Geoghegan wrote:
> I don't know much about Cisco hardware, but I've had great luck with the
> Edgerouter line of products. I've run my home network on an Edgerouter
> Pro for several years now without issue, and have dozens of ER4 and
> ER-Lite devices out in the wild.
> 
> If you're looking for non-x86 routing solutions, then the Edgerouter is
> one of the best bets.
> 
> Regards,
> 
> Jordan
> 
> On 2020-06-23 09:01, Daniel Ouellet wrote:
>> Hi,
>>
>> This might be a bit weird question, but I saw the wireguard being put in
>> the kernel in the last few days and I am very existed abut it oppose to
>> use the package on it and even today there was more on it.
>>
>> Many thanks for this!!!
>>
>> I also know there was effort and some Cisco router can run OpenBSD very
>> well, however I have no clue as to any of this stand now.
>>
>> I don't have a problem to use APU type or other Ubiquit for small
>> OpenBSD router, but I wonder about using Cisco instead. The only reason
>> is for may be more stability, most likely less performance for sure, but
>> less change to have corrupted reboot on power lost, etc.
>>
>> And sadly for some customers having what they see as computer as router
>> don't make them fell good, but seeing a Cisco box kind of wipe out the
>> impression. I am not saying it's justify, but perception is sometime
>> everything, but if I have my say in it I want all my routers to be
>> OpenBSD as much as I can where the needs is not to multiple Gb in speed.
>>
>> So, any suggestion or updates as to what's now available and hopefully
>> in use now.
>>
>> I really don't care for any special model, or even Juniper, as long as I
>> can put OpenBSD on it.
>>
>> So any feedback as to where it's stand now and what's usable in a
>> reliable way would be greatly appreciated.
>>
>> And yes I know I may well get better performance in some cases with a
>> small APU device then a Cisco one, but that's for what we all know may
>> not be logical to be used, but for sadly how some clients may fell, not
>> knowing any better.
>>
>> I guess you can see that as some people do security by obstruction, but
>> we al know it's not more secure, this is routing by obstruction I guess
>> and may be less performant, but achieve comfort obstruction confidence.
>>
>> I just have no clue if wireguard needs to be run, what can be achieve as
>> the CPU in all Cisco device is always under power, we all know that.
>>
>> This may not go anywhere, however I liked to look even if for nothing
>> else then just being fun to do if that can't even be usable.
>>
>> Many thanks for your time and feedback.
>>
>> Daniel
>>
>> PS; And yes, that's most likely stupid I know. Sometime what's used is
>> not always what make sense for other reason that are stupid.
>>
> 

Re: Any idea/suggestion for old Cisco router to be use running OpenBSD current for WG?

[Jordan Geoghegan]

I don't know much about Cisco hardware, but I've had great luck with the 
Edgerouter line of products. I've run my home network on an Edgerouter 
Pro for several years now without issue, and have dozens of ER4 and 
ER-Lite devices out in the wild.


If you're looking for non-x86 routing solutions, then the Edgerouter is 
one of the best bets.


Regards,

Jordan

On 2020-06-23 09:01, Daniel Ouellet wrote:

Hi,

This might be a bit weird question, but I saw the wireguard being put in
the kernel in the last few days and I am very existed abut it oppose to
use the package on it and even today there was more on it.

Many thanks for this!!!

I also know there was effort and some Cisco router can run OpenBSD very
well, however I have no clue as to any of this stand now.

I don't have a problem to use APU type or other Ubiquit for small
OpenBSD router, but I wonder about using Cisco instead. The only reason
is for may be more stability, most likely less performance for sure, but
less change to have corrupted reboot on power lost, etc.

And sadly for some customers having what they see as computer as router
don't make them fell good, but seeing a Cisco box kind of wipe out the
impression. I am not saying it's justify, but perception is sometime
everything, but if I have my say in it I want all my routers to be
OpenBSD as much as I can where the needs is not to multiple Gb in speed.

So, any suggestion or updates as to what's now available and hopefully
in use now.

I really don't care for any special model, or even Juniper, as long as I
can put OpenBSD on it.

So any feedback as to where it's stand now and what's usable in a
reliable way would be greatly appreciated.

And yes I know I may well get better performance in some cases with a
small APU device then a Cisco one, but that's for what we all know may
not be logical to be used, but for sadly how some clients may fell, not
knowing any better.

I guess you can see that as some people do security by obstruction, but
we al know it's not more secure, this is routing by obstruction I guess
and may be less performant, but achieve comfort obstruction confidence.

I just have no clue if wireguard needs to be run, what can be achieve as
the CPU in all Cisco device is always under power, we all know that.

This may not go anywhere, however I liked to look even if for nothing
else then just being fun to do if that can't even be usable.

Many thanks for your time and feedback.

Daniel

PS; And yes, that's most likely stupid I know. Sometime what's used is
not always what make sense for other reason that are stupid.

Re: Any idea/suggestion for old Cisco router to be use running OpenBSD current for WG?

[Kaya Saman]

Hi, I totally understand the position you're in and sympathize.

I've never heard of Cisco routers being able to run OpenBSD though IOS
is based on BSD as far as I'm aware.

Not a direct solution to your use case but you could always run a
small mini-itx or SBC system behind the Cisco router. You could put it
as a firewall solution and have the OBSD box doing all the major
routing, vlans, firewall (pf) etc... while the Cisco could just simply
forward information between the private and public IP ranges. Or if
using dial-in then you can bridge the OBSD and Cisco then use OBSD as
the PPPoE device

It is one suggestion in any case though it might not be the most ideal.

Regards,

Kaya

On Tue, Jun 23, 2020 at 5:03 PM Daniel Ouellet  wrote:
>
> Hi,
>
> This might be a bit weird question, but I saw the wireguard being put in
> the kernel in the last few days and I am very existed abut it oppose to
> use the package on it and even today there was more on it.
>
> Many thanks for this!!!
>
> I also know there was effort and some Cisco router can run OpenBSD very
> well, however I have no clue as to any of this stand now.
>
> I don't have a problem to use APU type or other Ubiquit for small
> OpenBSD router, but I wonder about using Cisco instead. The only reason
> is for may be more stability, most likely less performance for sure, but
> less change to have corrupted reboot on power lost, etc.
>
> And sadly for some customers having what they see as computer as router
> don't make them fell good, but seeing a Cisco box kind of wipe out the
> impression. I am not saying it's justify, but perception is sometime
> everything, but if I have my say in it I want all my routers to be
> OpenBSD as much as I can where the needs is not to multiple Gb in speed.
>
> So, any suggestion or updates as to what's now available and hopefully
> in use now.
>
> I really don't care for any special model, or even Juniper, as long as I
> can put OpenBSD on it.
>
> So any feedback as to where it's stand now and what's usable in a
> reliable way would be greatly appreciated.
>
> And yes I know I may well get better performance in some cases with a
> small APU device then a Cisco one, but that's for what we all know may
> not be logical to be used, but for sadly how some clients may fell, not
> knowing any better.
>
> I guess you can see that as some people do security by obstruction, but
> we al know it's not more secure, this is routing by obstruction I guess
> and may be less performant, but achieve comfort obstruction confidence.
>
> I just have no clue if wireguard needs to be run, what can be achieve as
> the CPU in all Cisco device is always under power, we all know that.
>
> This may not go anywhere, however I liked to look even if for nothing
> else then just being fun to do if that can't even be usable.
>
> Many thanks for your time and feedback.
>
> Daniel
>
> PS; And yes, that's most likely stupid I know. Sometime what's used is
> not always what make sense for other reason that are stupid.
>

Any idea/suggestion for old Cisco router to be use running OpenBSD current for WG?

[Daniel Ouellet]

Hi,

This might be a bit weird question, but I saw the wireguard being put in
the kernel in the last few days and I am very existed abut it oppose to
use the package on it and even today there was more on it.

Many thanks for this!!!

I also know there was effort and some Cisco router can run OpenBSD very
well, however I have no clue as to any of this stand now.

I don't have a problem to use APU type or other Ubiquit for small
OpenBSD router, but I wonder about using Cisco instead. The only reason
is for may be more stability, most likely less performance for sure, but
less change to have corrupted reboot on power lost, etc.

And sadly for some customers having what they see as computer as router
don't make them fell good, but seeing a Cisco box kind of wipe out the
impression. I am not saying it's justify, but perception is sometime
everything, but if I have my say in it I want all my routers to be
OpenBSD as much as I can where the needs is not to multiple Gb in speed.

So, any suggestion or updates as to what's now available and hopefully
in use now.

I really don't care for any special model, or even Juniper, as long as I
can put OpenBSD on it.

So any feedback as to where it's stand now and what's usable in a
reliable way would be greatly appreciated.

And yes I know I may well get better performance in some cases with a
small APU device then a Cisco one, but that's for what we all know may
not be logical to be used, but for sadly how some clients may fell, not
knowing any better.

I guess you can see that as some people do security by obstruction, but
we al know it's not more secure, this is routing by obstruction I guess
and may be less performant, but achieve comfort obstruction confidence.

I just have no clue if wireguard needs to be run, what can be achieve as
the CPU in all Cisco device is always under power, we all know that.

This may not go anywhere, however I liked to look even if for nothing
else then just being fun to do if that can't even be usable.

Many thanks for your time and feedback.

Daniel

PS; And yes, that's most likely stupid I know. Sometime what's used is
not always what make sense for other reason that are stupid.

Re: Installing OpenBSD -current snapshots

[Clay Daniels]

On Fri, 29 Nov 2019, Clay Daniels wrote:


Date: Fri, 29 Nov 2019 12:55:43 -0600
From: Clay Daniels 
To: "misc@openbsd.org" 
Subject: Re: Installing OpenBSD -current snapshots

Thanks to everyone who responded. If I knew all the answers I would not
have asked. And I should have read deeper into the documentation before
asking, and am in the process of doing so now.

What I decided was to stick with the release install66.fs boot image. It
works to completely install everything without floundering around to find
the file sets. I really have no need to run current OpenBSD. Maybe after a
few months of study I will think about it again.

Also I'm going to unsubscribe with this email account, and re-subscribe
with my account with sdf.org where I will not be stuck with google's
"top-posting". I don't like it either, same as everyone else.


Ok, this is my real unix email, run on netbsd. I use it via ssh in 
good old alpine. No more top-posting for me!

Re: Installing OpenBSD -current snapshots

[Clay Daniels]

Thanks to everyone who responded. If I knew all the answers I would not
have asked. And I should have read deeper into the documentation before
asking, and am in the process of doing so now.

What I decided was to stick with the release install66.fs boot image. It
works to completely install everything without floundering around to find
the file sets. I really have no need to run current OpenBSD. Maybe after a
few months of study I will think about it again.

Also I'm going to unsubscribe with this email account, and re-subscribe
with my account with sdf.org where I will not be stuck with google's
"top-posting". I don't like it either, same as everyone else.

Clay

Re: Installing OpenBSD -current snapshots

[Nick Holland]

On 2019-11-29 02:26, Clay Daniels wrote:
> Nick, thanks for straightening me out about what is actually going on here
> with the install. I see that there is now a fresh snapshot with today's
> date, not the one I downloaded and ran yesterday. This might tend to keep
> one busy. I'm not sure I would not be better off doing what Bruno & Marc
> suggested and run sysupgrade. Thanks to them for the advice.

sysupgrade does upgrades of existing systems.  Very slick.  However, it
isn't for fresh installs, and if you have convenient console access, it's
not the preferred way of doing it.  And based on the questions here,
NO WAY.  You need to understand what's going on before you start doing
unattended upgrades.

It also (by default) assumes network upgrades, and if you are wanting
everything on local media, there are existing better solutions.

And yes, following current is a never-ending quest.  However, problems
are relatively rare and usually not a big deal, and generally fixed on
the next snapshot.
 
> If I do decide to put the filesets on the the install thumbdrive, I see a
> total of 26 files in the directory. Obviously some are not necessary like
> the floppy or both the .fs & .iso (just one needed), nor the test
> instructions, etc.
> So which files do I REALLY need on my usb thumbdrive to get a complete
> install, x included?


STOP STOP STOP STOP.
You need to re-read what I wrote and the install part of the FAQ some
more times.
The install66.fs file is an image with the *entire install set included*.
You do not want to add things.  You COULD do some voodoo to add stuff to
the miniroot66.fs, but PLEASE DON'T...you would just be re-inventing the
install66.fs, poorly and with more difficulty.

> 
> Please excuse the "top-posting". That's the only way my darn google mail
> does reply's. Kind of irritating, to me and the reader too.
 
Bottom posting was invented for those who can't write in complete thoughts
with context.  You know, like most of the computer world. :-/

Nick.




> Clay
> 
> 
> 
> 
> On Thu, Nov 28, 2019 at 12:34 PM Nick Holland 
> wrote:
> 
>> On 2019-11-27 21:29, Edgar Pettijohn wrote:
>> > On Wed, Nov 27, 2019 at 08:05:30PM -0600, Clay Daniels wrote:
>> >> I have successfully installed OpenBSD 6.6 release and would like to give
>> >> the Current Snapshots a try. I went to a mirror, and to:
>> >>
>> >> Index of /pub/OpenBSD/snapshots/amd64/
>> >>
>> >> I saw install66.fs (probably for usb memstick) and install66.iso (surely
>> >> for a cd/dvd) at ~450Mb. I picked the install66.fs, wrote it to a usb
>> >> thumbdrive, and it starts the install. When i get into the install it
>> asks
>> >> where are the file sets? Humm, maybe it gets these online and it tries
>> to
>> >> do this but no luck. It was late last night, and I checked to see if it
>> had
>> >> written anything to my disk, which it had not, and went to bed. This
>> >> evening I'm looking a bit deeper at the snapshot directory and I
>> suspect I
>> >> need to provide the install with base66.tzg at ~239Mb.
>>
>> NO!
>>
>> [snip misleading stuff]
>> > I noticed this also, but hadn't had time to figure out if I had messed
>> up or
>> > the installer had. As a general rule I assume its me that messed up. Its
>> odd
>> > if you mount the install66.fs you can see the pub/amd64 directory, but
>> during
>> > installation it can't seem to find the directory regardless of what I
>> have
>> > tried.
>> >
>> > Edgar
>>
>> First of all...nothing at all to do about snapshots -- the OpenBSD
>> installation process has remained amazingly stable over the last 20
>> years.
>> New options here and there, but overall, very similar.  Unless something
>> changed in the last few days, installing a snapshot is identical to
>> installing 6.6.
>>
>> The installXX.iso and installXX.fs are complete, stand-alone installation
>> kits.  Everything you need is on them.  You can boot from them, and all
>> the installation files are right there.  Look Ma!  No network needed!
>> ...well...unfortunately there is the issue of firmware files, which are
>> legally not feasible to put on the install media, so you will need network
>> for most machines eventually.  But let's ignore that for now. :)
>>
>> Once the system has booted on the install kernel, you have three devices
>> you are working with:
>> 1) the install kernel's internal "RAM disk" that is part of bsd.rd which
>>   you booted from,
>> 2) your target disk
>> 3) the USB drive with the install files on it.
>>
>> The reason you can't see the install files on the USB stick from the
>> install kernel is they aren't mounted.  You didn't boot from the entire
>> USB stick, you booted from ONE TINY LITTLE bsd.rd file, that just happened
>> to be sitting on the big USB stick...but as far as bsd.rd is concerned,
>> the USB stick isn't part of the booted environment (yet).
>>
>> You aren't booting from a "Live Media".  You are booting from a tiny kernel
>> with a built in file system that's sitting on the same inert file 

Re: Installing OpenBSD -current snapshots

[Mihai Popescu]

> BTW, why do you want to run -current?
> There are only 2 real reasons to do that
> [ ... ]

Total nonsense ...

Re: Installing OpenBSD -current snapshots

[Eric Furman]

On Fri, Nov 29, 2019, at 2:26 AM, Clay Daniels wrote:
> Nick, thanks for straightening me out about what is actually going on here
> with the install. I see that there is now a fresh snapshot with today's
> date, not the one I downloaded and ran yesterday. This might tend to keep
> one busy. I'm not sure I would not be better off doing what Bruno & Marc
> suggested and run sysupgrade. Thanks to them for the advice.

BTW, why do you want to run -current?
There are only 2 real reasons to do that
1: You HAVE to (for various reasons)
2: You want to help with development and test things. This is a great reason, 
but
you better be prepared for a lot of work. Know what you are doing and file bug 
reports.
Else you won't be a whole lot of actual help.

If these don't apply then you might be better off just running Release.
Not trying to be an A hole here. Just giving you heads up of what is expected of
you if you run -current.
Good luck

Re: Installing OpenBSD -current snapshots

[Bodie]

On 29.11.2019 08:45, Clay Daniels wrote:

Another question. I know I need to write the boot file to the usb drive
thus:
# dd if=install66.fs of=/dev/da0 bs=1M conv=sync
But can I just use plain old "cp base66.tgz /mnt" etc for the other 
files?




Sounds like you are rushing too quickly and too much being used to
wrong approach learned on Linux.

How about to start here first:

https://www.openbsd.org/faq/faq4.html

then:

https://www.openbsd.org/faq/faq1.html#ManPages
https://www.openbsd.org/faq/faq10.html

followed by anything more you will need.

Trust me, you will be surprised how many questions will not need to be
asked at all in future ;-)

On Fri, Nov 29, 2019 at 1:26 AM Clay Daniels 


wrote:

Nick, thanks for straightening me out about what is actually going on 
here
with the install. I see that there is now a fresh snapshot with 
today's
date, not the one I downloaded and ran yesterday. This might tend to 
keep
one busy. I'm not sure I would not be better off doing what Bruno & 
Marc

suggested and run sysupgrade. Thanks to them for the advice.

If I do decide to put the filesets on the the install thumbdrive, I 
see a
total of 26 files in the directory. Obviously some are not necessary 
like

the floppy or both the .fs & .iso (just one needed), nor the test
instructions, etc.
So which files do I REALLY need on my usb thumbdrive to get a complete
install, x included?

Please excuse the "top-posting". That's the only way my darn google 
mail

does reply's. Kind of irritating, to me and the reader too.

Clay




On Thu, Nov 28, 2019 at 12:34 PM Nick Holland 


wrote:


On 2019-11-27 21:29, Edgar Pettijohn wrote:
> On Wed, Nov 27, 2019 at 08:05:30PM -0600, Clay Daniels wrote:
>> I have successfully installed OpenBSD 6.6 release and would like to
give
>> the Current Snapshots a try. I went to a mirror, and to:
>>
>> Index of /pub/OpenBSD/snapshots/amd64/
>>
>> I saw install66.fs (probably for usb memstick) and install66.iso
(surely
>> for a cd/dvd) at ~450Mb. I picked the install66.fs, wrote it to a usb
>> thumbdrive, and it starts the install. When i get into the install it
asks
>> where are the file sets? Humm, maybe it gets these online and it tries
to
>> do this but no luck. It was late last night, and I checked to see if
it had
>> written anything to my disk, which it had not, and went to bed. This
>> evening I'm looking a bit deeper at the snapshot directory and I
suspect I
>> need to provide the install with base66.tzg at ~239Mb.

NO!

[snip misleading stuff]
> I noticed this also, but hadn't had time to figure out if I had messed
up or
> the installer had. As a general rule I assume its me that messed up.
Its odd
> if you mount the install66.fs you can see the pub/amd64 directory, but
during
> installation it can't seem to find the directory regardless of what I
have
> tried.
>
> Edgar

First of all...nothing at all to do about snapshots -- the OpenBSD
installation process has remained amazingly stable over the last 20
years.
New options here and there, but overall, very similar.  Unless 
something

changed in the last few days, installing a snapshot is identical to
installing 6.6.

The installXX.iso and installXX.fs are complete, stand-alone 
installation
kits.  Everything you need is on them.  You can boot from them, and 
all

the installation files are right there.  Look Ma!  No network needed!
...well...unfortunately there is the issue of firmware files, which 
are
legally not feasible to put on the install media, so you will need 
network

for most machines eventually.  But let's ignore that for now. :)

Once the system has booted on the install kernel, you have three 
devices

you are working with:
1) the install kernel's internal "RAM disk" that is part of bsd.rd 
which

  you booted from,
2) your target disk
3) the USB drive with the install files on it.

The reason you can't see the install files on the USB stick from the
install kernel is they aren't mounted.  You didn't boot from the 
entire
USB stick, you booted from ONE TINY LITTLE bsd.rd file, that just 
happened
to be sitting on the big USB stick...but as far as bsd.rd is 
concerned,

the USB stick isn't part of the booted environment (yet).

You aren't booting from a "Live Media".  You are booting from a tiny
kernel
with a built in file system that's sitting on the same inert file 
system

as
the install files.

Read that over and over until you understand what I'm saying, not 
what you
are assuming is going on.  It's really important to understand.  It's 
very
different from many Linux installation processes -- you are running 
off a
file only 10MB in size which is now completely in RAM.  That file 
JUST

HAPPENED to come from a USB stick that's much bigger.

So, when it comes to answering where your install files are, they are 
on
a disk, but it's NOT a mounted disk.  It's on your USB drive that's 
not
mounted now, and won't be after installation, but could be useful 
shortly.


Your next problem is...WHICH 

Re: Installing OpenBSD -current snapshots

[Peter N. M. Hansteen]

On Fri, Nov 29, 2019 at 01:45:37AM -0600, Clay Daniels wrote:
> Another question. I know I need to write the boot file to the usb drive
> thus:
> # dd if=install66.fs of=/dev/da0 bs=1M conv=sync
> But can I just use plain old "cp base66.tgz /mnt" etc for the other files?

the installnn.fs image will have the file sets in there already. No need to 
copy.

- Peter

-- 
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.

Re: Installing OpenBSD -current snapshots

[Clay Daniels]

Another question. I know I need to write the boot file to the usb drive
thus:
# dd if=install66.fs of=/dev/da0 bs=1M conv=sync
But can I just use plain old "cp base66.tgz /mnt" etc for the other files?

On Fri, Nov 29, 2019 at 1:26 AM Clay Daniels 
wrote:

> Nick, thanks for straightening me out about what is actually going on here
> with the install. I see that there is now a fresh snapshot with today's
> date, not the one I downloaded and ran yesterday. This might tend to keep
> one busy. I'm not sure I would not be better off doing what Bruno & Marc
> suggested and run sysupgrade. Thanks to them for the advice.
>
> If I do decide to put the filesets on the the install thumbdrive, I see a
> total of 26 files in the directory. Obviously some are not necessary like
> the floppy or both the .fs & .iso (just one needed), nor the test
> instructions, etc.
> So which files do I REALLY need on my usb thumbdrive to get a complete
> install, x included?
>
> Please excuse the "top-posting". That's the only way my darn google mail
> does reply's. Kind of irritating, to me and the reader too.
>
> Clay
>
>
>
>
> On Thu, Nov 28, 2019 at 12:34 PM Nick Holland 
> wrote:
>
>> On 2019-11-27 21:29, Edgar Pettijohn wrote:
>> > On Wed, Nov 27, 2019 at 08:05:30PM -0600, Clay Daniels wrote:
>> >> I have successfully installed OpenBSD 6.6 release and would like to
>> give
>> >> the Current Snapshots a try. I went to a mirror, and to:
>> >>
>> >> Index of /pub/OpenBSD/snapshots/amd64/
>> >>
>> >> I saw install66.fs (probably for usb memstick) and install66.iso
>> (surely
>> >> for a cd/dvd) at ~450Mb. I picked the install66.fs, wrote it to a usb
>> >> thumbdrive, and it starts the install. When i get into the install it
>> asks
>> >> where are the file sets? Humm, maybe it gets these online and it tries
>> to
>> >> do this but no luck. It was late last night, and I checked to see if
>> it had
>> >> written anything to my disk, which it had not, and went to bed. This
>> >> evening I'm looking a bit deeper at the snapshot directory and I
>> suspect I
>> >> need to provide the install with base66.tzg at ~239Mb.
>>
>> NO!
>>
>> [snip misleading stuff]
>> > I noticed this also, but hadn't had time to figure out if I had messed
>> up or
>> > the installer had. As a general rule I assume its me that messed up.
>> Its odd
>> > if you mount the install66.fs you can see the pub/amd64 directory, but
>> during
>> > installation it can't seem to find the directory regardless of what I
>> have
>> > tried.
>> >
>> > Edgar
>>
>> First of all...nothing at all to do about snapshots -- the OpenBSD
>> installation process has remained amazingly stable over the last 20
>> years.
>> New options here and there, but overall, very similar.  Unless something
>> changed in the last few days, installing a snapshot is identical to
>> installing 6.6.
>>
>> The installXX.iso and installXX.fs are complete, stand-alone installation
>> kits.  Everything you need is on them.  You can boot from them, and all
>> the installation files are right there.  Look Ma!  No network needed!
>> ...well...unfortunately there is the issue of firmware files, which are
>> legally not feasible to put on the install media, so you will need network
>> for most machines eventually.  But let's ignore that for now. :)
>>
>> Once the system has booted on the install kernel, you have three devices
>> you are working with:
>> 1) the install kernel's internal "RAM disk" that is part of bsd.rd which
>>   you booted from,
>> 2) your target disk
>> 3) the USB drive with the install files on it.
>>
>> The reason you can't see the install files on the USB stick from the
>> install kernel is they aren't mounted.  You didn't boot from the entire
>> USB stick, you booted from ONE TINY LITTLE bsd.rd file, that just happened
>> to be sitting on the big USB stick...but as far as bsd.rd is concerned,
>> the USB stick isn't part of the booted environment (yet).
>>
>> You aren't booting from a "Live Media".  You are booting from a tiny
>> kernel
>> with a built in file system that's sitting on the same inert file system
>> as
>> the install files.
>>
>> Read that over and over until you understand what I'm saying, not what you
>> are assuming is going on.  It's really important to understand.  It's very
>> different from many Linux installation processes -- you are running off a
>> file only 10MB in size which is now completely in RAM.  That file JUST
>> HAPPENED to come from a USB stick that's much bigger.
>>
>> So, when it comes to answering where your install files are, they are on
>> a disk, but it's NOT a mounted disk.  It's on your USB drive that's not
>> mounted now, and won't be after installation, but could be useful shortly.
>>
>> Your next problem is...WHICH disk?  On a minimal system, it would be the
>> next sd device after your install disk -- assuming you are installing to
>> sd0, your USB stick might be sd1.  HOWEVER, if you have a flash media
>> reader
>> on your system, who knows where 

Re: Installing OpenBSD -current snapshots

[Clay Daniels]

Nick, thanks for straightening me out about what is actually going on here
with the install. I see that there is now a fresh snapshot with today's
date, not the one I downloaded and ran yesterday. This might tend to keep
one busy. I'm not sure I would not be better off doing what Bruno & Marc
suggested and run sysupgrade. Thanks to them for the advice.

If I do decide to put the filesets on the the install thumbdrive, I see a
total of 26 files in the directory. Obviously some are not necessary like
the floppy or both the .fs & .iso (just one needed), nor the test
instructions, etc.
So which files do I REALLY need on my usb thumbdrive to get a complete
install, x included?

Please excuse the "top-posting". That's the only way my darn google mail
does reply's. Kind of irritating, to me and the reader too.

Clay




On Thu, Nov 28, 2019 at 12:34 PM Nick Holland 
wrote:

> On 2019-11-27 21:29, Edgar Pettijohn wrote:
> > On Wed, Nov 27, 2019 at 08:05:30PM -0600, Clay Daniels wrote:
> >> I have successfully installed OpenBSD 6.6 release and would like to give
> >> the Current Snapshots a try. I went to a mirror, and to:
> >>
> >> Index of /pub/OpenBSD/snapshots/amd64/
> >>
> >> I saw install66.fs (probably for usb memstick) and install66.iso (surely
> >> for a cd/dvd) at ~450Mb. I picked the install66.fs, wrote it to a usb
> >> thumbdrive, and it starts the install. When i get into the install it
> asks
> >> where are the file sets? Humm, maybe it gets these online and it tries
> to
> >> do this but no luck. It was late last night, and I checked to see if it
> had
> >> written anything to my disk, which it had not, and went to bed. This
> >> evening I'm looking a bit deeper at the snapshot directory and I
> suspect I
> >> need to provide the install with base66.tzg at ~239Mb.
>
> NO!
>
> [snip misleading stuff]
> > I noticed this also, but hadn't had time to figure out if I had messed
> up or
> > the installer had. As a general rule I assume its me that messed up. Its
> odd
> > if you mount the install66.fs you can see the pub/amd64 directory, but
> during
> > installation it can't seem to find the directory regardless of what I
> have
> > tried.
> >
> > Edgar
>
> First of all...nothing at all to do about snapshots -- the OpenBSD
> installation process has remained amazingly stable over the last 20
> years.
> New options here and there, but overall, very similar.  Unless something
> changed in the last few days, installing a snapshot is identical to
> installing 6.6.
>
> The installXX.iso and installXX.fs are complete, stand-alone installation
> kits.  Everything you need is on them.  You can boot from them, and all
> the installation files are right there.  Look Ma!  No network needed!
> ...well...unfortunately there is the issue of firmware files, which are
> legally not feasible to put on the install media, so you will need network
> for most machines eventually.  But let's ignore that for now. :)
>
> Once the system has booted on the install kernel, you have three devices
> you are working with:
> 1) the install kernel's internal "RAM disk" that is part of bsd.rd which
>   you booted from,
> 2) your target disk
> 3) the USB drive with the install files on it.
>
> The reason you can't see the install files on the USB stick from the
> install kernel is they aren't mounted.  You didn't boot from the entire
> USB stick, you booted from ONE TINY LITTLE bsd.rd file, that just happened
> to be sitting on the big USB stick...but as far as bsd.rd is concerned,
> the USB stick isn't part of the booted environment (yet).
>
> You aren't booting from a "Live Media".  You are booting from a tiny kernel
> with a built in file system that's sitting on the same inert file system as
> the install files.
>
> Read that over and over until you understand what I'm saying, not what you
> are assuming is going on.  It's really important to understand.  It's very
> different from many Linux installation processes -- you are running off a
> file only 10MB in size which is now completely in RAM.  That file JUST
> HAPPENED to come from a USB stick that's much bigger.
>
> So, when it comes to answering where your install files are, they are on
> a disk, but it's NOT a mounted disk.  It's on your USB drive that's not
> mounted now, and won't be after installation, but could be useful shortly.
>
> Your next problem is...WHICH disk?  On a minimal system, it would be the
> next sd device after your install disk -- assuming you are installing to
> sd0, your USB stick might be sd1.  HOWEVER, if you have a flash media
> reader
> on your system, who knows where it is.  One trick would be to unplug your
> USB drive and plug it back in and look at the white-on-blue console message
> that come up at you.  Yes, you are unpluging your boot device, sounds bad,
> but read what I wrote earlier, it's no longer using that -- the boot has
> completed, and it's running from RAM now, it's completely ignoring that
> USB drive.  So let's say you do this and 

Re: Installing OpenBSD -current snapshots

[Nick Holland]

On 2019-11-27 21:29, Edgar Pettijohn wrote:
> On Wed, Nov 27, 2019 at 08:05:30PM -0600, Clay Daniels wrote:
>> I have successfully installed OpenBSD 6.6 release and would like to give
>> the Current Snapshots a try. I went to a mirror, and to:
>> 
>> Index of /pub/OpenBSD/snapshots/amd64/
>> 
>> I saw install66.fs (probably for usb memstick) and install66.iso (surely
>> for a cd/dvd) at ~450Mb. I picked the install66.fs, wrote it to a usb
>> thumbdrive, and it starts the install. When i get into the install it asks
>> where are the file sets? Humm, maybe it gets these online and it tries to
>> do this but no luck. It was late last night, and I checked to see if it had
>> written anything to my disk, which it had not, and went to bed. This
>> evening I'm looking a bit deeper at the snapshot directory and I suspect I
>> need to provide the install with base66.tzg at ~239Mb.

NO!

[snip misleading stuff]
> I noticed this also, but hadn't had time to figure out if I had messed up or
> the installer had. As a general rule I assume its me that messed up. Its odd
> if you mount the install66.fs you can see the pub/amd64 directory, but during
> installation it can't seem to find the directory regardless of what I have 
> tried.
> 
> Edgar

First of all...nothing at all to do about snapshots -- the OpenBSD
installation process has remained amazingly stable over the last 20 years.  
New options here and there, but overall, very similar.  Unless something
changed in the last few days, installing a snapshot is identical to
installing 6.6.

The installXX.iso and installXX.fs are complete, stand-alone installation
kits.  Everything you need is on them.  You can boot from them, and all
the installation files are right there.  Look Ma!  No network needed!
...well...unfortunately there is the issue of firmware files, which are
legally not feasible to put on the install media, so you will need network
for most machines eventually.  But let's ignore that for now. :)

Once the system has booted on the install kernel, you have three devices
you are working with:
1) the install kernel's internal "RAM disk" that is part of bsd.rd which
  you booted from,
2) your target disk 
3) the USB drive with the install files on it.

The reason you can't see the install files on the USB stick from the
install kernel is they aren't mounted.  You didn't boot from the entire
USB stick, you booted from ONE TINY LITTLE bsd.rd file, that just happened
to be sitting on the big USB stick...but as far as bsd.rd is concerned,
the USB stick isn't part of the booted environment (yet).

You aren't booting from a "Live Media".  You are booting from a tiny kernel
with a built in file system that's sitting on the same inert file system as
the install files.

Read that over and over until you understand what I'm saying, not what you
are assuming is going on.  It's really important to understand.  It's very
different from many Linux installation processes -- you are running off a
file only 10MB in size which is now completely in RAM.  That file JUST
HAPPENED to come from a USB stick that's much bigger.

So, when it comes to answering where your install files are, they are on
a disk, but it's NOT a mounted disk.  It's on your USB drive that's not
mounted now, and won't be after installation, but could be useful shortly.

Your next problem is...WHICH disk?  On a minimal system, it would be the
next sd device after your install disk -- assuming you are installing to
sd0, your USB stick might be sd1.  HOWEVER, if you have a flash media reader
on your system, who knows where it is.  One trick would be to unplug your
USB drive and plug it back in and look at the white-on-blue console message
that come up at you.  Yes, you are unpluging your boot device, sounds bad,
but read what I wrote earlier, it's no longer using that -- the boot has
completed, and it's running from RAM now, it's completely ignoring that
USB drive.  So let's say you do this and you see it's sd4.  Tell the
installer the files are coming from a file system not currently mounted
and when it asks, tell it "sd4"

Nick.

Re: Installing OpenBSD -current snapshots

[Marc Espie]

On Wed, Nov 27, 2019 at 08:05:30PM -0600, Clay Daniels wrote:
> I have successfully installed OpenBSD 6.6 release and would like to give
> the Current Snapshots a try. I went to a mirror, and to:

Just run sysupgrade -s

Done.

Re: Installing OpenBSD -current snapshots

[Edgar Pettijohn]

On Nov 28, 2019 2:15 AM, Bruno Flueckiger  wrote:
>
> On 27.11., Clay Daniels wrote:
> > I have successfully installed OpenBSD 6.6 release and would like to give
> > the Current Snapshots a try. I went to a mirror, and to:
> >
> > Index of /pub/OpenBSD/snapshots/amd64/
> >
> > I saw install66.fs (probably for usb memstick) and install66.iso (surely
> > for a cd/dvd) at ~450Mb. I picked the install66.fs, wrote it to a usb
> > thumbdrive, and it starts the install. When i get into the install it asks
> > where are the file sets? Humm, maybe it gets these online and it tries to
> > do this but no luck. It was late last night, and I checked to see if it had
> > written anything to my disk, which it had not, and went to bed. This
> > evening I'm looking a bit deeper at the snapshot directory and I suspect I
> > need to provide the install with base66.tzg at ~239Mb.
> >
> > My question now is after downloading the base, do I need to un-tar it, and
> > how to I provide it to the install? I wrote the install66.fs to the usb
> > with the dd command. Not clear to me how to either manually copy the base
> > file set to the usb, or maybe leave it on an accessible directory on my
> > machine. Any help would be appreciated.
> >
> > Clay Daniels
>
> I would recommend using sysupgrade(8) with the parameter -s to you.
>
> Cheers,
> Bruno
>

It's a fresh install unfortunately.

Re: Installing OpenBSD -current snapshots

[Bruno Flueckiger]

On 27.11., Clay Daniels wrote:
> I have successfully installed OpenBSD 6.6 release and would like to give
> the Current Snapshots a try. I went to a mirror, and to:
>
> Index of /pub/OpenBSD/snapshots/amd64/
>
> I saw install66.fs (probably for usb memstick) and install66.iso (surely
> for a cd/dvd) at ~450Mb. I picked the install66.fs, wrote it to a usb
> thumbdrive, and it starts the install. When i get into the install it asks
> where are the file sets? Humm, maybe it gets these online and it tries to
> do this but no luck. It was late last night, and I checked to see if it had
> written anything to my disk, which it had not, and went to bed. This
> evening I'm looking a bit deeper at the snapshot directory and I suspect I
> need to provide the install with base66.tzg at ~239Mb.
>
> My question now is after downloading the base, do I need to un-tar it, and
> how to I provide it to the install? I wrote the install66.fs to the usb
> with the dd command. Not clear to me how to either manually copy the base
> file set to the usb, or maybe leave it on an accessible directory on my
> machine. Any help would be appreciated.
>
> Clay Daniels

I would recommend using sysupgrade(8) with the parameter -s to you.

Cheers,
Bruno

Re: Installing OpenBSD -current snapshots

[Robert Klein]

On Wed, 27 Nov 2019 20:29:27 -0600
Edgar Pettijohn  wrote:

> On Wed, Nov 27, 2019 at 08:05:30PM -0600, Clay Daniels wrote:
> > I have successfully installed OpenBSD 6.6 release and would like to
> > give the Current Snapshots a try. I went to a mirror, and to:
> > 
> > Index of /pub/OpenBSD/snapshots/amd64/
> > 
> > I saw install66.fs (probably for usb memstick) and install66.iso
> > (surely for a cd/dvd) at ~450Mb. I picked the install66.fs, wrote
> > it to a usb thumbdrive, and it starts the install. When i get into
> > the install it asks where are the file sets? Humm, maybe it gets
> > these online and it tries to do this but no luck. It was late last
> > night, and I checked to see if it had written anything to my disk,
> > which it had not, and went to bed. This evening I'm looking a bit
> > deeper at the snapshot directory and I suspect I need to provide
> > the install with base66.tzg at ~239Mb.
> > 
> > My question now is after downloading the base, do I need to un-tar
> > it, and how to I provide it to the install? I wrote the
> > install66.fs to the usb with the dd command. Not clear to me how to
> > either manually copy the base file set to the usb, or maybe leave
> > it on an accessible directory on my machine. Any help would be
> > appreciated.
> > 
> > Clay Daniels  
> 
> I noticed this also, but hadn't had time to figure out if I had
> messed up or the installer had. As a general rule I assume its me
> that messed up. Its odd if you mount the install66.fs you can see the
> pub/amd64 directory, but during installation it can't seem to find
> the directory regardless of what I have tried.
> 
> Edgar
> 

You'll have to select “installation set is on disk” and “not mounted”.

Best regards
Robert

Re: Installing OpenBSD -current snapshots

[Edgar Pettijohn]

On Wed, Nov 27, 2019 at 08:05:30PM -0600, Clay Daniels wrote:
> I have successfully installed OpenBSD 6.6 release and would like to give
> the Current Snapshots a try. I went to a mirror, and to:
> 
> Index of /pub/OpenBSD/snapshots/amd64/
> 
> I saw install66.fs (probably for usb memstick) and install66.iso (surely
> for a cd/dvd) at ~450Mb. I picked the install66.fs, wrote it to a usb
> thumbdrive, and it starts the install. When i get into the install it asks
> where are the file sets? Humm, maybe it gets these online and it tries to
> do this but no luck. It was late last night, and I checked to see if it had
> written anything to my disk, which it had not, and went to bed. This
> evening I'm looking a bit deeper at the snapshot directory and I suspect I
> need to provide the install with base66.tzg at ~239Mb.
> 
> My question now is after downloading the base, do I need to un-tar it, and
> how to I provide it to the install? I wrote the install66.fs to the usb
> with the dd command. Not clear to me how to either manually copy the base
> file set to the usb, or maybe leave it on an accessible directory on my
> machine. Any help would be appreciated.
> 
> Clay Daniels

I noticed this also, but hadn't had time to figure out if I had messed up or
the installer had. As a general rule I assume its me that messed up. Its odd
if you mount the install66.fs you can see the pub/amd64 directory, but during
installation it can't seem to find the directory regardless of what I have 
tried.

Edgar

Re: Installing OpenBSD -current snapshots

[Clay Daniels]

Never mind, I found the instructions the the same mirror directory,in a
plain text file called "INSTALL.amd64".

Forgive the dummy here,

Clay

On Wed, Nov 27, 2019 at 8:05 PM Clay Daniels 
wrote:

> I have successfully installed OpenBSD 6.6 release and would like to give
> the Current Snapshots a try. I went to a mirror, and to:
>
> Index of /pub/OpenBSD/snapshots/amd64/
>
> I saw install66.fs (probably for usb memstick) and install66.iso (surely
> for a cd/dvd) at ~450Mb. I picked the install66.fs, wrote it to a usb
> thumbdrive, and it starts the install. When i get into the install it asks
> where are the file sets? Humm, maybe it gets these online and it tries to
> do this but no luck. It was late last night, and I checked to see if it had
> written anything to my disk, which it had not, and went to bed. This
> evening I'm looking a bit deeper at the snapshot directory and I suspect I
> need to provide the install with base66.tzg at ~239Mb.
>
> My question now is after downloading the base, do I need to un-tar it, and
> how to I provide it to the install? I wrote the install66.fs to the usb
> with the dd command. Not clear to me how to either manually copy the base
> file set to the usb, or maybe leave it on an accessible directory on my
> machine. Any help would be appreciated.
>
> Clay Daniels
>

Installing OpenBSD -current snapshots

[Clay Daniels]

I have successfully installed OpenBSD 6.6 release and would like to give
the Current Snapshots a try. I went to a mirror, and to:

Index of /pub/OpenBSD/snapshots/amd64/

I saw install66.fs (probably for usb memstick) and install66.iso (surely
for a cd/dvd) at ~450Mb. I picked the install66.fs, wrote it to a usb
thumbdrive, and it starts the install. When i get into the install it asks
where are the file sets? Humm, maybe it gets these online and it tries to
do this but no luck. It was late last night, and I checked to see if it had
written anything to my disk, which it had not, and went to bed. This
evening I'm looking a bit deeper at the snapshot directory and I suspect I
need to provide the install with base66.tzg at ~239Mb.

My question now is after downloading the base, do I need to un-tar it, and
how to I provide it to the install? I wrote the install66.fs to the usb
with the dd command. Not clear to me how to either manually copy the base
file set to the usb, or maybe leave it on an accessible directory on my
machine. Any help would be appreciated.

Clay Daniels

Re: OpenBSD -current on T495

[Thomas de Grivel]

With latest snapshot the iwm driver attaches the wireless card which
works. Awesome !

Le sam. 9 nov. 2019 à 22:02, Patrick Wildt  a écrit :
>
> On Sat, Nov 09, 2019 at 12:08:35PM +0100, Thomas de Grivel wrote:
> > Everything works except wifi, suspend/resume and screen backlight, and
> > mute speakers button.
>
> Hi,
>
> I have an X395 which is basically the same machine.
>
> For Wifi I have temporarily replaced the Intel WiFi with a bwfm(4), the
> Dell Wireless DW1820a (note the a), which has two antenna connectors.
> There's the DW1830 which has three.  My X395 has two connectors, so I
> just put in the DW1820a.  Both can be purchased cheaply on eBay.
>
> The mute speaker button works for me, but the light doesn't show up.
>
> I will try to have a look at suspend/resume at one of the next OpenBSD
> hackathons.
>
> For the screen backlight I have come up with a diff, but it's not yet
> ready to be committed, as it should be done in a different fashion.
> Still, I have attached the diff if you want to give it a go.
>
> Patrick
>
> diff --git a/sys/dev/acpi/acpivideo.c b/sys/dev/acpi/acpivideo.c
> index 9498465a418..a46a99a67f7 100644
> --- a/sys/dev/acpi/acpivideo.c
> +++ b/sys/dev/acpi/acpivideo.c
> @@ -149,7 +149,7 @@ acpi_foundvout(struct aml_node *node, void *arg)
> if (node->parent != sc->sc_devnode)
> return (0);
>
> -   if (aml_searchname(node, "_BCM") && aml_searchname(node, "_BQC")) {
> +   if (aml_searchname(node, "_BCM")) {
> memset(, 0, sizeof(aaa));
> aaa.aaa_iot = sc->sc_acpi->sc_iot;
> aaa.aaa_memt = sc->sc_acpi->sc_memt;
> diff --git a/sys/dev/acpi/acpivout.c b/sys/dev/acpi/acpivout.c
> index 5fb6973f595..b1957b0c652 100644
> --- a/sys/dev/acpi/acpivout.c
> +++ b/sys/dev/acpi/acpivout.c
> @@ -60,6 +60,7 @@ struct acpivout_softc {
>
> int *sc_bcl;
> size_t  sc_bcl_len;
> +   int sc_bcl_cur;
>  };
>
>  void   acpivout_brightness_cycle(struct acpivout_softc *);
> @@ -113,10 +114,16 @@ acpivout_attach(struct device *parent, struct device 
> *self, void *aux)
> aml_register_notify(sc->sc_devnode, aaa->aaa_dev,
> acpivout_notify, sc, ACPIDEV_NOPOLL);
>
> +   acpivout_get_bcl(sc);
> +   if (!sc->sc_bcl_len)
> +   return;
> +
> +   sc->sc_bcl_cur = sc->sc_bcl[sc->sc_bcl_len - 1];
> +   sc->sc_bcl_cur = acpivout_get_brightness(sc);
> +   acpivout_set_brightness(sc, sc->sc_bcl_cur);
> +
> ws_get_param = acpivout_get_param;
> ws_set_param = acpivout_set_param;
> -
> -   acpivout_get_bcl(sc);
>  }
>
>  int
> @@ -130,12 +137,15 @@ acpivout_notify(struct aml_node *node, int notify, void 
> *arg)
> break;
> case NOTIFY_BRIGHTNESS_UP:
> acpivout_brightness_step(sc, 1);
> +   wsdisplay_change_brightness(1);
> break;
> case NOTIFY_BRIGHTNESS_DOWN:
> acpivout_brightness_step(sc, -1);
> +   wsdisplay_change_brightness(-1);
> break;
> case NOTIFY_BRIGHTNESS_ZERO:
> acpivout_brightness_zero(sc);
> +   wsdisplay_change_brightness(0);
> break;
> case NOTIFY_DISPLAY_OFF:
> /* TODO: D3 state change */
> @@ -200,7 +210,9 @@ acpivout_get_brightness(struct acpivout_softc *sc)
> struct aml_value res;
> int level;
>
> -   aml_evalname(sc->sc_acpi, sc->sc_devnode, "_BQC", 0, NULL, );
> +   if (aml_evalname(sc->sc_acpi, sc->sc_devnode, "_BQC", 0, NULL, ))
> +   return sc->sc_bcl_cur;
> +
> level = aml_val2int();
> aml_freevalue();
> DPRINTF(("%s: BQC = %d\n", DEVNAME(sc), level));
> @@ -242,6 +254,7 @@ acpivout_set_brightness(struct acpivout_softc *sc, int 
> level)
> aml_evalname(sc->sc_acpi, sc->sc_devnode, "_BCM", 1, , );
>
> aml_freevalue();
> +   sc->sc_bcl_cur = level;
>  }
>
>  void
> diff --git a/sys/dev/pci/drm/amd/amdgpu/amdgpu_kms.c 
> b/sys/dev/pci/drm/amd/amdgpu/amdgpu_kms.c
> index 02a90069f8d..4bad51b7d5f 100644
> --- a/sys/dev/pci/drm/amd/amdgpu/amdgpu_kms.c
> +++ b/sys/dev/pci/drm/amd/amdgpu/amdgpu_kms.c
> @@ -1656,7 +1656,7 @@ amdgpu_wsioctl(void *v, u_long cmd, caddr_t data, int 
> flag, struct proc *p)
> case WSDISPLAYIO_PARAM_BRIGHTNESS:
> dp->min = 0;
> dp->max = bd->props.max_brightness;
> -   dp->curval = bd->ops->get_brightness(bd);
> +   dp->curval = bd->props.brightness;
> return (dp->max > dp->min) ? 0 : -1;
> }
> break;
> diff --git a/sys/dev/wscons/wsdisplay.c b/sys/dev/wscons/wsdisplay.c
> index 61ccd2dae43..eda5c9d8843 100644
> --- a/sys/dev/wscons/wsdisplay.c
> +++ b/sys/dev/wscons/wsdisplay.c
> @@ -3369,3 +3369,43 @@ mouse_remove(struct wsscreen *scr)
>  }
>
>  #endif /* 

Re: OpenBSD -current on T495

[Patrick Wildt]

On Sat, Nov 09, 2019 at 12:08:35PM +0100, Thomas de Grivel wrote:
> Everything works except wifi, suspend/resume and screen backlight, and
> mute speakers button.

Hi,

I have an X395 which is basically the same machine.

For Wifi I have temporarily replaced the Intel WiFi with a bwfm(4), the
Dell Wireless DW1820a (note the a), which has two antenna connectors.
There's the DW1830 which has three.  My X395 has two connectors, so I
just put in the DW1820a.  Both can be purchased cheaply on eBay.

The mute speaker button works for me, but the light doesn't show up.

I will try to have a look at suspend/resume at one of the next OpenBSD
hackathons.

For the screen backlight I have come up with a diff, but it's not yet
ready to be committed, as it should be done in a different fashion.
Still, I have attached the diff if you want to give it a go.

Patrick

diff --git a/sys/dev/acpi/acpivideo.c b/sys/dev/acpi/acpivideo.c
index 9498465a418..a46a99a67f7 100644
--- a/sys/dev/acpi/acpivideo.c
+++ b/sys/dev/acpi/acpivideo.c
@@ -149,7 +149,7 @@ acpi_foundvout(struct aml_node *node, void *arg)
if (node->parent != sc->sc_devnode)
return (0);
 
-   if (aml_searchname(node, "_BCM") && aml_searchname(node, "_BQC")) {
+   if (aml_searchname(node, "_BCM")) {
memset(, 0, sizeof(aaa));
aaa.aaa_iot = sc->sc_acpi->sc_iot;
aaa.aaa_memt = sc->sc_acpi->sc_memt;
diff --git a/sys/dev/acpi/acpivout.c b/sys/dev/acpi/acpivout.c
index 5fb6973f595..b1957b0c652 100644
--- a/sys/dev/acpi/acpivout.c
+++ b/sys/dev/acpi/acpivout.c
@@ -60,6 +60,7 @@ struct acpivout_softc {
 
int *sc_bcl;
size_t  sc_bcl_len;
+   int sc_bcl_cur;
 };
 
 void   acpivout_brightness_cycle(struct acpivout_softc *);
@@ -113,10 +114,16 @@ acpivout_attach(struct device *parent, struct device 
*self, void *aux)
aml_register_notify(sc->sc_devnode, aaa->aaa_dev,
acpivout_notify, sc, ACPIDEV_NOPOLL);
 
+   acpivout_get_bcl(sc);
+   if (!sc->sc_bcl_len)
+   return;
+
+   sc->sc_bcl_cur = sc->sc_bcl[sc->sc_bcl_len - 1];
+   sc->sc_bcl_cur = acpivout_get_brightness(sc);
+   acpivout_set_brightness(sc, sc->sc_bcl_cur);
+
ws_get_param = acpivout_get_param;
ws_set_param = acpivout_set_param;
-
-   acpivout_get_bcl(sc);
 }
 
 int
@@ -130,12 +137,15 @@ acpivout_notify(struct aml_node *node, int notify, void 
*arg)
break;
case NOTIFY_BRIGHTNESS_UP:
acpivout_brightness_step(sc, 1);
+   wsdisplay_change_brightness(1);
break;
case NOTIFY_BRIGHTNESS_DOWN:
acpivout_brightness_step(sc, -1);
+   wsdisplay_change_brightness(-1);
break;
case NOTIFY_BRIGHTNESS_ZERO:
acpivout_brightness_zero(sc);
+   wsdisplay_change_brightness(0);
break;
case NOTIFY_DISPLAY_OFF:
/* TODO: D3 state change */
@@ -200,7 +210,9 @@ acpivout_get_brightness(struct acpivout_softc *sc)
struct aml_value res;
int level;
 
-   aml_evalname(sc->sc_acpi, sc->sc_devnode, "_BQC", 0, NULL, );
+   if (aml_evalname(sc->sc_acpi, sc->sc_devnode, "_BQC", 0, NULL, ))
+   return sc->sc_bcl_cur;
+
level = aml_val2int();
aml_freevalue();
DPRINTF(("%s: BQC = %d\n", DEVNAME(sc), level));
@@ -242,6 +254,7 @@ acpivout_set_brightness(struct acpivout_softc *sc, int 
level)
aml_evalname(sc->sc_acpi, sc->sc_devnode, "_BCM", 1, , );
 
aml_freevalue();
+   sc->sc_bcl_cur = level;
 }
 
 void
diff --git a/sys/dev/pci/drm/amd/amdgpu/amdgpu_kms.c 
b/sys/dev/pci/drm/amd/amdgpu/amdgpu_kms.c
index 02a90069f8d..4bad51b7d5f 100644
--- a/sys/dev/pci/drm/amd/amdgpu/amdgpu_kms.c
+++ b/sys/dev/pci/drm/amd/amdgpu/amdgpu_kms.c
@@ -1656,7 +1656,7 @@ amdgpu_wsioctl(void *v, u_long cmd, caddr_t data, int 
flag, struct proc *p)
case WSDISPLAYIO_PARAM_BRIGHTNESS:
dp->min = 0;
dp->max = bd->props.max_brightness;
-   dp->curval = bd->ops->get_brightness(bd);
+   dp->curval = bd->props.brightness;
return (dp->max > dp->min) ? 0 : -1;
}
break;
diff --git a/sys/dev/wscons/wsdisplay.c b/sys/dev/wscons/wsdisplay.c
index 61ccd2dae43..eda5c9d8843 100644
--- a/sys/dev/wscons/wsdisplay.c
+++ b/sys/dev/wscons/wsdisplay.c
@@ -3369,3 +3369,43 @@ mouse_remove(struct wsscreen *scr)
 }
 
 #endif /* HAVE_WSMOUSED_SUPPORT */
+
+int
+wsdisplay_change_brightness(int dir)
+{
+   struct wsdisplay_softc *sc;
+   struct wsdisplay_param dp;
+   int step, ret;
+
+   sc = (struct wsdisplay_softc *)device_lookup(_cd, 0);
+   if (sc == NULL)
+   return ENODEV;
+
+   memset(, 0, sizeof(dp));
+   dp.param = WSDISPLAYIO_PARAM_BRIGHTNESS;
+   ret = 

Re: OpenBSD -current on T495

[Thomas de Grivel]

Sure, here it is :

OpenBSD 6.6-current (GENERIC.MP) #442: Sat Nov  9 01:36:23 MST 2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 23478448128 (22390MB)
avail mem = 22754553856 (21700MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.1 @ 0xb9ecc000 (63 entries)
bios0: vendor LENOVO version "R12ET44W(1.14 )" date 09/14/2019
bios0: LENOVO 20NJCTO1WW
acpi0 at bios0: ACPI 5.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT SSDT SSDT TPM2 SSDT MSDM SLIC BATB HPET
APIC MCFG SBST WSMT IVRS SSDT CRAT CDIT FPDT SSDT SSDT SSDT UEFI
acpi0: wakeup devices GPP0(S3) GPP1(S3) GPP2(S3) GPP3(S3) GPP4(S3)
L850(S3) GPP5(S3) GPP6(S3) GP17(S3) XHC0(S3) XHC1(S3) GP18(S3)
LID_(S3) SLPB(S3)
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpihpet0 at acpi0: 14318180 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD Ryzen 7 PRO 3700U w/ Radeon Vega Mobile Gfx, 2295.97 MHz, 17-18-01
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu0: 64KB 64b/line 4-way I-cache, 32KB 64b/line 8-way D-cache, 512KB
64b/line 8-way L2 cache, 4MB 64b/line 16-way L3 cache
cpu0: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 24MHz
cpu0: mwait min=64, max=64, C-substates=1.1, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: AMD Ryzen 7 PRO 3700U w/ Radeon Vega Mobile Gfx, 2295.66 MHz, 17-18-01
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu1: 64KB 64b/line 4-way I-cache, 32KB 64b/line 8-way D-cache, 512KB
64b/line 8-way L2 cache, 4MB 64b/line 16-way L3 cache
cpu1: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: AMD Ryzen 7 PRO 3700U w/ Radeon Vega Mobile Gfx, 2295.66 MHz, 17-18-01
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu2: 64KB 64b/line 4-way I-cache, 32KB 64b/line 8-way D-cache, 512KB
64b/line 8-way L2 cache, 4MB 64b/line 16-way L3 cache
cpu2: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: AMD Ryzen 7 PRO 3700U w/ Radeon Vega Mobile Gfx, 2295.67 MHz, 17-18-01
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA,IBPB,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu3: 64KB 64b/line 4-way I-cache, 32KB 64b/line 8-way D-cache, 512KB
64b/line 8-way L2 cache, 4MB 64b/line 16-way L3 cache
cpu3: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu3: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative
cpu3: smt 1, core 1, package 0
cpu4 at mainbus0: apid 4 (application processor)
cpu4: AMD Ryzen 7 PRO 3700U w/ Radeon Vega Mobile Gfx, 2295.66 MHz, 17-18-01
cpu4: 

Re: OpenBSD -current on T495

[Tony Boston]

Could you please provide a dmesg output? The info you gave is not very helpful 
without it.

--
Tony

GPG-FP: 49CC8250 CDCF2183 6209C1AE 625677C1 F7783D5F
Threema: DN8PJX4Z






> On 9. Nov 2019, at 12:08, Thomas de Grivel  wrote:
> 
> Everything works except wifi, suspend/resume and screen backlight, and
> mute speakers button.
> 
> --
> Thomas de Grivel
> kmx.io
> 

OpenBSD -current on T495

[Thomas de Grivel]

Everything works except wifi, suspend/resume and screen backlight, and
mute speakers button.

--
 Thomas de Grivel
 kmx.io

Re: OpenBSD current & Firefox

[Oriol Demaria]

So seems that going back to default configuration fixed for a bit 
ublock. But adding lists seems to break it (I really don't have time to 
debug this further). Trying now with umatrix instead and seems to work 
without any issues. Just in case someone has the same problem.


Regards,

---
Oriol Demaria
2FFED630C16E4FF8

On 04/12/2018 14:16, Oriol Demaria wrote:

So over the weekend I noticed that Ublock Origin is not working for me
anymore on firefox since the last upgrade. I have tried to debug with
ktrace to figure out why. Checked the list, but found only someone
having issues with pledge over some unusual configuration.

Has anyone else had this problem? Any advice on debugging this issue?

Thanks in advance.

OpenBSD current & Firefox

[Oriol Demaria]

So over the weekend I noticed that Ublock Origin is not working for me
anymore on firefox since the last upgrade. I have tried to debug with
ktrace to figure out why. Checked the list, but found only someone
having issues with pledge over some unusual configuration.

Has anyone else had this problem? Any advice on debugging this issue?

Thanks in advance.

-- 
Oriol Demaria
2FFED630C16E4FF8

Re: OpenBSD Current on MacBook Air 7,1

[YASUOKA Masahiko]

Hi,

On Mon, 12 Dec 2016 20:19:19 +0100
Piotr Isajew  wrote:
> There seems to be a problem with a bootloader though. Once the
> system is installed on the SSD, the bootloader just stucks after
> probing HDDs. Also it's not possible to boot from the
> installation USB anymore.

I'd like you to try the latest snapshot.  The boot loader had some
problems on handling 4K sector disks and they were resolved.

--yasuoka

Re: openbsd -current: can't find firefox

[Raf Czlonka]

On Tue, Nov 29, 2016 at 10:53:30PM GMT, jungle Boogie wrote:
> Hi All,
> On 29 November 2016 at 07:57, Carlin Bingham  wrote:
> > On Tue, Nov 29, 2016 at 07:30:42AM -0800, jungle boogie wrote:
> >> You mean like this:
> >> $ cat /etc/doas.conf
> >> permit persist :wheel
> >> permit persist keepenv jungle as root
> >>
> >> $ doas pkg_add base64
> >> doas (jungle@host) password:
> >> quirks-2.270 signed on 2016-11-26T13:32:57Z
> >> base64-1.5: ok
> >>
> >
> > Ah, sorry. The problem is that there's no package for standard firefox
> > there. What's there is firefox-esr and the il8n packages.
> >
> 
> How do I install any firefox version?

pkg_add firefox{,-esr}

> At the least, should I not have a list of available options, like with python:
> 
> $ doas pkg_add python
> quirks-2.270 signed on 2016-11-26T13:32:57Z
> Ambiguous: choose package for python
> a   0: 
> 1: python-2.7.12p1
> 2: python-3.4.5p1
> 3: python-3.5.2p1
> Your choice: 0

Nope, firefox-esr is not a flavour (AKA flavor).

As per Carlin's email above - firefox package simply didn't get
built but you had the option to install firefox-esr.

At the time of writing this email, firefox package is available again.

Cheers,

Raf

Re: openbsd -current: can't find firefox

[jungle Boogie]

Hi All,
On 29 November 2016 at 07:57, Carlin Bingham  wrote:
> On Tue, Nov 29, 2016 at 07:30:42AM -0800, jungle boogie wrote:
>> You mean like this:
>> $ cat /etc/doas.conf
>> permit persist :wheel
>> permit persist keepenv jungle as root
>>
>> $ doas pkg_add base64
>> doas (jungle@host) password:
>> quirks-2.270 signed on 2016-11-26T13:32:57Z
>> base64-1.5: ok
>>
>
> Ah, sorry. The problem is that there's no package for standard firefox
> there. What's there is firefox-esr and the il8n packages.
>

How do I install any firefox version?

At the least, should I not have a list of available options, like with python:

$ doas pkg_add python
quirks-2.270 signed on 2016-11-26T13:32:57Z
Ambiguous: choose package for python
a   0: 
1: python-2.7.12p1
2: python-3.4.5p1
3: python-3.5.2p1
Your choice: 0


> --
> Carlin



-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info

Re: openbsd -current: can't find firefox

[Carlin Bingham]

On Tue, Nov 29, 2016 at 07:30:42AM -0800, jungle boogie wrote:
> You mean like this:
> $ cat /etc/doas.conf
> permit persist :wheel
> permit persist keepenv jungle as root
> 
> $ doas pkg_add base64
> doas (jungle@host) password:
> quirks-2.270 signed on 2016-11-26T13:32:57Z
> base64-1.5: ok
> 
 
Ah, sorry. The problem is that there's no package for standard firefox
there. What's there is firefox-esr and the il8n packages.

-- 
Carlin

Re: openbsd -current: can't find firefox

[jungle boogie]

On 11/29/2016 02:08 AM, Carlin Bingham wrote:

On Mon, Nov 28, 2016 at 11:50:25PM -0800, jungle boogie wrote:

Hi All,

I'm running the latest i386 snapshot:

[...]

I'd like to install firefox:
$ doas pkg_add firefox
quirks-2.270 signed on 2016-11-26T13:32:57Z
Can't find firefox

$ echo $PKG_PATH
http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/i386/

At the link above, I can clearly see dozens of firefox versions.

Can I not install it because pkg_add knows my system is newer than packages
listed?


doas doesn't preserve the PKG_PATH variable by default. You need to use
keepenv in doas.conf or set the path in pkg.conf instead.



You mean like this:
$ cat /etc/doas.conf
permit persist :wheel
permit persist keepenv jungle as root

$ doas pkg_add base64
doas (jungle@host) password:
quirks-2.270 signed on 2016-11-26T13:32:57Z
base64-1.5: ok





--
Carlin

Re: openbsd -current: can't find firefox

[Carlin Bingham]

On Mon, Nov 28, 2016 at 11:50:25PM -0800, jungle boogie wrote:
> Hi All,
> 
> I'm running the latest i386 snapshot:
> 
> [...]
>
> I'd like to install firefox:
> $ doas pkg_add firefox
> quirks-2.270 signed on 2016-11-26T13:32:57Z
> Can't find firefox
> 
> $ echo $PKG_PATH
> http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/i386/
> 
> At the link above, I can clearly see dozens of firefox versions.
> 
> Can I not install it because pkg_add knows my system is newer than packages
> listed?

doas doesn't preserve the PKG_PATH variable by default. You need to use
keepenv in doas.conf or set the path in pkg.conf instead.


--
Carlin

openbsd -current: can't find firefox

[jungle boogie]

Hi All,

I'm running the latest i386 snapshot:
OpenBSD 6.0-current (GENERIC.MP) #0: Mon Nov 28 20:52:50 MST 2016
bu...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz ("GenuineIntel" 686-class) 
2 GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF,PERF,SENSOR

real mem  = 3210760192 (3062MB)
avail mem = 3136524288 (2991MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 12/18/06, BIOS32 rev. 0 @ 0xffa10, SMBIOS rev. 
2.4 @ 0xf6e60 (62 entries)



I'd like to install firefox:
$ doas pkg_add firefox
quirks-2.270 signed on 2016-11-26T13:32:57Z
Can't find firefox

$ echo $PKG_PATH
http://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/i386/

At the link above, I can clearly see dozens of firefox versions.

Can I not install it because pkg_add knows my system is newer than 
packages listed?


Thanks!

Re: acpiasus(4) not attached with EeePC 1000H on OpenBSD-current

[Neil Hughes]

On 29/07/2016 19:32, Dominique Goncalves wrote:


My EeePC runs OpenBSD-current and works good. Since I updated the bios
to the latest version, some hotkeys are not working as before.
wireless and brightness hotkeys are working. standby and volume are
not working.


Since I have an Asus netbook I thought I'd dig out my 1015PX and replace 
5.8 with the latest snapshot to see what happens. I'm seeing the same - 
acpiasus isn't appearing in dmesg and whereas before I had sleep, mute 
and volume up/down working now I have sleep and screen brightness up/down.


dmesg 6.0:
==
OpenBSD 6.0 (GENERIC.MP) #2319: Tue Jul 26 13:00:43 MDT 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 2120744960 (2022MB)
avail mem = 2052059136 (1956MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xf0740 (31 entries)
bios0: vendor American Megatrends Inc. version "1301" date 05/06/2011
bios0: ASUSTeK Computer INC. 1015PX
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC MCFG ECDT OEMB HPET GSCI SSDT SLIC
acpi0: wakeup devices P0P1(S4) P0P4(S4) P0P5(S4) P0P6(S4) P0P7(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Atom(TM) CPU N570 @ 1.66GHz, 1666.80 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,SENSOR

cpu0: 512KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 166MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.0.2, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Atom(TM) CPU N570 @ 1.66GHz, 1666.48 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,SENSOR

cpu1: 512KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Atom(TM) CPU N570 @ 1.66GHz, 1666.48 MHz
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,SENSOR

cpu2: 512KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Atom(TM) CPU N570 @ 1.66GHz, 1666.48 MHz
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,NXE,LONG,LAHF,PERF,SENSOR

cpu3: 512KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpiec0 at acpi0
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 4 (P0P4)
acpiprt2 at acpi0: bus 2 (P0P5)
acpiprt3 at acpi0: bus -1 (P0P6)
acpiprt4 at acpi0: bus 1 (P0P7)
acpicpu0 at acpi0: !C3(100@57 mwait.3@0x30), !C2(500@1 mwait.1@0x10), 
C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: !C3(100@57 mwait.3@0x30), !C2(500@1 mwait.1@0x10), 
C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: !C3(100@57 mwait.3@0x30), !C2(500@1 mwait.1@0x10), 
C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: !C3(100@57 mwait.3@0x30), !C2(500@1 mwait.1@0x10), 
C1(1000@1 mwait.1), PSS

acpitz0 at acpi0: critical temperature is 101 degC
"PNP0303" at acpi0 not configured
"SYN0A13" at acpi0 not configured
acpibat0 at acpi0: BAT0 model "1015PE" serial   type LION oem "ASUS"
acpiac0 at acpi0: AC unit offline
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpibtn2 at acpi0: PWRB
"PNP0C14" at acpi0 not configured
acpivideo0 at acpi0: VGA_
acpivout0 at acpivideo0: LCDD
cpu0: Enhanced SpeedStep 1666 MHz: speeds: 1667, 1333, 1000 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Pineview DMI" rev 0x02
inteldrm0 at pci0 dev 2 function 0 "Intel Pineview Video" rev 0x02
drm0 at inteldrm0
intagp0 at inteldrm0
agp0 at intagp0: aperture at 0xd000, size 0x1000
inteldrm0: msi
inteldrm0: 1024x600
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
"Intel Pineview Video" rev 0x02 at pci0 dev 2 function 1 not configured
azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x02: msi
azalia0: codecs: Realtek ALC269
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: msi
pci1 at ppb0 bus 4
ppb1 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: m

acpiasus(4) not attached with EeePC 1000H on OpenBSD-current

[Dominique Goncalves]

Hi,

My EeePC runs OpenBSD-current and works good. Since I updated the bios
to the latest version, some hotkeys are not working as before.
wireless and brightness hotkeys are working. standby and volume are
not working.

Any help is appreciated, let me know if you need more information.

Regards

$ dmesg
OpenBSD 6.0 (GENERIC.MP) #1992: Tue Jul 26 12:52:55 MDT 2016
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Atom(TM) CPU N270 @ 1.60GHz ("GenuineIntel" 686-class) 1.60 GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,xTPR,PDCM,MOVBE,LAHF,PERF,SENSOR
real mem  = 1064452096 (1015MB)
avail mem = 1031368704 (983MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 10/21/09, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev.
2.5 @ 0xf0720 (30 entries)
bios0: vendor American Megatrends Inc. version "2204" date 10/21/2009
bios0: ASUSTeK Computer INC. 1000H
acpi0 at bios0: rev 0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC MCFG OEMB HPET SSDT
acpi0: wakeup devices P0P2(S4) P0P1(S4) HDAC(S4) P0P4(S4) P0P8(S4)
P0P5(S4) P0P7(S4) P0P9(S4) P0P6(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 132MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.0.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Atom(TM) CPU N270 @ 1.60GHz ("GenuineIntel" 686-class) 1.60 GHz
cpu1: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,xTPR,PDCM,MOVBE,LAHF,PERF,SENSOR
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xe000, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 3 (P0P5)
acpiprt2 at acpi0: bus 1 (P0P7)
acpiprt3 at acpi0: bus -1 (P0P6)
acpiec0 at acpi0
acpicpu0 at acpi0: !C2(500@1 mwait.1@0x10), C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: !C2(500@1 mwait.1@0x10), C1(1000@1 mwait.1), PSS
acpitz0 at acpi0: critical temperature is 85 degC
"PNP0303" at acpi0 not configured
"SYN0A04" at acpi0 not configured
acpibat0 at acpi0: BAT0 model "1000H" serial   type LION oem "ASUS"
acpiac0 at acpi0: AC unit online
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpibtn2 at acpi0: PWRB
"PNP0C14" at acpi0 not configured
acpivideo0 at acpi0: VGA_
acpivout0 at acpivideo0: LCDD
bios0: ROM list: 0xc/0xec00!
cpu0: Enhanced SpeedStep 1596 MHz: speeds: 1600, 1333, 1067, 800 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82945GME Host" rev 0x03
inteldrm0 at pci0 dev 2 function 0 "Intel 82945GME Video" rev 0x03
drm0 at inteldrm0
intagp0 at inteldrm0
agp0 at intagp0: aperture at 0xd000, size 0x1000
inteldrm0: apic 2 int 16
error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is
invalid, remainder is 253
Raw EDID:

00 ff ff ff ff ff ff 00  22 64 e9 03 f2 0a 01 00
12 12 01 03 80 16 0d 78  0a 80 36 9a 5e 5d 91 28
20 4f 54 00 00 00 01 01  01 01 01 01 01 01 01 01
01 01 01 01 01 01 94 11  00 b0 40 58 19 20 35 23
45 00 dc 81 00 00 00 19  00 00 00 fd 00 37 41 22
29 05 00 0a 20 20 20 20  20 20 00 00 00 fc 00 48
53 44 31 30 30 49 46 57  31 0a 20 20 00 00 00 10
00 0a 20 20 20 20 20 20  20 20 20 20 20 20 00 81
error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is
invalid, remainder is 253
Raw EDID:

00 ff ff ff ff ff ff 00  22 64 e9 03 f2 0a 01 00
12 12 01 03 80 16 0d 78  0a 80 36 9a 5e 5d 91 28
20 4f 54 00 00 00 01 01  01 01 01 01 01 01 01 01
01 01 01 01 01 01 94 11  00 b0 40 58 19 20 35 23
45 00 dc 81 00 00 00 19  00 00 00 fd 00 37 41 22
29 05 00 0a 20 20 20 20  20 20 00 00 00 fc 00 48
53 44 31 30 30 49 46 57  31 0a 20 20 00 00 00 10
00 0a 20 20 20 20 20 20  20 20 20 20 20 20 00 81
error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is
invalid, remainder is 253
Raw EDID:

00 ff ff ff ff ff ff 00  22 64 e9 03 f2 0a 01 00
12 12 01 03 80 16 0d 78  0a 80 36 9a 5e 5d 91 28
20 4f 54 00 00 00 01 01  01 01 01 01 01 01 01 01
01 01 01 01 01 01 94 11  00 b0 40 58 19 20 35 23
45 00 dc 81 00 00 00 19  00 00 00 fd 00 37 41 22
29 05 00 0a 20 20 20 20  20 20 00 00 00 fc 00 48
53 44 31 30 30 49 46 57  31 0a 20 20 00 00 00 10
00 0a 20 20 20 20 20 20  20 20 20 20 20 20 00 81
error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is
invalid, remainder is 253
Raw EDID:

00 ff ff ff ff ff ff 00  22 64 e9 03 f2 0a 01 00
12 12 01 03 80 16 0d 78  0a 80 36 9a 5e 5d 91 28
20 4f 54 00 00 00 01 01  01 01 01 01 01 01 01 01
01 01 01 01 01 01 94 11  00 b0 40 58 19 20 35 23
45 00 dc 81 00 00 00 19  00 00 00 fd 00 37 41 22
29 05 00 

Re: Socklog on OpenBSD -current

[Stuart Henderson]

On 2016-03-30, Predrag Punosevac  wrote:
> On 3/29/16 5:42 PM, Stuart Henderson wrote:
>> On 2016-03-29, Jeff Ross  wrote:
>>> Greetings all!
>>>
>>> I've been away from OpenBSD for a while and for sure I've missed more
>>> than a few things.  Just updated a firewall in anticipation of
> upgrading
>>> my server but there are things that have changed.
>>>
>>> What has me puzzled now is the change to syslogd.  For literally
> years
>>> I've run socklog from ports to replace the stock syslog with no
> problems
>>> but now it simply doesn't work on 5.9 -current.
>>>
>>> My former installations of socklog all listen to /dev/log but when I
>>> couldn't get anything to work listening there I switched to listening
> to
>>> 0.0.0.0:514 but still no joy.
>>>
>>> If anyone out there is using socklog, or possibly any alternative to
>>> syslog, I'd sure appreciate a clue by four to get socklog running
> again.
>> OpenBSD's syslog functions now use sendsyslog(2) which doesn't use
>> /dev/log sockets any more.
>>
>> Here is where syslogd was modified to do things this way:
>>
> http://anoncvs.spacehopper.org/openbsd-src/commit/?id=c40e16771993e74275857863c928d7f9cffe3699
>> - it's probably not all that complex to convert other logging daemons,
>> but afaik nobody has yet felt the need to do this for any of the
>> alternative log daemons in ports.
>>
>> If you don't want to write code and want to stick with socklog,
>> the easiest way is probably a minimal syslogd(8) setup that
>> forwards everything via UDP.
>>
> Hi Stuart,
>
> Could you please clarify something to me? I am running a centralized
> logging server using syslog-ng from the ports. The way I read your
> e-mail is that I will no longer be able to log messages using syslog-ng
> from the local host but the port will continue to work as expected.

Yes, this isn't particularly new though, it changed in 5.6.

> Would I be able to run syslogd for the local host and syslog-ng for
> remote hosts simultaneously? IIRC I saw people posting on misc who were
> doing that in the past but I think when I played with it syslog-ng
> didn't want to start until I turned off syslogd.

You can run two simultaneously but you'll need to get one of them to
bind to a specific IP address.

>  How suitable is syslogd
> from the base as a centralized logging server. I know that it supports
> TCP and TLS now but does it play well with rsyslog or syslog-ng? I have
> bunch of Linux servers to log.

If you can get them to feed it syslog messages using either the usual
UDP-based syslog protocol or using a TCP/TLS protocol then that should
work fine (IIRC the TLS code was developed against one of these,
possibly rsyslog?). syslogd(8) / syslog.conf(5) gained +host/++host
matching that allows you to separate logs between different hosts
into different files which can be useful on a centralised log host.
There are lots of options of how to set this all up.

Re: Socklog on OpenBSD -current

[Predrag Punosevac]

On 3/29/16 5:42 PM, Stuart Henderson wrote:
> On 2016-03-29, Jeff Ross  wrote:
>> Greetings all!
>>
>> I've been away from OpenBSD for a while and for sure I've missed more
>> than a few things.  Just updated a firewall in anticipation of
upgrading
>> my server but there are things that have changed.
>>
>> What has me puzzled now is the change to syslogd.  For literally
years
>> I've run socklog from ports to replace the stock syslog with no
problems
>> but now it simply doesn't work on 5.9 -current.
>>
>> My former installations of socklog all listen to /dev/log but when I
>> couldn't get anything to work listening there I switched to listening
to
>> 0.0.0.0:514 but still no joy.
>>
>> If anyone out there is using socklog, or possibly any alternative to
>> syslog, I'd sure appreciate a clue by four to get socklog running
again.
> OpenBSD's syslog functions now use sendsyslog(2) which doesn't use
> /dev/log sockets any more.
>
> Here is where syslogd was modified to do things this way:
>
http://anoncvs.spacehopper.org/openbsd-src/commit/?id=c40e16771993e74275857863c928d7f9cffe3699
> - it's probably not all that complex to convert other logging daemons,
> but afaik nobody has yet felt the need to do this for any of the
> alternative log daemons in ports.
>
> If you don't want to write code and want to stick with socklog,
> the easiest way is probably a minimal syslogd(8) setup that
> forwards everything via UDP.
>
Hi Stuart,

Could you please clarify something to me? I am running a centralized
logging server using syslog-ng from the ports. The way I read your
e-mail is that I will no longer be able to log messages using syslog-ng
from the local host but the port will continue to work as expected.
Would I be able to run syslogd for the local host and syslog-ng for
remote hosts simultaneously? IIRC I saw people posting on misc who were
doing that in the past but I think when I played with it syslog-ng
didn't want to start until I turned off syslogd. How suitable is syslogd
from the base as a centralized logging server. I know that it supports
TCP and TLS now but does it play well with rsyslog or syslog-ng? I have
bunch of Linux servers to log.

Thanks,
Predrag

Re: Socklog on OpenBSD -current

[Jeff Ross]

On 3/29/16 5:42 PM, Stuart Henderson wrote:

On 2016-03-29, Jeff Ross  wrote:

Greetings all!

I've been away from OpenBSD for a while and for sure I've missed more
than a few things.  Just updated a firewall in anticipation of upgrading
my server but there are things that have changed.

What has me puzzled now is the change to syslogd.  For literally years
I've run socklog from ports to replace the stock syslog with no problems
but now it simply doesn't work on 5.9 -current.

My former installations of socklog all listen to /dev/log but when I
couldn't get anything to work listening there I switched to listening to
0.0.0.0:514 but still no joy.

If anyone out there is using socklog, or possibly any alternative to
syslog, I'd sure appreciate a clue by four to get socklog running again.

OpenBSD's syslog functions now use sendsyslog(2) which doesn't use
/dev/log sockets any more.

Here is where syslogd was modified to do things this way:
http://anoncvs.spacehopper.org/openbsd-src/commit/?id=c40e16771993e74275857863c928d7f9cffe3699
- it's probably not all that complex to convert other logging daemons,
but afaik nobody has yet felt the need to do this for any of the
alternative log daemons in ports.

If you don't want to write code and want to stick with socklog,
the easiest way is probably a minimal syslogd(8) setup that
forwards everything via UDP.

Thank you, Stuart!  As always, you've been very helpful.  For now I'll 
stick to forwarding and play with the code as time permits.


Jeff

Re: Socklog on OpenBSD -current

[Stuart Henderson]

On 2016-03-29, Jeff Ross  wrote:
> Greetings all!
>
> I've been away from OpenBSD for a while and for sure I've missed more 
> than a few things.  Just updated a firewall in anticipation of upgrading 
> my server but there are things that have changed.
>
> What has me puzzled now is the change to syslogd.  For literally years 
> I've run socklog from ports to replace the stock syslog with no problems 
> but now it simply doesn't work on 5.9 -current.
>
> My former installations of socklog all listen to /dev/log but when I 
> couldn't get anything to work listening there I switched to listening to 
> 0.0.0.0:514 but still no joy.
>
> If anyone out there is using socklog, or possibly any alternative to 
> syslog, I'd sure appreciate a clue by four to get socklog running again.

OpenBSD's syslog functions now use sendsyslog(2) which doesn't use
/dev/log sockets any more.

Here is where syslogd was modified to do things this way:
http://anoncvs.spacehopper.org/openbsd-src/commit/?id=c40e16771993e74275857863c928d7f9cffe3699
- it's probably not all that complex to convert other logging daemons,
but afaik nobody has yet felt the need to do this for any of the
alternative log daemons in ports.

If you don't want to write code and want to stick with socklog,
the easiest way is probably a minimal syslogd(8) setup that
forwards everything via UDP.

Socklog on OpenBSD -current

[Jeff Ross]

Greetings all!

I've been away from OpenBSD for a while and for sure I've missed more 
than a few things.  Just updated a firewall in anticipation of upgrading 
my server but there are things that have changed.


What has me puzzled now is the change to syslogd.  For literally years 
I've run socklog from ports to replace the stock syslog with no problems 
but now it simply doesn't work on 5.9 -current.


My former installations of socklog all listen to /dev/log but when I 
couldn't get anything to work listening there I switched to listening to 
0.0.0.0:514 but still no joy.


If anyone out there is using socklog, or possibly any alternative to 
syslog, I'd sure appreciate a clue by four to get socklog running again.


Thanks!

Jeff

dmesg;

OpenBSD 5.9-current (GENERIC.MP) #1682: Tue Mar 29 12:08:00 MDT 2016
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz ("GenuineIntel" 686-class) 
1.84 GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF,PERF,SENSOR

real mem  = 1040486400 (992MB)
avail mem = 1008070656 (961MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: date 07/29/05, SMBIOS rev. 2.4 @ 0xe (38 entries)
bios0: vendor Apple Inc. version "MM21.88Z.009A.B00.0706281359" date 
06/28/07

bios0: Apple Inc. Macmini2,1
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC MCFG ASF! SBST ECDT SSDT SSDT SSDT
acpi0: wakeup devices PXS1(S4) PXS2(S4) USB1(S3) USB2(S3) USB3(S3) 
USB4(S3) USB7(S3)

acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 166MHz
cpu0: mwait min=64, max=64, C-substates=0.2.2.2.2, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz ("GenuineIntel" 686-class) 
1.84 GHz
cpu1: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF,PERF,SENSOR

ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 1
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpiec0 at acpi0
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus 2 (RP02)
acpiprt3 at acpi0: bus 3 (PCIB)
acpicpu0 at acpi0: !C2(500@1 mwait@0x10), C1(1000@1 mwait), PSS
acpicpu1 at acpi0: !C2(500@1 mwait@0x10), C1(1000@1 mwait), PSS
acpibtn0 at acpi0: PWRB
"PNP0A08" at acpi0 not configured
"PNP0C02" at acpi0 not configured
"PNP0C0F" at acpi0 not configured
"PNP0C0F" at acpi0 not configured
"PNP0C0F" at acpi0 not configured
"PNP0C0F" at acpi0 not configured
"PNP0C0F" at acpi0 not configured
"PNP0C0F" at acpi0 not configured
"PNP0C0F" at acpi0 not configured
"PNP0C0F" at acpi0 not configured
"APP0001" at acpi0 not configured
"PNP0C09" at acpi0 not configured
"PNP0200" at acpi0 not configured
"INT0800" at acpi0 not configured
"PNP0103" at acpi0 not configured
"PNP" at acpi0 not configured
"PNP0C04" at acpi0 not configured
"PNP0C02" at acpi0 not configured
"PNP0B00" at acpi0 not configured
"PNP0100" at acpi0 not configured
acpivideo0 at acpi0: GFX0
bios0: ROM list: 0xc/0xe600!
cpu0: Enhanced SpeedStep 1834 MHz: speeds: 1833, 1667, 1500, 1333, 1000 MHz
memory map conflict 0xe00f8000/0x1000
memory map conflict 0xfed1c000/0x4000
memory map conflict 0xfffb/0x3
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82945GM Host" rev 0x03
inteldrm0 at pci0 dev 2 function 0 "Intel 82945GM Video" rev 0x03
drm0 at inteldrm0
intagp0 at inteldrm0
agp0 at intagp0: aperture at 0x4000, size 0x1000
inteldrm0: apic 1 int 16
inteldrm0: 1600x900
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
vendor "Intel", unknown product 0x27a3 (class DASP subclass Time and 
Frequency, rev 0x03) at pci0 dev 7 function 0 not configured

azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x02: msi
azalia0: codecs: Sigmatel STAC9220/1
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x02: apic 1 int 17
pci1 at ppb0 bus 1
mskc0 at pci1 dev 0 function 0 "Marvell Yukon 88E8053" rev 0x22, Yukon-2 
EC rev. A3 (0x2): apic 1 int 16

msk0 at mskc0 port A: address 00:1f:f3:44:ee:6f
eephy0 at msk0 phy 0: 88E Gigabit PHY, rev. 2
ppb1 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x02: apic 1 int 16
pci2 at ppb1 bus 2
ath0 at pci2 dev 0 function 0 "Atheros AR5424" rev 0x01: apic 1 int 17
ath0: AR5424 10.3 phy 6.1 rf 10.2 eeprom 5.3, WOR5_ETSIC, address 
00:1f:f3:fa:8d:3e

OpenBSD current crash (Thinkpad X220i)

[Stefan Berger]

hi, 

my notebook had a hiccup: it suddenly hanged and stoped working. 
I had firefox, cwm+X11, emacs (terminal) and a few tmux sessions open. 

The snapshot is from Monday, 24.08.  I also checkoud out the sources and it 
is selfcompiled. 

Here is what I can see in my /var/log/messages before the hiccup: 

Aug 26 11:29:19 x220i dhclient[6121]: iwn0 down; exiting
Aug 26 11:43:44 x220i apmd: battery status: high. external power status: not 
connected. estimated battery life 76% (251 minutes)
Aug 26 12:00:01 x220i syslogd: restart
Aug 26 12:33:14 x220i apmd: battery status: high. external power status: not 
connected. estimated battery life 55% (132 minutes)
Aug 26 12:43:14 x220i apmd: battery status: low. external power status: not 
connected. estimated battery life 50% (119 minutes)
Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:36 x220i /bsd: error: 

Re: Audio problems with OpenBSD-current/amd64 on Acer C720p Chromebook

[lists]

  Sorry for wasting yout time.

there is still stutter on disk activity on mp amd64 which is mostly in
media players depending on gtk libs, it is embarrassing to say the
least.

Re: Audio problems with OpenBSD-current/amd64 on Acer C720p Chromebook

[Alexandre Ratchov]

On Fri, Jul 31, 2015 at 03:05:40AM +0200, Alexander Shendi wrote:
 Hi,
 
 after rebooting the GENERIC.MP kernel supplied with the 5.8 snapshot I had 
 been using previously everything works fine.
 
 I don't actually know why -- I'll assume it was a hardware glitch.
 
 Sorry for wasting yout time.
 

no problem :)

Re: Audio problems with OpenBSD-current/amd64 on Acer C720p Chromebook

[Alexandre Ratchov]

On Fri, Jul 31, 2015 at 11:53:31AM +0300, li...@wrant.com wrote:
   Sorry for wasting yout time.
 
 there is still stutter on disk activity on mp amd64 which is mostly in
 media players depending on gtk libs, it is embarrassing to say the
 least.

You mean that audio on a mostly idle box, with only a gtk-based
player sutters?

When audio stutters, before playback stops, you could run audioctl
to see the number of errors, to determine whether they are caused
by the player (very few errors or not at all) or by the audio
sub-system.

Before testing, make sure you use the latest kernel, libsndio,
sndiod and audioctl.

Re: Audio problems with OpenBSD-current/amd64 on Acer C720p Chromebook

[Gregor Best]

On Fri, Jul 31, 2015 at 11:53:31AM +0300, li...@wrant.com wrote:
 [...]
 there is still stutter on disk activity on mp amd64 which is mostly in
 media players depending on gtk libs, it is embarrassing to say the
 least.
 [...]

I've seen something similar when my cvsync cronjob kicks in. I can live
with that though to be honest.

Your patch didn't apply though, you might want to resend it.

-- 
Gregor Best

Audio problems with OpenBSD-current/amd64 on Acer C720p Chromebook

[Alexander Shendi]

Dear list subscribers,
 
I have installed OpenBSD-current on my Acer C720p Chromebook.  
I am using -current because I had problems with X11 with 
the 5.7 release.
 
Audio used to work out of the box on that device with earlier 
versions of -current, but has stopped working in the most recent 
version I have installed (Playback of an MP3-file with either 
VLC or mpg123 produced no sound)
 
$ uname -a
OpenBSD alex-acer-720p.my.domain 5.8 GENERIC.MP#1206 amd64

Excerpt from dmesg follows:
 
[...]
azalia0 at pci0 dev 3 function 0 Intel Core 4G HD Audio rev 0x09: msi
azalia0: No codecs found
[...]
azalia1 at pci0 dev 27 function 0 Intel 8 Series HD Audio rev 0x04: msi
azalia1: codecs: Realtek/0x0283
audio0 at azalia1
[...]

(The entire dmesg can be found at: 
http://www.alexshendi.org/tmp/dmesg-c720p-20150730.txt)

However I had some success in getting sound to work: I added the line:

sndiod_flags='-f /dev/audio1'

to /etc/rc.conf.local

Now playing an MP3-file in VLC works, but I'm not able to adjust the volume
in VLC. Does this have something to do with /dev/audioctl?

I noticed that both /dev/audio and /dev/audioctl are symlinks to 
/dev/audio0 resp. /dev/audioctl0. Sould I change these links 
to point to audio1 and audioctl1? 

Any suggestions will be appreciated. Many thanks in advance.

Best Regards,

Alexander

Re: Audio problems with OpenBSD-current/amd64 on Acer C720p Chromebook

[Alexandre Ratchov]

On Thu, Jul 30, 2015 at 09:29:31PM +0200, Alexander Shendi wrote:
 Dear list subscribers,
  
 I have installed OpenBSD-current on my Acer C720p Chromebook.  
 I am using -current because I had problems with X11 with 
 the 5.7 release.
  
 Audio used to work out of the box on that device with earlier 
 versions of -current, but has stopped working in the most recent 
 version I have installed (Playback of an MP3-file with either 
 VLC or mpg123 produced no sound)
  
 $ uname -a
 OpenBSD alex-acer-720p.my.domain 5.8 GENERIC.MP#1206 amd64
 
 Excerpt from dmesg follows:
  
 [...]
 azalia0 at pci0 dev 3 function 0 Intel Core 4G HD Audio rev 0x09: msi
 azalia0: No codecs found
 [...]
 azalia1 at pci0 dev 27 function 0 Intel 8 Series HD Audio rev 0x04: msi
 azalia1: codecs: Realtek/0x0283
 audio0 at azalia1
 [...]
 
 (The entire dmesg can be found at: 
 http://www.alexshendi.org/tmp/dmesg-c720p-20150730.txt)
 
 However I had some success in getting sound to work: I added the line:
 
 sndiod_flags='-f /dev/audio1'
 
 to /etc/rc.conf.local
 

there's no /dev/audio1 according to your dmesg and -f uses another
syntax (see sndio(7) man page)

 Now playing an MP3-file in VLC works, but I'm not able to adjust the volume
 in VLC. Does this have something to do with /dev/audioctl?
 
 I noticed that both /dev/audio and /dev/audioctl are symlinks to 
 /dev/audio0 resp. /dev/audioctl0. Sould I change these links 
 to point to audio1 and audioctl1? 

The symlinks are only used by audioctl and mixerctl utilities, no
need to change them.

 
 Any suggestions will be appreciated. Many thanks in advance.

could you do the following: build  install a new kernel with these
options defined.

option AUDIO_DEBUG
option AZALIA_DEBUG

Then, boot it, kill sndiod, and start it in a terminal with:

sndiod -dd

and in another terminal, play a .mp3 with mpg123 (or whatever you
use) and see what errors sndiod displays and what dmesg says. Let
me know if you have questions and/or you need help for the setup.

thanks

Re: Audio problems with OpenBSD-current/amd64 on Acer C720p Chromebook

[Alexander Shendi]

Gesendet: Donnerstag, 30. Juli 2015 um 23:27 Uhr
Von: Alexandre Ratchov a...@caoua.org
An: Alexander Shendi alexander.she...@web.de
Cc: misc@openbsd.org
Betreff: Re: Audio problems with OpenBSD-current/amd64 on Acer C720p Chromebook
[snip]

 could you do the following: build  install a new kernel with these
 options defined.
 
 option AUDIO_DEBUG
 option AZALIA_DEBUG
 
 Then, boot it, kill sndiod, and start it in a terminal with:
 
 sndiod -dd
 
 and in another terminal, play a .mp3 with mpg123 (or whatever you
 use) and see what errors sndiod displays and what dmesg says. Let
 me know if you have questions and/or you need help for the setup.
 
 thanks

I did as you requested. Namely:

* Got the OpenBSD-current sources via AnonCVS.
* Built a custom kernel with the options above 
* Removed the -f /dev/audio1 flags from /etc/rc.conf.local
* Booted the new, custom kernel
* Killed sndiod via pkill sndiod
* Restarted it in a terminal as requested above
* Played an MP3-file in VLC (no sound output observed) for a 
  few seconds.

Please find the combined terminal output and the new dmesg at:

http://www.alexshendi.org/tmp/dmesg-acer-c720p-20150731.txt

However I can't make much sense of the output as I don't
know enough about the audio subsystem. Could you please 
have a look? Please let me know if I can run further test,
or if you need further info.

Many thanks for your help.

Best Regards,

Alexander

Re: Audio problems with OpenBSD-current/amd64 on Acer C720p Chromebook

[Alexander Shendi]

Hi,

after rebooting the GENERIC.MP kernel supplied with the 5.8 snapshot I had 
been using previously everything works fine.

I don't actually know why -- I'll assume it was a hardware glitch.

Sorry for wasting yout time.

Best Regards,

Alexander

Re: OpenBSD -current AHCI on HP Probook 450 G0

[nrmfh]

On Monday, 22 December 2014, 4:02, Doug Hogan d...@acyclic.org wrote:

 On Sun, Dec 21, 2014 at 10:05:22AM +, ali wrote:
  Atanas Vladimirov vlado at bsdbg.net writes:
   This is the first time when I try to install OpenBSD on a such hardware.
   I used bsd.rd to install it on a usb flash drive. After reboot I choose 
   to boot from the usb drive.
   Bootloader can't load bsd kernel and the laptop restarts without error.
   If I change SATA mode in BIOS from AHCI to IDE I can boot from the usb 
   drive.
  
  I have the same problem with my HP ProBook 4530s. I don't want to switch
  to AHCI. Is there another way to install OpenBSD?
 
 One of my laptops is a 4530s.  I was able to install by using a CD.
 It's running snapshots so I upgrade with bsd.rd.  I'm using BIOS F.41 if

 that helps.

Sorry, I said something mistakenly. I don't want to switch from AHCI to IDE.
It seems that OpenBSD kernel will not load correctly when AHCI is enabled.
Are you sure that AHCI was enabled during installation?

Re: OpenBSD -current AHCI on HP Probook 450 G0

[ali]

Atanas Vladimirov vlado at bsdbg.net writes:

 
 Hi,
 This is the first time when I try to install OpenBSD on a such hardware.
 I used bsd.rd to install it on a usb flash drive. After reboot I choose 
 to boot from the usb drive.
 Bootloader can't load bsd kernel and the laptop restarts without error.
 If I change SATA mode in BIOS from AHCI to IDE I can boot from the usb 
 drive.

I have the same problem with my HP ProBook 4530s. I don't want to switch
to AHCI. Is there another way to install OpenBSD?

Re: OpenBSD -current AHCI on HP Probook 450 G0

[Doug Hogan]

On Sun, Dec 21, 2014 at 10:05:22AM +, ali wrote:
 Atanas Vladimirov vlado at bsdbg.net writes:
  This is the first time when I try to install OpenBSD on a such hardware.
  I used bsd.rd to install it on a usb flash drive. After reboot I choose 
  to boot from the usb drive.
  Bootloader can't load bsd kernel and the laptop restarts without error.
  If I change SATA mode in BIOS from AHCI to IDE I can boot from the usb 
  drive.
 
 I have the same problem with my HP ProBook 4530s. I don't want to switch
 to AHCI. Is there another way to install OpenBSD?

One of my laptops is a 4530s.  I was able to install by using a CD.
It's running snapshots so I upgrade with bsd.rd.  I'm using BIOS F.41 if
that helps.

Re: Cannot determine prefetch area error with OpenBSD current autoinstall

[Nick Holland]

On 12/16/14 22:06, Adriaan wrote:
 On Tue, Dec 16, 2014 at 8:26 AM, Raf r...@devio.us wrote:

 On Tue, Dec 16, 2014 at 01:01:51AM EST, Adriaan wrote:

  An initial interactive install was succesful. A next autonstall using
  bsd,rd gave a Cannot determine prefetch area after selecting the
  sets.
  [...]
  Cannot determine prefetch area. Continue without verification? [no] no

 I see that tedu@ already mentioned the fact about your local storage is
 probably too small. I'll only add a link to the FAQ[0] in case you have
 missed it.

 
 With the following custom partition scheme of the same 3GB disk the
 verification succeeds:
 
 p m
 OpenBSD area: 63-6322176; size: 3087.0M; free: 0.0M
 #size   offset  fstype [fsize bsize  cpg]
   a:  2901.9M   64  4.2BSD   2048 163841 # /
   b:   185.1M  5943168swap   # none
   c:  3093.4M0  unused
 
...
 So the verification procedure simply needed a larger partition.

Look at the install scripts -- it doesn't prefetch just anywhere, it has
a few specific places.  /tmp, /home I think are two of the choices, may
be more (NOTE: I am too tired to bother looking this up myself now, and
it would be good experience for you to do so).  I don't think /usr is.
Thus, your original config, which had nowhere near enough space in /tmp
or /home for the prefetch caused it not to.

Nick.

Cannot determine prefetch area error with OpenBSD current autoinstall

[Adriaan]

OpenBSD 5.6-current (RAMDISK_CD) #573: Sun Dec 14 20:08:49 MST 2014
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISK_CD

An initial interactive install was succesful. A next autonstall using
bsd,rd gave a
Cannot determine prefetch area after selecting the sets.

(Complete  dmesg and install.conf will follow)

===
Let's install the sets!
Location of sets? (disk http or 'done') [http] http
HTTP proxy URL? (e.g. 'http://proxy:8080', or 'none') [none] none
(Unable to get list from ftp.openbsd.org, but that is OK)
HTTP Server? (hostname or 'done') hercules.utp.xnet
Server directory? [pub/OpenBSD/snapshots/i386] snapshots/i386

Select sets by entering a set name, a file name pattern or 'all'. De-select
sets by prepending a '-' to the set name, file name pattern or 'all'.
Selected
sets are labelled '[X]'.
[X] bsd   [X] base56.tgz[X] xbase56.tgz   [X] xserv56.tgz
[X] bsd.rd[X] comp56.tgz[X] xshare56.tgz  [ ] site56.tgz
[ ] bsd.mp[X] man56.tgz [X] xfont56.tgz
Set name(s)? (or 'abort' or 'done') [done] -all bsd bsd.rd bsd.mp
base56.tgz site56.tgz done
Cannot determine prefetch area. Continue without verification? [no] no
failed; check /ai.log
===
Note that all sets were specified in a single reply in the install.conf
here.

A retry with only listing a single set for each prompt, gave the same error:

===Select sets by entering a set name, a file name pattern or 'all'.
De-select
sets by prepending a '-' to the set name, file name pattern or 'all'.
Selected
sets are labelled '[X]'.
[X] bsd   [X] base56.tgz[X] xbase56.tgz   [X] xserv56.tgz
[X] bsd.rd[X] comp56.tgz[X] xshare56.tgz  [ ] site56.tgz
[ ] bsd.mp[X] man56.tgz [X] xfont56.tgz
Set name(s)? (or 'abort' or 'done') [done] -all
[ ] bsd   [ ] base56.tgz[ ] xbase56.tgz   [ ] xserv56.tgz
[ ] bsd.rd[ ] comp56.tgz[ ] xshare56.tgz  [ ] site56.tgz
[ ] bsd.mp[ ] man56.tgz [ ] xfont56.tgz
Set name(s)? (or 'abort' or 'done') [done] bsd
[X] bsd   [ ] base56.tgz[ ] xbase56.tgz   [ ] xserv56.tgz
[ ] bsd.rd[ ] comp56.tgz[ ] xshare56.tgz  [ ] site56.tgz
[ ] bsd.mp[ ] man56.tgz [ ] xfont56.tgz
Set name(s)? (or 'abort' or 'done') [done] bsd.rd
[X] bsd   [ ] base56.tgz[ ] xbase56.tgz   [ ] xserv56.tgz
[X] bsd.rd[ ] comp56.tgz[ ] xshare56.tgz  [ ] site56.tgz
[ ] bsd.mp[ ] man56.tgz [ ] xfont56.tgz
Set name(s)? (or 'abort' or 'done') [done] bsd.mp
[X] bsd   [ ] base56.tgz[ ] xbase56.tgz   [ ] xserv56.tgz
[X] bsd.rd[ ] comp56.tgz[ ] xshare56.tgz  [ ] site56.tgz
[X] bsd.mp[ ] man56.tgz [ ] xfont56.tgz
Set name(s)? (or 'abort' or 'done') [done] base56.tgz
[X] bsd   [X] base56.tgz[ ] xbase56.tgz   [ ] xserv56.tgz
[X] bsd.rd[ ] comp56.tgz[ ] xshare56.tgz  [ ] site56.tgz
[X] bsd.mp[ ] man56.tgz [ ] xfont56.tgz
Set name(s)? (or 'abort' or 'done') [done] site56.tgz
[X] bsd   [X] base56.tgz[ ] xbase56.tgz   [ ] xserv56.tgz
[X] bsd.rd[ ] comp56.tgz[ ] xshare56.tgz  [X] site56.tgz
[X] bsd.mp[ ] man56.tgz [ ] xfont56.tgz
Set name(s)? (or 'abort' or 'done') [done] done
Cannot determine prefetch area. Continue without verification? [no] no
failed; check /ai.log

The install.conf for this retry:

===Terminal type? = vt220
System hostname = andromache
Which network interface do you wish to configure? = xl0
IPv4 address for = 192.168.222.188
Netmask for = 255.255.255.0
IPv6 address for = none
Which network interface do you wish to configure? = done
Default IPv4 route? = 192.168.222.10
DNS domain name? = utp.xnet
DNS nameservers? = 192.168.222.10
Password for root account? = dfsdfsdfdf
Public ssh key for root account? = ecdsa-sha2-nistp256
E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBCMPEpNB1XOPiaIcv2NJhG1c5Os595IebooZdnloA0OT+npTyk9FQbysijlFq+GWyc7Wu27qaELlhikj//qAyGc=
adri...@hercules.utp.xnet
Start sshd(8) by default? = yes
Start ntpd(8) by default? = yes
NTP server? = default
Do you expect to run the X Window System? = no
Do you want the X Window System to be started by xdm(1)? = no
Do you want to suspend on lid close? = no
Change the default console to com0? = yes
Which speed should com0 use? = 19200
What timezone are you in? = Europe/Amsterdam
Setup a user? = no
Which disk is the root disk? = sd0
Use DUIDs rather than device names in fstab? = yes
Use (W)hole disk or (E)dit the MBR? = W
Use (A)uto layout, (E)dit auto layout, or create (C)ustom layout? = a
Which disk do you wish to initialize? = done
Location of sets? = http
HTTP proxy URL? = none
HTTP Server? = hercules.utp.xnet
Server directory? = snapshots/i386
Set name(s)? = -all
Set name(s)? = bsd
Set name(s)? = bsd.rd
Set name(s)? = bsd.mp
Set name(s)? = base56.tgz
Set name(s)? = site56.tgz
Set name(s)? = done
Checksum test for site56.tgz 

Re: Cannot determine prefetch area error with OpenBSD current autoinstall

[Ted Unangst]

On Tue, Dec 16, 2014 at 07:01, Adriaan wrote:
 OpenBSD 5.6-current (RAMDISK_CD) #573: Sun Dec 14 20:08:49 MST 2014
 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISK_CD
 
 An initial interactive install was succesful. A next autonstall using
 bsd,rd gave a
 Cannot determine prefetch area after selecting the sets.

this probably means there wasn't a partition with enough free space
available. looks like you have a pretty small disk.

Re: Cannot determine prefetch area error with OpenBSD current autoinstall

[Raf]

On Tue, Dec 16, 2014 at 01:01:51AM EST, Adriaan wrote:

 An initial interactive install was succesful. A next autonstall using
 bsd,rd gave a Cannot determine prefetch area after selecting the
 sets.
 [...]
 Cannot determine prefetch area. Continue without verification? [no] no

I see that tedu@ already mentioned the fact about your local storage is
probably too small. I'll only add a link to the FAQ[0] in case you have
missed it.

 failed; check /ai.log

Have you checked '/ai.log'?

 Checksum test for site56.tgz failed. Continue anyway? = yes
 Unverified sets: site56.tgz. Continue without verification? = yes
 Checksum test for site56-andromache.tgz failed. Continue anyway? = yes
 Unverified sets: site56-andromache.tgz. Continue without verification? =
 yes

Given that the initial installation finishes just fine, I conclude that
the second attempt fails due to your 'site*.tgz'[1] file sets being too
big - try again without them.

[0] http://www.openbsd.org/faq/faq4.html#InstMedia
[1] http://www.openbsd.org/faq/faq4.html#site

Regards,

Raf

Re: Cannot determine prefetch area error with OpenBSD current autoinstall

[Adriaan]

On Tue, Dec 16, 2014 at 7:35 AM, Ted Unangst t...@tedunangst.com wrote:

 On Tue, Dec 16, 2014 at 07:01, Adriaan wrote:
  OpenBSD 5.6-current (RAMDISK_CD) #573: Sun Dec 14 20:08:49 MST 2014
  dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISK_CD
 
  An initial interactive install was succesful. A next autonstall using
  bsd,rd gave a
  Cannot determine prefetch area after selecting the sets.

 this probably means there wasn't a partition with enough free space
 available. looks like you have a pretty small disk.


Yes, the disk is 3GB but I only installed the minimum:

$ df -h
Filesystem SizeUsed   Avail Capacity  Mounted on
/dev/wd0a  837M   44.4M750M 6%/
/dev/wd0e  323M   14.8M292M 5%/home
/dev/wd0d  1.7G205M1.4G13%/usr

During the install there is even more space, because then, the site56.tgz
has not  yet installed some packages, that are PKG_CACHEd in /home/packages.

ls -l /home/packages ; du -h $_
total 30160
-rw-r--r--  1 root  wheel  3265288 Dec 16 07:19 alpine-2.11p3.tgz
-rw-r--r--  1 root  wheel  3273159 Dec 16 07:19 aspell-0.60.6.1p1.tgz
-rw-r--r--  1 root  wheel   125754 Dec 16 07:19 bzip2-1.0.6p1.tgz
-rw-r--r--  1 root  wheel  5213261 Dec 16 07:19 gettext-0.19.3.tgz
-rw-r--r--  1 root  wheel  1540225 Dec 16 07:18 libiconv-1.14p1.tgz
-rw-r--r--  1 root  wheel  1374388 Dec 16 07:19 lynx-2.8.9pl1p0.tgz
-rw-r--r--  1 root  wheel 7580 Dec 16 07:18 quirks-2.43.tgz
-rw-r--r--  1 root  wheel   166936 Dec 16 07:19 unzip-6.0p5.tgz
-rw-r--r--  1 root  wheel   320970 Dec 16 07:19 xz-5.0.7.tgz
14.7M   /home/packages

Re: CPU power consumption on thinkpad x201 on openbsd current

[Stefan Sperling]

On Wed, Jun 04, 2014 at 11:08:42PM +0200, Johan Svensson wrote:
 I'm trying to migrate from Linux to Openbsd on my laptop (thinkpad x201).
 
 The first problem that i came across was that the Cpu fanspeed was running
 constantly at 3500RPM.
 After the acpithinkpad.c patch from jcs (and i modified to make it work on
 the openbsd-current(link: http://exclude.se/patch/jcs_mod_by_js.diff)
 
 Another thing that i noticed is that the battery lifetime is really bad.
 In Linux i get around ~5,5 hours.
 In OpenBSD i get around 2 hours.
 
 when i ran : sysctl hw.sensors | grep -i consumption.
 the output of the cpu was 6W.
 
 in Linux it's around 1,5W.
 
 with: apmd -C and apmd -L it's the same.
 dmesg: http://exclude.se/openbsd/dmesg.txt
 
 Is there anyway to fix this?
 
 Regards
 Johan Svensson

I've done some testing on an x201i and it seems the intel_powerclamp driver
(Package Level C-state Idle Injection for Intel CPUs) is responsible for
the difference in battery life. If that Linux driver is blacklisted battery
life drops to about the same levels as on OpenBSD.

OpenBSD -current AHCI on HP Probook 450 G0

[Atanas Vladimirov]

Hi,
This is the first time when I try to install OpenBSD on a such hardware.
I used bsd.rd to install it on a usb flash drive. After reboot I choose 
to boot from the usb drive.

Bootloader can't load bsd kernel and the laptop restarts without error.
If I change SATA mode in BIOS from AHCI to IDE I can boot from the usb 
drive.


# dmesg with SATA in IDE mode

OpenBSD 5.6-current (GENERIC.MP) #407: Thu Oct  9 00:51:33 MDT 2014
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4119818240 (3928MB)
avail mem = 4001447936 (3816MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xb7e7e000 (31 entries)
bios0: vendor Hewlett-Packard version 68IRF Ver. F.01 date 03/29/2013
bios0: Hewlett-Packard HP ProBook 450 G0
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC MCFG ASF! SSDT SSDT SSDT FPDT BGRT 
SSDT SSDT
acpi0: wakeup devices LANC(S5) EHC1(S3) EHC2(S3) XHC_(S3) PCIB(S5) 
RP02(S4) ECF0(S4) RP03(S4) RP04(S5) WNIC(S5) RP06(S5) NIC_(S5) RP07(S4) 
RP08(S4) HST1(S5)

acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i3-3120M CPU @ 2.50GHz, 2494.64 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,F16C,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS

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 99MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i3-3120M CPU @ 2.50GHz, 2494.34 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,F16C,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS

cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: Intel(R) Core(TM) i3-3120M CPU @ 2.50GHz, 2494.34 MHz
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,F16C,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS

cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i3-3120M CPU @ 2.50GHz, 2494.34 MHz
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,AVX,F16C,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS

cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 0 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpiprt0 at acpi0: bus -1 (PEGP)
acpiprt1 at acpi0: bus -1 (PCIB)
acpiprt2 at acpi0: bus 1 (RP01)
acpiprt3 at acpi0: bus 2 (RP03)
acpiprt4 at acpi0: bus 3 (RP04)
acpiprt5 at acpi0: bus 4 (RP06)
acpiprt6 at acpi0: bus 0 (PCI0)
acpiec0 at acpi0
acpicpu0 at acpi0: C2, C1, PSS
acpicpu1 at acpi0: C2, C1, PSS
acpicpu2 at acpi0: C2, C1, PSS
acpicpu3 at acpi0: C2, C1, PSS
acpipwrres0 at acpi0: APPR, resource for HDEF
acpipwrres1 at acpi0: COMP, resource for COM1
acpipwrres2 at acpi0: LPP_, resource for LPT0
acpitz0 at acpi0: critical temperature is 128 degC
acpitz1 at acpi0: critical temperature is 128 degC
acpitz2 at acpi0: critical temperature is 128 degC
acpitz3 at acpi0: critical temperature is 128 degC
acpitz4 at acpi0: critical temperature is 128 degC
acpitz5 at acpi0: critical temperature is 128 degC
acpitz6 at acpi0: critical temperature is 128 degC
acpitz7 at acpi0: critical temperature is 128 degC
acpibat0 at acpi0: BAT0 model Primary serial 00190 2013/05/22 type 
LIon oem Hewlett-Packard

acpibat1 at acpi0: BAT1 not present
acpiac0 at acpi0: AC unit online
acpibtn0 at acpi0: SLPB
acpibtn1 at acpi0: LID_
acpivideo0 at acpi0: GFX0
acpivout0 at acpivideo0: DD02
cpu0: Enhanced SpeedStep 2494 MHz: speeds: 2500, 2400, 2300, 2200, 2100, 
2000, 1900, 1800, 1700, 1600, 1500, 1400, 1300, 1200 MHz

pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 Intel Core 3G Host rev 0x09
vga1 at pci0 dev 2 function 0 Intel HD Graphics 4000 rev 0x09
intagp at vga1 not configured
inteldrm0 at vga1
drm0 at inteldrm0
drm: Memory usable by graphics device = 2048M
inteldrm0: 1366x768
wsdisplay0 at vga1 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
Intel 7 

Re: CPU power consumption on thinkpad x201 on openbsd current

[Johan Svensson]

On 06/05/14 00:53, STeve Andre' wrote:

On 06/04/14 17:08, Johan Svensson wrote:
I'm trying to migrate from Linux to Openbsd on my laptop (thinkpad 
x201).


The first problem that i came across was that the Cpu fanspeed was 
running constantly at 3500RPM.
After the acpithinkpad.c patch from jcs (and i modified to make it 
work on the openbsd-current(link: 
http://exclude.se/patch/jcs_mod_by_js.diff)


Another thing that i noticed is that the battery lifetime is really bad.
In Linux i get around ~5,5 hours.
In OpenBSD i get around 2 hours.

when i ran : sysctl hw.sensors | grep -i consumption.
the output of the cpu was 6W.

in Linux it's around 1,5W.

with: apmd -C and apmd -L it's the same.
dmesg: http://exclude.se/openbsd/dmesg.txt

Is there anyway to fix this?

Regards
Johan Svensson



Take a look at hw.setperf in sysctl.  I think you are running at the
maximum cpu speed?  On my 2.8GHz W500 I can run at 800, 1600,
2133 and 2801.  800MHz makes a huge difference.  You have to
try different values for setperf to see what happens.  sysctl will
also tell you the speed in hw.cpuspeed.

--STeve Andre'

This my output from sysctl and apm when running on the lowest clockspeed:
# sysctl hw | grep -iE cpuspeed|setperf|fan|consumption
hw.sensors.acpithinkpad0.fan0=1959 RPM
hw.sensors.itherm0.power0=6.00 W (CPU power consumption)
hw.cpuspeed=1199
hw.setperf=0
# apm
Battery state: high, 70% remaining, 111 minutes life estimate
A/C adapter state: not connected
Performance adjustment mode: manual (1199 MHz)


This is the output when i use apm -H:
# sysctl hw | grep -iE cpuspeed|setperf|fan|consumption
hw.sensors.acpithinkpad0.fan0=1972 RPM
hw.sensors.itherm0.power0=6.00 W (CPU power consumption)
hw.cpuspeed=2666
hw.setperf=100
# apm
Battery state: high, 68% remaining, 107 minutes life estimate
A/C adapter state: not connected
Performance adjustment mode: manual (2666 MHz)

The energy consumption is the same which is odd.

--Johan

Re: CPU power consumption on thinkpad x201 on openbsd current

[STeve Andre']

On 06/05/14 04:53, Johan Svensson wrote:


On 06/05/14 00:53, STeve Andre' wrote:

On 06/04/14 17:08, Johan Svensson wrote:
I'm trying to migrate from Linux to Openbsd on my laptop (thinkpad 
x201).


The first problem that i came across was that the Cpu fanspeed was 
running constantly at 3500RPM.
After the acpithinkpad.c patch from jcs (and i modified to make it 
work on the openbsd-current(link: 
http://exclude.se/patch/jcs_mod_by_js.diff)


Another thing that i noticed is that the battery lifetime is really 
bad.

In Linux i get around ~5,5 hours.
In OpenBSD i get around 2 hours.

when i ran : sysctl hw.sensors | grep -i consumption.
the output of the cpu was 6W.

in Linux it's around 1,5W.

with: apmd -C and apmd -L it's the same.
dmesg: http://exclude.se/openbsd/dmesg.txt

Is there anyway to fix this?

Regards
Johan Svensson



Take a look at hw.setperf in sysctl.  I think you are running at the
maximum cpu speed?  On my 2.8GHz W500 I can run at 800, 1600,
2133 and 2801.  800MHz makes a huge difference.  You have to
try different values for setperf to see what happens.  sysctl will
also tell you the speed in hw.cpuspeed.

--STeve Andre'

This my output from sysctl and apm when running on the lowest clockspeed:
# sysctl hw | grep -iE cpuspeed|setperf|fan|consumption
hw.sensors.acpithinkpad0.fan0=1959 RPM
hw.sensors.itherm0.power0=6.00 W (CPU power consumption)
hw.cpuspeed=1199
hw.setperf=0
# apm
Battery state: high, 70% remaining, 111 minutes life estimate
A/C adapter state: not connected
Performance adjustment mode: manual (1199 MHz)


This is the output when i use apm -H:
# sysctl hw | grep -iE cpuspeed|setperf|fan|consumption
hw.sensors.acpithinkpad0.fan0=1972 RPM
hw.sensors.itherm0.power0=6.00 W (CPU power consumption)
hw.cpuspeed=2666
hw.setperf=100
# apm
Battery state: high, 68% remaining, 107 minutes life estimate
A/C adapter state: not connected
Performance adjustment mode: manual (2666 MHz)

The energy consumption is the same which is odd.

--Johan


Hmmm.  Smells like a bug, to me.  But by changing hw.setperf your
self you should be able to go to other speeds(?).  And of course, the
real test is to see if you get longer life at setperf 0.

--STeve Andre'

Re: CPU power consumption on thinkpad x201 on openbsd current

[David Coppa]

On Thu, Jun 5, 2014 at 10:53 AM, Johan Svensson open...@exclude.se wrote:

 This my output from sysctl and apm when running on the lowest clockspeed:
 # sysctl hw | grep -iE cpuspeed|setperf|fan|consumption
 hw.sensors.acpithinkpad0.fan0=1959 RPM
 hw.sensors.itherm0.power0=6.00 W (CPU power consumption)
 hw.cpuspeed=1199
 hw.setperf=0
 # apm
 Battery state: high, 70% remaining, 111 minutes life estimate
 A/C adapter state: not connected
 Performance adjustment mode: manual (1199 MHz)


 This is the output when i use apm -H:
 # sysctl hw | grep -iE cpuspeed|setperf|fan|consumption
 hw.sensors.acpithinkpad0.fan0=1972 RPM
 hw.sensors.itherm0.power0=6.00 W (CPU power consumption)
 hw.cpuspeed=2666
 hw.setperf=100
 # apm
 Battery state: high, 68% remaining, 107 minutes life estimate
 A/C adapter state: not connected
 Performance adjustment mode: manual (2666 MHz)

 The energy consumption is the same which is odd.

Are you running with the latest bios (1.40-1.15) from Lenovo?

Re: CPU power consumption on thinkpad x201 on openbsd current

[Johan Svensson]

On 2014-06-05 11:09, David Coppa wrote:

On Thu, Jun 5, 2014 at 10:53 AM, Johan Svensson open...@exclude.se wrote:


This my output from sysctl and apm when running on the lowest clockspeed:
# sysctl hw | grep -iE cpuspeed|setperf|fan|consumption
hw.sensors.acpithinkpad0.fan0=1959 RPM
hw.sensors.itherm0.power0=6.00 W (CPU power consumption)
hw.cpuspeed=1199
hw.setperf=0
# apm
Battery state: high, 70% remaining, 111 minutes life estimate
A/C adapter state: not connected
Performance adjustment mode: manual (1199 MHz)


This is the output when i use apm -H:
# sysctl hw | grep -iE cpuspeed|setperf|fan|consumption
hw.sensors.acpithinkpad0.fan0=1972 RPM
hw.sensors.itherm0.power0=6.00 W (CPU power consumption)
hw.cpuspeed=2666
hw.setperf=100
# apm
Battery state: high, 68% remaining, 107 minutes life estimate
A/C adapter state: not connected
Performance adjustment mode: manual (2666 MHz)

The energy consumption is the same which is odd.

Are you running with the latest bios (1.40-1.15) from Lenovo?

Yes it is the latest bios.


Hmmm.  Smells like a bug, to me.  But by changing hw.setperf your
self you should be able to go to other speeds(?).  And of course, the
real test is to see if you get longer life at setperf 0.

--STeve Andre'

# sysctl hw | grep -iE cpuspeed|setperf|fan|consumption  apm
hw.sensors.acpithinkpad0.fan0=1965 RPM
hw.sensors.itherm0.power0=6.00 W (CPU power consumption)
hw.cpuspeed=1199
hw.setperf=0
Battery state: high, 57% remaining, 91 minutes life estimate
A/C adapter state: not connected
Performance adjustment mode: manual (1199 MHz)
#

It seems like that's the same output. If the processor throttles down it 
should also consume less energy, but it says 6W all the time though.

Re: CPU power consumption on thinkpad x201 on openbsd current

[Mike Larkin]

On Thu, Jun 05, 2014 at 10:53:38AM +0200, Johan Svensson wrote:
 On 06/05/14 00:53, STeve Andre' wrote:
 On 06/04/14 17:08, Johan Svensson wrote:
 I'm trying to migrate from Linux to Openbsd on my laptop
 (thinkpad x201).
 
 The first problem that i came across was that the Cpu fanspeed
 was running constantly at 3500RPM.
 After the acpithinkpad.c patch from jcs (and i modified to make
 it work on the openbsd-current(link:
 http://exclude.se/patch/jcs_mod_by_js.diff)
 
 Another thing that i noticed is that the battery lifetime is really bad.
 In Linux i get around ~5,5 hours.
 In OpenBSD i get around 2 hours.
 
 when i ran : sysctl hw.sensors | grep -i consumption.
 the output of the cpu was 6W.
 
 in Linux it's around 1,5W.
 
 with: apmd -C and apmd -L it's the same.
 dmesg: http://exclude.se/openbsd/dmesg.txt
 
 Is there anyway to fix this?
 
 Regards
 Johan Svensson
 
 
 Take a look at hw.setperf in sysctl.  I think you are running at the
 maximum cpu speed?  On my 2.8GHz W500 I can run at 800, 1600,
 2133 and 2801.  800MHz makes a huge difference.  You have to
 try different values for setperf to see what happens.  sysctl will
 also tell you the speed in hw.cpuspeed.
 
 --STeve Andre'
 This my output from sysctl and apm when running on the lowest clockspeed:
 # sysctl hw | grep -iE cpuspeed|setperf|fan|consumption
 hw.sensors.acpithinkpad0.fan0=1959 RPM
 hw.sensors.itherm0.power0=6.00 W (CPU power consumption)
 hw.cpuspeed=1199
 hw.setperf=0
 # apm
 Battery state: high, 70% remaining, 111 minutes life estimate
 A/C adapter state: not connected
 Performance adjustment mode: manual (1199 MHz)
 
 
 This is the output when i use apm -H:
 # sysctl hw | grep -iE cpuspeed|setperf|fan|consumption
 hw.sensors.acpithinkpad0.fan0=1972 RPM
 hw.sensors.itherm0.power0=6.00 W (CPU power consumption)
 hw.cpuspeed=2666
 hw.setperf=100
 # apm
 Battery state: high, 68% remaining, 107 minutes life estimate
 A/C adapter state: not connected
 Performance adjustment mode: manual (2666 MHz)
 
 The energy consumption is the same which is odd.
 
 --Johan
 

This may be a bug in itherm(4), I'll take a look.

Re: CPU power consumption on thinkpad x201 on openbsd current

[Johan Svensson]

On 2014-06-05 20:43, Mike Larkin wrote:

On Thu, Jun 05, 2014 at 10:53:38AM +0200, Johan Svensson wrote:

On 06/05/14 00:53, STeve Andre' wrote:

On 06/04/14 17:08, Johan Svensson wrote:

I'm trying to migrate from Linux to Openbsd on my laptop
(thinkpad x201).

The first problem that i came across was that the Cpu fanspeed
was running constantly at 3500RPM.
After the acpithinkpad.c patch from jcs (and i modified to make
it work on the openbsd-current(link:
http://exclude.se/patch/jcs_mod_by_js.diff)

Another thing that i noticed is that the battery lifetime is really bad.
In Linux i get around ~5,5 hours.
In OpenBSD i get around 2 hours.

when i ran : sysctl hw.sensors | grep -i consumption.
the output of the cpu was 6W.

in Linux it's around 1,5W.

with: apmd -C and apmd -L it's the same.
dmesg: http://exclude.se/openbsd/dmesg.txt

Is there anyway to fix this?

Regards
Johan Svensson



Take a look at hw.setperf in sysctl.  I think you are running at the
maximum cpu speed?  On my 2.8GHz W500 I can run at 800, 1600,
2133 and 2801.  800MHz makes a huge difference.  You have to
try different values for setperf to see what happens.  sysctl will
also tell you the speed in hw.cpuspeed.

--STeve Andre'

This my output from sysctl and apm when running on the lowest clockspeed:
# sysctl hw | grep -iE cpuspeed|setperf|fan|consumption
hw.sensors.acpithinkpad0.fan0=1959 RPM
hw.sensors.itherm0.power0=6.00 W (CPU power consumption)
hw.cpuspeed=1199
hw.setperf=0
# apm
Battery state: high, 70% remaining, 111 minutes life estimate
A/C adapter state: not connected
Performance adjustment mode: manual (1199 MHz)


This is the output when i use apm -H:
# sysctl hw | grep -iE cpuspeed|setperf|fan|consumption
hw.sensors.acpithinkpad0.fan0=1972 RPM
hw.sensors.itherm0.power0=6.00 W (CPU power consumption)
hw.cpuspeed=2666
hw.setperf=100
# apm
Battery state: high, 68% remaining, 107 minutes life estimate
A/C adapter state: not connected
Performance adjustment mode: manual (2666 MHz)

The energy consumption is the same which is odd.

--Johan


This may be a bug in itherm(4), I'll take a look.


Tell me if you find something, i'll gladly help if I could do something.

/J

CPU power consumption on thinkpad x201 on openbsd current

[Johan Svensson]

I'm trying to migrate from Linux to Openbsd on my laptop (thinkpad x201).

The first problem that i came across was that the Cpu fanspeed was 
running constantly at 3500RPM.
After the acpithinkpad.c patch from jcs (and i modified to make it work 
on the openbsd-current(link: http://exclude.se/patch/jcs_mod_by_js.diff)


Another thing that i noticed is that the battery lifetime is really bad.
In Linux i get around ~5,5 hours.
In OpenBSD i get around 2 hours.

when i ran : sysctl hw.sensors | grep -i consumption.
the output of the cpu was 6W.

in Linux it's around 1,5W.

with: apmd -C and apmd -L it's the same.
dmesg: http://exclude.se/openbsd/dmesg.txt

Is there anyway to fix this?

Regards
Johan Svensson

Re: CPU power consumption on thinkpad x201 on openbsd current

[STeve Andre']

On 06/04/14 17:08, Johan Svensson wrote:

I'm trying to migrate from Linux to Openbsd on my laptop (thinkpad x201).

The first problem that i came across was that the Cpu fanspeed was 
running constantly at 3500RPM.
After the acpithinkpad.c patch from jcs (and i modified to make it 
work on the openbsd-current(link: 
http://exclude.se/patch/jcs_mod_by_js.diff)


Another thing that i noticed is that the battery lifetime is really bad.
In Linux i get around ~5,5 hours.
In OpenBSD i get around 2 hours.

when i ran : sysctl hw.sensors | grep -i consumption.
the output of the cpu was 6W.

in Linux it's around 1,5W.

with: apmd -C and apmd -L it's the same.
dmesg: http://exclude.se/openbsd/dmesg.txt

Is there anyway to fix this?

Regards
Johan Svensson



Take a look at hw.setperf in sysctl.  I think you are running at the
maximum cpu speed?  On my 2.8GHz W500 I can run at 800, 1600,
2133 and 2801.  800MHz makes a huge difference.  You have to
try different values for setperf to see what happens.  sysctl will
also tell you the speed in hw.cpuspeed.

--STeve Andre'

Change default audiodevice in OpenBSD-current

[Johan Svensson]

I am trying to change my default output device from my builtin soundcard 
to an usb soundcard which is an output only device. I have tried:


# audioctl -f /dev/audio1
audioctl: /dev/audio1: Device not configured

I think there should be some controller that you configuring the audio 
device. But i manually tried to change the symlinks in the dev directory:

# ls -la * | grep -E mixer|audio
lrwxr-xr-x  1 root   wheel6 Jun  3 16:58 audio - audio1
crw-rw-rw-  1 root   wheel  42, 128 Jun  3 17:01 audio0
crw-rw-rw-  1 root   wheel  42, 129 May 28 19:07 audio1
crw-rw-rw-  1 root   wheel  42, 130 May 28 19:07 audio2
lrwxr-xr-x  1 root   wheel9 Jun  3 16:58 audioctl - audioctl1
crw-rw-rw-  1 root   wheel  42, 192 May 28 19:07 audioctl0
crw-rw-rw-  1 root   wheel  42, 193 May 28 19:07 audioctl1
crw-rw-rw-  1 root   wheel  42, 194 May 28 19:07 audioctl2
lrwxr-xr-x  1 root   wheel6 Jun  3 16:58 mixer - mixer1
crw-rw-rw-  1 root   wheel  42,  16 May 28 19:07 mixer0
crw-rw-rw-  1 root   wheel  42,  17 May 28 19:07 mixer1
crw-rw-rw-  1 root   wheel  42,  18 May 28 19:07 mixer2

But it is still defaulting to my builtin soundcard. How can i change the 
default sounddevice from audio0 to audio1?


/Regards
Johan Svensson

DMESG:
dmesg | grep audio
audio0 at azalia0
audio0 at azalia0
audio0 at azalia0
audio0 at azalia0
uaudio0 at uhub2 port 1 configuration 1 interface 1 NuForce, Inc. 
NuForce \M-5DAC 2 rev 1.10/0.01 addr 3

uaudio0: ignored setting with type 8193 format
uaudio0: audio rev 1.00, 2 mixer controls
audio1 at uaudio0

Re: Change default audiodevice in OpenBSD-current

[Remco]

Johan Svensson wrote:

 I am trying to change my default output device from my builtin soundcard
 to an usb soundcard which is an output only device. I have tried:
 
 # audioctl -f /dev/audio1
 audioctl: /dev/audio1: Device not configured
 

It seems this device does not exist from the kernel's point of view.
(there's also /dev/audioctl1, but using that probably doesn't make a 
difference)

 I think there should be some controller that you configuring the audio
 device. But i manually tried to change the symlinks in the dev directory:
 # ls -la * | grep -E mixer|audio
 lrwxr-xr-x  1 root   wheel6 Jun  3 16:58 audio - audio1
 crw-rw-rw-  1 root   wheel  42, 128 Jun  3 17:01 audio0
 crw-rw-rw-  1 root   wheel  42, 129 May 28 19:07 audio1
 crw-rw-rw-  1 root   wheel  42, 130 May 28 19:07 audio2
 lrwxr-xr-x  1 root   wheel9 Jun  3 16:58 audioctl - audioctl1
 crw-rw-rw-  1 root   wheel  42, 192 May 28 19:07 audioctl0
 crw-rw-rw-  1 root   wheel  42, 193 May 28 19:07 audioctl1
 crw-rw-rw-  1 root   wheel  42, 194 May 28 19:07 audioctl2
 lrwxr-xr-x  1 root   wheel6 Jun  3 16:58 mixer - mixer1
 crw-rw-rw-  1 root   wheel  42,  16 May 28 19:07 mixer0
 crw-rw-rw-  1 root   wheel  42,  17 May 28 19:07 mixer1
 crw-rw-rw-  1 root   wheel  42,  18 May 28 19:07 mixer2
 
 But it is still defaulting to my builtin soundcard. How can i change the
 default sounddevice from audio0 to audio1?
 

I think using sndiod(1) is the answer, in the most simplistic form, 
something like this in your rc.conf.local(8) should suffice:
sndiod_flags=-f rsnd/0 -s onboard -f rsnd/1 -s default

This should make your audio0 device available as snd/0.onboard and your 
audio1 device as the default sound device. (Both should be available as 
snd/0 and snd/1 respectively as well IIRC).

 /Regards
 Johan Svensson
 
 DMESG:
 dmesg | grep audio
 audio0 at azalia0
 audio0 at azalia0
 audio0 at azalia0
 audio0 at azalia0
 uaudio0 at uhub2 port 1 configuration 1 interface 1 NuForce, Inc.
 NuForce \M-5DAC 2 rev 1.10/0.01 addr 3
 uaudio0: ignored setting with type 8193 format

If I'm correct format 8193 (== 0x2001) means IEC1937 AC-3.
This is an encoded format. AFAICT the uaudio driver only supports plain PCM 
formats. (unencoded audio samples)

Do you know if your device only supports AC-3 inputs or can it also handle 
PCM signals ?

(running 'lsusb -v', from the usbutils package, on the device should give a 
good clue what your device supports)

 uaudio0: audio rev 1.00, 2 mixer controls
 audio1 at uaudio0

Re: Change default audiodevice in OpenBSD-current

[Johan Svensson]

On 06/03/14 18:22, Remco wrote:

Johan Svensson wrote:


I am trying to change my default output device from my builtin soundcard
to an usb soundcard which is an output only device. I have tried:

# audioctl -f /dev/audio1
audioctl: /dev/audio1: Device not configured


It seems this device does not exist from the kernel's point of view.
(there's also /dev/audioctl1, but using that probably doesn't make a
difference)


I think there should be some controller that you configuring the audio
device. But i manually tried to change the symlinks in the dev directory:
# ls -la * | grep -E mixer|audio
lrwxr-xr-x  1 root   wheel6 Jun  3 16:58 audio - audio1
crw-rw-rw-  1 root   wheel  42, 128 Jun  3 17:01 audio0
crw-rw-rw-  1 root   wheel  42, 129 May 28 19:07 audio1
crw-rw-rw-  1 root   wheel  42, 130 May 28 19:07 audio2
lrwxr-xr-x  1 root   wheel9 Jun  3 16:58 audioctl - audioctl1
crw-rw-rw-  1 root   wheel  42, 192 May 28 19:07 audioctl0
crw-rw-rw-  1 root   wheel  42, 193 May 28 19:07 audioctl1
crw-rw-rw-  1 root   wheel  42, 194 May 28 19:07 audioctl2
lrwxr-xr-x  1 root   wheel6 Jun  3 16:58 mixer - mixer1
crw-rw-rw-  1 root   wheel  42,  16 May 28 19:07 mixer0
crw-rw-rw-  1 root   wheel  42,  17 May 28 19:07 mixer1
crw-rw-rw-  1 root   wheel  42,  18 May 28 19:07 mixer2

But it is still defaulting to my builtin soundcard. How can i change the
default sounddevice from audio0 to audio1?


I think using sndiod(1) is the answer, in the most simplistic form,
something like this in your rc.conf.local(8) should suffice:
sndiod_flags=-f rsnd/0 -s onboard -f rsnd/1 -s default

This should make your audio0 device available as snd/0.onboard and your
audio1 device as the default sound device. (Both should be available as
snd/0 and snd/1 respectively as well IIRC).


/Regards
Johan Svensson

DMESG:
dmesg | grep audio
audio0 at azalia0
audio0 at azalia0
audio0 at azalia0
audio0 at azalia0
uaudio0 at uhub2 port 1 configuration 1 interface 1 NuForce, Inc.
NuForce \M-5DAC 2 rev 1.10/0.01 addr 3
uaudio0: ignored setting with type 8193 format

If I'm correct format 8193 (== 0x2001) means IEC1937 AC-3.
This is an encoded format. AFAICT the uaudio driver only supports plain PCM
formats. (unencoded audio samples)

Do you know if your device only supports AC-3 inputs or can it also handle
PCM signals ?

(running 'lsusb -v', from the usbutils package, on the device should give a
good clue what your device supports)


uaudio0: audio rev 1.00, 2 mixer controls
audio1 at uaudio0

I can successfully run this command:
if i use audioctl1 instead of audio1 it works, i dont know why tho.

# audioctl -f /dev/audioctl1
name=USB audio
version=
config=uaudio
encodings=slinear_le:16:2:1,slinear_le:24:3:1
properties=independent
full_duplex=0
fullduplex=0
blocksize=8816
hiwat=7
lowat=5
output_muted=0
monitor_gain=0
mode=
play.rate=44100
play.channels=2
play.precision=16
play.bps=2
play.msb=1
play.encoding=slinear_le
play.gain=127
play.balance=32
play.port=0x0
play.avail_ports=0x0
play.seek=0
play.samples=0
play.eof=0
play.pause=0
play.error=0
play.waiting=0
play.open=0
play.active=0
play.buffer_size=65536
play.block_size=8816
play.errors=0
record.rate=44100
record.channels=2
record.precision=16
record.bps=2
record.msb=1
record.encoding=slinear_le
record.gain=127
record.balance=32
record.port=0x0
record.avail_ports=0x0
record.seek=0
record.samples=0
record.eof=0
record.pause=0
record.error=0
record.waiting=0
record.open=0
record.active=0
record.buffer_size=65536
record.block_size=8816
record.errors=0

here is the output from the device in lsusb:

Bus 000 Device 003: ID 1852:db96 GYROCOM CC Co., LTD
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.10
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 8
  idVendor   0x1852 GYROCOM CC Co., LTD
  idProduct  0xdb96
  bcdDevice0.01
  iManufacturer   1 NuForce, Inc.
  iProduct2 NuForce µDAC 2
  iSerial 0
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength  251
bNumInterfaces  3
bConfigurationValue 1
iConfiguration  0
bmAttributes 0x80
  (Bus Powered)
MaxPower  500mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass 3 Human Interface Device
  bInterfaceSubClass  0 No Subclass
  bInterfaceProtocol  0 None
  iInterface  0
HID Device Descriptor:
  bLength 9
  bDescriptorType33
  bcdHID   1.00
  bCountryCode  

Re: Change default audiodevice in OpenBSD-current

[Johan Svensson]

On 06/03/14 18:22, Remco wrote:

Johan Svensson wrote:


I am trying to change my default output device from my builtin soundcard
to an usb soundcard which is an output only device. I have tried:

# audioctl -f /dev/audio1
audioctl: /dev/audio1: Device not configured


It seems this device does not exist from the kernel's point of view.
(there's also /dev/audioctl1, but using that probably doesn't make a
difference)


I think there should be some controller that you configuring the audio
device. But i manually tried to change the symlinks in the dev directory:
# ls -la * | grep -E mixer|audio
lrwxr-xr-x  1 root   wheel6 Jun  3 16:58 audio - audio1
crw-rw-rw-  1 root   wheel  42, 128 Jun  3 17:01 audio0
crw-rw-rw-  1 root   wheel  42, 129 May 28 19:07 audio1
crw-rw-rw-  1 root   wheel  42, 130 May 28 19:07 audio2
lrwxr-xr-x  1 root   wheel9 Jun  3 16:58 audioctl - audioctl1
crw-rw-rw-  1 root   wheel  42, 192 May 28 19:07 audioctl0
crw-rw-rw-  1 root   wheel  42, 193 May 28 19:07 audioctl1
crw-rw-rw-  1 root   wheel  42, 194 May 28 19:07 audioctl2
lrwxr-xr-x  1 root   wheel6 Jun  3 16:58 mixer - mixer1
crw-rw-rw-  1 root   wheel  42,  16 May 28 19:07 mixer0
crw-rw-rw-  1 root   wheel  42,  17 May 28 19:07 mixer1
crw-rw-rw-  1 root   wheel  42,  18 May 28 19:07 mixer2

But it is still defaulting to my builtin soundcard. How can i change the
default sounddevice from audio0 to audio1?


I think using sndiod(1) is the answer, in the most simplistic form,
something like this in your rc.conf.local(8) should suffice:
sndiod_flags=-f rsnd/0 -s onboard -f rsnd/1 -s default

This should make your audio0 device available as snd/0.onboard and your
audio1 device as the default sound device. (Both should be available as
snd/0 and snd/1 respectively as well IIRC).


/Regards
Johan Svensson

DMESG:
dmesg | grep audio
audio0 at azalia0
audio0 at azalia0
audio0 at azalia0
audio0 at azalia0
uaudio0 at uhub2 port 1 configuration 1 interface 1 NuForce, Inc.
NuForce \M-5DAC 2 rev 1.10/0.01 addr 3
uaudio0: ignored setting with type 8193 format

If I'm correct format 8193 (== 0x2001) means IEC1937 AC-3.
This is an encoded format. AFAICT the uaudio driver only supports plain PCM
formats. (unencoded audio samples)

Do you know if your device only supports AC-3 inputs or can it also handle
PCM signals ?

(running 'lsusb -v', from the usbutils package, on the device should give a
good clue what your device supports)


uaudio0: audio rev 1.00, 2 mixer controls
audio1 at uaudio0
I have updated my rc.conf.local line with sndiod_flags=-f rsnd/0 -s 
onboard -f rsnd/1 -s default

but the default output device is still builtin sounddevice.

Re: Change default audiodevice in OpenBSD-current

[Alexandre Ratchov]

On Tue, Jun 03, 2014 at 06:22:01PM +0200, Remco wrote:
 Johan Svensson wrote:
 
  I am trying to change my default output device from my builtin soundcard
  to an usb soundcard which is an output only device. I have tried:
  
  # audioctl -f /dev/audio1
  audioctl: /dev/audio1: Device not configured
  
 
 It seems this device does not exist from the kernel's point of view.
 (there's also /dev/audioctl1, but using that probably doesn't make a 
 difference)
 
  I think there should be some controller that you configuring the audio
  device. But i manually tried to change the symlinks in the dev directory:
  # ls -la * | grep -E mixer|audio
  lrwxr-xr-x  1 root   wheel6 Jun  3 16:58 audio - audio1
  crw-rw-rw-  1 root   wheel  42, 128 Jun  3 17:01 audio0
  crw-rw-rw-  1 root   wheel  42, 129 May 28 19:07 audio1
  crw-rw-rw-  1 root   wheel  42, 130 May 28 19:07 audio2
  lrwxr-xr-x  1 root   wheel9 Jun  3 16:58 audioctl - audioctl1
  crw-rw-rw-  1 root   wheel  42, 192 May 28 19:07 audioctl0
  crw-rw-rw-  1 root   wheel  42, 193 May 28 19:07 audioctl1
  crw-rw-rw-  1 root   wheel  42, 194 May 28 19:07 audioctl2
  lrwxr-xr-x  1 root   wheel6 Jun  3 16:58 mixer - mixer1
  crw-rw-rw-  1 root   wheel  42,  16 May 28 19:07 mixer0
  crw-rw-rw-  1 root   wheel  42,  17 May 28 19:07 mixer1
  crw-rw-rw-  1 root   wheel  42,  18 May 28 19:07 mixer2
  
  But it is still defaulting to my builtin soundcard. How can i change the
  default sounddevice from audio0 to audio1?
  
 
 I think using sndiod(1) is the answer, in the most simplistic form, 
 something like this in your rc.conf.local(8) should suffice:
 sndiod_flags=-f rsnd/0 -s onboard -f rsnd/1 -s default
 
 This should make your audio0 device available as snd/0.onboard and your 
 audio1 device as the default sound device. (Both should be available as 
 snd/0 and snd/1 respectively as well IIRC).
 

This changed a while ago: the device number in snd/N corrsponds
to the number of the -f option of sndiod. And snd/0 is always the
default. So I'd suggest:

sndiod_flags=-f rsnd/1 -f rsnd/0

This will kind of exchange the first two devices. I.e. this
exposes snd/0 as sub-device of rsnd/1 and snd/1 as sub-device
of rsnd/0.

-- Alexandre

Re: Change default audiodevice in OpenBSD-current

[Alexandre Ratchov]

On Tue, Jun 03, 2014 at 07:25:25PM +0200, Alexandre Ratchov wrote:
 
 sndiod_flags=-f rsnd/1 -f rsnd/0
 
 This will kind of exchange the first two devices. I.e. this
 exposes snd/0 as sub-device of rsnd/1 and snd/1 as sub-device
 of rsnd/0.
 

If device renumbering seems confusing/ugly, another option would be
to keep the kernel order:

sndiod_flags=-f rsnd/0 -f rsnd/1

then export AUDIODEVICE=snd/1 in your ~/.profile or equivalent

-- Alexandre

Re: Change default audiodevice in OpenBSD-current

[Johan Svensson]

On 06/03/14 19:33, Alexandre Ratchov wrote:

On Tue, Jun 03, 2014 at 07:25:25PM +0200, Alexandre Ratchov wrote:

sndiod_flags=-f rsnd/1 -f rsnd/0

This will kind of exchange the first two devices. I.e. this
exposes snd/0 as sub-device of rsnd/1 and snd/1 as sub-device
of rsnd/0.


If device renumbering seems confusing/ugly, another option would be
to keep the kernel order:

sndiod_flags=-f rsnd/0 -f rsnd/1

then export AUDIODEVICE=snd/1 in your ~/.profile or equivalent

-- Alexandre

grep sndiod /etc/rc.conf.local
#sndiod_flags=-f rsnd/0 -s onboard -f rsnd/1 -s default
sndiod_flags=-f rsnd/1 -f rsnd/0
#sndiod_flags=-f rsnd/0 -f rsnd/1

I've tried all three of the settings, the first and the last defaults to 
builtin soundcard. But if I use the second configuration setting this 
shows up in dmesg:


ehci0: Error opening low/full speed isoc endpoint.
A low/full speed device is attached to a USB2 hub, and transaction 
translations are not yet supported.

Reattach the device to the root hub instead.
uaudio_chan_open: error creating pipe: err=INVAL endpt=0x03


I dont know if that helps.

//Johan

Re: Change default audiodevice in OpenBSD-current

[Alexandre Ratchov]

On Tue, Jun 03, 2014 at 07:59:49PM +0200, Johan Svensson wrote:
 On 06/03/14 19:33, Alexandre Ratchov wrote:
 On Tue, Jun 03, 2014 at 07:25:25PM +0200, Alexandre Ratchov wrote:
 sndiod_flags=-f rsnd/1 -f rsnd/0
 
 This will kind of exchange the first two devices. I.e. this
 exposes snd/0 as sub-device of rsnd/1 and snd/1 as sub-device
 of rsnd/0.
 
 If device renumbering seems confusing/ugly, another option would be
 to keep the kernel order:
 
 sndiod_flags=-f rsnd/0 -f rsnd/1
 
 then export AUDIODEVICE=snd/1 in your ~/.profile or equivalent
 
 -- Alexandre
 grep sndiod /etc/rc.conf.local
 #sndiod_flags=-f rsnd/0 -s onboard -f rsnd/1 -s default
 sndiod_flags=-f rsnd/1 -f rsnd/0
 #sndiod_flags=-f rsnd/0 -f rsnd/1
 
 I've tried all three of the settings, the first and the last defaults to
 builtin soundcard. But if I use the second configuration setting this shows
 up in dmesg:
 
 ehci0: Error opening low/full speed isoc endpoint.
 A low/full speed device is attached to a USB2 hub, and transaction
 translations are not yet supported.
 Reattach the device to the root hub instead.
 uaudio_chan_open: error creating pipe: err=INVAL endpt=0x03
 

the usb stack is incomplete and doesn't support rate matching hubs
yet; sorry your sound card can't work on this machine yet.

recently discussed here:

http://comments.gmane.org/gmane.os.openbsd.misc/212991

-- Alexandre

Re: Change default audiodevice in OpenBSD-current

[Johan Svensson]

On 06/03/14 20:08, Alexandre Ratchov wrote:

On Tue, Jun 03, 2014 at 07:59:49PM +0200, Johan Svensson wrote:

On 06/03/14 19:33, Alexandre Ratchov wrote:

On Tue, Jun 03, 2014 at 07:25:25PM +0200, Alexandre Ratchov wrote:

sndiod_flags=-f rsnd/1 -f rsnd/0

This will kind of exchange the first two devices. I.e. this
exposes snd/0 as sub-device of rsnd/1 and snd/1 as sub-device
of rsnd/0.


If device renumbering seems confusing/ugly, another option would be
to keep the kernel order:

sndiod_flags=-f rsnd/0 -f rsnd/1

then export AUDIODEVICE=snd/1 in your ~/.profile or equivalent

-- Alexandre

grep sndiod /etc/rc.conf.local
#sndiod_flags=-f rsnd/0 -s onboard -f rsnd/1 -s default
sndiod_flags=-f rsnd/1 -f rsnd/0
#sndiod_flags=-f rsnd/0 -f rsnd/1

I've tried all three of the settings, the first and the last defaults to
builtin soundcard. But if I use the second configuration setting this shows
up in dmesg:

ehci0: Error opening low/full speed isoc endpoint.
A low/full speed device is attached to a USB2 hub, and transaction
translations are not yet supported.
Reattach the device to the root hub instead.
uaudio_chan_open: error creating pipe: err=INVAL endpt=0x03


the usb stack is incomplete and doesn't support rate matching hubs
yet; sorry your sound card can't work on this machine yet.

recently discussed here:

http://comments.gmane.org/gmane.os.openbsd.misc/212991

-- Alexandre

Okey, that explains it. Thanks for your help.

/Johan

Re: Change default audiodevice in OpenBSD-current

[Raf Czlonka]

On Tue, Jun 03, 2014 at 05:56:50PM BST, Johan Svensson wrote:

 I can successfully run this command:
 if i use audioctl1 instead of audio1 it works, i dont know why tho.
 
 # audioctl -f /dev/audioctl1
 [...]

That's because, instead of providing audio device to the '-f' option,
you need to provide audio *control* device.

man 1 audioctl

Regards,

Raf

Re: Problem booting OpenBSD-current AMD64

[Remco]

Martijn Rijkeboer wrote:

 I've installed OpenBSD-current AMD64 on my new computer without problems,
 but as soon as I reboot the system, it freezes in the post. The only way
 to go past the post is wiping the first few megabytes of the harddisk
 using another computer and than start again. After installing I can't even
 enter the bios setup.
 
 The system contains the following components:
 - Motherboard: Gigabyte GA-B85M-DS3H
 - CPU: Intel Core i3 4130T
 - Memory: Kingston ValueRAM 8 GB DDR3-1600 Kit
 
 I've configured the bios the following way:
 - Windows 8 Features: Other OS
 - Boot Mode Selection: Legacy Only
 - VGA Support: Auto (Enables legacy option)
 
 The system is working since I can install and run Ubuntu 14.04 AMD64
 without problems.
 
 Any suggestions on how to fix this?
 
 Kind regards,
 
 
 Martijn Rijkeboer

Experienced something similar today with a Gigabyte board from the Core 2 Duo 
era. (this may not be an OpenBSD problem in my opinion)

Used an disk with a working Fedora 20/OpenBSD 5.4 install on it to do a clean 
install of OpenSUSE 13.1. Upon first boot the system hangs in the Intel AHCI 
screen. Normally a list of SATA ports and connected disks would appear but 
nothing happens. 

Eventually the simple solution for me was to use the second SATA controller 
this board has. So it may be an issue with how the Intel SATA BIOS detects 
the disks.

I don't want to waste more time on this so I'm posting some minimal info which 
may or may not useful:

The disk originally had its first partitions start at offset 63:
Disk: sd0   geometry: 9729/255/63 [156301488 Sectors]
Offset: 0   Signature: 0xAA55
Starting Ending LBA Info:
 #: id  C   H   S -  C   H   S [   start:size ]
---
*0: 83   5660  19  56 -   5723 208  53 [90929152: 1024000 ] Linux 
files*
 1: 8E   5723 208  54 -   9729  78  13 [91953152:64348160 ] Linux LVM
 2: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
 3: A6  0   1   1 -   5659 254  63 [  63:90927837 ] OpenBSD

Now, in the non-working situation, it starts at 2048 (first MB was reserved by 
the OpenSUSE installer).

Another disk that used to work has its first partition start at offset 64:
Disk: sd0   geometry: 7297/255/63 [117231408 Sectors]
Offset: 0   Signature: 0xAA55
Starting Ending LBA Info:
 #: id  C   H   S -  C   H   S [   start:size ]
---
 0: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
 1: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
 2: 00  0   0   0 -  0   0   0 [   0:   0 ] unused
*3: A6  0   1   2 -   7297  36  27 [  64:   117228536 ] OpenBSD

Re: Problem booting OpenBSD-current AMD64

[Martijn Rijkeboer]

 Ubuntu (server) 14.04 supports UEFI so it's hard to tell what you are
 seeing here.

 Perhaps you could explain what happens when you try and boot OpenBSD?
 Let's start with 1. what medium are you using and 2. what does it
 display when it tries to boot?

When I power on the machine I see the GigaByte logo and at the bottom
the options to enter the bios, Q-flash and boot selection. As soon
as this is shown the system freezes. I can't enter the bios by pressing
Del or select the boot media by pressing F12 nor does OpenBSD start.

I've installed the system using the install55.iso onto the SATA
harddisk (WD Green 1TB).

Once I have installed OpenBSD onto the harddisk I can't get into
the bios or boot from a CDROM althrough the CDROM is specified as
the first boot device. To be able to enter the bios again I have
to remove the harddisk or whipe the first few megabytes of the harddisk
with dd on another computer.

Hope this helps.


Kind regards,


Martijn Rijkeboer

Re: Problem booting OpenBSD-current AMD64

[Manolis Tzanidakis]

On Mon (28/04/14), Martijn Rijkeboer wrote:
 I've installed OpenBSD-current AMD64 on my new computer without problems,
 but as soon as I reboot the system, it freezes in the post. The only way to
 go past the post is wiping the first few megabytes of the harddisk using
 another computer and than start again. After installing I can't even
 enter the bios setup.
 
 The system contains the following components:
 - Motherboard: Gigabyte GA-B85M-DS3H
 - CPU: Intel Core i3 4130T
 - Memory: Kingston ValueRAM 8 GB DDR3-1600 Kit
 
 I've configured the bios the following way:
 - Windows 8 Features: Other OS
 - Boot Mode Selection: Legacy Only
 - VGA Support: Auto (Enables legacy option)

Hello,
I'm not familiar with the particular motherboard, but I had success
with other Gigabyte models.

Find the option CSM Support in the bios and set it to Always, leave
Boot Mode Selection and Storage Boot Option Control to Legacy
Only, power down the system and then try booting OpenBSD.

If it works, could you pls try booting OpenBSD from PXE, with bios
option Other PCI Device ROM Priority set to Legacy OpROM ?

Re: Problem booting OpenBSD-current AMD64

[Martijn Rijkeboer]

 I've installed OpenBSD-current AMD64 on my new computer without problems,
 but as soon as I reboot the system, it freezes in the post. The only way to
 go past the post is wiping the first few megabytes of the harddisk using
 another computer and than start again. After installing I can't even
 enter the bios setup.
 
 The system contains the following components:
 - Motherboard: Gigabyte GA-B85M-DS3H
 - CPU: Intel Core i3 4130T
 - Memory: Kingston ValueRAM 8 GB DDR3-1600 Kit
 
 I've configured the bios the following way:
 - Windows 8 Features: Other OS
 - Boot Mode Selection: Legacy Only
 - VGA Support: Auto (Enables legacy option)

 I'm not familiar with the particular motherboard, but I had success
 with other Gigabyte models.

 Find the option CSM Support in the bios and set it to Always, leave
 Boot Mode Selection and Storage Boot Option Control to Legacy
 Only, power down the system and then try booting OpenBSD.

Unfortunately that doesn't work either. The strange thing is that if I remove
the harddisk and use an USB stick I can install OpenBSD on it and boot it
without problems.

When I place the harddisk back with only an OpenBSD fdisk partition (A6) I can
still boot from the USB stick, but once I place a disklabel on the harddisk I
can't boot anymore (the system freezes on reboot). Apparently the bios can't
handle the disklabel...

Kind regards,


Martijn Rijkeboer

Re: Problem booting OpenBSD-current AMD64

[Karl Karlsson]

I have exactly the same issues here on a Gigabyte GA-Z87MX-DH3, a bit
strange indeed. I have tried turn every knob there is in the bios menu.
:-)


2014-04-29 21:18 GMT+02:00 Martijn Rijkeboer mart...@bunix.org:

  I've installed OpenBSD-current AMD64 on my new computer without
 problems,
  but as soon as I reboot the system, it freezes in the post. The only
 way to
  go past the post is wiping the first few megabytes of the harddisk using
  another computer and than start again. After installing I can't even
  enter the bios setup.

  The system contains the following components:
  - Motherboard: Gigabyte GA-B85M-DS3H
  - CPU: Intel Core i3 4130T
  - Memory: Kingston ValueRAM 8 GB DDR3-1600 Kit

  I've configured the bios the following way:
  - Windows 8 Features: Other OS
  - Boot Mode Selection: Legacy Only
  - VGA Support: Auto (Enables legacy option)

  I'm not familiar with the particular motherboard, but I had success
  with other Gigabyte models.

  Find the option CSM Support in the bios and set it to Always, leave
  Boot Mode Selection and Storage Boot Option Control to Legacy
  Only, power down the system and then try booting OpenBSD.

 Unfortunately that doesn't work either. The strange thing is that if I
 remove
 the harddisk and use an USB stick I can install OpenBSD on it and boot it
 without problems.

 When I place the harddisk back with only an OpenBSD fdisk partition (A6) I
 can
 still boot from the USB stick, but once I place a disklabel on the
 harddisk I
 can't boot anymore (the system freezes on reboot). Apparently the bios
 can't
 handle the disklabel...

 Kind regards,


 Martijn Rijkeboer

Problem booting OpenBSD-current AMD64

[Martijn Rijkeboer]

I've installed OpenBSD-current AMD64 on my new computer without problems,
but as soon as I reboot the system, it freezes in the post. The only way to
go past the post is wiping the first few megabytes of the harddisk using
another computer and than start again. After installing I can't even
enter the bios setup.

The system contains the following components:
- Motherboard: Gigabyte GA-B85M-DS3H
- CPU: Intel Core i3 4130T
- Memory: Kingston ValueRAM 8 GB DDR3-1600 Kit

I've configured the bios the following way:
- Windows 8 Features: Other OS
- Boot Mode Selection: Legacy Only
- VGA Support: Auto (Enables legacy option)

The system is working since I can install and run Ubuntu 14.04 AMD64
without problems.

Any suggestions on how to fix this?

Kind regards,


Martijn Rijkeboer

Re: Problem booting OpenBSD-current AMD64

[Chris Cappuccio]

Martijn Rijkeboer [mart...@bunix.org] wrote:
 The system is working since I can install and run Ubuntu 14.04 AMD64
 without problems.
 
 Any suggestions on how to fix this?
 

Ubuntu (server) 14.04 supports UEFI so it's hard to tell what you are seeing 
here.

Perhaps you could explain what happens when you try and boot OpenBSD?

Let's start with 1. what medium are you using and 2. what does it display when 
it tries to boot?

Re: Problem booting OpenBSD-current AMD64

[Tomas Bodzar]

On Tue, Apr 29, 2014 at 12:49 AM, Martijn Rijkeboer mart...@bunix.orgwrote:

 I've installed OpenBSD-current AMD64 on my new computer without problems,
 but as soon as I reboot the system, it freezes in the post. The only way to
 go past the post is wiping the first few megabytes of the harddisk using
 another computer and than start again. After installing I can't even
 enter the bios setup.


Can you collect dmesg from installer and later on output or screenshot
during boot what it tries to do?



 The system contains the following components:
 - Motherboard: Gigabyte GA-B85M-DS3H
 - CPU: Intel Core i3 4130T
 - Memory: Kingston ValueRAM 8 GB DDR3-1600 Kit

 I've configured the bios the following way:
 - Windows 8 Features: Other OS
 - Boot Mode Selection: Legacy Only
 - VGA Support: Auto (Enables legacy option)

 The system is working since I can install and run Ubuntu 14.04 AMD64
 without problems.

 At least lspci -v output will be fine from some Linux



 Any suggestions on how to fix this?

 Kind regards,


 Martijn Rijkeboer