Re: Loading zfs module results in hangup on i386

From: Yasuhiro Kimura Subject: Re: Loading zfs module results in hangup on i386 Date: Sat, 08 May 2021 07:44:15 +0900 (JST) >> Now I think I know what is the source of problem. After all, on >> 13.0-RELEASE i386 system simply loading zfs module results in system >> hang up

Re: Loading zfs module results in hangup on i386

From: Yasuhiro Kimura Subject: Loading zfs module results in hangup on i386 (Re: Install of 13.0-RELEASE i386 with ZFS root hangs up) Date: Sat, 08 May 2021 07:31:47 +0900 (JST) > Now I think I know what is the source of problem. After all, on > 13.0-RELEASE i386 system simply loadi

Loading zfs module results in hangup on i386 (Re: Install of 13.0-RELEASE i386 with ZFS root hangs up)

From: Yasuhiro Kimura Subject: Install of 13.0-RELEASE i386 with ZFS root hangs up Date: Fri, 07 May 2021 21:47:59 +0900 (JST) > Hello, > > Does anyone succeed to install 13.0-RELEASE i386 with ZFS root? > > I tried this with VirtualBox and VMware Player on Windows with

Re: Install of 13.0-RELEASE i386 with ZFS root hangs up

From: 8zwk...@oldach.net (Helge Oldach) Subject: Re: Install of 13.0-RELEASE i386 with ZFS root hangs up Date: Fri, 7 May 2021 15:41:45 +0200 (CEST) > Yasuhiro Kimura wrote on Fri, 07 May 2021 14:47:59 +0200 (CEST): >> Does anyone succeed to install 13.0-RELEASE i386 with

Install of 13.0-RELEASE i386 with ZFS root hangs up

' at 'ZFS Configuration' menu and type return key. If I select UFS root installation completes successfully. So the problem is specific to ZFS root. --- Yasuhiro Kimura ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo

Re: How to make 'named' rc script invokded earlier at boot time

pdate' in the result of rcorder. --- Yasuhiro Kimura ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: How to make 'named' rc script invokded earlier at boot time

From: Yasuhiro Kimura Subject: Re: How to make 'named' rc script invokded earlier at boot time Date: Fri, 30 Apr 2021 17:18:26 +0900 (JST) >> The only way I can see is modify the named rc script and add the >> services that needs named to be started on the BEFORE line at the

Re: How to make 'named' rc script invokded earlier at boot time

ed rc script and add the > services that needs named to be started on the BEFORE line at the > beginning of the script. Mind you, it really needs to start after > syslog (unless you log directly to files and do not use syslog.) Thanks for advice. I'll try it.

Re: How to make 'named' rc script invokded earlier at boot time

/auditdistd /etc/rc.d/nfsclient /usr/local/etc/rc.d/tpmd /usr/local/etc/rc.d/tcsd /etc/rc.d/hastd /usr/local/etc/rc.d/named /etc/rc.d/SERVERS (snip) 'named' is still later than 'ntpdate' on my home server. --- Yasuhiro Kimura ___ freebsd-stable@freebsd

How to make 'named' rc script invokded earlier at boot time

. So it seems evaluation of rcorder(8) is changed between 12.2-RELASE and 13.0-RELEASE. Then is there any way to make 'named' rc script invoked earlier at boot time on 13.0-RELEASE? Best Regards. --- Yasuhiro Kimura ___ freebsd-stable@freebsd.org mailing

Re: Setting for displaying utf8 characters on all vt consoles results in panic on 14-CURRENT and 13.0-ALPHA3

rds. --- Yasuhiro Kimura ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Setting for displaying utf8 characters on all vt consoles results in panic on 14-CURRENT and 13.0-ALPHA3

From: Yasuhiro Kimura Subject: Setting for displaying utf8 characters on all vt consoles results in panic on 14-CURRENT and 13.0-ALPHA3 Date: Mon, 01 Feb 2021 11:41:35 +0900 (JST) > To display utf8 characters on all vt console I did following settings. > > 1. Download GNU Unifont

Setting for displaying utf8 characters on all vt consoles results in panic on 14-CURRENT and 13.0-ALPHA3

:30:28 JST 2021 ro...@rolling-vm-freebsd5.home.utahime.org:/usr0/freebsd/src/obj/usr0/freebsd/src/git/amd64.amd64/sys/GENERIC amd64 --- Yasuhiro Kimura ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/free

Re: No more update on stable/12

orrect and just the learning process of git or is something wrong > with my git clone? Which repository do you use?. Currently new canonical src repository (https://git.freebsd.org/src.git) is updated but not mirrored to GitHub yet. --- Yasuhiro Kimura

Re: Size of EFI system partition is much smaller when it is mounted

I'll try reformatting EFI system partition. --- Yasuhiro KIMURA ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Size of EFI system partition is much smaller when it is mounted

/mnt -- Is there any bug fix about it that is merged to 12.x but not 11.x? Best Regards. --- Yasuhiro KIMURA ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsub

Re: `efivar -l` fails on UEFI booted 11.4-RELEASE

d to `kldload efirt` or add `options EFIRT` to > your kernel config before efivar/efibootmgr become usable. Thank you for reply. After loading efirt.ko `efivar -l` succesfully lists UEFI environment variables. --- Yasuhiro KIMURA ___ freebsd-stable@fr

`efivar -l` fails on UEFI booted 11.4-RELEASE

root@rolling-vm-freebsd3[161]# efivar -l efivar: Error listing names: No such file or directory root@rolling-vm-freebsd3[162]# It also happens with latest (20200625) 11-STABLE snapshot, but not with either 12.1-RELEASE or 13-CURRENT. --- Yasuhiro KIMURA

Re: Buildworld and buildkernel with very slow compilation, recently

bugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely disable the most expensive debugging functionality run "ln -s 'abort:false,junk:false' /etc/malloc.conf".) --- Yasuhiro KIMURA ___ freebsd-stable@freeb

