Messages in this thread | | | Date | Fri, 6 Mar 1998 15:15:21 -0500 (EST) | From | "Richard B. Johnson" <> | Subject | Re: cua2/ttyS2 problems |
| |
On Fri, 6 Mar 1998 hemsleyr@keyline.co.uk wrote:
> I'm still having trouble with getting access to /dev/cua2 / /dev/ttyS2 > in 2.1.88 > > Thanks to those who suggested using /dev/ttyS2 instead of cua2, but > still no joy. > > Device is busy ? > > I don't understand why. > Where does this message come from, when there's no LCK.. files in > /var/lock ? If I know how the kernel determines if a device is 'busy', I > might be able to dig deeper. > > Rebooting to 2.0.33 isn't really fun, when I dial work every hour. > > Cheers, > Rik
Make sure that a 'getty' doesn't own it. Look in /etc/inittab # # inittab This file describes how the INIT process should set up # the system in a certain run-level. [SNIPPED]
# Serial lines ##########s1:45:respawn:/sbin/agetty -T vt100 ttyS0 9600 #s1:45:respawn:/sbin/agetty 19200 cua1 #s1:45:respawn:/sbin/agetty 19200 ttyS1
# Dialup lines #d1:45:respawn:/sbin/agetty -m -t60 38400,19200,9600,2400,1200 ttyS0 ####d2:45:respawn:/sbin/agetty -m -t60 38400,19200,9600,2400,1200 ttyS0
# Serial lines #s1:45:respawn:/sbin/agetty 19200 ttyS0 vt100 #s2:45:respawn:/sbin/agetty 19200 ttyS1 vt100
# Dialup lines #d1:45:respawn:/sbin/agetty -mt60 38400,19200,9600,2400,1200 ttyS0 vt100 #d2:45:respawn:/sbin/agetty -mt60 38400,19200,9600,2400,1200 ttyS1 vt100
Cheers, Dick Johnson ***** FILE SYSTEM MODIFIED ***** Penguin : Linux version 2.1.87 on an i586 machine (66.15 BogoMips). Warning : It's hard to remain at the trailing edge of technology.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |