[Xastir] Xastir on Mepis - ttyS0 hard fail

[Gale Wilkinson]

I have been doing some more researching and digging and am beginning to
suspect it might be some kind of hardware problem.  After really
watching the boot process closely I see that I am getting a "LSR safety
lock engaged" message for the ttyS* listings.  And if I am reading this
right this means that Linux is unhappy with my serial port for some
reason.  One thing I had not mentioned and probably should have is that
this is a IBM ThinkPad 570E laptop which is dual booting with Win2k. 
Windoze seems to have no problem with the serial port (I have ran
UI-View with a KPC-3 with no problems so unless something has changed
since the last time I tried UI-View under windoze it must be something
about the uart itself.  Though I did run setserial and if I read it
right it appears to thing the uart is ok?  I will list what it says
below in case it means more to you than to me (not hard at this point!).

setserial -av /dev/ttyS0
/dev/ttyS0, Line 0, UART: 16550A, PORT: Ox03f8, IRQ:4
        Baud_base: 115200, close_delay: 50, divisor: 0
        closing_wait: 3000
        Flags:  spd_normal  skip_test

  I will try to call you around 20:00 my time and see what we can come
up with.

     Gale

On Sun, 2004-02-08 at 17:12, James Washer wrote:
> Feel free to call me this eveing  877 834 8781, and we can figure out what is going on here. I'll be in and out, so you might have to try a couple of times.. or leave you number and I'll call you.. 
> 
>  - jim
> 
> p.s. I'm on the west coast... so if you want me to call you, let me know how late I may call.
> 
> On 08 Feb 2004 17:00:12 -0500
> Gale Wilkinson <gdwrbw at ftc-i.net> wrote:
> 
> > I checked the /var/lock directory and found that the only LCK..ttyS0
> > files were the ones generated by Xastir itself.  I did this on a full
> > reboot and then login as both a normal user and as Root.  No change in
> > either case (though the LCK file did state who I was logged in as.  I am
> > still trying to figure out what must be locking the port during the
> > initial boot process....
> > 
> >       Gale
> > 
> > 
> > On Sun, 2004-02-08 at 15:40, Curt Mills wrote:
> > > On 8 Feb 2004, Gale Wilkinson wrote:
> > > 
> > > > My next question in this case is:  Is there some nice little program
> > > > that I could use to see if/what is using ttyS0 at any given time?  I am
> > > > fairly new to Linux and am not sure how to track down what is actually
> > > > locking the port for me...
> > > 
> > > Check in /var/lock or /var/locks, perhaps your system has some other
> > > area under /var or /usr for creating lockfiles.  If you find a
> > > lockfile, check whether there is either a text string naming the
> > > program in the lockfile, or a process ID number that you can use
> > > with "ps" or "top" to determine which process opened the port.
> > > 
> > > These methods expect that whatever is using the port was nice enough
> > > to create a standard lockfile.  Not everything does this.
> > 
> > _______________________________________________
> > Xastir mailing list
> > Xastir at xastir.org
> > https://krypton.hscs.virginia.edu/mailman/listinfo/xastir
> >