On 12/01/2019 22.46, Marc Chamberlin wrote:
I am in the process of trying to upgrade one of my
computers to OpenSuSE
15.0 and running into a number of problems. I first started with
OpenSuSE42.3 x64 with the KDE/Plasma desktop, and I tried to do an in
place straight upgrade. I will also mention that my OpenSuSE42.3 system
had something broken with the network drivers so I did not have access
to the internet directly from it. So I used my laptop to download the
OpenSuSE 15.0 iso file and burned it to a DVD. I mention this because I
am suspicious that this may be what is causing me some of the problems I
am experiencing, though I do not understand why that should be the case.
After my first attempt to upgrade my computer to 15.0
it failed to boot.
My research lead me to discover that the installer had changed the grub
configuration so that it was trying to make calls to linuxefi and
initrdefi. I don't use the efi filesystem on this computer and have no
desire to do so. (don't get me started on how much troubles I have had
with efi. I use it on my laptop only because I am using solid state
drives and it seems that I must use efi on it.) My BIOS in the computer
I am trying to upgrade has EFI turned off and only uses legacy file
management. So I manually edited the grub configuration file and
removed the efi suffix of these calls, i.e. made calls to linux and
initrd instead, and the boot up succeeded.
Strange, but ok, understood.
However, that lead me to another mess, after logging
in to my account, I
discovered the KDE/Plasma desktop was not working properly. I had a few
konsole windows that opened up (ones I had left open when I brought the
system down) but the plasma part of the desktop was not there. No
background, no kicker bar, no mouse activity or the ability to right
click and bring up the pop up menu dialog etc. In other words almost
useless, although all the services and background tasks I have
configured to run started up fine. (things like Apache, Tomcat, Bind,
DHCPD etc.) I don't know how to recover from this mess, I tried
reinstalling all the KDE and Plasma packages but no joy, so I decided to
try a different approach -
At this point you should just have created a new user and login as him
instead. Seeing that you have not yet formatted this partition, you can
My next attempt was to install OpenSuSE 15.0 into a
partition but I cannot get past the partitioner. It appears it is trying
to force me into using the EFI boot system.
I don't know what is used to decided bios/uefi, but it is doing the
wrong detection. And I don't know how to change it either.
I don't allow the OpenSuSE
installer's partitioner to decide for me (it's defaults) how to
configure my system as it makes choices that I don't want. Instead I
have it import all my mount points that I have defined in what was my
OpenSuSE42.3 (now upgraded to a broken 15.0) system. That much works
fine and I just move the mount point for / to a new partition so that
the new OpenSuSE15.0 system will be mostly installed in a different
partition and I can keep my old system for the time being.
I tell the partitioner to accept all the new changes I get a complaint -
"Missing device for /boot/efi with size equal or bigger than 256MiB and
filesystem vfat." Why am I being forced into using EFI? My system/BIOS
is configured to use the legacy boot loaders and explicitly turns off
EFI! I cannot find any means of telling the OpenSuSE
installer/partitioner to use the legacy method of boot loading either,
so I am stuck.
Maybe go ahead as it wants, then later install grub your way.
I have one other complaint about the OpenSuSE 15.0
that I want to pass along as it almost destroyed my entire system, had I
not caught it. After I told the partitioner to import all my mount
points from my previous system, I fortunately observed that it had
marked ALL of my mount point partitions to be formatted!!! That is just
plain wrong, the user should NEVER have to opt out of having data
destroyed, but have to opt in to having anything formatted. That modus
operandi really needs to be reversed, formatting of any partition should
never be done by default. I will listen to any arguments to the contrary
but I feel pretty strongly that this should be reported as a bug and
fixed. (I am willing to do so.)
AFAIK, it was reported and ignored. I can't find the report, but it was
said to be intentional, that a new install needs a clean slate. This is
wrong, IMO, the previous YaST partitioner did a better effort at what
needed to be formatted and what not. /home, for instance, was not, while
Cheers / Saludos,
Carlos E. R.
(from 15.0 x86_64 at Telcontar)