How to get complete boot message

H

hwagemann

Hello,

I have issues with networking and NFS access So I want to read complete boot messages until login prompt, but in /var/log/messages I don't find complete content of it. During boot procedure I see following, referring to network card:
Code: 
re0: link state changed to DOWN
and some lines later:
Code: 
re0: link state changed to UP

I guess this curious effect has to do with failing NFS mount, see this thread:
https://forums.freebsd.org/threads/trouble-with-nfs-mount.53486/

But a look into /var/boot/message only shows me lines with:
Code: 
re0: link state changed to UP

So where can I see complete boot output? I need this for troubleshooting.

Kind regards,
Holger
 
hwagemann said:
I've issues with networking and nfs access So I want to read complete boot messages until login prompt, but in /var/log/messages I don't find complete content of it. During boot procedure I see following, refering to network card:
Code: 
re0: link state changed to DOWN
and some lines later:
Code: 
re0: link state changed to UP
Click to expand...

I solved this by setting link speed of my network interface in /etc/rc.conf :
Code: 
ifconfig_re0="inet 192.168.0.10 netmask 255.255.255.0 media 1000baseTX mediaopt full-duplex"
Speed negotiation with my switch caused toggling UP/DOWN my network interface.
 
You can get much more verbose boot information by pressing the number 6 key twice, then the enter key at the FreeBSD boot screen during boot. Running % dmesg should give you more detailed output after the machine has booted.
 
protocelt said:
You can get much more verbose boot information by pressing the number 6 key twice, then the enter key at the FreeBSD boot screen during boot. Running % dmesg should give you more detailed output after the machine has booted.
Click to expand...
Why not 3 times ? It's Beastie after all ;)

That said, no more NIC state in dmesg output.
 
Hello dlegrand,

thanks for your hints, but supplemented entry for network card in /etc/rc.conf does not help.

But I can scroll boot messages, and there is some output, referring to my network, which is not good:
Code: 
...
Setting hostname: gerbil.linux.pc
re0: link state changed to UP
re0: link state changed to DOWN
Starting Network: lo re0
lo0: blub blub blub
re0: blub blub blub
...
status: no carrier
...
And some lines deeper:
Code: 
Mounting NFS .... RPCPROG_NFS: RPC: Portmapper failure - RPC: Unable to send

On my computer with intel chip on network card everything is fine with nfs access under FreeBSD, it seems, that realtek chip on network cards make some problems with FreeBSD. Under Linux I've not such issues on computer from my wife.

Referring to computer from my wife I see following options now:
1. Replacing FreeBSD with an arch based Linux like Antergos
2. Buying a new pci network card with intelchip and give FreeBSD another try
3. Live with annoying bug, using bg option in /etc/fstab for nfs mountpoints and wait some minutes after finished boot procedure until nfs shares become ready.

Kind regards,
Holger
 
There are lots of not-quite-identical Realtek cards. Most work adequately. Some need offloading disabled, like -tso or maybe -rxcsum. There are Realtek cards built into a couple of motherboards I use, but I usually add Intel cards.

For a typical user PC, almost any card that can be plugged into a PCI or PCIE slot should work well enough.
 
Uncomment console logging in /etc/syslog.conf for full boot messages

Code: 
# uncomment this to log all writes to /dev/console to /var/log/console.log
# touch /var/log/console.log and chmod it to mode 600 before it will work
#console.info           /var/log/console.log
 
dlegrand said:
Why not 3 times ? It's Beastie after all ;)

That said, no more NIC state in dmesg output.
Click to expand...

# more /var/run/dmesg.boot
# dmesg -a

You can also enable Verbose booting from the loader menu at boot time, which will dump a lot more info into the kernel message buffer (which gets dumped to dmsg).
 
phoenix said:
# more /var/run/dmesg.boot
# dmesg -a

You can also enable Verbose booting from the loader menu at boot time, which will dump a lot more info into the kernel message buffer (which gets dumped to dmsg).
Click to expand...

Yes, but no.

Code: 
re0: link state changed to UP
appears on the console but not into the kernel message buffer, verbose booting or not.
 
You must log in or register to reply here.
Back
Top