search

Eeems-Org / oxide

A desktop environment for the reMarkable tablet
https://oxide.eeems.codes
MIT License
243 stars 21 forks source link

Rm2 rebooted immediately after disabling tarnish systemd service bricking device. #343

Closed aniket-deole closed 8 months ago

aniket-deole commented 8 months ago

Describe the bug Rm2 rebooted immediately after disabling tarnish systemd service bricking device.

I had installed oxide on 3.3.2.1666. After sshing into the device to disable tarnish, the device rebooted without giving me a chance to enable xochitl. The device was able to start but it was not able to connect to the wifi anymore as xochitl was not able to start. Screen remains blank after "starting...". I can restart the device, but it is still unable to connect the wifi.

Unfortunately i do not have journalctl logs. Please close this issue if I have missed any step while installing oxide..

Thanks for the hard work! Oxide is great.

To Reproduce Steps to reproduce the behavior:

  1. SSH into device.
  2. Disable tarnish systemd service
  3. Device rebooted..

Expected behavior Device should not reboot after disabling oxide/tarnish.

Screenshots If applicable, add screenshots to help explain your problem.

Version Information:

Additional context Add any other context about the problem here.

Eeems commented 8 months ago

Disable tarnish systemd service

Could you clarify what you did to disable the service. Disabling a service doesn't actually do anything, I expect this step is actually Disable and stop the tarnish systemd service.

You can still SSH in over usb. Please do so to get the logs. Without logs, I'm not able to do much unless you had telemetry enabled and can run tarnish to get it to upload its last crash. I suspect the logs won't give me a ton of information to work with, so I do hope you have telemetry enabled. If you do, just temporarily start the tarnish service (systemctl start tarnish) so that it can connect to the internet and then upload the crash report.

aniket-deole commented 8 months ago

I disabled using systemd disable --now tarnish.

Let me check if i can get it working over usb. I did not know that.

Eeems commented 8 months ago

I disabled using systemd disable --now tarnish.

The command you ran is equivalent to running the following:

systemctl disable tarnish
systemctl stop tarnish

So it was a disable and stop as I expected. Tarnish probably crashed while stopping, which would trigger the crash handling in an unexpected way.

Let me check if i can get it working over usb. I did not know that.

:+1:

Eeems commented 8 months ago

@aniket-deole any luck?

aniket-deole commented 8 months ago

@Eeems Sorry, i think i fried my device while trying to recover it using the pogo pins. It's out of power & unable to detect/charge/poweron. (This was before i knew network works over usb)

Today, I retried these steps on an another device I have, i was not able to repro it. We can close this issue.

Eeems commented 8 months ago

@Eeems Sorry, i think i fried my device while trying to recover it using the pogo pins. It's out of power & unable to detect/charge/poweron. (This was before i knew network works over usb)

I'm sorry to hear that, does the readme for remarkable2-recovery need to be updated with a strong warning about pogo pin order?

Today, I retried these steps on an another device I have, i was not able to repro it. We can close this issue.

Alright, I'll close the issue for now.

aniket-deole commented 8 months ago

I'm sorry to hear that, does the readme for remarkable2-recovery need to be updated with a strong warning about pogo pin order?

I was aware of the order, but I messed up being hasty during my attempts. I think the readme is good enough.