On Thu 27 Mar 20:19, Bjoern A. Zeeb wrote:
> On Thu, 27 Mar 2025, Baptiste Daroussin wrote:
> 
> > > > iwlwifi0: Detected Intel(R) Wi-Fi 6 AX101
> > > 
> > > That's the first time we see one of those special ones.
> > > Can you tell us what kind of Laptop this is?
> > 
> > This is a beelink mini s PC
> > (https://www.bee-link.com/products/beelink-mini-s12-pro-n100)
> > 
> > Note that a year ago creating wlan0 was working and I could even join a 
> > network,
> > but it was too slow to be usable.
> 
> I understand.  I believe we imported this functionality last year in
> September after vendor branches got sorted out.  I believe the AX101 is
> a 1T1R device, so don't expect 700Mbit/s either.
> 
> 
> > > > Anything I am missing on my side?
> > > 
> > > No, likely not.  Just the first one hitting this in all Intel internal 
> > > code.
> > > 
> > > It's trying to see if it can read 6Ghz regulatory information from UEFI
> > > (which LinuxKPI does not yet support) and so it should just fail but it
> > > walks over it due to what looks like a wrong return code and tries to
> > > program the unprovided information to firmware.
> > 
> > Note that a year ago, this was working but slow correctly but slow.
> > > 
> > > Can you bluntly give this a try and let us know if it helps?
> > > 
> > > diff --git sys/contrib/dev/iwlwifi/fw/uefi.h 
> > > sys/contrib/dev/iwlwifi/fw/uefi.h
> > > index 1f8884ca8997..0fba500b00be 100644
> > > --- sys/contrib/dev/iwlwifi/fw/uefi.h
> > > +++ sys/contrib/dev/iwlwifi/fw/uefi.h
> > > @@ -318,7 +318,7 @@ static inline
> > >  int iwl_uefi_get_uats_table(struct iwl_trans *trans,
> > >                             struct iwl_fw_runtime *fwrt)
> > >  {
> > > -       return 0;
> > > +       return -ENOENT;
> > >  }
> > >  #endif /* CONFIG_EFI */
> > >  #endif /* __iwl_fw_uefi__ */
> > > 
> > Will test ASAP
> 
> Great!  Thank you!  I'll be more than happy to have more people testing
> the current code.  Everythig we can flesh out before 14.3-R will be
> good (and I hear others waiting on other fixes).
> 
it goes a bit further wlan0 can be created but:

iwlwifi0: Failed to send LINK_CONFIG_CMD (action:2): -5
iwlwifi0: failed to update link
iwlwifi0: Failed to send MAC_CONFIG_CMD (action:2): -5  
iwlwifi0: failed to update MAC 0xfffffe010772dedeM
wlan0: link state changed to UP                                                 
                
iwlwifi0: Failed to send flush command (-5)
iwlwifi0: flush request fail                                                    
                
wlan0: link state changed to DOWN
iwlwifi0: Failed to trigger RX queues sync (-5)                                 
                
iwlwifi0: Failed to send rate scale config (-5)
iwlwifi0: Couldn't send the SESSION_PROTECTION_CMD: -5  
iwlwifi0: Failed to synchronize multicast groups update
iwlwifi0: Failed to send flush command (-5)                                     
                
iwlwifi0: Failed to send MAC_CONFIG_CMD (action:2): -5
iwlwifi0: failed to update MAC 0xfffffe010772dedeM      
iwlwifi0: Failed to send LINK_CONFIG_CMD (action:2): -5
iwlwifi0: Failed to send LINK_CONFIG_CMD (action:3): -5 
iwlwifi0: Failed to send LINK_CONFIG_CMD (action:1): -5
iwlwifi0: PHY ctxt cmd error. ret=-5                                            
                
iwlwifi0: Scan failed! ret -5
iwlwifi0: ERROR: lkpi_ic_scan_start: hw_scan returned -5
iwlwifi0: Scan failed! ret -5                                                   
                                                                                
                                
iwlwifi0: ERROR: lkpi_ic_scan_start: hw_scan returned -5
iwlwifi0: Scan failed! ret -5
iwlwifi0: ERROR: lkpi_ic_scan_start: hw_scan returned -5

And it never connexts.

Best regards,
Bapt

Reply via email to