From: dan@djph.net   
      
   On 2025-06-04, Mike Easter wrote:   
   > Paul wrote:   
   >> There should be some way for a user to figure out the "hardware"   
   >> files that a modprobe might discover on every boot.   
   >   
   > That reminds me of the wifi problem I was having w/ a laptop; a 'bunch'   
   > of different distro/s could not properly determine the broadcom wifi on   
   > a live boot.  All of those needed ethernet access to the repo/s so the   
   > user could 'spoonfeed' the hardware recognition for the wifi.   
   >   
   > One distro, MX Linux, could manage the recognition just fine 'all by   
   > itself' on booting the live.   
   >   
   > I was puzzled by how that all worked. Clearly the module was available,   
   > at the outset, but the recognition algo /usually/ couldn't handle the   
   > problem correctly.   
      
   Most likely a case of missing the "correct" firmware (broadcom tends to   
   get a bit "special")   
      
      
      
   --   
   |_|O|_|   
   |_|_|O| Github: https://github.com/dpurgert   
   |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1  E067 6D65 70E5 4CE7 2860   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)