-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(solved) More than one arch is specified on the command line.... Kernel 6.1.0-17-amd64 #203
Comments
Alright, so I tried a possible fix dkms-make.sh:
Sadly, no change, same error message. @morrownr any help would be great. |
I'm seeing some things that are hard to explain. Let's start with: $ dkms status Post the results. Let's see what else is on your system that uses dkms. |
Thanks for the reply @morrownr. I've already run
|
I'm having the exact same issue, also on MX-23 and with the -17 kernel but with the amdgpu DKMS module. OP, I think the problem could be in this particular distro/kernel constellation. |
I've been looking this over but am not sure what would cause this. I am aware of bugs that are caused by various distros and even try to correct some in the scripts but this is not something I have seen and I've been at this for a few years. My ability to help will depend on you guys helping. |
I had the same problem with mx linux (debian derived). The second part of the build and install commands picked up 13, 16 and 17 whereas the first part picked up 17. I only needed 17 so I took the failing command, edited out the extra 2 and patched the install script. FWIW my version follows - you need to fail & correct for your version: At line 362
at what is now line 383
|
I think I may have the fix for this. I'll try to merge a large patch very soon. I will need testers. |
If you are reading this message, I have already merged a big patch that may have the fix to this problem. Please test and report. |
Tried it this morning following the instructions for using the script (starting with a new directory, putting yesterdays modified version in another directory) and the result was: Using my butchered version from the old directory worked. It replaced lines for adding, building and installing with:
|
After stepping through install-driver.sh and the dkms docs again, I have not figured this out. We are all using Debian 12 based distros and the same version of dkms. I am not seeing this problem here. So what is different in my systems from the systems you guys are running? One obvious thing is that at least 2 of you are using multiple out-of-kernel drivers being handled by dkms. I have 5 dkms drivers installed on the box I am on right now but it is 5 of the drivers I maintain here so that are all installed by basically the same script. We do see where the problem is happening: /usr/sbin/dkms.mx build -m rtl88x2bu -v 5.13.1 -k 6.1.0-17-amd64/x86_64 -c /usr/src/rtl88x2bu-5.13.1/dkms.conf --force -k 6.1.0-16-amd64 -k 6.1.0-17-amd64 -k 6.1.0-13-amd64 -a x86_64 Everything beyond Any ideas? |
FYI: $ dkms status |
In my case its the dkms provided as part of mx linux so that might be the issue.
At least that's what I assume based on that line in the code generated by the script file.
|
I appreciate the help. I just merged another patch. I have no idea if it will help with this problem as I still cannot duplicate the problem here. If you could do a
My dkms shows as version 3.0.10 also. It could be modified by the distro or it could be something else. This problem is a challenge to diagnose. |
Watching it build correctly. 16, 17, 13. Install. Reboot. And the driver is correctly installed & wifi checked and working. Perfect thanks.
|
@john9631 is reporting success after the patch I merged today. I like to have test reports for both of you as well if you have time. FYI: I have been working on the installation and removal scripts for a few years now in an effort to make installing the out-of-kernel drivers easier. I have had to work around many distros specific ways of doing things. One of the goals I have here for the out-of-kernel drivers is to support as many distros as it feasible. That can be a challenge. It would help if distros worked together on establishing standards in as many areas as is feasible because the lack of standards for many of the areas causes a lot of work by people like me. I could use that time to make more progress in other areas to help users gain more satisfaction with usb wifi. FYI: I was unable to fully understand how my latest patch appears to fix this problem but the changes I made should not cause other problems and should make for more robust scripts anyway so once you guys are able to test more over the next few days, if I don't see any problem reports, I will use the patch on all of the scripts here. Thanks for the help |
Apparently "more than one arch is specified on the command line". What!?
Description: Debian GNU/Linux 12 (bookworm)
Linux version 6.1.0-17-amd64 ([email protected]) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.69-1 (2023-12-30)
@morrownr I appreciate that the driver, but yeah, any help would be great.
The text was updated successfully, but these errors were encountered: