Re: [SLE] Problems with serial port/suse 8
On Monday 30 September 2002 08:12, you wrote:
What software are you using and what port are you connected to/have the software configured to talk to?
Palm 105 is the hardware. It's plugged via its serial cable, into the serial port. Jpilot is pointing at ttys0 and is telling me this: pi_bind Invalid argument Check your serial port and settings exiting with status -10 Because of the below and the above; I would like to make sure that the /etc/fstab entry it is looking for is properly formatted. A light dawns. In preferences of Jpilot it says that it points at /dev/ttys0 fstab /dev/pilot but there is no fstab entry resembling that. Can I just do /dev/ttys00 /dev/pilot auto rw,noauto,user,exec 0 0 or something like that?
Also, look at the "dmesg" info and see if you see anything about serialport initialization...
Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI SERIAL_ACPI enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A IN reply to Jasko: In "/var/log/messages" what do You see when You try to communicate with palm? Nada. Run "dir /dev/ttyS*", and have a look at access rights (owner, group and rw-access). I have crw-rw---- root, uucp on my computer. Me too. You should at least belong to group uucp to be able to access the serial port. I do!
- Herman
Nick Selby wrote:
Since no one seemed to notice this one let me clarify. My machine is an HP Pavillion 5270 running Suse 8. I'm trying to get the serial port to talk to my palm device.
On Sunday 29 September 2002 12:20, Nick Selby wrote:
Hi, I have tried plugging my palm into the port (the palm works, as they always say, under a windows machine (a different one, not on this box)) and it is not recognized. I went into hwinfo and don't see the port listed. Perhaps that was a stupid place to look but it's where I looked...
Can anyone give me some ideas about how to tell (a) if the port is working and (b) to troubleshoot the connection process?
Thanks in advance, Nick
-- ---------------------------- Nick Selby
US Mobile: +1 646 334 3649 *Currently in: US - Itinerary available at
http://guidebookwriters.com/authors/itinerary.htm#nick
*
-------------------------------------------------------
Hi I tried with jpilot (installed from CD), and it did work, except it does not talk Compaq... So I believe it must be some change that You have made after SuSE installation... The error points, that jpilot is not able to use the serial port correctly. Are You able to open "minicom", set it up for ttyS0 (com1), and are You able to see anything coming up when firing pilots' coms up? Jaska. On Monday 30 September 2002 11:45, Nick Selby wrote:
On Monday 30 September 2002 08:12, you wrote:
What software are you using and what port are you connected to/have the software configured to talk to?
Palm 105 is the hardware. It's plugged via its serial cable, into the serial port. Jpilot is pointing at ttys0 and is telling me this:
pi_bind Invalid argument Check your serial port and settings exiting with status -10
The problem was as simple as a sim link; thanks to Gerhard Siegesmund on the Jpilot list I did: ln -s /dev/ttyS0 /dev/pilot which was what the Jpilot wanted to see. They synced up immediately. Thanks, nick
You can also point Jpilot directly at ttyS0 which I did. :) * Nick Selby (php@nickselby.com) [021001 03:18]: ::The problem was as simple as a sim link; thanks to Gerhard Siegesmund on the ::Jpilot list I did: :: :: ln -s /dev/ttyS0 /dev/pilot :: ::which was what the Jpilot wanted to see. They synced up immediately. -- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org Tell me what you believe.. I tell you what you should see.
participants (3)
-
Ben Rosenberg
-
jaakko tamminen
-
Nick Selby