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.2 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED,
	T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4
Received: (qmail 22607 invoked from network); 15 Feb 2022 10:12:02 -0000
Received: from 4ess.inri.net (216.126.196.42)
  by inbox.vuxu.org with ESMTPUTF8; 15 Feb 2022 10:12:02 -0000
Received: from wopr.sciops.net ([216.126.196.60]) by 4ess; Mon Feb 14 18:18:01 -0500 2022
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sciops.net; s=20210706;
	t=1644880671;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:  in-reply-to:in-reply-to;
	bh=DqUVVrMCFIcbBvF+SZzcblBrojYjn/XVsc+/cNsd9kE=;
	b=hkuLJNVLQ4A46TUxyqwNtLP+jYQZgMXUTh0IVjOlBTLtvrvvjllFqG3AFDZDFXtSuDo4Ix
	emzfy3PVOiYsKz+WLi+wOv17zNsn5qJP2IUov3Sv7ln8HNbTXsP8EZ+7bGItXrdWgHb9pI
	XoLhue35NERaXAJrY6tciPLD7b6NeGo=
Received: 
	by wopr.sciops.net (OpenSMTPD) with ESMTPSA id fb7a367c (TLSv1.2:ECDHE-RSA-CHACHA20-POLY1305:256:NO)
	for <9front@9front.org>;
	Mon, 14 Feb 2022 15:17:50 -0800 (PST)
Message-ID: <797CC5DE1D46F578188C7C59EC138EBE@wopr.sciops.net>
Date: Tue, 15 Feb 2022 00:17:49 +0100
From: qwx@sciops.net
To: 9front@9front.org
In-Reply-To: <CABO6shfyHBTREXVzzgfXxMGUUwJ15_eyjzrN9keGjrFEDot8iQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: database core realtime-java component 
Subject: Re: [9front] etheriwl intel wireless 7260 fatal firmware error
Reply-To: 9front@9front.org
Precedence: bulk

On Mon Feb 14 13:40:37 +0100 2022, kemalinanc8@gmail.com wrote:

> 2022-02-13 19:56 GMT+03:00, jpegbild@dismail.de <jpegbild@dismail.de>:
> >> I'll try the patch and return
> > It worked, and as kemal had said the only problem was with the calibration,
> > but nothing other than a warning at boot happened for me. someone should
> > commit
> > the patch [attached just in case]
> >
> 
> yes, but sadly i didn't manage to fix the issue. the fw does not send the calib
> results properly. i tried to change how etheriwl sends the calibration
> request cmd
> by making it similar to what openbsd and linux does, but it spits a fw
> error instead.
> i gave up on fixing that error, i see NO reason why it shits itself.
> 
> the diff jpegbild sent can be pushed, and here is the recent patch (that doesn't
> work and shouldn't be pushed):

Alright, pushed.  I took the liberty of including the email message
that included the diff for reference, I hope that that's alright.

Please report any breakage.

Thanks again!
qwx