Re: sysupgrade fails firmware fetch
On Sun, 18 Feb 2024 10:57:27 +0100, Stuart Henderson wrote: > > It's not too bad as long as the person building firmware tgz gets a > heads-up before the version number is updated. > Specially that right now it still can be run as: env VERSION=74 fw_update -p http://firmware.openbsd.org/firmware/snapshots I do not say that is good, but it isn't a disaster. Special for guys who runs on development snapshots. -- wbr, Kirill
Re: sysupgrade fails firmware fetch
On 2024-02-18, Theo de Raadt wrote: > Kirill A. Korinsky wrote: > >> On Sat, 17 Feb 2024 22:27:52 +0100, >> Sonic wrote: >> > >> > Seems it's looking for a 7.5 directory (-current apparently just moved >> > to 7.5-beta) instead of the snapshot directory. >> > >> >> And using snapshot directory fails because wrong signature: >> >> ~ $ doas fw_update -p http://firmware.openbsd.org/firmware/snapshots >> fw_update: failed. >> signify: verification failed: checked against wrong key >> Signature check of SHA256.sig failed >> ~ $ > > The heuristic in fw_update is weak. Every 6 months there is a chance > for someone to dig in and see if there is a better heuristic. It's not too bad as long as the person building firmware tgz gets a heads-up before the version number is updated.
Re: sysupgrade fails firmware fetch
Kirill A. Korinsky wrote: > On Sat, 17 Feb 2024 22:27:52 +0100, > Sonic wrote: > > > > Seems it's looking for a 7.5 directory (-current apparently just moved > > to 7.5-beta) instead of the snapshot directory. > > > > And using snapshot directory fails because wrong signature: > > ~ $ doas fw_update -p http://firmware.openbsd.org/firmware/snapshots > fw_update: failed. > signify: verification failed: checked against wrong key > Signature check of SHA256.sig failed > ~ $ The heuristic in fw_update is weak. Every 6 months there is a chance for someone to dig in and see if there is a better heuristic. But be careful. If the other side of the heuristic is broken for the real release cycle it will be very uncomfortable.
Re: sysupgrade fails firmware fetch
On Sat, 17 Feb 2024 22:27:52 +0100, Sonic wrote: > > Seems it's looking for a 7.5 directory (-current apparently just moved > to 7.5-beta) instead of the snapshot directory. > And using snapshot directory fails because wrong signature: ~ $ doas fw_update -p http://firmware.openbsd.org/firmware/snapshots fw_update: failed. signify: verification failed: checked against wrong key Signature check of SHA256.sig failed ~ $ -- wbr, Kirill
sysupgrade fails firmware fetch
Today "sysupgrade -s" failed to fetch updated firmware: = Verifying sets. Fetching updated firmware. fw_update: failed. Cannot fetch http://firmware.openbsd.org/firmware/7.5//SHA256.sig (404 Not Found) Upgrading. = Seems it's looking for a 7.5 directory (-current apparently just moved to 7.5-beta) instead of the snapshot directory.
Re: sysupgrade fails with "FAILED" when "verifying sets"?
> On Dec 14, 2022, at 03:03, Bodie wrote: >> On 14.12.2022 11:34, Why 42? The lists account. wrote: >> Right you are, that's the one :-/ I used to be a SPARC kinda guy, but >> those are all gone now. > > OT - they are not, but those prices... > > https://shop.eol.systems/servers/server/ Wow. OK, so maybe there’s hope for me unloading the Ultra 80 and random other Spark boxes I still have! :-) Sean
Re: sysupgrade fails with "FAILED" when "verifying sets"?
On 14.12.2022 11:34, Why 42? The lists account. wrote: On Mon, Dec 12, 2022 at 11:11:24PM -0500, Nick Holland wrote: On 12/12/22 07:22, Why 42? The lists account. wrote: > > Hi All, > > Today sysupgrade failed for me, but I'm not sure why? Here's the output: [ ... ] There is a problem with the distribution network currently. Hopefully will be resolved soon. Doing a quick check, looks like only amd64 is broke..but of course, that's what you probably want. (good time to upgrade your other platforms!) Right you are, that's the one :-/ I used to be a SPARC kinda guy, but those are all gone now. OT - they are not, but those prices... https://shop.eol.systems/servers/server/ I do have a Novena (Bunny + Xobs) ARMv7 Laptop, but I suspect installing there would make my AMD64 issue look like a walk in the park :-) Anyway, the sysupgrade download + verify works now. Just have to reboot ... If I had the slightest of quibbles it would be to wonder why sysupgrade shows "SHA256.sig" (2144 bytes) being downloaded, but it only saves "SHA256" (1992 bytes). Just seems a bit odd is all. Thanks! Cheers, Robb.
Re: sysupgrade fails with "FAILED" when "verifying sets"?
On Tue, Dec 13, 2022 at 11:12:18AM -, Stuart Henderson wrote: > On 2022-12-12, Why 42? The lists account. wrote: > > Today sysupgrade failed for me, but I'm not sure why? Here's the output: > > As the various mirrors get updated, this should be coming back to normal now. Just FYI, It's working for me now. I'll see you after the reboot ... Thanks! Cheers, Robb.
Re: sysupgrade fails with "FAILED" when "verifying sets"?
On Mon, Dec 12, 2022 at 11:11:24PM -0500, Nick Holland wrote: > On 12/12/22 07:22, Why 42? The lists account. wrote: > > > > Hi All, > > > > Today sysupgrade failed for me, but I'm not sure why? Here's the output: > [ ... ] > > There is a problem with the distribution network currently. Hopefully > will be resolved soon. > > Doing a quick check, looks like only amd64 is broke..but of course, > that's what you probably want. (good time to upgrade your other platforms!) Right you are, that's the one :-/ I used to be a SPARC kinda guy, but those are all gone now. I do have a Novena (Bunny + Xobs) ARMv7 Laptop, but I suspect installing there would make my AMD64 issue look like a walk in the park :-) Anyway, the sysupgrade download + verify works now. Just have to reboot ... If I had the slightest of quibbles it would be to wonder why sysupgrade shows "SHA256.sig" (2144 bytes) being downloaded, but it only saves "SHA256" (1992 bytes). Just seems a bit odd is all. Thanks! Cheers, Robb.
Re: sysupgrade fails with "FAILED" when "verifying sets"?
On 2022-12-12, Why 42? The lists account. wrote: > Today sysupgrade failed for me, but I'm not sure why? Here's the output: As the various mirrors get updated, this should be coming back to normal now.
Re: sysupgrade fails with "FAILED" when "verifying sets"?
On Mon, Dec 12, 2022 at 8:19 AM Stuart Henderson wrote: > > On 2022-12-12, Amit Kulkarni wrote: > > retry, and all should be ok. > > No, there is a problem with the files. > Sorry for that Robb and Stuart.
Re: sysupgrade fails with "FAILED" when "verifying sets"?
On 12/12/22 07:22, Why 42? The lists account. wrote: Hi All, Today sysupgrade failed for me, but I'm not sure why? Here's the output: [ ... ] There is a problem with the distribution network currently. Hopefully will be resolved soon. Doing a quick check, looks like only amd64 is broke..but of course, that's what you probably want. (good time to upgrade your other platforms!) Nick.
Re: sysupgrade fails with "FAILED" when "verifying sets"?
On Mon, Dec 12, 2022 at 07:39:49AM -0600, Amit Kulkarni wrote: > retry, and all should be ok. What's the basis of your statement, did something change? It still fails for me (now @16:15 CET). I also tried a different mirror, same failure (below). @Stuart: Although sysupgrade output says that it fetched and used SHA256.sig, it appears only to save a file SHA256. That's why I tried using SHA256 on the signify command line :) Yours, Robb. > mjoelnir:_sysupgrade 12.12 16:13:38 # sysupgrade -s -n > Fetching from https://ftp.halifax.rwth-aachen.de/pub/OpenBSD/snapshots/amd64/ > SHA256.sig 100% > |*| > 2144 00:00 > Signature Verified > INSTALL.amd64 100% > || > 43554 00:00 > base72.tgz 100% > |*| >332 MB00:40 > bsd 100% > |*| > 22470 KB00:04 > bsd.mp 100% > |*| > 22578 KB00:02 > bsd.rd 100% > |*| > 4546 KB00:01 > comp72.tgz 100% > |*| > 75019 KB00:13 > game72.tgz 100% > |*| > 2745 KB00:00 > man72.tgz100% > |*| > 7610 KB00:01 > xbase72.tgz 100% > |*| > 52860 KB00:06 > xfont72.tgz 100% > |*| > 22967 KB00:03 > xserv72.tgz 100% > |*| > 14815 KB00:03 > xshare72.tgz 100% > |*| > 4573 KB00:01 > Verifying sets. > (SHA256) base72.tgz: FAILED > (SHA256) bsd: FAILED > (SHA256) bsd.mp: FAILED > (SHA256) bsd.rd: FAILED > (SHA256) comp72.tgz: FAILED > (SHA256) game72.tgz: FAILED > (SHA256) man72.tgz: FAILED > (SHA256) xbase72.tgz: FAILED > (SHA256) xfont72.tgz: FAILED > (SHA256) xserv72.tgz: FAILED > (SHA256) xshare72.tgz: FAILED > mjoelnir:_sysupgrade 12.12 16:15:17 [$?==1]# ls -l SHA256* > -rw-r--r-- 1 root wheel 1992 Dec 12 16:13 SHA256
Re: sysupgrade fails with "FAILED" when "verifying sets"?
On 2022-12-12, Amit Kulkarni wrote: > retry, and all should be ok. No, there is a problem with the files. >> I have never really used signify before, but this command from the man >> page also generates an error: >> > mjoelnir:_sysupgrade 12.12 13:03:30 # signify -C -p >> > /etc/signify/openbsd-73-base.pub -x SHA256 >> > signify: invalid comment in SHA256; must start with 'untrusted comment: ' Should use SHA256.sig not SHA256. -- Please keep replies on the mailing list.
Re: sysupgrade fails with "FAILED" when "verifying sets"?
retry, and all should be ok. On Mon, Dec 12, 2022 at 7:18 AM Why 42? The lists account. wrote: > > > Hi All, > > Today sysupgrade failed for me, but I'm not sure why? Here's the output: > > # sysupgrade -s -n > > Fetching from http://ftp.fau.de/pub/OpenBSD/snapshots/amd64/ > > SHA256.sig 100% > > |***| > > 2144 00:00 > > Signature Verified > > Verifying old sets. > > base72.tgz 100% > > |***| > >332 MB00:28 > > bsd 100% > > |***| > > 22470 KB00:02 > > bsd.mp 100% > > |***| > > 22578 KB00:02 > > bsd.rd 100% > > |***| > > 4546 KB00:01 > > comp72.tgz 100% > > |***| > > 75019 KB00:07 > > game72.tgz 100% > > |***| > > 2745 KB00:00 > > man72.tgz100% > > |***| > > 7610 KB00:01 > > xbase72.tgz 100% > > |***| > > 52860 KB00:05 > > xfont72.tgz 100% > > |***| > > 22967 KB00:02 > > xserv72.tgz 100% > > |***| > > 14815 KB00:02 > > xshare72.tgz 100% > > |***| > > 4573 KB00:01 > > Verifying sets. > > (SHA256) base72.tgz: FAILED > > (SHA256) bsd: FAILED > > (SHA256) bsd.mp: FAILED > > (SHA256) bsd.rd: FAILED > > (SHA256) comp72.tgz: FAILED > > (SHA256) game72.tgz: FAILED > > (SHA256) man72.tgz: FAILED > > (SHA256) xbase72.tgz: FAILED > > (SHA256) xfont72.tgz: FAILED > > (SHA256) xserv72.tgz: FAILED > > (SHA256) xshare72.tgz: FAILED > > I see that the sha256 digests/checksums in "SHA256" differ from those of > the downloaded files: > > mjoelnir:_sysupgrade 12.12 13:02:53 [$?==1]# grep bsd.rd SHA256 > > SHA256 (bsd.rd) = > > 9065a190be5eaf047c1c0ece2517712e21964c17f39bebe3420aba2372c054ad > > mjoelnir:_sysupgrade 12.12 13:03:15 # sha256 bsd.rd > > SHA256 (bsd.rd) = > > 84ce928ccf6d71ebe5e7673aa198e424a9fdaf409d64723ba6dc8cd9333d9388 > > I don't know if that's the problem though ... > > I have never really used signify before, but this command from the man > page also generates an error: > > mjoelnir:_sysupgrade 12.12 13:03:30 # signify -C -p > > /etc/signify/openbsd-73-base.pub -x SHA256 > > signify: invalid comment in SHA256; must start with 'untrusted comment: ' > > That file starts like this: > > mjoelnir:_sysupgrade 12.12 13:05:09 # head SHA256 > > SHA256 (BOOTIA32.EFI) = > > e05572dc89a5c2c1ac53962cbf6fecda01dad0d4330d95a27e2d645a63b92d6e > > SHA256 (BOOTX64.EFI) = > > c9cf5ec60caba47c4b4ad0dc37dc88409ff9b5adb38814de1e35496759c2eed8 > > SHA256 (BUILDINFO) = > > 4d0249887ed7db9e9f336556c33a7e66024e08aeb5643f517b98c0815917529b > > ... > > Any suggestions? > > Cheers, > Robb. >
sysupgrade fails with "FAILED" when "verifying sets"?
Hi All, Today sysupgrade failed for me, but I'm not sure why? Here's the output: > # sysupgrade -s -n > Fetching from http://ftp.fau.de/pub/OpenBSD/snapshots/amd64/ > SHA256.sig 100% > |***| > 2144 00:00 > Signature Verified > Verifying old sets. > base72.tgz 100% > |***| >332 MB00:28 > bsd 100% > |***| > 22470 KB00:02 > bsd.mp 100% > |***| > 22578 KB00:02 > bsd.rd 100% > |***| > 4546 KB00:01 > comp72.tgz 100% > |***| > 75019 KB00:07 > game72.tgz 100% > |***| > 2745 KB00:00 > man72.tgz100% > |***| > 7610 KB00:01 > xbase72.tgz 100% > |***| > 52860 KB00:05 > xfont72.tgz 100% > |***| > 22967 KB00:02 > xserv72.tgz 100% > |***| > 14815 KB00:02 > xshare72.tgz 100% > |***| > 4573 KB00:01 > Verifying sets. > (SHA256) base72.tgz: FAILED > (SHA256) bsd: FAILED > (SHA256) bsd.mp: FAILED > (SHA256) bsd.rd: FAILED > (SHA256) comp72.tgz: FAILED > (SHA256) game72.tgz: FAILED > (SHA256) man72.tgz: FAILED > (SHA256) xbase72.tgz: FAILED > (SHA256) xfont72.tgz: FAILED > (SHA256) xserv72.tgz: FAILED > (SHA256) xshare72.tgz: FAILED I see that the sha256 digests/checksums in "SHA256" differ from those of the downloaded files: > mjoelnir:_sysupgrade 12.12 13:02:53 [$?==1]# grep bsd.rd SHA256 > > SHA256 (bsd.rd) = > 9065a190be5eaf047c1c0ece2517712e21964c17f39bebe3420aba2372c054ad > mjoelnir:_sysupgrade 12.12 13:03:15 # sha256 bsd.rd > > SHA256 (bsd.rd) = > 84ce928ccf6d71ebe5e7673aa198e424a9fdaf409d64723ba6dc8cd9333d9388 I don't know if that's the problem though ... I have never really used signify before, but this command from the man page also generates an error: > mjoelnir:_sysupgrade 12.12 13:03:30 # signify -C -p > /etc/signify/openbsd-73-base.pub -x SHA256 > signify: invalid comment in SHA256; must start with 'untrusted comment: ' That file starts like this: > mjoelnir:_sysupgrade 12.12 13:05:09 # head SHA256 > SHA256 (BOOTIA32.EFI) = > e05572dc89a5c2c1ac53962cbf6fecda01dad0d4330d95a27e2d645a63b92d6e > SHA256 (BOOTX64.EFI) = > c9cf5ec60caba47c4b4ad0dc37dc88409ff9b5adb38814de1e35496759c2eed8 > SHA256 (BUILDINFO) = > 4d0249887ed7db9e9f336556c33a7e66024e08aeb5643f517b98c0815917529b > ... Any suggestions? Cheers, Robb.
sysupgrade fails after reboot with: The directory '/home/_sysupgrade/' does not exist.
Hi All, I seem to have a sysupgrade problem ... sysupgrade fails after reboot with an error: The directory '/home/_sysupgrade/' does not exist. Sometime ago I had a similar issue due to my having "/home" as a sub-directory of a filesystem "/space". My mistake apparently. Never the less, I had a simple and effective workaround of modifying the path defined in /auto_upgrade.conf before rebooting. Weirdly, that workaround no longer seems to work. To try and avoid any trace of the previous "/home" mount issue, here is what happens when I use the sysupgrade -b flag to set a completely different "base-directory", located in a different filesystem ... Can anyone see where I am going wrong? mjoelnir:/etc 8.11 15:55:08 # sysupgrade -n -b /fast Fetching from http://ftp.fau.de/pub/OpenBSD/snapshots/amd64/ SHA256.sig 100% |*| 2144 00:00 Signature Verified INSTALL.amd64 100% || 43554 00:00 base72.tgz 100% |*| 332 MB00:33 bsd 100% |*| 22463 KB00:06 bsd.mp 100% |*| 22578 KB00:05 bsd.rd 100% |*| 4541 KB00:02 comp72.tgz 100% |*| 74968 KB00:11 game72.tgz 100% |*| 2745 KB00:01 man72.tgz100% |*| 7612 KB00:03 xbase72.tgz 100% |*| 52850 KB00:09 xfont72.tgz 100% |*| 22967 KB00:06 xserv72.tgz 100% |*| 14815 KB00:04 xshare72.tgz 100% |*| 4573 KB00:02 Verifying sets. Fetching updated firmware. fw_update: added none; updated none; kept intel,inteldrm,vmm Will upgrade on next reboot ### The new "base-directory" has been created: mjoelnir:/etc 8.11 15:57:15 # ls -ld /fast/_sysupgrade drwxr-xr-x 2 root wheel 512 Nov 8 15:57 /fast/_sysupgrade ### It contains the newly downloaded files: mjoelnir:/etc 8.11 15:57:26 # ls -l /fast/_sysupgrade total 1141408 -rw-r--r-- 1 root wheel 43554 Nov 8 00:18 INSTALL.amd64 -rw-r--r-- 1 root wheel 1992 Nov 8 15:55 SHA256 -rw-r--r-- 1 root wheel 348171346 Nov 8 00:13 base72.tgz -rw-r--r-- 1 root wheel 23002725 Nov 8 00:12 bsd -rw-r--r-- 1 root wheel 23120636 Nov 8 00:12 bsd.mp -rw-r--r-- 1 root wheel4650857 Nov 8 00:18 bsd.rd -rw-r--r-- 1 root wheel 76767540 Nov 8 00:13 comp72.tgz -rw-r--r-- 1 root wheel2811462 Nov 8 00:13 game72.tgz -rw-r--r-- 1 root wheel7794925 Nov 8 00:13 man72.tgz -rw-r--r-- 1 root wheel 54119339 Nov 8 00:34 xbase72.tgz -rw-r--r-- 1 root wheel 23518994 Nov 8 00:34 xfont72.tgz -rw-r--r-- 1 root wheel 15170647 Nov 8 00:34 xserv72.tgz -rw-r--r-- 1 root wheel4683158 Nov 8 00:34 xshare72.tgz ### The root directory now also has some new files: mjoelnir:/etc 8.11 15:57:32 # ls -ltr / total 153738 -rw-r--r-- 1 root wheel 468 Jun 2 2019 .profile -rw-r--r-- 1 root wheel 578 Jun 2 2019 .cshrc drwxr-xr-x 2 root wheel 512 Sep 29 2019 space lrwxr-xr-x 1 root wheel 9 Jun 3 2020 opt -> /fast/opt -rw-r--r-- 1 root wheel 90496 Jan 28 2021 boot lrwxrwx--- 1 root wheel11 Aug 19 07:54 sys -> usr/src/sys drwxr-xr-x 2 root wheel 512 Aug 19 07:54 altroot drwxr-xr-x 2 root wheel 1024 Aug 19 07:55 bin drwxr-xr-x 2 root wheel 1536 Aug 19 07:55 sbin drwxr-xr-x 31 root wheel 512 Aug 19 08:34 var drwxr-xr-x 16 root wheel 512 Aug 19 08:34 usr -rwx-- 1 root wheel 22982134 Aug 19 14:46 bsd.sp -rw--- 1 root wheel 4638162 Aug 19 14:46 bsd.rd drwxr-xr-x 4 root wheel 512 Nov 8 13:43 mnt drwxr-xr-x 20 root wheel 512 Nov 8 13:48 home -rwx-- 1 root wheel 23088585 Nov 8 15:02 bsd.booted drwxr-xr-x 6 root wheel 19968 Nov 8 15:41 dev -rwx-- 1 root wheel 23082305 Nov 8 15:41 bsd drwxr-xr-x 6 roo
Re: sysupgrade fails due to "CHECK AND RESET DATE" ?
> 7 апр. 2022 г., в 17:13, Jan Stary написал(а): > > >> >> It seems that problem is not having any display device during sysupgrade >> process. > > I don't think sysupgrade has any requirements regarding a display device: > headless machines get sysupgraded regularly Yes. I have some another headless machines, but this pc not updating without display. And some guys on reddit also had this issue
Re: sysupgrade fails due to "CHECK AND RESET DATE" ?
> It seems that problem is not having any display device during sysupgrade > process. I don't think sysupgrade has any requirements regarding a display device: headless machines get sysupgraded regularly
Re: sysupgrade fails due to "CHECK AND RESET DATE" ?
19.10.2021 10:14, kasak пишет: 18.10.2021 23:18, kasak пишет: Hello everyone! I have one mini router, made from gigabyte GB-SBCAP4200 barebone It has nothing special. Just base openbsd, without any additional packages and modifications. for some reason, sysupgrade does not upgrade this system. It successfully boot new kernel, but do not process the upgrade, Just load 6.9 back. This is dmesg from loading 7.0 and further: OpenBSD 7.0 (RAMDISK_CD) #219: Thu Sep 30 14:32:42 MDT 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 8415617024 (8025MB) avail mem = 8156545024 (7778MB) random: good seed from bootblocks mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x79db7000 (50 entries) bios0: vendor American Megatrends Inc. version "F1" date 06/11/2018 bios0: Gigabyte Technology Co., Ltd. Default string acpi0 at bios0: ACPI 6.0 acpi0: tables DSDT FACP FPDT FIDT MCFG DBG2 DBGP HPET LPIT APIC NPKT PRAM WSMT SSDT SSDT SSDT SSDT SSDT SSDT SSDT UEFI TPM2 WDAT acpihpet0 at acpi0: 1920 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Pentium(R) CPU N4200 @ 1.10GHz, 1097.47 MHz, 06-5c-09 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu0: 1MB 64b/line 16-way L2 cache cpu0: apic clock running at 19MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.2.4.2.1.1, IBE cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 120 pins 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 2 (RP04) acpiprt5 at acpi0: bus 3 (RP05) acpiprt6 at acpi0: bus 4 (RP06) acpiec0 at acpi0: not present acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 acpicmos0 at acpi0 "PNP0C0C" at acpi0 not configured aplgpio0 at acpi0 GPO0 uid 1 addr 0xd0c5/0x76c irq 14, 78 pins aplgpio1 at acpi0 GPO1 uid 2 addr 0xd0c4/0x764 irq 14, 77 pins aplgpio2 at acpi0 GPO2 uid 3 addr 0xd0c7/0x674 irq 14, 47 pins aplgpio3 at acpi0 GPO3 uid 4 addr 0xd0c0/0x654 irq 14, 43 pins "INT33A1" at acpi0 not configured "MSFT0101" at acpi0 not configured "PNP0C0B" at acpi0 not configured acpicpu at acpi0 not configured acpipwrres at acpi0 not configured acpitz at acpi0 not configured pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Apollo Lake Host" rev 0x0b "Intel HD Graphics 505" rev 0x0b at pci0 dev 2 function 0 not configured "Intel Apollo Lake HD Audio" rev 0x0b at pci0 dev 14 function 0 not configured "Intel Apollo Lake TXE" rev 0x0b at pci0 dev 15 function 0 not configured ahci0 at pci0 dev 18 function 0 "Intel Apollo Lake AHCI" rev 0x0b: msi, AHCI 1.3.1 ahci0: PHY offline on port 0 ahci0: port 1: 6.0Gb/s scsibus0 at ahci0: 32 targets sd0 at scsibus0 targ 1 lun 0: naa.50026b7783a249ed sd0: 228936MB, 512 bytes/sector, 468862128 sectors, thin ppb0 at pci0 dev 19 function 0 "Intel Apollo Lake PCIE" rev 0xfb: msi pci1 at ppb0 bus 1 ppb1 at pci0 dev 19 function 1 "Intel Apollo Lake PCIE" rev 0xfb: msi pci2 at ppb1 bus 2 ppb2 at pci0 dev 19 function 2 "Intel Apollo Lake PCIE" rev 0xfb: msi pci3 at ppb2 bus 3 re0 at pci3 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G (0x4c00), msi, address e0:d5:5e:e7:50:4f rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0 ppb3 at pci0 dev 19 function 3 "Intel Apollo Lake PCIE" rev 0xfb: msi pci4 at ppb3 bus 4 re1 at pci4 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G (0x4c00), msi, address e0:d5:5e:e7:50:51 rgephy1 at re1 phy 7: RTL8251 PHY, rev. 0 xhci0 at pci0 dev 21 function 0 "Intel Apollo Lake xHCI" rev 0x0b: msi, xHCI 1.0 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 "Intel Apollo Lake LPC" rev 0x0b at pci0 dev 31 function 0 not configured "Intel Apollo Lake SMBus" rev 0x0b at pci0 dev 31 function 1 not configured isa0 at mainbus0 pckbc0 at isa0 port 0x60/5 irq 1 irq 12 efifb at mainbus0 not configured softraid0 at root scsibus1 at softraid0: 256 targets root on rd0a swap on rd0b dump on rd0b WARNING: CHECK AND RESET THE DATE! OpenBSD 6.9 (GENERIC.MP) #4: Tue Aug 10 08:12:23 MDT 2021 r...@syspatch-69-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8415617024 (8025MB) avail mem = 8145182720 (7767MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x79db7000 (50 entries) bios0: vendor American Megatrends Inc. version "F1"
Re: sysupgrade fails due to "CHECK AND RESET DATE" ?
On 2021-10-19 02:45, Otto Moerbeek wrote: On Mon, Oct 18, 2021 at 11:18:20PM +0300, kasak wrote: Hello everyone! I have one mini router, made from gigabyte GB-SBCAP4200 barebone It has nothing special. Just base openbsd, without any additional packages and modifications. for some reason, sysupgrade does not upgrade this system. It successfully boot new kernel, but do not process the upgrade, Just load 6.9 back. This is dmesg from loading 7.0 and further: OpenBSD 7.0 (RAMDISK_CD) #219: Thu Sep 30 14:32:42 MDT 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 8415617024 (8025MB) avail mem = 8156545024 (7778MB) random: good seed from bootblocks mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x79db7000 (50 entries) bios0: vendor American Megatrends Inc. version "F1" date 06/11/2018 bios0: Gigabyte Technology Co., Ltd. Default string acpi0 at bios0: ACPI 6.0 acpi0: tables DSDT FACP FPDT FIDT MCFG DBG2 DBGP HPET LPIT APIC NPKT PRAM WSMT SSDT SSDT SSDT SSDT SSDT SSDT SSDT UEFI TPM2 WDAT acpihpet0 at acpi0: 1920 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Pentium(R) CPU N4200 @ 1.10GHz, 1097.47 MHz, 06-5c-09 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu0: 1MB 64b/line 16-way L2 cache cpu0: apic clock running at 19MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.2.4.2.1.1, IBE cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 120 pins 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 2 (RP04) acpiprt5 at acpi0: bus 3 (RP05) acpiprt6 at acpi0: bus 4 (RP06) acpiec0 at acpi0: not present acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 acpicmos0 at acpi0 "PNP0C0C" at acpi0 not configured aplgpio0 at acpi0 GPO0 uid 1 addr 0xd0c5/0x76c irq 14, 78 pins aplgpio1 at acpi0 GPO1 uid 2 addr 0xd0c4/0x764 irq 14, 77 pins aplgpio2 at acpi0 GPO2 uid 3 addr 0xd0c7/0x674 irq 14, 47 pins aplgpio3 at acpi0 GPO3 uid 4 addr 0xd0c0/0x654 irq 14, 43 pins "INT33A1" at acpi0 not configured "MSFT0101" at acpi0 not configured "PNP0C0B" at acpi0 not configured acpicpu at acpi0 not configured acpipwrres at acpi0 not configured acpitz at acpi0 not configured pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Apollo Lake Host" rev 0x0b "Intel HD Graphics 505" rev 0x0b at pci0 dev 2 function 0 not configured "Intel Apollo Lake HD Audio" rev 0x0b at pci0 dev 14 function 0 not configured "Intel Apollo Lake TXE" rev 0x0b at pci0 dev 15 function 0 not configured ahci0 at pci0 dev 18 function 0 "Intel Apollo Lake AHCI" rev 0x0b: msi, AHCI 1.3.1 ahci0: PHY offline on port 0 ahci0: port 1: 6.0Gb/s scsibus0 at ahci0: 32 targets sd0 at scsibus0 targ 1 lun 0: naa.50026b7783a249ed sd0: 228936MB, 512 bytes/sector, 468862128 sectors, thin ppb0 at pci0 dev 19 function 0 "Intel Apollo Lake PCIE" rev 0xfb: msi pci1 at ppb0 bus 1 ppb1 at pci0 dev 19 function 1 "Intel Apollo Lake PCIE" rev 0xfb: msi pci2 at ppb1 bus 2 ppb2 at pci0 dev 19 function 2 "Intel Apollo Lake PCIE" rev 0xfb: msi pci3 at ppb2 bus 3 re0 at pci3 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G (0x4c00), msi, address e0:d5:5e:e7:50:4f rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0 ppb3 at pci0 dev 19 function 3 "Intel Apollo Lake PCIE" rev 0xfb: msi pci4 at ppb3 bus 4 re1 at pci4 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G (0x4c00), msi, address e0:d5:5e:e7:50:51 rgephy1 at re1 phy 7: RTL8251 PHY, rev. 0 xhci0 at pci0 dev 21 function 0 "Intel Apollo Lake xHCI" rev 0x0b: msi, xHCI 1.0 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 "Intel Apollo Lake LPC" rev 0x0b at pci0 dev 31 function 0 not configured "Intel Apollo Lake SMBus" rev 0x0b at pci0 dev 31 function 1 not configured isa0 at mainbus0 pckbc0 at isa0 port 0x60/5 irq 1 irq 12 efifb at mainbus0 not configured softraid0 at root scsibus1 at softraid0: 256 targets root on rd0a swap on rd0b dump on rd0b WARNING: CHECK AND RESET THE DATE! OpenBSD 6.9 (GENERIC.MP) #4: Tue Aug 10 08:12:23 MDT 2021 r...@syspatch-69-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8415617024 (8025MB) avail mem = 8145182720 (7767MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x79db7000 (50 entries) bios0: vendor American
Re: sysupgrade fails due to "CHECK AND RESET DATE" ?
18.10.2021 23:18, kasak пишет: Hello everyone! I have one mini router, made from gigabyte GB-SBCAP4200 barebone It has nothing special. Just base openbsd, without any additional packages and modifications. for some reason, sysupgrade does not upgrade this system. It successfully boot new kernel, but do not process the upgrade, Just load 6.9 back. This is dmesg from loading 7.0 and further: OpenBSD 7.0 (RAMDISK_CD) #219: Thu Sep 30 14:32:42 MDT 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 8415617024 (8025MB) avail mem = 8156545024 (7778MB) random: good seed from bootblocks mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x79db7000 (50 entries) bios0: vendor American Megatrends Inc. version "F1" date 06/11/2018 bios0: Gigabyte Technology Co., Ltd. Default string acpi0 at bios0: ACPI 6.0 acpi0: tables DSDT FACP FPDT FIDT MCFG DBG2 DBGP HPET LPIT APIC NPKT PRAM WSMT SSDT SSDT SSDT SSDT SSDT SSDT SSDT UEFI TPM2 WDAT acpihpet0 at acpi0: 1920 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Pentium(R) CPU N4200 @ 1.10GHz, 1097.47 MHz, 06-5c-09 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu0: 1MB 64b/line 16-way L2 cache cpu0: apic clock running at 19MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.2.4.2.1.1, IBE cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 120 pins 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 2 (RP04) acpiprt5 at acpi0: bus 3 (RP05) acpiprt6 at acpi0: bus 4 (RP06) acpiec0 at acpi0: not present acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 acpicmos0 at acpi0 "PNP0C0C" at acpi0 not configured aplgpio0 at acpi0 GPO0 uid 1 addr 0xd0c5/0x76c irq 14, 78 pins aplgpio1 at acpi0 GPO1 uid 2 addr 0xd0c4/0x764 irq 14, 77 pins aplgpio2 at acpi0 GPO2 uid 3 addr 0xd0c7/0x674 irq 14, 47 pins aplgpio3 at acpi0 GPO3 uid 4 addr 0xd0c0/0x654 irq 14, 43 pins "INT33A1" at acpi0 not configured "MSFT0101" at acpi0 not configured "PNP0C0B" at acpi0 not configured acpicpu at acpi0 not configured acpipwrres at acpi0 not configured acpitz at acpi0 not configured pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Apollo Lake Host" rev 0x0b "Intel HD Graphics 505" rev 0x0b at pci0 dev 2 function 0 not configured "Intel Apollo Lake HD Audio" rev 0x0b at pci0 dev 14 function 0 not configured "Intel Apollo Lake TXE" rev 0x0b at pci0 dev 15 function 0 not configured ahci0 at pci0 dev 18 function 0 "Intel Apollo Lake AHCI" rev 0x0b: msi, AHCI 1.3.1 ahci0: PHY offline on port 0 ahci0: port 1: 6.0Gb/s scsibus0 at ahci0: 32 targets sd0 at scsibus0 targ 1 lun 0: naa.50026b7783a249ed sd0: 228936MB, 512 bytes/sector, 468862128 sectors, thin ppb0 at pci0 dev 19 function 0 "Intel Apollo Lake PCIE" rev 0xfb: msi pci1 at ppb0 bus 1 ppb1 at pci0 dev 19 function 1 "Intel Apollo Lake PCIE" rev 0xfb: msi pci2 at ppb1 bus 2 ppb2 at pci0 dev 19 function 2 "Intel Apollo Lake PCIE" rev 0xfb: msi pci3 at ppb2 bus 3 re0 at pci3 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G (0x4c00), msi, address e0:d5:5e:e7:50:4f rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0 ppb3 at pci0 dev 19 function 3 "Intel Apollo Lake PCIE" rev 0xfb: msi pci4 at ppb3 bus 4 re1 at pci4 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G (0x4c00), msi, address e0:d5:5e:e7:50:51 rgephy1 at re1 phy 7: RTL8251 PHY, rev. 0 xhci0 at pci0 dev 21 function 0 "Intel Apollo Lake xHCI" rev 0x0b: msi, xHCI 1.0 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 "Intel Apollo Lake LPC" rev 0x0b at pci0 dev 31 function 0 not configured "Intel Apollo Lake SMBus" rev 0x0b at pci0 dev 31 function 1 not configured isa0 at mainbus0 pckbc0 at isa0 port 0x60/5 irq 1 irq 12 efifb at mainbus0 not configured softraid0 at root scsibus1 at softraid0: 256 targets root on rd0a swap on rd0b dump on rd0b WARNING: CHECK AND RESET THE DATE! OpenBSD 6.9 (GENERIC.MP) #4: Tue Aug 10 08:12:23 MDT 2021 r...@syspatch-69-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8415617024 (8025MB) avail mem = 8145182720 (7767MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x79db7000 (50 entries) bios0: vendor American Megatrends Inc. version "F1" date 06/11/2018 bios0: Gigabyte
Re: sysupgrade fails due to "CHECK AND RESET DATE" ?
19.10.2021 09:41, Otto Moerbeek пишет: On Tue, Oct 19, 2021 at 09:30:47AM +0300, kasak wrote: 19.10.2021 08:45, Otto Moerbeek пишет: On Mon, Oct 18, 2021 at 11:18:20PM +0300, kasak wrote: Hello everyone! I have one mini router, made from gigabyte GB-SBCAP4200 barebone It has nothing special. Just base openbsd, without any additional packages and modifications. for some reason, sysupgrade does not upgrade this system. It successfully boot new kernel, but do not process the upgrade, Just load 6.9 back. This is dmesg from loading 7.0 and further: OpenBSD 7.0 (RAMDISK_CD) #219: Thu Sep 30 14:32:42 MDT 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 8415617024 (8025MB) avail mem = 8156545024 (7778MB) random: good seed from bootblocks mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x79db7000 (50 entries) bios0: vendor American Megatrends Inc. version "F1" date 06/11/2018 bios0: Gigabyte Technology Co., Ltd. Default string acpi0 at bios0: ACPI 6.0 acpi0: tables DSDT FACP FPDT FIDT MCFG DBG2 DBGP HPET LPIT APIC NPKT PRAM WSMT SSDT SSDT SSDT SSDT SSDT SSDT SSDT UEFI TPM2 WDAT acpihpet0 at acpi0: 1920 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Pentium(R) CPU N4200 @ 1.10GHz, 1097.47 MHz, 06-5c-09 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu0: 1MB 64b/line 16-way L2 cache cpu0: apic clock running at 19MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.2.4.2.1.1, IBE cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 120 pins 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 2 (RP04) acpiprt5 at acpi0: bus 3 (RP05) acpiprt6 at acpi0: bus 4 (RP06) acpiec0 at acpi0: not present acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 acpicmos0 at acpi0 "PNP0C0C" at acpi0 not configured aplgpio0 at acpi0 GPO0 uid 1 addr 0xd0c5/0x76c irq 14, 78 pins aplgpio1 at acpi0 GPO1 uid 2 addr 0xd0c4/0x764 irq 14, 77 pins aplgpio2 at acpi0 GPO2 uid 3 addr 0xd0c7/0x674 irq 14, 47 pins aplgpio3 at acpi0 GPO3 uid 4 addr 0xd0c0/0x654 irq 14, 43 pins "INT33A1" at acpi0 not configured "MSFT0101" at acpi0 not configured "PNP0C0B" at acpi0 not configured acpicpu at acpi0 not configured acpipwrres at acpi0 not configured acpitz at acpi0 not configured pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Apollo Lake Host" rev 0x0b "Intel HD Graphics 505" rev 0x0b at pci0 dev 2 function 0 not configured "Intel Apollo Lake HD Audio" rev 0x0b at pci0 dev 14 function 0 not configured "Intel Apollo Lake TXE" rev 0x0b at pci0 dev 15 function 0 not configured ahci0 at pci0 dev 18 function 0 "Intel Apollo Lake AHCI" rev 0x0b: msi, AHCI 1.3.1 ahci0: PHY offline on port 0 ahci0: port 1: 6.0Gb/s scsibus0 at ahci0: 32 targets sd0 at scsibus0 targ 1 lun 0: naa.50026b7783a249ed sd0: 228936MB, 512 bytes/sector, 468862128 sectors, thin ppb0 at pci0 dev 19 function 0 "Intel Apollo Lake PCIE" rev 0xfb: msi pci1 at ppb0 bus 1 ppb1 at pci0 dev 19 function 1 "Intel Apollo Lake PCIE" rev 0xfb: msi pci2 at ppb1 bus 2 ppb2 at pci0 dev 19 function 2 "Intel Apollo Lake PCIE" rev 0xfb: msi pci3 at ppb2 bus 3 re0 at pci3 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G (0x4c00), msi, address e0:d5:5e:e7:50:4f rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0 ppb3 at pci0 dev 19 function 3 "Intel Apollo Lake PCIE" rev 0xfb: msi pci4 at ppb3 bus 4 re1 at pci4 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G (0x4c00), msi, address e0:d5:5e:e7:50:51 rgephy1 at re1 phy 7: RTL8251 PHY, rev. 0 xhci0 at pci0 dev 21 function 0 "Intel Apollo Lake xHCI" rev 0x0b: msi, xHCI 1.0 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 "Intel Apollo Lake LPC" rev 0x0b at pci0 dev 31 function 0 not configured "Intel Apollo Lake SMBus" rev 0x0b at pci0 dev 31 function 1 not configured isa0 at mainbus0 pckbc0 at isa0 port 0x60/5 irq 1 irq 12 efifb at mainbus0 not configured softraid0 at root scsibus1 at softraid0: 256 targets root on rd0a swap on rd0b dump on rd0b WARNING: CHECK AND RESET THE DATE! OpenBSD 6.9 (GENERIC.MP) #4: Tue Aug 10 08:12:23 MDT 2021 r...@syspatch-69-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8415617024 (8025MB) avail mem = 8145182720 (7767MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at
Re: sysupgrade fails due to "CHECK AND RESET DATE" ?
On Tue, Oct 19, 2021 at 09:30:47AM +0300, kasak wrote: > > 19.10.2021 08:45, Otto Moerbeek пишет: > > On Mon, Oct 18, 2021 at 11:18:20PM +0300, kasak wrote: > > > > > Hello everyone! > > > > > > I have one mini router, made from gigabyte GB-SBCAP4200 barebone > > > > > > It has nothing special. Just base openbsd, without any additional packages > > > and modifications. > > > > > > for some reason, sysupgrade does not upgrade this system. > > > It successfully boot new kernel, but do not process the upgrade, Just load > > > 6.9 back. > > > > > > This is dmesg from loading 7.0 and further: > > > > > > OpenBSD 7.0 (RAMDISK_CD) #219: Thu Sep 30 14:32:42 MDT 2021 > > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD > > > real mem = 8415617024 (8025MB) > > > avail mem = 8156545024 (7778MB) > > > random: good seed from bootblocks > > > mainbus0 at root > > > bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x79db7000 (50 entries) > > > bios0: vendor American Megatrends Inc. version "F1" date 06/11/2018 > > > bios0: Gigabyte Technology Co., Ltd. Default string > > > acpi0 at bios0: ACPI 6.0 > > > acpi0: tables DSDT FACP FPDT FIDT MCFG DBG2 DBGP HPET LPIT APIC NPKT PRAM > > > WSMT SSDT SSDT SSDT SSDT SSDT SSDT SSDT UEFI TPM2 WDAT > > > acpihpet0 at acpi0: 1920 Hz > > > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > > > cpu0 at mainbus0: apid 0 (boot processor) > > > cpu0: Intel(R) Pentium(R) CPU N4200 @ 1.10GHz, 1097.47 MHz, 06-5c-09 > > > 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN > > > cpu0: 1MB 64b/line 16-way L2 cache > > > cpu0: apic clock running at 19MHz > > > cpu0: mwait min=64, max=64, C-substates=0.2.0.2.4.2.1.1, IBE > > > cpu at mainbus0: not configured > > > cpu at mainbus0: not configured > > > cpu at mainbus0: not configured > > > ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 120 pins > > > 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 2 (RP04) > > > acpiprt5 at acpi0: bus 3 (RP05) > > > acpiprt6 at acpi0: bus 4 (RP06) > > > acpiec0 at acpi0: not present > > > acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 > > > acpicmos0 at acpi0 > > > "PNP0C0C" at acpi0 not configured > > > aplgpio0 at acpi0 GPO0 uid 1 addr 0xd0c5/0x76c irq 14, 78 pins > > > aplgpio1 at acpi0 GPO1 uid 2 addr 0xd0c4/0x764 irq 14, 77 pins > > > aplgpio2 at acpi0 GPO2 uid 3 addr 0xd0c7/0x674 irq 14, 47 pins > > > aplgpio3 at acpi0 GPO3 uid 4 addr 0xd0c0/0x654 irq 14, 43 pins > > > "INT33A1" at acpi0 not configured > > > "MSFT0101" at acpi0 not configured > > > "PNP0C0B" at acpi0 not configured > > > acpicpu at acpi0 not configured > > > acpipwrres at acpi0 not configured > > > acpitz at acpi0 not configured > > > pci0 at mainbus0 bus 0 > > > pchb0 at pci0 dev 0 function 0 "Intel Apollo Lake Host" rev 0x0b > > > "Intel HD Graphics 505" rev 0x0b at pci0 dev 2 function 0 not configured > > > "Intel Apollo Lake HD Audio" rev 0x0b at pci0 dev 14 function 0 not > > > configured > > > "Intel Apollo Lake TXE" rev 0x0b at pci0 dev 15 function 0 not configured > > > ahci0 at pci0 dev 18 function 0 "Intel Apollo Lake AHCI" rev 0x0b: msi, > > > AHCI > > > 1.3.1 > > > ahci0: PHY offline on port 0 > > > ahci0: port 1: 6.0Gb/s > > > scsibus0 at ahci0: 32 targets > > > sd0 at scsibus0 targ 1 lun 0: > > > naa.50026b7783a249ed > > > sd0: 228936MB, 512 bytes/sector, 468862128 sectors, thin > > > ppb0 at pci0 dev 19 function 0 "Intel Apollo Lake PCIE" rev 0xfb: msi > > > pci1 at ppb0 bus 1 > > > ppb1 at pci0 dev 19 function 1 "Intel Apollo Lake PCIE" rev 0xfb: msi > > > pci2 at ppb1 bus 2 > > > ppb2 at pci0 dev 19 function 2 "Intel Apollo Lake PCIE" rev 0xfb: msi > > > pci3 at ppb2 bus 3 > > > re0 at pci3 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G > > > (0x4c00), msi, address e0:d5:5e:e7:50:4f > > > rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0 > > > ppb3 at pci0 dev 19 function 3 "Intel Apollo Lake PCIE" rev 0xfb: msi > > > pci4 at ppb3 bus 4 > > > re1 at pci4 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G > > > (0x4c00), msi, address e0:d5:5e:e7:50:51 > > > rgephy1 at re1 phy 7: RTL8251 PHY, rev. 0 > > > xhci0 at pci0 dev 21 function 0 "Intel Apollo Lake xHCI" rev 0x0b: msi, > > > xHCI > > > 1.0 > > > 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 > > > "Intel Apollo Lake LPC" rev 0x0b at pci0 dev 31 function 0 not configured > > > "Intel Apollo Lake SMBus" rev 0x0b at pci0 dev 31
Re: sysupgrade fails due to "CHECK AND RESET DATE" ?
19.10.2021 08:45, Otto Moerbeek пишет: On Mon, Oct 18, 2021 at 11:18:20PM +0300, kasak wrote: Hello everyone! I have one mini router, made from gigabyte GB-SBCAP4200 barebone It has nothing special. Just base openbsd, without any additional packages and modifications. for some reason, sysupgrade does not upgrade this system. It successfully boot new kernel, but do not process the upgrade, Just load 6.9 back. This is dmesg from loading 7.0 and further: OpenBSD 7.0 (RAMDISK_CD) #219: Thu Sep 30 14:32:42 MDT 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 8415617024 (8025MB) avail mem = 8156545024 (7778MB) random: good seed from bootblocks mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x79db7000 (50 entries) bios0: vendor American Megatrends Inc. version "F1" date 06/11/2018 bios0: Gigabyte Technology Co., Ltd. Default string acpi0 at bios0: ACPI 6.0 acpi0: tables DSDT FACP FPDT FIDT MCFG DBG2 DBGP HPET LPIT APIC NPKT PRAM WSMT SSDT SSDT SSDT SSDT SSDT SSDT SSDT UEFI TPM2 WDAT acpihpet0 at acpi0: 1920 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Pentium(R) CPU N4200 @ 1.10GHz, 1097.47 MHz, 06-5c-09 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu0: 1MB 64b/line 16-way L2 cache cpu0: apic clock running at 19MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.2.4.2.1.1, IBE cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 120 pins 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 2 (RP04) acpiprt5 at acpi0: bus 3 (RP05) acpiprt6 at acpi0: bus 4 (RP06) acpiec0 at acpi0: not present acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 acpicmos0 at acpi0 "PNP0C0C" at acpi0 not configured aplgpio0 at acpi0 GPO0 uid 1 addr 0xd0c5/0x76c irq 14, 78 pins aplgpio1 at acpi0 GPO1 uid 2 addr 0xd0c4/0x764 irq 14, 77 pins aplgpio2 at acpi0 GPO2 uid 3 addr 0xd0c7/0x674 irq 14, 47 pins aplgpio3 at acpi0 GPO3 uid 4 addr 0xd0c0/0x654 irq 14, 43 pins "INT33A1" at acpi0 not configured "MSFT0101" at acpi0 not configured "PNP0C0B" at acpi0 not configured acpicpu at acpi0 not configured acpipwrres at acpi0 not configured acpitz at acpi0 not configured pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Apollo Lake Host" rev 0x0b "Intel HD Graphics 505" rev 0x0b at pci0 dev 2 function 0 not configured "Intel Apollo Lake HD Audio" rev 0x0b at pci0 dev 14 function 0 not configured "Intel Apollo Lake TXE" rev 0x0b at pci0 dev 15 function 0 not configured ahci0 at pci0 dev 18 function 0 "Intel Apollo Lake AHCI" rev 0x0b: msi, AHCI 1.3.1 ahci0: PHY offline on port 0 ahci0: port 1: 6.0Gb/s scsibus0 at ahci0: 32 targets sd0 at scsibus0 targ 1 lun 0: naa.50026b7783a249ed sd0: 228936MB, 512 bytes/sector, 468862128 sectors, thin ppb0 at pci0 dev 19 function 0 "Intel Apollo Lake PCIE" rev 0xfb: msi pci1 at ppb0 bus 1 ppb1 at pci0 dev 19 function 1 "Intel Apollo Lake PCIE" rev 0xfb: msi pci2 at ppb1 bus 2 ppb2 at pci0 dev 19 function 2 "Intel Apollo Lake PCIE" rev 0xfb: msi pci3 at ppb2 bus 3 re0 at pci3 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G (0x4c00), msi, address e0:d5:5e:e7:50:4f rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0 ppb3 at pci0 dev 19 function 3 "Intel Apollo Lake PCIE" rev 0xfb: msi pci4 at ppb3 bus 4 re1 at pci4 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G (0x4c00), msi, address e0:d5:5e:e7:50:51 rgephy1 at re1 phy 7: RTL8251 PHY, rev. 0 xhci0 at pci0 dev 21 function 0 "Intel Apollo Lake xHCI" rev 0x0b: msi, xHCI 1.0 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 "Intel Apollo Lake LPC" rev 0x0b at pci0 dev 31 function 0 not configured "Intel Apollo Lake SMBus" rev 0x0b at pci0 dev 31 function 1 not configured isa0 at mainbus0 pckbc0 at isa0 port 0x60/5 irq 1 irq 12 efifb at mainbus0 not configured softraid0 at root scsibus1 at softraid0: 256 targets root on rd0a swap on rd0b dump on rd0b WARNING: CHECK AND RESET THE DATE! OpenBSD 6.9 (GENERIC.MP) #4: Tue Aug 10 08:12:23 MDT 2021 r...@syspatch-69-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8415617024 (8025MB) avail mem = 8145182720 (7767MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x79db7000 (50 entries) bios0: vendor American Megatrends Inc. version
Re: sysupgrade fails due to "CHECK AND RESET DATE" ?
On Mon, Oct 18, 2021 at 11:18:20PM +0300, kasak wrote: > Hello everyone! > > I have one mini router, made from gigabyte GB-SBCAP4200 barebone > > It has nothing special. Just base openbsd, without any additional packages > and modifications. > > for some reason, sysupgrade does not upgrade this system. > It successfully boot new kernel, but do not process the upgrade, Just load > 6.9 back. > > This is dmesg from loading 7.0 and further: > > OpenBSD 7.0 (RAMDISK_CD) #219: Thu Sep 30 14:32:42 MDT 2021 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD > real mem = 8415617024 (8025MB) > avail mem = 8156545024 (7778MB) > random: good seed from bootblocks > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x79db7000 (50 entries) > bios0: vendor American Megatrends Inc. version "F1" date 06/11/2018 > bios0: Gigabyte Technology Co., Ltd. Default string > acpi0 at bios0: ACPI 6.0 > acpi0: tables DSDT FACP FPDT FIDT MCFG DBG2 DBGP HPET LPIT APIC NPKT PRAM > WSMT SSDT SSDT SSDT SSDT SSDT SSDT SSDT UEFI TPM2 WDAT > acpihpet0 at acpi0: 1920 Hz > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Pentium(R) CPU N4200 @ 1.10GHz, 1097.47 MHz, 06-5c-09 > 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN > cpu0: 1MB 64b/line 16-way L2 cache > cpu0: apic clock running at 19MHz > cpu0: mwait min=64, max=64, C-substates=0.2.0.2.4.2.1.1, IBE > cpu at mainbus0: not configured > cpu at mainbus0: not configured > cpu at mainbus0: not configured > ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 120 pins > 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 2 (RP04) > acpiprt5 at acpi0: bus 3 (RP05) > acpiprt6 at acpi0: bus 4 (RP06) > acpiec0 at acpi0: not present > acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 > acpicmos0 at acpi0 > "PNP0C0C" at acpi0 not configured > aplgpio0 at acpi0 GPO0 uid 1 addr 0xd0c5/0x76c irq 14, 78 pins > aplgpio1 at acpi0 GPO1 uid 2 addr 0xd0c4/0x764 irq 14, 77 pins > aplgpio2 at acpi0 GPO2 uid 3 addr 0xd0c7/0x674 irq 14, 47 pins > aplgpio3 at acpi0 GPO3 uid 4 addr 0xd0c0/0x654 irq 14, 43 pins > "INT33A1" at acpi0 not configured > "MSFT0101" at acpi0 not configured > "PNP0C0B" at acpi0 not configured > acpicpu at acpi0 not configured > acpipwrres at acpi0 not configured > acpitz at acpi0 not configured > pci0 at mainbus0 bus 0 > pchb0 at pci0 dev 0 function 0 "Intel Apollo Lake Host" rev 0x0b > "Intel HD Graphics 505" rev 0x0b at pci0 dev 2 function 0 not configured > "Intel Apollo Lake HD Audio" rev 0x0b at pci0 dev 14 function 0 not > configured > "Intel Apollo Lake TXE" rev 0x0b at pci0 dev 15 function 0 not configured > ahci0 at pci0 dev 18 function 0 "Intel Apollo Lake AHCI" rev 0x0b: msi, AHCI > 1.3.1 > ahci0: PHY offline on port 0 > ahci0: port 1: 6.0Gb/s > scsibus0 at ahci0: 32 targets > sd0 at scsibus0 targ 1 lun 0: > naa.50026b7783a249ed > sd0: 228936MB, 512 bytes/sector, 468862128 sectors, thin > ppb0 at pci0 dev 19 function 0 "Intel Apollo Lake PCIE" rev 0xfb: msi > pci1 at ppb0 bus 1 > ppb1 at pci0 dev 19 function 1 "Intel Apollo Lake PCIE" rev 0xfb: msi > pci2 at ppb1 bus 2 > ppb2 at pci0 dev 19 function 2 "Intel Apollo Lake PCIE" rev 0xfb: msi > pci3 at ppb2 bus 3 > re0 at pci3 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G > (0x4c00), msi, address e0:d5:5e:e7:50:4f > rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0 > ppb3 at pci0 dev 19 function 3 "Intel Apollo Lake PCIE" rev 0xfb: msi > pci4 at ppb3 bus 4 > re1 at pci4 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G > (0x4c00), msi, address e0:d5:5e:e7:50:51 > rgephy1 at re1 phy 7: RTL8251 PHY, rev. 0 > xhci0 at pci0 dev 21 function 0 "Intel Apollo Lake xHCI" rev 0x0b: msi, xHCI > 1.0 > 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 > "Intel Apollo Lake LPC" rev 0x0b at pci0 dev 31 function 0 not configured > "Intel Apollo Lake SMBus" rev 0x0b at pci0 dev 31 function 1 not configured > isa0 at mainbus0 > pckbc0 at isa0 port 0x60/5 irq 1 irq 12 > efifb at mainbus0 not configured > softraid0 at root > scsibus1 at softraid0: 256 targets > root on rd0a swap on rd0b dump on rd0b > WARNING: CHECK AND RESET THE DATE! > OpenBSD 6.9 (GENERIC.MP) #4: Tue Aug 10 08:12:23 MDT 2021 > r...@syspatch-69-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 8415617024 (8025MB) > avail mem = 8145182720 (7767MB) > random: good seed from bootblocks >
sysupgrade fails due to "CHECK AND RESET DATE" ?
Hello everyone! I have one mini router, made from gigabyte GB-SBCAP4200 barebone It has nothing special. Just base openbsd, without any additional packages and modifications. for some reason, sysupgrade does not upgrade this system. It successfully boot new kernel, but do not process the upgrade, Just load 6.9 back. This is dmesg from loading 7.0 and further: OpenBSD 7.0 (RAMDISK_CD) #219: Thu Sep 30 14:32:42 MDT 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 8415617024 (8025MB) avail mem = 8156545024 (7778MB) random: good seed from bootblocks mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x79db7000 (50 entries) bios0: vendor American Megatrends Inc. version "F1" date 06/11/2018 bios0: Gigabyte Technology Co., Ltd. Default string acpi0 at bios0: ACPI 6.0 acpi0: tables DSDT FACP FPDT FIDT MCFG DBG2 DBGP HPET LPIT APIC NPKT PRAM WSMT SSDT SSDT SSDT SSDT SSDT SSDT SSDT UEFI TPM2 WDAT acpihpet0 at acpi0: 1920 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Pentium(R) CPU N4200 @ 1.10GHz, 1097.47 MHz, 06-5c-09 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu0: 1MB 64b/line 16-way L2 cache cpu0: apic clock running at 19MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.2.4.2.1.1, IBE cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 120 pins 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 2 (RP04) acpiprt5 at acpi0: bus 3 (RP05) acpiprt6 at acpi0: bus 4 (RP06) acpiec0 at acpi0: not present acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 acpicmos0 at acpi0 "PNP0C0C" at acpi0 not configured aplgpio0 at acpi0 GPO0 uid 1 addr 0xd0c5/0x76c irq 14, 78 pins aplgpio1 at acpi0 GPO1 uid 2 addr 0xd0c4/0x764 irq 14, 77 pins aplgpio2 at acpi0 GPO2 uid 3 addr 0xd0c7/0x674 irq 14, 47 pins aplgpio3 at acpi0 GPO3 uid 4 addr 0xd0c0/0x654 irq 14, 43 pins "INT33A1" at acpi0 not configured "MSFT0101" at acpi0 not configured "PNP0C0B" at acpi0 not configured acpicpu at acpi0 not configured acpipwrres at acpi0 not configured acpitz at acpi0 not configured pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Apollo Lake Host" rev 0x0b "Intel HD Graphics 505" rev 0x0b at pci0 dev 2 function 0 not configured "Intel Apollo Lake HD Audio" rev 0x0b at pci0 dev 14 function 0 not configured "Intel Apollo Lake TXE" rev 0x0b at pci0 dev 15 function 0 not configured ahci0 at pci0 dev 18 function 0 "Intel Apollo Lake AHCI" rev 0x0b: msi, AHCI 1.3.1 ahci0: PHY offline on port 0 ahci0: port 1: 6.0Gb/s scsibus0 at ahci0: 32 targets sd0 at scsibus0 targ 1 lun 0: naa.50026b7783a249ed sd0: 228936MB, 512 bytes/sector, 468862128 sectors, thin ppb0 at pci0 dev 19 function 0 "Intel Apollo Lake PCIE" rev 0xfb: msi pci1 at ppb0 bus 1 ppb1 at pci0 dev 19 function 1 "Intel Apollo Lake PCIE" rev 0xfb: msi pci2 at ppb1 bus 2 ppb2 at pci0 dev 19 function 2 "Intel Apollo Lake PCIE" rev 0xfb: msi pci3 at ppb2 bus 3 re0 at pci3 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G (0x4c00), msi, address e0:d5:5e:e7:50:4f rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0 ppb3 at pci0 dev 19 function 3 "Intel Apollo Lake PCIE" rev 0xfb: msi pci4 at ppb3 bus 4 re1 at pci4 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G (0x4c00), msi, address e0:d5:5e:e7:50:51 rgephy1 at re1 phy 7: RTL8251 PHY, rev. 0 xhci0 at pci0 dev 21 function 0 "Intel Apollo Lake xHCI" rev 0x0b: msi, xHCI 1.0 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 "Intel Apollo Lake LPC" rev 0x0b at pci0 dev 31 function 0 not configured "Intel Apollo Lake SMBus" rev 0x0b at pci0 dev 31 function 1 not configured isa0 at mainbus0 pckbc0 at isa0 port 0x60/5 irq 1 irq 12 efifb at mainbus0 not configured softraid0 at root scsibus1 at softraid0: 256 targets root on rd0a swap on rd0b dump on rd0b WARNING: CHECK AND RESET THE DATE! OpenBSD 6.9 (GENERIC.MP) #4: Tue Aug 10 08:12:23 MDT 2021 r...@syspatch-69-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8415617024 (8025MB) avail mem = 8145182720 (7767MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x79db7000 (50 entries) bios0: vendor American Megatrends Inc. version "F1" date 06/11/2018 bios0: Gigabyte Technology Co., Ltd. Default string acpi0
Re: Sysupgrade fails with "cannot create SHA256.sig: Permission denied"
Bingo! You are right on, as /home is an nfs mount. Unmounting it allows sysupgrade to work. Thanks! Dave Raymond On 6/17/20, Florian Obser wrote: > Wild guess, /home is an nfs mount or mounted read-only? That's not going to > work unfortunately. > > > On 17 June 2020 22:23:13 CEST, "Raymond, David" > wrote: >>I am trying to upgrade a bunch of machines from 6.6 to 6.7 using >>sysupgrade and I get the message >> >>/usr/sbin/sysupgrade[136]: cannot create SHA256.sig: Permission denied >> >>These are AMD64 machines on wired internet at my university. >>Sysupgrade worked fine on a laptop and on an AMD desktop using my home >>internet provider. >> >>Any hints? Might there be some protocol that is blocked by the >>university network? When I boot bsd.rd directly (after having been >>locally verified), the upgrade works fine. >> >>Dave Raymond > > -- > Sent from a mobile device. Please excuse poor formating. > -- David J. Raymond david.raym...@nmt.edu http://kestrel.nmt.edu/~raymond
Re: Sysupgrade fails with "cannot create SHA256.sig: Permission denied"
Wild guess, /home is an nfs mount or mounted read-only? That's not going to work unfortunately. On 17 June 2020 22:23:13 CEST, "Raymond, David" wrote: >I am trying to upgrade a bunch of machines from 6.6 to 6.7 using >sysupgrade and I get the message > >/usr/sbin/sysupgrade[136]: cannot create SHA256.sig: Permission denied > >These are AMD64 machines on wired internet at my university. >Sysupgrade worked fine on a laptop and on an AMD desktop using my home >internet provider. > >Any hints? Might there be some protocol that is blocked by the >university network? When I boot bsd.rd directly (after having been >locally verified), the upgrade works fine. > >Dave Raymond -- Sent from a mobile device. Please excuse poor formating.
Sysupgrade fails with "cannot create SHA256.sig: Permission denied"
I am trying to upgrade a bunch of machines from 6.6 to 6.7 using sysupgrade and I get the message /usr/sbin/sysupgrade[136]: cannot create SHA256.sig: Permission denied These are AMD64 machines on wired internet at my university. Sysupgrade worked fine on a laptop and on an AMD desktop using my home internet provider. Any hints? Might there be some protocol that is blocked by the university network? When I boot bsd.rd directly (after having been locally verified), the upgrade works fine. Dave Raymond -- David J. Raymond david.raym...@nmt.edu http://kestrel.nmt.edu/~raymond
Re: sysupgrade fails
On Mon, Jan 6, 2020 at 1:30 PM Christer Solskogen < christer.solsko...@gmail.com> wrote: > > On Mon, Jan 6, 2020 at 12:27 PM Stuart Henderson > wrote: > >> >> Are you able to ^Z at that point and run "mount"? (I can't remember if >> sysupgrade lets you do this). >> >> > I can. My root disk is not mounted. > > Sorry, something was wrong with my console, so it wasn't showing. But now it does (that damn cable wasn't inserted properly) hugs# mount /dev/rd0a on / type ffs (local) /dev/sd0a on /mnt type ffs (local, read-only) I can unmount /mnt manually. No problem there. Can you show your /etc/fstab? >> > > 89100ad7b8b8d77a.b none swap sw > 89100ad7b8b8d77a.a / ffs rw,wxallowed,softdep,noatime 1 1 > Same problem without softdep, in case you were wondering.
Re: sysupgrade fails
On Mon, Jan 6, 2020 at 12:27 PM Stuart Henderson wrote: > > Are you able to ^Z at that point and run "mount"? (I can't remember if > sysupgrade lets you do this). > > I can. My root disk is not mounted. Can you show your /etc/fstab? > 89100ad7b8b8d77a.b none swap sw 89100ad7b8b8d77a.a / ffs rw,wxallowed,softdep,noatime 1 1
Re: sysupgrade fails
On 2020-01-05, Christer Solskogen wrote:
> Hi!
>
> On one(out of two!) of my APUs sysupgrade fails, and I'm having trouble
> understanding why.
> This is what happens:
>
> Available disks are: sd0.
> Which disk is the root disk? ('?' for details) [sd0] sd0
> Checking root filesystem (fsck -fp /dev/sd0a)... OK.
> Mounting root filesystem (mount -o ro /dev/sd0a /mnt)... OK.
> Force checking of clean non-root filesystems? [no] no
> umount: /mnt: Device busy
> Can't umount sd0a!
>
> This does not happen if I run the upgrade manually by downloading a newer
> bsd.rd and boot that.
> This is a APU2c4 - My APU1 does not have this problem.
>
Are you able to ^Z at that point and run "mount"? (I can't remember if
sysupgrade lets you do this).
Can you show your /etc/fstab?
Re: sysupgrade fails
On Sun, Jan 5, 2020 at 1:11 PM Anders Andersson wrote: > > > Not sure if it's in any way related when it comes to doing a > sysupgrade compared to a clean install, but did you see this thread > and the corresponding BIOS upgrade? > > http://openbsd-archive.7691.n7.nabble.com/APU2-fails-to-boot-on-OpenBSD-6-6-current-521-td379219.html > > https://github.com/pcengines/coreboot/issues/356 Yes-ish. I was running apu2_v4.10.0.3, but upgraded to apu2_v4.11.0.2 today. Because of the problems reported I didn't run apu2_v4.11.0.1. Not sure if the bios has anything to do with it. I do run the same bios version on my apu1, and that does not have this problem.
Re: sysupgrade fails
On Sun, Jan 5, 2020 at 1:05 PM Christer Solskogen
wrote:
>
> Sorry, I forgot to telll you that I run current. I was upgrading a snapshot
> from 1st of january to the latest one. But this has happened before (It
> looks like the last time sysupgrade did successfully work was 4th of
> December)
>
> On Sun, Jan 5, 2020 at 12:58 PM Christer Solskogen <
> christer.solsko...@gmail.com> wrote:
>
> > Hi!
> >
> > On one(out of two!) of my APUs sysupgrade fails, and I'm having trouble
> > understanding why.
> > This is what happens:
> >
> > Available disks are: sd0.
> > Which disk is the root disk? ('?' for details) [sd0] sd0
> > Checking root filesystem (fsck -fp /dev/sd0a)... OK.
> > Mounting root filesystem (mount -o ro /dev/sd0a /mnt)... OK.
> > Force checking of clean non-root filesystems? [no] no
> > umount: /mnt: Device busy
> > Can't umount sd0a!
> >
> > This does not happen if I run the upgrade manually by downloading a newer
> > bsd.rd and boot that.
> > This is a APU2c4 - My APU1 does not have this problem.
> >
Not sure if it's in any way related when it comes to doing a
sysupgrade compared to a clean install, but did you see this thread
and the corresponding BIOS upgrade?
http://openbsd-archive.7691.n7.nabble.com/APU2-fails-to-boot-on-OpenBSD-6-6-current-521-td379219.html
https://github.com/pcengines/coreboot/issues/356
Re: sysupgrade fails
Sorry, I forgot to telll you that I run current. I was upgrading a snapshot
from 1st of january to the latest one. But this has happened before (It
looks like the last time sysupgrade did successfully work was 4th of
December)
On Sun, Jan 5, 2020 at 12:58 PM Christer Solskogen <
christer.solsko...@gmail.com> wrote:
> Hi!
>
> On one(out of two!) of my APUs sysupgrade fails, and I'm having trouble
> understanding why.
> This is what happens:
>
> Available disks are: sd0.
> Which disk is the root disk? ('?' for details) [sd0] sd0
> Checking root filesystem (fsck -fp /dev/sd0a)... OK.
> Mounting root filesystem (mount -o ro /dev/sd0a /mnt)... OK.
> Force checking of clean non-root filesystems? [no] no
> umount: /mnt: Device busy
> Can't umount sd0a!
>
> This does not happen if I run the upgrade manually by downloading a newer
> bsd.rd and boot that.
> This is a APU2c4 - My APU1 does not have this problem.
>
sysupgrade fails
Hi!
On one(out of two!) of my APUs sysupgrade fails, and I'm having trouble
understanding why.
This is what happens:
Available disks are: sd0.
Which disk is the root disk? ('?' for details) [sd0] sd0
Checking root filesystem (fsck -fp /dev/sd0a)... OK.
Mounting root filesystem (mount -o ro /dev/sd0a /mnt)... OK.
Force checking of clean non-root filesystems? [no] no
umount: /mnt: Device busy
Can't umount sd0a!
This does not happen if I run the upgrade manually by downloading a newer
bsd.rd and boot that.
This is a APU2c4 - My APU1 does not have this problem.
