π
2026-10-15 01:01
in Electronics, Hiking, Linux
Making Garmin MTP units like Montana 710 not immediately shut down when plugged into a linux machine
This is a bit of a long page, so the TLDR, is:
Create /etc/udev/rules.d/99-garmin-passthrough.rules with
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="091e", ATTR{power/control}="on", ATTR{power/autosuspend}="-1"
save and run "udevadm control --reload-rules; udevadm trigger"
this ensures linux will not autosuspend the port which in turn causes the montana not to shut down, allows virtualbox to grab the port, hand it over to windows, and have basecamp work again. Yeah!
So many Crashes and Bugs with Montana 700
I have been a Garmin GPS user for over 20 years, starting with a Vista, upgraded to Oregon 700 and stayed with that for many years until they were discontinued, and my last one died. From there the Montana was the only Garmin GPS with a touchscreen and reasonable on screen keyboard to create new waypoints on the fly when I travel, so despite its size and weight (both too big compared to a more capable cell phone), I went with that. The Montana 700 worked just like the ancient Vista HCx, it emulated a usb storage drive when you plug it in USB and I could mount it on linux as a drive, move files around like gmapsupp_xxx.img files when I had too many and wanted to hide some to avoid overwhelming the GPS. Also, it was easy to just copy all the tracks to linux and store them forever (I have all my tracks from the last 20+ years, you never know, haha). This is also the time garmin introduced garmin explorer that was meant to sync all the tracks and waypoints of your GPS to the garmin cloud. It's a great idea in principle, in practise it was written poorly and never fixed in the last 2 years I've seen it, so with lots of tracks and 4000+ waypoints, I got:Stopping using 3rd party openstreetmap gmapsupp.img files and moving to Garmin Topoactive data
Unfortunately none of the coredumps gave any clue if we were hitting hardware bugs, or software bugs, and whether they were linked to the openstreetmap maps I was using when travelling in other countries. This is where I have to thank Leslie and Elizabeth from garmin support for pointing out that topoactive maps that were added in the last years are actually free repackaging of openstreetmap data in a way that has been verified not to crash the garmin software. This is not to say that the openstreetmap maps I was used to getting from the net, were crashing the montana, but it's technically possible. Big bummer that the many coredumps I gave never got anyone to say why the unit was crashing and whether it could be linked to bad map data. That said, the new topoactive data is much simpler to get than what I was doing manually and moving to the sdcard in a bunch of gmapsupp_country.img files, so I happily switched to that. Links:Upgrading from Montana 700 (usb-storage) to Montana 710 (MTP)
At the same time, Garmin kindly authorized upgrading me to a Montana 710 at their cost, which I assume they did without ever being able to figure out if the 700 hardware was it fault. At the same time, I vouched to fully switch to topoactive maps, which is actually one great thing garmin implemented and that I'm happy to switch to. However, I still need to get the data off it (tracks and waypoints) and cannot use garmin explorer as explained above due to how broken it is, so I still need to use garmin basecamp in virtualbox with my windows 7 image, the last ok-ish windows :)When switching to USB-C garmin also switched from USB-storage (drive emulation) to MTP, which is reasonable. Linux has supported MTP for over 10 years, and it also works in windows 7, so no problem in theory. In practise, everytime I plugged the GPS in and activated storage mode (when using garmin spanner mode so it asks me before doing so), the GPS said it was switching to usb-storage mode, and then would shut down.
When plugged in a real windows machine (not through virtualbox), it worked perfectly fine, and I tried with 7 other linux machines, including one 15 years old with a very old linux kernel, and each time it shut down, bummer. By then, I was pretty screwed because I did need basecamp and virtualbox to work, and eventually google gemini looked at the logs before shutdown:
kernel: [94868.932764] usb 3-5: new high-speed USB device number 34 using xhci_hcd kernel: [94869.136992] usb 3-5: New USB device found, idVendor=091e, idProduct=0003, bcdDevice= 0.01 kernel: [94869.136998] usb 3-5: New USB device strings: Mfr=0, Product=0, SerialNumber=0 kernel: [94869.740855] usb 3-5: reset high-speed USB device number 34 using xhci_hcdTurns out the problem was this, as explained by The entire crash and shutdown loop was driven by the kernel's runtime USB autosuspend dropping link power at the 2-second mark. When no host kernel driver binds to the interface, the kernel suspends the port. The Montana firmware interprets that link drop as a physical cable disconnect, terminates storage negotiation, executes an emergency waypoint flush, and turns off. Keeping the link energized via ATTR{power/autosuspend}="-1" completely resolves the failure mode, allowing any VM to claim the device without racing against link power down. The montana is wrong, but garmin support made it clear that because it works on windows, they were not super interested in diagnosing or fixing it. Maybe with this page, they'll consider a fix, but in the meantime, the workaround is this:
Create /etc/udev/rules.d/99-garmin-passthrough.rules with
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="091e", ATTR{power/control}="on", ATTR{power/autosuspend}="-1"
save and run "udevadm control --reload-rules; udevadm trigger"
this ensures linux will not autosuspend the port which in turn causes the montana not to shut down, allows virtualbox to grab the port, hand it over to windows, and have basecamp work again. Yeah!
See more images for Garmin Montana 710 MTP Shutdowns Virtualbox and Linux
