How are serial ports identified in 11.1? I have been unable to find anything in Yast that I can recognise as representing the serial ports on my PC consequently how can you make applications in 11.1 read the serial ports?
Have been attempting to communicate with a Garmin Etrex GPS Personal Navigator using Gpsmap and Qlandkarte both of which fail telling me they cannot open the relevant serial port. I have tried using a USB to serial cable which is identified correctly in Yast/Hardware/Hardware Information but the serial port fails to open.
I have also tried a straight serial cable to COMM2 which fails also but am unable to find any kind of notification as to how, or if, it is recognised.
Communication works perfectly in MS Windows XP with either cable.
Please can anyone help?
merkland wrote:
> How are serial ports identified in 11.1?
In suse and the rest of linux distributions, check for the boot messages:
stthpc:~ # cat /var/log/boot.msg | grep serial
<6>serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
<6>serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
doneConfiguring serial ports…
Configured serial ports
That says I’ve got 2 serial ports: a COM1 under /dev/ttysS0 and COM2
under /dev/ttyS1.
If you are getting error messages about “connection to port failure”, maybe
is because you have to configure first where is the com port located.
Greetings,
–
Camaleón
Camaleon,
Thank you for your reply.
I am really struggling with this problem as I have never been able to understand using the command line and at my age I am never likely to,however I can usually work in windows without any major problem.
I had a look at /var/log/boot.msg and these are the lines relating to the serial ports:
<6>Serial: 8250/16550 driver8 ports, IRQ sharing enabled
<6>serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
<6>serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
<6>00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
<6>00:0a: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
you can see it is more or less the same as yours - there are no error messages.
The message I get from both programs is “unable to open serial port /dev/ttyS1” or “unable to open serial port /dev/ttyUSB0” depending on which cable I use.
So what do I have to do to get things working? !!
merkland.
merkland wrote:
> Camaleon,
>
> Thank you for your reply.
> I am really struggling with this problem as I have never been able to
> understand using the command line and at my age I am never likely
> to,however I can usually work in windows without any major problem.
> I had a look at /var/log/boot.msg and these are the lines relating to
> the serial ports:
> <6>Serial: 8250/16550 driver8 ports, IRQ sharing enabled
> <6>serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> <6>serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
> <6>00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> <6>00:0a: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
>
> you can see it is more or less the same as yours - there are no error
> messages.
You it seems you also have 2 serial ports on the computer. Nice.
> The message I get from both programs is “unable to open serial port
> /dev/ttyS1” or “unable to open serial port /dev/ttyUSB0” depending on
> which cable I use.
> So what do I have to do to get things working? !!
First, take a look into the docs of the program you are using so you can
find more information about the correct setup. For instance, Gpsylon says
here that it can only work with pure serial ports, so if using usb you will
need a symlink to the device.
Supported GPS Devices
http://www.tegmento.org/gpsylon/#supported_devices
Linux users please note: serial ports must be like /dev/ttySXX, as otherwise
rxtx does not recognize the port. So for bluetooth or USB devices, a
symlink is needed!
So discard (for now) the usb adapter and use the serial one, that way you
won’t need to make a symlink.
Also, after running the program (it seems is java based) run “dmesg” to
watch what is going on.
Besides that, you can also try to run the application as the “root” user, to
discard any permission problem you may be facing with serial ports.
Greetings,
–
Camaleón
For me, the issue turned out to be permissions, I’m using putty for serial port connections and had to login as su.
Thanks so much for the suggestions Camaleon.