I have a MSI GS60 Ghost that I have SuSe 13.2 installed on. I have the NVIDIA drivers and Bumble bee installed and for the most part things work well. Today when I tried to boot I got a repeating message:
“driver nvlink is already registered”
and the system failed to boot. I was unable to get the message to stop or break out of the loop with any key sequences, so i had to power off. I tried booting into recovery and ended up in a different endless boot error loop that I could not stop. I tried to snap a picture of the messages but it was too blurry to make much out, other than a message like the one above.
I have the choice of two kernels to boot in the advanced boot menu:
22.214.171.124 - Fails on desktop and recovery boot.
126.96.36.199 - Works on desktop and recovery boot.
I went to “/var/log” and grepped for “nvlink”. I did not find any entries.
Does anyone have any suggestions as to how to proceed?
I have waited nearly a week and not gotten any replies. Did I phrase my problem incorrectly? Did I not supply enough information? Please let me know what I did wrong and I will correct it. Is there anyway to see the boot log from the failed boot? I looked in /var/log after booting the kernel that I can boot but found nothing concerning “nvlink”. I have some programming languages installed, but so far as I know I don’t have “cuda” installed. Can some one please help?
On Fri 08 May 2015 12:16:01 PM CDT, kaptdeath wrote:
I have waited nearly a week and not gotten any replies. Did I phrase my
problem incorrectly? Did I not supply enough information? Please let
me know what I did wrong and I will correct it. Is there anyway to see
the boot log from the failed boot? I looked in /var/log after booting
the kernel that I can boot but found nothing concerning “nvlink”. I
have some programming languages installed, but so far as I know I don’t
have “cuda” installed. Can some one please help?
With 13.2 you need to use journalctl to see the logs (systemd), try;
journalctl --no-pager |grep nvlink
You can also look at specific boot logs as well, check the man page.
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.39-47-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
I was unfamiliar with “journalctl”. That really does supply a lot of useful information. It did not have any thing about “nvlink” in it, but I did see some other entries that might help with solving some other small issues that I am experiencing. I am familiar with “dmesg” (and now “journalctl”). Where is a good resource for describing all of the logging features and what they contain? (I find “man” a bit difficult to search for general questions.)
Sorry that we let you down for a week. I think nobody realy felt that they could say anything useful. And then there is of course the problem that people here can not point to one saying: you are going to help him.
Incorrectly phrasing or lack of information will normally of course slow down the help (because people have to ask and you have to answer and so on), but it should not result in silence.
Glad you found a solution.
BTW it is openSUSE 13.2, not SuSe or any other fancy spelling.
I have the same issue apparently. Please, could you give more details how did you refresh your working kernel? I successfully booted my Opensuse with 188.8.131.52 kernel, but the newer 184.108.40.206 is not to work ( error nvlink is already registered"). Thenks in advance.
Quoted : Oops, my bad. I got it figured out now. I just went into YAST in the kernel I could boot (220.127.116.11) and refreshed the kernel I couldn’t boot (18.104.22.168). Now it works. Thanks for your patience.
Start YAST (or YAST2). Click on “Software Management”. Search for “kernel”. Select “kernel-desktop”. If it is the graphical version of YAST (YAST2) click the icon on the left of the line until it turns into an arrow pointing up with a check mark. If it is the non-graphical interface I think you change the action with the space bar. BTW if you click on the menu item “Help | Symbols” and get a description of what all the icons mean. (I wish more programs had a feature like that!)