Running Lenovo p70 with NVIDIA Quadro graphics card. Applied recommended updates and now can only boot into a command prompt.
I issued a journalctl -b command to check the logs. The following messages are in the logs.
Failed to start show Plymouth boot screen
Plymouth-Start-Service: unit entered failed state
Plymouth-Start-Service: Failed with result ‘Core-Dump’ Several core dumps in the root directory for Plymouth
Failed to Start Modem Manager
Failed to start Network Manager
Failed to start manage Install and generate Color Profile
Failed to start xDisplay Manager
I’ve tried advanced booting to a previous version of Tumbleweed 4.4.176-96 with no luck Can only boot into command line mode on Tumbleweed 5.1.3.1
I suspect my NVIDIA card may be the culprit from reading other posts in this forum.
How can I confirm this? Zypper cannot find NVIDIA on my system. I believe the drivers where loaded from Lenovo when I purchased the p70 and not installed by Zypper.
What NVIDIA sites or OpenSuse sites can I visit to determine if there are current drivers for the Quadro M4000M?
Any recommendations to get beyond a command prompt and to a working desktop?
Seeking help and guidance here. Anything is appreciated.
Can only boot into command line mode on Tumbleweed 5.1.3.1
This is the current TW kernel.
I suspect my NVIDIA card may be the culprit from reading other posts in this forum.
I believe mixed repos is the basic problem. Please show input and output from:
zypper lr -d
cat /etc/os-release
Please wrap your paste, including the command and the following prompt, using the # ] icon above the input window. Once this is done, a plan can be recommended.
How can I confirm this? Zypper cannot find NVIDIA on my system. I believe the drivers where loaded from Lenovo when I purchased the p70 and not installed by Zypper.
What NVIDIA sites or OpenSuse sites can I visit to determine if there are current drivers for the Quadro M4000M?
Any recommendations to get beyond a command prompt and to a working desktop?
Virtually all NVidia cards released more than several months ago are supported by FOSS drivers. However, installing proprietary video drivers disables them. Partial removal of formerly installed proprietary drivers leaves them disabled. Upgrading kernel and/or OS version commonly creates this condition. If you have upgraded OS version without first removing proprietary drivers according to the instructions provided for their installation, you can expect the condition you are in.
I can run those two commands and produce the output. However since I am in command line mode I do not have the ability to capture the output and place it in this forum. I’m open to suggestions on how to do this.
The latter will remain at the indicated URL one day, while the former will remain one week. Each will provide a pair of URLs for you to type or paste here. (Either of the two for each command should suffice.)
man susepaste
Susepaste can also upload the file generated by arvidjaar’s suggestion.
Here is the output of the two commands you requested. apologies the second file did not paste properly. I was not quite sure what your reference to wrapping the paste and # reference was for. Hopefully this is adequate.
It looks as if you had been using the 42.3 release, in which case I suspect repository #3 ( openSUSE:Factory ) has been inadvertently added ( one-click install maybe? ) and is causing you grief…
I do appreciate the assistance here. Based on the responses, it seems I have too many repositories? Do I have this correct? And they are conflicting meaning I have Tumbleweed and Leap?
My original intent was to only have Leap. This is because I am a novice user and don’t want to be fiddling with the frequency of Tumbleweed updates. I’d much rather the Leap frequency of once a year.
What are the steps to resolve this?
How do I, or do I need to get to a state before the updates? Is there a way to back out these updates?
Then would I use Zypper and remove the unwanted repositories? Before applying updates again?
If you disable the Factory/Tumbleweed, DVD & USB repos you may be able to resurrect your 42.3 via:
sudo zypper dup
Those other optional repos make the possibility iffy. You should probably disable all except OSS, non-OSS, Update, Non-OSS-Update, and opensuse-guide, do the zypper dup, then add back the others that you know are needed.
You don’t necessarily have too many just mixed version.
So to move to TW make OSS, non-OSS, Update, Non-OSS-Update disable all others at this point then point them to TW
To move back to 42.3 remove or disable the TW repo you have
Then do a zypper dup to get to the desired OS. You can add back the other repos being sure that they point to your current OS Best not to try it all in one step;)
I built this system using the Leap install. I did not want Tumbleweed because I’m not a developer or an expert with SuSE. So I wanted to keep patching and maintenance on an annual basis.
The system prompted me for applying recommended updates. I’m sorry that’s all that was in the message. Stupidly I did.
When the maintenance asked me to reboot, it booted into Tumbleweed. I’m 99.9% sure my base system is Leap. The 42.3 release you are referring to.
How do I get back to that Leap system?
It seems that you are a victim of the one-click install.
Assaid earlier, when you want a Leap 42.3 system, carefully check that you have only 42.3 repos active. When you have any repos that point to Tumbleweed then remove them.
Also as long as yopu are recovering, disable all extra repos you may have added.
I removed the Tumbleweed repo. I also disabled some of the other repo’s that I felt were not needed.
I kept the repo’s that you suggested active. The OSS, NON-OSS, UPDATE, NON-OSS-UPDATE
I ran the command Zypper dup and received the following error message.
symbol look up error: /usr/lib64/libproxy.so.1: undefined symbol: _ZN9libmodman14module_manager8load_dirENst7_cxx1112basic_stringlcst11char_traitslcESalceeeb
I’m going to search the Forum for this message and see if there are any hits. Any thoughts on this message?