Linux-kernel mailing list archive 1998-48,: pre-patch-2.1.131-3.gz still breaks 38400 baud to /dev/ttyS0

# pre-patch-2.1.131-3.gz still breaks 38400 baud to /dev/ttyS0

David Dyck (dcd@tc.fluke.com)
Wed, 2 Dec 1998 13:02:05 -0800 (PST)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Alan Cox: "Re: lynx <-> linux tcp suckage."
- Previous message: Oren Laadan: "[BUG] arp replies with BOOTP (nfsroot)"

pre-patch-2.1.131-3.gz still breaks 38400 baud to /dev/ttyS[01]

Actually this seems to have been broken since 2.1.127 or so, I
think 2.1.125 is the last version that worked at 38400 ....

crw-rw-rw- 1 root tty 4, 64 Jul 17 1994 /dev/ttyS0
crw-rw-rw- 1 root tty 4, 65 Nov 4 12:31 /dev/ttyS1

Using C-Kermit 6.0.192, 6 Sep 96, for Linux,
I can communicate to /dev/ttyS1 at 19200 correctly, but
when I attempt to connect at 38400 using the following command
line I get an error "?unsupported transmission rate"

$ ./wermit -Y -l /dev/ttyS1 -b 38400 -c

?unsupported transmission rate

Once this happens, I can no longer connect even at 19200 as I get
the error "?can't open device"

dd:ckermit$ ./wermit -Y -l /dev/ttyS1 -b 19200 -c

?can't open device

Testing with the command "stty 38400 </dev/ttyS0" earlier
seemed to work, but after this mishap with kermit and 38400,
then bash reports "bash: /dev/ttyS0: Device or resource busy"
when attempting even "stty < /dev/ttyS0"

I've looked throught the archives but haven't seen any hints or help.

If it helps, here's the stuff I have in my .config
(e.g. grep '=[ym]' .config)

CONFIG_EXPERIMENTAL=y
CONFIG_M586=y
CONFIG_MTRR=y
CONFIG_MODULES=y
CONFIG_KMOD=y
CONFIG_NET=y
CONFIG_PCI=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_QUIRKS=y
CONFIG_PCI_OLD_PROC=y
CONFIG_SYSVIPC=y
CONFIG_SYSCTL=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_CMD640=y
CONFIG_BLK_DEV_RZ1000=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_AUTO=y
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_RAM=m
CONFIG_PARIDE_PARPORT=y
CONFIG_PACKET=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_NOSR=y
CONFIG_SKB_LARGE=y
CONFIG_SCSI=y
CONFIG_BLK_DEV_SD=y
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_CONSTANTS=y
CONFIG_SCSI_LOGGING=y
CONFIG_SCSI_PPA=m
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
CONFIG_NET_ETHERNET=y
CONFIG_NET_VENDOR_3COM=y
CONFIG_EL3=y
CONFIG_VORTEX=m
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=y
CONFIG_SERIAL_NONSTANDARD=y
CONFIG_CYCLADES=m
CONFIG_UNIX98_PTYS=y
CONFIG_MOUSE=y
CONFIG_PSMOUSE=y
CONFIG_RTC=y
CONFIG_NVRAM=m
CONFIG_MINIX_FS=m
CONFIG_EXT2_FS=y
CONFIG_ISO9660_FS=y
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_PROC_FS=y
CONFIG_NFS_FS=y
CONFIG_NFSD=y
CONFIG_SUNRPC=y
CONFIG_LOCKD=y
CONFIG_SMB_FS=m
CONFIG_AUTOFS_FS=y
CONFIG_DEVPTS_FS=y
CONFIG_NLS=y
CONFIG_NLS_CODEPAGE_437=m
CONFIG_NLS_ISO8859_1=m
CONFIG_VGA_CONSOLE=y
CONFIG_VIDEO_SELECT=y
CONFIG_SOUND=m
CONFIG_SOUND_OSS=m
CONFIG_SOUND_SB=m
CONFIG_SOUND_ADLIB=m
CONFIG_SOUND_CS4232=m
CONFIG_SOUND_OPL3SA2=m
CONFIG_SOUND_OPL3SA1=m
CONFIG_SOUND_SOFTOSS=m
CONFIG_SOUND_YM3812=m
CONFIG_SOUND_VMIDI=m

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

- Next message: Alan Cox: "Re: lynx <-> linux tcp suckage."
- Previous message: Oren Laadan: "[BUG] arp replies with BOOTP (nfsroot)"