Off-topic, and I’m probably going to get in trouble for posting this but …
Some cherry-picked quotes from the No boot with kernel 6.2 thread:
It is a 15 years old museum piece…. As there is continous development of hardware and software you can‘t keep backwards compatibility forever…
@suse_rasputin nvidia cards have a product lifetime of 10 years of support. Something has to break at some point, as the user base declines for old cards I suspect the kernel developers don’t have the hardware to test (do you expect them to test everything?) so rely on bug reports to try and fix.
For myself personally, I don’t expect them to have and test all and/or old hardware. I would hope they’d respond to detailed bug reports, including suggestions on how to build debug kernels/modules and capture their output.
And in this case where there’s a post exactly showing the problem and providing a patch for it. There shouldn’t be any “we can’t accept this patch because it might break something else” when the patch clearly shows a coding error (out of bounds array access) that’s obvious from static code analysis and should be fixed even if it coincidentally never caused a problem before. And if there is some secondary or tertiary effect, that’s also a newly exposed bug which needs to be addressed.
In my little world: change nothing, nothing will break. So it’s win7 times? Really?
I’ve been a LInux booster for almost 30 years now, making fun of the Apple and M$ bigots who don’t have any of these problems … because their only support option is, “Your machine is no longer supported. Please buy a new one.”
I accept that there will be problems and I’ll have to help however I can with them, but this issue – or more specifically how it’s been handled – is shaking my faith.
that’s business as usual with TW, change over to leap and done
This is my first experience with Tumbleweed, and it’s something I resisted for a very long time. I feel I was forced into it because I can no longer live with the 3+ year release cycle of Leap. I’m getting killed being stuck on GCC 7 and Python 3.6 and have to move forward.
I’ve always thought along the lines of the following, that there’s a conflict between the claims about Tumbleweed stability and the reality of using it:
From Latest updates killed my GUI (4th week of Jan'23) - Kernel 6.8.1?:
Those are all valid points, of course, but it might be nice to put that on the website before people install it. Currently, it only says “Tumbleweed – Get the newest Linux packages with our rolling release. Fast! Integrated! Stabilized! Tested!” It’s not until you get to the second “learn more” option on the installation page that there are any warnings about who should not use Tumbleweed or what can happen.
And as before, note that I’m not averse to working around problems. I understand the limitations of the OBS automated testing. I’d like to see an openSUSE flavor that’s halfway between Leap and Tumbleweed, but think that between delaying my zypper dups and snapper I can probably achieve that by myself.
Practical question: I originally installed TW from Snapshot20230420 which I think was already 6.2 and this problem. So I can’t snapper back before it. Can I zypper dup to some earlier repo and get back to where it might work on my system?
Also:
My practice with Tumbleweed, is to keep one kernel from the previous series. At present, that’s a 6.1 kernel. And I will keep it around until 6.3 kernels show up.
Can anyone point me to documentation on how to do this? And I thought TW always had to be kept in dist-upgrade sync, that you couldn’t mix packages compiled against a different kernel. Or is that only for modules, like if I ever can get the closed-source NVIDIA driver working?
Thanks for listening to my complaints.