UDEV rules for FTDI not completely working
I know this question has been asked many times but I cannot make it work. I have a FTDI serial-usb converter. I have generated 10-fhss-usb.rules
in /etc/udev/rules.d/
:
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="FTTA5DMA", SYMLINK+="fhss", GROUP="dialout", MODE="0777", RUN+="echo USB CONNECTED!"
I have also added my user to dialout
group:
sudo usermod -a -G dialout $USER
and groups $USER
returns:
jvgomez : jvgomez adm dialout sudo plugdev lpadmin sambashare
(The plugdev group was created following another post) Now, when I connect the USB, running ls -al
I can see:
$ ls -al /dev/fhss
lrwxrwxrwx 1 root root 7 Jun 4 17:13 /dev/fhss -> ttyUSB0
$ ls -al /dev/ttyUSB0
crw-rw-r-- 1 root dialout 188, 0 Jun 4 17:13 /dev/ttyUSB0
The echo USB CONNECTED!
message is never displayed. And when I use screen /dev/fhss/
it immediately says [screen is terminating]
. To make it work, I sill have to run chmod
$ sudo chmod a+rwx /dev/fhss
And now:
$ ls -al /dev/ttyUSB0
crwxrwxrwx 1 root dialout 188, 0 Jun 4 17:13 /dev/ttyUSB0
1) What am I missing? I still have to run chmod which is what I am trying to avoid.
2) What is the difference between using SUBSYSTEM=="tty"
and SUBSYSTEM=="usb"
?
Any help is welcome!
EDIT: adding NAME="my_device" as proposed in Usb udev rule never worked for me didn't change anything.
usb permissions udev
add a comment |
I know this question has been asked many times but I cannot make it work. I have a FTDI serial-usb converter. I have generated 10-fhss-usb.rules
in /etc/udev/rules.d/
:
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="FTTA5DMA", SYMLINK+="fhss", GROUP="dialout", MODE="0777", RUN+="echo USB CONNECTED!"
I have also added my user to dialout
group:
sudo usermod -a -G dialout $USER
and groups $USER
returns:
jvgomez : jvgomez adm dialout sudo plugdev lpadmin sambashare
(The plugdev group was created following another post) Now, when I connect the USB, running ls -al
I can see:
$ ls -al /dev/fhss
lrwxrwxrwx 1 root root 7 Jun 4 17:13 /dev/fhss -> ttyUSB0
$ ls -al /dev/ttyUSB0
crw-rw-r-- 1 root dialout 188, 0 Jun 4 17:13 /dev/ttyUSB0
The echo USB CONNECTED!
message is never displayed. And when I use screen /dev/fhss/
it immediately says [screen is terminating]
. To make it work, I sill have to run chmod
$ sudo chmod a+rwx /dev/fhss
And now:
$ ls -al /dev/ttyUSB0
crwxrwxrwx 1 root dialout 188, 0 Jun 4 17:13 /dev/ttyUSB0
1) What am I missing? I still have to run chmod which is what I am trying to avoid.
2) What is the difference between using SUBSYSTEM=="tty"
and SUBSYSTEM=="usb"
?
Any help is welcome!
EDIT: adding NAME="my_device" as proposed in Usb udev rule never worked for me didn't change anything.
usb permissions udev
Did you ever get a solution?
– Goddard
Apr 15 '16 at 5:51
@Goddard I have it working yes, although the udev rule is exactly the same as posted (withNAME="my_device"
). I cannot tell what I did to make it work, I cannot remember, sorry!
– Javi V
Apr 19 '16 at 11:41
add a comment |
I know this question has been asked many times but I cannot make it work. I have a FTDI serial-usb converter. I have generated 10-fhss-usb.rules
in /etc/udev/rules.d/
:
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="FTTA5DMA", SYMLINK+="fhss", GROUP="dialout", MODE="0777", RUN+="echo USB CONNECTED!"
I have also added my user to dialout
group:
sudo usermod -a -G dialout $USER
and groups $USER
returns:
jvgomez : jvgomez adm dialout sudo plugdev lpadmin sambashare
(The plugdev group was created following another post) Now, when I connect the USB, running ls -al
I can see:
$ ls -al /dev/fhss
lrwxrwxrwx 1 root root 7 Jun 4 17:13 /dev/fhss -> ttyUSB0
$ ls -al /dev/ttyUSB0
crw-rw-r-- 1 root dialout 188, 0 Jun 4 17:13 /dev/ttyUSB0
The echo USB CONNECTED!
message is never displayed. And when I use screen /dev/fhss/
it immediately says [screen is terminating]
. To make it work, I sill have to run chmod
$ sudo chmod a+rwx /dev/fhss
And now:
$ ls -al /dev/ttyUSB0
crwxrwxrwx 1 root dialout 188, 0 Jun 4 17:13 /dev/ttyUSB0
1) What am I missing? I still have to run chmod which is what I am trying to avoid.
2) What is the difference between using SUBSYSTEM=="tty"
and SUBSYSTEM=="usb"
?
Any help is welcome!
EDIT: adding NAME="my_device" as proposed in Usb udev rule never worked for me didn't change anything.
usb permissions udev
I know this question has been asked many times but I cannot make it work. I have a FTDI serial-usb converter. I have generated 10-fhss-usb.rules
in /etc/udev/rules.d/
:
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", ATTRS{serial}=="FTTA5DMA", SYMLINK+="fhss", GROUP="dialout", MODE="0777", RUN+="echo USB CONNECTED!"
I have also added my user to dialout
group:
sudo usermod -a -G dialout $USER
and groups $USER
returns:
jvgomez : jvgomez adm dialout sudo plugdev lpadmin sambashare
(The plugdev group was created following another post) Now, when I connect the USB, running ls -al
I can see:
$ ls -al /dev/fhss
lrwxrwxrwx 1 root root 7 Jun 4 17:13 /dev/fhss -> ttyUSB0
$ ls -al /dev/ttyUSB0
crw-rw-r-- 1 root dialout 188, 0 Jun 4 17:13 /dev/ttyUSB0
The echo USB CONNECTED!
message is never displayed. And when I use screen /dev/fhss/
it immediately says [screen is terminating]
. To make it work, I sill have to run chmod
$ sudo chmod a+rwx /dev/fhss
And now:
$ ls -al /dev/ttyUSB0
crwxrwxrwx 1 root dialout 188, 0 Jun 4 17:13 /dev/ttyUSB0
1) What am I missing? I still have to run chmod which is what I am trying to avoid.
2) What is the difference between using SUBSYSTEM=="tty"
and SUBSYSTEM=="usb"
?
Any help is welcome!
EDIT: adding NAME="my_device" as proposed in Usb udev rule never worked for me didn't change anything.
usb permissions udev
usb permissions udev
edited Apr 13 '17 at 12:25
Community♦
1
1
asked Jun 4 '15 at 15:24
Javi VJavi V
12316
12316
Did you ever get a solution?
– Goddard
Apr 15 '16 at 5:51
@Goddard I have it working yes, although the udev rule is exactly the same as posted (withNAME="my_device"
). I cannot tell what I did to make it work, I cannot remember, sorry!
– Javi V
Apr 19 '16 at 11:41
add a comment |
Did you ever get a solution?
– Goddard
Apr 15 '16 at 5:51
@Goddard I have it working yes, although the udev rule is exactly the same as posted (withNAME="my_device"
). I cannot tell what I did to make it work, I cannot remember, sorry!
– Javi V
Apr 19 '16 at 11:41
Did you ever get a solution?
– Goddard
Apr 15 '16 at 5:51
Did you ever get a solution?
– Goddard
Apr 15 '16 at 5:51
@Goddard I have it working yes, although the udev rule is exactly the same as posted (with
NAME="my_device"
). I cannot tell what I did to make it work, I cannot remember, sorry!– Javi V
Apr 19 '16 at 11:41
@Goddard I have it working yes, although the udev rule is exactly the same as posted (with
NAME="my_device"
). I cannot tell what I did to make it work, I cannot remember, sorry!– Javi V
Apr 19 '16 at 11:41
add a comment |
2 Answers
2
active
oldest
votes
To make a FTDI breakout work on Ubuntu:
Open the file /etc/group with root permissions:
sudo nano /etc/group
After that, search for tty:x5:
and dialout:x20:
Add your user to this groups typing your username in front of each line:
tty:x5:<user>
dialout:x20:<user>
You can also use the next two commands to avoid search for the file:
sudo usermod -aG tty <user>
sudo usermod -aG dialout <user>
Where <user>
, is your user name.
Finally, reboot your computer.
If you want to use udev rules, connect the FTDI Module, then run:
lsusb
This will show the vendorID and the productID. For example:
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Where 8087 is the vendorID, and 0024 the productID.
Then, create a rule like this:
ATTRS{idVendor}="8087", ATTRS{idProduct}="0024", MODE="0660", GROUP="dialout"
1
This was what I was looking for all the time. I had got the "ftdi" driver as part of my linux kernel (/usr/share/hwdatausb.ids) to detect the vendor ID available and could confirm that "udev rules" had my Vid and Pid. But still, the driver wasn't detected the connection. THis was the trick ! Thanks @Gtronick !!
– Adit Ya
Jul 20 '17 at 10:21
1
There's a typo, it should beATTRS{idVendor}="8087", ATTRS{idProduct}="0024", MODE="0660", GROUP="dialout"
, instead of the second "ATRRS".
– PJ_Finnegan
yesterday
Thanks, edit made. :D
– GTRONICK
10 hours ago
add a comment |
I use a FT232RL chip in Bit Bang mode and ran into the same permission issues.
The rules suggested above did not work for me for reasons I do not understand.
However, with some modification I got it working.
Hopefully this can be of help to someone:
$ lsusb
:
Bus 001 Device 023: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
As above, I added the user to dialout
and tty
:
$ sudo usermod -aG dialout $USER
$ sudo usermod -aG tty $USER
But, the line in /etc/udev/rules.d/99-libftdi.rules
, is different:
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="0403", ATTRS={idProduct}=="6001", OWNER="user", MODE="0777", GROUP="dialout"
It could be that the crucial difference is SUBSYSTEM=="usb"
.
It worked for me. You can substituteATTRS="idProduct"
withATTRS{idProduct}
though, as inidVendor
.
– PJ_Finnegan
yesterday
@PJ_Finnegan edited included. Thanks.
– kalleknast
10 hours ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f632261%2fudev-rules-for-ftdi-not-completely-working%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
To make a FTDI breakout work on Ubuntu:
Open the file /etc/group with root permissions:
sudo nano /etc/group
After that, search for tty:x5:
and dialout:x20:
Add your user to this groups typing your username in front of each line:
tty:x5:<user>
dialout:x20:<user>
You can also use the next two commands to avoid search for the file:
sudo usermod -aG tty <user>
sudo usermod -aG dialout <user>
Where <user>
, is your user name.
Finally, reboot your computer.
If you want to use udev rules, connect the FTDI Module, then run:
lsusb
This will show the vendorID and the productID. For example:
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Where 8087 is the vendorID, and 0024 the productID.
Then, create a rule like this:
ATTRS{idVendor}="8087", ATTRS{idProduct}="0024", MODE="0660", GROUP="dialout"
1
This was what I was looking for all the time. I had got the "ftdi" driver as part of my linux kernel (/usr/share/hwdatausb.ids) to detect the vendor ID available and could confirm that "udev rules" had my Vid and Pid. But still, the driver wasn't detected the connection. THis was the trick ! Thanks @Gtronick !!
– Adit Ya
Jul 20 '17 at 10:21
1
There's a typo, it should beATTRS{idVendor}="8087", ATTRS{idProduct}="0024", MODE="0660", GROUP="dialout"
, instead of the second "ATRRS".
– PJ_Finnegan
yesterday
Thanks, edit made. :D
– GTRONICK
10 hours ago
add a comment |
To make a FTDI breakout work on Ubuntu:
Open the file /etc/group with root permissions:
sudo nano /etc/group
After that, search for tty:x5:
and dialout:x20:
Add your user to this groups typing your username in front of each line:
tty:x5:<user>
dialout:x20:<user>
You can also use the next two commands to avoid search for the file:
sudo usermod -aG tty <user>
sudo usermod -aG dialout <user>
Where <user>
, is your user name.
Finally, reboot your computer.
If you want to use udev rules, connect the FTDI Module, then run:
lsusb
This will show the vendorID and the productID. For example:
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Where 8087 is the vendorID, and 0024 the productID.
Then, create a rule like this:
ATTRS{idVendor}="8087", ATTRS{idProduct}="0024", MODE="0660", GROUP="dialout"
1
This was what I was looking for all the time. I had got the "ftdi" driver as part of my linux kernel (/usr/share/hwdatausb.ids) to detect the vendor ID available and could confirm that "udev rules" had my Vid and Pid. But still, the driver wasn't detected the connection. THis was the trick ! Thanks @Gtronick !!
– Adit Ya
Jul 20 '17 at 10:21
1
There's a typo, it should beATTRS{idVendor}="8087", ATTRS{idProduct}="0024", MODE="0660", GROUP="dialout"
, instead of the second "ATRRS".
– PJ_Finnegan
yesterday
Thanks, edit made. :D
– GTRONICK
10 hours ago
add a comment |
To make a FTDI breakout work on Ubuntu:
Open the file /etc/group with root permissions:
sudo nano /etc/group
After that, search for tty:x5:
and dialout:x20:
Add your user to this groups typing your username in front of each line:
tty:x5:<user>
dialout:x20:<user>
You can also use the next two commands to avoid search for the file:
sudo usermod -aG tty <user>
sudo usermod -aG dialout <user>
Where <user>
, is your user name.
Finally, reboot your computer.
If you want to use udev rules, connect the FTDI Module, then run:
lsusb
This will show the vendorID and the productID. For example:
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Where 8087 is the vendorID, and 0024 the productID.
Then, create a rule like this:
ATTRS{idVendor}="8087", ATTRS{idProduct}="0024", MODE="0660", GROUP="dialout"
To make a FTDI breakout work on Ubuntu:
Open the file /etc/group with root permissions:
sudo nano /etc/group
After that, search for tty:x5:
and dialout:x20:
Add your user to this groups typing your username in front of each line:
tty:x5:<user>
dialout:x20:<user>
You can also use the next two commands to avoid search for the file:
sudo usermod -aG tty <user>
sudo usermod -aG dialout <user>
Where <user>
, is your user name.
Finally, reboot your computer.
If you want to use udev rules, connect the FTDI Module, then run:
lsusb
This will show the vendorID and the productID. For example:
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Where 8087 is the vendorID, and 0024 the productID.
Then, create a rule like this:
ATTRS{idVendor}="8087", ATTRS{idProduct}="0024", MODE="0660", GROUP="dialout"
edited 11 hours ago
answered Jul 19 '16 at 17:08
GTRONICKGTRONICK
2,88811021
2,88811021
1
This was what I was looking for all the time. I had got the "ftdi" driver as part of my linux kernel (/usr/share/hwdatausb.ids) to detect the vendor ID available and could confirm that "udev rules" had my Vid and Pid. But still, the driver wasn't detected the connection. THis was the trick ! Thanks @Gtronick !!
– Adit Ya
Jul 20 '17 at 10:21
1
There's a typo, it should beATTRS{idVendor}="8087", ATTRS{idProduct}="0024", MODE="0660", GROUP="dialout"
, instead of the second "ATRRS".
– PJ_Finnegan
yesterday
Thanks, edit made. :D
– GTRONICK
10 hours ago
add a comment |
1
This was what I was looking for all the time. I had got the "ftdi" driver as part of my linux kernel (/usr/share/hwdatausb.ids) to detect the vendor ID available and could confirm that "udev rules" had my Vid and Pid. But still, the driver wasn't detected the connection. THis was the trick ! Thanks @Gtronick !!
– Adit Ya
Jul 20 '17 at 10:21
1
There's a typo, it should beATTRS{idVendor}="8087", ATTRS{idProduct}="0024", MODE="0660", GROUP="dialout"
, instead of the second "ATRRS".
– PJ_Finnegan
yesterday
Thanks, edit made. :D
– GTRONICK
10 hours ago
1
1
This was what I was looking for all the time. I had got the "ftdi" driver as part of my linux kernel (/usr/share/hwdatausb.ids) to detect the vendor ID available and could confirm that "udev rules" had my Vid and Pid. But still, the driver wasn't detected the connection. THis was the trick ! Thanks @Gtronick !!
– Adit Ya
Jul 20 '17 at 10:21
This was what I was looking for all the time. I had got the "ftdi" driver as part of my linux kernel (/usr/share/hwdatausb.ids) to detect the vendor ID available and could confirm that "udev rules" had my Vid and Pid. But still, the driver wasn't detected the connection. THis was the trick ! Thanks @Gtronick !!
– Adit Ya
Jul 20 '17 at 10:21
1
1
There's a typo, it should be
ATTRS{idVendor}="8087", ATTRS{idProduct}="0024", MODE="0660", GROUP="dialout"
, instead of the second "ATRRS".– PJ_Finnegan
yesterday
There's a typo, it should be
ATTRS{idVendor}="8087", ATTRS{idProduct}="0024", MODE="0660", GROUP="dialout"
, instead of the second "ATRRS".– PJ_Finnegan
yesterday
Thanks, edit made. :D
– GTRONICK
10 hours ago
Thanks, edit made. :D
– GTRONICK
10 hours ago
add a comment |
I use a FT232RL chip in Bit Bang mode and ran into the same permission issues.
The rules suggested above did not work for me for reasons I do not understand.
However, with some modification I got it working.
Hopefully this can be of help to someone:
$ lsusb
:
Bus 001 Device 023: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
As above, I added the user to dialout
and tty
:
$ sudo usermod -aG dialout $USER
$ sudo usermod -aG tty $USER
But, the line in /etc/udev/rules.d/99-libftdi.rules
, is different:
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="0403", ATTRS={idProduct}=="6001", OWNER="user", MODE="0777", GROUP="dialout"
It could be that the crucial difference is SUBSYSTEM=="usb"
.
It worked for me. You can substituteATTRS="idProduct"
withATTRS{idProduct}
though, as inidVendor
.
– PJ_Finnegan
yesterday
@PJ_Finnegan edited included. Thanks.
– kalleknast
10 hours ago
add a comment |
I use a FT232RL chip in Bit Bang mode and ran into the same permission issues.
The rules suggested above did not work for me for reasons I do not understand.
However, with some modification I got it working.
Hopefully this can be of help to someone:
$ lsusb
:
Bus 001 Device 023: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
As above, I added the user to dialout
and tty
:
$ sudo usermod -aG dialout $USER
$ sudo usermod -aG tty $USER
But, the line in /etc/udev/rules.d/99-libftdi.rules
, is different:
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="0403", ATTRS={idProduct}=="6001", OWNER="user", MODE="0777", GROUP="dialout"
It could be that the crucial difference is SUBSYSTEM=="usb"
.
It worked for me. You can substituteATTRS="idProduct"
withATTRS{idProduct}
though, as inidVendor
.
– PJ_Finnegan
yesterday
@PJ_Finnegan edited included. Thanks.
– kalleknast
10 hours ago
add a comment |
I use a FT232RL chip in Bit Bang mode and ran into the same permission issues.
The rules suggested above did not work for me for reasons I do not understand.
However, with some modification I got it working.
Hopefully this can be of help to someone:
$ lsusb
:
Bus 001 Device 023: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
As above, I added the user to dialout
and tty
:
$ sudo usermod -aG dialout $USER
$ sudo usermod -aG tty $USER
But, the line in /etc/udev/rules.d/99-libftdi.rules
, is different:
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="0403", ATTRS={idProduct}=="6001", OWNER="user", MODE="0777", GROUP="dialout"
It could be that the crucial difference is SUBSYSTEM=="usb"
.
I use a FT232RL chip in Bit Bang mode and ran into the same permission issues.
The rules suggested above did not work for me for reasons I do not understand.
However, with some modification I got it working.
Hopefully this can be of help to someone:
$ lsusb
:
Bus 001 Device 023: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
As above, I added the user to dialout
and tty
:
$ sudo usermod -aG dialout $USER
$ sudo usermod -aG tty $USER
But, the line in /etc/udev/rules.d/99-libftdi.rules
, is different:
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="0403", ATTRS={idProduct}=="6001", OWNER="user", MODE="0777", GROUP="dialout"
It could be that the crucial difference is SUBSYSTEM=="usb"
.
edited 10 hours ago
answered Jun 29 '17 at 20:43
kalleknastkalleknast
363
363
It worked for me. You can substituteATTRS="idProduct"
withATTRS{idProduct}
though, as inidVendor
.
– PJ_Finnegan
yesterday
@PJ_Finnegan edited included. Thanks.
– kalleknast
10 hours ago
add a comment |
It worked for me. You can substituteATTRS="idProduct"
withATTRS{idProduct}
though, as inidVendor
.
– PJ_Finnegan
yesterday
@PJ_Finnegan edited included. Thanks.
– kalleknast
10 hours ago
It worked for me. You can substitute
ATTRS="idProduct"
with ATTRS{idProduct}
though, as in idVendor
.– PJ_Finnegan
yesterday
It worked for me. You can substitute
ATTRS="idProduct"
with ATTRS{idProduct}
though, as in idVendor
.– PJ_Finnegan
yesterday
@PJ_Finnegan edited included. Thanks.
– kalleknast
10 hours ago
@PJ_Finnegan edited included. Thanks.
– kalleknast
10 hours ago
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f632261%2fudev-rules-for-ftdi-not-completely-working%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Did you ever get a solution?
– Goddard
Apr 15 '16 at 5:51
@Goddard I have it working yes, although the udev rule is exactly the same as posted (with
NAME="my_device"
). I cannot tell what I did to make it work, I cannot remember, sorry!– Javi V
Apr 19 '16 at 11:41