If you have graphic issues with that computer it is because of this:
Graphics: Device-1: NVIDIA C51PV [GeForce 6150]
I do not have nVidia hardware and I have no idea what is best way to handle that nVidia chipset.
Another thing to remember that Rock/OMLx 4.3 does not work with secure boot enabled in BIOS. I recall that you had previously had Windows on this box so might be worth checking the BIOS and being sure that is disabled.
Thanks for the reply, Ben.
Clarification:
I did not have Windows on this computer,
Windows was previously installed on the original 40GB drive, which was removed from another computer. The most recent attempt replaced that 40GB drive with two WD 13GB drives.
This computer does not have any secure boot function setting options appearing in the BIOS, so there’s nothing I can do about that.
The “basic graphics” boot setup works fine, the default boot option does have some glitches. The Nvidis graphics are on-chip MB graphics. I’ve used this same board for many years with various incarnations of open mandreva, Although there would be some mentions in the logs about Potential restrictions, I never had problems with the video previously. (I never attempted anything particularly out of the ordinary as far as video graphics.)
From looking at the logs I saw many repeated any repeated entries that something called uvedma (spelling?) was not responding as expected. I’m not familiar with that, but from what I can tell it has to do all it has to do with overseeing overseeing devices, So I ran the disk checking utility in K Partition Manager, and that showed no errors.
Do you think I should forward this information to the bug report link you sent me?
Yes.
Again the Calamares installer installed boot loader. Did you try to boot in to the newly installed operating system?
Why report something this way? Post the exact journal entries or post the actual journal log. Edit: But udev actions are critical so that could be something very important.
A 13GB / system could get to full rather easily.
Booting into default GUI, logged in as user, returns this screen before I can open a terminal:
Booting into Advanced Options GUI, logged in as user, returns the same screen message.
Booting into Advanced Options CLI, logged in as user:
open terminal and run:
$ sudo /usr/sbin/calamares-post-script
returns:
“command not found”
sudo sh /usr/sbin/calamares-post-script
Thanks.
Booting into Advanced Options CLI, logged in as user:
$ sudo sh /usr/sbin/calamares-post-script
returns:
Curious:
Is there any diagnostic routine that will check an existing system for possible problems and report and/or offer suggestions/attempt to correct them?
Thanks.
The only packages that did not get removed (according to the log posted) are:
virtualbox-guest-additions
calamares
console-setup
grub2-editor
Removing those will also remove a few unneeded dependencies. This would not have anything to do with you other current issue.
A guess: Your current issue is most likely related to graphics not working.
You can try adding xdriver=vesa nomodeset to the linux line of the of the first entry (the default one) in grub2 menu. The instructions for how to edit are at the bottom of grub2 menu. Why? Because this is what you had to use to boot the ‘Live’ iso. Also you could try xdriver=nouveau nomodeset. Or look around the internet and see what boot parameters work for GeForce 6150 graphics or install proprietary driver from nividia web site. GeForce 6150 is not trouble free, people had problems with this when it was new.
Also you can try booting to console mode, logging in there, and running one of these commands and see if any work:
startx
startplasma-x11
startplasma-wayland
systemctl start sddm
systemctl restart sddm
Remember only one of those at the time. Any error messages may be useful, but if you post something please post all of any error message. Users with problem do not know what might be important to a developer.
Beyond this you need some that knows more than me.
@deltakprime what about to try install a rolling ISO?
I’d suggest as a first test the very minimal system ISO ‘slim’.
The latest [HERE].
Download from command line :
$ aria2c http://file-store.openmandriva.org/api/v1/file_stores/d6cfca0ff5f8d3fac5e9e5a9a9ca9afb81ad7811
Don’t forget to compare the checksums;
use rosa-imagewriter tool or dd only;
LVM and Raid setups with Calamares installer are not supported.
Thanks, Ben.
You have been more than helpful so many times for me.
I want you to know that you are truly appreciated.
Do you have a suggestion as to the best way to remove those dependencies? (CLI, I presume.) Even if it doesn’t solve the immediate issue, I’d like to know how to do that.
In addition, I can search for specifics regarding drivers, etc. for that graphics chip.
(Maybe someone on the forum has some experience with it.)
I will look into your suggested CLI commands (one at a time!) and see if they make any improvements.
TTYL
I hadn’t considered that.
Curious…why might that might make a difference?
As said
Just remove the packages I listed, dnf will automatically remove the unused dependencies for those packages.
$ sudo dnf rm virtualbox-guest-additions calamares console-setup grub2-editor
Thank you.
Ok, something different to report:
In an experimental mood, I re-configured the drives:
Primary master: WD 40GB
Primary slave: DVD-ROM
Secondary master: WD 13GB
Secondary slave: WD 13 GB
I booted into the live 4.3 system from USB stick, selected the Troubleshooting>Basic Graphics mode, selected Install from the launch menu…
…and it completed without a problem!
Atached is the Calamares installation log file located at:
/root/cache/calamares/session.log
(I had to add the .txt extension so I could upload it here.)
session.log.txt (387 Bytes)
It is very brief, only five lines long.
At any rate, the system installation completed without incident (according to the Calamares GUI, anyway) and boots as expected, minus a few graphics glitches, but I will continue to attempt to resolve those.
Maybe now is the time to post the bug report.
Thanks again guys, for all your help with this.
TTYL
Mike
Don’t know if this constitutes a solution that will be helpful to anyone else, but if that serves as a resolution to the thread, I will mark it as being resolved.
That means no log was generated. This is a bug in OM Calamares installer. And this is why we ask users having problems to use the command from terminal pkexec calamares -d | tee calamares-install.log.txt.
Then what a bug report be for?
Unless you already posted about not entering an administrator password?
(I presume they already know about the Calamares bug?)
Click on the part highlighted in blue.
I believe a developer has already fixed that in Cooker. Any fix will be in future versions of OMLx. The expected behavior will be that in that case installation succeeds and root account is locked.
Edit: Any problems with graphics please start a new thread with a descriptive title and all the information someone else might need to help.
Edit: Closing thread as user found solution. In this case the solution was to reconfigure drives as stated in this post. Any new issues please start a new thread with a descriptive title and all the information someone else might need to help.
