From: Andrew Wong <brosasaki@gmail.com>
To: help-guix@gnu.org
Subject: Re: brcmfmac
Date: Sat, 18 May 2024 01:58:51 -0400 [thread overview]
Message-ID: <96358D2C-50AF-47BD-9401-F51FDAD7C1F9@gmail.com> (raw)
In-Reply-To: <CD269464-64DB-404A-8033-520211555809@gmail.com>
I have done some further research on this issue and have determined that
it is both an upstream and non-free issue, so it doesn’t belong here.
For posterity, however, I have found that:
- The WiFi card _is_ the “ethernet” device seen in ‘ip address’.
- The brcmfmac driver searches for the following missing files in the
firmware directory:
1. brcmfmac43602-pcie.txt
This file can be found in the attachments of this thread [1],
where others encountering this issue made it via
reverse-engineering.
2, brcmfmac43602-pcie.Apple Inc-<product name>.txt
3. brcmfmac43602-pcie.Apple Inc-<product name>.bin
Where <product name> is in my case ‘MacBookPro-12,1’.
These files are indicated to be searched for and missing by dmesg
[2], but I have no idea where these would be found. I’d guess that
some more “user-friendly” distros would ship them, so I’ll start
the search with their install images. Again, if the .txt file’s
licensing is OK, it should be in the libre kernel, I think?
I’m going to try to write a package that includes these missing files.
If anyone has any recommendations of relevant mailing lists or resources
for this problem, I would be very appreciative.
[1] https://bugzilla.kernel.org/show_bug.cgi?id=193121
[2] https://askubuntu.com/questions/1217400/how-can-i-solve-problems-\
from-dual-boot-on-macbookproubuntu-wifi
prev parent reply other threads:[~2024-05-18 6:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 8:59 brcmfmac Andrew Wong
2024-05-17 9:50 ` brcmfmac pelzflorian (Florian Pelz)
2024-05-18 0:20 ` brcmfmac Andrew Wong
2024-05-18 5:58 ` Andrew Wong [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=96358D2C-50AF-47BD-9401-F51FDAD7C1F9@gmail.com \
--to=brosasaki@gmail.com \
--cc=help-guix@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).