From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 30490 invoked from network); 12 Feb 2022 09:57:19 -0000 Received: from 4ess.inri.net (216.126.196.42) by inbox.vuxu.org with ESMTPUTF8; 12 Feb 2022 09:57:19 -0000 Received: from mimir.eigenstate.org ([206.124.132.107]) by 4ess; Sat Feb 12 00:15:06 -0500 2022 Received: from abbatoir.myfiosgateway.com (pool-74-108-56-225.nycmny.fios.verizon.net [74.108.56.225]) by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id b29a95e7 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO) for <9front@9front.org>; Fri, 11 Feb 2022 21:14:42 -0800 (PST) Message-ID: To: 9front@9front.org Date: Sat, 12 Feb 2022 00:14:40 -0500 From: ori@eigenstate.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: rich-client polling scripting interface Subject: Re: [9front] etheriwl intel wireless 7260 fatal firmware error Reply-To: 9front@9front.org Precedence: bulk Quoth babe : > 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.