On Tue, 22 Mar 2022, Kevin Oberman wrote:
Sorry for the top-post, but can this make it into 13.1 at this late date?
I would hope so (along with the other changes). It's all fixes still.
--
Bjoern A. Zeeb r15:7
Sorry for the top-post, but can this make it into 13.1 at this late date?
On Tue, Mar 22, 2022 at 4:53 PM Kevin Oberman wrote:
> On Tue, Mar 22, 2022 at 6:23 AM Bjoern A. Zeeb <
> bzeeb-li...@lists.zabbadoz.net> wrote:
>
>> On Tue, 22 Mar 2022, Emmanuel Vadot wrote:
>>
>> > There is a lot of rea
On Tue, Mar 22, 2022 at 6:23 AM Bjoern A. Zeeb <
bzeeb-li...@lists.zabbadoz.net> wrote:
> On Tue, 22 Mar 2022, Emmanuel Vadot wrote:
>
> > There is a lot of reasons for having drivers compiled into the kernel
> > or loaded by loader(8), for me one is to have a small mfsroot (either
> > embedded or
On Tue, 22 Mar 2022, Emmanuel Vadot wrote:
There is a lot of reasons for having drivers compiled into the kernel
or loaded by loader(8), for me one is to have a small mfsroot (either
embedded or not) without any kernel modules.
Yeah, I have those myself plenty. Even then I can often load
driv
On Mon, 21 Mar 2022 18:33:55 + (UTC)
"Bjoern A. Zeeb" 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 thi
On Tue, 22 Mar 2022, Stefan Blachmann wrote:
On 3/22/22, Kevin Oberman wrote:
It's a race between
the driver loading and the interface starting (or, more accurately,
creating the wlan interface.
Exactly this is why I ended up loading the driver in /boot/loader.conf.
Loading it in /etc/rc.conf
On 3/22/22, Kevin Oberman wrote:
> It's a race between
> the driver loading and the interface starting (or, more accurately,
> creating the wlan interface.
Exactly this is why I ended up loading the driver in /boot/loader.conf.
Loading it in /etc/rc.conf did not lead to an enjoyable experience for
On Mon, 21 Mar 2022, Kevin Oberman wrote:
This looks like the issue I have and I boot to single-user until the fix is
committed.and enter:
#kldlload iwlwifi
#exit
Your issue was likely fixed in stable/13 on Saturday with
eeec49e0b30a3faf2985e27f163a4c2f7b511e7c by Warner.
I'd love to hear if
On Mon, Mar 21, 2022 at 11:34 AM Bjoern A. Zeeb <
bzeeb-li...@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"
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 d
@"FreeBSDUser" maybe try with the iwm driver instead of the iwlwifi one?
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="YES"
which for some reason causes error messages about firmware not found.
However, e
On Mon, 21 Mar 2022, FreeBSD User wrote:
Dear "FreeBSD User",
Subject is a notebook Lenovo E540 equipted with an Intel i7260 WiFi adaptor,
iwm0@pci0:5:0:0:class=0x028000 rev=0x73 hdr=0x00 vendor=0x8086
device=0x08b2
subvendor=0x8086 subdevice=0x4262 vendor = 'Intel Corporation'
Subject is a notebook Lenovo E540 equipted with an Intel i7260 WiFi adaptor,
iwm0@pci0:5:0:0:class=0x028000 rev=0x73 hdr=0x00 vendor=0x8086
device=0x08b2
subvendor=0x8086 subdevice=0x4262 vendor = 'Intel Corporation'
device = 'Wireless 7260'
class = network
bar
13 matches
Mail list logo
