Hello,
ROME Plasma6 wayland AMD CPU (newer than 2017)
As another Lunduke follower I installed this a few days ago and had enormous issues with it barfing at “blah desktop main py” at the time I found a post somewhere which gave me a small change to the script. Now reinstalling it I can neither remember the change or the site that showed it … duh!
Can anyone help
Ta
Mal
Not exactly what you asked for but generally a good idea is to get the calamares-installation-log.txt. Or a least a screen-shot of the error message. I have difficulty comprehending why people can not provide an accurate error message. Perhaps that is my own shortcoming?
Look under Installation
A forum search of desktop main py turns up nothing that looked relevant.,
And by the way:
Welcome to OpenMandriva Linux and our forum.
I believe this is what you need:
Specifically (from @rogers):
I’ve since found that changing installEFIFallback to false in /etc/calamares/modules/bootloader.conf works
This is the error that pops up Main script file /usr/lib64/calamares/modules/displaymanager/main.py for python job displaymanager raised an exception. I searched the machine for calamares-installation-log.txt and I couldn’t find it .. where is the little bugger hiding 
Fiddled in displaymanager.conf
#Enable the following settings to force a desktop environment in your displaymanager configuration file:
defaultDesktopEnvironment:
executable: “startkde”
desktopFile: “plasma”
And it installed - now the big moment a reboot !
There won’t be one if the installation failed. To get around that you have to run Calamares from cli with a command that makes the log.
That is what this was for:
I am guessing that what @SomeDudeInAZ posted would be the answer to your issue?
I am doubtful that those changes would work. I think instead you would want to edit /ect/calamares/bootloader.conf setting installEFIFallback to false.
I think this happens when people install other OS’s and then install OMLx but I am not sure. I haven’t used anything but OMLx for a while.
No, Thats all it seems to need. My attempt to upgrade to Cooker was a bit of a disaster so I just did that change and the install sailed through.
I shall now go and find another thread to hassle about why I broke my install with the upgrade
Many thanks to all
Mal
Please use the template (you deleted the majority of to make this post) in the future.
If you are using an iso writing utility, it must write with dd (or with a raw utility) not a hybrid ISO. You can use newer ISO’s with Ventoy now.
Most people break their update/grade by using Discover to manage their repos. We are testing the use of Discover to update and install with dnf but we do not fully support it yet. We had to patch it just to make it use our required command to update. The forum also contains what that command is. I believe it is in the banner on the page (that you probably closed) or may be pinned in this category.
The template didn’t work. it wouldn’t let me check the boxes and then it wouldn’t let me post with them there saying I can’t post links and yes i did read the banner and didn’t use discover.
As I remember it doesn’t matter what the “other” OS is. On my test computer I’ve only got OM installed. But it’s several installations: Rock, Rome, Cooker, Rock Slim, & Rock LXQT in different partitions
As soon as anything else was in the UEFI partition things broke and only changing installEFIFallback to false in “/etc/calamares/modules/bootloader.conf” fixed it.
Thanks, that is helpful information.
I don’t know what happened here, but you can ask @rugyada to give you permission to do that after you clarify what the link was you needed to post. We don’t enable it by default to keep spam posting to a minimum. Any reason why you didn’t reply to this?
The template and the banner are more than just decoration. I brought them up because your first post to get help didn’t really do anything to inform us what is going on. Just that you had a problem with a script. We can’t possibly deduce what issue you are experiencing based on so little information.
It’s also the go-to way for trolls to interact with us. They like to think that because they just hate-watched Lunduke and discovered OMLx that the distro is new and full of people that don’t know how Linux distributions are made or work. It would go a long way to get the help you need if you would put in the effort required to inform us how you need help.
No need, because the user already got the permission (automatically switched from new user to basic user level).
I did check earlier tbh, when I saw the comment, and everything looked as expected even then.
@interele please post a link now to confirm.
Aside, here is the template in details.
Thank you for posting this! I had this exact same issue but couldn’t figure out a decent solution. Where exactly is the displaymanager.conf that needs this change to be made located?
Welcome @sluke0 to the OpenMandriva forum and OpenMandriva Linux.
/etc/calamares/modules/displaymanager.conf
An easy way to edit would be to use the simple test editor nano thus:
sudo nano /etc/calamares/modules/displaymanager.conf
For these kind of quick one off edits I usually open the file from Dolphin and use Kate (or KWrite) myself. (This assumes user is using one of the Plasma isos)
I can’t remember exactly, I am back on opensuse atm. Look through the file and find a section where it tries to give you a selection of desktops and force it to pick plasma. If you are really stuck let me know and I’ll put openMandriva back on the machine and post the file
Mal
Thank you for the super detailed response, very much appreciated
Not sure if I need to make a new post for this or not but I also noticed that the “ROME Plasma6.wayland AMD CPU (newer than 2017)” ISO does not seem to exist when following the link. It currently has no builds. Is it expected to reappear soon?
