I upgraded the kernel and had problems with my nvidia drivers. I first removed the nvidia packages(nvidia-G03*) and then I was able to login recovery mode. I tried the one click update and i get a message saying “Wrong digest” and that the checksum don’t match and I cannot install it even if i tried to ignore the security risks. installing G04 is not working for me either. Any suggestions? did I somehow corrupted the rpm package ? how can I overcome this error? Currently i can have XWindow only in recovery mode otherwise fails to terminal mode. Thank you
On 2015-08-21 02:36, dmera wrote:
> I upgraded the kernel and had problems with my nvidia drivers.
I just learnt today that reinstalling the nvidia drivers, the same rpms
as currently installed, can solve issues with kernel updates and changed
kabi.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Just go to yast and install Note that you need all packages with same GO number and only any package with the proper kernel flavour name.
Did you try download with chromium?? One click does not work with that
But first What desktop? Gnome?
is this a notebook using optimus tech??? If so you need bumblebee do not install the normal driver you need to follow instruction here
forgot to mention that i get the same from yast(in the recovery session). i tried to install it from the terminal(updated kernel which xwindow fails) and i get the same message. i used firefox and this is a custom desktop built 4-5 yrs ago. i use KDE.
thanks
Yes, it does, as the kernel module will get recompiled.
But there should be no kabi changes in a release like 13.2. This is even checked automatically.
(that check had been forgotten to be enabled when 13.2 was released, that’s why such an incompatibility was able to happen with a kernel update months ago which then was retracted the next day, that’s “fixed” meanwhile though)
There might be something wrong with the repo at the moment.
Try again later.
Or maybe try to clean your zypper cache (“zypper clean -a”) and run “zypper ref”.
Do you have an /etc/X11/xorg.conf? That would prevent nouveau from being loaded. If you remove/rename it, nouveau should at least give you a useable GUI in normal boot mode (after you uninstalled all nvidia packages).
On 2015-08-21 12:06, wolfi323 wrote:
> robin_listas;2725010 Wrote:
>> I just learnt today that reinstalling the nvidia drivers, the same rpms
>> as currently installed, can solve issues with kernel updates and changed
>> kabi.
> Yes, it does, as the kernel module will get recompiled.
> But there should be no kabi changes in a release like 13.2. This is even
> checked automatically.
They are discussing this precisely (now) at the kernel mail list 
There was the suggestion to remove the “no kabi change” rule.
> (that check had been forgotten to be enabled when 13.2 was released,
> that’s why such an incompatibility was able to happen with a kernel
> update months ago which then was retracted the next day, that’s “fixed”
> meanwhile though)
Yes, this was commented there.
And that the people that applied the first update, and had to reinstall
the nvidia rpm, when the second update came, had to reinstall the rpms a
second time.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
This indeed seems to be the case:
https://forums.opensuse.org/showthread.php/509303-Unsigned-File-repomd-xml-from-repository-nVidia-Graphics-Drivers?p=2725057#post2725057
The driver packages have been updated, it will take a while until the repo is properly signed (AFAIK this is all done manually in the case of the nvidia repo).
Bad timing, I’m afraid… :\
Hm? What I saw right now, they seem to agree to keep it:
http://lists.opensuse.org/opensuse-kernel/2015-08/msg00084.html
At least the automatic kABI check is in place at the moment, since that “problematic” kernel update, so an incompatibility should not be possible to happen in an update for 13.2.
On 2015-08-21 14:16, wolfi323 wrote:
>> They are discussing this precisely (now) at the kernel mail list
>>
>> There was the suggestion to remove the “no kabi change” rule.
> Hm? What I saw right now, they seem to agree to keep it:
Yes, but just before that they were considering removing it. Then they
thought better
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Thank you wolfi323 for the zypper parameters. Not sure if they did the trick or the repository was with the problem. Anyway everything went smooth after I cleaned up and reinstalling them(using yast). i will try to keep in mind if it happens again to remove the xorg.conf file so nouveau at least can give me an XWindow. definitely i will remember zypper clean -a and zypper ref. thanks
In hindsight, I’d say the latter… 