Closed please-enter-a-username closed 9 months ago
Hello,
It's not the Tuxedo's fault, it's dkms' fault. As you can see, the errors come from /usr/sbin/dkms.
Lines 2372-2375 in dkms 2.8.8:
2372 # Since initramfs/initrd rebuild is not requested, skip it with Redhat's weak-modules
2373 if [[ $weak_modules ]]; then
2374 weak_modules_no_initrd="--no-initramfs"
2375 fi
Fix: either modify line 2374 to:
2374 weak_modules_no_initrd=""
or install dkms 3.0.12 for Leap 15.5. / Tumbleweed.
Regards, temirg.
PS: Affected lines from dkms 3.0.12 (tumbleweed):
2542 # Since initramfs/initrd rebuild is not requested, skip it with Redhat's weak-modules
2543 if [[ $weak_modules ]]; then
2544 # Not required for SUSE/openSUSE
2545 #weak_modules_no_initrd="--no-initramfs"
2546 weak_modules_no_initrd=""
2547 fi
Thank you Temirg, I understand now. And sorry for bother you. Closing this issue.
Hi, no problem, you didn't bother me :-) Btw: I'm not employed by Tuxedo, if that's what you meant.
Regards, temirg.
I think tuxedo has wrong package requirements info in tuxedo-driver package, so I'll try to reopen this issue. I don't have a gitlab account, so I can't report this issue here.
I'm on openSUSE Leap 15.5 and have dkms 2.8.8-bp155.1.6 installed.
The tuxedo-driver 4.2.1-1 has these requirements:
dkms >= 2.1
/bin/sh
And it still fails to work when installed:
# zypper install --force tuxedo-drivers
Loading repository data...
Reading installed packages...
Forcing installation of 'tuxedo-drivers-4.2.1-1.noarch' from repository 'TUXEDO'.
Resolving package dependencies...
The following package is going to be reinstalled:
tuxedo-drivers
1 package to reinstall.
Overall download size: 0 B. Already cached: 85.7 KiB. No additional space will be used or freed after the operation.
Continue? [y/n/v/...? shows all options] (y): y
In cache tuxedo-drivers-4.2.1-1.noarch.rpm (1/1), 85.7 KiB
Checking for file conflicts: .......................................................................................................................................................................................................................................[done]
Error! DKMS tree already contains: tuxedo-drivers-4.2.1
You cannot add the same module/version combo more than once.
Building module:
cleaning build area....
make -j12 KERNELRELEASE=5.14.21-150500.55.49-default -C /lib/modules/5.14.21-150500.55.49-default/build M=/var/lib/dkms/tuxedo-drivers/4.2.1/build....(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.14.21-150500.55.49-default (x86_64)
Consult /var/lib/dkms/tuxedo-drivers/4.2.1/build/make.log for more information.
Building module:
cleaning build area....
make -j12 KERNELRELEASE=5.14.21-150500.55.49-default -C /lib/modules/5.14.21-150500.55.49-default/build M=/var/lib/dkms/tuxedo-drivers/4.2.1/build....(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.14.21-150500.55.49-default (x86_64)
Consult /var/lib/dkms/tuxedo-drivers/4.2.1/build/make.log for more information.
Check tccd running status
Stop tccd temporarily
(Re)load modules if possible
Start tccd again
(1/1) Installing: tuxedo-drivers-4.2.1-1.noarch ....................................................................................................................................................................................................................[done]
As a friendly user Temirg said, this requires dkms 3.x to work, but the package only ask for dkms >= 2.1, which isn't correct.
On TUXEDO OS we are still on dkms 2.8.7 and it builds just fine, so there is no actuall need for dkms >= 3, but it could ofc be a regression where 2.8.7 works, 2.8.8 - 3.0.11 doesn't and 3.0.12 works again.
We need to do some testing.
btw the bugtracker for tuxedo-drivers has moved to here https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers
Just did a fresh install of leap and have dkms v2.8.7 @please-enter-a-username please check if you have some 3rd party repo making something in your install weird.
Please note: the error comes from dkms itself, after trying to reinstall tuxedo-drivers:
Error! DKMS tree already contains: tuxedo-drivers-4.2.1
You cannot add the same module/version combo more than once.
dkms status
tuxedo-drivers/4.2.2, 6.7.6-1-default, x86_64: installed
tuxedo-drivers/4.2.2, 6.7.7-1-default, x86_64: installed
dkms --help
Error! Unknown option: --help
Usage: /sbin/dkms [action] [options]
[action] = { add | remove | build | install | uninstall | match | autoinstall |
mktarball | ldtarball | status }
[options] = [-m module] [-v module-version] [-k kernel-version] [-a arch]
[-c dkms.conf-location] [-q] [--force] [--force-version-override] [--all]
[--templatekernel=kernel] [--directive='cli-directive=cli-value']
[--config=kernel-.config-location] [--archive=tarball-location]
[--kernelsourcedir=source-location]
[--binaries-only] [--source-only] [--verbose]
[--no-depmod] [--modprobe-on-install] [-j number] [--version]
i.e. cleanup would be (for version 4.2.2):
dkms remove -m tuxedo-drivers/4.2.2 --all
and reinstall:
dkms install -m tuxedo-drivers/4.2.2 --all
Just did a fresh install of leap and have dkms v2.8.7 @please-enter-a-username please check if you have some 3rd party repo making something in your install weird.
Hi, thanks for reply! I have 2 thrid party repo: tuxedo and packman-essentials. And I don't use nvidia repo but ".run" file instead.
BTW I confirm that "tuxedo-driver-4.2.2" seems have fixed the "Error! Bad return status" problem and works with "dkms-2.8.8-bp155.1.6" and "kernel-5.14.21-150500.55.49-default".
The earlier working (for me) version was 4.0.2. I locked tuxedo-driver package to skip the 4.2.1 version.
Please note: the error comes from dkms itself, after trying to reinstall tuxedo-drivers:
Error! DKMS tree already contains: tuxedo-drivers-4.2.1 You cannot add the same module/version combo more than once.
dkms status tuxedo-drivers/4.2.2, 6.7.6-1-default, x86_64: installed tuxedo-drivers/4.2.2, 6.7.7-1-default, x86_64: installed dkms --help Error! Unknown option: --help Usage: /sbin/dkms [action] [options] [action] = { add | remove | build | install | uninstall | match | autoinstall | mktarball | ldtarball | status } [options] = [-m module] [-v module-version] [-k kernel-version] [-a arch] [-c dkms.conf-location] [-q] [--force] [--force-version-override] [--all] [--templatekernel=kernel] [--directive='cli-directive=cli-value'] [--config=kernel-.config-location] [--archive=tarball-location] [--kernelsourcedir=source-location] [--binaries-only] [--source-only] [--verbose] [--no-depmod] [--modprobe-on-install] [-j number] [--version]
i.e. cleanup would be (for version 4.2.2):
dkms remove -m tuxedo-drivers/4.2.2 --all
and reinstall:
dkms install -m tuxedo-drivers/4.2.2 --all
Hi Temirg, thanks a lot for your help!
I'm on "dkms-2.8.8-bp155.1.6" and "kernel-5.14.21-150500.55.49-default" now, and I can confirm tuxedo-drivers/4.2.2 works fine with them, thank you for your patience, your guide and info!
But the 4.2.1 version still not work. The problem isn't "Error! DKMS tree already contains", but "Error! Bad return status".
For further info, this is the fail log of the fresh install 4.2.1 version, although I'm not a developer nor coder, I guess something is wrong in the code of version 4.2.1, and might be already fixed in 4.2.2 version:
And this is the fresh install log of tuxedo-drivers 4.2.2. It shows the build was success, but in the end some "echo" fails with unknown reason. Anyway at least it's working now!
@please-enter-a-username Please test with the latest version of tuxedo-drivers v4.3.1 and check where your dkms version comes from. tuxedo-drivers is known to work with dkms v2.8.7 (the default for Ubuntu 22.04 and openSUSE leap 15.5) and v3.0.12 (the default for arch and other bleeding edge distros).
Just found out that "getopt: unrecognized option '--no-initramfs'" seems to be a know bug on openSUSEs side and is fixed in tumbleweed, hopefully it comes quickly to leap. However from my testing today tuxedo-drivers worked regardless after the install.
If the "Error! Bad return status" persists with the latest tuxedo-drivers package please open a new issue regarding this.
@please-enter-a-username Please test with the latest version of tuxedo-drivers v4.3.1 and check where your dkms version comes from. tuxedo-drivers is known to work with dkms v2.8.7 (the default for Ubuntu 22.04 and openSUSE leap 15.5) and v3.0.12 (the default for arch and other bleeding edge distros).
Hi, sorry for late reply. Version 4.3.1 works with leap 15.5 (dkms 2.8.7 & kernel 5.14.21-150500.55.49-default). Here's my install log about it:
Thanks for your help! I'll try to get a gitlab account and report there if new issue is found.
Oh, and I just found that... Well...
laptop:~ # dkms --version
dkms-2.8.7
laptop:~ # zypper info dkms
Loading repository data...
Reading installed packages...
Information for package dkms:
-----------------------------
Repository : mirror-main-oss
Name : dkms
Version : 2.8.8-bp155.1.6
Arch : noarch
Vendor : openSUSE
Installed Size : 134.5 KiB
Installed : Yes
Status : up-to-date
Source package : dkms-2.8.8-bp155.1.6.src
Upstream URL : https://github.com/dell/dkms
Summary : Dynamic Kernel Module Support Framework
Description :
This package contains the framework for the Dynamic
Kernel Module Support (DKMS) method for installing
module RPMS as originally developed by Dell.
laptop:~ #
Although the package version of dkms is 2.8.8, the actual real version is still 2.8.7... This is suse's duty, I guess... Sorry for providing wrong info earlier.
4.02 works fine, 4.03 hase parm errors "getopt: unrecognized option '--no-initramfs'"
detail logs: