Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions.org? Visit the following links: If you have any problems with the registration process or your account login, please.

If you need to reset your password,. Having a problem logging in? Please visit to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant.

Using minicom to interface with serial devices on Linux. I came across a problem recently, I needed to configure a Cisco switch and all I had was a Ubuntu machine. Phoenix Drive Direct Game Rar File. Ubuntu putty and serial port. I use minicom. How to access to cisco's serial port using an usb-adapter?

They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. To receive this Complete Guide absolutely free.

Code: mknod /dev/ttyUSB0 c 188 0but this would not address why the device does not exist to begin with. If you manually create it, and it works, you'd need to ensure it remains persistent across reboots, or gets re-created with each reboot. In order for someone to help you address why it doesn't exist already, and how to ensure the device is created in the future, it would be helpful if you at least tell us what Linux OS you are working on, and perhaps, what sort of device you're toying with. Best regards!

Code:. Atma Darshan Krishna Menon Pdf Writer here. A - Serial Device: /dev/ttyUSB0 B - Lockfile Location: /var/lock C - Callin Program: D - Callout Program: E - Bps/Par/Bits: 9600 8N1 F - Hardware Flow Control: No G - Software Flow Control: No4. Save as default 5.Exit 6 In Terminal type minicom Device /dev/ttyUSB0 access failed:No such file or DIR I checked in dev directory ttyUSB0 does not exist What should i do Check the permissions on the /dev/ttyUSB0 device. If you're running it as a 'regular' user, the may not have rights to read/write the device. If not, go into root (or SUDO), and do a 'chmod 766' on that device, or try Minicom as root. Hi,I just discuss the problem if no device,maybe the driver not exist,so it maybe need to check the kernel or maybe to recompile,the problem puzzled me and your post,I read and then I had to clean my eyes What's there to be puzzled about?? Pay attention: • The module exists in every modern, current distro.

• At worst, the OP should have had to type in 'modprobe usb_serial' • Telling a newbie to recompile their kernel, when there's NOTHING to suggest they had to is very bad advice. Add to that, the OP has obviously solved their problem, since they didn't post back. So be sure to clean your eyes well.perhaps you'l then be able to write a clear sentence. What's there to be puzzled about??

Pay attention: • The module exists in every modern, current distro. • At worst, the OP should have had to type in 'modprobe usb_serial' • Telling a newbie to recompile their kernel, when there's NOTHING to suggest they had to is very bad advice. Add to that, the OP has obviously solved their problem, since they didn't post back. So be sure to clean your eyes well.perhaps you'l then be able to write a clear sentence. OK,now I show my detail to you some months ago, I had to communicate a ARM with serial cable,but there is not any serial port in my computer,so I used usb converting to serial. In that time I configure my minicom,but I hadn't found ttyUSB*,so I searched in google and got the resolvent that to make usb converting serial supported by kernel and recompile it.then I successed,when I modprobe usb_serial,I got a ttyUSB in my /dev in additional why do you think a newbie unable to recompile the kernel? The computer science requires a mass of practice.no practice,no inprovement.Is anybody a expert when he burning?

I am a newbie but I have the courage to ask,answer and do. OK,now I show my detail to you some months ago, I had to communicate a ARM with serial cable,but there is not any serial port in my computer,so I used usb converting to serial. In that time I configure my minicom,but I hadn't found ttyUSB*,so I searched in google and got the resolvent that to make usb converting serial supported by kernel and recompile it.then I successed,when I modprobe usb_serial,I got a ttyUSB in my /dev EXACTLY MY POINT. You didn't have to recompile your kernel, as I said several times. You had to do a modprobe.the module was already there, and I mentioned that to the OP before.