I think Owain is on to something here...
[we...@desktop] $ cu -l /dev/tty01
/dev/tty01: Device not configured
link down
[we...@desktop] $ cu -l /dev/tty00
can't open log file /var/log/aculog.
Connected
You don't seem to have a /dev/tty01 device. Check that you
a) actually have the device
b) it has the correct device major/minor and type
c) you don't have a "special" kernel without the driver
d) your BIOS has COM2 disabled
e) another reason is preventing the kernel from knowing about this
device
I'm really hoping you're not mistakenly assuming COM1 to be /dev/tty01
(COM1 is tty00). Most of these problems would've been easily
identified had you sent your dmesg along in the first post...
Paul 'WEiRD' de Weerd
On Thu, Jul 15, 2010 at 07:23:21AM -0600, fred wrote:
| I am sure the cable is ok. The response from tip is:
| /dev/tty01: Device not configured
| link down
|
| I connected a dumb terminal to the port to see if it expects a modem
| to respond but this is not the case.
|
| I tried: echo "this is the time" >/dev/tty01
| ksh: cannot create /dev/tty01: Device not configured
|
| Before I added the user to the Dialer group, tip and the port would
| work for root but it does not work for root now. Maybe it is time
| for a reboot.
|
|
|
| Nicholas Marriott wrote:
| >cua doesn't wait for handshaking, so it may work.
| >
| >
| >On Tue, Jul 13, 2010 at 11:51:35AM -0600, fred wrote:
| >>The response now is that the link is down. The cable only uses rxd,
| >>txd and sg. The others are all tied together. The Sun has at least
| >>one signal pulling the others high but the pc does not. I need to
| >>add another wire to pull the handshake inputs high but won't have
| >>time for that until late tonight.
| >>
| >>Fred
| >>
| >>Nicholas Marriott wrote:
| >>>And what is the response now?
| >>>
| >>>You should be using cua01 not tty01.
| >>>
| >>>
| >>>On Tue, Jul 13, 2010 at 06:47:18AM -0600, fred wrote:
| >>>>I restored the dialer group to /dev/tty01 and added the user to the
| >>>>dialer group as Nick suggested. It still doesn't work but the
| >>>>response is different now. I believe there is a cable problem now.
| >>>>The cable works with a Sun Ultra 10 but not with the PC running
| >>>>openbsd.
| >>>>
| >>>>Thank you for the help.
| >>>>
| >>>>Nick Holland wrote:
| >>>>>On 07/12/10 19:32, patrick keshishian wrote:
| >>>>>>On Mon, Jul 12, 2010 at 2:58 PM, fred <[email protected]> wrote:
| >>>>>>>Hello,
| >>>>>>>
| >>>>>>>A user needs to connect to external equipment using tip and a serial
port.
| >>>>>>>
| >>>>>>>I created an /etc/remote file:
| >>>>>>>snake:br=9600:dv=/dev/tty01:hf:nb:pa=none
| >>>>>>>
| >>>>>>>The group associated with /dev/tty01 was changed from dialer to one
that
| >>>>>>>includes the user:
| >>>>>>>$ls -l /dev/tty01
| >>>>>>>crw-rw---- 1 uucp wheel 8, 1 Feb 7 09:38 /dev/tty01
| >>>>>>so, the user is already in wheel group. Revert above change. Enable
| >>>>>>sudo (if not already done so) for users in group wheel.
| >>>>>>
| >>>>>>$ sudo -u uucp tip snake
| >>>>>>
| >>>>>>--patrick
| >>>>>uh...if all else fails, do it as root? I think we'd prefer to avoid
| >>>>>that, unless really a root-like activity.
| >>>>>
| >>>>>The "dialer" group is set up just for this purpose.
| >>>>>
| >>>>>The problem with changing the ownership (or group) of a device file is
| >>>>>the next upgrade will overwrite your ownership change. Ask me how I
| >>>>>know. Better idea, don't -- just use your imagination.
| >>>>>
| >>>>>I'm not sure why you didn't just add that user to group "dialer", but it
| >>>>>is quite straight forward:
| >>>>>
| >>>>>/home/nick $ grep nick /etc/group
| >>>>>wheel:*:0:root,nick
| >>>>>wsrc:*:9:nick
| >>>>>dialer:*:117:nick
| >>>>>nick:*:1000:
| >>>>>
| >>>>>and...I (as "nick") have no trouble using my serial port without using
| >>>>>sudo and without changing device file ownership.
| >>>>>
| >>>>>You will probably want to create a file /var/log/aculog which is
| >>>>>writable by group "dialer", as well... Squishes an error message, and
| >>>>>provides some useful logging, too.
| >>>>>
| >>>>>Nick.
|
--
>++++++++[<++++++++++>-]<+++++++.>+++[<------>-]<.>+++[<+
+++++++++++>-]<.>++[<------------>-]<+.--------------.[-]
http://www.weirdnet.nl/
