Brooks Davis <brooks_at_one-eyed-alien.net> writes: > On Mon, Oct 17, 2005 at 11:48:45AM +0300, Max N. Boyarov wrote: >> >> Hello! >> >> I have strange problems after upgrading system from BETA5 to RC1. >> After upgrade i see the following messages in mgetty log and on serial console and mgetty does not work >> >> >> 10/15 18:59:04 ad1 mgetty: interim release 1.1.33-Apr10 >> 10/15 18:59:05 ad1 mod: cannot make /dev/cuad1 stdin: Bad file descriptor >> 10/15 18:59:05 ad1 open device /dev/cuad1 failed: Bad file descriptor >> 10/15 18:59:05 ad1 cannot get terminal line dev=cuad1, exiting: Bad file descriptor >> -- >> 10/15 18:59:18 ad1 mgetty: interim release 1.1.33-Apr10 >> 10/15 18:59:19 ad1 mod: cannot make /dev/cuad1 stdin: Bad file descriptor >> 10/15 18:59:19 ad1 open device /dev/cuad1 failed: Bad file descriptor >> 10/15 18:59:19 ad1 cannot get terminal line dev=cuad1, exiting: Bad file descriptor >> >> systems sources were "cvsupped" on 14/10/2005 >> and mgetty was installed from ports >> >> >> What can i do to solve this problem ? > > Do the devices in question actually exist? Mgetty appears to be > misconfigured to attempt to create them when missing which is alwasy > wrong in the devfs world. Yes, devices are present. And if i run mgetty from command line it work. I use cu to connect, and is working. ppp on this port also works. Mgetty started from /etc/ttys - does not.. Also mgetty work normal on 6.0-BETA5. I have tried to check mgetty on my laptop with ltmdm and also got this error. -- // Max N. Boyarov // 2:450/262 _at_ FidoNet
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:45 UTC