<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#969586">
<div class="moz-cite-prefix">On 6/17/24 20:21, David Wright wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAAwBpLJ5NwVJ2jfYparWy_9XpACYheCkfXVGocziUTdkhTXgxw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr"><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, 17 Jun 2024 at
08:42, Alex Johns <<a href="mailto:chris352011@gmail.com"
moz-do-not-send="true" class="moz-txt-link-freetext">chris352011@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
</blockquote>
<div> </div>
<div>Can I suggest then that you try editing the line I
suggested and removing quiet splash and adding nomodset
noacpi in the past that has solved many boot issues for me</div>
<div> good luck
<p>cheers Chris <br>
</p>
</div>
<div><br>
</div>
<div>Hi Chris</div>
<div><br>
</div>
<div>That has worked! Thank you! For my education, what
exactly have we done there? I did see upon reboot that the
scary lines of code are all visible, which I think is the
removal of 'quiet splash' but what does 'nomodset' and
'noacpi' do? And am I okay leaving those in the file
forever, no untoward effects?<br>
</div>
<div><br>
</div>
<div>Many thanks</div>
<div>Dave<br>
</div>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
</blockquote>
<p>Hi Dave <br>
</p>
<p>glad you have got it booting</p>
<p><br>
</p>
<p>Removing quiet splash means you can see the code on the screen
and if there is an issue in the boot process it will stop at the
line which is causing the problem which gives you a chance to sort
out the issue. <br>
</p>
<p>No modeset means don't try to force a display resolution ie
don't set the graphic's card resolution. It will default to
it's native resolution No acpi means don't try to set the acpi
power configuration interface. <br>
</p>
<p>Generally I have found that the ubuntu installer seems to run
into trouble with those two parameters. However once you have got
an install, you can usually boot normally as the installed system
has enough drivers to sort it all out. A simplistic way of
putting it. <br>
</p>
<p>I f you can not boot normally once the system has been installed
to the hard drive then you will have to include that line in your
grub config which can be found in etc/default /grub, and you will
need to copy it first to your desktop using sudo thunar to copy.
Then using mousepad to edit the line. keep the updated grub off
the system to keep it safe in case you ever need it again.</p>
<p>Once you have edited the file replace it in /etc/default using
sudo Thunar and reboot.</p>
<p>If you have replaced the grub file then you need to run sudo
update-grub to reset the boot parameters<br>
</p>
<p>I have included an attachment of one of my versions of grub which
may suit your purposes if you can't boot normally.</p>
<p><br>
</p>
<p>Good luck and let me know how it goes</p>
<p>cheers chris<br>
</p>
</body>
</html>