Re: 6.7 boot crashes on "entry point at" X1 Carbon gen7 i7-10510U
On 2020-05-23, John Mettraux wrote: >> > On 23 May 2020, at 12:54, John Mettraux wrote: >> > >> > I tried to upgrade my Lenovo X1 Carbon 7th generation i7-10510U >> > from 6.6 to 6.7. >> > >> > The last reboot freezes at "entry point at 0x1001000". >> > >> > I tried to do a pure install, but booting from the USB stick leads >> > immediately >> > to the "entry point at 0x1001000" freeze. >> > >> > I found various past threads here or on Reddit for "entry point at 0x..." >> > but none yield anything useful. >> > >> > I attach the 6.6 dmesg, I fetched it after re-installing 6.6. > > On Sat, May 23, 2020 at 8:50 PM Joseph A Borg wrote: >> >> happened to me twice. Doing a hard power down worked for me but this is >> anecdotal. > > Hard power down is the only way out, but rebooting still leads > immediately to the > "entry point at 0x1001000" wall. It is consistent. I tried boot -c, > boot -d or boot -s, > still the same wall. > > I have just tried with the install67.img snapshot (22-May-2020 21:12 > 476545024) from > https://ftp.openbsd.org/pub/OpenBSD/snapshots/amd64/ but it leads to the same > "entry point at 0x1001000" right after boot. Try downloading a 6.7 kernel (bsd.mp) to e.g. /bsd.test, and from the 6.6 boot loader type "b /bsd.test". Do you still get the hang? This will give you an idea whether the problem in 6.7 is with the newer boot loader or the kernel.
Re: 6.7 boot crashes on "entry point at" X1 Carbon gen7 i7-10510U
On Sun, May 24, 2020 at 5:36 PM Stuart Henderson wrote: > > On 2020-05-23, John Mettraux wrote: > > > > (...) > > > > Hard power down is the only way out, but rebooting still leads > > immediately to the > > "entry point at 0x1001000" wall. It is consistent. I tried boot -c, > > boot -d or boot -s, > > still the same wall. > > > > I have just tried with the install67.img snapshot (22-May-2020 21:12 > > 476545024) from > > https://ftp.openbsd.org/pub/OpenBSD/snapshots/amd64/ but it leads to the > > same > > "entry point at 0x1001000" right after boot. > > Try downloading a 6.7 kernel (bsd.mp) to e.g. /bsd.test, and from the 6.6 boot > loader type "b /bsd.test". Do you still get the hang? This will give you an > idea > whether the problem in 6.7 is with the newer boot loader or the kernel. Hello, I can confirm that the hang doesn't happen with the 6.7 kernel and the 6.6 boot loader (bootx64 3.46). The hang happens with the 6.7 boot loader (3.50). I will try to do a 6.7 install with the 3.46 boot loader. Thanks a lot! John
Re: 6.7 boot crashes on "entry point at" X1 Carbon gen7 i7-10510U
On Sun, May 24, 2020 at 08:26:43PM +0900, John Mettraux wrote: > On Sun, May 24, 2020 at 5:36 PM Stuart Henderson wrote: > > > > On 2020-05-23, John Mettraux wrote: > > > > > > (...) > > > > > > Hard power down is the only way out, but rebooting still leads > > > immediately to the > > > "entry point at 0x1001000" wall. It is consistent. I tried boot -c, > > > boot -d or boot -s, > > > still the same wall. > > > > > > I have just tried with the install67.img snapshot (22-May-2020 21:12 > > > 476545024) from > > > https://ftp.openbsd.org/pub/OpenBSD/snapshots/amd64/ but it leads to the > > > same > > > "entry point at 0x1001000" right after boot. > > > > Try downloading a 6.7 kernel (bsd.mp) to e.g. /bsd.test, and from the 6.6 > > boot > > loader type "b /bsd.test". Do you still get the hang? This will give you an > > idea > > whether the problem in 6.7 is with the newer boot loader or the kernel. > > Hello, > > I can confirm that the hang doesn't happen with the 6.7 kernel and the 6.6 > boot > loader (bootx64 3.46). The hang happens with the 6.7 boot loader (3.50). > > I will try to do a 6.7 install with the 3.46 boot loader. > > Thanks a lot! > > John > Can you also try using legacy boot mode (mbr)? THere should be some setting in the bios to enable that. -Otto
Re: Select ssh key from ssh-agent?
On 5/24/20 3:55 AM, David A. Pocock wrote: > I can't relate; doing this from OpenBSD6.7 to OpenBSD6.7 the ecdsa forward > through and show up via ssh-add without any issues (and allow using the > intermediary host without having the keys present (and being able to choose > keys as per the initial question). If you want to use a specific agent-forwarded key on the intermediary host, you can put the public key (sic!) in a file on the intermediary host and use that file with the -i option or in the config file. The private key for doing the signature during authentication is then automatically selected from the agent. /m
Re: 6.7 boot crashes on "entry point at" X1 Carbon gen7 i7-10510U
On Sun, May 24, 2020 at 8:38 PM Otto Moerbeek wrote: > > On Sun, May 24, 2020 at 08:26:43PM +0900, John Mettraux wrote: > > > On Sun, May 24, 2020 at 5:36 PM Stuart Henderson > > wrote: > > > > > > On 2020-05-23, John Mettraux wrote: > > > > > > > > (...) > > > > > > > > Hard power down is the only way out, but rebooting still leads > > > > immediately to the > > > > "entry point at 0x1001000" wall. It is consistent. I tried boot -c, > > > > boot -d or boot -s, > > > > still the same wall. > > > > > > > > I have just tried with the install67.img snapshot (22-May-2020 21:12 > > > > 476545024) from > > > > https://ftp.openbsd.org/pub/OpenBSD/snapshots/amd64/ but it leads to > > > > the same > > > > "entry point at 0x1001000" right after boot. > > > > > > Try downloading a 6.7 kernel (bsd.mp) to e.g. /bsd.test, and from the 6.6 > > > boot > > > loader type "b /bsd.test". Do you still get the hang? This will give you > > > an idea > > > whether the problem in 6.7 is with the newer boot loader or the kernel. > > > > I can confirm that the hang doesn't happen with the 6.7 kernel and the 6.6 > > boot > > loader (bootx64 3.46). The hang happens with the 6.7 boot loader (3.50). > > > > I will try to do a 6.7 install with the 3.46 boot loader. > > Can you also try using legacy boot mode (mbr)? There should be some > setting in the bios to enable that. > > -Otto I tried to set the boot mode to [Legacy First] and [Legacy Only]. In both cases the Boot 3.47 kicked in and allowed me to install. I performed the install on the machine drive (sd0) with MBR and the install was successful. Dmesg below for the resulting 6.7 Snapshot. I tried to install on sd0 with GPT. The install warned me "An EFI/GPT disk may not boot. Proceed?" I answered yes. The install proceeded but upon reboot it froze with the "entry point at 0x1001000". This was with bootx64 3.50. I am going to re-install with sd0 MBR. Thanks a lot! John ---dmesg--- OpenBSD 6.7-current (RAMDISK_CD) #204: Fri May 22 20:38:04 MDT 2020 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 16197828608 (15447MB) avail mem = 15702892544 (14975MB) random: good seed from bootblocks mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.2 @ 0x6cc77000 (65 entries) bios0: vendor LENOVO version "N2QET18W (1.12 )" date 12/10/2019 bios0: LENOVO 20R1CTO1WW acpi0 at bios0: ACPI 6.1 acpi0: tables DSDT FACP SSDT SSDT SSDT SSDT SSDT TPM2 SSDT HPET APIC MCFG ECDT SSDT SSDT SSDT NHLT BOOT SSDT LPIT WSMT SSDT DBGP DBG2 MSDM BATB DMAR UEFI FPDT acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz, 7498.82 MHz, 06-8e-0c 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,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 256KB 64b/line 8-way L2 cache cpu0: apic clock running at 24MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins acpiec0 at acpi0 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (RP01) acpiprt2 at acpi0: bus -1 (RP02) acpiprt3 at acpi0: bus -1 (RP03) acpiprt4 at acpi0: bus -1 (RP04) acpiprt5 at acpi0: bus -1 (RP05) acpiprt6 at acpi0: bus -1 (RP06) acpiprt7 at acpi0: bus -1 (RP07) acpiprt8 at acpi0: bus -1 (RP08) acpiprt9 at acpi0: bus 3 (RP09) acpiprt10 at acpi0: bus -1 (RP10) acpiprt11 at acpi0: bus -1 (RP11) acpiprt12 at acpi0: bus -1 (RP12) acpiprt13 at acpi0: bus 5 (RP13) acpiprt14 at acpi0: bus -1 (RP14) acpiprt15 at acpi0: bus -1 (RP15) acpiprt16 at acpi0: bus -1 (RP16) acpiprt17 at acpi0: bus -1 (RP17) acpiprt18 at acpi0: bus -1 (RP18) acpiprt19 at acpi0: bus -1 (RP19) acpiprt20 at acpi0: bus -1 (RP20) acpiprt21 at acpi0: bus -1 (RP21) acpiprt22 at acpi0: bus -1 (RP22) acpiprt23 at acpi0: bus -1 (RP23) acpiprt24 at acpi0: bus -1 (RP24) acpipwrres at acpi0 not configured acpipwrres at acpi0 not configured acpipwrres at acpi0 not configured acpipwrres at acpi0 not configured acpipwrres at acpi0 not configured acpipwrres at acpi0 not configured acpipwrres at acpi0 not configured acpipwrres at acpi0 not configured acpipwrres at acpi0 not configured acpicpu at acpi0 not configured acpitz at acpi0 not configured acpipwrres at acpi0 not configured acpipwrres at acpi0 not configured acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 "LEN0268"
wsmouse0 detached ttyc0
A while back there were several threads going on about wsmouse0 issues on the console port. After installing 6.7 I chose to move away from xfce4 and use Awesome as my window manager. I noticed I don't receive these errors anymore. wsmouse0 detached ums0 detached uhidev0 detached uhidev0 at uhub2 port 3 configuration 1 interface 0 "PixArt USB Optical Mouse" rev 2.00/1.00 addr 5 uhidev0: iclass 3/1 ums0 at uhidev0: 3 buttons, Z dir wsmouse0 at ums0 mux 0 Jon
OK to GC net/hpodder?
The upstream has ceased hpodder development over 8 years ago. The port has to be updated every time GHC is released and for all other infrastructure changes. Even though we have enough patches for the code to compile with GHC 8.10, there needs to be somebody who runs this package to test it. Hence the proposal: Can we remove net/hpodder? Thanks Greg -- nest.cx is Gmail hosted, use PGP: https://pgp.key-server.io/0x0B1542BD8DF5A1B0 Fingerprint: 5E2B 2D0E 1E03 2046 BEC3 4D50 0B15 42BD 8DF5 A1B0
OpenBSD Qemu
OpenBSD 6.7 version crashed on Qemu5.0.0. any idea?
Re: OpenBSD Qemu
I failed to install it with Qemu because keyboard was "mad" ;) > > From: abed > Sent: Sun May 24 23:19:16 CEST 2020 > To: > Cc: > Subject: OpenBSD Qemu > > > OpenBSD 6.7 version crashed on Qemu5.0.0. any idea? > > Cordialement Francois Pussault 10 chemin de négo saoumos apt 202 - bat 2 31300 Toulouse +33 6 17 230 820 fpussa...@contactoffice.fr
Re: OpenBSD Qemu
Even better. no hopefully I was able to press some keys but it crashing randomly. On 5/24/20 9:27 PM, Francois Pussault wrote: > I failed to install it with Qemu because keyboard was "mad" > ;) > > > >> >> From: abed >> Sent: Sun May 24 23:19:16 CEST 2020 >> To: >> Cc: >> Subject: OpenBSD Qemu >> >> >> OpenBSD 6.7 version crashed on Qemu5.0.0. any idea? >> >> > > Cordialement > Francois Pussault > 10 chemin de négo saoumos > apt 202 - bat 2 > 31300 Toulouse > +33 6 17 230 820 > fpussa...@contactoffice.fr >
Re: OpenBSD Qemu
Sorry what kind of details you guess we need? Host OS: FreeBSD 12.1 VMM: Qemu 5.0.0 (compiled from source) Guest OS: OpenBSD 6.7 qemu-system-x86_64 -m 2048 \ -cdrom cd67.iso \ -drive if=virtio,file=disk.qcow2,format=qcow2 \ -enable-kvm \ -netdev user,id=mynet0,hostfwd=tcp:127.0.0.1:7922-:22 \ -device virtio-net,netdev=mynet0 \ -smp 2 On 5/24/20 10:19 PM, Solene Rapenne wrote: > Le Sun, 24 May 2020 21:19:16 +, > abed a écrit : > >> OpenBSD 6.7 version crashed on Qemu5.0.0. any idea? > I think you forgot to attach some information like the crash details. > >
FAQ/Multimedia: Burning CDs and DVDs
Hi there! I just noticed that the sections on burning CDs and DVDs are no longer present in OpenBSD's FAQ related to multimedia. Is this intentional? I didn't see anything on this on tech@ or misc@... Best, STEFAN pEpkey.asc Description: application/pgp-keys
Re: OK to GC net/hpodder?
Hi, On Sun, May 24, 2020 at 01:17:09PM -0700, Greg Steuck wrote: > The upstream has ceased hpodder development over 8 years ago. The port > has to be updated every time GHC is released and for all other > infrastructure changes. Even though we have enough patches for the > code to compile with GHC 8.10, there needs to be somebody who runs > this package to test it. Hence the proposal: > > Can we remove net/hpodder? I never used it, and dcoppa@ (the original maintainer) is inactive, so unless someone speaks up soon, I'm with you for removing it. CIao, Kili
Dovecot and multi-factor auth support
OpenBSD 6.6 amd64 OpenSMTPD 6.6.0 Dovecot 2.3.9.3 (9f41b88fa) login_duo 1.11.2 I'm working with an OpenSMTPD/Dovecot installation that will support users authenticating over the internet and I'm curious if any form of multi-factor authentication is possible for IMAP (and optionally, SMTP). Currently SMTP auth and Dovecot both authenticate users over TLS using their system user passwords. I have also set up Duo MFA for sshd using the login_duo package so admins can additionally authenticate with a push notification to phone. Is there any sort of supported way of wiring up login_duo with OpenSMTPD and Dovecot, or using bsdauth in some way to enforce a second auth factor? -- Darren Spruell phatbuck...@gmail.com
clang analyzer
Hello, clang --analyze main.c error: action RunAnalysis not compiled in I find it strange. Is there any particular reason for not including it? Is there any procedure I can use to get a "full" clang? Thank you. -- With best regards, Gregory Edigarov
Help, i want to ask if my Asus Vivobook Ryzen 3 , Vega 3 can run openbsd
Help, i want to ask if my Asus Vivobook Ryzen 3 , Vega 3 can run openbsd I have problems with freebsd i can't run xorg it has a problem with efi framebuffer and amdgpu driver. It seems that this laptop can boot only efi partitions there's no setting on bios about csm or anything else related to it. Is it possible openbsd would work ? Also is the process the same as freebsd ? I need to install drm-kmod and add kld_list amdgpu on rc.conf The openbsd installer create efi boot partition ? I think this laptop can boot only efi partitions
Re: clang analyzer
On Mon, May 25, 2020 at 02:34:53AM +0300, Gregory Edigarov wrote: > Hello, > > clang --analyze main.c > error: action RunAnalysis not compiled in > > I find it strange.?? Is there any particular reason for not including it? > > Is there any procedure I can use to get a "full" clang? $ which clang Also, have you tried the ports version? $ pkg_info -q llvm > > Thank you. > > -- > > With best regards, > > ?? Gregory Edigarov > >
Re: Help, i want to ask if my Asus Vivobook Ryzen 3 , Vega 3 can run openbsd
On Mon, May 25, 2020 at 1:49 PM Digital Crow wrote: > > Help, i want to ask if my Asus Vivobook Ryzen 3 , Vega 3 can run openbsd > I have problems with freebsd i can't run xorg it has a problem with efi > framebuffer and amdgpu driver. > It seems that this laptop can boot only efi partitions there's no setting > on bios about csm or anything else related to it. > Is it possible openbsd would work ? > Also is the process the same as freebsd ? > I need to install drm-kmod and add kld_list amdgpu on rc.conf > The openbsd installer create efi boot partition ? > I think this laptop can boot only efi partitions There's only one way to find out... -- Aaron Mason - Programmer, open source addict I've taken my software vows - for beta or for worse
Re: OpenBSD Qemu
On 25/5/20 8:34 am, abed wrote: > Sorry what kind of details you guess we need? > > Host OS: FreeBSD 12.1 > > VMM: Qemu 5.0.0 (compiled from source) > > Guest OS: OpenBSD 6.7 > > qemu-system-x86_64 -m 2048 \ -cdrom cd67.iso \ -drive > if=virtio,file=disk.qcow2,format=qcow2 \ -enable-kvm \ -netdev > user,id=mynet0,hostfwd=tcp:127.0.0.1:7922-:22 \ -device > virtio-net,netdev=mynet0 \ -smp 2 Maybe direct a virtual serial port to a telnet port in QEMU, use `telnet` within `script` to log everything seen there and tell OpenBSD to use serial console on aforementioned serial port? That might give us a `dmesg` dump to work with at least. If it really is interaction with the video console that causes it, maybe pressing some keys on said console will trigger it with the log messages going to the virtual serial port? -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere.
Re: Distorted sound in 6.7
On Fri, May 22, 2020 at 12:35:06PM +0100, Maurice McCarthy wrote: > Hi, > > Since installing 6.7 I've found that human voices in mpv or youtube > sound either very quiet or as-if "under water" or bubbly. I was > unable to cure this with sndioctl but succeeded with the old mixerctl > > doas outputs.master=200,150 > Most probably the speaker(s) are not properly wired and left and right channels cancel each other. You could check this as follows: play a mono file and meanwhile try the following: doas outputs.master=200,0 doas outputs.master=0,200 doas outputs.master=200,200 first two should play but the last one should produce (almost) silence. > If I understand sndioctl well enough this kind of left and right > speaker adjustment is not possible under sndioctl. dmesg attached. > fwiw, to control individual channels (if hardware allows it), put the channel number between squire brackets: sndioctl output[1].level=0 > Thanks again for all the magnificent effort. I've made a donation > within my means. > thank you
Re: 6.7 boot crashes on "entry point at" X1 Carbon gen7 i7-10510U
On Sun, May 24, 2020 at 09:46:09PM +0900, John Mettraux wrote: > On Sun, May 24, 2020 at 8:38 PM Otto Moerbeek wrote: > > > > On Sun, May 24, 2020 at 08:26:43PM +0900, John Mettraux wrote: > > > > > On Sun, May 24, 2020 at 5:36 PM Stuart Henderson > > > wrote: > > > > > > > > On 2020-05-23, John Mettraux wrote: > > > > > > > > > > (...) > > > > > > > > > > Hard power down is the only way out, but rebooting still leads > > > > > immediately to the > > > > > "entry point at 0x1001000" wall. It is consistent. I tried boot -c, > > > > > boot -d or boot -s, > > > > > still the same wall. > > > > > > > > > > I have just tried with the install67.img snapshot (22-May-2020 21:12 > > > > > 476545024) from > > > > > https://ftp.openbsd.org/pub/OpenBSD/snapshots/amd64/ but it leads to > > > > > the same > > > > > "entry point at 0x1001000" right after boot. > > > > > > > > Try downloading a 6.7 kernel (bsd.mp) to e.g. /bsd.test, and from the > > > > 6.6 boot > > > > loader type "b /bsd.test". Do you still get the hang? This will give > > > > you an idea > > > > whether the problem in 6.7 is with the newer boot loader or the kernel. > > > > > > I can confirm that the hang doesn't happen with the 6.7 kernel and the > > > 6.6 boot > > > loader (bootx64 3.46). The hang happens with the 6.7 boot loader (3.50). > > > > > > I will try to do a 6.7 install with the 3.46 boot loader. > > > > Can you also try using legacy boot mode (mbr)? There should be some > > setting in the bios to enable that. > > > > -Otto > > I tried to set the boot mode to [Legacy First] and [Legacy Only]. In > both cases the Boot 3.47 kicked in > and allowed me to install. > > I performed the install on the machine drive (sd0) with MBR and the > install was successful. > Dmesg below for the resulting 6.7 Snapshot. > > I tried to install on sd0 with GPT. The install warned me "An EFI/GPT > disk may not boot. Proceed?" > I answered yes. The install proceeded but upon reboot it froze with > the "entry point at 0x1001000". > This was with bootx64 3.50. > > I am going to re-install with sd0 MBR. > > Thanks a lot! > > John I have an x1 6th generation that also does not like to boot using EFI. There's is a difference though: it already had problems with EFI when I initially installed it in Feb 2019. I'll see if I can find some time to make a more detail diagnosis. -Otto > > ---dmesg--- > > OpenBSD 6.7-current (RAMDISK_CD) #204: Fri May 22 20:38:04 MDT 2020 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD > real mem = 16197828608 (15447MB) > avail mem = 15702892544 (14975MB) > random: good seed from bootblocks > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 3.2 @ 0x6cc77000 (65 entries) > bios0: vendor LENOVO version "N2QET18W (1.12 )" date 12/10/2019 > bios0: LENOVO 20R1CTO1WW > acpi0 at bios0: ACPI 6.1 > acpi0: tables DSDT FACP SSDT SSDT SSDT SSDT SSDT TPM2 SSDT HPET APIC > MCFG ECDT SSDT SSDT SSDT NHLT BOOT SSDT LPIT WSMT SSDT DBGP DBG2 MSDM > BATB DMAR UEFI FPDT > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz, 7498.82 MHz, 06-8e-0c > 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,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES > cpu0: 256KB 64b/line 8-way L2 cache > cpu0: apic clock running at 24MHz > cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE > cpu at mainbus0: not configured > cpu at mainbus0: not configured > cpu at mainbus0: not configured > cpu at mainbus0: not configured > cpu at mainbus0: not configured > cpu at mainbus0: not configured > cpu at mainbus0: not configured > ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins > acpiec0 at acpi0 > acpiprt0 at acpi0: bus 0 (PCI0) > acpiprt1 at acpi0: bus -1 (RP01) > acpiprt2 at acpi0: bus -1 (RP02) > acpiprt3 at acpi0: bus -1 (RP03) > acpiprt4 at acpi0: bus -1 (RP04) > acpiprt5 at acpi0: bus -1 (RP05) > acpiprt6 at acpi0: bus -1 (RP06) > acpiprt7 at acpi0: bus -1 (RP07) > acpiprt8 at acpi0: bus -1 (RP08) > acpiprt9 at acpi0: bus 3 (RP09) > acpiprt10 at acpi0: bus -1 (RP10) > acpiprt11 at acpi0: bus -1 (RP11) > acpiprt12 at acpi0: bus -1 (RP12) > acpiprt13 at acpi0: bus 5 (RP13) > acpiprt14 at acpi0: bus -1 (RP14) > acpiprt15 at acpi0: bus -1 (RP15) > acpiprt16 at acpi0: bus -1 (RP16) > acpiprt17 at acpi0: bus -1 (RP17) > acpiprt18 at acpi0: bus -1 (RP18) > acpiprt19 at acpi0: bus -1 (RP19) > acpiprt20 at acpi0: bus -1 (RP20) > acpiprt21 at acpi0: bus -1 (RP21) > acpiprt22 at acpi0: bus -1 (RP22) > acpiprt23 at acpi0: bus
Re: Why does OpenBSD still include Perl in its base installation?
Good morning Dawid, Have you looked at different installations methods and post install options ? Customizing the Install Process https://www.openbsd.org/faq/faq4.html#site This will certainly be worth looking at if you intend to optimize and customize installation. Regards, Jean-François Le 23/05/2020 à 17:38, Dawid Czeluśniak a écrit : An important note: If you do any of that and subsequently encounter a problem, you must 1. Assume you created that problem for yourself 2. Not file a bug report 3. Not complain to others on OpenBSD mailing lists. Fair enough. Thank you all for a detailed explanation.
