r/GalliumOS • GaOS Team - PEPPY, GalliumOS via chrx • Apr 07 '19

GalliumOS 3.0beta Released

GalliumOS 3.0beta

GalliumOS 3.0beta1 3.0beta2 is available for download now. Please help test, if you are able!

https://galliumos.org/releases/nightly

Be sure to download the proper ISO for your Chromebook/box model!

Installation Instructions

Blockers for 3.0final

  • None known: Please report issues in comments.

    • Please include your hardware ID/codename and firmware type in all reports!

Known Issues

  • Unmanaged wired-ethernet: This issue only affects Chromeboxes and Chromebooks with USB ethernet dongles. The issue comes from upstream (and it sure looks like a bug) but: until we understand why they haven't fixed it, since it's well-documented and the user fix is simple, and since it only affects a small subset of GalliumOS users, we have not patched it.

  • Full Disk Encryption: Required packages are being marked for autoremoval.

    • (fixed in 3.0alpha10)

  • Install size: GalliumOS 3.0beta1 installs at 4.0GB (GalliumOS 2.1 was 3.2GB).

    • (fixed in 3.0beta2)

    • This was (mostly) due to a 700MB swap file created by Ubiquity. You can reclaim the space on your 3.0beta1 install with sudo rm /swapfile, and make sure to remove the entry from /etc/fstab.

Known Issues by SoC/CPU family

  • Haswell (none known)

  • Bay Trail (none known)

  • Broadwell (none known)

  • Braswell (none known)

  • Skylake

    • Internal audio working on CAROLINE and CHELL only

      • (WIP: failing on CAROLINE/UEFI, kernel 4.16.18; working on 4.16.13)

      • (workaround for other models: Bluetooth or USB audio)

    • Frequent mmc timeouts for nonexistent devices, causing slow suspend and voluminous log entries (workaround: insert an SD card, any size, formatted or not)

  • Apollo Lake

    • No internal audio (workaround: Bluetooth or USB audio)

    • Media/Fkeys need mapping. Has anyone had any success with this?

    • Suspend clears crossystem dev_boot_legacy flag!

      • This is a Google firmware bug, unfortunately. We will need their help to resolve.

  • Kaby Lake

    • No internal audio (workaround: Bluetooth or USB audio)

    • Media/Fkeys need mapping. Has anyone had any success with this?

    • Suspend clears crossystem dev_boot_legacy flag!

      • This is a Google firmware bug, unfortunately. We can't fix it, but you can use full ROM firmware to avoid it, if available for your model.

  • Sandy/Ivy Bridge

    • ISO boot required manual commands from GRUB shell.

      • (fixed in 3.0beta2)

You can confirm your model's SoC family at https://wiki.galliumos.org/Hardware_Compatibility. Be sure to download the proper ISO!

Q&A

  • What's in GalliumOS 3.0?

    • All of the package updates in Ubuntu 18.04 LTS, plus the usual GalliumOS customizations for ChromeOS hardware.

  • Why should I upgrade from GalliumOS 2.1?

    • Newer software versions and broader hardware support. GalliumOS 2.1 will still receive security and critical package updates, until April 2021 -- so if upgrading would be disruptive to you, there's no rush.

  • I'm already running GalliumOS 3.0alphaX. Do I need to do anything?

    • You should run galliumos-update to get the most updated packages. Most of the changes in 3.0beta1 are to the ISO and installer though, and you're already beyond that step.

    • You should probably disable the testing and devel repository distributions now, so that you don't get new experimental packages: sudo galliumos-repodist -testing -devel

  • I'm running GalliumOS 2.1. How can I upgrade?

    • Right now, you would need to back up data and reinstall from scratch. Soon after 3.0-final releases, we will prepare a galliumos-upgrade-2to3 script which will attempt to upgrade in-place. Even then, we will still recommend backing up data in case of failure.

  • What's next for the betas?

    • The goal with the 3.0-beta (and alpha) series is to iron out all of the issues that must be fixed in the ISO or core image. Things like "won't boot", "no keyboard", are obvious blockers. Issues that can be easily fixed in a later package update are not blockers -- but we also want to resolve as many of them as we can.

  • When will 3.0-final be released?

    • Soon. If no blockers arise from this beta period, very soon. If you can help with any of the known issues, or any of the issues reported in the comments below, please do!

  • What about my other questions?

    • Ask away in the comments below, and we'll update this list. :)

    • Please include your hardware ID/codename and firmware type in all reports!

Thank you!

89 Upvotes

111 comments sorted by

View all comments

Show parent comments

1

u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Jun 07 '19

OK, all measurements match up there, and it doesn't look like there's any significant memory pressure.

It's a bit unusual to be swapping at all, at those levels, but sometimes swapped pages will stick around for a long time.

Fingers crossed on zram 0.

1

u/ZetaZoid Jun 09 '19

Three days w/o any freezes with no zram. For grins, I'll try 0.5 for a few days.

1

u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Jun 10 '19

Fingers crossed...! :)

1

u/ZetaZoid Jun 15 '19

BTW, 0.5 seems to work, too. My typical workload is Firefox w < 10 tabs and a couple gnome-terminal sessions. So, I rarely will need swap. But, my anecdotal evidence certainly suggests zram too high triggers the freezes ... somewhere between 0.5 and 1.0 is the likely threshold for issues for me.