On 6/17/24 20:21, David Wright wrote:
On Mon, 17 Jun 2024 at 08:42, Alex Johns <chris352...@gmail.com> wrote:
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
good luck
cheers Chris
Hi Chris
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?
Many thanks
Dave
Hi Dave
glad you have got it booting
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.
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.
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.
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.
Once you have edited the file replace it in /etc/default using sudo
Thunar and reboot.
If you have replaced the grub file then you need to run sudo update-grub
to reset the boot parameters
I have included an attachment of one of my versions of grub which may
suit your purposes if you can't boot normally.
Good luck and let me know how it goes
cheers chris
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT=noacpi nomodset""
GRUB_CMDLINE_LINUX=""
GRUB_DISABLE_OS_PROBER=false
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=800x600
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
--
xubuntu-users mailing list
xubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/xubuntu-users
