Re: A curious question regarding Radeon & the latest kernel

Originally Posted by
Bill_L
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:
Code:
# 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.
This chrooting process is the same method for resetting root's password.
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.
Reg. Linux User 211409 *** multibooting since 1992
Primary: 15.3, TW, 15.1 & 13.1 on Haswell @earthlink.net
Secondary: eComStation (OS/2) &15.2 on i965P/Radeon
Tertiary: Debian, Fedora, Mageia, more on Rocket Lake & older Intel, AMD, NVidia....