/dev/ttySx problems... solved

Gene Heskett gene.heskett at verizon.net
Fri Nov 10 14:28:27 UTC 2006


On Friday 10 November 2006 06:59, stan mcintosh wrote:
>Gene Heskett wrote:
>> selinux is set permissive, and an ls -l of /dev/ttyS* show this:
>>
>> crw-rw---- 1 root uucp 4, 64 Nov  9 16:35 /dev/ttyS0
>> crw------- 1 root root 4, 65 Nov  9 16:35 /dev/ttyS1
>> crw------- 1 root root 4, 66 Nov  9 16:35 /dev/ttyS2
>> crw------- 1 root root 4, 67 Nov  9 16:35 /dev/ttyS3
>
>Cool use of your serial port.  Have you gone into your /dev directory
>and 'chmod o+rw ttyS*' as root?
>
>If this is too much of a noob approach, then I'm busted ;>)
>
>My privileges are:
>[root at localhost dev]# ls -l ttyS*
>crw-rw-rw- 1 root uucp 4, 64 Nov  9 19:29 ttyS0
>crw-rw-rw- 1 root uucp 4, 65 Nov  9 19:31 ttyS1
>crw-rw-rw- 1 root uucp 4, 66 Nov  9 14:13 ttyS2
>crw-rw-rw- 1 root uucp 4, 67 Nov  9 14:13 ttyS3
>
>Regards,
>stan

Ok, tried that, got this:
[root at coyote dev]# ls -l ttyS*
crw-rw-rw- 1 root uucp 4, 64 Nov  9 16:35 ttyS0
crw----rw- 1 root root 4, 65 Nov  9 16:35 ttyS1
crw----rw- 1 root root 4, 66 Nov  9 16:35 ttyS2
crw----rw- 1 root root 4, 67 Nov  9 16:35 ttyS3

So then I run my daytime script:

[root at coyote dev]# its-daylight

And which generates this in the heyu.log:
-----
Fri Nov 10 09:13:08 EST 2006 my name is /root/bin/its-daylight
Fri Nov 10 09:13:08 EST 2006: its-daylight:doing a killall xtend
xtend: no process killed
heyu: no process killed
Fri Nov 10 09:13:09 EST 2006: heyu-restart: sleep done now doing a heyu 
setclock

HEYU: Can't open tty line.  Check the permissions.

Fri Nov 10 09:13:13 EST 2006: heyu-restart: now restarting the heyu monitor
Fri Nov 10 09:13:13 EST 2006: heyu-restart all done - exiting
Fri Nov 10 09:13:13 EST 2006: its-daylight:heyu-restart completed

HEYU: Can't open tty line.  Check the permissions.

Fri Nov 10 09:13:16 EST 2006: its-daylight:Changing to /etc/.xtendrc-day
Fri Nov 10 09:13:17 EST 2006: its-daylight: heyu turn off a14

HEYU: Can't open tty line.  Check the permissions.

Fri Nov 10 09:13:20 EST 2006: its-daylight:executing xtend -f /etc/.xtendrc
Fri Nov 10 09:13:20 EST 2006: its-daylight:xtend running with daytime 
config
Fri Nov 10 09:13:20 EST 2006: its-daylight: cd /root/bin
Fri Nov 10 09:13:20 EST 2006: its-daylight:removing the link heyu-now

Couldn't open Heyu spool file: No such file or directory
Couldn't fcntl x10: Bad file descriptor

# these last two are normal when its not running. The output file from 
# the 'heyu monitor' function doesn't exist because heyu couldn't access 
# the port and exited.

Fri Nov 10 09:13:21 EST 2006: its-daylight:set heyu-now link to myself so I 
will run on a reboot
Fri Nov 10 09:13:21 EST 2006: its-daylight script has completed
------

I do all sorts of funky things with links so I always call the current 
setup on a reboot.

On the odd chance, I did this:
[root at coyote dev]# lsof | grep ttyS
[root at coyote dev]#

so nothing has them tied up. Then a setserial /dev/ttyS0:
[root at coyote dev]# setserial /dev/ttyS0
Cannot get serial info: Invalid argument
And
[root at coyote dev]# setserial /dev/ttyS1
/dev/ttyS1: No such device or address

But as you can see, it does exist, the cm11a is still plugged into it etc 
etc.

I am beginning to think we have a buglet in this kernel.  Since I'm running 
the latest 2.6.19-rc5 on the FC2 install on the /dev/hdb drive, I'll copy 
that vmlinuz and initrd to this boot partition, and edit the grub.conf to 
use it for my next test sometime today.  If it then works, I'll bugzilla 
it.

Thanks.

-- 
Cheers, Gene




More information about the users mailing list