Joined
·
114 Posts
It's a long shot, but has anyone managed to get Aquaero 5 working in Linux?
My experience so far (Ubuntu 12:04):
Official software does not compile (duh ... 6 years since the last update)
Code from https://github.com/lynix/aerotools/ does not compile either (no libraries/headers)
Once I install missing packages (fortunately, libusb-1.0 is available via apt-get), it still does not compile. Did someone change the command-line syntax of gcc in the last few years so that it ignores -l options passed before the list of input files?
Hacked the makefile. Got it to compile and to link. It does not find the device. Problem solved by replacing the hardcoded device ID 0c70:f0b0 (Aquaero 4) with 0c70:f001 (Aquaero 5).
Now it finds the device, but it does not get past the call to libusb_set_configuration(). By default, it'll try again after the timeout, but the value of the timeout is set to 200 seconds. Besides, waiting does not help. dmesg displays multiple warning messages: "interface 1 claimed by usbhid while 'aerocli' sets config #1" Looks like the device is forcibly taken over by the usbhid driver. Problem solved by calling libusb_detach_kernel_driver(handle, 1); libusb_detach_kernel_driver(handle, 2);
After jumping through these hoops, one might hope that it would finally work, but no ... now I get a timeout in libusb_interrupt_transfer(). And this one feels like a change in the device protocol. But it's 5 AM and I'm too sleepy to investigate.
Google is not helpful. Am I the first person ever to get this far?
My experience so far (Ubuntu 12:04):
Official software does not compile (duh ... 6 years since the last update)
Code from https://github.com/lynix/aerotools/ does not compile either (no libraries/headers)
Once I install missing packages (fortunately, libusb-1.0 is available via apt-get), it still does not compile. Did someone change the command-line syntax of gcc in the last few years so that it ignores -l options passed before the list of input files?
Hacked the makefile. Got it to compile and to link. It does not find the device. Problem solved by replacing the hardcoded device ID 0c70:f0b0 (Aquaero 4) with 0c70:f001 (Aquaero 5).
Now it finds the device, but it does not get past the call to libusb_set_configuration(). By default, it'll try again after the timeout, but the value of the timeout is set to 200 seconds. Besides, waiting does not help. dmesg displays multiple warning messages: "interface 1 claimed by usbhid while 'aerocli' sets config #1" Looks like the device is forcibly taken over by the usbhid driver. Problem solved by calling libusb_detach_kernel_driver(handle, 1); libusb_detach_kernel_driver(handle, 2);
After jumping through these hoops, one might hope that it would finally work, but no ... now I get a timeout in libusb_interrupt_transfer(). And this one feels like a change in the device protocol. But it's 5 AM and I'm too sleepy to investigate.
Google is not helpful. Am I the first person ever to get this far?