New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GalliumOS 2.1 Live Image boots to GRUB shell (PARROT, other Sandy/Ivy Bridge models?) #342

Open
reynhout opened this Issue Feb 28, 2017 · 35 comments

Comments

Projects
None yet
@reynhout
Member

reynhout commented Feb 28, 2017

The GalliumOS 2.1 ISO boots to the GRUB shell on PARROT.

Installation is reported to succeed without issues, so it's just a matter of getting past the initial boot.

Manual workaround:

grub> set root=usb0,gpt3
grub> set prefix=(usb0,gpt3)/boot/grub
grub> linux /casper/vmlinuz boot=casper file=/cdrom/preseed/galliumos.seed acpi_osi=Linux tpm_tis.interrupts=0
grub> initrd /casper/initrd.img
grub> boot

Alternately, PARROT users can install from the GalliumOS 2.0 ISO (https://galliumos.org/releases/2.0) and then update packages.

The boot failures should be straightforward to resolve in the ISO GRUB config, but will require access to hardware (or a very patient tester!).

@ReddestDream

This comment has been minimized.

ReddestDream commented Mar 1, 2017

I can be your tester. ;P

I found this issue early in testing. Not sure how it resurfaced . . . :/

Just not today. But Thursday I'll be around. Got work today.

@NoPinky

This comment has been minimized.

NoPinky commented Mar 1, 2017

I also have a PARROT and can help resolving the problem. I also had this described issue that after install the only thing that boots up is the GRUB console. So now I have Ubuntu Mate running.

@ReddestDream

This comment has been minimized.

ReddestDream commented Mar 2, 2017

grub> set root=usb0,gpt3
grub> set prefix=(usb0,gpt3)/boot/grub
grub> linux /casper/vmlinuz boot=casper file=/cdrom/preseed/galliumos.seed acpi_osi=Linux tpm_tis.interrupts=0
grub> initrd /casper/initrd.img
grub> boot

I can confirm that this works.

@reynhout Let me know if/when you have test ISOs ready. Thx. :)

@reynhout

This comment has been minimized.

Member

reynhout commented Mar 2, 2017

@ReddestDream Awesome, thank you. Did you try the full install to verify that post-install boot works properly? That was a report from initial testing, but a few things have changed since then.

We could easily "fix" the ISO by specifying that config, but it will fail for other Sandy/Ivy models (and for SD card, I suspect). I'm not sure why this model is behaving so differently.

@ReddestDream

This comment has been minimized.

ReddestDream commented Mar 2, 2017

@ReddestDream Awesome, thank you. Did you try the full install to verify that post-install boot works properly? That was a report from initial testing, but a few things have changed since then.

No. I haven't tested fully installing.

We could easily "fix" the ISO by specifying that config, but it will fail for other Sandy/Ivy models (and for SD card, I suspect). I'm not sure why this model is behaving so differently.

Is it a problem with the USB number? C710 has 3 USB ports and 2 EHCI HUBs. And the SD card won't be working anyway on C710 with Class 10 cards without this fix incorporated:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1307674/comments/23

@coltondrg

This comment has been minimized.

Member

coltondrg commented May 15, 2017

I have a PARROT too, @reynhout, I just stopped using it actively because it's slow. :P
Fwiw, it also lacks a storage device.

@MonkeybrainsDan

This comment has been minimized.

MonkeybrainsDan commented May 18, 2017

Just wanted to chime in and say this also effects Lenovo X131e STOUT models but the workaround works.

@coltondrg

This comment has been minimized.

Member

coltondrg commented May 18, 2017

It may be wise to just take down the 2.1 sandy image at this point (or at least change the link on galliumos.org/download to the 2.0 release)

@ReddestDream

This comment has been minimized.

ReddestDream commented May 18, 2017

We could easily "fix" the ISO by specifying that config, but it will fail for other Sandy/Ivy models (and for SD card, I suspect). I'm not sure why this model is behaving so differently.

So, what other devices would fixing this break? Does anyone know?

It may be wise to just take down the 2.1 sandy image at this point (or at least change the link on galliumos.org/download to the 2.0 release)

Seems rather silly to take it down. Could you not just put up some info about a workaround needed for some models?

@coltondrg

This comment has been minimized.

Member

coltondrg commented May 18, 2017

