How to connect to my usb-to-serial thingy on OpenBSD

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












3















I have an old OpenBSD (5.0 GENERIC#43 i386) at a production site. Now I'm trying to connect a zebra-printer to it with a usb-to-serial cable without success. The issue is getting the device to exist and configured.



How do I do that? Or is it already there?



Some output:



foobar# dmesg
...
uplcom0 at uhub1 port 1 "Prolific Technology Inc. USB-Serial Controller D" rev 1.10/3.00 addr 2
ucom0 at uplcom0
...

foobar# usbdevs -d
addr 1: EHCI root hub, Intel
uhub0
addr 1: UHCI root hub, Intel
uhub1
addr 2: USB-Serial Controller D, Prolific Technology Inc.
uplcom0
addr 1: UHCI root hub, Intel
uhub2
addr 2: Lexmark T630, Lexmark International
ulpt0
addr 3: USB Optical Mouse, Logitech
uhidev0
addr 1: UHCI root hub, Intel
uhub3

foobar# usbdevs -df /dev/usb1
addr 1: UHCI root hub, Intel
uhub1
addr 2: USB-Serial Controller D, Prolific Technology Inc.
uplcom0

foobar# ls /dev/ucom0 /dev/uplcom0
ls: /dev/ucom0: No such file or directory
ls: /dev/uplcom0: No such file or directory


Note that the ulpt0-device is connected to a regular paper-printer and that is working properly, it is the uplcom0-device that I can't get to.



According to man ucom there seems to be some thing on /dev/ttyU?. I have also tried sending data to these with no success. On /dev/ttyU0 I interrupt after waiting some minutes and get the message:



ksh: cannot create /dev/ttyU0: Interrupted system call


For the others /dev/ttyU[1-3] I get messages similar to this:



ksh: cannot create /dev/ttyU1: Device not configured









share|improve this question
























  • Do you have anything attaching as an ulpt device? (Reading again) Yes you have. Is that not your printer?

    – Kusalananda
    Apr 25 '17 at 10:13












  • Ah, sorry for the confusion. The ulpt0-device is a regular paper-printer, and that is working properly. It is the uplcom0 that is connected to the zebra-label-printer, but I can not get to it.

    – UlfR
    Apr 25 '17 at 10:34















3















I have an old OpenBSD (5.0 GENERIC#43 i386) at a production site. Now I'm trying to connect a zebra-printer to it with a usb-to-serial cable without success. The issue is getting the device to exist and configured.



How do I do that? Or is it already there?



Some output:



foobar# dmesg
...
uplcom0 at uhub1 port 1 "Prolific Technology Inc. USB-Serial Controller D" rev 1.10/3.00 addr 2
ucom0 at uplcom0
...

foobar# usbdevs -d
addr 1: EHCI root hub, Intel
uhub0
addr 1: UHCI root hub, Intel
uhub1
addr 2: USB-Serial Controller D, Prolific Technology Inc.
uplcom0
addr 1: UHCI root hub, Intel
uhub2
addr 2: Lexmark T630, Lexmark International
ulpt0
addr 3: USB Optical Mouse, Logitech
uhidev0
addr 1: UHCI root hub, Intel
uhub3

foobar# usbdevs -df /dev/usb1
addr 1: UHCI root hub, Intel
uhub1
addr 2: USB-Serial Controller D, Prolific Technology Inc.
uplcom0

foobar# ls /dev/ucom0 /dev/uplcom0
ls: /dev/ucom0: No such file or directory
ls: /dev/uplcom0: No such file or directory


Note that the ulpt0-device is connected to a regular paper-printer and that is working properly, it is the uplcom0-device that I can't get to.



According to man ucom there seems to be some thing on /dev/ttyU?. I have also tried sending data to these with no success. On /dev/ttyU0 I interrupt after waiting some minutes and get the message:



ksh: cannot create /dev/ttyU0: Interrupted system call


For the others /dev/ttyU[1-3] I get messages similar to this:



ksh: cannot create /dev/ttyU1: Device not configured









share|improve this question
























  • Do you have anything attaching as an ulpt device? (Reading again) Yes you have. Is that not your printer?

    – Kusalananda
    Apr 25 '17 at 10:13












  • Ah, sorry for the confusion. The ulpt0-device is a regular paper-printer, and that is working properly. It is the uplcom0 that is connected to the zebra-label-printer, but I can not get to it.

    – UlfR
    Apr 25 '17 at 10:34













3












3








3








I have an old OpenBSD (5.0 GENERIC#43 i386) at a production site. Now I'm trying to connect a zebra-printer to it with a usb-to-serial cable without success. The issue is getting the device to exist and configured.



How do I do that? Or is it already there?



Some output:



foobar# dmesg
...
uplcom0 at uhub1 port 1 "Prolific Technology Inc. USB-Serial Controller D" rev 1.10/3.00 addr 2
ucom0 at uplcom0
...

foobar# usbdevs -d
addr 1: EHCI root hub, Intel
uhub0
addr 1: UHCI root hub, Intel
uhub1
addr 2: USB-Serial Controller D, Prolific Technology Inc.
uplcom0
addr 1: UHCI root hub, Intel
uhub2
addr 2: Lexmark T630, Lexmark International
ulpt0
addr 3: USB Optical Mouse, Logitech
uhidev0
addr 1: UHCI root hub, Intel
uhub3

foobar# usbdevs -df /dev/usb1
addr 1: UHCI root hub, Intel
uhub1
addr 2: USB-Serial Controller D, Prolific Technology Inc.
uplcom0

foobar# ls /dev/ucom0 /dev/uplcom0
ls: /dev/ucom0: No such file or directory
ls: /dev/uplcom0: No such file or directory


Note that the ulpt0-device is connected to a regular paper-printer and that is working properly, it is the uplcom0-device that I can't get to.



According to man ucom there seems to be some thing on /dev/ttyU?. I have also tried sending data to these with no success. On /dev/ttyU0 I interrupt after waiting some minutes and get the message:



ksh: cannot create /dev/ttyU0: Interrupted system call


For the others /dev/ttyU[1-3] I get messages similar to this:



ksh: cannot create /dev/ttyU1: Device not configured









share|improve this question
















I have an old OpenBSD (5.0 GENERIC#43 i386) at a production site. Now I'm trying to connect a zebra-printer to it with a usb-to-serial cable without success. The issue is getting the device to exist and configured.



How do I do that? Or is it already there?



Some output:



foobar# dmesg
...
uplcom0 at uhub1 port 1 "Prolific Technology Inc. USB-Serial Controller D" rev 1.10/3.00 addr 2
ucom0 at uplcom0
...

foobar# usbdevs -d
addr 1: EHCI root hub, Intel
uhub0
addr 1: UHCI root hub, Intel
uhub1
addr 2: USB-Serial Controller D, Prolific Technology Inc.
uplcom0
addr 1: UHCI root hub, Intel
uhub2
addr 2: Lexmark T630, Lexmark International
ulpt0
addr 3: USB Optical Mouse, Logitech
uhidev0
addr 1: UHCI root hub, Intel
uhub3

foobar# usbdevs -df /dev/usb1
addr 1: UHCI root hub, Intel
uhub1
addr 2: USB-Serial Controller D, Prolific Technology Inc.
uplcom0

foobar# ls /dev/ucom0 /dev/uplcom0
ls: /dev/ucom0: No such file or directory
ls: /dev/uplcom0: No such file or directory


Note that the ulpt0-device is connected to a regular paper-printer and that is working properly, it is the uplcom0-device that I can't get to.



According to man ucom there seems to be some thing on /dev/ttyU?. I have also tried sending data to these with no success. On /dev/ttyU0 I interrupt after waiting some minutes and get the message:



ksh: cannot create /dev/ttyU0: Interrupted system call


For the others /dev/ttyU[1-3] I get messages similar to this:



ksh: cannot create /dev/ttyU1: Device not configured






usb openbsd serial-port printer






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 13 at 21:45









Rui F Ribeiro

39.7k1479132




39.7k1479132










asked Apr 25 '17 at 10:01









UlfRUlfR

1737




1737












  • Do you have anything attaching as an ulpt device? (Reading again) Yes you have. Is that not your printer?

    – Kusalananda
    Apr 25 '17 at 10:13












  • Ah, sorry for the confusion. The ulpt0-device is a regular paper-printer, and that is working properly. It is the uplcom0 that is connected to the zebra-label-printer, but I can not get to it.

    – UlfR
    Apr 25 '17 at 10:34

















  • Do you have anything attaching as an ulpt device? (Reading again) Yes you have. Is that not your printer?

    – Kusalananda
    Apr 25 '17 at 10:13












  • Ah, sorry for the confusion. The ulpt0-device is a regular paper-printer, and that is working properly. It is the uplcom0 that is connected to the zebra-label-printer, but I can not get to it.

    – UlfR
    Apr 25 '17 at 10:34
















Do you have anything attaching as an ulpt device? (Reading again) Yes you have. Is that not your printer?

– Kusalananda
Apr 25 '17 at 10:13






Do you have anything attaching as an ulpt device? (Reading again) Yes you have. Is that not your printer?

– Kusalananda
Apr 25 '17 at 10:13














Ah, sorry for the confusion. The ulpt0-device is a regular paper-printer, and that is working properly. It is the uplcom0 that is connected to the zebra-label-printer, but I can not get to it.

– UlfR
Apr 25 '17 at 10:34





Ah, sorry for the confusion. The ulpt0-device is a regular paper-printer, and that is working properly. It is the uplcom0 that is connected to the zebra-label-printer, but I can not get to it.

– UlfR
Apr 25 '17 at 10:34










1 Answer
1






active

oldest

votes


















3














Read man 4 ucom. You are probably looking for /dev/cuaU0 which is the "calling unit" (see man 4 tty) for the ttyU0 terminal.



Try # cu -s 115200 -l /dev/cuaU0 to see if you can chat with the printer. Change the baud rate from 115200 to something else, if needed be (the default is 9600).



Also, remember that only root and users on the dialer group have permission to read/write to /dev/cuaU0, so you might want to add your user to the dialer group: # usermod -G dialer foo.






share|improve this answer






















    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    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: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    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
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f361150%2fhow-to-connect-to-my-usb-to-serial-thingy-on-openbsd%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    3














    Read man 4 ucom. You are probably looking for /dev/cuaU0 which is the "calling unit" (see man 4 tty) for the ttyU0 terminal.



    Try # cu -s 115200 -l /dev/cuaU0 to see if you can chat with the printer. Change the baud rate from 115200 to something else, if needed be (the default is 9600).



    Also, remember that only root and users on the dialer group have permission to read/write to /dev/cuaU0, so you might want to add your user to the dialer group: # usermod -G dialer foo.






    share|improve this answer



























      3














      Read man 4 ucom. You are probably looking for /dev/cuaU0 which is the "calling unit" (see man 4 tty) for the ttyU0 terminal.



      Try # cu -s 115200 -l /dev/cuaU0 to see if you can chat with the printer. Change the baud rate from 115200 to something else, if needed be (the default is 9600).



      Also, remember that only root and users on the dialer group have permission to read/write to /dev/cuaU0, so you might want to add your user to the dialer group: # usermod -G dialer foo.






      share|improve this answer

























        3












        3








        3







        Read man 4 ucom. You are probably looking for /dev/cuaU0 which is the "calling unit" (see man 4 tty) for the ttyU0 terminal.



        Try # cu -s 115200 -l /dev/cuaU0 to see if you can chat with the printer. Change the baud rate from 115200 to something else, if needed be (the default is 9600).



        Also, remember that only root and users on the dialer group have permission to read/write to /dev/cuaU0, so you might want to add your user to the dialer group: # usermod -G dialer foo.






        share|improve this answer













        Read man 4 ucom. You are probably looking for /dev/cuaU0 which is the "calling unit" (see man 4 tty) for the ttyU0 terminal.



        Try # cu -s 115200 -l /dev/cuaU0 to see if you can chat with the printer. Change the baud rate from 115200 to something else, if needed be (the default is 9600).



        Also, remember that only root and users on the dialer group have permission to read/write to /dev/cuaU0, so you might want to add your user to the dialer group: # usermod -G dialer foo.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Apr 26 '17 at 10:24









        Zé LoffZé Loff

        42329




        42329



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • 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.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f361150%2fhow-to-connect-to-my-usb-to-serial-thingy-on-openbsd%23new-answer', 'question_page');

            );

            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






            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Displaying single band from multi-band raster using QGIS

            How many registers does an x86_64 CPU actually have?