From nobody Fri Dec 27 16:22:16 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 4YKW4672v0z5j0Rm for ; Fri, 27 Dec 2024 16:22:30 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-il1-x129.google.com (mail-il1-x129.google.com [IPv6:2607:f8b0:4864:20::129]) (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 4YKW463D19z4nKP for ; Fri, 27 Dec 2024 16:22:30 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-il1-x129.google.com with SMTP id e9e14a558f8ab-3a8160382d4so22156805ab.0 for ; Fri, 27 Dec 2024 08:22:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1735316549; x=1735921349; 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=MrbnsorG0uODVfl5WdlkA7qFfEMRrSaMMxEOVLgVHzA=; b=NTYYa+e3ijokpDjXhhAyKVP4SPq/KDCLNpD8IEAN/8N9n0/5qMlZRDyhY/xoMrYYFI zQTAMkQETwY1GJPtndLjEZ6ouWsiM2CJul5klgIFmJXYY97mgK9dBsqjCaYVB1L5Te7E 3Y+eN6DkyvgUoh6OMw6FmOmXiNRN2aUT9t2xj6l14pkdmRXYPBN87s+FkRtewp+cKw+y YgGyrcO0PFaMUcRBshO1+f8I0lyXSZ4P4EpJVR/9+iPOnTtenmWAjhC6cWIDWsPs48DJ gjkNOfEpc6Ui97QnxIGbiM2VizQZlQJpE3Z+It/8Aq228UUTbmxKYbr+eX9f8xl0UNbS 6fXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1735316549; x=1735921349; 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=MrbnsorG0uODVfl5WdlkA7qFfEMRrSaMMxEOVLgVHzA=; b=AdiOtAEP7wGFVr24OlNdyLew0B2UywaxtOOjHKFQ5t2921L218KhTGuKYf6/jDphya vo1OVzGYfkZVGIfsHha3eGvJkWMPFZHPjafQfQ9d9ULVTrDm8eM99yqHasXxQQc2ab4K 3E77aRSCFGUwLbWnc7OsIYzBQx+HHM3uGSapXuIM3lcyUL/+ysoor5KpNSLeQDu+8f8Z npGks819BBzSbo7Wg2c7p15b962jfIT5ipKFzMO1pF+m0LwrG9VSkHbIQc2222FnrsBs hS9qzxp1+kGYZnaD0KkDfcW6IXQ4fC65Po4yI0o9X2xsO7SS2GJ8wF7xk0IDnlysQxJr RA0A== X-Forwarded-Encrypted: i=1; AJvYcCVnkbQX9Y/IYoBJL+y5j8AGaUW0okgF5KhrC1yARKqkgGQoGr+Go8jZ7HvyZjaHid1W4eQUUa2zFONz0NJ95dU=@freebsd.org X-Gm-Message-State: AOJu0Yxkmy1xHe5M+oF5cW0/+sSlH5oIW4NJNng6SGzrpSv5qkXAOn7v Cp54CjkM0vfftyXpbhhjmd+tdSBDwTyHdwR8dSyPdoS8HFtvSwofiyCl17uikNK9MUcCxowtz2l e/Qkzqpg26CWORX6h3lAN1GOTm/+exgPq X-Gm-Gg: ASbGnctUFDZ8fqnGDYBgIFycZGBUpdqbjxf3z7RpqIHwUz1ZpnPgJPMwf6J/lvY33jQ 6snvigciXbgXW7SScA7jBTxYNLQN4sb0h8fj3 X-Google-Smtp-Source: AGHT+IGLYn02m8B9rmBounMx12ybEUHJyg72/X+PuCqC7IYf2e74KKEf/nFT8tHGsKvd6L89kQz3BylIrG059+IArRU= X-Received: by 2002:a05:6e02:1c81:b0:3a7:c2ea:1095 with SMTP id e9e14a558f8ab-3c2d1b9ceaemr194444995ab.1.1735316548744; Fri, 27 Dec 2024 08:22:28 -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: =?UTF-8?Q?Fernando_Apestegu=C3=ADa?= Date: Fri, 27 Dec 2024 17:22:16 +0100 Message-ID: Subject: Re: No iwm interface in current. To: Warner Losh Cc: Emmanuel Vadot , FreeBSD Hackers Content-Type: multipart/alternative; boundary="00000000000075fee6062a42de4b" X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4YKW463D19z4nKP X-Spamd-Bar: ---- --00000000000075fee6062a42de4b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Dec 27, 2024 at 3:00=E2=80=AFPM Warner Losh wrote: > > > 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, 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 >> > >> > 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 an= d >> > 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 th= e > loader. With the firmware shift, we may need to defer drivers that need > firmware until after mountroot generally. > In my case 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? Cheers > > Warnet > > -- >> Emmanuel Vadot >> >> --00000000000075fee6062a42de4b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


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


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

>
>=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> <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?

C= heers
=C2=A0

Warn= et

--
Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>

--00000000000075fee6062a42de4b--