Repetitive Options Request Slows Boot

I'm quite happily running FreeBSD/XFCE on a Dell 7490 laptop, but one issue has left me curious. It seems to take an unexpectedly long time to boot, and one of the reasons is that during the boot process I see a repeated entry that says:

Options:
- T TERM
- V print curses-version
- x do not try to clear scrollback

I see this in particular after the wifi driver loads at boot, when it repeats itself ten or fifteen times. There are other times in the boot process when it also repeats. Is there some setting in the boot section that I should have included? Thanks in advance.
 
What's in rc.conf?
SirDice: thanks for responding! My rc.conf looks like this:

Code:
hostname="freebie"
wlans_iwlwifi0="wlan0"
ifconfig_wlan0="WPA  DHCP"
ifconfig_wlan0_ipv6="inet6 accept_rtadv"
sshd_enable="YES"
ntpd_enable="YES"
ntpd_sync_on_start="YES"
ntpd_flags="-g"
clear tmp_enable="YES"
powerd_enable="YES"
moused_enable="YES"
# Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable
dumpdev="AUTO"
zfs_enable="YES"
kld_list="i915kms snd_hda"
dbus_enable="YES"
lightdm_enable="YES"
networkmgr_enable="YES"
ifconfig_em0="DHCP"
cupsd_enable="YES"
firewall_enable="YES"
firewall_quiet="YES"
firewall_type="workstation"
firewall_myservices="80 443"
firewall_allowservices="any"
firewall_logdeny="YES"
 
there is a missing underscore: clear_tmp_enable="YES"
Nice catch.

Without underscore /usr/bin/clear is executed, not /etc/rc.d/cleartmp script.
Rich (BB code):
% clear tmp_enable="YES"
Usage: clear [options]

Options:
  -T TERM     use this instead of $TERM
  -V          print curses-version
  -x          do not try to clear scrollback
 
Nice catch.

Without underscore /usr/bin/clear is executed, not /etc/rc.d/cleartmp script.
Rich (BB code):
% clear -h
clear: illegal option -- h
Usage: clear [options]

Options:
  -T TERM     use this instead of $TERM
  -V          print curses-version
  -x          do not try to clear scrollback
Thank you, "do not try to clear scrollback" is what led me to it.
 
Every rc.d(8) script sources rc.conf (indirectly through /etc/rc.subr), then inadvertently executes that clear(1) command. So you get to see it's usage output multiple times during boot.
 
gotnull: Wow. I suspect that I would have looked at that file for weeks or months before finding that. Thankyouthankyou! The boot now indeed no longer includes all those entries.

T-daemon: So, per the snd_hda(4) link in your post:

https://man.freebsd.org/cgi/man.cgi?query=snd_hda&sektion=4&manpath=freebsd-release-ports, should I delete

should I delete the line

kld_list="i915kms snd_hda"

and replace it with

snd_hda_load="YES" ?

I remember fiddling with this setting to get the sound working when I did the install. Right now, the sound works.

Thanks to all of you. This level of support is great!
 
SirDice: So in my ignorance, I simply hashed out that whole line and rebooted. But now the system will not complete the boot; I'm left with a black screen. I booted into safe mode, and tried to edit out the hash with both nano and vi, but I get an error message stating that /etc/rc.conf is read only, even though I'm running from su. So I tried booting Ghost BSD from a USB drive, but that won't boot either. Is there a way to edit the rc.conf file from safe mode? Or ? Thanks for any help you can give me; I would hate to have to reinstall the whole system simply because of one character.
 
Solved. Found a post that explained how to mount the / file system:

mount -u /
mount -a -t ufs

and then nano was able to save the edited file. The system now boots normally, and I also eliminated the "snd_hda" entry.

Somehow, the fastest way for me to find the right post to solve a problem is to post it on here. Then I find it before an answer. Thanks to all for your patient support!
 
Back
Top