/dev/pilot does not exist
Timothy Payne
tim at tmpco.com
Sun Jul 11 05:11:08 UTC 2004
On Sat, 2004-07-10 at 12:46, fedora wrote:
> Situation-
> /dev/pilot does not exist
>
> What I am trying to do-
> sync palm Vx with Evolution1.4 on fc2
>
> Spec
> Palm Vx OS_3.5 after hard reset
> Serial cradle connected
> Evolution 1.4 never been synced before
>
> What I have tried...after Googling and fedora archive-
>
> 1_ originally I thought it was permissions
> [root at blue root]# chmod 0666 /dev/pilot
> chmod: cannot access `/dev/pilot': No such file or directory
>
> and
>
> [root at blue root]# pilot-xfer -p /dev/pilot -l
>
> The device /dev/pilot does not exist..
> Possible solution:
>
> mknod /dev/pilot c <major> <minor>
>
> Unable to bind to port: /dev/pilot
> Please use --help for more information
>
>
> 2_Well, I know ttyS0 and ttyS1 do exist...
>
> [root at blue root]# setserial -g /dev/ttyS[0-4]
> /dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4
> /dev/ttyS1, UART: 16550A, Port: 0x02f8, IRQ: 3
> /dev/ttyS2, UART: unknown, Port: 0x03e8, IRQ: 4
> /dev/ttyS3, UART: unknown, Port: 0x02e8, IRQ: 3
> /dev/ttyS4, UART: unknown, Port: 0x0000, IRQ: 0
>
> ?Advice please..
> Should I make a soft link between ttyS0 and /dev/pilot...?
>
> or something with mknod? I did a man mknod, but do not understand what
> should be done.
>
> tia
> chris
>
> --
> Certified Microsoft-free e-mail.
I just changed pilot device to /dev/ttyS0 and it worked, so far it's the
only thing on the port so no problems.
Tim...
More information about the fedora-list
mailing list