Peter Grehan wrote this message on Wed, Dec 03, 2014 at 10:30 -0800:
> >> It may be possible that this file isn't being populated in your image,
> >>or being read in by bhyveload.
> >show from loader:
> >OK show
> >Any ideas?
> Looks like device.hints isn't being sourced in by the loader (aka
> bhyveload in this case). This is done on a stock system from:
> % grep device.hints /boot/defaults/loader.conf
> loader_conf_files="/boot/device.hints /boot/loader.conf
> Any chance on your system that you've overridden loader_conf_files, or
> are using a custom setup for loader config ?
Nope, my /boot/loader.conf looks like:
That's all... And /boot/defaults/loader.conf had the line:
loader_conf_files="/boot/device.hints /boot/loader.conf /boot/loader.conf.local"
and, no, I don't have a loader.conf.local file..
Hmmm... I just realized that my i386 system doesn't have the beastie
menu when it boots, but my amd64 system does... This image was
recently built using installworld/distribution w/ -DNO_ROOT, but the
steps to produce the image are exactly the same wrt amd64...
Ok, if I do a: set hint.uart.0.flags="0x10"
in loader, and boot... serial console still doesn't work, but the flag
is now seen by uart0:
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
So, it's not just that flag that's the issue..
I also just did a diff between the amd64 and i386 /boot dir, and besides
the expected, boot blocks and loader differing, the only differences are
if_faith_load got removed and ata and apm hints are now present..
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to