Since today, I can't connect my 84+ to my computer via USB anymore. TILP gives the standard error:
Code:
The calculator just doesn't show up at all in lsusb, and dmesg says:
Code:
However, that error doesn't show up every time. I tried it as well on a different computer (with an older version of TILP), and this one gave a few more errors:
Code:
...and of course also the -110 error from before. TILP says in the console:
Code:
Furthermore, I've tried:
It was working just fine last time I tried and I am not aware of any changes that happened. Does anyone have any clues as to what the issue could be?
Code:
Msg: failed to open the USB device.
Cause: Check that the USB cable is plugged in and that the calculator is turned ON! Also, check libusb and usbfs for valid permissions.
System: Inappropriate ioctl for device (errno = 25)
Code:
device descriptor read/64, error -110
Code:
Timeout while waiting for setup device command
device not accepting address 120, error -62
device not accepting address 121, error -62
device not accepting address 124, error -62
device not accepting address 125, error -62
unable to enumerate USB device
device not accepting address 3, error -62
device not accepting address 5, error -62
Code:
tilp-INFO: Opening cable DirectLink on port #1 to communicate with calculator TI84+ USB
ticables-INFO: Check for lib-usb support:
ticables-INFO: usb support: available.
ticables-INFO: Check for lib-usb usability:
ticables-INFO: usb filesystem (/dev/bus/usb/): mounted
(tilp:14483): ticables-WARNING **: no devices found!
- a different calculator (nspire cx) works fine
- changing batteries
- a different cable
- a different port
- running TILP as root
- cleaning the port
- rebooting, power cycling, completely unpowering etc. both the computer and the calculator.
- reinstalling TILP, newest version
- usb8x works just fine with other peripherals
- the computer works just fine with other peripherals
It was working just fine last time I tried and I am not aware of any changes that happened. Does anyone have any clues as to what the issue could be?