Page 1 of 2 12 LastLast
Results 1 to 10 of 20

Thread: serial terminal

  1. #1

    Default serial terminal

    openSUSE 13.2 (Harlequin) (x86_64)

    I have device connected to my PC via USB TTL Serial Adapter.
    I can see it OK:
    Code:
    linux-zajy:/dev/serial # ls by-id
    usb-1a86_USB2.0-Serial-if00-port0
    linux-zajy:/dev/serial # ls by-path
    pci-0000:00:02.0-usb-0:10:1.0-port0
    I have installed cutecom (serial terminal) from YAST

    but... when I try to connect/open device I just get error message (... could not connect...)
    I have tried all different permutations, but still no good

    Any ideas what am I doing wrong??

  2. #2
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,973

    Default Re: serial terminal

    ls -l would hve been better, It will show if this is a symlink and when yes to what and you are then able to do an ls -l of that device file and show it's permissions. When not it will show permissions directly.

    Also saying "when I try to connect/open device" is not very informative. You have to see these things from thje computers interpratation side. And the computer does not know any "I". It does know loged in users. Also it is always much, much better to not say: "When I ..., Then ...", show what you did and what the computer did. Copy/paste from the terminal into a post here. Like you did with those ls commands above.
    Henk van Velden

  3. #3

    Default Re: serial terminal

    thank you for replying.

    Quote Originally Posted by hcvv View Post
    ls -l would hve been better, It will show if this is a symlink and when yes to what and you are then able to do an ls -l of that device file and show it's permissions. When not it will show permissions directly...
    if I understand you correctly?
    Code:
    linux-zajy:~ # cd /dev/serial
    linux-zajy:/dev/serial # ls -l
    total 0
    drwxr-xr-x 2 root root 60 Jun 22 13:56 by-id
    drwxr-xr-x 2 root root 60 Jun 22 13:56 by-path
    linux-zajy:/dev/serial #
    Quote Originally Posted by hcvv View Post
    ...Also saying "when I try to connect/open device" is not very informative...
    Sorry, my description was deficient indeed.
    Hopefully this is better?:
    1 - start cutecom
    2 - press "opendevice" key after selecting device from dropdown list




    Quote Originally Posted by hcvv View Post
    ...You have to see these things from thje computers interpratation side. And the computer does not know any "I". It does know loged in users...
    I will try the cutecom as root?

    Quote Originally Posted by hcvv View Post
    ...Also it is always much, much better to not say: "When I ..., Then ...", show what you did and what the computer did....
    I did run cutecom and tried to open the device in cutecom

    Quote Originally Posted by hcvv View Post
    ...Copy/paste from the terminal into a post here. Like you did with those ls commands above.
    I didn't do anything in the terminal
    I tried using cutecom (serial terminal available from YAST)

  4. #4
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,973

    Default Re: serial terminal

    In your first post you did
    Code:
    ls /dev/serial/by-id
    I asked for
    Code:
    ls -l /dev/serial/by-id
    And that is done in the terminal isn't it?
    So you did do something in the terminal. Though not the program cutecom. And yes, when you would have explained that it is a GUI program that would have been more informative.

    As it is we still wait for the ownership and permissions of the device file as asked above. So the ls -l as asked above and when they are symlinks, then allso an ls -l of the file that they point to.

    If you should run cutecom as root I do not know. The documentation should tell you. But because "never run anything as root when it is not explicetly needed" you should not do that with the idea: Oh, I can always try as root
    Henk van Velden

  5. #5

    Default Re: serial terminal

    Quote Originally Posted by hcvv View Post
    ...
    I asked for
    Code:
    ls -l /dev/serial/by-id
    Now I understand , here it is:
    Code:
    linux-zajy:/home/bambuko # ls -l /dev/serial/by-id
    total 0
    lrwxrwxrwx 1 root root 13 Jun 22 13:56 usb-1a86_USB2.0-Serial-if00-port0 -> ../../ttyUSB0
    linux-zajy:/home/bambuko #

    Quote Originally Posted by hcvv View Post
    ... And yes, when you would have explained that it is a GUI program that would have been more informative...
    Indeed it would - sorry for not doing it in the first place.

  6. #6
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,973

    Default Re: serial terminal

    Quote Originally Posted by bambuko View Post
    Now I understand , here it is:
    Code:
    linux-zajy:/home/bambuko # ls -l /dev/serial/by-id
    total 0
    lrwxrwxrwx 1 root root 13 Jun 22 13:56 usb-1a86_USB2.0-Serial-if00-port0 -> ../../ttyUSB0
    linux-zajy:/home/bambuko #
    Thus, as explained above, we now need
    Code:
    ls -l /dev/ttyUSB0
    That is where the symlink you show points to. And that is the "real" device file.

    Quote Originally Posted by bambuko View Post
    Indeed it would - sorry for not doing it in the first place.
    Never mind.
    Henk van Velden

  7. #7

    Default Re: serial terminal

    Quote Originally Posted by hcvv View Post
    ...If you should run cutecom as root I do not know...
    cutecom in itself runs fine either as a root or anything else

    Quote Originally Posted by hcvv View Post
    ...The documentation should tell you...
    Perhaps it should, but I didn't find anything?

    Quote Originally Posted by hcvv View Post
    ...But because "never run anything as root when it is not explicetly needed" you should not do that with the idea: Oh, I can always try as root
    Good advice, however my reasons for asking this were not "...I can always try as root ..." rather a suspicion that my problems with opening of the device might have something to do with ownership and permissions.

    So, I did run cutecom as root and device seems to have opened OK.

  8. #8
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,696

    Default Re: serial terminal

    Firewall problem??

  9. #9

    Default Re: serial terminal

    Quote Originally Posted by hcvv View Post
    Thus, as explained above, we now need
    Code:
    ls -l /dev/ttyUSB0
    That is where the symlink you show points to. And that is the "real" device file.
    Doing that comes up with:
    Code:
    linux-zajy:/dev/serial # ls -l /dev/ttyUSB0
    crw-rw---- 1 root dialout 188, 0 Jun 22 15:26 /dev/ttyUSB0

  10. #10

    Default Re: serial terminal

    and a final edit:
    Everything works fine
    Device is opened and responding correctly

    all it took was to run cutecom as a root
    Thank you for your help and replies.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •