FAQ/Troubleshooting - Revision history

Reynhout: /* Login Issues */

2020-08-04T22:50:06Z

‎Login Issues

Reynhout: /* Login Issues */

2020-08-04T22:49:39Z

‎Login Issues

Reynhout at 22:38, 4 August 2020

2020-08-04T22:38:00Z

Nskelsey: wrong command

2017-02-08T17:16:51Z

wrong command

Nskelsey at 17:16, 8 February 2017

2017-02-08T17:16:10Z

Nskelsey: Initial commit.

2017-02-08T17:15:04Z

Initial commit.

New page

This page contains resources and answers to common issues related to installation, maintenance, and usage of GalliumOS.

== Bootup Issues ==

; I accidentally reenabled Chrome's OS Verification and now I can't boot. What now?

If you are using RW_LEGACY firmware and you have not disabled the GBB flags. You can check some crossystem settings from the boot screen with CTRL+T.

Additionally, you can reset the crossystem flags by using a [https://galliumos.org/fixflags/ custom recovery image] for your model and following the [https://galliumos.org/fixflags/README README].

; I updated GRUB and now I can't boot. What now?

This question was resolved on [https://www.reddit.com/r/GalliumOS/comments/5mhjd3/acer_14_wont_boot_after_grub_update/dc3o3iv/?st=iyx72g0o&sh=e942f15b reddit].

== Hardware Issues ==

; No audio output

Here are some quick commands to try.

If you just want to start from scratch:

<code>sudo apt-get install --reinstall galliumos-baytrail</code>

If you haven't changed your audio config:

<code>rm -rf $HOME/.config/pulse</code>

@@ Line 26: / Line 26: @@
 * Reboot and try to log in again
 * If that doesn't clear enough space, repeat VT2 login, and try <code>rm</code>'ing unnecessary files (<code>$HOME/Downloads</code> is usually a good place to start)
-* When you're back in through the usual graphical login process, clear some extra space. Use a tool like Baobab to visualize your disk usage. Install with <code>sudo apt install baobab</code>.
 == Hardware Issues ==

@@ Line 26: / Line 26: @@
 * Reboot and try to log in again
 * If that doesn't clear enough space, repeat VT2 login, and try <code>rm</code>'ing unnecessary files (<code>$HOME/Downloads</code> is usually a good place to start)
+* When you're back in through the usual graphical login process, clear some extra space. Use a tool like Baobab to visualize your disk usage. Install with <code>sudo apt install baobab</code>.
 == Hardware Issues ==

← Older revision		Revision as of 22:38, 4 August 2020
Line 12:		Line 12:

	This question was resolved on [https://www.reddit.com/r/GalliumOS/comments/5mhjd3/acer_14_wont_boot_after_grub_update/dc3o3iv/?st=iyx72g0o&sh=e942f15b reddit].		This question was resolved on [https://www.reddit.com/r/GalliumOS/comments/5mhjd3/acer_14_wont_boot_after_grub_update/dc3o3iv/?st=iyx72g0o&sh=e942f15b reddit].
		+
		+	== Login Issues ==
		+
		+	; Graphical login fails, goes back to login screen
		+
		+	Your internal storage is probably nearly full. The Desktop Environment (Xfce) can't start, and you're dropped back to the Greeter (login screen).
		+
		+	To clear disk space:
		+
		+	* Log in on VT2 (Press Ctrl+Alt+F2 at the login screen, enter username and password)
		+	* Try removing unnecessary packages: <code>sudo apt autoremove</code>
		+	* And clearing the package cache: <code>sudo apt clean</code>
		+	* Reboot and try to log in again
		+	* If that doesn't clear enough space, repeat VT2 login, and try <code>rm</code>'ing unnecessary files (<code>$HOME/Downloads</code> is usually a good place to start)
		+

	== Hardware Issues ==		== Hardware Issues ==

@@ Line 5: / Line 5: @@
 ; I accidentally reenabled OS verification and now I can't boot into gallium. What now?
-If you are using RW_LEGACY firmware and you have not disabled the GBB flags. You can check some crossystem settings from the boot screen with ctrl+T.
+If you are using RW_LEGACY firmware and you have not disabled the GBB flags. You can check some crossystem settings from the boot screen with <code>tab</code>
 Additionally, you can reset the crossystem flags by using a [https://galliumos.org/fixflags/ custom recovery image] for your model and following the [https://galliumos.org/fixflags/README README].

@@ Line 3: / Line 3: @@
 == Bootup Issues ==
-; I accidentally reenabled Chrome's OS Verification and now I can't boot. What now?
+; I accidentally reenabled OS verification and now I can't boot into gallium. What now?
-If you are using RW_LEGACY firmware and you have not disabled the GBB flags. You can check some crossystem settings from the boot screen with CTRL+T.
+If you are using RW_LEGACY firmware and you have not disabled the GBB flags. You can check some crossystem settings from the boot screen with ctrl+T.
 Additionally, you can reset the crossystem flags by using a [https://galliumos.org/fixflags/ custom recovery image] for your model and following the [https://galliumos.org/fixflags/README README].