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=1.0 required=5.0 tests=DATE_IN_PAST_12_24, DKIM_INVALID,DKIM_SIGNED,T_SCC_BODY_TEXT_LINE,UNPARSEABLE_RELAY autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 7360 invoked from network); 16 Feb 2022 10:48:46 -0000 Received: from 4ess.inri.net (216.126.196.42) by inbox.vuxu.org with ESMTPUTF8; 16 Feb 2022 10:48:46 -0000 Received: from wopr.sciops.net ([216.126.196.60]) by 4ess; Tue Feb 15 13:32:06 -0500 2022 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sciops.net; s=20210706; t=1644949907; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=t92+8hgR7dy0tKx/XZjZQcnKSX1OPtN3Ohvx9AkkLY0=; b=CMKY/UDRp55ymEaYfo9AC733jvpAZ3VeesSjKMkxe/6q6ZVyxWHVe0/cawo1rOU8HS2Oc9 V4MOtXhgmlSks4/v24roonwq4jiOXyQGiQLlRnxNGDi4l6rfHSJV1P9j33JAcdFOdst3F3 6A7cDNUAt6iYoFxg2j/jpxgg1nkZ2hk= Received: from localhost (wopr.sciops.net [local]) by wopr.sciops.net (OpenSMTPD) with ESMTPA id 9de98347 for <9front@9front.org>; Tue, 15 Feb 2022 10:31:47 -0800 (PST) Date: Tue, 15 Feb 2022 10:31:47 -0800 From: Kurt H Maier To: 9front@9front.org Message-ID: Mail-Followup-To: 9front@9front.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: mobile asynchronous persistence proxy enhancement-based scripting backend Subject: Re: [9front] etheriwl intel wireless 7260 fatal firmware error Reply-To: 9front@9front.org Precedence: bulk On Tue, Feb 15, 2022 at 09:23:52PM +0300, kemal wrote: > 2022-02-15 5:33 GMT+03:00, jpegbild@dismail.de : > >>i gave up on fixing that error, i see NO reason why it shits itself. > > kemal do you think it could be something along the lines of the > > openbsd commit ori quoted? > > > > https://github.com/openbsd/src/commit/7b7ad45c6eb1f81fda7b875a3e190e53cf2d4bd2 > > > > no, we don't do device scan, so this issue is unrelated. > problem is that fw doesn't send the calibration data properly > while we're in init firmware, which i have no idea why. have we tested this with old firmware?