There are a number of driver updates in Sauerland’s repository. Myrlyn cannot update the kernel modules.
YaST Software Management offers fixes.
How to get Myrlyn to offer fixes?
Thanks,
Howard
YaST Software Management offers fixes.
How to get Myrlyn to offer fixes?
Thanks,
Howard
I update and delete with the version tab…
Also I would advise you to use my hardware Repo and not my /home Repo.
On Leap 15.6:
zypper does it the same way as myrlyn:
LANG=C zypper se -s r8168
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+-----------------------------+------------+---------------------------------------------+--------+------------------
| r8168 | srcpackage | 8.055.00-lp156.66.23 | noarch | Sauerland-OSS
| r8168 | srcpackage | 8.053.00-150600.2.pm.14 | noarch | Packman
i | r8168-blacklist-r8169 | package | 8.055.00-lp156.66.23 | x86_64 | Sauerland-OSS
v | r8168-blacklist-r8169 | package | 8.053.00-150600.2.pm.14 | x86_64 | Packman
| r8168-debugsource | package | 8.053.00-150600.2.pm.14 | x86_64 | Packman
i+ | r8168-kmp-default | package | 8.055.00_k6.4.0_150600.23.73-lp156.66.22 | x86_64 | (System Packages)
v | r8168-kmp-default | package | 8.055.00_k6.4.0_150600.21-lp156.66.23 | x86_64 | Sauerland-OSS
v | r8168-kmp-default | package | 8.053.00_k6.4.0_150600.23.78-150600.2.pm.14 | x86_64 | Packman
| r8168-kmp-default-debuginfo | package | 8.053.00_k6.4.0_150600.23.78-150600.2.pm.14 | x86_64 | Packman
i+ | r8168-ueficert | package | 8.055.00-lp156.66.23 | x86_64 | Sauerland-OSS
LANG=C zypper up
Loading repository data...
Reading installed packages...
The following 11 items are locked and will not be changed by any action:
Available:
broadcom-wl broadcom-wl-debugsource broadcom-wl-kmp-default broadcom-wl-kmp-default-debuginfo broadcom-wl-kmp-rt broadcom-wl-kmp-rt-debuginfo broadcom-wl-ueficert rtw88-blacklist-rtw88
rtw88-kmp-default rtw88-ueficert vlc-beta
The following 36 package updates will NOT be installed:
ghostscript ghostscript-x11 hwinfo libfdk-aac2 libxcb1 libxcb-composite0 libxcb-damage0 libxcb-devel libxcb-dpms0 libxcb-dri2-0 libxcb-dri3-0 libxcb-glx0 libxcb-present0 libxcb-randr0 libxcb-record0
libxcb-render0 libxcb-res0 libxcb-screensaver0 libxcb-shape0 libxcb-shm0 libxcb-sync1 libxcb-xf86dri0 libxcb-xfixes0 libxcb-xinerama0 libxcb-xinput0 libxcb-xkb1 libxcb-xtest0 libxcb-xv0 libxcb-xvmc0
libzstd1 libzstd-devel pesign-obs-integration python-rpm-generators python-rpm-macros ucode-intel zstd
The following 23 packages are going to be upgraded:
curl grub2 grub2-i386-pc grub2-i386-pc-extras grub2-snapper-plugin grub2-systemd-sleep-plugin grub2-x86_64-efi grub2-x86_64-efi-extras hdparm libarchive13 libarchive-devel libcurl4 libebml5 libGLU1
libGLU1-32bit libOpenCL1 Mesa-demo-egl Mesa-demo-x MozillaFirefox MozillaFirefox-translations-common mozilla-nspr rsync strawberry
The following 2 NEW packages are going to be installed:
libdecor libdecor-0-0
23 packages to upgrade, 2 new.
Package download size: 96,9 MiB
Package install size change:
| 335,4 MiB required by packages that will be installed
201,4 KiB | - 335,2 MiB released by packages that will be removed
Backend: classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y):
As you can see, no r8168-kmp-default will be updated.
Only a zypper dup will help.
What happens when you run
zypper up
?
This is a bug in KMP packages similar to the bug fixed for the kernel itself: 867595 – Kernel update in stock factory report colision with older version of itself
KMP are subject to multiversion handling, but packages that differ only in rebuild counter contain the same files, they cannot be installed side by side. It has nothing to do with Myrlyn vs. YaST.
zypper dup is not a solution, just a workaround.
This is apparently the generic problem, someone needs to open bug report.
OK, I switched.
Thanks
@System means: The Package is installed and does not belong to any active Repo.
You are on Leap 16.0 and have kmps installed for Leap 15.6, so is the Kernel 6.4 also installed:
zypper se -si kernel-default
Yes, kernel 6.4 is still hanging around:
howard@HP-oS160:~> sudo zypper se -si kernel-default
[sudo] password for root:
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+-------------------------+---------+----------------------+--------+------------------
i+ | kernel-default | package | 6.4.0-150600.23.70.1 | x86_64 | (System Packages)
i+ | kernel-default | package | 6.12.0-160000.6.1 | x86_64 | repo-oss (16.0)
i+ | kernel-default | package | 6.12.0-160000.5.1 | x86_64 | repo-oss (16.0)
i+ | kernel-default-devel | package | 6.4.0-150600.21.3 | x86_64 | (System Packages)
i+ | kernel-default-devel | package | 6.12.0-160000.6.1 | x86_64 | repo-oss (16.0)
i+ | kernel-default-devel | package | 6.12.0-160000.5.1 | x86_64 | repo-oss (16.0)
i+ | kernel-default-extra | package | 6.4.0-150600.23.70.1 | x86_64 | (System Packages)
i+ | kernel-default-extra | package | 6.12.0-160000.6.1 | x86_64 | repo-oss (16.0)
i+ | kernel-default-extra | package | 6.12.0-160000.5.1 | x86_64 | repo-oss (16.0)
i+ | kernel-default-optional | package | 6.4.0-150600.23.70.1 | x86_64 | (System Packages)
i+ | kernel-default-optional | package | 6.12.0-160000.6.1 | x86_64 | repo-oss (16.0)
i+ | kernel-default-optional | package | 6.12.0-160000.5.1 | x86_64 | repo-oss (16.0)
Note: For an extended search including not yet activated remote resources please use 'zypper
search-packages'.
howard@HP-oS160:~>
Have you problems with your kernel 6.12?
If no, I would delete all kernel 6.4
And also all matching kmps.
No problems with kernel 6.12. I’ll clean as you suggest.
Thanks,
Howard
I switched from your /home to hardware (https://download.opensuse.org/repositories/home:/Sauerland:/hardware/openSUSE_Leap_16.0/), but trying updates I get errors:
Subprocess failed. Error: RPM failed: Command exited with status 1.
History:
- error: File not found: /var/cache/zypp/packages/sauerland's-home-project-(16.0)/x86_64/r8168-ueficert-8.055.00-lp160.67.23.x86_64.rpm
Subprocess failed. Error: RPM failed: Command exited with status 1.
History:
- error: File not found: /var/cache/zypp/packages/sauerland's-home-project-(16.0)/x86_64/rtl8821au-ueficert-20251003-lp160.3.3.x86_64.rpm
Subprocess failed. Error: RPM failed: Command exited with status 1.
History:
- error: File not found: /var/cache/zypp/packages/sauerland's-home-project-(16.0)/x86_64/rtw88-ueficert-5.16~114.g9bc8fec-lp160.2.3.x86_64.rpm
Something still points to your home-project repository.
Post:
zypper lr -d
Maybe clean all:
zypper clean -a && zypper ref && zypper up
Just as a general remark: Myrlyn, YaST software and zypper all use the same libzypp with the same dependency resolver. If one of them reports a dependency problem, you will find that the other ones report the exact same problem; with the exact same proposed solutions.
When you try a dist upgrade or package update in Myrlyn, and there are sad faces left over, that means that there are packages where a newer version is available, but the dup / up couldn’t update them because there were dependency problems with them. You can easily find out when you click on the status icon at the left; it will try to update that package manually. If there is a sad face in that line, that will fail with a dependency conflict.
What the solver does when you click on the dist upgrade or package update button on the left side panel is that it goes through all update candidates (the packages where a newer version is available) and tries the update; if it works, it marks that package for update, if not, it leaves it alone. Those packages will be left over, and Myrlyn adds the sad face to show you that those couldn’t be updated.
HTH
howard@HP-oS160:~> zypper lr -d
# | Alias | Name | Enabled | GPG Check | Refresh | Keep | Priority | Type | URI | Service
---+---------------------------------------+-------------------------------+---------+-----------+---------+------+----------+--------+------------------------------------------------------------------------------------------+---------
1 | Multimedia | Multimedia | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://download.opensuse.org/repositories/multimedia:/apps/16.0/ |
2 | NVIDIA:repo-non-free | repo-non-free (16.0) | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://download.nvidia.com/opensuse/leap/16.0 | NVIDIA
3 | VLC | VLC | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://download.videolan.org/SuSE/16.0/ |
4 | ftp.gwdg.de-openSUSE_Leap_$releasever | Packman Repository | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_16.0/ |
5 | mozilla | Mozilla based projects (16.0) | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://download.opensuse.org/repositories/mozilla/16.0/ |
6 | openSUSE:repo-non-oss | repo-non-oss (16.0) | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://cdn.opensuse.org/distribution/leap/16.0/repo/non-oss/x86_64 | openSUSE
7 | openSUSE:repo-non-oss-debug | repo-non-oss-debug (16.0) | No | ---- | ---- | - | 99 | N/A | http://cdn.opensuse.org/debug/distribution/leap/16.0/repo/non-oss/x86_64 | openSUSE
8 | openSUSE:repo-openh264 | repo-openh264 (16.0) | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://codecs.opensuse.org/openh264/openSUSE_Leap_16 | openSUSE
9 | openSUSE:repo-oss | repo-oss (16.0) | Yes | (r ) Yes | Yes | - | 99 | rpm-md | http://cdn.opensuse.org/distribution/leap/16.0/repo/oss/x86_64 | openSUSE
10 | openSUSE:repo-oss-debug | repo-oss-debug (16.0) | No | ---- | ---- | - | 99 | N/A | http://cdn.opensuse.org/debug/distribution/leap/16.0/repo/oss/x86_64 | openSUSE
11 | openSUSE:repo-oss-source | repo-oss-source (16.0) | No | ---- | ---- | - | 99 | N/A | http://cdn.opensuse.org/source/distribution/leap/16.0/repo/oss | openSUSE
12 | sauerland's-home-project-(16.0) | Sauerland Hardware (16.0) | Yes | (r ) Yes | Yes | - | 99 | rpm-md | https://download.opensuse.org/repositories/home:/Sauerland:/hardware/openSUSE_Leap_16.0/ |
howard@HP-oS160:~>
What’s with the sauerland’s-home-project-(16.0) Alias?
What do you mean?
Repo #12 which I named Sauerland Hardware (16.0) has URI
https://download.opensuse.org/repositories/home:/Sauerland:/hardware/openSUSE_Leap_16.0/
has an Alias sauerland’s-home-project-(16.0).
Did I get the wrong repo address?
The name or alias is unimportant, important is only the URL.
But I would not use special charakters, only - and _ in Names.
So when do you get the error, on which command?
Have you cleaned tha cahe as described?
1 Like
The URL is working, mark it and open it in a new window.