Irresponse
New Around Here
First post in the forum, sorry for bad or weird english.
-Router: RT-AX82U v1 (tri-core, 512mb RAM, single USB 3.0 port)
-Firmware: 388.2_2_0-gnuton1 (merlin NG)
-Storage: Kingston XS2000 4Tb SSD with original cable (male USB-C in both ends) and USB-C-to-USB-A adapter (female C and male A)
-amtm with all bells and whistles, and opkg with usbutils, pciutils, etc, everything updated and running fine
The USB drivers are built-in kernel modules, hardcoded in the firmware.
There are 2 modules built-in, the old usb-storage.ko, and the newer uas.ko.
Early in the boot process, the kernel loads the xhci_hcd module (USB 3.0 driver), which then detects the Kingston SSD and loads the UAS module by default.
But I want to use the usb-storage driver instead of the uas driver (for testing purposes, kernel of this era are know to misbehave with the UAS driver, and I want to compare the performance).
The 2 main ways to do this are adding a usb-storage.quirk as kernel boot parameter in /proc/cmdline.txt, or blacklisting the uas module early in the boot process with modprobe.
I know that these need to be done with amtm startup scripts (probably in the init-start script), but after many trials i'm unable to do so, maybe i'm too dumb to understand the scripts lingo.
Someone can help?
-Router: RT-AX82U v1 (tri-core, 512mb RAM, single USB 3.0 port)
-Firmware: 388.2_2_0-gnuton1 (merlin NG)
-Storage: Kingston XS2000 4Tb SSD with original cable (male USB-C in both ends) and USB-C-to-USB-A adapter (female C and male A)
-amtm with all bells and whistles, and opkg with usbutils, pciutils, etc, everything updated and running fine
The USB drivers are built-in kernel modules, hardcoded in the firmware.
There are 2 modules built-in, the old usb-storage.ko, and the newer uas.ko.
Early in the boot process, the kernel loads the xhci_hcd module (USB 3.0 driver), which then detects the Kingston SSD and loads the UAS module by default.
But I want to use the usb-storage driver instead of the uas driver (for testing purposes, kernel of this era are know to misbehave with the UAS driver, and I want to compare the performance).
The 2 main ways to do this are adding a usb-storage.quirk as kernel boot parameter in /proc/cmdline.txt, or blacklisting the uas module early in the boot process with modprobe.
I know that these need to be done with amtm startup scripts (probably in the init-start script), but after many trials i'm unable to do so, maybe i'm too dumb to understand the scripts lingo.
Someone can help?