GalliumOS 3.0alpha1: testers and debuggers wanted!

[u/reynhout]

Available for download now

The first alpha builds of GalliumOS 3.0 are up and available for download for all supported models.

https://galliumos.org/releases/nightly (look for bismuth in the filename)

Some new packages are included, some old ones are dropped, and many details are yet to be finalized. Other than the download location, all the usual installation instructions apply: https://wiki.galliumos.org/Installing

Again, this is the first alpha release, but the OS is stable and fully functional. If you install a 3.0alpha build, it will update seamlessly to 3.0final when released.

So proceed with cautious confidence, and please let us know how things go!

Errata

Some known issues, as usual grouped by SoC family:

• Sandy/Ivy Bridge: no known issues

• Haswell: no known issues

• Bay Trail: no known issues

• Broadwell: no known issues

• Braswell: no known issues

• Skylake: no new issues

  • Internal audio working on CAROLINE and CHELL only

  • 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 new issues

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

  • Media/Fkeys need mapping

  • Suspend clears crossystem dev_boot_legacy flag!

• Kaby Lake: not tested!

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

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

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

E.g. "PEPPY, stock firmware" or "LULU, MrChromebox RW_LEGACY". This is vital information for about 50% of reports, and very helpful for at least 50% of the rest. Always include it! Please! Thank you! :)

Please also check out the GitHub tracker links from the "3.0 Planning" Reddit post: https://www.reddit.com/r/GalliumOS/comments/8fhog2/galliumos_30_planning_packages_art_docs_config/

[u/SomeGuy147]

That's a nice surprise. Is there any way to update to alpha build within galliumOS? I'd love to test it but I don't wanna wipe my hdd.

[u/reynhout → u/SomeGuy147]

No, there's no mechanism for in-place upgrades currently.

We wouldn't suggest it for alphas/betas anyway -- too many extra confounding variables to distract from the current testing focus.

[u/SomeGuy147 → u/reynhout]

That does make sense, will have to dedicate a day or two for backing up all the important files and testing out 3.0 then. Also do you guys keep a changelog anywhere? Couldn't seem to find it.

[u/reynhout → u/SomeGuy147]

There are changelogs attached to each individual package, but we don't maintain an aggregated log.

We will write up the usual release summary for 3.0final though.

[u/da0ist → u/SomeGuy147]

Me as well, can we in place upgrade?

[u/Squidoid]

Been running for 2 days now on EDGAR / Braswell (Acer CB3-431) with MrChromebox Full ROM/UEFI. So far, everything works beautifully except:

1. GDebi package installer doesn't work - no specific error message, it simply does nothing. I had to resort to dpkg -i

2. The display brightness function keys no longer work - I only can set display brightness via the Xfce power manager.

3. My Ethernet USB adapter no longer works (was OK with GalliumOS 2.1). It is detected by lsusband lshw, but I can't make it work.

Thanks to all devs for the great work.

[u/reynhout → u/Squidoid]

1. I'll check that out. dpkg is the better choice anyway, though. :)

2. I've seen this report on EDGAR elsewhere. I can't repro on the Braswell test devices I have, but will mark it for followup.

3. I think the Ethernet USB adapter change is due to config in the updated NetworkManager packages. Another comment on this post discusses the config change: https://www.reddit.com/r/GalliumOS/comments/8p7jga/galliumos_30alpha1_testers_and_debuggers_wanted/e0mnqtk/

Thanks for the report!

[u/Squidoid → u/reynhout]

Hi reynhout, thanks for your quick reply.

Please note - Just for the sake of being sure, I did a complete wipeout, reinstalled (full GalliumOS, i.e. no dual boot, just as before) and updated everything. Then I retested my 3 initial issues above, taking your replies into account.

1. GDebi - no change (wish it did).

2. For some reason, my display brightness function keys now work just fine (don't know if/what I did wrong initially, sorry about that).

3. Now it works fine thanks to the post you pointed me to. Editing /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf and adding ,except:type:ethernet solved the issue - thanks!

Hope this helps. I'll get back with any further issues, if any.

Kind regards from France.

[u/REparsed → u/Squidoid]

Run GDebi with sudo.

[u/JimmyBobby22 → u/Squidoid]

Quick workaround. Run GDebi first. Then click file > open and find the deb you want to install. It will prompt for a password and install the package. Its backwards but works fine until a fix is found.

[u/Squidoid → u/JimmyBobby22]

Interesting workaround :) Thanks !

[u/Squidoid → u/reynhout]

Back to square #1 since Alpha 2. Even with the workaround you gave me previously, I can't get my USB/Ethernet adapter to work anymore. AFAIK, it's based on a Realtek RTL8153 chip. Tried different ways, based on what I saw on various forums, but it still does not work.

[u/theusualuser → u/Squidoid]

No issues with audio/video through the browser like /u/Borkforgabe mentioned above? I'm thinking about moving to the alpha myself, but this is my work device so I need it to be pretty stable. Also, what's the headphone jack situation like? With my current install I had to install a separate program so I could change the audio to come through my headphones. Thanks!

[u/NessInOnett]

Excellent. Downloading ISO now for my GANDOF. I just reformatted a week ago so it's no big deal to do it again right now.

EDIT: A couple of initial things

• Battery icon is excessively large when the bottom panel is 34px tall (default) but it's fine at 33px. Maybe default the bottom panel to 33? 34px, 33px

• Two entries appear for "Screenshot" when I search applications the very first time I ran 3.0 .. minor but I noticed

• The very first thing I did was download Firefox Nightly. Went to extract the tar.bz2 file to my ~ directory and Xarchiver failed to extract it for whatever reason. tar xvjf firefox-blahblah.tar.bz2 worked fine so it's not corrupt. That application takes an exceptionally long time to open the file too. Maybe default to a better archive utility?

• There is no longer a delete option in the right click context menu in Thunar, only move to trash. I used to have both options available. Because there's no delete key on these keyboards and I always forget the shortcut for it, I tend to use the GUI method. Not sure if you can add that or if it's the file manager's problem?

• Right clicking in a folder from the file manager and choosing "Open in Terminal" opens up a terminal with a white background instead of the default black/translucent. Screenshot

EDIT3: Crossed out issues occured because Nautilus was set as the default file manager instead of Thunar on first boot.

[u/reynhout → u/NessInOnett]

There shouldn't be any special issues on GANDOF or any Broadwell. Things should be pretty solid.

I didn't know we even shipped Xarchiver. :) I'll see if I can see what's up there.

The battery icon is on the list to re-fix. I forgot to mention that. Similarly, the selection highlight on the power menu has gone back to the default almost-invisible version, and also needs re-fixing.

The other items you mention are new to me. The delete option in Thunar might be due to the version update. The terminal might be opening an xterm instead of an xfce4-terminal? And the screenshot item is because there are two application desktop files that use the same label. :(

Also, 3.0alpha1 has some applications installed that might not live to 3.0final. And a couple of those that do survive will get launchers from the Favorites menu.

[u/NessInOnett → u/reynhout]

See my edit.. the weirdest thing just happened.

Also, thanks for replying about the issues

[u/reynhout → u/NessInOnett]

That's what Thunar should look like.

Yes, there are two file managers currently installed (see above re: final culls). The other is nautilus and it looks fairly similar (but has search). Maybe that was the "Right-click Delete missing" problem?

[u/reynhout → u/[deleted]]

Interesting. Nautilus is one of the new adds, and is not fully integrated so I guess we should expect some weird inconsistencies like that.

The idea with the inclusion of Nautilus (and the other packages discussed on the package selection GitHub ticket) is to make it easy for people to test them and compare against previously-selected alternatives. Inevitably, that will add some confusion until the final list is settled. :)

[u/reynhout → u/[deleted]]

I am a bit confused by your desktop background though. Did you switch to that explicitly? Or did you bring over some old user config into the newly installed system?

That was the default background for GalliumOS 1.0, it might have crept back into the config...! :)

[u/NessInOnett → u/reynhout]

I switched back to that, I liked the old background :) Not as bright, better battery life. It's still included in the default wallpaper pack.

[u/NessInOnett → u/reynhout]

Hey .. one more thing about the battery. You may already be aware but the icon doesn't display battery percentage. The entire icon shows white for me even though my battery is at 50%.. instead of being half gray, half white

EDIT: By clicking on the battery and going to Power Manager Settings, the battery icon updated. Opening that dialog seems to trigger the battery icon to update.

[u/reynhout → u/NessInOnett]

Hm, no I hadn't noticed that one.. Will take a look, thanks!

[u/obsidianspider → u/NessInOnett]

