Date: Wed, 2 Apr 2025 23:15:28 +0200 From: ltning-freebsd-wireless@anduin.net To: wireless@freebsd.org Subject: Re: Intel Wi-Fi: scope of iwx(4) on FreeBSD Message-ID: <d9ccbed0-d95d-46f7-a0c9-d8d2a95831b8@anduin.net> In-Reply-To: <s8310124-093s-p743-9sn6-spr86r5r5980@SerrOFQ.bet> References: <0e1690b9-1426-4ecd-a6f4-5185f00dc4ef@gmail.com> <jprUa2c3TCygs9XT5EeYkjm-ifrpI3wVe8Nbt94AuA4GzMRdfOnEkCg3ABmCyEULk3XFRS48_Jgy4Vq4SvYjvhWZSgML7rO33kW93GDoCB4=@xyinn.org> <20250401202322.433735a31ee9c9fb7adf3481@dec.sakura.ne.jp> <b17239ff-ad0d-4129-8674-a5583a9ddd7d@anduin.net> <s8310124-093s-p743-9sn6-spr86r5r5980@SerrOFQ.bet>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02.04.2025 18:11, Bjoern A. Zeeb wrote: > On Tue, 1 Apr 2025, ltning-freebsd-wireless@anduin.net wrote: > >> After a few attempts at this, I gave up and reverted to iwlwifi (which >> gave me a whole new set of headaches since I can no longer disable HT/ >> VHT, so I have to cold reboot every few hours to restore network). > > You can, see https://lists.freebsd.org/archives/freebsd-wireless/2025- > March/003091.html Yeah, but me being who I am, I keep running this new code and with a variety of devctl and kld(un)load invocations, I can usually restore network. When it works, it's fantastic for a Mbps-starved FreeBSDizen. When it doesn't, it's an opportunity. So .. I've managed to resucitate networking after several suspend/resume and firmware crash (not correlated) cycles, but each time the steps I have to take are somewhat different, so I don't have any additional useful info, sorry. /Eirik
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d9ccbed0-d95d-46f7-a0c9-d8d2a95831b8>