linux-samus icon indicating copy to clipboard operation
linux-samus copied to clipboard

Ubuntu 14.04 LTS Not booting with 4.2.5ph+

Open jwhipp opened this issue 10 years ago • 24 comments

When booting, I get some odd coloration at the top of the screen. Hitting enter causes that to go away but then I just have a cursor at the top of the screen.

Is 14.04 supported?

jwhipp avatar Oct 30 '15 18:10 jwhipp

I have dealt with this issue. the odd coloration is actually your grub menu, but the resolution in the grub config is something that the pixel can't deal with. you can still navigate the grub menu with the arrow keys if you are able to guess what option you have selected. once you get it to boot, you can change the resolution/screen modes in your grub config to something that works.

c0z3n avatar Oct 30 '15 18:10 c0z3n

I've tried arrowing down and hitting enter with varying increments (1 down, 2 down, etc.) and hitting enter and I can't get it to boot.

jwhipp avatar Oct 30 '15 20:10 jwhipp

Alright...I was able to get the grub menu configured so I could us it with the Pixel 2.

I can confirm that this kernel will not boot for 14.04 LTS. Not even getting the output about loading the image, so there's no crash or debug info as a result.

That's making me suspect that this is supported for 15.04+ only.

jwhipp avatar Oct 31 '15 23:10 jwhipp

What grub graphic config did you use? Just for future reference.

AdaRoseCannon avatar Nov 01 '15 00:11 AdaRoseCannon

Comment out:

GRUB_HIDDEN_TIMEOUT GRUB_HIDDEN_TIMEOUT_QUIET

Uncomment/Add:

GRUB_TERMINAL=console GRUB_GFXMODE=640x480

I used grub customizer from this ppa for speed in testing:

https://launchpad.net/~danielrichter2007/+archive/ubuntu/grub-customizer

In terms of this issue:

If I had to guess, the init system isn't being fired even though the kernel is loaded. I get the loading messages if I select the 4.2ph recovery image, but nothing happens after that.

jwhipp avatar Nov 02 '15 18:11 jwhipp

I think others have been able to use that kernel with 15.04 but there are also reports about boot issues although noone was ever able to figure it out as far as I can tell. The grub graphic corruption is independent of the OS (as you've probable guessed). I use console output for grub instead of graphic and that works fine.

raphael avatar Nov 03 '15 01:11 raphael

I think I might have figured out why. I was able to get 15.10 installed and have a working boot menu thanks to those settings I found for grub.

On 14.04, there is a the 4.2 and 4.2 (recovery) boot options. On 15.10, there is a 4.2, 4.2 (recovery) and a 4.2 (upstart). For some reason, the upstart option which is needed for 14.04 isn't installing. Could be an issue with the deb package, not sure. But it looked to me like the init system isn't firing up so it makes more sense now that I know there's supposed to be an upstart option available.

jwhipp avatar Nov 03 '15 03:11 jwhipp

I can confirm this issue is present in Elementary OS Freya as well, which is based on Ubuntu 14.04.

therocco avatar Nov 08 '15 18:11 therocco

I updated to 4.3.3, curious to see if that's still an issue? It seems the debian build script was updated upstream.

raphael avatar Jan 05 '16 17:01 raphael

The issue is in your grub config. If you could enter into the grub command line (which you technically can, but can't see, since it won't display properly), you could run vbeinfo, which would tell you that the 2015 Pixel (at least with my version of SeaBIOS) only supports a resolution of 1280x850x16! How silly.

You can fix this by modifying your grub config (/etc/default/grub for me) with this line. Then mount /boot and do all of your grub update stuff (grub2-mkconfig -o /boot/grub/grub.cfg for me, but different for you probably).

EDIT: I may have spoken too soon. I can't tell from the comments if people are experiencing grub menu issues or black screen issues post-bootloader.

ehegnes avatar Jan 07 '16 03:01 ehegnes

Somebody probably ought to write a fancy script to automate this across distros. Maybe a simple sed invocation with some privileged commands to update the grub config. I don't have too much of an interest in doing this, but I will if nobody else wants to take the bait.

ehegnes avatar Jan 07 '16 03:01 ehegnes

@ehegnes Thanks, I'll try it as soon as i get out the office :)

polentino avatar Jan 07 '16 08:01 polentino

Sadly, I wasn't able to make it work on my Linux Mint 3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu Oct 22 09:41:40 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux . I tried to edit /etc/default/grub, and add the line mentioned by @ehegnes, that is,

GRUB_GFXMODE=1280x850x16

and then ran "sudo update-grup", but i only got a black screen. I tried different configuration of GRUB_GFXMODE and GRUB_TERMINAL (just in case) but I got nothing, and I'm running out of ideas :(

polentino avatar Jan 08 '16 00:01 polentino

yep, grub2.

2016-01-08 3:56 GMT+01:00 Eric Hegnes [email protected]:

Ooof, that's a bummer. This is grub2 that you're using, yes? grub2 is versions past 0.97.

— Reply to this email directly or view it on GitHub https://github.com/raphael/linux-samus/issues/54#issuecomment-169878839.

H: Who is Watson without Sherlock Holmes? G: Watson was a genius in his own right.

My personal blog: http://polentino911.wordpress.com/

polentino avatar Jan 08 '16 08:01 polentino

Is that still an issue with the latest release?

raphael avatar Jan 17 '16 06:01 raphael

With Mint 17.3 yes, it's still an issue. Basically I've tried to combine various GRUB_GFXMODE and GRUB_TERMINAL, but I couldn't get past the grub screen. I also tried with grub-customizer just in case, but nothing again. With Ubuntu.... well, I can't say anything because I can't even run the Live ISO, due to the very same graphics issue. Which makes me wonder if someone really succeeded to install and run any recent $buntu on a Pixel 2: as far as I understood, @jwhipp did install it (but there's no instruction about how he did it).

polentino avatar Jan 21 '16 21:01 polentino

Instructions regarding getting graphical grub menu are in my comment above on Nov 2, 2015.

The problem is the 4.x kernels don't kick off upstart (the init system).

jwhipp avatar Jan 21 '16 21:01 jwhipp

@jwhipp my bad, I was in a hurry and I wasn't clear enough. I did try your instructions on Mint 17.3 (which is based on Ubuntu 14.04), but I had no luck. Probably because they changed something compared to a vanilla Ubuntu, but that's just my guess.

Anyways, I was referring at the comment where you said you managed to install 15.10: how did you do that? Because all I've gotten so far, as soon as I hit Enter on the SeaBios menu to boot from my Live Usb, was an immediate black terminal displaying the following error:

graphics initialization failed Error setting up gfxboot boot:

And from there, I couldn't do anything else, at all. Not even with this workaround. I downloaded Kubuntu and Xubuntu (15.10) too and once again, same error. Tried a different usb drive, same error. Tried on the laptop I use at work, and this time I could see the Live installer, every single time. Am I missing something?

Edit: The moment I submitted this comment, a thought crossed my mind: did you, by any chance, upgraded your existing 14.04 installation to 15.10?

polentino avatar Jan 21 '16 23:01 polentino

I'm stretching, but what is your SeaBIOS version @polentino ?

colemickens avatar Jan 21 '16 23:01 colemickens

No worries @colemickens, I'm really out of ideas so any suggestion is very welcome :) It's the stock version, 20150225_120401-build122-m2.

polentino avatar Jan 21 '16 23:01 polentino

I also install elementary os (0.3.2, based on Ubuntu 14.04. I'm with the stock BIOS, didn't change anything). It boot up when with the stock Kernel, but when I install this one (4.x) I also get the some odd coloration at the top of the screen, and the system don't boot up. When I tried to install Ubuntu 15.10 (Gnome) it was OK. And the old kernel (3.x from tsowell repo) also works fine.

nirgn975 avatar Jan 22 '16 08:01 nirgn975

is that still an issue with latest?

raphael avatar Aug 24 '16 20:08 raphael

I gave up using Mint, and installed instead GalliumOS which was made exactly to provide a complete Linux support for Chromebook(s), so I suggest anyone to do the same. I followed their instructions to install the kernel provided by @raphael, and everything worked fine since then ;-)

polentino avatar Aug 26 '16 08:08 polentino

@raphael I upgrade to Ubuntu 16.04 and it was fine. I think you can close this issue since a new LTS was released and it's works with it.

nirgn975 avatar Aug 26 '16 11:08 nirgn975