One of my drives I want to use(so my windows drive stays away from Linux) exhibits odd messages depending on how I boot it.
if I boot as updated I get tossed into that RESCUE> mode that gets me nowhere(because I don’t know what I’m doing!)
If I do the edit at the Grub screen and add ‘nomodeset’ at the end of the ‘linux’ line, it opens a screen with my router IP, followed by prompt ‘ENTER LOCALHOST’, and I’ve tried root and my names but it keeps going back to that ‘LOCALHOST’ prompt. I did not try 127.0.0.0 however.
in order to do the workaround for Radeon graphics from the long thread,
I need to be in the ‘system’ to apply it, right?
or is there TTY I can get into to add the workaround?
Boot something other than the installed system. The installation media will do this by selecting rescue. Once booted this way, assuming the rescue boot configured working network, you’ll need to mount the installed system and chroot into it, whether to apply the bug’s workaround, or to install some other kernel:
# mount /dev/***devicename*** /mnt
# mount -o bind /proc /mnt/proc
# mount -o bind /sys /mnt/sys
# mount -o bind /dev /mnt/dev
# **chroot** /mnt
# mount -a
At this point you are running the installed system, and can do anything you could ordinarily do, except for running an X session, and a few things that won’t get in the way of what you need to do to fix your booting problem.
If you wish to use the workaround, and don’t have the required module to copy, you can boot something else, download the kernel it needs to come from, “enter” the rpm from an MC session, navigate to the module file, and copy it to a USB stick or network share for transfer to the problem PC.