-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UUCP locking step fail in archlinuxARM #1189
Comments
See the discussion here, essentially Arch Linux seems to have some odd file permissions. Fix those and hopefully it will start working. |
OK that solved it, indeed ! I just had to copy /usr/lib/tmpfiles.d/legacy.conf into /etc/tmpfiles.d/ and edit it to set lock files to be owned by root, group uucp, perms 775 (instead of user root, group root and perm 755). I think I would be able to write a proper doc for using this device (and others) for archlinux (udev rule, uucp lock files, ola compilation and configuration, ...). Could you add it to the main site / somewhere else ? I think it could be very useful to archlinux ARM users. Who do I have to send it to ? Thanks a lot for this, |
I think you mean 777, unless your user is in the root group too? We've already got (a number) of docs on compiling OLA, so it would be more helpful to add any differences to those. Likewise we've got a page on device config (udev etc), we probably need to add the notes about UUCP on Arch to that page. |
Nop', root:uucp / 775 is good if you are in the uucp group. root:root / 777 works too. Considering the fact that you have to create a udev rule to mount /dev/ttyUSB0 with the uucp group, you're already supposed to be part of it, so I chose the uucp solution. Ok, do you want me to think of something for the page that you could just copy / paste ? Or you just prefer to let the OLA team doing so ? |
Sorry, I missed the uucp group bit. Yes if you can write something that would be great. Here are the pages we've got that I think are relevant: |
I have exams atm but i promise, I won't let down archlinux OLA users, as I had so much difficulties with this !! Give me one week or so :) |
Linux InstallArchlinuxJust install it from the AUR packages, with yaourt or packer : And then follow instructions for dependencies and compilation. Archlinux ARMYou can install it from the AUR too (see Archlinux section), but an extra step is required. Yaourt is more difficult to install on Arch ARM, so we'll use packer package manager for AUR access. Edit PKGBUILD to add "armv7h" or whatever your architecture is in the line For example, for armv7h : And then follow instructions for dependencies and compilation. Device specific configurationEnttec USB/DMX Pro on Archlinux ARMTo access the Enttec USB/DMX Pro in OLA on Archlinux ARM, you have to add a udev rule to mount the device with correct permissions :
(found on D-Light linux instructions) Then you have to ensure your /run/lock directory is mounted with permission such as root:lock / 775.
Then add yourself to both Ensure your systemd-tmpfiles service is running by doing : Then reboot and use the OLA usbserial module to detect your Enttec USB/DMX Pro. |
Hi,
I've got some problems running ola on my raspberry pi B2, with ArchlinuxARM and an Enttec DMX USB Pro.
I have the latest version of everything.
Basically ola is telling that it does not have the permission to access / modify /var/lock/LCK..ttyUSB0
I have explained everything on the archlinux ARM forum, and posted a message in ola's google mailing list too
In #960, i see that you added uucp locking. I got the message that the permission required is not checked, but in fact there is no LCK..ttyUSB0 file in /var/lock/ ... So I don't know who to tell this to, you the ola dev team or the archlinux ARM team for driver oriented solution maybe ?
Please see my archlinux ARM post for full logs and infos.
Thank you for reading.
The text was updated successfully, but these errors were encountered: