MacBook Pro, Mid 2012 | Ubuntu 18.04 partition, installed from USB | Main/original partition is macOS Sierra
Hi ):P After my first several days with Ubuntu booting normally, I now get indefinitely stuck on the purple logo screen with no white dots loaded (pic1). This used to load fairly quickly, maybe one orange dot per second. *The freeze happens with both the plain old Ubuntu selection from GRUB, as well as with the Advanced options for Ubuntu -> Ubuntu, with Linux 4.15.0-34-generic selection, which I'm pretty sure is the same thing.
Advice for similar complaints says to go into recovery mode and do stuff, but my Recovery Mode is frozen too. The Recovery Mode GUI gets displayed (pic2), but my arrows don't work to navigate it. Neither does Enter. :-| It was navigable for the first couple reboots after this whole problem commenced, and then less and less often, and now it's almost never navigable.
*Sometimes--like one time out of every several dozen reboots--Recovery Mode is magically navigable. When this happens, it sometimes freezes after just a few arrow-keystrokes. So for all intents and purposes, I think we should just assume that going into 4.15.0-34's Recovery Mode isn't feasible.
**Also: on one of these magical occasions when Recovery Mode was navigable, I got so excited that I left the menu open for a long time while I googled what to do on my phone. After a while, a [ TIME ] error appeared pasted on top of the screen (pic3)--and then a bunch of other laggy terminal-ish descriptor phrases pasted themselves diagonally all across the screen (pic4). :-? Then when I tried arrowing again, the phrases cleared away. ...No idea what this is about.
However, the "older" Linux kernel--listed as 4.15.0-29-generic--boots just fine when I select it from Advanced options for Ubuntu. So does the older kernel's Recovery Mode, though I don't know why I'd need it.
Mind you, I know next to nothing about...any of this...so I have no idea how I could've screwed up one kernel version and not the other.*(Also, I don't rightly understand how you can load two different kernels on your computer yet still see the same files on both...?? guess I don't fully know what a kernel is) I thought I could just use this older kernel instead because everything seemed at first to be identical. But the wifi on it was screwed up (Broadcom problems), just like when I first installed Ubuntu (I eventually fixed it following this advice)...so from that being non-identical, I extrapolate that other things are non-identical too.
The last thing I remember doing back when I could boot normally was trying to figure out why VLC's audio only worked occasionally, and researching why YouTube videos were loading so slowly (and learning along the way that my MBP has a "dual graphics card" and that's apparently problematic), and potentially downloading packages or doing other root commands to try to fix those problems, though I can't remember what if any.
Did I explain this clearly?? Did I leave anything out? Can anyone help me diagnose what in the HECK might be going wrong??? [-o< Thxxxx
I'm new to Linux, fairly new to the command line, and have little understanding of computer guts. Please phrase your helpful replies closer on the spectrum to ExplainLikeImFive than ExplainLikeIm120.
Hi ):P After my first several days with Ubuntu booting normally, I now get indefinitely stuck on the purple logo screen with no white dots loaded (pic1). This used to load fairly quickly, maybe one orange dot per second. *The freeze happens with both the plain old Ubuntu selection from GRUB, as well as with the Advanced options for Ubuntu -> Ubuntu, with Linux 4.15.0-34-generic selection, which I'm pretty sure is the same thing.
Advice for similar complaints says to go into recovery mode and do stuff, but my Recovery Mode is frozen too. The Recovery Mode GUI gets displayed (pic2), but my arrows don't work to navigate it. Neither does Enter. :-| It was navigable for the first couple reboots after this whole problem commenced, and then less and less often, and now it's almost never navigable.
*Sometimes--like one time out of every several dozen reboots--Recovery Mode is magically navigable. When this happens, it sometimes freezes after just a few arrow-keystrokes. So for all intents and purposes, I think we should just assume that going into 4.15.0-34's Recovery Mode isn't feasible.
**Also: on one of these magical occasions when Recovery Mode was navigable, I got so excited that I left the menu open for a long time while I googled what to do on my phone. After a while, a [ TIME ] error appeared pasted on top of the screen (pic3)--and then a bunch of other laggy terminal-ish descriptor phrases pasted themselves diagonally all across the screen (pic4). :-? Then when I tried arrowing again, the phrases cleared away. ...No idea what this is about.
However, the "older" Linux kernel--listed as 4.15.0-29-generic--boots just fine when I select it from Advanced options for Ubuntu. So does the older kernel's Recovery Mode, though I don't know why I'd need it.
Mind you, I know next to nothing about...any of this...so I have no idea how I could've screwed up one kernel version and not the other.*(Also, I don't rightly understand how you can load two different kernels on your computer yet still see the same files on both...?? guess I don't fully know what a kernel is) I thought I could just use this older kernel instead because everything seemed at first to be identical. But the wifi on it was screwed up (Broadcom problems), just like when I first installed Ubuntu (I eventually fixed it following this advice)...so from that being non-identical, I extrapolate that other things are non-identical too.
The last thing I remember doing back when I could boot normally was trying to figure out why VLC's audio only worked occasionally, and researching why YouTube videos were loading so slowly (and learning along the way that my MBP has a "dual graphics card" and that's apparently problematic), and potentially downloading packages or doing other root commands to try to fix those problems, though I can't remember what if any.
Did I explain this clearly?? Did I leave anything out? Can anyone help me diagnose what in the HECK might be going wrong??? [-o< Thxxxx
I'm new to Linux, fairly new to the command line, and have little understanding of computer guts. Please phrase your helpful replies closer on the spectrum to ExplainLikeImFive than ExplainLikeIm120.