Warner Losh writes:
> coretemp is a CPU device, and so I'm not sure we have the right PNP
> information for the CPU bus for it to even load.
The coretemp device is not really a device, it's just a couple of MSRs.
As such, it is not attached to an enumerable bus, or any bus at all that
devd's awar
On Wed, Nov 21, 2018, 11:43 PM Dan Partelly wireless lagg initialization is broken in this scenario, all-right. The
> init/rc system as it is now can’t cope easily with a modern asynchronous
> initialization sequence. Sure you could probably find an order which works,
> only to find yourself in tr
We're missing a fair bit of information to come to any conclusion yet.
Cy, did you used it when loading the wifi drivers automatically with
devmatcher ? Cause if you run GENERIC, chances are that you will not
see any weird behavior. Most wifi drivers are compiled in kernel in this
case.
In message <798c848d-5f32-4bf9-87e0-add4f9b74...@rdsor.ro>, Dan
Partelly writes
:
> wireless lagg initialization is broken in this scenario, all-right. The init/
> rc system as it is now canât cope easily with a modern asynchronous initial
> ization sequence. Sure you could probably find an orde
wireless lagg initialization is broken in this scenario, all-right. The init/rc
system as it is now can’t cope easily with a modern asynchronous initialization
sequence. Sure you could probably find an order which works, only to find
yourself in trouble next time you want add some modern functi
On 20 Nov 2018, at 8:17, dan_parte...@rdsor.ro wrote:
No, that's not what's happening. wlan0 isn't racing anything,
because it's no longer listed in ifconfig
But when is created lagg0 ? Acording rc output on screen , creation of
cloned interface lagg0 takes place before wlan0 is created. The
No, that's not what's happening. wlan0 isn't racing anything, because
it's no longer listed in ifconfig
But when is created lagg0 ? Acording rc output on screen , creation of
cloned interface lagg0 takes place before wlan0 is created. Then this
means SIOCLAGPORT will fail with Invalid argume
On Mon, Nov 19, 2018 at 7:48 PM Dan Partelly wrote:
> Hello,
>
> Today I tried a simple wireless failover on a machine running free-bsd.
> After reboot the system cannot complete the initialization sequence OK with
> devmatcher.
> The devd/devmatch(8) combo correctly identified the wireless card
Hello,
Today I tried a simple wireless failover on a machine running free-bsd. After
reboot the system cannot complete the initialization sequence OK with
devmatcher.
The devd/devmatch(8) combo correctly identified the wireless card and loaded
required drivers and firmware. rcorder(8) reports
