→ BUG 17548: early boot framebuffer reach exceeds grasp (New)

dboot must be gone, its an abomination.

I don't think anybody disagrees that it's time for it to go

Or, at least, that it should be out of the regular boot path we use

its only purpose was to support multiboot1 and later it was easy path to use multiboot2 but IMO multiboot (protocol) is basically abandoned (even as the code is still here and there and sometimes in use) and native boot protocols are in use.

is it possible to get a more verbose output during the boot process? like what ones get in linux if you omit "quiet" from the kernel command line

there is the -v kernel option for more verbose messages... usually there's some way to pass this in from the bootloader

for omnios and smartos at least, there's a 'boot options' menu where you can toggle passing it

(I'm assuming openindiana is using the same bootloader and should have a similar option unless they've altered the default configuration to remove it, but haven't used it in a long time)

there are further things that are more geared towards kernel debugging that are slightly more involved to enable (I suppose the assumption is those that would need to use them probably don't need to be concerned about having a nice menu for them)

is there a specific issue you're having, or is it just more about curiosity?

morbid curiosity :-) also I absolutely HATE when the computer sits there for seconds without apparently doing nothing.

now that I have oi on a laptop, I prefer to see what's doing.

then it sounds like -v is probably what you want

though IIRC, I think openindiana also does a graphical screen (I forget the actual term since i never touch it :P)

though I think pressing ESC might turn it off during boot...

ok... the loader configuration I suppose it's the one in /boot/loader.conf? and yes, oi has a fancy, quiet boot

I'll test the ESC, if that works I dno't even need to mess with the loader

IIRC (tsoome would be the one who knows better than anyone) you should be able to create a /boot/loader.conf.local with customizations that override what's there

I don't know if openindiana does it, but it's possible that updates might clobber loader.conf

while .local should i think be left alone

looks like I have some man page reading for the weekend. Thanks

.local is ok (its original fbsd loader approach), but the current best approach is to put snippets into /boot/conf.d

loader.conf(5) documents it.

ok so I dropped 'boot-args="-v"' into a conf.d file and it does what I wanted

it might be better to do 'set boot_verbose=YES' -- i'm not sure if explicitly setting boot-args will merge if you ever need to do kmdb or single-user

it does. if boot_args is present, it will get parsed into known options and on boot, it will get merged back together.

but individual ones are good if you set them up in different sinppets;)

ahh neat

better than most things :)

hrm.. i thought there was an openzfs change to attempt to TRIM a disk (or at least the zfs partition) when creating a pool (or adding a disk to a pool)

but I can't seem to find it (or the code)... so maybe it never got added...