Date: Fri, 27 Dec 2024 17:25:15 +0100 From: =?UTF-8?Q?Fernando_Apestegu=C3=ADa?= <fernando.apesteguia@gmail.com> To: Warner Losh <imp@bsdimp.com> Cc: Emmanuel Vadot <manu@bidouilliste.com>, FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: No iwm interface in current. Message-ID: <CAGwOe2YF5buDpCiXG_R0iLEgY4Rf4P4mQghtF0e_B3w2QsWikw@mail.gmail.com> In-Reply-To: <CAGwOe2aHgnpCY9nXkweGdfDxQhei9oDLi=PxtRPQ_bf-F3XPzw@mail.gmail.com> References: <CAGwOe2Y41hPU8CXag_G9o30i9VB2jP6FH-F7uKB2yoZP9%2ByGRg@mail.gmail.com> <20241227094322.64a88d47bc806904f40a51d3@bidouilliste.com> <20241227095321.a8309bd2512b9d43f944e530@bidouilliste.com> <CANCZdfruqLnJNE=f%2BOo7VoFvspVrzevZrr0VSbnguKDKt7Qz4w@mail.gmail.com> <CAGwOe2aHgnpCY9nXkweGdfDxQhei9oDLi=PxtRPQ_bf-F3XPzw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--00000000000018bdc2062a42e9ca Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Dec 27, 2024 at 5:22=E2=80=AFPM Fernando Apestegu=C3=ADa < fernando.apesteguia@gmail.com> wrote: > > > On Fri, Dec 27, 2024 at 3:00=E2=80=AFPM Warner Losh <imp@bsdimp.com> wrot= e: > >> >> >> On Fri, Dec 27, 2024, 1:53=E2=80=AFAM Emmanuel Vadot <manu@bidouilliste.= com> >> wrote: >> >>> On Fri, 27 Dec 2024 09:43:22 +0100 >>> Emmanuel Vadot <manu@bidouilliste.com> wrote: >>> >>> > >>> > 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 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. >>> >> The stack trace: https://people.freebsd.org/~fernape/iwm.jpg > > 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: <Intel(R) Dual Band Wireless AC 7265> 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: <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.361476.0, address 10:02:b5:5c:f3:d7 > > >> > >>> > Cheers, >>> > >>> > -- >>> > Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org> >>> > >>> >>> 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? > > Cheers > > >> >> Warnet >> >> -- >>> Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org> >>> >>> --00000000000018bdc2062a42e9ca Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote g= mail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Dec 27,= 2024 at 5:22=E2=80=AFPM Fernando Apestegu=C3=ADa <<a href=3D"mailto:fer= nando.apesteguia@gmail.com">fernando.apesteguia@gmail.com</a>> wrote:<br= ></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;= border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><= div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" c= lass=3D"gmail_attr">On Fri, Dec 27, 2024 at 3:00=E2=80=AFPM Warner Losh <= ;<a href=3D"mailto:imp@bsdimp.com" target=3D"_blank">imp@bsdimp.com</a>>= wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px = 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir= =3D"auto"><div><br><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D= "gmail_attr">On Fri, Dec 27, 2024, 1:53=E2=80=AFAM Emmanuel Vadot <<a hr= ef=3D"mailto:manu@bidouilliste.com" rel=3D"noreferrer" target=3D"_blank">ma= nu@bidouilliste.com</a>> wrote:<br></div><blockquote class=3D"gmail_quot= e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)= ;padding-left:1ex">On Fri, 27 Dec 2024 09:43:22 +0100<br> Emmanuel Vadot <<a href=3D"mailto:manu@bidouilliste.com" rel=3D"noreferr= er noreferrer" target=3D"_blank">manu@bidouilliste.com</a>> wrote:<br> <br> > <br> >=C2=A0 Hi,<br> > <br> > On Thu, 26 Dec 2024 23:55:24 +0100<br> > Fernando Apestegu=C3=ADa <<a href=3D"mailto:fernando.apesteguia@gma= il.com" rel=3D"noreferrer noreferrer" target=3D"_blank">fernando.apesteguia= @gmail.com</a>> wrote:<br> > <br> > > I updated to today's current from a version from Nov 18th.<br= > > > <br> > > I had these lines in loader.conf:<br> > > <br> > > iwm7265Dfw_load=3D"YES"<br> > > if_iwm_load=3D"YES"<br> > > <br> > > And with those the kernel panics. Then I saw the entry 20241216 i= n<br> > > UPDATING. Can't reproduce it here since I'm writing in my= phone, but it<br> > > says the iwm firmwares are now shipped as raw files.<br> > > So, how can I get the firmware loaded to make my nic work?<br> > > <br> > > Cheers<br> > <br> >=C2=A0 Without panic trace it's hard to really know what's goin= g on but I<br> > think that the problem is that the firmware wasn't loaded by loade= r and<br> > iwm panics since root fs isn't there yet.<br></blockquote></div></= div></div></blockquote></div></div></blockquote><div><br></div><div>The sta= ck trace:<br></div><div><a href=3D"https://people.freebsd.org/~fernape/iwm.= jpg">https://people.freebsd.org/~fernape/iwm.jpg</a></div><div>=C2=A0</div>= <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-= left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div cla= ss=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p= x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div d= ir=3D"auto"><div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quot= e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)= ;padding-left:1ex"> >=C2=A0 Just removing those lines will make iwm works again or you can u= se :<br> > iwm7265Dfw_load=3D"YES"<br> > iwm7265Dfw_name=3D"/boot/firmware/iwm7265Dfw"<br> > iwm7265Dfw_type=3D"firmware"<br></blockquote></div></div></d= iv></blockquote><div><br></div><div>I just removed the lines from /boot/loa= der.conf and the NIC is up again, thanks.</div><div>I can see these message= s in dmesg though:</div><div><br></div><div>$ dmesg | grep iwm <br></div><d= iv>iwm0: <Intel(R) Dual Band Wireless AC 7265> mem 0xdf200000-0xdf201= fff irq 16 at device 0.0 on pci2<br>iwm0: hw rev 0x210, fw ver 22.361476.0,= address 10:02:b5:5c:f3:d7<br>iwm0: <Intel(R) Dual Band Wireless AC 7265= > mem 0xdf200000-0xdf201fff irq 16 at device 0.0 on pci2<br>iwm7265Dfw: = could not load firmware image, error 2<br>iwm0: hw rev 0x210, fw ver 22.361= 476.0, address 10:02:b5:5c:f3:d7<br></div><div>=C2=A0</div><blockquote clas= s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r= gb(204,204,204);padding-left:1ex"><div dir=3D"auto"><div><div class=3D"gmai= l_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e= x;border-left:1px solid rgb(204,204,204);padding-left:1ex"> > <br> >=C2=A0 Cheers,<br> > <br> > -- <br> > Emmanuel Vadot <<a href=3D"mailto:manu@bidouilliste.com" rel=3D"nor= eferrer noreferrer" target=3D"_blank">manu@bidouilliste.com</a>> <<a = href=3D"mailto:manu@freebsd.org" rel=3D"noreferrer noreferrer" target=3D"_b= lank">manu@freebsd.org</a>><br> > <br> <br> =C2=A0<a href=3D"https://reviews.freebsd.org/D48211" rel=3D"noreferrer nore= ferrer noreferrer" target=3D"_blank">https://reviews.freebsd.org/D48211</a>= will help too.<br> <br> =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 ?<br></blockquot= e></div></div><div dir=3D"auto"><br></div><div dir=3D"auto">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.</div></div></blockquote><div><br></div><div>In my c= ase it's always been in loader.conf. I don't remember when I put it= there.</div><div><br></div><div>Would suggesting removing the load of the = modules for iwm(4) worth mentioning in UPDATING?</div><div><br></div><div>C= heers<br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"= margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef= t:1ex"><div dir=3D"auto"><div dir=3D"auto"><br></div><div dir=3D"auto">Warn= et</div><div dir=3D"auto"><br></div><div dir=3D"auto"><div class=3D"gmail_q= uote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b= order-left:1px solid rgb(204,204,204);padding-left:1ex"> -- <br> Emmanuel Vadot <<a href=3D"mailto:manu@bidouilliste.com" rel=3D"noreferr= er noreferrer" target=3D"_blank">manu@bidouilliste.com</a>> <<a href= =3D"mailto:manu@freebsd.org" rel=3D"noreferrer noreferrer" target=3D"_blank= ">manu@freebsd.org</a>><br> <br> </blockquote></div></div></div> </blockquote></div></div> </blockquote></div></div> --00000000000018bdc2062a42e9ca--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGwOe2YF5buDpCiXG_R0iLEgY4Rf4P4mQghtF0e_B3w2QsWikw>