From nobody Fri Dec 27 16:27:11 2024 X-Original-To: freebsd-hackers@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 4YKW9m668fz5j0qM for ; Fri, 27 Dec 2024 16:27:24 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pl1-x62f.google.com (mail-pl1-x62f.google.com [IPv6:2607:f8b0:4864:20::62f]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YKW9l4HsNz4q28 for ; Fri, 27 Dec 2024 16:27:23 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20230601.gappssmtp.com header.s=20230601 header.b=pD5ZJjbT; spf=none (mx1.freebsd.org: domain of wlosh@bsdimp.com has no SPF policy when checking 2607:f8b0:4864:20::62f) smtp.mailfrom=wlosh@bsdimp.com; dmarc=none Received: by mail-pl1-x62f.google.com with SMTP id d9443c01a7336-21628b3fe7dso86455705ad.3 for ; Fri, 27 Dec 2024 08:27:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1735316842; x=1735921642; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=XNtBqBJQzkrbjSnoeTjkGBt/irPHU+LqCl1jgrHEVL0=; b=pD5ZJjbTaVF4W9pTmg3bK8IDt7bx8j9sWaw0CESjAQ71xOOoNiS3Jh+Vc+J6AtnNTW ThsJJMDe89h97sKpksGyNORu/jqr15sZGGB4RIXoQgFcRrs7+fwjciBs7y1eqFSek/As ExrnHLFioWTUYzmCWu5tH6kcJxdlN2Igtf4fGxzkwGaYYeDkF4UdSlopTs37J4v78DuG N4YlqM19MjzrSUpXzLbTdP+MekLnLGaIvDZ8iIKShdVKfIT0e5poe+jvtfaXiXuetfOw 57fZbrUnIs39UXziOscGw22sdBSFoonPSjVlfapYPw/OQe3JGNCHVI/kJihdaRNFnSL5 cXRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1735316842; x=1735921642; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=XNtBqBJQzkrbjSnoeTjkGBt/irPHU+LqCl1jgrHEVL0=; b=MkRzCgmRnKxQzAGIGWg4qQ41FQzem0s4h7UMBNG0vJNLYsObPiocQNWoXXSs0fmwoB 2x6dOnrZBLpVDc/QQofP8bcgSPoqxoPbrHu8m/ihGVQAxXHGJQkBkASwNpV7cgysY1O0 xIJT8NYvyU0vwikQm4WkYqHaICPweLUG0zYPo/lXLc0ixNXpOyBojZUYtpVEhYZi1r2I nTJwrzLjuTbVJW2bN1ut4ZLXxODEM3TTkeSJFu3lsvbjNprgYHeHbUywK0zYDTVrGdTa DqXgG1kSrMabPtznRM1wwqnHOyMFlYhfxerD3+mmRXDz9Xk/tXRI+YAt52iBxrCVH+Fe 3Tmw== X-Forwarded-Encrypted: i=1; AJvYcCUHXKhWQ7+aqcjq1HEDeK0i7RGlr5rBydPEbYvOzdJUE79CuOBuewX6VZ/PIsh0f2+p9WfzulZNgJZaGLV1Aoc=@freebsd.org X-Gm-Message-State: AOJu0YxQx2nT+t9iktj5cSmyGi00qN8Z57g6FMbUU/xllt6BYY+YgpCP f3HN8IxtqO04i9Tx9Stpi2oxZGskE6J8PRkh2byzkT2SjnOXU/z7VIiDj4f8AML3n0rJgm5USbA fw4ObAflNqDwWIxq7drMh9nugNv40rG10WgYSww== X-Gm-Gg: ASbGnct8K0+VHMDAPLxyPV0FJynNFm3Fp7expMcZpudDCbbnT6dU2RmLQnOgGw5nCNx pf086jRHZdVLxbaJst2xFPEkmY8AOmc0V7b+99Xy2hAOAzFFttFCFXDMzSXXU8cF7Hi53 X-Google-Smtp-Source: AGHT+IECDN2DNipGom4W+K0VcBiNhhmkfeLK3yDLbtynlTUIirfpMKhw2KxtRjNibrXVRY53kI2QGklzLf0aIR1X1TQ= X-Received: by 2002:a17:90b:2807:b0:2ee:599e:f411 with SMTP id 98e67ed59e1d1-2f452eeb5a3mr35880409a91.34.1735316842355; Fri, 27 Dec 2024 08:27:22 -0800 (PST) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@FreeBSD.org MIME-Version: 1.0 References: <20241227094322.64a88d47bc806904f40a51d3@bidouilliste.com> <20241227095321.a8309bd2512b9d43f944e530@bidouilliste.com> In-Reply-To: From: Warner Losh Date: Fri, 27 Dec 2024 09:27:11 -0700 Message-ID: Subject: Re: No iwm interface in current. To: =?UTF-8?Q?Fernando_Apestegu=C3=ADa?= Cc: Emmanuel Vadot , FreeBSD Hackers Content-Type: multipart/alternative; boundary="000000000000f63b6e062a42ef39" X-Spamd-Result: default: False [-3.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20230601.gappssmtp.com:s=20230601]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MISSING_XM_UA(0.00)[]; DMARC_NA(0.00)[bsdimp.com]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::62f:from]; ARC_NA(0.00)[]; TAGGED_RCPT(0.00)[]; R_SPF_NA(0.00)[no SPF record]; FREEMAIL_TO(0.00)[gmail.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; TO_DN_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[bsdimp-com.20230601.gappssmtp.com:+] X-Rspamd-Queue-Id: 4YKW9l4HsNz4q28 X-Spamd-Bar: -- --000000000000f63b6e062a42ef39 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Dec 27, 2024, 9:22=E2=80=AFAM Fernando Apestegu=C3=ADa < fernando.apesteguia@gmail.com> wrote: > > > On Fri, Dec 27, 2024 at 3:00=E2=80=AFPM Warner Losh wrot= e: > >> >> >> On Fri, Dec 27, 2024, 1:53=E2=80=AFAM Emmanuel Vadot >> wrote: >> >>> On Fri, 27 Dec 2024 09:43:22 +0100 >>> Emmanuel Vadot wrote: >>> >>> > >>> > Hi, >>> > >>> > On Thu, 26 Dec 2024 23:55:24 +0100 >>> > Fernando Apestegu=C3=ADa wrote: >>> > >>> > > I updated to today's current from a version from Nov 18th. >>> > > >>> > > I had these lines in loader.conf: >>> > > >>> > > iwm7265Dfw_load=3D"YES" >>> > > if_iwm_load=3D"YES" >>> > > >>> > > And with those the kernel panics. Then I saw the entry 20241216 in >>> > > UPDATING. Can't reproduce it here since I'm writing in my phone, bu= t >>> it >>> > > says the iwm firmwares are now shipped as raw files. >>> > > So, how can I get the firmware loaded to make my nic work? >>> > > >>> > > Cheers >>> > >>> > Without panic trace it's hard to really know what's going on but I >>> > think that the problem is that the firmware wasn't loaded by loader a= nd >>> > iwm panics since root fs isn't there yet. >>> > Just removing those lines will make iwm works again or you can use : >>> > iwm7265Dfw_load=3D"YES" >>> > iwm7265Dfw_name=3D"/boot/firmware/iwm7265Dfw" >>> > iwm7265Dfw_type=3D"firmware" >>> >> > I just removed the lines from /boot/loader.conf and the NIC is up again, > thanks. > I can see these messages in dmesg though: > > $ dmesg | grep iwm > iwm0: mem 0xdf200000-0xdf201fff irq > 16 at device 0.0 on pci2 > iwm0: hw rev 0x210, fw ver 22.361476.0, address 10:02:b5:5c:f3:d7 > iwm0: mem 0xdf200000-0xdf201fff irq > 16 at device 0.0 on pci2 > iwm7265Dfw: could not load firmware image, error 2 > iwm0: hw rev 0x210, fw ver 22.361476.0, address 10:02:b5:5c:f3:d7 > > >> > >>> > Cheers, >>> > >>> > -- >>> > Emmanuel Vadot >>> > >>> >>> https://reviews.freebsd.org/D48211 will help too. >>> >>> P.S.: Note that I don't understand why anyone wants to load wifi >>> driver in loader, was it suggested somewhere at some point ? >>> >> >> Many people want to run minimal + their drivers and load them all from >> the loader. With the firmware shift, we may need to defer drivers that n= eed >> firmware until after mountroot generally. >> > > In my case it's always been in loader.conf. I don't remember when I put i= t > there. > > Would suggesting removing the load of the modules for iwm(4) worth > mentioning in UPDATING? > Likely mention it as a workaround for this bug... loading from the loader should be supported, but our firmware interface needs to defer loadings and such until after mountroot. Sure, a lot can be done with devmatch, but that doesn't mean we have to not support from loader... Warner Cheers > > >> >> Warnet >> >> -- >>> Emmanuel Vadot >>> >>> --000000000000f63b6e062a42ef39 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Fri, Dec 27, 2024, 9:22=E2=80= =AFAM Fernando Apestegu=C3=ADa <fernando.apesteguia@gmail.com> wrote:


On Fri, Dec 27, 20= 24 at 3:00=E2=80=AFPM Warner Losh <imp@bsdimp.com> wrote:

=
On Fri= , Dec 27, 2024, 1:53=E2=80=AFAM Emmanuel Vadot <manu@bidou= illiste.com> wrote:
On Fri, 27 Dec 2024 09:43:22 +0100
Emmanuel Vadot <manu@bidouilliste.com> w= rote:

>
>=C2=A0 Hi,
>
> On Thu, 26 Dec 2024 23:55:24 +0100
> Fernando Apestegu=C3=ADa <fernando= .apesteguia@gmail.com> wrote:
>
> > I updated to today's current from a version from Nov 18th. > >
> > I had these lines in loader.conf:
> >
> > iwm7265Dfw_load=3D"YES"
> > if_iwm_load=3D"YES"
> >
> > And with those the kernel panics. Then I saw the entry 20241216 i= n
> > UPDATING. Can't reproduce it here since I'm writing in my= phone, but it
> > says the iwm firmwares are now shipped as raw files.
> > So, how can I get the firmware loaded to make my nic work?
> >
> > Cheers
>
>=C2=A0 Without panic trace it's hard to really know what's goin= g on but I
> think that the problem is that the firmware wasn't loaded by loade= r and
> iwm panics since root fs isn't there yet.
>=C2=A0 Just removing those lines will make iwm works again or you can u= se :
> iwm7265Dfw_load=3D"YES"
> iwm7265Dfw_name=3D"/boot/firmware/iwm7265Dfw"
> iwm7265Dfw_type=3D"firmware"

I just removed the lines from /boot/loa= der.conf and the NIC is up again, thanks.
I can see these message= s in dmesg though:

$ dmesg | grep iwm
iwm0: <Intel(R) Dual Band Wireless AC 7265> mem 0xdf200000-0xdf201= fff irq 16 at device 0.0 on pci2
iwm0: hw rev 0x210, fw ver 22.361476.0,= address 10:02:b5:5c:f3:d7
iwm0: <Intel(R) Dual Band Wireless AC 7265= > mem 0xdf200000-0xdf201fff irq 16 at device 0.0 on pci2
iwm7265Dfw: = could not load firmware image, error 2
iwm0: hw rev 0x210, fw ver 22.361= 476.0, address 10:02:b5:5c:f3:d7
=C2=A0
>
>=C2=A0 Cheers,
>
> --
> Emmanuel Vadot <manu@bidouilliste.com&= gt; <manu@freebsd.org>
>

=C2=A0https://reviews.freebsd.org= /D48211 will help too.

=C2=A0P.S.: Note that I don't understand why anyone wants to load wifi<= br> driver in loader, was it suggested somewhere at some point ?

Many people wan= t to run minimal + their drivers and load them all from the loader. With th= e firmware shift, we may need to defer drivers that need firmware until aft= er mountroot generally.

In my c= ase it's always been in loader.conf. I don't remember when I put it= there.

Would suggesting removing the load of the = modules for iwm(4) worth mentioning in UPDATING?

Likely mentio= n it as a workaround for this bug... loading from the loader should be supp= orted, but our firmware interface needs to defer loadings and such until af= ter mountroot. Sure, a lot can be done with devmatch, but that doesn't = mean we have to not support from loader...

Warner

Cheers
=C2=A0

Warnet

--
Emmanuel Vadot <manu@bidouilliste.com> &= lt;manu@freebsd.org>

--000000000000f63b6e062a42ef39--