From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] Free Carrots #6: Tools For Fighting WiFi Inequality
Date: Sun, 23 Jul 2023 22:35:48 -0400 [thread overview]
Message-ID: <F158C3010DFAB2C1AB2D15E5C666A7E8@eigenstate.org> (raw)
In-Reply-To: <CABO6shcKGEpB3C2v-Qp7wfTv2svs5JDUgjQkj0-s+c_5aE7zHA@mail.gmail.com>
Quoth kemal <kemalinanc8@gmail.com>:
>
> my mail didn't end up in /n/lists/9front, so the mail server may have
> ate my mail. i'm going to reply to my original message and upload
> my patch to okturing instead of attaching it, hoping that it will get
> sent
> http://okturing.com/src/16441/body
this breaks wireless on my t460s (Intel Wireless 8260, 8086:24f3).
Before, it would often give me firmware crashes, but with this it
does it on every bind:
#l1: fatal firmware error
lastcmd: 108 (0x6c)
error: id 2b12, trm_hw_status 000002f0 00000000,
branchlink2 0002395c, interruptlink 0003867a 00000000,
errordata 80087cca 7acdf1f6 00000000
#l1: flushq: broken
happy to help debug, but not sure where to start.
next prev parent reply other threads:[~2023-07-24 2:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 2:51 sl
2023-06-04 13:39 ` hiro
2023-06-04 16:48 ` sl
2023-06-04 19:32 ` hiro
2023-06-05 5:04 ` Stanley Lieber
2023-06-05 7:56 ` hiro
2023-07-08 2:38 ` sl
2023-07-22 19:53 ` kemal
2023-07-22 21:30 ` kemal
2023-07-22 21:49 ` kemal
2023-07-22 22:22 ` qwx
2023-07-22 22:57 ` Stanley Lieber
2023-07-23 0:24 ` kemal
2023-07-24 2:35 ` ori [this message]
2023-07-24 9:58 ` kemal
2023-07-24 11:55 ` kemal
2023-07-24 12:08 ` Steve simon
2023-07-24 12:40 ` kemal
2023-06-10 12:21 ` mkf9
2023-06-10 23:01 ` sl
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=F158C3010DFAB2C1AB2D15E5C666A7E8@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.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).