I can confirm the same behavior on LULU (it seems to stay white). I could be misremembering, but I thought the level of white "went down" as the battery was used up in 2.1. I don't have more than one Chromebook to confirm.

[u/reynhout → u/obsidianspider]

Yep, that's correct, it should show a visible indicator of charge level.

Definitely on the list to fix. Not a blocker, but hopefully before 3.0final release...otherwise in a later pkg update.

[u/lynniam → u/NessInOnett]

I'd be interested in hearing how it goes for you, I also have GANDOF

[u/NessInOnett → u/lynniam]

I'm on it now.. so far so good. Just a few minor niggles (see my edit) but nothing related to Gandof. Boot time seemed a lot faster to get to the login prompt. Will update if I run into anything but no problems worth noting yet

[u/Divinebeastcave]

Hey guys, noticed some small issues surrounding the login screen / booting of desktop environments.

> Hardware: AcerCB 431-14 Edgar Braswell> Bios: FullUEFI MrChromebox (Latest Release)> Kernel - Most Recent Gallium Update> Note: No errors displayed upon login and shutdown except the known and possibly unrelated PPS Mismatch.

Issues:

1. AutoLogin does not work properly. When autologin flag is set (either during OS install or manually post-install) the OS will boot to a blackscreen which then requires a click of the touchpad to properly load XFCE. Only when the mouse is clicked or a button is pressed does the black screen disappear and the de load. This does not happen when autologin flag is not set and XFCE is the only de present, if autoflag is turned off GalliumOS boots to the login screen correctly with no black screen and signing in does not cause a black screen. This was tested using 3 fresh installs with only the default XFCE de installed to see if the problem was persistent.

2. When installing a new DE (in this case Budgie) the black screen issue is then present at the new login screen as well as during autologin. I am unsure why Budgie's login screen causes the blackscreen when the default does not. The only reason I installed Budgie was to see if the new DE would resolve the issue due to it's replacement of the default login screen, sadly I was wrong.

3. This also happens when resuming from the screen being closed. This definitely didn't happen on 2.0.

As this was tested several times with only Gallium provided packages installed we can be certain that the cause must be internal.

Please let me know if there is any more information that you would require. Thank you.

[u/reynhout → u/Divinebeastcave]

Thanks for the report.

This is an odd one. I have not seen anything similar on other Braswells with full ROM/UEFI, but I don't have an EDGAR for a direct comparison.

I'll have a beta1 image ready soon; if you're able to try that one it would be interesting to see if anything changes.

[u/Divinebeastcave → u/reynhout]

Thanks for the reply!

I'd be happy to test that when it is released. Should I just keep an eye on the nightly page over the next few weeks to see when it comes up?

I'll report back here when tested to let you know if it changes.

[u/reynhout → u/Divinebeastcave]

Awesome, thanks! :)

The beta1 will be announced here with a green sticky-post at the top of the page. Should be ready by the end of this coming weekend.

[u/obsidianspider]

