New loader (installed with ALPHA3) complains about missing modules but doesn't say what it needed
Hello FreeBSD, When I rebuilt NanoBSD image from CYRRENT r336582 to ALPHA3 r338399 loader starts to complain that it could not find required module(s). But I don't have any in my /boot/loader.conf and I didn't change anything in my configs. Unfortunately, loader doesn't provide any details: which modules are required. -- Best regards, Lev mailto:l...@freebsd.org ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Regression: ALPHA3 can not properly init diskless / nanobsd system
Hello FreeBSD, I have NanoBSD system built from and it works. It creates THREE memory filesystems, as needed: % mount | grep /dev/md /dev/md0 on /etc (ufs, local) /dev/md1 on /var (ufs, local) /dev/md2 on /var/tmp (ufs, local) % But same system built from ALPHA3 sources (r338399 to be exact) doesn't create /etc in-memory overlay, and can not copy SSHD keys and create host.conf. After that sshd could not start. New version doesn't properly create overlay for /etc: % mount | grep /dev/md /dev/md1 on /var (ufs, local) /dev/md2 on /var/tmp (ufs, local) % All configuration files are the same. -- Best regards, Lev mailto:l...@freebsd.org ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r336921 broke booting on MBP 2017, EFIRT related
Am 31.08.18 um 10:27 schrieb Konstantin Belousov: > On Thu, Aug 30, 2018 at 10:12:33PM +0300, Konstantin Belousov wrote: >> On Thu, Aug 30, 2018 at 12:22:36PM +0300, Yuri Pankov wrote: >>> Sorry, I accidentally took the discussion off-list, where Konstantin >>> provided some more patches. I'm attaching the one that finally worked >>> for me. It also adds some diagnostic prints which require bootverbose >>> to be enabled. >> >> This patch requires some more work to make it committable. >> Do not try to build it with efirt device in the kernel config, >> only efirt.ko works, but it can be preloaded from loader. > > A version of the patch which finishes items which I wanted > to handle, is available both for review and for testing at > https://reviews.freebsd.org/D16972 . > I tried the patches from D16972 and it seems to work on a DELL Latitude E6520. It now boots with OPTIONS EFIRT and without efi.rt.disabled=1. Many thanks! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: r336921 broke booting on MBP 2017, EFIRT related
On Thu, Aug 30, 2018 at 10:12:33PM +0300, Konstantin Belousov wrote: > On Thu, Aug 30, 2018 at 12:22:36PM +0300, Yuri Pankov wrote: > > Sorry, I accidentally took the discussion off-list, where Konstantin > > provided some more patches. I'm attaching the one that finally worked > > for me. It also adds some diagnostic prints which require bootverbose > > to be enabled. > > This patch requires some more work to make it committable. > Do not try to build it with efirt device in the kernel config, > only efirt.ko works, but it can be preloaded from loader. A version of the patch which finishes items which I wanted to handle, is available both for review and for testing at https://reviews.freebsd.org/D16972 . ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: NFS via IPv6 between 11.2-REL amd64 and larger (>45 files) directories?
Hi! > As Rick told me there's a ongoing debate on this, here's a copy > from my mail to stable@: PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231050 -- p...@freebsd.org +49 171 3101372 2 years to go ! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: NFS via IPv6 between 11.2-REL amd64 and larger (>45 files) directories?
Hi! As Rick told me there's a ongoing debate on this, here's a copy from my mail to stable@: I've seen a strange effect: NFS via IPv6 between 11.2-REL amd64 boxes failed for directories with more than 45 files or directories. Small directories worked. It seems to be an issue with ipv6 fragmentation (?), as can be seen by tcpdump: 17:54:16.855978 IP6 nfs-serv > nfs-client frag (0|1448) 2049 > 709: NFS reply xid 1536109002 reply ok 1440 readdir 17:54:16.855979 IP6 nfs-serv > nfs-client frag (1448|36) As soon as the NFS request is sent with fragments, it stalls. Using TCP or IPv4 for the nfs mount works, UDP fails. -- p...@freebsd.org +49 171 3101372 2 years to go ! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
