Tiny Core Extensions > TCE Q&A Forum
how do firmware extensions work without startup script?
curaga:
modprobe -r sometimes fails if the driver is in use. Your chain of modprobe -r and modprobe should normally work. I suppose it could also be another driver that loads the firmware, IIRC ath9k had multiple component drivers.
GNUser:
--- Quote from: Rich on August 30, 2024, 09:38:29 AM ---Hi GNUser
Despite the firmware failure, does lsmod show that the
driver is still loaded? If it does, see if this works:
--- Code: ---sudo modprobe -r ath9k_htc
tce-load -i firmware-atheros
sudo udevadm trigger
--- End code ---
--- End quote ---
Hi Rich. Yes lsmod shows the driver still loaded. The above commands do not cause the firmware to get loaded.
Hi curaga. I tried modprobe -r followed by modprobe using all of the ath component drivers, no luck.
I'm guessing that in the particular case of usb devices it's the usb system that's requesting the driver to load the firmware?
GNUser:
cuaraga, I can confirm that modprobe -r is removing the modules as expected (according to lsmod).
GNUser:
For pci devices, the modprobe -r <driver>; modprobe <driver> strategy works just fine for firmware loaded after boot. It seems the modprobe strategy only fails in the specific case of usb devices.
In the special case of usb devices, user needs to either a) load firmware during boot (via onboot.lst) or b) disconnect+reconnect the device after loading the necessary firmware.
While it would be nice to simulate usb device disconnect+reconnect at software level, it seems non-trivial and more trouble than it's worth.
Thread is solved. Thank you all.
CentralWare:
@GNUser:
Take a peek at /usr/local/tce.installed/firmware-atheros and see if there are additional "instructions" which may not being launched when the extension is loaded (-i) manually
The firmware package is crammed with a good amount of compiler/source debris (looking at 14.x64 file listing) however, you may need to simply probe the device chipset (sudo modprobe ar9271) if it's not already showing in lsmod (just a guess with limited intel) before you launch udevadm. It's my guess that when you bring ar9271 online... it likely sees ath#k as a dependency and brings that online as well. See what happens?! Again... it's a total guess... but looks like /usr/local/lib/firmware/carl9170fw contains most everything you'd need to trace it out yourself! :D
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version