Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
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. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm actually not a 'really' newbie in Linux, but it's already been a while since I used openSUSE 10.2, I don't really touch Linux until now.
I just installed openSUSE 11.1 in my PC. And I found no problem in installing it. But later i realized that the on-board serial port is not working. I've tried to see the configuration using setserial, and the result is like this:
I assumed that it should be working fine, but actually I can't connect to other equipment using it. For example, I tried to connect to a cisco device using minicom, but it failed to connect. It seems like Linux (or the program) doesn't recognize the port.
Does anyone here have any idea on how to make it work? Thanks in advance.
A number of possibilities exist. Since setserial recognizes the port, and since the numbers that is report look completely normal, I am going to work on the premise that the device and attendant driver are present and working. The connection to your external device require that a proper cable (and not all RS-232 cables are created equal) is installed. Usually, this means a cable with at least a ground, Tx, and Rx conductors wired correctly. Depending on the device and style of connectors, you may have to cross over the Tx & Rx pins. You haven't stated what you do know about the required cabling, so I leave it to you to confirm that you know it is cabled correctly, or find out from documentation for the device.
You can verify that the serial port transmits and receives by looping the Tx pin back onto the Rx pin. In almost all cases this means jumpering pin 2 to pin 3 of the serial port. Having done this, start up a terminal emulator such as minicom (or C-Kermit, which I prefer), and when in 'connected' mode, type some keystrokes. The sent data should be echoed back through the connector & cable, and appear as incoming data. Seeing this happen confirms that the serial port and driver are working. You can use a short piece of wire, paper clip, screwdriver tip, or whatever to short the two pins for this test. It should go without saying that you need to use the correct connector on each device, but more than one person has used the wrong one. Don't ask me how I know this.
Having verified that the serial port, driver, and cable are correct, you will then need to configure the serial port to use the correct communications parameters, according to the requirements or the external device with which you want to communicate. These parameters should be documented, but if not, 9600 baud, No parity, 8 data bits, and one stop bit is a very common configuration. There are a smallish number of other bit rates, and trying the faster rates first is more likely to bring success. When the bit rate is correct, you will likely start to see some recognizable communications, but possibly interlaced with garbage characters. This indicates that you need to adjust the word size and or parity settings. Again, given tha small number of possibilities, trial and error adjustment can usually home in on the correct settings.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.