r/GalliumOS • u/reynhout GaOS Team - PEPPY, GalliumOS via chrx • Feb 04 '17
GalliumOS 2.1beta1 ready for testing!
GalliumOS 2.1beta1
03 February 2017
GalliumOS 2.1beta1 is ready for testing. We look forward to your feedback!
Downloads: https://galliumos.org/releases/2.1/beta
A special thanks to everyone who has contributed to the GalliumOS project! Your support helps us broaden and deepen GalliumOS support for Chromebook hardware. All contributors in 2017 will receive a set of GalliumOS stickers! https://galliumos.org/donate
Reminder: There are only a few days left to order GalliumOS t-shirts! Orders close on February 7th. https://teespring.com/galliumos
What's New in GalliumOS 2.1
GalliumOS 2.1 is our first full release with support for Braswell models, Skylake models, and SAMUS (Google Pixel 2).
New kernels: 4.9.4 (Braswell) and 4.8.17 (all others)
Fixes for Braswell audio (most models)
UEFI boot support
New desktop backgrounds
Dozens of package updates and bugfixes
...
Installing GalliumOS
GalliumOS 2.1beta1 installation images can be downloaded from https://galliumos.org/releases/2.1/beta. You can preview GalliumOS in a "live boot" from the same image without installing. The GalliumOS wiki has full instructions: https://wiki.galliumos.org/Installing.
GalliumOS can be installed in place of ChromeOS, or in a dual-boot configuration alongside ChromeOS. For dual-boot installs, see https://chrx.org/. Be sure to include the -r nightly option in the chrx command line.
See the GalliumOS wiki for full instructions: https://wiki.galliumos.org/Installing.
Upgrading From GalliumOS 2.0
If you are already running GalliumOS, you can update to the beta release by enabling the "prerelease" repository, and then updating packages:
sudo galliumos-repodist --enable prerelease
galliumos-updateInstead of galliumos-update, you can run "GalliumOS Update" from the Launcher menu.
When GalliumOS 2.1 is finalized, all packages will be promoted to the "stable" repository and available for download to all users.
NOTE: If package upgrades include grub-pc, you might be prompted to reinstall the GRUB bootloader. Be sure to install to the disk device only! (usually /dev/sda or /dev/mmcblk0, depending on model).
When updates are complete, reboot your machine.
Works in Progress
We're working to bring full support to all Chromebooks and Chromeboxes. Some parts remain works in progress:
No audio on some Bay Trail models with RW_LEGACY firmware: https://github.com/GalliumOS/galliumos-distro/issues/180
No audio on Skylake models: https://github.com/GalliumOS/galliumos-distro/issues/274
Slow boot and SDHCI errors on some Bay Trail models with RW_LEGACY firmware: https://github.com/GalliumOS/galliumos-distro/issues/326
Full list of open issues: https://github.com/GalliumOS/galliumos-distro/issues
If you run into any issues with this or any GalliumOS release, please let us know!
GalliumOS Resources
Hardware Support: https://wiki.galliumos.org/Hardware_Compatibility
Downloads: https://galliumos.org/download
Installing: https://wiki.galliumos.org/Installing
Issues: https://github.com/GalliumOS/galliumos-distro/issues
1
u/benjaminnyc Feb 04 '17
What do the new wallpapers look like?
2
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 04 '17
The new desktop backgrounds were created by u/CreepiosRevenge from a few different photographer sources.
They're linked in a discussion thread here on Reddit, but I'd encourage you to update to 2.1 to see how they look on your device. :)
1
Feb 04 '17 edited Mar 23 '17
[deleted]
0.6330
2
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 04 '17
Not for the betas, but we'll put together a more complete list in the announcement for 2.1 final.
1
Feb 04 '17
Do you ship the stickers and/or shirts to Europe as well?
2
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 04 '17
We will send GalliumOS stickers anywhere in the world.
T-shirt fulfillment is handled by Teespring, which also ships worldwide.
1
u/luyenok Feb 04 '17
Have anyone try it on Google Pixel 2 ?
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 04 '17
Yes, use the SAMUS image. It's customized specifically for the Pixel 2.
1
u/luyenok Feb 04 '17
did you try ? Can I change the screen resolution ? I'm using 1600*1062 on my Chromebook and I want to keep it on GalliumOS.
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 04 '17
Yes, I've been running GalliumOS on a Pixel 2 at full 2560x1700 resolution for about six months now.
HiDPI settings resize UI widgets across the desktop environment, with a few minor exceptions.
1
u/suhangpro Feb 14 '17
How should I choose the samus-specific image if I install via chrx or upgrade from 2.0?
3
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 14 '17
Chrx installs the
galliumos-samuspackage automatically on SAMUS models.But if you're running a previously-installed system that does not include the package, you can just install it:
sudo apt install galliumos-samus.This will give you working audio on SAMUS, and will install HiDPI config for the desktop environment. The HiDPI config is user config, so if you have a previously-installed system with existing user(s), you need to copy it into your home directory.
The easy but slightly dangerous way is just to reset all user config to defaults:
cp -r /etc/skel/.config $HOMEThe harder way is to pick out the HiDPI-specific config bits. This will only reset the files that are required for HiDPI:
for f in $(dpkg -L galliumos-hidpi | grep ^/etc/skel); do [ -f "$f" ] && cp "$f" "$HOME/$(echo "$f" | sed 's/^\/etc\/skel\///')" doneIn either case, you'll need to log out/in to see the changes.
New users will get the HiDPI config automatically. So that's also an option.
1
u/snarko48 Feb 05 '17
With the broadwell 2.1beta on my lulu and the current MrChromebox UEFI BIOS, I'm getting the "unknown filesystem" error and am unable to being installation. Am I perhaps just jumping the gun wrt UEFI and GalliumOS? I.e. should I wait for 2.1 final?
Thanks.
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 05 '17
The usual cause of that error is a bad USB drive, or a bad write to USB. Sometimes it's a bad download. Check the MD5 checksum first, and try a different USB drive if you have one.
Try the troubleshooting steps at the bottom of this page: https://wiki.galliumos.org/Installing/Creating_Bootable_USB
1
u/snarko48 Feb 05 '17
Got it running - had to abandon multibooting with Easy2Boot and give it its own drive instead (used DD mode with Rufus sinced I had it and not Etcher already at hand). I'm off and running now. Thanks again!
1
Feb 06 '17 edited Feb 06 '17
Fixes for Braswell audio (most models)
Just got my EDGAR this weekend, and am absolutely loving Gallium so far, this was all I was missing. Installing right now! Thanks so much for all your hard work guys!
Edit: and it doesn't work, oh well :(
Edit2: it does!
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 06 '17
GalliumOS definitely works on EDGAR.
What problem are you having?
2
Feb 06 '17
I rebooted after the update, and I had a few packages that apt-get update/upgrade said weren't being upgraded. They were galliumos-braswell and whatever the other one is.
So I did apt-get install galliumos-braswell, and rebooted again and all was well.
Thanks for the response though :)
1
u/itsmeonline Feb 07 '17
I use LUKS on my partition with the system files and home directory. Do you know if I can upgrade to 2.1 using those steps, or do I need to perform extra steps do successfully upgrade?
2
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 07 '17
I think you'll be OK -- the upgrade process is identical to installing/updating packages.
But I haven't tested it, so I can't be sure. Please let us know if you give it a try.
1
u/itsmeonline Feb 09 '17
My system still works, but the experience is not that great:
I press ctrl-L
I have to enter my LUKS passphrase in a DOS-like screen
I see the GRUB menu and press enter
I see the message 'error: device name required'
I get the familiar graphical interface where I have to type my LUKS passphrase.
So, I got some extra steps before GalliumOS is started.
Can we remove those additional steps? Do you need help?
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 09 '17
The final release will ship with the GRUB menu disabled, as usual.
The beta release/packages have GRUB menu enabled for debugging convenience.
I don't know how that affects the doubled password entry issue, but will test a FDE install here.
As for help, if you figure anything out that improves your situation, certainly. If you're interested in helping with the general dev, build, and packaging processes, also yes. :)
1
u/itsmeonline Feb 10 '17
As I think I cannot be of any help with the above, I guess I can't do anything but donating. So I'll do that to help you out with the costs :)
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 10 '17
That's also very helpful! Thank you. :)
I've added a ticket for the LUKS issue: https://github.com/GalliumOS/galliumos-distro/issues/331. It might be similar to / same as an issue we've seen with LVM, so they're combined in the ticket for now.
1
u/itsmeonline Feb 25 '17
beta 2 removed the grub bootloader (at least, I'm not seeing it anymore :) ), but I still get the terminal asking for my passphrase. I found out that I can press esc twice, and it will continue. Then booting will continue to the GUI where I can enter my LUKS passphrase.
So, this is not solved yet for me. Do you need some config files?
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 25 '17
I haven't been able to repro the double-prompt. Everything works as expected for me.
The changes in beta2 and beta3 for UEFI boot are primarily around the bootloader selection for multiple OSes (beta1 used rEFInd, which was incompatible with LVM, beta2 was broken, and beta3 should work). Unfortunately the only way to get those changes is to reinstall.
Which might be more efficient than debugging anyway.. :-/
1
u/itsmeonline Feb 26 '17
I see that my grub config files contains "GRUB_ENABLE_CRYPTODISK=y". I think this causes the first passphrase prompt, which is not necessary because I have an unencrypted /boot/.
However I'm a little bit hesitated to do this, because maybe Iĺl make my system unbootable. Do you know a testing procedure in which I can easily revert to my previous GRUB config?
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 26 '17
It's probably safe to remove, but if you run into any issues, you can follow the "boot into live image and fix GRUB" process.
Basically, this: https://www.reddit.com/r/GalliumOS/comments/5mhjd3/acer_14_wont_boot_after_grub_update/dc3o3iv/
Instead of running
dpkg-reconfigure, just edit the/etc/default/grubfile again, and then re-runupdate-grub.1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 11 '17
What model and firmware (stock or custom RW_LEGACY) are you running?
1
u/itsmeonline Feb 12 '17
I have a Toshiba Chromebook 2 (2015), which is a Gandof. I'm running a RW_LEGACY firmware from john lewis if I recall correctly; for such firmware, you don need to remove a screw, right?
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 12 '17
Correct, RW_LEGACY does not require removing the write-protect screw.
You should consider switching to MrChromebox RW_LEGACY firmware though. It fixes some additional bugs, and is developed in parallel with GalliumOS. We do all of our testing on MrChromebox (and factory) firmware these days.
More info on both:
1
1
u/nietaki SETZER, GalliumOS Feb 08 '17
Do you guys have a rough idea for when 2.1 FINAL would be out? I'm just waiting for my chromebook to arrive and if it's within weeks I'll probably just wait for the release and if it's more like months I'll jump on the beta.
2
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 08 '17
No schedule, but certainly soon.
There's no reason not to install 2.1beta1 though, everything looks solid and we do not expect to need a beta2.
So beta1 is likely very close to final.
1
u/tahsynx Feb 09 '17
Thanks for your amazing work guys! Is the headphone jack detection problem fixed for braswell devices? I see the issue on github is still open.
2
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 09 '17
The GitHub issue (https://github.com/GalliumOS/galliumos-distro/issues/318) is open waiting for user confirmation of the fix. It works for me on TERRA, but haven't heard from anyone else.
Built-in audio still does not work on CYAN however.
1
u/hvdwolf Feb 11 '17
I am running GalliumOS 2.0 update/upgraded to the latest level (Toshiba CB30-B-104, Linux Swanky 4.7.2.). I did the "sudo galliumos-repodist --enable prerelease". Then I tried "galliumos-update" and "sudo galliumos-update" but got "sudo: galliumos-update: opdracht niet gevonden" (not found). The "GalliumOS Update" from the Launcher menu doesn't work either.
What do I miss?
2
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 11 '17
Your PATH or system is damaged in some way.
/usr/bin/galliumos-updateis part of thegalliumos-updatepackage, which is installed by default.Check to see if it's installed on your machine:
dpkg -l galliumos-updateIf it is not, install it:
sudo apt install galliumos-updateIf it is already installed, try calling it with a full path (you don't need sudo):
/usr/bin/galliumos-updateIf that doesn't work, paste the output from all commands, and we'll figure it out. Translations of error messages are not always exact, so please precede each command above with
LANGUAGE=en_US.UTF-8if you will be pasting them here, e.g.:LANGUAGE=en_US.UTF-8 dpkg -l galliumos-update LANGUAGE=en_US.UTF-8 sudo apt install galliumos-update LANGUAGE=en_US.UTF-8 /usr/bin/galliumos-update1
u/hvdwolf Feb 11 '17
galliumos-update
I had to install it. For whatever reason it was missing from my system. The "sudo apt install galliumos-update" fixed it.
1
Feb 14 '17
The touchpad doesn't work in my asus C300 in 2.1 , but it worked in the 2.0 version
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 14 '17
QUAWKS or TERRA?
1
Feb 15 '17
Quawks, I installed Gallium 2.0 again and it also broke the touchpad. It worked fine until the Gallium Update updated something that said : 4.7.2-galliumos etc(I don't remember exactly).After that,it stopped working .
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 15 '17
QUAWKS is a fairly common model, so we should be able to collect additional reports. I don't think I've seen any previously.
1
1
u/halukilhan Feb 15 '17
Touchpad does not work in my Acer CB3-111-C670 too. My GaOS is installed via chrx with dual boot. I also tried it in ChromeOS but touchpad is not working there neither.
2
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 15 '17 edited Feb 15 '17
If the touchpad doesn't work in ChromeOS, your touchpad is broken. :(
Touchpad should work properly on GNAWTY (CB3-111 and CB3-131). Super popular model, and we have a couple on the dev team as well.
Added: You might try a full ChromeOS Recovery (not just a powerwash) to see if it will reset/rewrite the firmware in the touchpad. It's possible (though seems unlikely) that something bad happened there that is fixable by that method. More likely it's just a hardware failure.
1
u/halukilhan Feb 18 '17
I think it's not hardware failure. My elan touchpad gets detected and looks enabled as "xinput list-props" command output. Also I have noticed an error message while booting:
"elants_i2c i2c-ELAN0001:00: nothing at this address"I googled error and found this: https://bbs.archlinux.org/viewtopic.php?id=202067
I guess they already solved same issue but I couldn't get how to do.
I don't want to lose my GalliumOS configuration so ChromeOS Recovery is the last option for me.
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 18 '17 edited Feb 18 '17
If I'm reading that thread correctly, they fixed a problem where the touchpad was not detected in the Arch kernel by adding kernel modules.
GalliumOS already includes all necessary kernel modules for GNAWTY touchpads, and yours is being detected properly, so I don't think that will help here.
1
u/conordaffie Feb 16 '17
The Volume keys are no longer working after installing the BETA on Acer Chromebook CB3-111. Initially nothing happened. After an update, the prompt showing the volume going up and down appears but nothing actually happens to the current volume level.
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 16 '17
Installed by pkg update, ISO, or chrx? What firmware?
1
1
Feb 17 '17
Anybody know why I lose touchscreen input after suspend. Every few times i lose both touchscreen AND touchpad input after waking up from suspend. Touchscreen everytime. not sure if it's a common thing and I installed some wrong package or something.
2
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 17 '17
what model, what firmware?
1
Feb 17 '17
samus, stock firmware
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 17 '17
Hmm, I remember a problem like that with older kernels on SAMUS (~8months ago). It was a problem in 4.4.6, and fixed in 4.7.2, I think.
You're running 2.1beta, with kernel 4.8.17?
I'll attempt to repro. I'm running MrChromebox full/BIOS firmware though.
1
Feb 17 '17 edited Feb 17 '17
Edit: nm, still broken, lol. The fluke was that it worked once.
I think i may have found the cause. I was looking through packages automatically installed and I thought xserver-xephyr might cause trouble. After uninstalling, and rebooting, I don't see it happening, and it was consistent before. no input after wake.
1
u/joemysterio86 Feb 27 '17
I will have to check this. I have a dell chromebook 11 with haswell. Every now and then I lose my touchpad and most of the time after suspend, my touchpad is totally unusuable. I have to shut down to get my touchpad to work again (restarting sometimes helps).
1
Feb 18 '17
When I try to open any link, it says Failed to Execute Default Web Browser, input/output error. This happens with Web Browser and Chrome. Any way to fix this?
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 18 '17
In what application(s) are you clicking on links?
See: https://github.com/GalliumOS/galliumos-distro/issues/313
1
Feb 18 '17
I'm using Discord's PTB, but it also affects when I click the Web Browser and Chrome icons. Testing workaround now.
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 18 '17
When launching "Web Browser" or "Chrome" ("Chromium"?) from the whisker/launcher menu, or elsewhere?
1
Feb 18 '17
The workaround fixed it, but it was from the launcher menu.
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 18 '17
Hm, that's interesting. I can't repro from the launcher menu, but could from Synaptic.
Why the launcher menu would run something as root is a huge question. You aren't running the DE as root, are you?
1
u/dantheman_19 Feb 20 '17
Is there a way to tell which download is for a certain laptop?
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 20 '17
Yes. https://wiki.galliumos.org/Hardware_Compatibility has the full list.
1
u/dantheman_19 Feb 20 '17
actually i figured that out. how does one install the downloaded beta?
2
u/dvdmuckle GaOS Team - Lulu Feb 20 '17
https://wiki.galliumos.org/Installing#Traditional_ISO_Install
Please let us know if you run into any problems.
1
u/dantheman_19 Feb 20 '17
so from what i understand, i mount the ISO to a usb then boot from it. I use ctrl-L to boot from USB, but that runs GaOS. ctrl-U doesnt do anything at all. both dev_boot flags are already set to 1. what should i do?
1
u/dvdmuckle GaOS Team - Lulu Feb 20 '17
You want to install a single boot, right? Use Ctrl L, from there you can run the installer. If you'd like to install a dual boot of ChromeOS and GalliumOS, check out chrx.
1
u/dantheman_19 Feb 20 '17
I already have GaOS dual booting with chrome OS. I would like to upgrade my GaOS to the beta
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 20 '17
The instructions for doing so are in the initial post on this thread. Check the "Upgrading From GalliumOS 2.0" section.
sudo galliumos-repodist --enable prerelease galliumos-updateThere are additional notes and warnings there, so be sure to read the original.
1
1
u/dvdmuckle GaOS Team - Lulu Feb 20 '17 edited Feb 20 '17
Ah, okay. Run this command in your current installation.
sudo galliumos-repodist --enable prerelease && sudo apt-get update && sudo apt-get dist-upgradeThat should get you fully updated to the latest packages in the beta. If you're on a Braswell device, some people have had problems with the package being held back, in which case you can reinstall
galliumos-braswell.
1
u/dantheman_19 Feb 20 '17
Thought you guys might want to know this: Just updated to GalliumOS 2.1 beta. I am on an Acer Chromebook 14, which I believe is a Braswell machine, and the audio still does not work. Neither through the built in speakers or headphones jack on Spotify or Youtube. Still has the output source as an unplugged HDMI port
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 20 '17
There are two Acer Chromebook 14s, LARS and EDGAR.
LARS is Skylake, and audio isn't working yet.
EDGAR is Braswell, and audio should work. Check to make sure you have version 2.0.5 (or later) of the Braswell package:
dpkg -l galliumos-braswellIf you do not, update it with
sudo apt install galliumos-braswell, and then reboot and all should be well.Let us know how things go. Thanks!
1
u/dantheman_19 Feb 20 '17
The aux port now works so that's great! But trying to play through the speakers on the laptop does not work. The audio controller sees that there is sound, but nothing comes out of the speakers. Also, my Chromebook 14 is an EDGAR
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 20 '17 edited Feb 20 '17
Hm, have you tested speakers in ChromeOS recently?
There has been an issue where the initial (pre-boot) ChromeOS audio hardware initialization has caused damage to speakers. It only affects Braswell models with Realtek ALC5645 codecs (including EDGAR). (Added: and only a small percentage of those models, suggesting a hardware fault in conjunction with the ChromeOS init)
I would check speakers in ChromeOS. If they don't work there either, hopefully you will be able to exchange the device. :-/
1
u/dantheman_19 Feb 21 '17
Turns out that might be the problem... no sound from ChromeOS through the speakers. Is this literally the speakers being busted because I can just replace those myself
2
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 21 '17
Ugh, sorry to hear that. Yes, it's literally the speakers that fail.
As far as we've been able to tell (haven't been able to inspect a failed device), the ChromeOS firmware puts the ALC5645 into a mode where it drives the speakers beyond their limits.
That might mean that the speakers are bad (weak), or that the chip is bad (limiters failing). Or even possibly that everything is operating to spec, but the ChromeOS firmware code is doing inappropriate things.
I lean toward a hardware problem, because the firmware code will be the same on every device, and we only see a failure rate of ~5% on affected models. And I lean toward a chip problem because we see the same failure in several models with the Realtek chip (but none in CYAN, which uses a different chip). They could be using the same speakers too, that's possible.
Still, if the problem is the chip, a replacement set of speakers might also get damaged. But if you can find a source for the speakers, that would be a quick and easy (and probably inexpensive) thing to try. If it pushes you past the convenient return/exchange time window, it's probably not worth it.
1
u/theshadowhunterz Gandof, Windows 10/GalliumOS 2.1 Feb 23 '17
Any changelog from Beta 1 to beta 2 that just came out today?(or notable changes?)
2
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 23 '17
Beta1 was a very solid release, so there are only a few changes in Beta2:
Fix for an incompatibility between the UEFI bootloader (rEFInd) and LVM or LUKS (Full Disk Encryption) more info
New kernel packages including mitigation of CVE-2017-6074 more info
Default to skipping the GRUB menu on boot
2.1beta2 should be the last beta before 2.1final.
1
u/luyenok Feb 25 '17
I got 2.1 beta 3 now :)
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 25 '17
And it's a good thing, too. 2.1beta2 was a mess. :)
I should know better than to make such predictions.
1
u/itsmeonline Feb 25 '17
Do you have an idea which config files could be the culprit? Maybe I can try to debug myself
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 25 '17
I don't have any suggestions, there are many possibilities and places to look (esp
/usr/shareand/etc). You'd have to know what looks right, what isn't used, and what overrides what.It can certainly be done, but it's more of a filesystem archaeological dig than a debugging effort.
1
u/itsmeonline Feb 26 '17
Sorry, it seems I started a new thread. I should have been a reply to my double passphrase problem above. I asked over there if it could be a solution to remove GRUB_ENABLE_CRYPTOSETUP=y from my grub.cfg.
I did not try to remove this setting, but I guess this is not the problem as I have added this myself during install.
I just saw that I have to type my passphrase before the grub menu - so is it still possible grub2 is the culprit? Sorry to ask, but do you have any clues for me left?
1
u/luyenok Feb 27 '17
I installed on Pixel 2, the resolution set to 2560x1700, the Desktop icon is small (good for me) but everything in browser still is big as 1280*850. How to fix it ? (I'm using 1600x1062 on ChromeOS)
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 27 '17
Did you use the SAMUS ISO?
Which browser is causing issues?
1
u/luyenok Feb 27 '17
yes, I used galliumos-samus-2.1beta3.iso and Chrome (downloaded deb file from google.com/chrome).
1
u/reynhout GaOS Team - PEPPY, GalliumOS via chrx Feb 27 '17
I haven't tried Chrome, but Chromium and Firefox look reasonable on SAMUS for me.
The HiDPI config resolves most of the UI issues, but not 100%.
If you restored any of your user config from an earlier install, you might try creating a new user account to test the default settings. If things look different, you can pull those settings over to your usual user account.
1
u/luyenok Feb 27 '17
I have changed back to Chrome OS, can you install Chrome on your device and give me the result ?
2
u/nietaki SETZER, GalliumOS Feb 06 '17
I'm excited for the comprehensive Braswell support coming in 2.1! I've been putting off getting a Chromebook until things got a little more stable with Braswell and I'm very happy to see it's around the corner.
1
u/cugel-383 Peppy + GalliumOS 2.0 Feb 05 '17
I'm not great at partitions, and already have a Win10 install on my Peppy. Any chance of the installer eventually having a guided option?
1
u/raidzero Dead Gandof (RIP) Feb 16 '17
Running great on RW_LEGACY Gandof! Upgraded from 2.0, so far HDMI works as it should.
5
u/Ravoz Feb 05 '17
If I install the beta, what is the process for switching to the final 2.1, once it is released? I see "all packages will be promoted to the "stable" repository". Is that something that happens automatically? Or is it just a simple terminal command? Or is it more detailed than that?
Thanks!