Since I moved to debian13 the SAMD board s do not mount anymore properly when set into bootloader mode. It shows up as /dev/sdb, The is an entry in the file manager as being mounted, but no file access. It workd fine up to debian 12. Other similar bootloaders like the ones provided by tinyu2 register fine. Does anyone have a clue how to proceed?
This sounds like a USB handling change in Debian 13 affecting SAMD bootloaders. It’s worth checking dmesg for any errors when the board connects, and also reviewing udev rules or permissions, since older setups from Debian 12 may no longer apply. Many people find manually remounting or adjusting permissions helps in the meantime.
Hi Olicia, thank you for the swift reply, I had looked at the dmesg output, which looks clean, and tried manual mount, which failed as well. retrying the same now a few hours later, the boards mount fine without having changed any configuration. I just used the computer for other work. This sudden disappearance of the problem is as confusing as the problem itself, meaning that it can & will reappear..
As expected, the problem returned after reboot. More strange, i I repeat the mount attempt sufficiently often, mounting succeeds. It starts to work at the 19th attempt in a row, and then attempts work. If the system is the quiet for a few hours or rebooted, mounting fails again until a stat again with a series of attempt. When dump the drive content into a file, I can always mount the file w/o problems.
Does it work fine on other OS?
At the moment I can only compare with anther Linux systems, which is Mint linux (debian based) with a slightly older version and a really old rasbian. Mounting works at both, and it worked with debian 12. Tomorrow I can try windows computer and a Ubuntu system.
Windows 10 is fine. I had also a talk with ChatGPT which was very confident to know the reason and how to solve it be reconfiguration of the PC to less strict timing requirements … the solution does not help. But ChatGPT was polite and very keen all the time.