From: TotallyEz <TotallyEz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Missing Mediatek WLAN drivers from the Linux-Firmware package on the latest iso
Date: Tue, 18 Apr 2023 23:36:48 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43515@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]
New issue by TotallyEz on void-packages repository
https://github.com/void-linux/void-packages/issues/43515
Description:
### Is this a new report?
Yes
### System Info
Typing from another distro
### Package(s) Affected
linux-firmware
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
The firmware package provided by the iso is expected to contain mediatek WLAN drivers in a folder titled as mediatek as shown in the package's github.
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/mediatek
This issue can be temporally solved by migrating files from the previously mentioned github to the installed system and reinstalling linux-firmware (whilst overriding the previously migrated files).Although simple this may be quite cumbersome for new users of Void.
### Actual behaviour
The firmware package provided by the iso on the following path /lib/firmware/ is missing the mediatek folder which contains the WLAN drivers for multiple mediatek wifi cards.Resulting in void being unable to detect WIFI on systems with Mediatek WLAN drivers.
### Steps to reproduce
1)Download the base/xfce iso
2)Flash it
3)Boot into iso
next reply other threads:[~2023-04-18 21:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 21:36 TotallyEz [this message]
2023-04-29 22:43 ` [ISSUE] [CLOSED] " classabbyamp
-- strict thread matches above, loose matches on Subject: below --
2023-01-25 16:07 [ISSUE] " TotallyEz
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-43515@inbox.vuxu.org \
--to=totallyez@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).