You might try 19200 or 9600 for baud and none on parity and 1 stop bit, that's pretty vanilla...
john
Les Mikesell wrote:
On Mon, 2006-08-07 at 19:34 +0200, SoNicX wrote:
hello, i have wired myself a nullmodemcable to connect a small machine to my centos-ltsp-and-so-on-server. using agetty i can login fine, just a few garbage chars here and there but working is ok. now this isnt what i wanted, so i disabled agetty, made a line in syslog.conf like *.* /dev/ttyS0 and made the system produce a lockfile after syslog is started to lock that serial port. now data reaches my minicom using terminal emulator, but its garbage, looking like this: ...x.x.x@..x.x. and so on. if i do echo "somechar" > /dev/ttyS0 its the same garbage. im sure this is a quite simple thing, but i dont get it to work. do i need another terminal prog if i try to send plaintext with syslog (as it seems to me clueless as i am). do i need to manipulate syslog output somehow? i tried to fiddle around with setserial but the port should work, as they to with agetty. i hope someone on this list has experience with this, doenst seem to be too popular.
You need to set the speed and parity to match at both ends on the serial port. Agetty probably cycled through some speeds to match up or had a config file. Stty will show/change the settings but I think they revert to defaults on the last close.