Results 1 to 2 of 2

Thread: A curious question regarding Radeon & the latest kernel

  1. #1
    Join Date
    Apr 2018
    Location
    In S.E. Iowa, on the Mississippi River
    Posts
    973

    Default A curious question regarding Radeon & the latest kernel

    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?
    HP Compaq desktop Leap15.2, Win10, Win7
    Toshiba laptops Leap15.2 & Win10, HP AiO Leap 15.2.
    I can now print with openSuSe Leap! Can Scan now, could be better!!
    I can backup my iPod and iPad with Windows, can't with Linux.(Will get there someday!)

  2. #2
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    3,952
    Blog Entries
    1

    Default Re: A curious question regarding Radeon & the latest kernel

    Quote Originally Posted by Bill_L View Post
    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....

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •