From: qwx@sciops.net
To: 9front@9front.org
Subject: Re: [9front] etheriwl intel wireless 7260 fatal firmware error
Date: Sat, 12 Feb 2022 22:42:01 +0100 [thread overview]
Message-ID: <04B4814A9132B5C5261B748CCE982970@wopr.sciops.net> (raw)
In-Reply-To: <C42207AB25BCBE7EE65A17DD52F94AFE@eigenstate.org>
On Sat Feb 12 06:20:39 +0100 2022, ori@eigenstate.org wrote:
> Quoth babe <jpegbild@dismail.de>:
> > Hello,
> > I saw that the intel wireless 7260 AC card got added to etheriwl
> > (thanks khm!), so I tried it out. At first I got this error:
> >
> > iwl: unsupported controller type 20
> >
> > I then edited line 638 in etheriwl to change the controller type to 20,
> > from 30. It seemed to have worked, as the card was now loaded:
> >
> > #l0: iwl: 54Mbps port 0xF7700000 irq 11 ea 000000000000
> > #l0: firmware: iwm-7260-17, rev 11, build 3216344376, size [3] 14000+2c000 + [3] 14000+2c000 + 0
> >
> > But then it gave me a fatal firmware error:
> >
> > #l0: fatal firmware error
> > lastcmd: 136 (0x88)
> > error: id 65, trm_hw_status 000002f0 00000000,
> > branchlink2 0000099a, interruptlink 0000d340 0000b8ca,
> > errordata 00000000 00000200 02030000
> > #l0: cmd 136: flushq: broken
> > readnvmsect: flushq: broken
> > #l0: cmd 152: qcmd: broken
> > #l0: qcmd: broken
> >
> > Could any of you give me a heads up on how to fix this? I don't really
> > know how to program but if I could help in any way I'll be glad to :D
> >
> > --babe
> >
>
> Does this still happen if you connect quickly to a wifi network?
>
> I think this may be related to active scans, and the fix
> will likely be similar to this OpenBSD commit:
>
> https://github.com/openbsd/src/commit/7b7ad45c6eb1f81fda7b875a3e190e53cf2d4bd2
>
> But I haven't had time to tests/investigate/try to put
> a patch together.
kemal did a ton of work on the driver trying to get 7260 to work,
without success. The firmware errors made no sense and it was
impossible to understand where the issue was. I don't remember if his
latest patch was merged or not, I believe that it's floating on the ml
from around august last year, but again, no dice. If anyone wants to
stare at it some more, I suggest looking at his mails and diffs. I
remember I helped test it with a 7260 (x240) and with my t490s' i219-v
with similar results.
Cheers,
qwx
next prev parent reply other threads:[~2022-02-12 21:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 3:22 babe
2022-02-12 5:14 ` ori
2022-02-12 21:42 ` qwx [this message]
2022-02-13 15:53 ` Fwd: " jpegbild
2022-02-13 16:56 ` jpegbild
2022-02-14 11:08 ` qwx
2022-02-15 2:33 ` jpegbild
2022-02-15 18:23 ` kemal
2022-02-15 18:31 ` Kurt H Maier
2022-02-16 17:27 ` kemal
2022-02-15 9:20 ` cinap_lenrek
2022-02-14 12:26 ` kemal
2022-02-14 23:17 ` qwx
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=04B4814A9132B5C5261B748CCE982970@wopr.sciops.net \
--to=qwx@sciops.net \
--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).