MX Tweak Graphic adjustment from live USB to working system on SSD?
 

Good morning everyone.
I have a bit of a unique situation.
Yesterday I decided to change from one laptop to another. In order to simplify the process, something which I've done in the past by the way, I went ahead and took my MX Linux SSD out of the old laptop and installed it in the new/other laptop. The other laptop was a royal PITA to work with since it had a pressed together housing as well as three thin strand cables which had to be disconnected and reconnected again. It's a process that I'd prefer not to have to do again. I'd like to leave the laptops as they are now, without installing the drive into the older laptop again.

That said, I didn't pay attention to the fact that the older laptop was using AMD graphics while the newer one is using Intel graphics. Consequently (so I believe anyway) the boot process gets stuck. During the process there's an error indicating a graphic issue. The boot process definitely works to apx. 50 percent before getting stuck at a black screen (no errors) with a flashing cursor that can't be used for any commands. It also goes by too quickly for me to take a photo. Then I remembered that MX Linux has MX Tweak which allows you to customize the graphics that are being used, something that would enable me to switch from AMD to Intel.

So I booted up into the Live MX .iso which I have and that was no problem at all. Then I entered MX Tweak and changed the setting from AMD to Intel which was also not problem. But of course the setting wasn't saved on the working disk since I was using a live system via usb. So the question is this:
How can I implement the change from AMD graphics to Intel graphics on the working SSD once I've booted into the live usb system? If possible, please explain this step by step since I have no idea how to utilize MX Tweak via the console in order to make the changes remain set on the SSD system.
Thank you.

To make a change on an installed system from a 'live' Linux, you need to chroot into that system so that you are not attempting to modify files on the 'live' system which is read only. Many tutorials at various sites explaining this process including the one below.

https://forum.manjaro.org/t/howto-ch...ribution/34071

Thank you. This is helpful for letting me know how to enable changes onto the primary drive. But this does not tell me how to change usage of the current AMD graphic to the default Intel graphic driver instead. I'm familiar with chroot and using commands, but I do not know how to make changes to the assigned gpu settings within the installed system, from one driver (AMD) to another one (Intel). MX Linux has MX Tools as well as MX Tweak for this. Those are GUI tools which I now need to be able to use from the command line instead.

When I've swapped out Linux drives in other machines before, this problem didn't occur before because apparently the graphic assignments were always the default installation settings. This time the graphic settings need to be changed from what's on the system right now (AMD) to a standard Intel driver since the new laptop only has Intel gpu available for graphic use.

In your initial post, you indicated that you made the change and the problem was that you made it on the 'live' system so now you need to use the same process after chrooting. I don't use MX and have no familiarity with MX Tweaks. Usually a user can start a program such as this from a terminal. You could try find it with variations of mx-tweaks using whereis or which mx-tweaks.

Well I suppose what I really needed was a response from an MX Linux developer. There's no way for me to use the correct commands for what I need to do without knowing exactly what those MX Tweak related commands are. So there's no solution here, but I'm going to fix the problem by installing MX from scratch again. Ultimately this will get me to my goal faster. Thanks for the replies. ;)

I doubt you would get a response from an MX developer here, maybe at their forums but that isn't likely either. Typing some spelling variation of mx-tweak in a terminal seems like a pretty simple thing to test.