Mailinglist Archive: opensuse (2162 mails)

< Previous Next >
Re: [opensuse] Long standing serial port issue in openSuse
  • From: Roger Oberholtzer <roger@xxxxxx>
  • Date: Wed, 27 Aug 2008 14:27:59 +0200
  • Message-id: <1219840080.5345.106.camel@xxxxxxxxxxxx>
On Wed, 2008-08-27 at 14:00 +0200, Per Jessen wrote:
Roger Oberholtzer wrote:

we have two applications that both read/write to/from a serial port.
One application reads temperature measurements and writes commands,
the other is a standard NTP reading a DCF77 signal from the serial
port. The first application is on SUSE 9.0, the second is on openSUSE
10.2. They've both been running for a couple of years, and neither
have ever showed any problems.

OOC, do you run X on these systems?


Nope, no X.

We run X. The GPS is recorded as part of a measurement in a moving
vehicle, and it can steer location info during data collection.

Maybe the X server is part of my problem. (Of course, I do not want to
rule out anything else.) I remember back when you had to restart X if
you added an input device. If it was not found at X's start, it was not
available. More recently, X finds these devices as they are available.
Which is really nice. Does X ever re-check the serial ports after it
starts? In my use, X is never restarted when this problem occurs.

Or maybe it is something in how /dev/input/mice is implemented. What
does it consider to be a potential mouse?

--
Roger Oberholtzer

OPQ Systems / Ramböll RST

Ramböll Sverige AB
Kapellgränd 7
P.O. Box 4205
SE-102 65 Stockholm, Sweden

Office: Int +46 8-615 60 20
Mobile: Int +46 70-815 1696

And remember:

It is RSofT and there is always something under construction.
It is like talking about large city with all constructions finished.
Not impossible, but very unlikely.


--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups