9front - general discussion about 9front
 help / color / mirror / Atom feed
From: qwx@sciops.net
To: 9front@9front.org
Subject: Re: [9front] etheriwl intel wireless 7260 fatal firmware error
Date: Tue, 15 Feb 2022 00:17:49 +0100	[thread overview]
Message-ID: <797CC5DE1D46F578188C7C59EC138EBE@wopr.sciops.net> (raw)
In-Reply-To: <CABO6shfyHBTREXVzzgfXxMGUUwJ15_eyjzrN9keGjrFEDot8iQ@mail.gmail.com>

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

      reply	other threads:[~2022-02-15 10:12 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
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 [this message]

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=797CC5DE1D46F578188C7C59EC138EBE@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).