Tiny Core Extensions > TCE Q&A Forum

how do firmware extensions work without startup script?

<< < (3/10) > >>

Paul_123:
That doesn't work, udev will find the usb device and tell the kernel to load the driver.  The driver is what loads the firmware.   The firmware must be loaded before (or during boot) the kernel device driver is loaded.

GNUser:

--- Quote from: Paul_123 on August 30, 2024, 08:22:10 AM ---The driver is what loads the firmware.   The firmware must be loaded before (or during boot) the kernel device driver is loaded.

--- End quote ---
I figured it's the driver that loads the firmware. But that doesn't explain everything either, because the following doesn't work :-\

--- Code: ---$ tce-load -i firmware-atheros
firmware-atheros.tcz: OK
$ sudo modprobe -r ath9k_htc
$ sudo modprobe ath9k_htc
--- End code ---
Just to clarify that all this is just an exercise in understanding. All my gear is working fine.

GNUser:
So there's no way for a firmware extension loaded after boot to help the user short of manually disconnecting and reconnecting the relevant device?

Paul_123:
Don’t load the device drivers at boot either (in this case wireless-KERNEL.tcz).

Rich:
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 ---

Navigation

[0] Message Index

[#] Next page

[*] Previous page