Jim
Have you got any results for this? - it maybe somethings sitting on it and
you can kill that process - at least to prove it works, then move onto
sorting out the problem with whatever is sitting on tyS0

73s
Dave
G0CER

2008/8/10 Dave H <[EMAIL PROTECTED]>

> I don't want to confuse things - but would you try this to show if anything
> is sitting on ttyS0 (it might be something you ran earlier.
>
> From a terminal screen type this and enter..
>
> sudo  ps -aux | grep ttyS0
>
> there should be a list - perhaps copy and paste that into a message
> (ignore the 'warning' about'bad ps syntax')
>
> Dave
> G0CER
>
> 2008/8/10 Jim Morgan <[EMAIL PROTECTED]>
>
>
>>
>> > Ok I loaded Gtkterm fired it up and I get this error message
>> > "Cannot open /dev/ttyS0: Device or resource busy."
>> > So the question now is how do I find out what is making the
>> > port busy and how do I turn it off?
>>
>>
>> I bet there's a serial getty sitting on the port right now for a serial
>> console.  Look inside a file called /etc/inittab for the serial port.  You
>> can
>> do it this way:
>>
>> grep ttyS0 /etc/inittab
>>
>> If it comes back with a line that doesn't have a # in front, that's
>> probably
>> part of the problem.
>>
>>
>>
>> >>>I come back with nothing:
>>
>> [EMAIL PROTECTED]:~$ grep ttyS0 /etc/inittab
>> grep: /etc/inittab: No such file or directory
>> [EMAIL PROTECTED]:~$ cd /root
>> [EMAIL PROTECTED]:/root$ sudo grep ttyS0 /etc/inittab
>> [sudo] password for jim:
>> grep: /etc/inittab: No such file or directory
>> [EMAIL PROTECTED]:/root$
>>
>> Jim Morgan KE5MKT
>>
>>
>>
>>
>> _______________________________________________
>> Xastir mailing list
>> [email protected]
>> http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
>>
>
>
>
> --
> Dave
> G0CER
> (also G6VSG)
> http://www.eQSL.cc/Member.cfm?G0CER
>



-- 
Dave
G0CER
(also G6VSG)
http://www.eQSL.cc/Member.cfm?G0CER
_______________________________________________
Xastir mailing list
[email protected]
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

Reply via email to