<div><div dir="auto">Were you affected by this bug affecting Ubuntu 4.18 kernel: <div><a href="https://news.softpedia.com/news/canonical-apologizes-for-another-ubuntu-linux-kernel-regression-fix-available-524892.shtml">https://news.softpedia.com/news/canonical-apologizes-for-another-ubuntu-linux-kernel-regression-fix-available-524892.shtml</a></div></div></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Feb 19, 2019 at 11:07 D. Hugh Redelmeier via talk <<a href="mailto:talk@gtalug.org">talk@gtalug.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">| From: Clive DaSilva via talk <<a href="mailto:talk@gtalug.org" target="_blank">talk@gtalug.org</a>><br>
<br>
Note: I barely touch Ubuntu so I may be wrong in important details.<br>
<br>
| I had a problem with my recent Ubuntu 18.10 install which I thought that I<br>
| should share. I was running Ubuntu 18.04 on an older Pentium (R)Dual Core<br>
| CPU E5200 with 4 gigs of ram and things went well. About 2 months ago, I<br>
| noticed that there was an Ubuntu 18.10 so I thought that I would give it a<br>
| try. So I downloaded Ubuntu 18.10 with kernel 4.18.0.10 and it worked well<br>
| with all my machine learning stuff (Anaconda3, etc.).<br>
<br>
So far, so good.<br>
<br>
| About 2 weeks ago,<br>
| Ubuntu informed me that I had a kernel update so I downloaded the update<br>
| (kernel 4.18.0.14) and tried to install it. Couldn't get past the boot<br>
| screen, so I reinstalled 4.18.0.10 but right away I was informed of the<br>
| waiting update.<br>
<br>
I'm not 100% sure what you mean by "the boot screen".<br>
<br>
(1) trying a previous kernel<br>
<br>
My systems always have the most recent three installed kernels<br>
available for booting. All you have to do is talk to grub at boot<br>
time to select one of the two older kernels. Did you try that?<br>
<br>
If that works, you have something more concrete to report.<br>
<br>
(2) getting more information out of the boot process<br>
<br>
GRUB invokes the kernel with parameters. Ted pointed you at a page<br>
one some parameters that you could try tweaking.<br>
<br>
Before you do that,<br>
<br>
- boot your system<br>
<br>
- early on, get grub's attention<br>
<br>
- choose the boot entry you wish to use<br>
<br>
- edit that entry (there's a key for that). (The edit is only for this<br>
boot.). Remove "quiet splash" from the kernel parameters. This<br>
will cause the boot process to be logged to the console. That way you<br>
can often find out where it goes wrong.<br>
<br>
You should be able to tell if it is a kernel problem or an X problem<br>
or something else.<br>
<br>
I admit that the result looks like gobbledygook to the unfamiliar.<br>
<br>
(3) lock the system to a kernel that works.<br>
<br>
I'm pretty sure that there are magic things to do with apt-get or<br>
whatever you use to update to say<br>
<br>
(a) don't update the kernel (if, in fact, that turns out the be the<br>
problem), or<br>
<br>
(b) keep this working kernel even if you install new ones. Also: you<br>
need to tell grub to keep using the kernel you like.<br>
<br>
| I googled the issue and the only comment that made sense was<br>
| to block Wayland being loaded and instead default to Xorg by adjust<br>
| custom.conf \etc\gdm3. That made no difference to my situation as described<br>
<br>
Xorg and Wayland both talk to the kernel. But there is usually a<br>
difference between a bug in them and a bug in the kernel.<br>
<br>
You need to narrow down the problem: identify the component that is<br>
the most likely culprit. Or give up (which might save you time).<br>
<br>
I imagine that there is a way to boot to text console mode (its been years <br>
since I've done that). From there you can start X by hand. That might <br>
give you insight.<br>
---<br>
Talk Mailing List<br>
<a href="mailto:talk@gtalug.org" target="_blank">talk@gtalug.org</a><br>
<a href="https://gtalug.org/mailman/listinfo/talk" rel="noreferrer" target="_blank">https://gtalug.org/mailman/listinfo/talk</a><br>
</blockquote></div></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div>Eric Brown MD HBSc FRCPC<br></div><div dir="ltr">For encryption, OpenPGP public key available on request.</div></div></div></div>