March 2019 - openSUSE Support - openSUSE Mailing Lists

[opensuse-support] package database corruption
by DennisG 20 Mar '19

20 Mar '19

After having run a routine YaST Online Update, somehow my package database appears to have gotten corrupted. Specifically, I have ~30 packages where YaST/zypper thinks that the older (replaced) version is still installed and therefore should be deleted. The new version was installed in the update, and YaST Software shows that as the installed version. However, when YaST/zypper attempts to delete that older version, it fails because that version is no longer found on the system. Yet when I run "zypper se -s", it reports that both versions are installed. If I tell zypper to rm the older version with the -f (force) option, it errors on being unable to find it. If I tell zypper to delete the entire package (so I can just reinstall the new version), it again returns an error saying that it cannot find it, displaying the old version number. Forcing a reinstall again installs the newest version, but the problem still exists. I've checked the dates on a sampling of files from these packages, and they are the newest, so the initial updates were done correctly. The old package versions and the old files indeed do not exist - except in the mind of libzypp. I assume that the package database is somehow corrupted. What can I do to correct this problem? TIA, --dg -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

5 4

[opensuse-support] Tumbleweed kernel 5.x: ima: impossible to appraise a kernel image without a file descriptor; try using kexec_file_load syscall.
by mh＠mike.franken.de 19 Mar '19

19 Mar '19

Hi *, any idea, what ima: impossible to appraise a kernel image without a file descriptor; try using kexec_file_load syscall. means? I get this message on my Tumbleweed machines since kernel 5.x. TIA. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 0

[opensuse-support] Re: [opensuse-factory] What alternative kernel can we use on Leap 15.0?
by Michal Kubecek 19 Mar '19

19 Mar '19

On Tuesday, 19 March 2019 11:37 Carlos E. R. wrote: > I have problems with hibernation crashing in my 15.0 machine, on > restore. The situation has improved, but it always crashes after 3..6 > cycles. The remaining recommendation is to use a more modern kernel. > > The > <https://download.opensuse.org/repositories/Kernel:/stable/standard/x8 > 6_64/> has version 5. This is way too advanced for Leap 15.0. In which sense? You may also want newer versions of system utilities like iproute2 or ethtool if you want access to some new features but in general, kernel is relatively independent of the rest of the system. I'm using Kernel:stable kernel on one of my 15.0 systems (and Kernel:HEAD on another, but that's mostly to test it) and there is no obvious incompatibility. > <http://download.opensuse.org/tumbleweed/repo/oss/x86_64/> has > version 5. But just yesterday I managed to download version 4.20 from > there, today they have disappeared. ... > Which is the best kernel to use for people on 15.0 that need a more > modern kernel? > > Michal Kubecek said that the TW kernel would make more sense > (<https://lists.opensuse.org/opensuse-factory/2019-01/msg00325.html>) > > Takashi Iwai said re OBS Kernel:stable "another bigger disadvantage is > the lack of KMPs" and "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." > (<https://lists.opensuse.org/opensuse-factory/2019-01/msg00232.html>) Kernel:stable OBS project builds daily snapshot of the "stable" branch in our repository. This is where kernel for Tumbleweed is submitted from so there is not much of a difference. Kernel:stable is a bit ahead, usually few days but it can be up to 2-3 weeks when switching to a new version. And with Tumbleweed, you know the kernel has passed openQA automatic tests so that the risk that it's seriously broken is lower. As for the out-of-tree (or even closed source) modules, there is no difference: neither Kernel:stable nor Tumbleweed kernels preserve kABI or (kernel) API so that you have to expect problems form time to time. > <https://download.opensuse.org/repositories/Kernel:/openSUSE-15.0/stan > dard/x86_64/> has the same version as Leap. The relationship between Kernel:openSUSE-15.0 and Leap 15.0 updates similar to Kernel:stable vs. Tumbleweed repository, i.e. the former are daily snapshots built from the git branch. Michal Kubecek -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 0

Re: [opensuse-support] problems with new kernel-default-5.0.1-1.2.x86_64
by Patrick Shanahan 17 Mar '19

17 Mar '19

cannot compile kernel module for nvidia 390.87 (last for my card) with new kernel-default-5.0.1-1.2.x86_64 sh ./NVIDIA-Linux-x86_64-390.87.run -aqs --install-libglvnd --no-drm /var/log/nvidia-installer.log is here: http://wahoo.no-ip.org/~paka/nvidia-installer.log cannot run newer version NVIDIA* as my GTS450 card is no longer supported. rebooted to kernel-default-4.20.13-1.2.x86_64 successfully rebuilt nvidia 390.87 changed to graphical.target system did not switch to vt7, and graphical interface did not display returned to multi-user.target and ran successfully startx -- :0 tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 1

[opensuse-support] [SOLVED] nvidia 390.87 build fails with kernel-default-devel-5.0.1-1.2.x86_64
by Patrick Shanahan 17 Mar '19

17 Mar '19

