If you can chroot into the installed system you could try installing the 6.12.x LTS kernel as a possible workaround, usable until 6.15 or newer kernels get a fix, or until 6.12 support expires late next year, if this new hardware wasn’t brokenly backported into it as it apparently exists in 6.15.
Greetings!!! New to Linux / Tumbleweed here for about 2 months now.
Can you please specify why to not use Ventoy? Because me personally I installed it with it and the reason is I don’t have a lot of USB sticks and I tried so many distribution before without success (because I’m on the audio production side too),with Tumbleweed being the first try. So far after two months or so there isn’t any significant problem that I faced.
With all that being said if there is a way to check anything that is correct because I used Ventoy for the installation it will be much appreciated.
Have a good one!. 
1 Like
Ohhh… well, doesn’t matter now I’ll take a sleep and as soon I wake up I’ll start again the process to reinstall openSUSE including to create from scratch the USB at least it’s not so late on my journey to Linux, and also I can’t even imagine how it will be if needed support not knowing that. The only downside is that I have to set up again all the things around audio with geekosdaw etc. but anyway.
Thank you very much.
If it works, don’t fix it…
The first problem with booting from a stick is getting the target computer to recognize there is a stick there in the first place.
In this context Impression and ImageWriter, both offerings from OpenSuse are not recognized, so there’s no point using them. Balena Etcher and Ventoy are both recognized. There is also dd for people good at command-line gymnastics - I’m not.
Ventoy is useful, precisely in that you can keep all your .iso’s in one place and change them if there’s an update. As I posted in a comment above, the developer is taking steps to address the concerns raised in the forums and on the app’s github itself. From his comments, part of the problem is he doesn’t fully understand how github works but he now knows there are people willing to help.
2 Likes
Ok I agree with the if it works don’t fix it.
But as @hui said and also on the quote above
There will not be support for any installation of openSUSE made with Ventoy.
If that’s the case and as I’m new on Linux in general if by any chance I come to a point of needing support it will be hard to guess on things that I don’t know.
And also if there is indeed any security/privacy concerns around a system that is configured via Ventoy, then I don’t know.
Basic openSUSE install rules via USB.
Must binary copy the iso without changes ie no additions or subtractions to the USB device not a partition on the device. ISO is totally boot ready
1 Like
Yeah I was so impressed that I can have more than one iso images in a single usb. I didn’t knew openSUSE doesn’t recommends or even give any support for installations made that way. so now I already backed up my secondary SSD, some screenshots, browser bookmarks,exported my Reaper DAW configuration, and exported all chats from Duck AI. So I’ll do all the installation process the right way again including the optimization for audio production. So far Tumbleweed worked very well considering that I didn’t played a lot with creating music, I didn’t got any sys internal error like on all the distros I tried before not even a Reaper crash.
I use Ventoy all the time and have never seen it change ANY ISO file or write ANYTHING to the main storage. Ever! Just make sure you get Ventoy from the source, not some other place. I always create my Ventoy USB device to support both BIOS and EFI, And I have never had opportunity to test on one of those little fruit machines.
Anyways me personally only because openSUSE maintainers as said they don’t give support for installations made with Ventoy. I already created a single bootable with TW via impression app. And installed it again. The good part on this is in comparison with my first installation and because I didn’t knew that YaSt is unmaintained and not recommended to use especially the online update on TW (I had some quirks with that back then) plus because I’m on audio side of things too I installed geekosDAW repo and the packages for the realtime optimizations and after that I started an app called geeDAWupdate which messed up with a dependency? named libffado to a point that KDE Plasma reverted to the icewm and I was going crazy 
.
Until I joined the geekosDAW group on telegram and thankfully everyone helped me .
So to close things up this time I took it more wisely without using yast software management nor yast online update . And after a thought I went to the site of openSUSE software in proaudio’s repo to find the exact name of the package rt-config & rtcqs . So after that I went to terminal with sudo zypper in rt-config rtcqs.
So far everything seems to be sweet. I’m feeling grateful for the community & kinda proud for myself for the last step above.
1 Like