From: AngryPhantom <AngryPhantom@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Some dkms modules don't get updated. A little help needed.
Date: Tue, 26 May 2020 11:59:21 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22307@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1714 bytes --]
New issue by AngryPhantom on void-packages repository
https://github.com/void-linux/void-packages/issues/22307
Description:
# System
Void Linux x86_64, updated, up and running
* xuname: Void 5.4.4**1**_1 x86_64 AuthenticAMD uptodate rrFFF
and
* xuname: Void 5.4.4**2**_1 x86_64 AuthenticAMD uptodate rrFFF
* packages: Recent kernels?
### Steps to reproduce the behavior
I've got two USB WiFi adapters (TL-WN722N and D-Link DWA-131) and I use the github drivers for them since the stock ones are unstable and sometime do not work at all almost in all distros. The [first one](https://github.com/aircrack-ng/rtl8188eus) for TL-WN722N is being compiled with a **dkms-install.sh** script and the module is placed in /lib/modules/5.4.4x_y/updates/.
While the [second one](https://github.com/Mange/rtl8192eu-linux-driver) is installed with a **dkms add .** method and the module is placed in /lib/modules/5.4.42_1/kernel/drivers/net/wireless/realtek/ (as it is defined in the dkms.conf of the driver install config).
The problem is that upon kernel update the driver for TL-WN722N (placed in /lib/modules/5.4.4x_y/updates/) **is updated** by the dkms, while the second one for D-Link DWA-131 (placed in /lib/modules/5.4.42_1/kernel/drivers/net/wireless/realtek/) **is not**.
The thing is that in Debian **both** drivers are placed in /lib/modules/4.19.0-9-amd64/updates/dkms and are updated without issues upon every kernel update.
### Expected behavior
Should be updated (?)
Please, help me figure this out. What should be done? Do I have to contact the author of the second driver to make some changes or is there some another way out since in Debian it works OK?
Thank you in advance.
next reply other threads:[~2020-05-26 9:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 9:59 AngryPhantom [this message]
2020-05-27 3:26 ` ericonr
2020-05-27 3:32 ` ericonr
2020-05-27 7:46 ` AngryPhantom
2020-05-27 7:47 ` AngryPhantom
2020-05-27 18:48 ` ericonr
2020-05-27 19:13 ` AngryPhantom
2020-05-27 21:18 ` ericonr
2020-05-29 15:01 ` [ISSUE] [CLOSED] " AngryPhantom
2020-05-29 15:01 ` AngryPhantom
2020-05-29 15:02 ` AngryPhantom
2020-05-29 15:03 ` AngryPhantom
2020-05-29 15:03 ` ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22307@inbox.vuxu.org \
--to=angryphantom@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).