* Patrick Shanahan <paka(a)opensuse.org> [03-15-19 18:04]: > cannot compile kernel module for nvidia 390.87 (last for my card) with new > kernel-default-devel-5.0.1-1.2.x86_64 > > sh ./NVIDIA-Linux-x86_64-390.87.run -aqs --install-libglvnd --no-drm > > /var/log/nvidia-installer.log is here: > http://wahoo.no-ip.org/~paka/nvidia-installer.log > > cannot run newer version NVIDIA* as my GTS450 card is no longer supported. NVIDIA-Linux-x86_64-390.116.run package works with 5.0* kernel-default. tks Larry Finger -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 0

[opensuse-support] Weird kernel message during boot
by Neil Rickert 16 Mar '19

16 Mar '19

Tumbleweed (64-bit) at 20190314: The following lines are from "dmesg" output: [ 1.774479] Couldn't get size: 0x800000000000000e [ 1.774490] fbcon: Taking over console [ 1.774491] MODSIGN: Couldn't get UEFI db list [ 1.774513] Couldn't get size: 0x800000000000000e [ 1.774515] Couldn't get UEFI MokListRT [ 1.774535] Couldn't get size: 0x800000000000000e [ 1.774536] Couldn't get UEFI dbx list I am seeing 4 of those lines on the screen in early boot (before prompted for LUKS passphrase. The lines on the boot screen are the three "Couldn't get size" lines and the "MODSIGN" line. It is not causing problems, and I am ignoring for now. But I'm posting this in case they matter. I see these only with the 5.0 kernel. I did not see them with the previous 4.20 kernels. I do not see this with a legacy BIOS. I do not see this with a 64-bit UEFI BIOS. I only see it with a 32-bit UEFI BIOS ("ia32"). I should add that this is on a KVM virtual machine, with the OVMF UEFI firmware. I do not have a physical machine with ia32 firmware. My best guess is that the kernel sees that this is a UEFI system but fails to recognize that it is using 32-bit UEFI rather than 64-bit UEFI. -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 2

[opensuse-support] clamav
by mike 16 Mar '19

16 Mar '19

Hi, Still getting freshclam stopping on update with nearly 100% cpu, having to stop it with Cntrl-C. Also recommending update to clamav-0.101.1. Should I wait for opensuse-tumbleweed update or do it myself?? mike s -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 0

[opensuse-support] kernel: pstore: Unknown compression: deflate
by mh＠mike.franken.de 16 Mar '19

16 Mar '19

Hi *, I updated one of my openSUSE Leap 15.0 servers to kernel 5.0.2-2.gd1f1d19-default today. Everything seems to work ok - and it is significantly faster, especially regarding network performance. I get one error message during boot, though: kernel: zswap: loaded using pool lzo/zbud perth kernel: pstore: Unknown compression: deflate I couldn't find any information for this message. Any idea, how to solve it? TIA. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 1

[opensuse-support] LEAP 15 live image via PenDrive YUMI
by David T-G 11 Mar '19

11 Mar '19

Hi, all -- I am trying to load the LEAP 15 live image after having use PenDrive's YUMI to install it on my thumb drive. When it boots, however, it asks for the installation medium path, giving me cd:/ hd:/ Enter another URL choices. Neither preset appears to work, and I don't know what I'd put as "another". Any suggestions? TIA & HAND :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 1

[opensuse-support][TW] menus black Plasma screen
by Felix Miata 11 Mar '19

11 Mar '19

Today is not the first time getting black screens trying to use Plasma's app menu. KDM and XDM are the only installed DMs. After duping to 20190307 (32bit today, but other TW installations 64 bit), first attempt to multi-user.target startx Plasma session produced a black screen. I killed the session, deleted content of ~/.cache/, then tried again. Session opened normally, but attempting to open an app from menu turned the screen black. I had to move the mouse near upper right corner and left click to unblack the screen. Then I right clicked the starter to see what the menu style is (non-default, KDE3-style) and the screen turned black again, this time non-recoverably except to close the session via remote login. .xsession-errors was last written 2 months ago. If journal or dmesg contain clues, I'm missing them. Ctrl-Alt-BS instead of closing the session powered down the PC. On reboot IceWM from startx worked as expected. Reboot without vga=791 or video=1440x900@60 and with 5 produces working KDM and succeeds to open IceWM working as expected. Plasma from KDM is still blacking the screen in similar fashion to opening from startx. Right click on desktop also blacks, and Ctrl-Alt-BS worked as expected on last try. # inxi -G Graphics: Device-1: Advanced Micro Devices [AMD/ATI] RV370 [Radeon X600/X600 SE] driver: radeon v: kernel Display: server: X.org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa tty: 189x52 # uname -a Linux gx151 4.20.13-1-pae #1 SMP Wed Feb 27 18:03:26 UTC 2019 (fb7c4a5) i686 i686 i386 GNU/Linux -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

3 5

2023

2022

2021

2020

2019

2018

openSUSE Support March 2019