Re: boot drive hide and seek on new notebook

2020-04-29 Thread f.holop
f.holop - Wed, 29 April 2020 at 14:57:46
> i'll try to make a similar test with some linux live distro to see
> if i get similar results.

I have tested MX linux install ISO that also doubles as a Live distro.

In the end it's apples and oranges because I use the openbsd USB key to
boot the system from the internal drive ("boot hd1a:bsd"),
while the Live Linux boots from the USB key and runs from RAM (so more
like a beefed up "boot hd0a:bsd.rd")...

Nevertheless linux detects the nvme drive in all cases (entering
BIOS/not entering BIOS).


This inspired me to let the openbsd USB key boot up all the way when the
internal drive was not detected in the first stage boot.  The internal
drive was right there in `dmesg`, `sysctl hw`, `disklabel`, etc.  I
could mount it while running off of the USB key.

I think this makes the case less clear cut... Who knows what the BIOS
is doing with/without entering, but the kernel has no difficulties
seeing the drive in either case, just like linux.


Astute readers will notice that there is discrepancy in my story:

I said I can't change the boot order without entering the BIOS, but
entering the BIOS makes the internal disk show up. How could I have
this then:

probing: pc0 mem[636k 1928M 14304M]
disk: hd0


"Elemental."  With all these reboots I have worked out how this sorry
excuse for a BIOS's boot order mechanism works, and it's horrible:

It is not possible to select a generic slot like "USB media" or such.
Only when the device is bootable and is recognized by the BIOS, only
then does it show up in the dropdown and can be put in the first boot
slot.  Even then, it is remembered between reboots only until it's not
removed from the port.

It is between these types of reboots (not entering the BIOS, but the USB
key is still "remembered") that the system is booting from USB (without
entering the BIOS), however the internal drive does not show up in first
stage boot.

I wonder how many of the newer ASUS notebooks behave like this and if
this is the future, or just some frankenstein experiment...

When clearing the secure boot keys disappears from the BIOS menus,
I guess it's game over.

-f
-- 



Re: boot drive hide and seek on new notebook

2020-04-29 Thread f.holop
Stuart Henderson - Wed, 29 April 2020 at 12:24:50
> The boot loader only has access to what bios/uefi makes available,
> it looks like it isn't setting up your nvme device if you boot from USB
> unless you go through that menu. There isn't much OpenBSD can do about this.

i'll try to make a similar test with some linux live distro to see
if i get similar results.

-f
-- 



Re: boot drive hide and seek on new notebook

2020-04-29 Thread f.holop
Chris Bennett - Tue, 28 April 2020 at 23:03:32
> Some BIOS's require you to select legacy boot and legacy boot before
> UEFI in order to boot off of a USB. Also might need to turn off boot
> security option, too.
> 
> A lot of BIOS's suck nowadays. Who woulda thought that examining the
> BIOS would become a purchasing decision?

couple of points i did not go into (but i plan to make a longer
writeup):

1. legacy boot is NOT an option in this BIOS. the ASUS knowledge
base site says this option was removed for any Coffee Lake or later CPU,
so it's not coming back. For me this is an issue only because my old
notebook cannot boot UEFI, and this new one cannot boot legacy :D
so i cannot share the usb key between them.

2. secure boot MUST be disabled.  no way to boot a usb key otherwise
without mucking with platform keys or such.  In this particular (full
GUI) BIOS with a "dumb mode" and an "advanced mode", there is no
"disable secure boot" option and the installed secure keys must be NUKED
for secure boot to be disabled.

I agree that BIOS is very important, but it's impossible to use it as a
purchasing decision.  It is never indicated in the tech specs, and i
havent bought a notebook in a shop where i MIGHT be allowed to enter the
bios in more than a decade.  Even then, an update might change anything
in a flash of an eye.


Besides sharing information in my email I was kind of asking if maybe
the boot program needs some changes to be able to detect the boot drive
even without entering the BIOS (which seems to initialize something that
makes the detection work as it is).

To reiterate: if the boot order is changed in BIOS and saved, at startup
the USB key boots up, but sees only itself.  If I enter the BIOS and use
the boot order menu there to select the usb key, it boots up and sees
the internal drive as well.

-f
-- 



boot drive hide and seek on new notebook

2020-04-28 Thread f.holop
hi,

i am trying to run openbsd on a very new notebook and it kind of works.

i have taken away some space from win10 and created a partition, and the
installation went well.  atm i dont want to create a boot menu, so i
just insert a usb key with openbsd installed on it, and i select the
kernel from the internal drive.  however...  this is a normal boot:


probing: pc0 mem[636k 1928M 14304M]
disk: hd0
>> OpenBSD/amd64 BOOTX64 3.50
boot> machine diskinfo
DiskBlkSiz  IoAlign SizeFlags   Checksum
hd0 512 0   3919MB  0x2 0xa3b9b69  Removable


the internal nvme disk is nowhere to be seen.
but i have just installed openbsd on it...

another boot, this time i enter the BIOS, and it has a menu to select
the boot device manually, so i select the USB key:


probing: pc0 mem[636k 1928M 14304M]
disk: hd0 hd1
>> OpenBSD/amd64 BOOTX64 3.50
boot> machine diskinfo
DiskBlkSiz  IoAlign SizeFlags   Checksum
hd0 512 0   3919MB  0x2 0xa3b9b69  Removable
hd1 512 4   953GB   0x2 0x122409ee
boot> b hd1a:/bsd
...

and success.  but unless i enter the bios, the internal drive is not in
that list.  i think the installation process went well because i also
had to enter the BIOS to select the usb key to boot from.


here i would like to say, that amazingly, most stuff worked when i
booted up openbsd on this ASUS ROG Zephyrus gaming machine (despite
the sea of "unknown" devices ;).

here is a dmesg:


OpenBSD 6.7-beta (GENERIC.MP) #157: Sat Apr 25 15:58:34 MDT 2020
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 17005793280 (16217MB)
avail mem = 16477765632 (15714MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.2 @ 0x7a9e9000 (37 entries)
bios0: vendor American Megatrends Inc. version "GX531GW.306" date 06/28/2019
bios0: ASUSTeK COMPUTER INC. Zephyrus S GX531GW_GX531GW
acpi0 at bios0: ACPI 6.1
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT FIDT MCFG ECDT SSDT SSDT MSDM SSDT SSDT HPET 
UEFI LPIT SSDT SSDT DBGP DBG2 SSDT DMAR SSDT SSDT TPM2 BGRT SSDT WSMT
acpi0: wakeup devices PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PEGP(S4) 
XHC_(S3) XDCI(S4) HDAS(S4) AWAC(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) Core(TM) i7-8750H CPU @ 2.20GHz, 2096.70 MHz, 06-9e-0a
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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 24MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz, 2095.13 MHz, 06-9e-0a
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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz, 2095.13 MHz, 06-9e-0a
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,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz, 2095.13 MHz, 06-9e-0a
cpu3: 

snapshot checksums failing

2020-04-28 Thread f.holop
hi,

would it be possible to regenerate the latest snapshots
(amd64, cdn.openbsd.org)?  some of the archives show
checksum errors...

thank you.

-f
-- 



Re: Has anyone launched Steam for Linux on openbsd?

2020-04-22 Thread f.holop
Kevin Chadwick - Wed, 22 April 2020 at 11:01:55
> ID and the company providing Steam (Valve) have always been very good to
> Linux/OpenSource, even releasing binaries for Linux imediately and sometimes
> open sourcing further down the line.

offtopic for openbsd, sorry, but linux "has" many AAA titles:

https://github.com/ValveSoftware/Proton

-f
-- 



Re: wsmouse: disable touch-panel

2019-06-14 Thread f.holop
Benny - Tue, 11 June 2019 at 05:43:50
> Something like in xorg.conf or a config file in xorg.conf.d:
> 
> Section "InputClass"
>   Identifier "NO touch"
>   Driver "some driver"
>   MatchIsTouchscreen "on"
> Option "Ignore" "true"
> EndSection

this is the next thing i was about to try.

unfortunately it works only partially, as /dev/wsmouse seems to be some
kind of "extended" device and for some reason the config override is not
applied to it...  here are the relevant lines from Xorg.log after adding
the conf file override:

[43.542] (II) XINPUT: Adding extended input device "/dev/wskbd" (type: 
KEYBOARD, id 6)
[44.065] (II) config/wscons: checking input device /dev/wsmouse0
[44.066] (II) LoadModule: "ws"
[44.072] (II) Loading /usr/X11R6/lib/modules/input/ws_drv.so
[44.075] (II) Module ws: vendor="X.Org Foundation"
[44.076]compiled for 1.19.7, module version = 1.3.0
[44.078]Module class: X.Org XInput Driver
[44.078]ABI class: X.Org XInput driver, version 24.1
[44.080] (II) Using input driver 'ws' for '/dev/wsmouse0'
[44.081] (**) /dev/wsmouse0: always reports core events
[44.083] (II) ws: /dev/wsmouse0: debuglevel 0
[44.084] (**) Option "Device" "/dev/wsmouse0"
[44.086] (**) ws: /dev/wsmouse0: ZAxisMapping: buttons 4 and 5
[44.087] (**) ws: /dev/wsmouse0: WAxisMapping: buttons 6 and 7
[44.088] (**) ws: /dev/wsmouse0: associated screen: 0
[44.542] (II) ws: /dev/wsmouse0: minimum x position: 0
[44.543] (II) ws: /dev/wsmouse0: maximum x position: 1599
[44.544] (II) ws: /dev/wsmouse0: minimum y position: 0
[44.545] (II) ws: /dev/wsmouse0: maximum y position: 899
[44.547] (==) ws: /dev/wsmouse0: Buttons: 7
[44.598] (**) ws: /dev/wsmouse0: YAxisMapping: buttons 4 and 5
[44.600] (II) XINPUT: Adding extended input device "/dev/wsmouse0" (type: 
MOUSE, id 7)
[45.052] (**) /dev/wsmouse0: (accel) keeping acceleration scheme 1
[45.052] (**) /dev/wsmouse0: (accel) acceleration profile 0
[45.052] (**) /dev/wsmouse0: (accel) acceleration factor: 2.000
[45.053] (**) /dev/wsmouse0: (accel) acceleration threshold: 4
[45.054] (II) config/wscons: checking input device /dev/wsmouse1
[45.054] (**) /dev/wsmouse1: Ignoring device from InputClass "NO touch"
[45.055] (II) config/wscons: checking input device /dev/wsmouse2
[45.056] (**) /dev/wsmouse2: Ignoring device from InputClass "NO touch"
[45.057] (II) config/wscons: checking input device /dev/wsmouse3
[45.057] (**) /dev/wsmouse3: Ignoring device from InputClass "NO touch"
[45.058] (II) config/wscons: checking input device /dev/wsmouse
[45.058] (II) Using input driver 'ws' for '/dev/wsmouse'
[45.058] (**) /dev/wsmouse: always reports core events
[45.059] (II) ws: /dev/wsmouse: debuglevel 0
[45.060] (**) Option "Device" "/dev/wsmouse"
[45.060] (**) ws: /dev/wsmouse: ZAxisMapping: buttons 4 and 5
[45.062] (**) ws: /dev/wsmouse: WAxisMapping: buttons 6 and 7
[45.063] (**) ws: /dev/wsmouse: associated screen: 0
[45.063] (**) ws: /dev/wsmouse: device will work in raw mode
[45.063] (II) ws: /dev/wsmouse: minimum x position: 0
[45.064] (II) ws: /dev/wsmouse: maximum x position: 9600
[45.064] (II) ws: /dev/wsmouse: minimum y position: 0
[45.065] (II) ws: /dev/wsmouse: maximum y position: 7200
[45.065] (==) ws: /dev/wsmouse: Buttons: 7
[45.067] (**) ws: /dev/wsmouse: YAxisMapping: buttons 4 and 5
[45.067] (II) XINPUT: Adding extended input device "/dev/wsmouse" (type: 
TOUCHSCREEN, id 8)
[45.069] (**) /dev/wsmouse: (accel) keeping acceleration scheme 1
[45.070] (**) /dev/wsmouse: (accel) acceleration profile 0
[45.070] (**) /dev/wsmouse: (accel) acceleration factor: 2.000
[45.071] (**) /dev/wsmouse: (accel) acceleration threshold: 4

-f
-- 
[41.535] (--) checkDevMem: using aperture driver /dev/xf86
[41.571] (--) Using wscons driver on /dev/ttyC4
[41.606] 
X.Org X Server 1.19.7
Release Date: 2019-03-02
[41.608] X Protocol Version 11, Revision 0
[41.608] Build Operating System: OpenBSD 6.5 amd64 
[41.608] Current Operating System: OpenBSD monster.obiit.org 6.5 
GENERIC.MP#11 amd64
[41.609] Build Date: 08 June 2019  12:59:22PM
[41.610]  
[41.610] Current version of pixman: 0.38.4
[41.611]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[41.612] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[41.616] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jun 13 00:43:24 
2019
[41.621] (==) Using config directory: "/etc/X11/xorg.conf.d"
[41.621] (==) Using system config directory 
"/usr/X11R6/share/X11/xorg.conf.d"
[41.624] (==) No Layout section.  Using the first Screen section.
[