That's an interesting question. I actually doubt that it would. I don't remember specifically, but I remember that the Sandy image started out as a specific PARROT image (I don't remember when the last parrot image was, iirc, it was pre-beta1 release when we first started attracting attention), after which we realized that most other Sandy Bridge models had the same downfalls, so we renamed things. I'm not sure if it's still there, but for a long time there was a dummy package in the repos called galliumos-device-c710 which just pulled in galliumos-sandy as a dep

@ReddestDream

This comment has been minimized.

ReddestDream commented May 18, 2017

So, with SNB/IVB, unlike the other platforms, the devices, other than SNB/IVB Parrot, are not variants of one base board. This has made developing UEFI firmware for them more difficult.

We have fully working UEFI firmware for Parrot (IVB/SNB; CoolStar and I both have IVB Parrot. I also have SNB Parrot boards), Butterfly (SNB; Two testers checked it), and Stumpy (SNB; MrChromebox has one).

Stout (IVB) appears to be working fine, but we've only had one solid tester (MonkeybrainsDan). Lumpy (SNB) has some issue with its device-specific Embedded Controller ACPI config and can't boot Windows. I've got someone sending me one to fix that. MrChromebox made some headway on Link (IVB), and we have a pretty solid ROM for that. It's just missing some features we can't add now because the test unit got bricked and obviously it's lacking Windows drivers due to its crazy touchpad config. :/

I say all this because we /are/ trying to cover all these older devices with UEFI firmware and, for them to be able to boot GaOS on the UEFI firmware, a 2.1+ ISO for SNB/IVB with UEFI support needs to be available.

@coltondrg

This comment has been minimized.

Member

coltondrg commented May 18, 2017

Well, we will definitely make sure we have a working 3.x iso, weather that's another sandy iso, or a handful of different isos for several devices. I hate to distribute even more isos, but if it must be done, then it will be done. We're definitely not abandoning those devices. I have an SNB parrot too, but I haven't used it recently. Perhaps it's time to fire it up and do some testing. I would be interested in trying out the UEFI stuff you've got over in your corner of the universe, though it may also be worth noting that I have no desire to run Windows on anything ever.

(Please note, my mention of 3.x here does not in any way imply that GalliumOS 3.x development is underway. The current projected release timeframe is mid 2018 and even at that it's not in any way solid, so don't expect it anytime soon)

@IdiosApps

This comment has been minimized.

IdiosApps commented Jul 9, 2017

I had a similar problem where, after sucessfully booting the GalliumOS iso and installing it, I couldn't go to GOS on boot (USB ejected). I tried to do a reinstall, but I kept booting to GRUB and the iso for GOS wasn't being read. Using Rufus to mount the GOS file as "dd" (not iso) allowed it to be read, and from there on it was smooth sailing. Hope it helps!
n..b on Peppy 2955u, seabios

@Leoazul

This comment has been minimized.

Leoazul commented Jan 28, 2018

@ReddestDream Awesome, thank you. Did you try the full install to verify that post-install boot works
properly? That was a report from initial testing, but a few things have changed since then.

I've used the grub workaround to boot GaOS 2.1 from a usb stick. Then full installed it to my ssd. Everything works fine after the instalation.

I'm on a c710 (SNB) with coreboot (UEFI).

@johncos001

This comment has been minimized.

johncos001 commented Apr 10, 2018

I am also on a c710 (SNB) with coreboot (UEFI). Was able to boot GaOS 2.1 from a usb stick. Not sure how to completely install to my hard drive. Any help would be appreciated. Thanks

@TheRink

This comment has been minimized.

TheRink commented May 23, 2018

Thank you! Your GalliumOS 2.1 ISO install with GRUB shell on PARROT Manual workaround listed above worked on my Acer C710 (unwrite protected & coreboot flashed) Chromebook.

@delmartechdude

This comment has been minimized.

delmartechdude commented Jun 3, 2018

This happened to me on my Samsung Chromebook XE550C22 (LUMPY) with MrChromeBox.tech's Full ROM firmware replacement. Your instructions saved me @reynhout. Thank you so much! Hopefully, we can get this fix into the next version of GalliumOS!

@thromer

This comment has been minimized.

thromer commented Jun 11, 2018

+1, same experience as @delmartechdude on the same model, thank you @reynhout! Lumpy recently hit end-of-life so I expect folks will be turning to GalliumOS.

@MarcKarasek

This comment has been minimized.

MarcKarasek commented Jun 12, 2018

Same problem on both the 2.1 and Alpha 3.0 images on a C710.
Would be nice to have some note on the Gallium Website that this is a problem. Just saying..

@joshtbw

This comment has been minimized.

joshtbw commented Jun 16, 2018

I am on a Samsung 550 (LUMPY), and I can confirm that I can boot to install GalliumOS 2.1 with @reynhout's workaround (with slight changes to the partition number to suit my system) and GOS seems to install without hitches. However, when I reboot I am back at the grub prompt and don't know what changes to those commands now that the OS installed. I have the options of hd0, hd0,gpt1 and hd0,gpt2.

I would like to avoid having to type commands to boot up the machine each time.

Does anyone have suggestions as to how I can achieve this?

@joshtbw

This comment has been minimized.

joshtbw commented Jun 16, 2018

Gopod must be looking down on me and took pity because after reading the grub documentation I found if I issued the commands:

set root=hd0,gpt2
linux /vmlinuz set root=/dev/sda2
initrd /initrd.img
boot

I can now boot into my GOS 2.1 installation without issue. Now it's just finding out how to make these command permanent before I wear my fingers to the bone typing them every time I boot the machine.

Even if I have to type them, GOS is a great step ahead of plain ubuntu I finally have a machine that no longer needs an external mouse (or indeed any rodents).

@coltondrg

This comment has been minimized.

Member

coltondrg commented Jun 17, 2018

Try running sudo update-grub from the booted system, then post the output of cat /boot/grub/grub.cfg

@joshtbw

This comment has been minimized.

joshtbw commented Jun 17, 2018

As you requested @coltondrg:

grub.output.txt

I've tried to read through this, but I'm not a programmer so I get easily lost.

@coltondrg

This comment has been minimized.

Member

coltondrg commented Jun 17, 2018

Hmm. Try rebooting now, that file looks good to me. If it still doesn't work I'll take a closer look at it.

@joshtbw

This comment has been minimized.

joshtbw commented Jun 17, 2018

Unfortunately @coltondrg the result is the same, some text flashes too fast for me to read it and then I'm returned to a

grub>

prompt. TBH this is the third time I've run update-grub I was just hoping you had some long-distance Sunday morning magic for me, but alas.

@coltondrg

This comment has been minimized.

Member

coltondrg commented Jun 17, 2018

Ah, I did assume you had already tried that, that's why I asked for the file before I told you to reboot. Whatever is flashing on the screen might be immensely useful. You think you could get a camcorder to capture it?

@joshtbw

This comment has been minimized.

joshtbw commented Jun 17, 2018

Sure, it'll take a bit of doing but let me strap my GoPro to my head and see what I can come up with.

@joshtbw

This comment has been minimized.

joshtbw commented Jun 17, 2018

And, as if by magic:

capto_capture 2018-06-17_10-00-46_pm2

This is a much clearer capture of the text but if you still can't read it it says:

System BootOrder not found. Initializing defaults.
Created boot entry “Boot0002” with label “ubuntu” for file “\EFI\ubuntu\shimx64.efi”

Can you tell what's going on @coltondrg?

@joshtbw

This comment has been minimized.

joshtbw commented Jun 20, 2018

I think in within spitting distance of solving the problem.

I found that I could boot into GOS if I went through the UEFI interface by hitting esc before grub runs. However, the Mr Chromebox website clearly says the firmware does not support changing or saving settings. If it did allow saving settings, this would be a perfectly acceptable solution to my issue. But reading further on the website I found this choice quote:

image

I noticed that in my installation of GOS has an efi directory is inside the /boot directory. If I moved the EFI directory from /boot/efi to /efi would this solve the problem as now the firmware will be able to find the files it needs to boot? I am hesitant to try this because I don't want to mess up my machine when it's almost working perfectly (for me).

I'm into opensource for the danger, I guess.

I'll report back with my findings.

@reynhout

This comment has been minimized.

Member

reynhout commented Jun 20, 2018

@joshtbw I don't have an answer, but it should be safe and non-conflicting to copy /boot/efi to /efi.

IIRC though, the path difference is non-default but correct for the firmware.

@joshtbw

This comment has been minimized.

joshtbw commented Jun 20, 2018

Yep, it didn't work and, looking more closely at it; you are correct @reynhout.

@simongis

This comment has been minimized.

simongis commented Jun 23, 2018

  • Chromebook Acer C710
  • Added some foil to the jumper connection.
  • Flashed BIOS with Full Firmware from MrChromeBox.
  • Downloaded GalliumOS-Sandy-2.1
  • Created a bootable USB using Etcher
  • Entered BIOS (ESC key)
  • Boot manager --> UEFI USB Device
  • Get the 'Minimal BASH-like line editing is supported' screen

@reynhout pointed me to this issue, which resolved my problem. Just a FYI.

@FabioMen10

This comment has been minimized.

FabioMen10 commented Jul 26, 2018

Fork this and solve problem.
https://github.com/isantop/kernelstub
I found this in git's Pop!_Os
On my Acer C710(Parrot) it worked very well.

@dedeluca

This comment has been minimized.

dedeluca commented Nov 7, 2018

I can confirm this fix worked for STOUT x131e. If only I had checked with a different flash drive sooner.

@btharper

This comment has been minimized.

btharper commented Dec 2, 2018

Ran into this on Gallium 3.0alpha1 on LUMPY with MrChromeBox Full Rom. Manual workaround in the first post worked for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment