8000 Not booting quietly · Issue #39 · anatol/booster · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Not booting quietly #39

< 8000 div class="gh-header-actions mt-0 mb-3 mb-md-2 ml-1 flex-md-order-1 flex-shrink-0 d-flex flex-items-center gap-1">
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
medhefgo opened this issue Feb 26, 2021 · 12 comments
Closed

Not booting quietly #39

medhefgo opened this issue Feb 26, 2021 · 12 comments

Comments

@medhefgo
Copy link

Despite having quiet in my kernel command line I get the following message twice during boot:

devAdd: cannot detect block device type

Both are due to ntfs partitions (which booster does not support), but these messages should not be shown when booting quietly anyway.
@coxackie
Copy link

yes, I have also a bunch of

devAdd: cannot detect block device type

appearing upon boot. There are several windows partitions (for recoveries, etc.) that I presume are parsed. I do not see the point of these messages though.

@anatol
Copy link
Owner
anatol commented Mar 13, 2021

This message says that some block device type was not recognized. This block device might contain the root filesystem user intends to mount. If booster unable to detect rootfs then the user should know why.

From other side I agree that it can be a bit annoying to print it for every unrecognized block device (e.g. like in case of ntfs).

So what I can do is to introduce 3 levels of messages:

  • error, always printed
  • warnings printed by default but can be disabled with quiet boot param
  • debug, these are verbose messages from booster. Disabled by default but can be enabled with booster.debug=1 boot param.

And then turn this devAdd message into a warning.

Yay or nay?

@medhefgo
Copy link
Author

Sounds fine to me.

@coxackie
Copy link

it is ok I guess, but coming from mkinitcpio (as I am sure many will), this is quite weird - it never happened there, even without the quiet parameter. It will just confuse that something is really amiss...

@anatol anatol closed this as completed in 07d44f6 Mar 15, 2021
anatol added a commit that referenced this issue Mar 15, 2021
@anatol
Do not show warnings if quiet boot option is present
e1465d2 
Introduce 3 levels of verbosity: debug, warning and severe. By default
'warning' level is used and shows some suspicious moments found by
booster (e.g. a block partition with unknown filesystem).

A user can either increase verbosity with `booster.debug` boot param, or
decrease verbosity with `quiet` param.

Closes #39
@anatol
Copy link
Owner
anatol commented Mar 15, 2021 •
edited
Loading

Alright, the fix has been pushed to master.

Now booster respects quiet boot option. If the option is set then booster reduces verbosity of the output.

Please take a look and let me know if you see any issues with it.

@eugene55
Copy link

Now it boots almost quietly, just prints capital G with a cursor. Can it be hid?

@anatol
Copy link
Owner
anatol commented Mar 15, 2021

I use quiet boot param and I do not see any "G". For me the screen is empty until the login screen comes up.

I checked init code and I do not see any places where such thing can be printed (either with fmt.Print*() or with severe().

Are you sure that it comes from booster? Can anyone else confirm it?

@eugene55
Copy link
eugene55 commented Mar 16, 2021 •
edited
Loading

Can it be part of console.go:118 ?
I start booster directly from uefi so I guess it comes from booster itself

@anatol
Copy link
Owner
anatol commented Mar 16, 2021

Do y 8000 ou have vconsole enabled?

@eugene55
Copy link
eugene55 commented Mar 16, 2021 •
edited
Loading

Yes, I do

@anatol
Copy link
Owner
anatol commented Mar 16, 2021

I see the issue with vconsole. Thanks for reporting it.

@anatol anatol reopened this Mar 16, 2021
@anatol anatol closed this as completed in 04a0167 Mar 16, 2021
@anatol
Copy link
Owner
anatol commented Mar 16, 2021

Thank you @eugene55. The problem was the console escape sequence indeed. Hopefully it is fixed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@anatol @medhefgo @coxackie @eugene55
0