Skip to content
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.

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

google-walleye: Fix early framebuffer #67

Merged
merged 2 commits into from Dec 28, 2019

Conversation

@samueldr
Copy link
Member

samueldr commented Dec 27, 2019

It looks like not having quiet in the kernel cmdline somehow makes
the early init of the framebuffer fail.

I don't know the exact difference, but lowering loglevel rather than
using quiet doesn't work here.

In addition, this splits up the cmdline as a list.

samueldr added 2 commits Dec 27, 2019
It looks like *not* having `quiet` in the kernel cmdline somehow makes
the early init of the framebuffer fail.

I don't know the exact difference, but lowering loglevel rather than
using quiet doesn't work here.

In addition, this changes
@samueldr samueldr merged commit 7803d9e into NixOS:master Dec 28, 2019
@samueldr samueldr deleted the samueldr-wip:fix/google-walleye-framebuffer branch Dec 28, 2019
@samueldr samueldr added the type: bug label Jan 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

1 participant
You can’t perform that action at this time.