Re: 13-CURRENT won't boot after switch to sysutils/openzfs

2020-08-22 Thread Ryan Moeller
On 8/22/20 7:39 PM, marco wrote: On Sat, Aug 22, 2020 at 10:10:14PM +, you (marco) sent the following to [freebsd-current] : On Sat, Aug 22, 2020 at 04:48:48PM +, you (marco) sent the following to [freebsd-current] : On Sat, Aug 22, 2020 at 12:31:24PM -0400, you (Ryan Moeller) sent

Re: 13-CURRENT won't boot after switch to sysutils/openzfs

2020-08-22 Thread marco
On Sat, Aug 22, 2020 at 10:10:14PM +, you (marco) sent the following to [freebsd-current] : > On Sat, Aug 22, 2020 at 04:48:48PM +, you (marco) sent the following to > [freebsd-current] : > > On Sat, Aug 22, 2020 at 12:31:24PM -0400, you (Ryan Moeller) sent the > > following to [freebsd-

Re: freebsd-current Digest, Vol 877, Issue 7

2020-08-22 Thread Vanbreukelingen Ltd.
replying to myself at 1am: 1. completely new-install 2. kmod-legacy and kmd-stable built 3. svn up; make kernel 4. linux-c7 from /ports installed 5. kld_load x 2 6. fine drm initialized but when trying to sddm or xinit or startx or whatever I get a loong debug output message with self r

Re: 13-CURRENT won't boot after switch to sysutils/openzfs

2020-08-22 Thread marco
On Sat, Aug 22, 2020 at 04:48:48PM +, you (marco) sent the following to [freebsd-current] : > On Sat, Aug 22, 2020 at 12:31:24PM -0400, you (Ryan Moeller) sent the > following to [freebsd-current] : > > > > > So besides not being able to boot > from the openzfs 2020080800 package install, I

Re: 13-CURRENT won't boot after switch to sysutils/openzfs

2020-08-22 Thread marco
On Sat, Aug 22, 2020 at 12:31:24PM -0400, you (Ryan Moeller) sent the following to [freebsd-current] : > > > So besides not being able to boot from the openzfs 2020080800 package > > install, I can't figure out why I can't upgrade the openzfs pkg to > > 2020081800 (which is the latest one in po

Re: 13-CURRENT won't boot after switch to sysutils/openzfs

2020-08-22 Thread Ryan Moeller
On 8/22/20 12:27 PM, marco wrote: On Sat, Aug 22, 2020 at 09:47:49AM -0400, you (Ryan Moeller) sent the following to [freebsd-current] : On 8/22/20 9:29 AM, Ryan Moeller wrote: When switching from base ZFS to sysutils/openzfs 2020080800 the boot process fails. The most recent version (20200

Re: 13-CURRENT won't boot after switch to sysutils/openzfs

2020-08-22 Thread marco
On Sat, Aug 22, 2020 at 09:47:49AM -0400, you (Ryan Moeller) sent the following to [freebsd-current] : > > On 8/22/20 9:29 AM, Ryan Moeller wrote: > >> > >> When switching from base ZFS to sysutils/openzfs 2020080800 the boot > >> process fails. > > > > The most recent version (2020081800) fixes

Re: 13-CURRENT won't boot after switch to sysutils/openzfs

2020-08-22 Thread Ryan Moeller
On 8/22/20 9:29 AM, Ryan Moeller wrote: On 8/22/20 7:49 AM, marco wrote: I'm running r364030.   [~] uname -apKU   FreeBSD harbinger 13.0-CURRENT FreeBSD 13.0-CURRENT #5 r364030: Tue Aug   11 07:15:59 UTC 2020 root@harbinger:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64   amd64 1300

Re: 13-CURRENT won't boot after switch to sysutils/openzfs

2020-08-22 Thread Ryan Moeller
On 8/22/20 7:49 AM, marco wrote: I'm running r364030. [~] uname -apKU FreeBSD harbinger 13.0-CURRENT FreeBSD 13.0-CURRENT #5 r364030: Tue Aug 11 07:15:59 UTC 2020 root@harbinger:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64 amd64 1300105 1300105 When switching from base ZF

13-CURRENT won't boot after switch to sysutils/openzfs

2020-08-22 Thread marco
I'm running r364030. [~] uname -apKU FreeBSD harbinger 13.0-CURRENT FreeBSD 13.0-CURRENT #5 r364030: Tue Aug 11 07:15:59 UTC 2020 root@harbinger:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64 amd64 1300105 1300105 When switching from base ZFS to sysutils/openzfs 2020080800 the boot

Re: /usr/lib/libomp.so : is there a reason that aarch64 does not have such by default?

2020-08-22 Thread myfreeweb
On August 21, 2020 6:52:23 PM UTC, Mark Millard via freebsd-arm wrote: >My context: head ( currently at -r363590 ) > >man src.conf is explicit that WITHOUT_OPENMP is the default for >aarch64 (for example). [...] >Nothing stands out for why WITH_OPENMP is in use by default only >for amd64, i386