-
Notifications
You must be signed in to change notification settings - Fork 11
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
Gallium OS 3.1 installer fails with GRUB install error #629
Comments
@archit i was running into this issue tonight while installing GalliumOS 3.1 on a Lenovo N23. I worked around the issue by NOT connecting wifi and NOT installing updates during the installation. After the first bootup, I performed an That said, I'm considering a vanilla install of Ubuntu 22.04 since GalliumOS 3.1 is still based on Ubuntu 18.04 and many of the available packages are now out of date. |
thanks @masenf . I've since switched to Arch linux, and planning to try out their port of linux-galliumos kernel |
This isn't the first time this issue occurred, I discovered. March 30, 2020. Right at the start of the pandemic. Should I be worried? |
Happens with Acer Chromebook R 11 as well, not connecting to a network fixes it. |
@0cwa R11 owner here, having just been bitten by the "chomeos updates are no longer supported for your device". I also tried chrome os flex but the sound doesn't work - any other R11 users here have a recommendation now that gallium seems to be deprecated? |
@dc2tom I just installed my favorite Linux distro, and it worked like a charm 😄 |
Hello I confirm, you need to not connect the Wifi to complete the setup. After, some feature of the Live CD is broken (like the logout and terminal), you need to reboot for restart the setup. If you ry before a reboot, the setup stop after the GMT selection with error. |
Attempting to install Gallium OS 3.1 on Samsung Chromebox Series 3 (STUMPY). I overwrote the firmware using mrchromebox.tech. While installing using USB stick (ISO); I run into this error from the installer ...
Any ideas how to get past this error? Any other diagnostic information that would be useful?
I'm not sure if its related, but there is a repeating error after the first error, that I observe in the syslog
The text was updated successfully, but these errors were encountered: