From nobody Tue Mar 22 00:01:28 2022 X-Original-To: freebsd-wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 963901A3E08E for ; Tue, 22 Mar 2022 00:02:23 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oa1-x2c.google.com (mail-oa1-x2c.google.com [IPv6:2001:4860:4864:20::2c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KMs9p5Gfbz3tns for ; Tue, 22 Mar 2022 00:02:22 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-oa1-x2c.google.com with SMTP id 586e51a60fabf-ddfa38f1c1so368348fac.11 for ; Mon, 21 Mar 2022 17:02:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jPdzfwlPadVJCVZ+B/7C8WwcitAvUwLqLQFCxJcUEyg=; b=ZIhFheyZhXrPFt0R3nomYPIijfO2M5WPorA1gf44n8ZkWHpdz9qbAWRpXiOh7vhi0j smh2bT5Ej+Re2/zxyXgp7tBvefiKUAVslLMjmuxsK4846RM3XCuwWWNh1mmH8ZdSjhEQ Uf6jhCejzBySStJSO6VnL7vTTSB4a0ccG2Vi0i5TWUpf6XhNuqF2smLwOXoKzlJO1SfI 0Of4fQiID7CQzG8vNghMdrD2WeZ9yLm3QiJSJZ1cD3e5o2uiO7qq4uUZKigrSUXy89eZ zfmWJESK/8ZfwLaW6h89IH807uF4p1NgLuZYVWPTixHmFTplL0oI8ZKCmjjB7e4JyGeI t7og== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jPdzfwlPadVJCVZ+B/7C8WwcitAvUwLqLQFCxJcUEyg=; b=ZHHJcCAw8N/AuWdhId61zrp3z8p0zCUCbDBiWZrNtvlE7sdCZvYkpPLF5cf5NVwXqG qWmgPeKBfuwl7/xy+LiwgZniEB/wE+bEGfsnA0y/Mg+rpBx+TeMOHIq3V09B1CUcjla1 j/zryCpuxgyW+L3qlLXvtV45VvCwPgyo8KvRPBP/cEykDz4LbxgJYKP+eGkEy3Il+ZWa QFIcXdavqI7aLqaORBdSumh/nz9kkaEsKMpcsAjc4t7hq1inoONTj7Yxg5zXehp55PBJ AZTEGNceGLCB20rjfg+3Eh0S9Qem67jHN8QtMRBTvOmrLTpbzrZwMMGdCPAqK7hCI7N2 WxxA== X-Gm-Message-State: AOAM530n4JJhvURpzhhlEwteXJBpSStJndnyL4j/kNDHslNpYxev//J2 /vC4j/uhYDcFS8ytprcay00bZh8me6pmOE1yVnswMfOJ X-Google-Smtp-Source: ABdhPJxJr/A8sexG+wIg1NX+BSDsxSqG4RR7hHE1BFFyeUHJ+7oiqdGhI7uJWuBymfGXlAXzPC07XnxBPckBrzTB6z4= X-Received: by 2002:a05:6871:822:b0:dd:b9a5:f5cf with SMTP id q34-20020a056871082200b000ddb9a5f5cfmr626083oap.230.1647907335380; Mon, 21 Mar 2022 17:02:15 -0700 (PDT) List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org MIME-Version: 1.0 References: <20220321141121.32088ecc@hermann> In-Reply-To: From: Kevin Oberman Date: Mon, 21 Mar 2022 17:01:28 -0700 Message-ID: Subject: Re: iwlwifi: i7260 does not load firmware properly/wifi not working To: "Bjoern A. Zeeb" Cc: Stefan Blachmann , FreeBSD User , FreeBSD Wireless Content-Type: multipart/alternative; boundary="00000000000059236505dac353cd" X-Rspamd-Queue-Id: 4KMs9p5Gfbz3tns X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=ZIhFheyZ; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of kob6558@gmail.com designates 2001:4860:4864:20::2c as permitted sender) smtp.mailfrom=kob6558@gmail.com X-Spamd-Result: default: False [-3.39 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2001:4860:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.69)[-0.690]; FORGED_SENDER(0.30)[rkoberman@gmail.com,kob6558@gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2001:4860:4864::/48, country:US]; FROM_NEQ_ENVFROM(0.00)[rkoberman@gmail.com,kob6558@gmail.com]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; URIBL_BLOCKED(0.00)[zabbadoz.net:email]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-wireless@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MLMMJ_DEST(0.00)[freebsd-wireless]; RCVD_COUNT_TWO(0.00)[2]; FREEMAIL_CC(0.00)[gmail.com,walstatt-de.de,freebsd.org]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N --00000000000059236505dac353cd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Mar 21, 2022 at 11:34 AM Bjoern A. Zeeb < bzeeb-lists@lists.zabbadoz.net> wrote: > On Mon, 21 Mar 2022, Stefan Blachmann wrote: > > > @"FreeBSDUser" maybe try with the iwm driver instead of the iwlwifi one= ? > > I understood that iwm with lagg wasn't working well either for > "FreeBSD User" or did I misread this? > > > > It works fine for me. The only thing is the firmware loading thing: > > it does not work for me when I set in /boot/loader.conf > > iwmfw_load=3D"YES" > > which for some reason causes error messages about firmware not found. > > However, explicitly specifying > > iwmXXXXfw_load=3D"YES" > > works just fine. > > > > @Bj=C3=B6rn, is this normal (mistake on my side), or could it be consid= ered a > bug? > > "iwmfw" is a catch-all to compile all iwm firmare into the kernel. > > As both man iwm and man iwmfw state (ot my memory) you have to load the > individual firmware from loader directly if they are not compiled into th= e > kernel (either indidivdually or by catch-all); there is no catch-all > module. > We could add that but that would just load a lot of blobs into memory we > don't need. > > In general I'd suggest to not load any WiFi drivers from loader > anymore these days (that's a relict of old times). At least move to > kld_list=3D".." in rc.conf if the drivers do not properly support > auto-loading yet. It's way faster to load the driver that way rather > than from loader. > > I would hope that in the longer-term we get away from loading > non-essential drivers from loader (or compiling them into GENERIC) given = we > have way better facilities these days (faster and more flexible). One of > the reasons iwlwifi cannot even be compiled into the kernel anymore; jus= t > don't want to start it at all anymore unless someone knows a good reason = it > is needed in the kernel before we go multi-user (*). > > /bz > > (*) One is securelevels but that hasn't come up yet... > > -- > Bjoern A. Zeeb r15:7 This looks like the issue I have and I boot to single-user until the fix is committed.and enter: #kldlload iwlwifi #exit So far, this works flawlessly, though it is annoying. It's a race between the driver loading and the interface starting (or, more accurately, creating the wlan interface. The scan issue remains and continues to bite me every couple of days. This gets "fixed" with "service netif restart wlan0". On occasion, the restart fails to work repeatedly and a need to reboot. I might have gotten it to work by reloading the driver, but at least most of the time the kldunload panics the system and that leaves a bit of a mess to clean up, so I am now rebooting. --=20 Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --00000000000059236505dac353cd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Mar 21, 2022 at 11:34 A= M Bjoern A. Zeeb <bzee= b-lists@lists.zabbadoz.net> wrote:
On Mon, 21 Mar 2= 022, Stefan Blachmann wrote:

> @"FreeBSDUser" maybe try with the iwm driver instead of the = iwlwifi one?

I understood that iwm with lagg wasn't working well either for
"FreeBSD User" or did I misread this?


> It works fine for me. The only thing is the firmware loading thing: > it does not work for me when I set in /boot/loader.conf
>=C2=A0 =C2=A0 iwmfw_load=3D"YES"
> which for some reason causes error messages about firmware not found.<= br> > However, explicitly specifying
>=C2=A0 =C2=A0 iwmXXXXfw_load=3D"YES"
> works just fine.
>
> @Bj=C3=B6rn, is this normal (mistake on my side), or could it be consi= dered a bug?

"iwmfw" is a catch-all to compile all iwm firmare into the kernel= .

As both man iwm and man iwmfw state (ot my memory) you have to load the
individual firmware from loader directly if they are not compiled into the<= br> kernel (either indidivdually or by catch-all);=C2=A0 there is no catch-all = module.
We could add that but that would just load a lot of blobs into memory we don't need.

In general I'd suggest to not load any WiFi drivers from loader
anymore these days (that's a relict of old times).=C2=A0 At least move = to
kld_list=3D".." in rc.conf if the drivers do not properly support=
auto-loading yet.=C2=A0 It's way faster to load the driver that way rat= her
than from loader.

I would hope that in the longer-term we get away from loading
non-essential drivers from loader (or compiling them into GENERIC) given we=
have way better facilities these days (faster and more flexible).=C2=A0 One= of
the reasons iwlwifi cannot even be compiled into the kernel anymore;=C2=A0 = just
don't want to start it at all anymore unless someone knows a good reaso= n it
is needed in the kernel before we go multi-user (*).

/bz

(*) One is securelevels but that hasn't come up yet...

--
Bjoern A. Zeeb=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0r15:7
=C2=A0
This looks like the issue I have and I boot = to single-user until the fix is committed.and enter:
#kldllo= ad iwlwifi
#exit

So far, = this works flawlessly, though it is annoying. It's a race between the d= river loading and the interface starting (or, more accurately, creating the= wlan interface.

The scan issue remains = and continues to bite me every couple of days. This gets "fixed" = with "service netif restart wlan0". On occasion, the restart fail= s to work repeatedly and a need to reboot. I might have gotten it to work b= y reloading the driver, but at least most of the time the kldunload panics = the system and that leaves a bit of a mess to clean up, so I am now rebooti= ng.

--
= Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail:= rkoberman@gmail.c= om
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055= 683
--00000000000059236505dac353cd--