On 1/2/19 10:11 pm, Carlos E. R. wrote:
On 01/02/2019 08.58, Basil Chupin wrote:
On 31/1/19 9:04 pm, Carlos E. R. wrote:
On 01/30/2019 11:15 PM, Basil Chupin wrote:
I am trying to update my wife's Leap 15.0 system and get this error when using either zypper or Yast2.
I am using the kernel from the ../Kernel:/stable/standard/ repository on my Leap 15.0 as well as hers but I am not having this hassle.
When using zypper to update I get this error msg (pls see attached zypper_error-31.png) and when using Yast I get the error msg in the attached Yast_error-31.png.
Yesterday when I tried to do same, the 'zypper up' got a lot further in the installation - pls see attached zypper_error.png. Do "dmesg" just after the error. There should be an entry in the last
On 31/01/2019 06.30, David C. Rankin wrote: line about the segmentation fault.
Or just peruse the log now and search back for it (word "segmentation" or perhaps "coredump").
I have run 'zypper clean -a' and 'zypper refresh -fdb' but this hasn't helped.
Anyone please suggest what is causing this problem and how to how to get rid of the cause of this problem? I would try "rpmdb --rebuilddb".
This is more a calculated guess than a silver bullet, but it looks like the 4.20.5 kernel (brand new) is not playing well with the 20181218 kernel-firmware patch. I do know I got new firmware with 4.20.5 on Arch, so I suspect the same would be needed with openSuSE. From a recent thread in factory mail list, I understand it is better to try the tumbleweed kernel. I can search the explanation if you want.
(Just had a break for dinner...)
Thanks, Carlos, I'll do what you suggest above tomorrow and see what the log states re the seg. fault. I'm interested if you can find out if the command "rpmdb --rebuilddb" works. I think it doesn't, but now I have my doubts. So please try that one first, and if it says "unknown option" try "rpmdb --rebuilddb" instead ;-)
See my response to Felix -- the problem has been solved and I used 'rpm --rebuild'.
Re the TW kernel, I would be grateful if you could find that post in
factory. +++................. Date: Thu, 17 Jan 2019 10:10:17 +0100 From: Takashi Iwai <...@suse.de> To: opensuse-factory@opensuse.org Subject: Re: TW kernel and Leap image (Re: [opensuse-factory] Leap 15.0 - Lots of troubles with old kernel in DVD image)
On Wed, 16 Jan 2019 21:00:15 +0100,
Takashi Iwai wrote:
On Wed, 16 Jan 2019 19:58:42 +0100, Takashi Iwai wrote:
2. Extend the current DVD ISO to allow to choose between current official kernel and this new 4.20 kernel. (I am no developer, I don't know how to do that). This should be rather easy, and even doable with the current installer. In the online repo setup, you can add your own repo, and just put OBS Kernel:stable repo there. That's all. BTW, the kernel in OBS Kernel:stable repo has one big disadvantage. It's not signed with the official openSUSE key, thus it won't boot with secure boot. OTOH, if we take the real TW kernel package, it should work with secure boot, too. ... and last but not least, another bigger disadvantage is the lack of KMPs. The extra kernel module packages provided for Leap 15.0 kernel won't be available for this one. If there are alternative ones for TW, we can take them, though.
Also, the Nvidia KMP build is often broken with each kernel version update. It'd be another reason to stick with TW kernel, not the bleeding edge one in OBS Kernel:stable.
Takashi .................++-
There you have.
I pasted it because it is in my archive of important messages re kernel. To post a link I would have to find it first ;-)
Thanks for finding the thread. Fortunately I do not use UEFI (why is MS such a PITA? :-) ) but I am now prepared when I do have to <shudder> use UEFI which I fear I will be forced to do very shortly :-(. BC -- 'When I use a word', Humpty Dumpty said, in a rather scornful tone, 'it means just what I choose it to mean.' Lewis Carroll, Through the Looking-Glass -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org