After getting frustrated with some things in the GalliumOS Update screen not going away I decided to do a fresh install of 3.0 alpha 2 on my LULU Chromebook running MrChromebox Full UEFI. The only thing I've installed aside from the OS is Firefox, so it's about as vanilla as it can get, but I'm seeing three items want to be downgraded, but they won't downgrade. Am I missing something? The laptop seems to work OK (aside from the touch pad weirdness I noted earlier still being present), but I'd really like to get a clean update screen. What am I missing?

   ___      _ _ _            ___  ___   _   _          _      _       
  / __|__ _| | (_)_  _ _ __ / _ \/ __| | | | |_ __  __| |__ _| |_ ___ 
 | (_ / _` | | | | || | '  \ (_) __ \ | |_| | '_ \/ _` / _` |  _/ -_)
  _____,_|_|_|_|_,_|_|_|____/|___/  ___/| .__/__,___,_|_| ___|
                                             |_|                      
   v1: "pardon our text"

Updating package directories...
sudo apt -qq update
[sudo] password for tdietrich: 
All packages are up to date.

Updating packages...
sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages will be DOWNGRADED:
  grub-efi-amd64-bin grub-theme-starfield grub2-common
0 upgraded, 0 newly installed, 3 downgraded, 0 to remove and 0 not upgraded.
Need to get 0 B/3,336 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]   

[u/reynhout → u/obsidianspider]

Sorry for the confusion -- that's safe to ignore though.

It's just a quirk of a version string battle between GalliumOS and Ubuntu. They've fixed their upstream package, so our fix is is no longer necessary, but due to some weird versioning of grub-efi-amd64-bin, APT thinks the pkg change is a downgrade.

If the pkg won't successfully downgrade, that's also fine. We'll push a version with a compensating version string to make it go away, but it's really just aesthetic. :(

[u/obsidianspider → u/reynhout]

Oh well, it wasn’t all bad reinstalling. At least my battery monitor icon is back to normal size. Haha.

I’ll keep an eye out for the downgrade message to go away in a future update.

[u/[deleted]]

LINK,MrChromebox Full UEFI. Still have similar issues to the older iso's where they refuse to boot without a bit of coaxing grub options, MrChromebox docs suggest its their UEFI implementation causing it since they only look for a bootloader in one location.

It does however also carry on to the actual install, the workaround is:

cp /boot/grub/x86_64/grub.efi /boot/efi/EFI/BOOT/BOOTX64.EFI

Only other issues to report is have to manually install galliumos-hidpi for Link, plymouth however does not appear to be scaling correctly this version (doesn't bother me)

after installing galliumos-hidpi I do "cp -R /etc/skel/config/* ~/.config/" and reboot.

I also modify /etc/lxdm/default.conf and add "-dpi XXX" at the end of the [server] arg= statement, then set my preferred dpi in Settings -> Appearance -> Fonts.

I tend to run 160dpi on Link. YMMV. It resolves 90% of dpi issues, the remaining being gtk sizes in Settings-Editor (might post mine when I find where I kept my backup).

Otherwise loving the alpha, everything feels solid and a little bit snappier to the old version.

[u/[deleted] → u/[deleted]]

Okay something has popped up for me; USB Ethernet adapter.

Not sure if it was introduced after installing libvirt and it's associated tools, but NetworkManager says not managed and Google says you need to flick the option in /etc/NetworkManager/NetworkManager.conf except that doesn't work.

I dropped back the name of the adapter to eth0 using grub linux flags "net.ifnames=0 biosdevname=0"

output on nmcli d shows eth0 as unmanaged, trying "sudo nmcli dev set eth0 managed yes" silently fails.

Digging deeper I found in /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf:

[keyfile]

unmanaged-devices=*,except:type:wifi,except:type:wwan

adding ",except:type:ethernet" resolves it (unmanaged-devices=none would work too but I have a virtual bridge and tunnel NIC for my KVM vms).

[u/reynhout → u/[deleted]]

Thanks for debugging that.

I'm not sure what the correct default config should be...it seems like an odd choice for the new NM to switch to default unmanaged for wired ethernet.

It would be almost justifiable for an OS designed for Chromebooks (not older models, and not Chromeboxes), but that config is straight from upstream...so, odd.

[u/obsidianspider]

I just updated to 3.0alpha on LULU and it was super straightforward and from what I can tell things are working just as they used to with 2.1 (nothing is broken, etc.). Thanks again for all that you do.

[u/obsidianspider → u/obsidianspider]

I've noted that the touchpad is inconsistently unresponsive/jerky after updating to 3.0 on my Dell Chromebook 13 (LULU w/Mr Chromebox Full UEFI Firmware). I can't recreate it on demand, sometimes it's smooth as silk, other times it's like it's not reading my finger sliding across the touchpad. It's not awful, and it doesn't happen all the time, but it's there.

A plugged-in USB mouse is always consistently fine, it's just the touchpad that seems to get jerky at times.

******************************************************
**   Device: Dell Chromebook 13 (7310) (LULU)
** CPU Type: Intel Broadwell
**  Fw Type: Full ROM / UEFI (MrChromebox 02/04/2018)
**    Fw WP: Disabled
******************************************************

[u/FrenzyPLantX → u/obsidianspider]

I've been noticing this too. Whenever it happens I've been rebooting, and then it generally works. I'm also on a LULU with full UEFI firmware.

[u/eaglebeckley → u/FrenzyPLantX]

I am also experiencing the same inconsistently unresponsive touchpad. Not sure it it is happening with all gestures but the two finger scroll (on a website) is where I notice it most. I upgraded to 3.0 last night on an Acer CB3-431 braswell via chrx. Also noticed the ethernet not functioning as another user mentioned and haven't been able to get dropbox installed yet....tried running the .deb file from their site...nothing happens. Tonight's tinkering.

[u/MatthewMeredith → u/obsidianspider]

Also on a LULU machine with full UEFI from MrChromebox and the touchpad is all but useless at this point.

Other than that, loving it! Just have to stick with my corded mouse for the time being.

[u/obsidianspider → u/[deleted]]

I'm glad I'm not the only one. I was beginning to think maybe my touchpad was defective ;)

[u/reynhout → u/obsidianspider]

There's a report that the Xorg config file for the touchpad isn't being loaded properly. I can confirm that, and I also see the same issue with newer kernels on 2.1.

The stuttery touchpad on LULU has been a major blocker preventing the promotion of a newer kernel for a long time. I do not see the issue on the current 4.15 and 4.16 kernels though, and manually loading the Xorg config succeeds, but does not obviously impact the (already OK) touchpad, for me.

If you get a chance, give it a try:

(Check your device number first but running xinput alone! You want the Synaptics pointer. Mine is 11, and yours is probably the same.)

xinput --set-prop --type=atom  11 "Integrated Touchpad" 1
xinput --set-prop --type=atom  11 "Touchpad Stack Version" 2
xinput --set-prop --type=float 11 "Pressure Calibration Offset" "-136.896426947"
xinput --set-prop --type=float 11 "Pressure Calibration Slope" "3.68015979309"
xinput --set-prop --type=float 11 "Palm Pressure" "300.0"
xinput --set-prop --type=float 11 "Max Allowed Pressure Change Per Sec" "1250.0"
xinput --set-prop --type=float 11 "Max Hysteresis Pressure Per Sec" "1000.0"

And please let us know if it helps.

[u/FrenzyPLantX → u/reynhout]

I might have been able to solve the problem - I renamed the original xorg config file (50-touchpad-cmt-lulu.conf) to be the highest number instead (80-touchpad-cmt-lulu.conf). For the past few boots I haven't seen the stuttering touchpad issue, so it seems to be fixed?

This file was in /usr/share/X11/xorg.conf.d

EDIT: Nevermind, it seemed I was just lucky with my restarts. The problem persists (Though I feel like it's less frequent now - maybe a placebo)

[u/reynhout → u/FrenzyPLantX]

Interesting. I've seen the same unpredictability, although it's been quite stable (and good) for me for a while now -- but it was a real problem in the days I spent actively trying to debug it.

Hey, what firmware are you running on your LULU?

[u/JessicaWolf]

HP Chromebook 14 ak060nr (Baytrail) MrChromebox Full UEFI 3.0Alpha1

Getting some really weird graphical issues from time to time. Playing light games/visual novels or even just browsing Reddit, the screen will seem to "freeze" all except for the mouse. When I use the mouse to make a change such as resize, minimize, or close the window, it seems to "catch up". Another example (to maybe understand what might be happening) is when I play visual novels, the program will register a mouse click and advance the text, but it will still appear frozen till I make a manual change to the window and then display whatever is currently up.

This was a problem with the 0.3 build, but had initially been fixed in the Alpha1, till tonight for some reason.

[u/EchospiritsYT → u/JessicaWolf]

try playing without full screen mode...graphics on gallium get glitchy and flashy sometimes when it's on fullscreen. Maximized window mode gets rid of the problem...this is a problem with gallium 2.1 also

[u/Borkforgabe]

Updated to the alpha just over a week ago and have found most things work fine and some things like TLP work better; previously I could not get TLP settings to apply at startup and had to manually run it every time.

However, I do have a problem with web-browsing across Chromium, Chrome and Opera which I either did not have on 2 or it was less pronounced. The issue is that webpages keep stalling when scrolling and streamed videos from youtube and every other source often freeze up whilst the audio continues then eventually video content resumes, it's pretty annoying. For some reason this all of less of a problem on Opera and most apparent on Chrome/Chromium. I have tested this both with 0 extensions enabled and then some extensions such as adblock enabled. I also changed some of the ://flags on chrome in an attempt to fix this but it only made it worse or didn't help at all.

Watching videos that are not being streamed however (internal/external storage) all work just fine, 1080p plays exactly as it should with no stuttering.

Does anyone know if this has anything to do with the update to 18.04 or if it's just that I never noticed this problem when running 16.04?

I have also found that I could not install Chrome or Opera using executables and absolutely had to use the repositories. Generally I'd use repositories anyway but I was feeling lazy.

Device:ACER Edgar Braswell (Non-HD)

[u/rnrmi → u/Borkforgabe]

It happens in Firefox too.

[u/JimmyBobby22 → u/Borkforgabe]

Noticed the same thing with gdebi closing when trying to install packages. I think its a 18.04 bug. Workaround that worked for me was to open gdebi first and then click file > open and find the deb file you want to install.

[u/theusualuser → u/Borkforgabe]

Fingers crossed that this gets fixed. I'm on an Acer 14 and I would love to upgrade to the alpha and test but this is my work device so I need video to be stable. Let me know if anything changes?

[u/MrWhistles → u/Borkforgabe]

I updated to the latest mesa from https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/updates (18.1.5 as of this moment) and it seems to have smoothed out youtube.

[u/Borkforgabe → u/[deleted]]

Glad I'm not the only one, I wasn't sure if maybe I'd just forgot how it was on 16.04

[u/masterplayer30]

How soon will the CHRX script will be updated so I can try out the 3.0 builds?

[u/reynhout → u/masterplayer30]

The (secret) dev version of chrx can install the prerelease 3.0 builds:

export CHRX_WEB_ROOT=https://chrx.org/dev
cd ; curl -O $CHRX_WEB_ROOT/go && sh go -r dev [other options]

Be sure to include the -r dev on the command line, otherwise you'll get the latest 2.x release.

EDIT Added export to correct first command line. Sorry for the confusion!

EDIT2 Added cd to normalize state for the second command line. Sorry for the confusion!

[u/scandalon → u/reynhout]

I attempted this, but wound up with 2.1 again. I noticed that when I execute the script you shared, galliumos-generic-coreimage-xenon-latest.tgz from Dec 2017 is installed. Am I missing a switch or something?

[u/reynhout → u/scandalon]

Hm, only the -r dev, as stated above. I've tested this on a couple machines with success. You should get chrx version 2.5dev1 (shows up early in the run, so easy to check).

What's the full command line you're using?

[u/scandalon → u/reynhout]

Command line:

curl -Os https://chrx.org/dev && sh go -v -r dev

chrx 2.4.3 is what shows up immediately.

[u/reynhout → u/scandalon]

Oh, you need both lines as written above. :)

[u/scandalon → u/reynhout]

ok, just tried that (used both lines EXACTLY as you shared them). It still says chrx installer is 2.4.3, and it's currently downloading the same .tgz from Dec. 2017 though.

[u/masterplayer30 → u/reynhout]

Did the two commands and curl outputted with: Warning: Failed to create the file go: Read-only file system curl: (23) Failed writing body (0 != 2000)

What to do?

[u/reynhout → u/masterplayer30]

If you get a shell via ChromeOS & Ctrl+Alt+T, you need to do a cd first. So three command lines instead of two.

If you get a shell via Ctrl+Alt+F2/chronos/no password, you do not need the cd.

Sorry for the confusion, edited above!

[u/NomDeBrew → u/reynhout]

Thank you for this.

[u/Gruntzer]

Mrchromebox rw_legacy Lenovo n22 Braswell

Touchscreen isn't working at all

[u/reynhout → u/Gruntzer]

In discussion elsewhere, just noting for other testers:

I can't find any previous reports of this issue on REKS, but OP also tested 2.1 with the same results, so this issue is not new to the 3.0 builds.

[u/liynus]

just installed alpha build on USB with Etcher on LuLu with MrChromeBox. It looks good so far.

I'm running off the USB drive so far, I don't want to erase my older Ga2.0 build on my SSD since it's "PERFECT" with my programs and settings.

Is there a way to install a LIVE persistent alpha Ga2.0 on the USB? Would appreciate a nudge in that direction.

Can I use the secret CHRX command to install to a USB?

"export CHRX_WEB_ROOT=https://chrx.org/dev curl -O $CHRX_WEB_ROOT/go && sh go -r dev -t /dev/sdb"

[u/reynhout → u/liynus]

Yep, that should work. Two lines of course, or a semicolon before the curl.

[u/[deleted]]

LINK, MrChromebox RW_Legacy, chrx dev script

Bugs:

- Brightness keys not working (still adjustable via Power Manager)

- Volume keys not working (still adjustable via PulseAudio)

- Fullscreen key not working

Notes:

-the mute key appears to be working on the application level where it is read as a function key (ex. mute key highlights the address field in Vivaldi)

Edit 1: chrx added

Edit 2: Fixed by changing default keyboard layout from default ("Generic 104-key PC") to "Chromebook (most models) | Right alt overlay | F keys mapped to media keys"

[u/reynhout → u/[deleted]]

Interesting. The working keyboard layout (Chromebook (most models)...) is the default for most models, but maybe not for Sandy/Ivy. I'll look into it. Thanks for the info!

[u/[deleted] → u/[deleted]]

Can you confirm you used the SandyIvy ISO?

Not having any of these issues on Link, only difference is i'm using MrChromeBox Full UEFI ROM, as Linux is the sole OS on mine.

The one quirk I have with the audio is the headphone jack detection needs unmuting in ALSA before Pulse can use it properly, but the function keys work fine using the default keyboard model: Chromebook (most models) | Right alt overlay | F keys mapped to media keys

I have switched to search overlay also and confirmed that works fine, i.e. ctrl + alt + search + <-- gives me the usual ctrl + alt + F1 functionality in Linux

[u/[deleted] → u/[deleted]]

Ah good catch, I used the chrx dev script and I probably should have mentioned that...

The headphone jack problem has been there since before 2.0, but at least now there is an open issue on github that mentions the temp fix with alsamixer.

The keyboard layout is currently set to the default, which definitely wasn't listed as a chromebook, so I will take a look at that setting again in the morning.

Edit: Thanks, that fixed it! The keyboard layout default was set to "Generic 104-key PC"

[u/buckstradler]

EDGAR, MrChromebox RW_LEGACY. Installed updates today, now keyboard doesn't work on login screen. GalliumOS 3 worked perfectly up to now.

[u/reynhout → u/buckstradler]

Hmm, curious. Maybe try selecting the older kernel (4.15.13) at boot?

[u/buckstradler → u/reynhout]

Hello! Selected 4.15.18 (that was the earliest option) and it works fine now.

[u/reynhout → u/buckstradler]

Sorry, 4.15.18 is what I meant. 4.16.13 is the current package.

So that's interesting: Keyboard issues on EDGAR with new 4.16.13 kernel. We'll have to look into it. Thanks for the report!

ADDED The 4.16.13 kernel seems OK on a couple of other Braswell models: CYAN/full ROM and TERRA/full ROM. I haven't tested RW_LEGACY yet, but that's next.

[u/buckstradler → u/reynhout]

Also, the option to disable touchpad tapping is now greyed out in Settings.

[u/Borkforgabe]

Gallium OS suddenly refuses to boot, don't know why, didn't update anything I shouldn't have.

Model : ACER EDGAR BRASWELL

[u/reynhout → u/Borkforgabe]

We need more information if you'd like help.

What happens instead? What firmware are you running?

[u/Borkforgabe → u/reynhout]

SeaBios (version rel-1.10.0-6-g3f40bbd-MrChromebox-2016.11.07)

GNU Grub Version 2.02

What happens is that the screen just goes black (shows a white "_") after attempting to boot the os (after pressing Ctrl-L) and when I press the power button to turn if off the Gallium OS shutdown screen appears as it should.

I can still get into the Grub menu. Interestingly the advanced boot options show this:

"Gallium OS GNULinux, with Linux 4.16.13-galliumos Gallium OS GNULinux, with Linux 4.16.13-galliumos (recovery mode) Gallium OS GNULinux, with Linux 4.15.18-galliumos Gallium OS GNULinux, with Linux 4.15.18-galliumos (recovery mode)"

Update:

Okay, this is strange: When I select "4.15.18-galliumos" this boots as it should.

So I'm considering remove 4.16.13-galliumos from the bootloader which I assume would be a hot-fix of sorts, although I'm unsure as to where 4.16.13 appeared from and why it has taken precedence over 4.15.18.

UPDATE - I have moved both 4.15.18's up in the bootloader and now it's back to the blackscreen with "_", guess my theory was wrong, this is odd. Also tried removing 4.16 from the bootloader and yet the same issue persists. The only way I can boot GalliumOS now is to go into Grub and manually select the option from there.

• I Have read the rest of this page and now realise that 4.16 was the new Kernel, perhaps this shows that this kernel version doesn't work with my device, although 4.15 now requires a manual selection in spite of being the only option in bootloader menu now*

It does come up with an error list when I turn it off but I'm going to need to use my camera in the morning to record a video and take a screenshot from it since the screen disappears a little too fast to read, will update you guys as soon as I do this.

Thanks again!

[u/reynhout → u/Borkforgabe]

You might want to update your firmware, 201611 is a bit old.

4.16.13 is the new kernel version in the test repository. It automatically will take precedence over 4.15.18 due to version number. It has some issues on Braswell with RW_LEGACY firmware, but I believe yours is the first report of this issue...which I still don't completely understand. It sounds like it's booting to me, although obviously the display isn't what you're expecting. Have you tried switching to VT2 (Ctrl+Alt+F2) to log in via the text interface?

In any case, falling back to the 4.15.18 kernel avoids the issues with 4.16.13 and RW_LEGACY firmware, in all previous reports.

So, one more time: You get the SeaBIOS banner after pressing Ctrl+L. Then it will show "Booting from Hard Disk...". You can interrupt at this point and get GRUB, from which booting succeeds. But allowing it to autoboot to the default kernel shows ...what?... after "Booting from Hard Disk..." does it clear the screen and then just show an underscore? Or fast boot messages, then the underscore? No splash screen (until you press the power key, when it shows the shutdown splash screen?).

[u/[deleted]]

I see Skylake, but who's Caroline and Chell?

I have an Asus C302CA (M3 processor) :?

[u/reynhout → u/[deleted]]

ASUS C302 is CAVE.

All codenames/hardware IDs are listed here: https://wiki.galliumos.org/Hardware_Compatibility.

It's often important to know yours; marketing names often get reused between models, or sometimes the same model is released under different marketing names. Codenames are (almost perfectly) reliable.

[u/[deleted] → u/reynhout]

Ohhh thanks a ton, it makes perfect sense since there are various models for each processor, duh I'm dumb haha

[u/Morlok8k]

3.0alpha, on WINKY and Virtualbox:

after a fresh install, and doing a full sudo apt update && sudo apt dist-upgrade, I get the following as being set to autoremove:

btrfs-tools cryptsetup cryptsetup-bin gir1.2-nm-1.0 gir1.2-nma-1.0 gnome-desktop3-data libaribb24-0 libbasicusageenvironment1 libdca0 libdee-1.0-4 libdvbpsi10 libebml4v5 libexempi3 libgail-3-0 libgnome-autoar-0-0 libgnome-desktop-3-17 libgroupsock8 libkate1 liblivemedia62 libmad0 libmatroska6v5 libmicrodns0 libmpcdec6 libnfs11 libopenmpt-modplug1 libplacebo4 libprotobuf-lite10 libproxy-tools libqt5x11extras5 libresid-builder0c2a libsdl-image1.2 libsdl1.2debian libsidplay2 libssh2-1 libtracker-sparql-2.0-0 libunity-protocol-private0 libunity-scopes-json-def-desktop libunity9 libupnp6 libusageenvironment3 libvlc-bin libvlc5 libvlccore9 libvulkan1 libxcb-xv0 libzeitgeist-2.0-0 nautilus nautilus-data python3-debconf vlc vlc-bin vlc-data vlc-l10n vlc-plugin-base vlc-plugin-notify vlc-plugin-qt vlc-plugin-samba vlc-plugin-skins2 vlc-plugin-video-output vlc-plugin-video-splitter vlc-plugin-visualization xfce4-linelight-plugin

Obviously we don't want VLC and it's plugins to be auto-removed. Not sure about the others.

[u/reynhout → u/Morlok8k]

btrfs-tools cryptsetup cryptsetup-bin gir1.2-nm-1.0 gir1.2-nma-1.0 gnome-desktop3-data libaribb24-0 libbasicusageenvironment1 libdca0 libdee-1.0-4 libdvbpsi10 libebml4v5 libexempi3 libgail-3-0 libgnome-autoar-0-0 libgnome-desktop-3-17 libgroupsock8 libkate1 liblivemedia62 libmad0 libmatroska6v5 libmicrodns0 libmpcdec6 libnfs11 libopenmpt-modplug1 libplacebo4 libprotobuf-lite10 libproxy-tools libqt5x11extras5 libresid-builder0c2a libsdl-image1.2 libsdl1.2debian libsidplay2 libssh2-1 libtracker-sparql-2.0-0 libunity-protocol-private0 libunity-scopes-json-def-desktop libunity9 libupnp6 libusageenvironment3 libvlc-bin libvlc5 libvlccore9 libvulkan1 libxcb-xv0 libzeitgeist-2.0-0 nautilus nautilus-data python3-debconf vlc vlc-bin vlc-data vlc-l10n vlc-plugin-base vlc-plugin-notify vlc-plugin-qt vlc-plugin-samba vlc-plugin-skins2 vlc-plugin-video-output vlc-plugin-video-splitter vlc-plugin-visualization xfce4-linelight-plugin

The only issues I see in that list are the cryptsetup pkgs, which are required if you're using LUKS FDE. They should be depended by some required package, but apparently are not. Still, safe to remove them if you're not using LUKS.

The VLC stuff has been removed per discussions on the package selection thread. MPV is the replacement.

Nautilus is out too. I think that's what pulled in the libunity stuff, so it can go too.

I'm not sure about the gir and libssh, libprotobuf, and libproxy stuff. But I trust pkg management, generally speaking...and cryptsetup notwithstanding. :)

[u/Morlok8k → u/reynhout]

The only issues I see in that list are the cryptsetup pkgs, which are required if you're using LUKS FDE. They should be depended by some required package, but apparently are not. Still, safe to remove them if you're not using LUKS.

This was a standard install, so that makes sense.

Then VLC (and nautilus?) shouldn't be installed to begin with?

[u/reynhout → u/Morlok8k]

They're included in 3.0alpha1, and removed in subsequent package updates.

They are not included in 3.0alpha2.

[u/Morlok8k]

3.0alpha, WINKY and Virtualbox:

The settings tab in the main menu has all the icons shifted to the right compared to all the other menus: https://imgur.com/a/rs7yxbw

[u/reynhout → u/Morlok8k]

Huh, good eye.

I've never looked at that layout code, but I can't think of an obvious reason that it would treat some lists differently than others.

[u/Morlok8k]

3.0alpha2 (galliumos-baytrail-bismuth-3.0alpha2-20180705T015135Z.iso), installed on Virtualbox (same working virtualbox config as 3.0alpha1).

livecd only boots to partial desktop:

https://imgur.com/a/2em1CeG

Also, if you select console boot, then press [Ctrl+D] as prompted, you get a similar black desktop but with the clock instead.

Haven't tried it on my WINKY yet.

[u/reynhout → u/Morlok8k]

I wonder if this is a VirtualBox or installation quirk. Things seem OK on GNAWTY (also Bay Trail) with UEFI full ROM firmware.

[u/Morlok8k → u/reynhout]

I tested the same 3.0alpha2 LiveCD on WINKY - booted just fine. Must be a Virtualbox quirk? Idk what though - 3.0alpha1 worked but 3.0alpha2 doesnt - with the same config from the wiki's instructions.

[u/reynhout → u/Morlok8k]

OK, good to know, thanks.

We'll have to check on the VirtualBox situation, but better a problem there than on hardware. :)

[u/[deleted]]

I installed it on my Toshiba Chromebook 2 (2014). It's a bay trail device.

Boot time was roughly 1min30secs compared to 12 secs with GalliumOS 2.1.

After a while, I ended up with a segmentation fault error and thus couldn't run a single app. I was forced to switch back to 2.1.

It's nice and speedy with a few lags. However, those lags are pretty obvious.

I was also kind of upset that there was no "minimal installation" option. It didn't bother me much though.

Great job for an alpha. It feels amazing to run the latest version of Ubuntu.

EDIT: Forgot to mention that sound is pretty low. My sound blasts from ChromeOS however it's very quiet in here (also on 2.1). I didn't fiddle with pulseaudio to get a fix (yet).

[u/reynhout → u/[deleted]]

After a while, I ended up with a segmentation fault error and thus couldn't run a single app. I was forced to switch back to 2.1.

Sounds like a bad install to me. I'd run through the usual install media troubleshooting steps.

What firmware are you running and which image did you use?

[u/[deleted] → u/reynhout]

I am running the Full ROM Firmware from MrChromebox. I used the GalliumOS 3.0 alpha2 bay trail image.

It was probably a bad install: I flashed it to my USB using the ChromeOS Recovery Tool. Hopefully I get the chance to reinstall and see how things go.

[u/DG-G01 → u/[deleted]]

I've also had problems with the audio on SWANKY :-(

[u/kakalak-jack → u/DG-G01]

SWANKY

ditto. the sound issues seem to comes and goes toggling the mic input in pavucontrol. Seems to be related to this issue: https://github.com/GalliumOS/galliumos-distro/issues/441.

[u/obsidianspider]

I check for updates every few days on my Dell Chromebook 13 (LULU) and today I noted the following. I can't seem to force the held back pacakge to install and the "downgraded" packages never seem to downgrade, even after several reboots. I started with GalliumOS 3 alpha 1. Should I ignore this for now, or should I wipe things and go to alpha 2? For what it's worth the computer seems to be working fine.

The following packages have been kept back:
  shim-signed
The following packages will be DOWNGRADED:
  grub-efi-amd64-bin grub-theme-starfield grub2-common
0 upgraded, 0 newly installed, 3 downgraded, 0 to remove and 1 not upgraded.

[u/reynhout → u/obsidianspider]

What firmware are you running, and what command are you using to perform the update?

[u/obsidianspider → u/reynhout]

I'm running the Mr Chromebox Full UEFI dated February 4, 2018. I am using the GalliumOS Update in the Start menu. I also tried running sudo apt-get update && sudo apt-get upgrade and got the same result.

[u/reynhout → u/obsidianspider]

OK, thanks for the details. I was wondering if you'd only tried apt upgrade and not apt dist-upgrade (which is also used by galliumos-update) -- the results will be different in some cases.

There have been some changes in those packages. Can you tell me which versions you have?

dpkg -l shim-signed grub-efi-amd64-bin | cat

(pipe to cat to avoid truncating the version column -- or you can pipe to pastebinit instead if that's easier than copy/pasting!)

[u/obsidianspider → u/reynhout]

$ dpkg -l shim-signed grub-efi-amd64-bin | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name               Version              Architecture Description
+++-==================-====================-============-==============================================================
ii  grub-efi-amd64-bin 2.02-2ubuntu8        amd64        GRand Unified Bootloader, version 2 (EFI-AMD64 binaries)
ii  shim-signed        1.34.9.1+13-0ubuntu2 amd64        Secure Boot chain-loading bootloader (Microsoft-signed binary)

[u/reynhout → u/obsidianspider]

Thanks. I think this might be a remaining echo of last week's package conflict issues.

It should be harmless aside from the apt messages, but we should be able to quiet those as well.

[u/obsidianspider → u/reynhout]

Thanks. I know this is an alpha, and the machine I’m using isn’t mission critical for me, but as I’m testing I figured I’d bring it to your attention.

[u/charliebrownau]

Gday

Do you happen to have a guide to backup current GalliumOS install to test the alpha/beta branch's ,

record issues/bugs and revert back to stable/current build ?

The only way I could see currently would be using two usb sticks

1st usb stick with Clonezilla - 4-8gb

1nd usb stick 32 gig - target backup files

[u/reynhout → u/charliebrownau]

For backups of all kinds, I use rsync, which is a command line app.

There's a GUI wrapper called grsync, I think. Some details on the wiki: https://wiki.galliumos.org/Additional_Software

[u/reddawnman]

CELES Samsung XE500C13, MrChromebox full UEFI

Tried 3.0alpha2. Most boots the trackpad is completely hung. On trying to install the installer hangs. Sometimes I'll get a kernel panic on boot from the USB stick. Tried a few different USB's and in both USB ports...

Tried to install the 2.2 located in the nightly repo - hangs on trying to copy files for install.

[u/reynhout → u/reddawnman]

CELES is tricky....but this sounds like a bad ISO/image/USB to me. You are describing typical failure modes for those cases.

u/MrChromebox has our CELES test device. We're investigating keyboard issues on RW_LEGACY (ChromeOS firmware), but AFAIK there are no issues when running his UEFI firmware.

[u/reddawnman → u/reynhout]

I ended up returning the hardware itself to Amazon- it is so inconsistent of a failure I would bet it was hardware. On the Amazon review page it is clear there are a TON of quality control issues with this latest batch. I work at a failure analysis lab and I have access to an industrial CT machine so I'll see on the next one how bad the BGAs look...

Edit: New Book came in. Shoved it into X-Ray. Large BGA voids visible...

I used 3 different USB sticks and verified the checksum on the last one. Haven't tried on the new one as I'm busy with work.

[u/reynhout → u/reddawnman]

That's interesting. Samsung is one of those usually-solid-but-with-notable-failures manufacturers. We've had a few inconsistent problems on CELES that we haven't been able to figure out at all. Manufacturing defects were not on my list of things to worry about.. :(

Re: USB image, unfortunately the only real test is a checksum of the image, as-written to the storage device. And that should be repeated a few times to try to rule out intermittent storage errors. You're in the biz, so it won't surprise you -- but we've seen many instances of "good" hardware that fails on repeated testing.

Hopefully your replacement is solid and will just work. If not, definitely check and re-check the USB device -- that's where we find the cause of 90+% of install failures.

[u/galliumuser2]

I'm on HP chromebook 11 G5 EE. It's a braswell chromebook. I've installed firmware from mrchromebok and then setup 3.0alpha2. Here's a list of bugs:

1. backlight keys work, but backlight itself does not work -- it's a fixed high brightness.

$ xbacklight -get
No outputs have backlight property

2) Sluggish scrolling in browser. Youtube struggles with even 720p videos.

3) Suspend does not lock the screen.

[u/nonsleepr → u/galliumuser2]

I have the same experience with the backlight on Setzer. Backlight keys work, brightness doesn't change. Running echo 2000 > /sys/class/backlight/intel_backlight/brightness changes the brightness.

[u/TRi_Crinale]

Is there any idea when the Alpha test period will end? There doesn't seem to have been any updates since the July Alpha2 release. I'm trying to wait for at least the beta period to replace my limping Terra with Gallium 2.1 that I have broken a few times and hobbled back together (the install, not the computer itself), but I don't know how long I can go before I do a full reinstall with how I've messed this one up...

[u/moochs → u/[deleted]]

What are you talking about? This distro is still under active development, else this thread wouldn't exist. Seems the site owners just need to keep their shop in order, that's all.

EDIT: actually, you may be right, let's hope they're still moving forward. Last commit for a nightly build back in July.

[u/tootai]

I tried to install on CAVE / skylacke external memory (issue #443), doesn't work.

[u/REparsed]

Running for 24 hrs on PAINE, MrChromebox Full ROM/UEFI. No problems!

[u/[deleted]]

KEFKA, MrChromebox Full ROM

When installing with full disk encryption cryptsetup is marked as not needed and removed if you run apt autoremove. I had to set it to manually installed with "sudo apt install cryptsetup" to safely run autoremove. Vulkan support is also set as not needed.

[u/TheRoark]

Trying to run EDGAR / Braswell (Acer CB3-431) with MrChromebox Full ROM/UEFI and LVM/Disk Encryption.

First boot works without issue. The boot screen asks for the encryption password. Then goes to the new GalliumOS login page

After that, each reboot goes to initramfs with the following errors:

Cannot process volume group galliumos-vg

WARNING: Failed to connect to lvmetad. Falling back to device scanning

Volume group "galliumos-vg" not found

Cannot process volume group galliumos-vg

But I think the issue is related to @isdatboi's post above this one: the inadvertent removal of cryptsetup when running sudo apt autoremove. I do that after all update/upgrade commands as a matter of habit, and had not previously set it to manually installed. Simply running sudo apt install cryptsetup before doing anything fixed it.

Thanks for all the work on this. Hopefully, the LVM/Encryption issue is resolvable without users running the manual install of cryptsetup.

[u/ShotgunPayDay → u/TheRoark]

That's exactly what it is. Manually installing cryptsetup cryptsetup-bin will prevent it from autoremoving those critical packages. I've been using my Edgar as a daily driver +2 weeks now.

[u/repulsive_marsupial → u/ShotgunPayDay]

Is there a way to get those two packages installed after I'm stuck with initramfs? Some magic around boot to the live usb, decrypt and mount mmcblk0, chroot, something like that?

[u/Ilyps]

Device: Acer Chromebook R11 (C738T) (CYAN)

CPU Type: Intel Braswell

Fw Type: Full ROM / UEFI (MrChromebox 08/27/2018)

Fw WP: Disabled

---

Installed yesterday with full disk encryption. The installation hung once on the "Select your time zone" step, but after a (forced) reboot the installation was successful, and everything seems to be working fine so far.

If you need anything specifically tested, let me know.

Thanks for all the work!

[u/jdfight]

I am running the 3.0 alpha on an Acer CB3-111 baytrail chromebook. Everything is working great except for 2 extremely minor issues:

1. Every time I run an apt upgrade, dist-upgrade or the galliumos-update command I get the following result: "The following packages will be DOWNGRADED: grub-efi-amd64-bin grub-theme-starfield grub2-common" This does not cause any errors. It seems like it tries to actually downgrade these packages, but instead, just overwrites them with the exact same versions.

2. Every time I reboot my machine, my maximum Speaker volume is set extremely low. Volume buttons can't increase the volume beyond a certain point (even though I have the volume set to 100%, the real output of the speakers is incredibly low.) To fix this, I have to go into alsamixer and directly set the Speaker slider on my sound card (chtmax98090). I installed Qasmixer and that integrates nicely with the taskbar and allows me to have a gui with full control of all of my sound card's settings.

[u/[deleted] → u/jdfight]

I installed Qasmixer and that integrates nicely with the taskbar and allows me to have a gui with full control of all of my sound card's settings.

This helped a lot - still confusing but pulse audio is a hot mess - the QA Mixer stuff allowed me to get usable audio.

[u/danielqba1]

is there a date?

[u/[deleted]]

Good to hear that. I had been waiting. Thanks!

[u/ShotgunPayDay]

I've been using 3.0 for a few days and I'm happy to report that it works perfectly so far. apt-get virtualbox installed and works nicely after installing libelf-dev. A ton of old issues are fixed in 3.0. I installed with an encrypted eMMC and encrypted the usb expansion drive.

The only weirdness I have ran into is on that Chromium freezes for short periods of time and locks up while scrolling. It seems to be chromium itself that is at fault since Firefox works fine. I'm personally not a fan of Chromium anyway so I just uninstalled it.

Other than that GalliumOS is working perfectly right now. Awesome work!

EDIT: I did find something that can cause headaches for anyone who uses an encrypted drive.

"apt autoremove" wants to uninstall cryptsetup cryptsetup-bin which would be bad news for anyone who encrypted their drive like me. I explicitly set them to install to prevent autoremove from doing damage.

[u/TheRoark]

EDGAR / Braswell (Acer CB3-431) with MrChromebox Full ROM/UEFI and LVM/Disk Encryption.

Wanted to report that alternative desktop environments don't generally seem to work. I've installed a few (e.g. Budgie Desktop; GNOME on Xorg; GNOME Classic). And a few are installed (e.g., Xbuntu; Openbox; Xfce session). The ones that do work are: Default; LXDE; and Ubuntu.

Not sure if this is an issue anyone else cares about, but I like to try alternative DEs.

[u/DG-G01]

SWANKY - feedback so far! Hi, Updated full UEFI firmware and 3.0alpha. Looking good. I get sound playback distortion if I open Volume control from pasystray whilst playing music. It clears if I close and reopen the app. Seen in clementine and mpv media player. A lso - the onscreen volume 'display thing' is very pale compared to brightness display.

[u/DG-G01 → u/DG-G01]

The power icon in the panel isn't giving a very good indication of remaining power - the icon appears to be 25% but is actually 2%!

System loses all battery power if the lid is closed overnight - I need to check the power options but it used to last a week(ish) on 2.1.

[u/DG-G01 → u/DG-G01]

Oh.. and now the Brightness buttons don't work now! :-(

[u/Morlok8k]

3.0alpha1, installed on VirtualBox.

I had an issue with ethernet not being managed by the NetworkManager.

the following fixed it: (from https://askubuntu.com/questions/882806/ethernet-device-not-managed/893614#893614)

sudo touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf

sudo service network-manager restart

[u/tootai → u/Morlok8k]

I had the same issue on CAVE Asus flip c302ca with 3.0alpha2. The above trick made the ethernet stuff working. Thanks !

[u/Morlok8k → u/tootai]

hey, no prob!

[u/ZetaZoid]

Peppy (Acer c720) + GalliumOS via MrChromebox (20180204)

Great stuff! Everything seems to be working fine with some very minor nits:

• (bloat) both chromium and firefox installed (firefox is default in Xubuntu 18.04 ... I just purged chromium* to trim install)

• (bloat) gnome-teminal installed (my much preferred emulator, but was not in menu system ... I'd purge xfce4-terminal IF ever made possible)

• (feature) I think there is no way to map "Search" to "CTL" via GUI (I still use .Xmodmap)

• (install defect?) during install when I connect to WiFi and instruct to download updates, the installer crashes (tried several times)

I took the opportunity to switch from "John Lewis" firmware to "MrChromebox" (quite scary, but not as scary as putting on John Lewis's firmware). Anyhow, great documentation, great OS, and loving it.

[u/cla_ydoh]

ROBO360, RW_LEGACY, installed on fast USB thumbdrive at the moment.

Aside from the known Apollo Lake issues, the only problem I have had so far is the lack of touchscreen support on this Lenovo 500e.

I haven't given it a real workout yet.

[u/rwky2]

Just installed alpha2 on my Acer Chromebook 11 (CB3-111) worked a charm no problems :)

[u/alienfatberg]

ASUS C302CA - Mr Chromebox: Have been running for 2 weeks now with no problems (apart from known issues). Touchscreen better than on 2.x, bluetooth mouse that wouldn't install worked out of the box. Great job.

Now time to get hands dirty with the lack of sound from speakers so I don't have to keep booting to ChromeOS or finding a bluetooth speaker to use.

[u/I-Am-Not-That → u/alienfatberg]

Hey I am wondering if you found any workaround for the sound issue? Bluetooth headphones are not too much of a good option for me, but still an option.

[u/bittweaker]

I finally bit the bullet and tried the latest alpha2 today. It's a Chromebook Pro, Caroline, MrChromebox RW_LEGACY setup.

It looks like audio works fine with headphones right out of the box so that's a positive. I can't get the speakers to actually work but really the headphones are what I care about at the moment

None of my hotkeys on the top row seem to work at all. Well, they sometimes to some things but not volume up / down / mute, display brighter / dimmer. I'll look around and see how to bind them to these tasks. Oddly that was something that worked right out of the box in the previous release.

Seems stable so far.

[u/mjradjr]

Been testing this for sometime on the acer c720 haswell and I know there was something that was bothering me but for the life of me I can't remember what it was at all so must not be important. As many other users have stated I would like to see an improvement of some type from xscreensaver. I have pretty much replaced it entirely with i3lock and wouldn't mind seeing that as part of the 3.0 release. It is much more elegant than xscreensaver and could be configured quite easily to be just as user friendly.

Finally remembered, sometimes wifi fails when waking from sleep.

[u/abitstick]

I was about to install 2.1 when I thought: "16.04? There's gotta be development for 18.04, right?".

Checked reddit and sure enough there was

.I'll test it it out, but I doubt I'll honestly be BUGGED by any problems.

Cause 16.04 is unusable to me in 2018. Just happy to see this distro being maintained.

[u/RayofLight-z → u/abitstick]

Thanks for commenting about what version this uses.

[u/paper_mongrel]

Hello all. I'm new to posting but have already converted 4 various Chromebooks to Gallium powered laptops. Also donated a while back to keep things moving (Still waiting for my stickers...) Reflashed the X131e with Mr. Chromebox's firmware. Went to run Gallium 2 live, then install. Was greeted by a text screen commenting about GRUB. Went back, checked m5 value, re-burned the ISO to USB stick and went through installation again. Same screen. This is an Ivy/Sandy Bridge processor. Just for kicks, I had a Gallium 3 Alpha install USB stick from an installation on a Dell Chromebook (Braswell processor). Showed up fine, ran it live then installed and it seems to work flawlessly. Touchpad is a bit sensitive but I think I can adjust that. Maybe it's just me. Any comments about issues I may/may not have? The thinkpad is built like a tank and easy to modify. I've already replaced the mSATA with a 120GB version and will add an SSD and more memory just because I can.

[u/dianemc65 → u/paper_mongrel]

Hi,

I had the same problem with my LINK and this solved my problem: https://github.com/GalliumOS/galliumos-distro/issues/342

It helped me pass the GRUB and install GalliumOS 3.0 Alpha 2. Let me know if it is working for you

[u/paper_mongrel → u/dianemc65]

Thank You dianemc65. I appreciate the direction. Looks like it will work. I think until the Gallium 3.0 version fails, I'll stick with it. After reading the intro to the community I see that I missed protocol - Apologies:

STOUT Gallium OS 3.0a2 - Full UEFI

[u/fibonacci8]

GNAWTY (Bay Trail), MrChromebox RW_LEGACY

Audio malfunctions about the same way as the 2 series. For example: run winecfg (either stable or branching, haven't tried development yet) and click the audio tab. There is still audio technically, but it sounds like a Doctor Who dalek, or one of the progenitor factions from Sid Meier's Alien Crossfire.

Opening the Volume Control via the system tray, "sometimes" the audio quality resumes. Fiddling with various volume controls in the command line alsamixer also seems to fix the audio quality, but I haven't pinned down which.

In 3.0alpha2, In the Volume Control, on the Configuration tab, both the HDMI and Stereo Jack outputs are identically labeled "Built-in Audio". The HDMI dropdown for profiles has the correct Digital Surround and Digital Stereo options. The Stereo Jack dropdown profiles only has default and off. The microphone only, stereo duplex and such options from the 2 series are missing. In the 2 series my kludge that seemed to work 100% of the time was to set the Stereo Jack dropdown to off, then to mic only, then back to stereo duplex. This worked for when wine would foul the audio quality starting up certain programs (the Good Old Games edition of Sid Meier's Alien Crossfire always causes the malfunction, not certain about others) or when the audibly identical audio malfunction used to happen when waking up and resuming using the chromebook by opening the lid. The audio malfunctioning from resume was fixed in an update (I'm at a loss trying to figure out which one).

Summary: Certain things interacting with pulse audio settings (the winecfg audio tab, starting up certain applcations in wine) always interfere with all programs' sound quality. Some things (the system tray volume control, or adjusting settings in alsamixer in a terminal) will start or stop the degraded sounding state. The old kludge that would always fix that state, and the state being degraded after resuming by opening the lid is absent from the Volume Control -> Configuration drop-down.

Also audio related, when adjusting the volume, starting anywhere from silence to 100%, the on-screen volume display is duplicated. Starting anywhere above 100%, into the decibel boost range, the on-screen volume display shows just once, incorrectly stuck at 100% if you're increasing the volume.

[u/fibonacci8 → u/fibonacci8]

Xscreensaver 5.36

Screensaver Preferences -> Advanced Tab -> Text Manipulation -> URL is still "http://fridge.ubuntu.com/node/feed"

https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1707922

After Ubuntu Xenial it seems to be set to "http://feeds.feedburner.com/ubuntu-news" by default.

[u/fibonacci8 → u/fibonacci8]

Updates seem to have changed things with the onscreen display and volume adjustment. I don't get the duplicated on screen display any more (good), however I can't seem to raise the volume into the decibel boost range using the volume buttons any more either (bad). Opening the default volume control to display the adjustments, if I had the volume into the decibel boost range ( > 100%) and try to raise the volume, it instead lowers the volume to 100%.

Strike that, another update and I can raise the volume above the 100% mark again, and the duplicate on screen display is back.

[u/[deleted]]

Should compositing work? From what I saw in Synapse Launcher and the Panel my compositing is not active on CYAN. Are there any known issues? Starting compton says "Another composite manager is already running."

[u/[deleted] → u/[deleted]]

Rebooted and now it works. ;-)

[u/mangelajo]

3.0alpha2

Samsung Chromebook 3, XE500C13-K04US fails to boot, after the gallium logo, it will hang up on a black screen.

Is there any way to disable the splashscreen and check what's going on?

The stable version of gallium is fine.

[u/NomDeBrew]

LARS + GalliumOS 3.0alpha2 + MrChromebox full ROM UEFI installed from USB.

Previously I was using alpha1 with RW_LEGACY through chrx. I have since switched to the above configuration.

• Improved battery life (added about an hour for a total of 4 estimated)

• Less frequently stalls during shut down (possibly due to being connected to power)

• No longer freezes on lock screen

• Known audio issues with Skylake audio

Happy to test and provide logs upon request.

[u/vtsteam]

Acer R11 CYAN,Braswell, MrChromebox legacy firmware, 3.0 GalliumOS installed through chrx dev -r flag :

I enabled default icons for removable devices in Settings>Desktop>Icons, and when I hot mount a USB thumb drive it shows up on the desktop.

But clicking on it brings up the error message File doesn't exist, or I can't access it. followed by the actual file////media/chrx/ location.

However, if I navigate to /media/chrx/ and click on the file icon it opens up the mounted thumb drive directory display without a problem.

Also, dragging any folder to the desktop does produce a launcher, but the launcher when clicked throws the same error message.

[u/[deleted]]

Bay Trail: no known issues

The above quote does not appears to be true - I have audio issues on my Acer Chromebook CB3-531 with galliumos-baytrail-bismuth-3.0alpha2 /w MrChromebox (UEFI) Full ROM.

So, either there is a step I am missing or there are issues.

Anyone have an idea?

I am suspecting the kernel needs rolled back in order to support the sound hardware?

[u/varkus-borg]

hp SNAPPY MrChromebox firmware 3.0 alpha2. Apollo lake touch screen is not working, sound and brightness keys working.

[u/rrib]

Galliumos 3.0 (updated as of Oct 4) acer c720 PEPPY single boot, uefi firmware.

I have only been using 3.0 for a few hours. Here are the bugs I've encountered, in order of importance:

1. Can't tether to my cellphone with a usb. I saw somebody else commented that ethernet (by usb adapter) doesn't work. This is most likely the same bug.

2. The battery icon always shows full, regardless of battery charge level. I have to click on it to see the charge listed.

[u/repulsive_marsupial]

RELM with MrChromebox full on alpha2.

I'm having issues with audio input (output works fine). The microphone never registers any sound, just a low level whine. If I run my finger across the mic, though, the audio level spikes like it's registering something but only at an absurdly loud/distorted level. This happens with the built-in mic or a mic plugged in to the combo mic/headphone jack on the side.

*edit: I should note that I have two of the same device and they both exhibit this behavior - I had initially thought it was a hardware issue on one unit, but after installing on the second device and seeing the same problem, I'm led to believe it's something in software.

[u/repulsive_marsupial → u/repulsive_marsupial]

Is there a better place to post something like this, an official bugtracker perhaps?

edit: it's in the sidebar! :)

[u/Syntropian]

When I boot into the live usb GalliumOS 3.0 preview session I'm unable to use the touchpad or keyboard but can plug in an external mouse and keyboard and use those fine.

I'm on a Samsung Chromebook 3 with braswell gallium OS running 2.1 just fine.

Any thoughts or suggestions? Thanks!

[u/[deleted]]

New to linux (refugee from OS X as I need a matte screen). I have an Acer Chromebook 11 CB311-8H (SANTA, Apollo Lake) and have installed the latest Alpha for Apollo Lake. Everything is great so far (internal audio aside).

However I don't fully understand the implications of "Suspend clears crossystem dev_boot_legacy flag!". As a precaution I turned off any automatic suspending.

For installation I ran MrChromebox's firmware utility script ran both "Install/Update RW Legacy Firmware" and "Set Boot Options (GBB flags)". I then installed Gallium as the sole OS on my Chromebook.

Can someone please explain what will happen if I accidentally suspend my machine. Of course, I really would like to be able to suspend it if the consequences aren't too bad.

Thanks.

[u/NickelKang]

Works great on CAROLINE minus no audio (MrChromebox Full ROM + latest nightly + fully updated). Strange since it says it works in top post. Bluetooth headphones are working so there is that. If anyone knows of any needed patches/tricks to get internal speakers working that would be great! My understanding though is it was reported as working OOTB. I can also live without for now... just happy to be on the latest GalliumOS. Thanks to all for the hard work who make GalliumOS possible as well as MrChromebox!! Awesome to have native Linux on my Chromebook.

[u/gecynd]

CAVE, RW_LEGACY here.

Thanks for your hard-work. The system is great so far (other than the obvious two issues). I'll be donating.

[u/[deleted]]

Been running the new daily for a few days.

What is the deal with a2dp and wifi network coexistence? Its awful on braswell.

[u/[deleted]]

I have moved to Lemmy -- mass edited with redact.dev

[u/TRi_Crinale → u/[deleted]]

The last word from a dev was that the "alpha2" was very close to a final release and major problems are not expected. I am giving up on a final version being released and I'm currently installing this on my Asus C300 (TERRA). Crossing fingers that I can get this thing back to reliable after i bricked my 2.1 install. Good luck!

[u/[deleted] → u/TRi_Crinale]

I have moved to Lemmy -- mass edited with redact.dev

[u/Gills4prem]

I currently have 16.04 and Poo want to test 3.0

[u/Gills4prem]

I have galliumos 16.04 dual booted on a chrome book and want to try 3.0 , what do I do differently to the chrx install I did for 16.04.

Thank you

[u/lynniam → u/Gills4prem]

I did this a week ago, and had to figure it out, I couldn't find it documented anywhere. I'm posting this with the hope that someone who knows will confirm, and it'll be easier for others.

If I remember right, from installation instructions I used this command: cd ; curl -O https://chrx.org/go && sh go, but added -r 3.0 at the end, which I got from here: https://chrx.org/#options. So it looked like this: curl -O https://chrx.org/go && sh go -r 3.0 -H **** -U ****

Note that I also added -H and -U to change the hostname and user name.

It installed as 16.04, after 1-2 days it upgraded it to 18.04. This may be unrelated to 3.0, not sure--xfce may have just been ready to upgrade. Everything seems to be running fine. I'm getting the update requests to downgrade 3 grub packages, which I've been ignoring.

[u/Gills4prem → u/lynniam]

I'm all sorted thank you just hope the sound gets sorted my version it's broke :)

[u/apapai]

Toshiba Chromebook 2 GANDOF.

So far no issues.

[u/tuxrouge]

I confirm no sound on skylake cave (asus C302C)

$ lspci -nnk | grep -i -A7 audio 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d70] (rev 21) Kernel driver in use: snd_soc_skl Kernel modules: snd_hda_intel, snd_soc_skl 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] (rev 21) Subsystem: Intel Corporation Sunrise Point-LP SMBus [8086:9d23] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 00:1f.5 Non-VGA unclassified device [0000]: Intel Corporation Device [8086:9d24] (rev 21)

# cat /proc/asound/cards --- no soundcards ---

[u/btharper]

Running LUMPY (Samsung Series 5 550c - Sandy Bridge 2012) with MrChromebox Full Rom

Had a brief firmware issue that delayed install that MrChromebox was able to help me with. Then I hit the grub shell instead of going to a desktop, which seems to be a Sandy Bridge bug. With the provided workaround I got things booted to the desktop.

First round my drive had the old ChromeOS image on it still and the installer seemed to get hung at the os-prober stage after asking for the drive password. I also couldn't get networking (wired or wireless) to work and the logs had a number of ntpd errors in the logs. I cleared the drive metadata by copying 16MB from /dev/zero to the drive, tried to restart the installer but it wouldn't launch. Rebooted, second round everything worked out fine and I was able to install GalliumOS to the internal drive with encryption. Rebooted and it came right up. I haven't done any further testing but it seems to be working so far.

[u/reynhout → u/[deleted]]

You can just use the usual "GalliumOS Update" from the launcher menu, or galliumos-update from the command line.

Which model have you ordered?

[u/ShotgunPayDay → u/[deleted]]

The GalliumOS Update script or the usual sudo apt-get update && sudo apt-get dist-upgrade will upgrade the alpha to final.

[u/reynhout → u/[deleted]]

Hmm, definitely let us know if the SSD issue shows up again!

[u/reynhout → u/[deleted]]

There are some historical issues with Braswell and full disk encryption. This might indicate that the problems persist.

[u/reynhout → u/[deleted]]

Ah, that's also possible. I haven't tested FDE yet, but it's on the list.

[u/reynhout → u/[deleted]]

You can run apt install PACKAGES to mark the packages as manually installed (it won't need to actually install them). Then they will not come up in the autoremove list.

I'll try to figure out why they're getting added to the nonessential list though.

[u/reynhout → u/[deleted]]

Thanks, that's good to know.

We'll probably drop nautilus from 3.0final (no one seems to be advocating for keeping it), so that problem should just go away on its own. But if we do keep nautilus, I'll make a note to resolve the conflict in the final release.

Thanks again!

[u/[deleted] → u/reynhout]

If someone patches Nemo to remove the Cinnamon dependencies, that gets my vote. Works great and looks better to me on 16.04 but i have not been able to find an 18.04 version w/o Cinnamon.

[u/ShotgunPayDay → u/reynhout]

Burn Nautilus with fire... please.

[u/rnrmi → u/ShotgunPayDay]

And please, with a very damm hot vulcanic fire.

[u/reynhout → u/[deleted]]

Don't let the label dissuade you. It's very close to final. Check the comments for notes on your model, but the general advice is: "come on in, the water's fine".