Replies: 2 comments
-
You probably want to run something like Have you tried the Buster image? The Bullseye image isn't very well tested or optimized. |
Beta Was this translation helpful? Give feedback.
-
One thing I noticed is that autofs depends on the networking service (presumably because autofs is often used to automount network shares), and the network service can take a while to start up. Modifying the systemd config file for autofs to no longer list that it depends on the network service shaves a few seconds off of TeslaUSB startup time, though some more investigation is needed to see if that's an OK thing to do. |
Beta Was this translation helpful? Give feedback.
-
I'm currently using a Raspberry Pi 4B with my 2018 Model 3, and it takes around 55 seconds before the car recognizes the storage device. I've done some optimization by disabling some services, and when I run
systemd-analyze
, I getStartup finished in 3.698s (kernel) + 7.417s (userspace) = 11.116s
, so something is definitely dragging. The wiki shows that it can take anywhere from seconds to a minute, but If I can even get down to 20-30 seconds, I'd be pretty happy.I'd prefer to not always power on the Pi 4 because it produces quite a bit a heat, and keeping sentry mode on 24/7 seems to be quite a waste of power and storage space. 55 seconds can cause me to miss a parking accident, so I'm wondering how long it's taking others to boot up and using what setup?
EDIT: Just adding some more details, I used the prebuilt bullseye image. Using SD as storage is slightly faster than external SSD when booting.
Beta Was this translation helpful? Give feedback.
All reactions