Re: php56

m will not work under php7* > > context is 11-stable/amd64 > > thanks, svn checkout -r 488893 /usr/ports --- Yasuhiro KIMURA ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe

Re: Getting value of MAKEOBJDIRPREFIX with 'make -V MAKEOBJDIRPREFIX'

From: Yasuhiro KIMURA Subject: Re: Getting value of MAKEOBJDIRPREFIX with 'make -V MAKEOBJDIRPREFIX' Date: Sat, 17 Nov 2018 09:18:53 +0900 (JST) > As far as I read this, behavior change of 'make -V MAKEOBJDIRPREFIX` > doesn't seem intentional. So I'll submit bug report. Submitted.

Re: Getting value of MAKEOBJDIRPREFIX with 'make -V MAKEOBJDIRPREFIX'

From: Yasuhiro KIMURA Subject: Getting value of MAKEOBJDIRPREFIX with 'make -V MAKEOBJDIRPREFIX' Date: Sat, 17 Nov 2018 01:57:58 +0900 (JST) > Then is this just bug? Or are there any reason that behavior is > changed from 11.x to 12.x and later? To find when behavior changed I bisecte

Getting value of MAKEOBJDIRPREFIX with 'make -V MAKEOBJDIRPREFIX'

-C /usr0/freebsd/base/stable/12 yasu@eastasia[2404]% I used env(1) to customize but I got same results when I use src-env.conf. Then is this just bug? Or are there any reason that behavior is changed from 11.x to 12.x and later? Best Regards. --- Yasuhiro KIMURA

Re: Console is broken after updating to 11.2-RELEASE

I submitted this problem as following bug report. Bug 229235 - vt(4) of 11.2-RELEASE is broken with hardware dependent problem. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229235 Just FYI. --- Yasuhiro KIMURA ___ freebsd-stable@freebsd.org

Re: Console is broken after updating to 11.2-RELEASE

bose="YES" > > Hope this helps! Thank you for information. I added above lines to /boot/loader.conf and rebooted system. Then all boot messages are displayed and console works fine! --- Yasuhiro KIMURA ___ freebsd-stable@freebsd.org mailing

Re: Console is broken after updating to 11.2-RELEASE

From: Warner Losh Subject: Re: Console is broken after updating to 11.2-RELEASE Date: Fri, 22 Jun 2018 05:03:43 -0600 > UEFI or legacy boot? Is a BMC involved? Legacy boot. And BMC is not involved. --- Yasuhiro KIMURA ___ freebsd-stable@freebsd.

Re: Console is broken after updating to 11.2-RELEASE

asu@maybe[2016]% LANG=C ls -l /var/log/console.log ~ -rw-r--r-- 1 root wheel 9568 Jun 22 20:29 /var/log/console.log yasu@maybe[2016]% So my case seems to be different from yours. --- Yasuhiro KIMURA ___ freebsd-stable@freebsd.

Re: Console is broken after updating to 11.2-RELEASE

From: Yasuhiro KIMURA Subject: Console is broken after updating to 11.2-RELEASE Date: Fri, 22 Jun 2018 17:07:20 +0900 (JST) > With the commit of r335510 releng/11.2 switched to -RELEASE. So I > updated one of my home server from 11.1-RELEASE-p11 to 11.2-RELEASE. > > But when I rebo

Re: Console is broken after updating to 11.2-RELEASE,Re: Console is broken after updating to 11.2-RELEASE

ll. Folloging is loader.conf of my home server in question. yasu@maybe[2019]% cat /boot/loader.conf kern.geom.label.disk_ident.enable="0" kern.geom.label.gptid.enable="0" #zfs_load="YES" yasu@maybe[2020]% --- Yasuhiro KIMURA

Console is broken after updating to 11.2-RELEASE

://www.eizoglobal.com/support/db/products/model/L565) M/B and display are connected with analog VGA. Does anyone experiences same problem? Are there any solution or workaound? Best Regards. --- Yasuhiro KIMURA ___ freebsd-stable@freebsd.org mailing list

Re: syslogd became silent between 11.2-PRERELEASE r334874 and r335282

ebuild and reinstall /usr/sbin/syslogd and /usr/bin/wall on both host and jail. 3. Restart syslogd on both host and jail. And if the problem is dissapeared, then you should open bug report. Best, --- Yasuhiro KIMURA ___ freebsd-stable@freebsd.org mailin

Two problems about ASUS N3150I-C

to the latter are cause of NIC hangup. Then, are there any way to fix these problems or investigate why they happens? Any suggestions or comments are welcome. --- Yasuhiro KIMURA ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman

Re: Freebsd 10 to 11 sendmail compile issues..

rouble. So you should keep above steps anyway. --- Yasuhiro KIMURA ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"