When I connect my RM2 to a computer, the USB connection button shows up but can’t be toggled. I’ve already tried different computers, different cables (which work fine with my phone), and a hard reset while plugged in, but nothing helps. RM2 support hasn’t found a solution so far. Has anyone experienced this or knows what might be wrong?
#[Solved] USB Connection cannot be toggled
ripe flame
topaz atlas
Have you tried connecting to your device over SSH to investigate it at all? One thing to check would be if the root partition is full.
Step #4 of this FAQ has information on this: https://remarkable.guide/faqs.html#my-device-is-connected-to-wifi-but-can-t-sync-or-check-for-updates-how-can-i-fix-this
ripe flame
It syncs well. I cannot connect over SSH with WLAN since the update to 3.22.0.64. Therefore I tried to do it over USB to enable SSH over WLAN but with no success.
ripe flame
Customer Service couldn't find a solution and are replacing my device. Thanks for your help!
cold roost
Jdkslslss
What
But it's a 5 minute fix
I feel gutted not reading this in time.
Alas. Glad it's getting fixed!
topaz atlas
Care to share with the class?
Unless you are saying it's the lack of spae?
And 5 minutes for you or I can be an hour for others.
cold roost
Care to share with the class?
There is a bug with the ethernet gadget module
If you check dmesg on affected units, it reports a crash in the power allocation
Usually a reboot alone doesn't fix it, but kicking it into recovery and out again seems to kick it back into action in super fucked cases
topaz atlas
Could you open a PR to remarkable guide to add a FAQ for this?
cold roost
But if you have WiFi you can go in and manually re-enable the gadgget module
and sure
topaz atlas
But if you have WiFi you can go in and manually re-enable the gadgget module
In this case they don't have SSH access over wifi, so that solution doesn't work. But the recovery would.
cold roost
Yeah :D
I don't know EXACTLY what causes it
But I can reliably trigger it by stopping Xochitl, doing a hashtable calc, then leaving it for a minute or two without reloading it
It seems some kind of watchdog catches the dead/unloaded xochitl, and tries to reload it
And at that point, something goes wrong and the adapter dies
I suspect this can be triggered 'naturally' by a frozen Xochitl reloading
topaz atlas
Have you reported the issue to rM yet?
cold roost
Have you reported the issue to rM yet?
Not yet, nopers
topaz atlas
I recommend you do
cold roost
Will do c: