That worked!!
Thank you
1 Like
Your last command solve my problem. But why this method is not the one that described in FAQ?
I was going to suggest it was because we are looking at the latest version of the documentation (meaning the develop branch), rather than the stable (i.e. master branch) version… but that’s not the case…
It may be an oversight… I’ll open an issue against https://github.com/platformio/platformio-docs/blob/master/faq.rst#platformio-udev-rules and see what Ivan thinks…
Edit: Ivan can’t remember why it was the path it was, and it’s been updated to point to the master branch, so following the docs should be ‘safe’ now 
1 Like
Thanks pfeerick! That did the trick for me, no more error when running. 
1 Like
Debian Stable. All new install of platformio. Same issue. I’m using Emacs but that’s immaterial. And that includes the fix here: Warning! Please install `99-platformio-udev.rules` keeps showing up - #22 by pfeerick
I have also got the prompt, but it seemed that it could also work without install it, so my question is, what is that file for, and which users should install it?
The udev rules file (install of which is documented here - Redirecting...) tells udev (the device events manager on linux) how to configure your device, what permissions should be applied to it, what ModemManager configuration values to set, etc.
If your system is working, then you can safely ignore it. Or you can apply it, so the warning goes away But generally, it should be applied, as it will prevent problems in the future when you use a board that needs to be configured properly before PlatformIO can program / access it.
One other thing about the rules file.
If you edit it, you get told that it is out of date and needs updating. This on every compile. I believe it’s checking with a standard version and reporting back if they differ.
Not a lot that can done to alleviate the message, I suspect, I’ll just have to continue to live with it.
Cheers,
Norm.
1 Like
Yup, it’s compared with the version you’re told to download. Unless there is a need to change one of the rules, it’s best to do it in in a separate file. And depending on the change, that could probably be done in a separate rules files that runs AFTER the PlatformIO one - i.e. just add another rule file with a later number so it runs after the PlatformIO one. 
It’s not a huge problem. I think I added a different group (as well as dialout) to the file. I can live with it, until I fix it properly.
Mint 20.x upgrade in the near future.
Cheers,
Norm.
1 Like
Upgrade? Why would you want to do a silly thing like that? 
My desktop runs Manjaro (an Arch derivative, so it’s a rolling update distro), but my laptop (as my backup development machine) runs Ubuntu LTS, so it’s still on 18.04 IIRC (since 20.04 isn’t available for the LTS users yet).
What was the problem? Were devices not been assigned to the dialout group (which I presume you’ve added to your account)? On Manjaro/Arch it’s the uucp group, so that doesn’t add the confusion whatsoevert! 
To be honest, I can’t remember. I think it was my usbTiny comes up in a different group to dialout so I amended the file to add that group. I’ll get around to checking it sometime!
I tried Manjaro for a while but I didn’t get on with it. No particular reason – it just didn’t feel right somehow. I’ve used Arch in the past, and Suse, Open Suse, Red Hat (before they went paid for), Oracle Linux. Fedora. Settled on Mint as I really do not like Gnome 3’s destop.
Upgrading isn’t rolling, like Arch etc, but it doesn’t take long. Even on my Dell Vostro 17" laptop from 15 plus years ago!
Cheers,
Norm.
1 Like
Me neither… I came into Linux during the early Ubuntu days and still love the GNOME2 interface style, so prefer Ubuntu Mate to ‘regular’ Ubuntu. Nowadays I use KDE since it is no longer the slower more resource-hungry DE, and has all the bells and whistles. I went with Manjaro as I have pine64 hardware that needs specialised support, and I wanted to try Arch out. Hasn’t broken on me (yet!), but the forum certainly imploded somewhat recently. If I don’t want to have to think about anything OS/support-wise I usually use Ubuntu LTS, or Debian. Just don’t get me started on Windows 10… even the bleeding edge ‘unstable’ Arch would have to be more stable than that beast!
Interesting… funnily enough, it looks like the PlatformIO uDev rules don’t specify the default group - probably because it’s different between at least Arch and Debian and derivatives - not sure if the other root distros do it differently. That might be something worth looking into in the future.
1 Like
There is another posibility with Ubuntu’s Flatpacks. VSCode terminal can’t access root filesystem, and no /etc/udev can be found.
In a system terminal everything goes ok, but in VSCode term, the warning shows up.
A simple ‘ls -l /’ prints different contents. You can create /etc/udev/rules.d and copy the file there to avoid the warning.
I see this topic is outdated, but I haven’t found any answer about this anywhere, and maybe someone could need it.
1 Like