Am Mittwoch, 16. Jan 2019, 15:14:29 schrieb Stefan Seyfried:
Am 16.01.19 um 13:36 schrieb Rainer Hantsch:
Hello, and good day.
I am often installing openSuSE on customer hardware (Laptops, Desktops, Servers). This worked well in the past, but in last time I notice an extreme (not to say scarying) increase of issues with Leap 15.0.
Excuse me, I am not convinced. Show me those weapons of mass destruction^W^W^W^W bugzilla entries. My experience with the SUSE kernel team is, that if make good bug reports for such issues, they are often fixed. :/
On younger hardware (not older than 1-2 years) this Leap 15 often causes troubles with even booting from the USB stick.
I do not own such new hardware, so cannot comment on that.
Two years old hardware is actually "slightly ancient" (in terms of hardware progress), not new. If one comes to me and wants to bus a computer, I cannot really sell him old hardware. :D
Even when successfully installing it somehow, it is not sure that ACPI is working, so Leap does the full shutdown but not power-off, and/or that the battery-status is available at all. Even worser, when running the default update in KDE (simply allowing all suggested updates), often ends up with a system where the boot process stops after displaying "Loading initial ramdisk".
Again, show us those bugreport numbers. Kernel regressions are fought even harder by the excellent SUSE kernel team.
As long as I can remember back it never(!) happened that an existing ISO image was replaced by a newer one. (Tumbleweed may possibly be the first exception, but I don't use it, so don't nail me up, I usually use Leap.). So the overall situation is as follows: 1. I have only one possible USB Stick with this one ISO on it. Using it, I always get the same base system installed first. (I am talking of a default setup, because it has to work reproducable, so I use the default settings.) As result the system may (or may not) boot and/or install at all. --> AT THIS POINT THE PROBLEM IS !!!!! It may boot or not !!! 2. Possible updates happen, as the name sais, always later and require a already installed (and at least partially running) system. 3. So when I cannot install the initial system on some hardware, the existing update mechanism will not work at all! -> Back to 1. 4. Because it does not install, I cannot get any useful information for debugging, so I also cannot supply something useful for bugzilla. Also, I am no developer. 5. Points 1-4 finally made me join to this list (after many years) again, to let related people know about the situation.
Complaining here will most likely not solve your problems. Creating bugzilla reports might.
Because I am almost sure that most of this problems will vanish with a new kernel (because this also made a very poorely running LEAP perfectly running after manual kernel replacement, I asked here if I can get a new ISO for testing on systems where the default one does not work. I ASKED. And I also suggested to make such DVD-ISO available for download. When this happens, I will be happy to test this ISO with the next problematic hardware, and then I can give feedback here. This is - from my point of view - the best and easiest way to find out if something works or not, especially when it is so clear to see where the problem is located. See above, points 1-4, too. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org