Edit:
The solution is in third post
Hi,
I’m a bit annoyed by the topic.
I’ve already searched the internet for a solution, but I can’t get any further.
A little more to start with… Yes, I did the installation according to the instructions from here made! And the dGPU also works quite well with steam 
About the system:
Ubuntu 22.04.04 LTS
Kernel 6.5.0-1018-oem
syscrash@framework16:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.4 LTS
Release: 22.04
Codename: jammy
syscrash@framework16:~$ java --version
openjdk 11.0.22 2024-01-16
OpenJDK Runtime Environment (build 11.0.22+7-post-Ubuntu-0ubuntu222.04.1)
OpenJDK 64-Bit Server VM (build 11.0.22+7-post-Ubuntu-0ubuntu222.04.1, mixed mode, sharing)
Linux Framework16 6.5.0-1018-oem #19-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 14 21:40:46 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
I’ve tried the following so far:
-
Start the CurseForge launch using
"DRI_PRIME=1 "
“DRI_PRIME=1!” # why is that! at the end? I read this in the forum in connection with steam here and also tried it out. On Steam, the version with an exclamation mark works for me. -
Start java using a script in the Minecraft Launcher options
The script is from here.
I tried both variants.
#!/bin/sh
DRI_PRIME=1 exec /usr/bin/java "$@"
and
#!/bin/sh
export DRI_PRIME=1
exec java "$@"
-
Use another launcher (MultiMC5) that directly supports dGPU, such as steam.
Here I failed to import the profile I had previously installed in CurseForge and gave up in frustration and am now writing to you in the hope of a solution -
Oh, I also tried to deactivate the internal graphics using the bios, but failed because of the missing option in the bios
The output of “vulkaninfo | grep “GPU[0123]” -A 10” gives
syscrash@Framework16:~$ vulkaninfo | grep "GPU[0123]" -A 10
WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Failed to CreateInstance in ICD 0. Skipping ICD.
GPU0:
VkPhysicalDeviceProperties:
---------------------------
apiVersion = 4206847 (1.3.255)
driverVersion = 96477185 (0x5c02001)
vendorID = 0x1002
deviceID = 0x15bf
deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
deviceName = AMD Unknown (RADV GFX1103_R1)
pipelineCacheUUID = e75ab6b8-f0a3-6b04-20f4-e8b7f1c24530
--
GPU1:
VkPhysicalDeviceProperties:
---------------------------
apiVersion = 4206847 (1.3.255)
driverVersion = 1 (0x0001)
vendorID = 0x10005
deviceID = 0x0000
deviceType = PHYSICAL_DEVICE_TYPE_CPU
deviceName = llvmpipe (LLVM 15.0.7, 256 bits)
pipelineCacheUUID = 32332e32-2e31-2d31-7562-756e7475332e
--
GPU2:
VkPhysicalDeviceProperties:
---------------------------
apiVersion = 4206847 (1.3.255)
driverVersion = 96477185 (0x5c02001)
vendorID = 0x1002
deviceID = 0x7480
deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
deviceName = AMD Unknown (RADV GFX1102)
pipelineCacheUUID = e10a6cab-7e01-d585-a6dc-927c1b1fd8cd
Why is my dGPU called “deviceName = AMD Unknown (RADV GFX1102)” instead of “AMD Radeon RX 7700S (RADV NAVI33)”?
When I search, I keep coming across the tip that I should set it under “Windows” in the graphics card settings so that this or that program should be tested with the dGPU… that of course doesn’t help me under Linux, nor this tip is almost always suggested in conjunction with an Nvidia and not for an AMD Radeon.
Is there something like this for Linux too? I read somewhere that there should be something like this in the XServer settings.
For example, I would also like to run other programs with the dGPU, for example my FreeCAD or the slicer for my 3D printer or GIMP simply where graphics and rendering of 3D images or video editing are involved.
Why doesn’t the system recognize that the CPU is running at 100 °C and switches to the dGPU instead of staying on the iGPU?
I’m attaching a few more pictures, if any data is still missing, please let me know.
PS: I’ve been using Linux (with a long break from Apple) for years (1999) only Debian or Gentoo and not Ubuntu, I’ve got that down for now so that it doesn’t fail because of something fundamental, I’m a bit rusty after all that years Mac OS X 
When I inserted the script here as described on the website, I always got the same error when I tried to start Minecraft. I tried it with and without hooks.
The error message:
Here I tried to insert the line “DRI_PRIME=1 %command%” in all variations into the line, which had no effect.
No matter what I tried, it was always unsuccessful, even starting the entire launcher via the console, which showed that Java was supposedly using the dGPU, the iGPU remained active and the CPU briefly heated up to 100 ° C and then went to 70 -80 °C down.
And via console
I start it with this command:
