From: AngryPhantom <AngryPhantom@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Some dkms modules don't get updated. A little help needed.
Date: Wed, 27 May 2020 09:47:28 +0200 [thread overview]
Message-ID: <20200527074728.CMWzAa2ybYkywzwi408DP_39kZTKkBGyGFVltGVjeDQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22307@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 696 bytes --]
New comment by AngryPhantom on void-packages repository
https://github.com/void-linux/void-packages/issues/22307#issuecomment-634489707
Comment:
@ericonr
**nvidia** is placed in /lib/modules/5.4.42_1/kernel/drivers/video and is updated upon kernel updates as well. Dunno about **zfs**, I don't use it, but I guess it is also updated without problems since it comes from Void repos and is properly packaged.
What I'm dealing with here is an issue with [D-Link DWA-131](https://github.com/Mange/rtl8192eu-linux-driver) WiFi USB driver. I just don't know how to force **dkms** make updates every time.
P.S. Yes, The sources of the driver are being added to /usr/src/. So that's a bit strange.
next prev parent reply other threads:[~2020-05-27 7:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 9:59 [ISSUE] " AngryPhantom
2020-05-27 3:26 ` ericonr
2020-05-27 3:32 ` ericonr
2020-05-27 7:46 ` AngryPhantom
2020-05-27 7:47 ` AngryPhantom [this message]
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=20200527074728.CMWzAa2ybYkywzwi408DP_39kZTKkBGyGFVltGVjeDQ@z \
--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).