Re: Select ssh key from ssh-agent?
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). I was also able to do this over to a MacOS system which also handled the scenario excellently as described above and handled ECDSA just as well.
Re: acme client failing [SOLVED]
On Sat, May 23, 2020 at 8:22 PM Stuart Henderson wrote: > > On 2020-05-23, Teno Deuter wrote: > > acme-client: challenge, token: , status: 2 > > acme-client: dochngreq: > > https://acme-v02.api.letsencrypt.org/acme/authz-v3/4766326725 > > acme-client: challenge, token: ... , status: 0 > > acme-client: /var/www/acme/...: created > > acme-client: https://acme-v02.api.letsencrypt.org/acme/chall-v3/4766326725/TzAk5w: > > challenge > > acme-client: order.status -1 > > acme-client: bad exit: netproc(62115): 1 > > > > Thank you for your kind help > > > > > > https://acme-v02.api.letsencrypt.org/acme/authz-v3/4766326725 shows an > error from letsencrypt: > > "DNS problem: NXDOMAIN looking up A for www.jpcode.org - check that a > DNS record exists for this domain" > Thank you for your swift response. I didn't know how to debug the acme-client output. Correct. I forgot to update the DNS records. Now everything works well.
Re: 6.7 boot crashes on "entry point at" X1 Carbon gen7 i7-10510U
> > 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. Best regards, John
acme client failing
I have following configuration:
OpenBSD amd64 6.7
acme-client.conf:
authority letsencrypt {
api url "https://acme-v02.api.letsencrypt.org/directory;
account key "/etc/acme/letsencrypt-privkey.pem"
}
authority letsencrypt-staging {
api url "https://acme-staging-v02.api.letsencrypt.org/directory;
account key "/etc/acme/letsencrypt-staging-privkey.pem"
}
domain myserver.com {
alternative names { www.myserver.com, mail.myserver.com }
domain key "/etc/ssl/private/myserver.com.key"
domain certificate "/etc/ssl/myserver.com.crt"
domain full chain certificate "/etc/ssl/myserver.com.fullchain.pem"
sign with letsencrypt
}
httpd.conf:
server "myserver.com" {
listen on * port 80
location "/.well-known/acme-challenge/*" {
root "/acme"
request strip 2
}
location * {
block return 302 "https://$HTTP_HOST$REQUEST_URI;
}
}
server "myserver.com" {
listen on * tls port 443
tls {
certificate "/etc/ssl/myserver.com.fullchain.pem"
key "/etc/ssl/private/myserver.com.key"
}
location "/pub/*" {
directory auto index
}
location "/.well-known/acme-challenge/*" {
root "/acme"
request strip 2
}
}
when running acme-client as root, I get the following:
acme-client -vF myserver.com
acme-client: https://acme-v02.api.letsencrypt.org/directory: directories
acme-client: acme-v02.api.letsencrypt.org: DNS: 172.65.32.248
acme-client: dochngreq: ...
acme-client: challenge, token: ... status: 2
acme-client: dochngreq:
acme-client: challenge, token: , status: 2
acme-client: dochngreq:
https://acme-v02.api.letsencrypt.org/acme/authz-v3/4766326725
acme-client: challenge, token: ... , status: 0
acme-client: /var/www/acme/...: created
acme-client:
https://acme-v02.api.letsencrypt.org/acme/chall-v3/4766326725/TzAk5w:
challenge
acme-client: order.status -1
acme-client: bad exit: netproc(62115): 1
Thank you for your kind help
Re: Select ssh key from ssh-agent?
> On May 22, 2020, at 11:45 AM, Stuart Henderson wrote: > > Ahh I just realised that you might be wanting to use agent-forwarded > keys to connect to bitbucket. What I described should work if you have > local keys on the server where you run the git commands but it's not > using them because it's using a key from the agent that you don't > want it to use - but if you're trying to use one of several agent > keys then I'm not sure if it will be possible. Also, I noticed something which I think is working as intended, but seems odd. When I ssh to the intermediate server, I can do an ssh-add on there to load up a key that is only on the intermediate server. That key then is held in the ssh-agent on my workstation. After I disconnect from the intermediate server, the ssh-agent on my workstation retains the key and can use it for authentication to other hosts. I get why this happens, but it seems a little paradoxical. There also doesn’t seem to be a way to delete the key from the ssh-agent on the workstation after I disconnect (other than using ssh-add -D to blow away all of the keys.) —Paul smime.p7s Description: S/MIME cryptographic signature
Re: Select ssh key from ssh-agent?
On May 22, 2020, at 10:08 PM, David A. Pocock wrote: > > Consider: > > workstation$ eval $(ssh-agent) > workstation$ ssh-add ~/.ssh/my_primary_key > workstation$ ssh-add ~/.ssh/my_secondary_key > workstation$ ssh-add -l > hash /home/user/.ssh/my_primary_key > hash /home/user/.ssh/my_secondary_key > > workstation$ ssh -A intermediaryhost > > intermediaryhost$ ssh-add -l > hash /home/user/.ssh/my_primary_key > hash /home/user/.ssh/my_secondary_key David, It doesn’t seem to work. When I do a ssh-add -l I get file paths only for rsa keys, not ecdsa keys. I’m running OpenSSH 8.1 (OpenBSD 6.6 - yes I need to run sysupgrade), 8.1p1 (macOS 10.15.4), and 8.2p1 (Ubuntu server 20.04 LTS). In any case I tried specifying the original key file paths to ssh on my intermediate server > ssh -v -i /Users/myusername/.ssh/id_ecdsa g...@bitbucket.org but got the warning: > Warning: Identity file /Users/myusername/.ssh/id_ecdsa not accessible: No > such file or directory. According to the debug trace, the authentication then went through using a different key from my ssh-agent’s store. —Paul smime.p7s Description: S/MIME cryptographic signature
Re: acme client failing [SOLVED]
A common problem. :( I finally got around to improve acme-client's error reporting, it should be better in -current and 6.8 On 23 May 2020 21:28:23 CEST, Teno Deuter wrote: >On Sat, May 23, 2020 at 8:22 PM Stuart Henderson >wrote: >> >> On 2020-05-23, Teno Deuter wrote: >> > acme-client: challenge, token: , status: 2 >> > acme-client: dochngreq: >> > https://acme-v02.api.letsencrypt.org/acme/authz-v3/4766326725 >> > acme-client: challenge, token: ... , status: 0 >> > acme-client: /var/www/acme/...: created >> > acme-client: >https://acme-v02.api.letsencrypt.org/acme/chall-v3/4766326725/TzAk5w: >> > challenge >> > acme-client: order.status -1 >> > acme-client: bad exit: netproc(62115): 1 >> > >> > Thank you for your kind help >> > >> > >> >> https://acme-v02.api.letsencrypt.org/acme/authz-v3/4766326725 shows >an >> error from letsencrypt: >> >> "DNS problem: NXDOMAIN looking up A for www.jpcode.org - check that a >> DNS record exists for this domain" >> > >Thank you for your swift response. I didn't know how to debug the >acme-client output. > >Correct. I forgot to update the DNS records. Now everything works well. -- Sent from a mobile device. Please excuse poor formating.
openBSD on chromebook ASUS c202sa-ys02
Hello Community, did anyone manage to install openBSD on a ASUS c202sa-ys02 chromebook ? What about any other chromebook? If yes, would you share some thoughts/warning/recommendations ? Thanks in advance. Best Regards, Strahil Nikolov
[cwm] Minor leak & truncation fixes, visual/colormap question
Hi,
I'm using cwm as a daily driver on my Linux desktop machine and have
been maintaining a custom patchset for about half a year now. It mainly
removes features I never use, but also has seen one or two bug fixes.
In the hope that they are useful for upstream, I've attached a few of
them. Whilst based on my own tree of the cwm source, I've made sure that
these apply cleanly on top of the official xenocara tree with -p1.
PATCH 1/3) Fix string truncation in menu_draw
This one is pretty straightforward - the size calculation for dispstr
from menu.c did not account for the prompt characters, leading to
possible truncation.
I think I've also identified a string truncation problem at menu.c:207
if (mi->text[0] != '\0')
snprintf(mr->text, sizeof(mr->text), "%s \"%s\"",
mc->searchstr, mi->text);
As far as I can see, mr->text may end up being used for u_spawn,
possibly corrupting the quoted path if the string is truncated. I do not
have a fix ready for this as my patchset removes the path completion
functionality altogether.
PATCH 2/3) Plug memory leak in conf_clear
cargs and cargs->cmd were never freed in conf.c. My patch simply uses
the already existing conf_unbind_key() function to free those properly.
Lastly, PATCH 3/3 exists more as a request for comments and is not meant
for immediate inclusion. I am aware of a problem where certain windows'
borders (and the size or position popup menus) do not render correctly
when displayed with a compositor running.
I think this is because cwm uses the screen's default colormap and
visual to draw borders and popup menus, when it should be using each
window's colormap and visual instead. Borders and popup menus render
fine for me with the attached patch (more details there), but I am
unsure whether this is the correct solution.
I am very much not familiar with X11 programming and this patch is more
than 6 months old at this point, so I may just be doing the wrong thing
here. Nevertheless, maybe it's useful for further discussion.
Thanks a lot for your time,
--
Wolf
>From b87031f89bdbdaff956e307cc18dd3aa3b95aca3 Mon Sep 17 00:00:00 2001
From: Wynn Wolf Arbor
Date: Wed, 18 Mar 2020 19:47:54 +0100
Subject: [PATCH 1/3] Fix string truncation in menu_draw
The previous size calculation did not account for the prompt characters
(0xc2 0xbb and 0xc2 0xab respectively).
---
app/cwm/menu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app/cwm/menu.c b/app/cwm/menu.c
index 60ee46a..f2eddc3 100644
--- a/app/cwm/menu.c
+++ b/app/cwm/menu.c
@@ -53,7 +53,7 @@ struct menu_ctx {
XftDraw *xftdraw;
struct geom geom;
char searchstr[MENU_MAXENTRY + 1];
- char dispstr[MENU_MAXENTRY*2 + 1];
+ char dispstr[MENU_MAXENTRY*2 + 5];
char promptstr[MENU_MAXENTRY + 1];
int list;
int listing;
--
2.26.2
>From dc6573f7a15d09a7d985271c45398edacae9090b Mon Sep 17 00:00:00 2001
From: Wynn Wolf Arbor
Date: Wed, 18 Mar 2020 19:47:55 +0100
Subject: [PATCH 2/3] Plug a memory leak in conf_clear
These loops never freed cargs and cargs->cmd from bind_ctx. Instead of
adding more calls to free() manually, replace the whole loops with the
conf_unbind_* functions which free the struct properly.
---
app/cwm/conf.c | 11 ++-
1 file changed, 2 insertions(+), 9 deletions(-)
diff --git a/app/cwm/conf.c b/app/cwm/conf.c
index 597dd79..ad097f3 100644
--- a/app/cwm/conf.c
+++ b/app/cwm/conf.c
@@ -326,7 +326,6 @@ void
conf_clear(struct conf *c)
{
struct autogroup *ag;
- struct bind_ctx *kb, *mb;
struct winname *wn;
struct cmd_ctx *cmd, *wm;
int i;
@@ -343,10 +342,7 @@ conf_clear(struct conf *c)
free(wm->path);
free(wm);
}
- while ((kb = TAILQ_FIRST(>keybindq)) != NULL) {
- TAILQ_REMOVE(>keybindq, kb, entry);
- free(kb);
- }
+ conf_unbind_key(c, NULL);
while ((ag = TAILQ_FIRST(>autogroupq)) != NULL) {
TAILQ_REMOVE(>autogroupq, ag, entry);
free(ag->class);
@@ -358,10 +354,7 @@ conf_clear(struct conf *c)
free(wn->name);
free(wn);
}
- while ((mb = TAILQ_FIRST(>mousebindq)) != NULL) {
- TAILQ_REMOVE(>mousebindq, mb, entry);
- free(mb);
- }
+ conf_unbind_mouse(c, NULL);
for (i = 0; i < CWM_COLOR_NITEMS; i++)
free(c->color[i]);
--
2.26.2
>From da176f9f5e2f4a762d08e639c3edb0e8dee8224c Mon Sep 17 00:00:00 2001
From: Wynn Wolf Arbor
Date: Wed, 18 Mar 2020 19:47:55 +0100
Subject: [PATCH 3/3] Calculate colors using the client's visual and colormap
As cwm was using the screen's default visual and colormap to draw all
client borders, borders for windows that had a depth of 32 bits were not
rendered correctly. The same happened with text in the popup menus which
were recently changed to be drawn in the context of the client.
This commit introduces a Visual reference for each client, and allocates
all potential colors for a client's specific visual and colormap in the
client_ctx struct. These colors are then
Re: OpenVPN and 6.7
It works fine here - I just had to do a pkg_add -u after upgrading. No changes to either hostname.tap or openvpn config file. My tap0: up !cd /etc/openvpn; /usr/local/sbin/openvpn --config /etc/openvpn/openvpn-server.conf --daemon openvpn/tap0 group vpn Med Venlig Hilsen / Best Regards Henrik Krysteli Semark On 23/05/2020 06.38, oo...@pm.me wrote: > Is anyone successfully using openvpn on 6.7? Was working on 6.6 and seems > broken after upgrade. > > Oolon > > Sent from ProtonMail mobile
Re: acme client failing
On 2020-05-23, Teno Deuter wrote: > acme-client: challenge, token: , status: 2 > acme-client: dochngreq: > https://acme-v02.api.letsencrypt.org/acme/authz-v3/4766326725 > acme-client: challenge, token: ... , status: 0 > acme-client: /var/www/acme/...: created > acme-client: > https://acme-v02.api.letsencrypt.org/acme/chall-v3/4766326725/TzAk5w: > challenge > acme-client: order.status -1 > acme-client: bad exit: netproc(62115): 1 > > Thank you for your kind help > > https://acme-v02.api.letsencrypt.org/acme/authz-v3/4766326725 shows an error from letsencrypt: "DNS problem: NXDOMAIN looking up A for www.jpcode.org - check that a DNS record exists for this domain"
Re: 6.7 boot crashes on "entry point at" X1 Carbon gen7 i7-10510U
happened to me twice. Doing a hard power down worked for me but this is anecdotal. regards > On 23 May 2020, at 12:54, John Mettraux wrote: > > Hello, > > 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. > > > Thanks a lot, > > John >
Re: Unable to sysupgrade to 6.7!
On 2020-05-23 10:45, Otto Moerbeek wrote: On Sat, May 23, 2020 at 09:33:59AM +0200, Federico Giannici wrote: I was unable to upgrade my amd64 6.6 workstation to 6.7. Here is what happens: https://www.neomedia.it/tmp/67.jpg Then system reboot in an infinite loop (finally I changed the boot image to "bsd" and returned to previous 6.6). Other system infos at the end of the email. Anybody knows what the problem could be? I don't understand if it's related to the "CHECK AND RESET THE DATE" warning (never seen before and in normal 6.6 boots). I tried to advance the BIOS clock two hours (I'm UTC+2) so it shows the corret time, but nothing changed. This has nothing to do with the time or date. You have an inconsistency on your filesystem fsck -p cannot fix. It was! Thanks... Boot into bsd.rd and fsck /dev/rsd2a That said, the auto upgrade script should abort in this case. -Otto Thanks. casa:/home/giannici# df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/sd2a92878104 42769116 4546508448%/ /dev/sd2d 143421884 103486968 3276382476%/home casa:/home/giannici# mount /dev/sd2a on / type ffs (local, wxallowed) /dev/sd2d on /home type ffs (local, nodev, nosuid) casa:/home/giannici# disklabel sd2 # /dev/rsd2c: type: SCSI disk: SCSI disk label: SR RAID 1 duid: 409ffd737f4265d7 flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 30400 total sectors: 488391473 boundstart: 64 boundend: 488376000 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a:188747616 64 4.2BSD 2048 16384 12958 # / b: 10490450188747680swap# none c:4883914730 unused d:289137856199238144 4.2BSD 4096 32768 26062 # /home casa:/home/giannici# bioctl sd2 Volume Status Size Device softraid0 0 Online 250056434176 sd2 RAID1 0 Online 250056434176 0:0.0 noencl 1 Online 250056434176 0:1.0 noencl casa:/home/giannici# fdisk sd2 Disk: sd2 geometry: 30400/255/63 [488391473 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 - 30399 254 63 [ 64: 488375936 ] OpenBSD casa:/home/giannici# dmesg OpenBSD 6.6 (GENERIC.MP) #8: Fri Apr 17 15:06:32 MDT 2020 r...@syspatch-66-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17075994624 (16284MB) avail mem = 16545767424 (15779MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.2 @ 0xe6f40 (70 entries) bios0: vendor American Megatrends Inc. version "1407" date 04/02/2020 bios0: ASUSTeK COMPUTER INC. PRIME X570-P acpi0 at bios0: ACPI 6.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT SSDT WSMT SSDT SSDT MCFG HPET SSDT UEFI WPBT IVRS PCCT SSDT CRAT CDIT SSDT acpi0: wakeup devices GPP0(S4) GPP2(S4) GPP3(S4) GPP4(S4) GPP5(S4) GPP6(S4) GPP7(S4) GPP8(S4) X161(S4) GPP9(S4) X162(S4) GPPA(S4) GPPB(S4) GPPC(S4) GPPD(S4) GPPE(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Ryzen 5 3600 6-Core Processor, 3593.74 MHz, 17-71-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,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,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,IBPB,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache, 32MB 64b/line disabled 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 99MHz cpu0: mwait min=64, max=64, C-substates=1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: AMD Ryzen 5 3600 6-Core Processor, 3593.25 MHz, 17-71-00 cpu1:
Re: Why does OpenBSD still include Perl in its base installation?
> 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.
Re: OpenVPN and 6.7
I kept getting client resets from the server. I fixed it by switching to openvpn-mbedtls. Maybe some issue with libressl and openvpn? Sent from ProtonMail mobile Original Message On May 23, 2020, 00:05, Rares Aioanei wrote: > On Sat, May 23, 2020 at 04:38:59AM +, oo...@pm.me wrote: >> Is anyone successfully using openvpn on 6.7? Was working on 6.6 and seems >> broken after upgrade. >> >> Oolon >> >> Sent from ProtonMail mobile > Can you offer more details? What doesn't work? Anything in the logs? dmesg?
6.7 boot crashes on "entry point at" X1 Carbon gen7 i7-10510U
Hello, 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. Thanks a lot, John OpenBSD 6.6 (RAMDISK_CD) #349: Sat Oct 12 11:03:52 MDT 2019 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 16809205760 (16030MB) avail mem = 16295788544 (15540MB) 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, 7509.68 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 "PNP0A08" at acpi0 not configured "LEN0268" at acpi0 not configured "ACPI0003" at acpi0 not configured "PNP0C0A" at acpi0 not configured "PNP0C60" at acpi0 not configured "LEN0111" at acpi0 not configured "LEN0100" at acpi0 not configured "INT3403" at acpi0 not configured "INT3403" at acpi0 not configured "INT34BB" at acpi0 not configured "SYNA8004" at acpi0 not configured "ACPI000E" at acpi0 not configured "PNP0C14" at acpi0 not configured "INT0E0C" at acpi0 not configured "PNP0C0E" at acpi0 not configured "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured "INT33A1" at acpi0 not configured "PNP0C0D" at acpi0 not configured "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured "INT3400" at acpi0 not configured "STM7308" at acpi0 not configured "USBC000" at acpi0 not configured pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 vendor "Intel", unknown product 0x9b61 rev 0x0c vendor "Intel", unknown product 0x9b41 (class display subclass VGA, rev 0x02) at pci0 dev 2 function 0 not configured "Intel Core 6G Thermal" rev 0x0c at pci0 dev 4 function 0 not configured "Intel Core GMM" rev 0x00 at pci0 dev 8 function 0 not configured vendor "Intel", unknown product 0x02f9 (class DASP subclass miscellaneous, rev 0x00) at pci0 dev 18 function 0 not configured xhci0 at pci0 dev 20 function 0 vendor "Intel", unknown product 0x02ed rev 0x00: msi, xHCI 1.10 usb0 at xhci0: USB revision 3.0 uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 addr 1 vendor "Intel", unknown product 0x02ef (class memory
Re: acpivout error using vega20 hardware
You sent an email 11MiB in size!! Upload it elsewhere, please don't attach huge images to email.
Re: Unable to sysupgrade to 6.7!
On Sat, May 23, 2020 at 09:33:59AM +0200, Federico Giannici wrote: > I was unable to upgrade my amd64 6.6 workstation to 6.7. > > Here is what happens: https://www.neomedia.it/tmp/67.jpg > > Then system reboot in an infinite loop (finally I changed the boot image to > "bsd" and returned to previous 6.6). > > Other system infos at the end of the email. > > Anybody knows what the problem could be? > > I don't understand if it's related to the "CHECK AND RESET THE DATE" warning > (never seen before and in normal 6.6 boots). I tried to advance the BIOS > clock two hours (I'm UTC+2) so it shows the corret time, but nothing > changed. This has nothing to do with the time or date. You have an inconsistency on your filesystem fsck -p cannot fix. Boot into bsd.rd and fsck /dev/rsd2a That said, the auto upgrade script should abort in this case. -Otto > > Thanks. > > > > casa:/home/giannici# df > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/sd2a92878104 42769116 4546508448%/ > /dev/sd2d 143421884 103486968 3276382476%/home > > > casa:/home/giannici# mount > /dev/sd2a on / type ffs (local, wxallowed) > /dev/sd2d on /home type ffs (local, nodev, nosuid) > > > casa:/home/giannici# disklabel sd2 > # /dev/rsd2c: > type: SCSI > disk: SCSI disk > label: SR RAID 1 > duid: 409ffd737f4265d7 > flags: > bytes/sector: 512 > sectors/track: 63 > tracks/cylinder: 255 > sectors/cylinder: 16065 > cylinders: 30400 > total sectors: 488391473 > boundstart: 64 > boundend: 488376000 > drivedata: 0 > > 16 partitions: > #size offset fstype [fsize bsize cpg] > a:188747616 64 4.2BSD 2048 16384 12958 # / > b: 10490450188747680swap# none > c:4883914730 unused > d:289137856199238144 4.2BSD 4096 32768 26062 # /home > > > casa:/home/giannici# bioctl sd2 > Volume Status Size Device > softraid0 0 Online 250056434176 sd2 RAID1 > 0 Online 250056434176 0:0.0 noencl > 1 Online 250056434176 0:1.0 noencl > > > casa:/home/giannici# fdisk sd2 > Disk: sd2 geometry: 30400/255/63 [488391473 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 - 30399 254 63 [ 64: 488375936 ] OpenBSD > > > casa:/home/giannici# dmesg > OpenBSD 6.6 (GENERIC.MP) #8: Fri Apr 17 15:06:32 MDT 2020 > > r...@syspatch-66-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 17075994624 (16284MB) > avail mem = 16545767424 (15779MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 3.2 @ 0xe6f40 (70 entries) > bios0: vendor American Megatrends Inc. version "1407" date 04/02/2020 > bios0: ASUSTeK COMPUTER INC. PRIME X570-P > acpi0 at bios0: ACPI 6.0 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP APIC FPDT FIDT SSDT WSMT SSDT SSDT MCFG HPET SSDT > UEFI WPBT IVRS PCCT SSDT CRAT CDIT SSDT > acpi0: wakeup devices GPP0(S4) GPP2(S4) GPP3(S4) GPP4(S4) GPP5(S4) GPP6(S4) > GPP7(S4) GPP8(S4) X161(S4) GPP9(S4) X162(S4) GPPA(S4) GPPB(S4) GPPC(S4) > GPPD(S4) GPPE(S4) [...] > acpitimer0 at acpi0: 3579545 Hz, 32 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: AMD Ryzen 5 3600 6-Core Processor, 3593.74 MHz, 17-71-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,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,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,IBPB,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES > cpu0: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB > 64b/line 8-way L2 cache, 32MB 64b/line disabled 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 99MHz > cpu0: mwait min=64, max=64, C-substates=1.1, IBE > cpu1 at mainbus0: apid 2 (application processor) > cpu1: AMD Ryzen 5 3600 6-Core Processor, 3593.25 MHz, 17-71-00 > cpu1: >
OpenVPN and 6.7
Is anyone successfully using openvpn on 6.7? Was working on 6.6 and seems broken after upgrade. Oolon Sent from ProtonMail mobile
Unable to sysupgrade to 6.7!
I was unable to upgrade my amd64 6.6 workstation to 6.7. Here is what happens: https://www.neomedia.it/tmp/67.jpg Then system reboot in an infinite loop (finally I changed the boot image to "bsd" and returned to previous 6.6). Other system infos at the end of the email. Anybody knows what the problem could be? I don't understand if it's related to the "CHECK AND RESET THE DATE" warning (never seen before and in normal 6.6 boots). I tried to advance the BIOS clock two hours (I'm UTC+2) so it shows the corret time, but nothing changed. Thanks. casa:/home/giannici# df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/sd2a92878104 42769116 4546508448%/ /dev/sd2d 143421884 103486968 3276382476%/home casa:/home/giannici# mount /dev/sd2a on / type ffs (local, wxallowed) /dev/sd2d on /home type ffs (local, nodev, nosuid) casa:/home/giannici# disklabel sd2 # /dev/rsd2c: type: SCSI disk: SCSI disk label: SR RAID 1 duid: 409ffd737f4265d7 flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 30400 total sectors: 488391473 boundstart: 64 boundend: 488376000 drivedata: 0 16 partitions: #size offset fstype [fsize bsize cpg] a:188747616 64 4.2BSD 2048 16384 12958 # / b: 10490450188747680swap# none c:4883914730 unused d:289137856199238144 4.2BSD 4096 32768 26062 # /home casa:/home/giannici# bioctl sd2 Volume Status Size Device softraid0 0 Online 250056434176 sd2 RAID1 0 Online 250056434176 0:0.0 noencl 1 Online 250056434176 0:1.0 noencl casa:/home/giannici# fdisk sd2 Disk: sd2 geometry: 30400/255/63 [488391473 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 - 30399 254 63 [ 64: 488375936 ] OpenBSD casa:/home/giannici# dmesg OpenBSD 6.6 (GENERIC.MP) #8: Fri Apr 17 15:06:32 MDT 2020 r...@syspatch-66-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17075994624 (16284MB) avail mem = 16545767424 (15779MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.2 @ 0xe6f40 (70 entries) bios0: vendor American Megatrends Inc. version "1407" date 04/02/2020 bios0: ASUSTeK COMPUTER INC. PRIME X570-P acpi0 at bios0: ACPI 6.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT SSDT WSMT SSDT SSDT MCFG HPET SSDT UEFI WPBT IVRS PCCT SSDT CRAT CDIT SSDT acpi0: wakeup devices GPP0(S4) GPP2(S4) GPP3(S4) GPP4(S4) GPP5(S4) GPP6(S4) GPP7(S4) GPP8(S4) X161(S4) GPP9(S4) X162(S4) GPPA(S4) GPPB(S4) GPPC(S4) GPPD(S4) GPPE(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Ryzen 5 3600 6-Core Processor, 3593.74 MHz, 17-71-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,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,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,IBPB,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache, 32MB 64b/line disabled 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 99MHz cpu0: mwait min=64, max=64, C-substates=1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: AMD Ryzen 5 3600 6-Core Processor, 3593.25 MHz, 17-71-00 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,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,IBPB,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2
Re: OpenVPN and 6.7
On Sat, May 23, 2020 at 04:38:59AM +, oo...@pm.me wrote: > Is anyone successfully using openvpn on 6.7? Was working on 6.6 and seems > broken after upgrade. > > Oolon > > Sent from ProtonMail mobile Can you offer more details? What doesn't work? Anything in the logs? dmesg?
