UUCP/serial fails after upgrading to 2.0.27<ELF>

UUCP/serial fails after upgrading to 2.0.27<ELF>

Post by Thor Farri » Wed, 18 Dec 1996 04:00:00



Hi.  I posted some time ago about a problem with
UUCP getting "Line Disconnected" when trying to dial out.
I took the plunge and upgraded my system from 1.2.13
(slackware) to 2.0.27  I also rev'd gcc to 2.7.2, and
UUCP to 1.05

Now, I can't do much of anything with my serial ports. /dev/cua0
is used for my dedicated slip connection to my ISP.  This
continues to work without a problem (a USR 33.6 sportster
connected).  cu, uucico and minicom all fail on /dev/cua1
and /dev/cua2 (a Zoom 33.6 and USR 28.8 sporters, repsectively).
The errors I get from cu are: "cu: open: (/dev/cua1) Permission
denied".  The errors I get from uucico (in /var/spool/uucp/.Log/
uucico/ANY) are: "FATAL: open (/dev/null) Permission denied".
Minicom simply opens the ports and sits there, with no error
message, and no <apparent> connection with the modem: "AT"
commands produce no response.

I have disabled slip, and tried "cu" and "uucico" on the
known good port of /dev/cua0 --- they fail there as they
fail on /dev/cua1 and /dev/cua2.  All permissions in dev
are the same.

uugetty fails on /dev/cua1 (as does agetty).  IN /var/adm/debug
I find the fillowing conversation:
uugetty[x]: D_INIT: opening line /dev/ttyS1
uugetty[x]: D_INIT: opening init line: /dev/ttyS1
uugetty[x]: D_INIT: initializing line
uugetty[x]: D_INIT: chat("" ATZ\r OK) called
uugetty[x]: D_INIT: EXPECT: ([nothing])
uugetty[x[: D_INIT: SEND: (A) -- Failed: I/O error
uugetty[x]: D_INIT: init failed... aborting

Any help or suggestions would be appreciated.  I am really
lost, and have found no real answers/source/oracle for
hints, places to look, etc.

Thanks in advance.....
-Thor-

 
 
 

UUCP/serial fails after upgrading to 2.0.27<ELF>

Post by Daniel Sawye » Wed, 18 Dec 1996 04:00:00


Hello, I also am having trouble with 2.0.x kernel and serial ports. The
ports seem to be unknown outside of the /dev directory. I don't know if
this is the same problem. What has changed that would make the ports
unknown?

BTW: PPP continues to mostly work.

Thanks is advance.

Dan

 
 
 

UUCP/serial fails after upgrading to 2.0.27<ELF>

Post by bill davids » Thu, 19 Dec 1996 04:00:00


| Hi.  I posted some time ago about a problem with
| UUCP getting "Line Disconnected" when trying to dial out.
| I took the plunge and upgraded my system from 1.2.13
| (slackware) to 2.0.27  I also rev'd gcc to 2.7.2, and
| UUCP to 1.05

Did you install a new Slackware version or follow all the changes in
the "Changes" document? Done both, like the total upgrade better. If
you did the hand upgrade you may have missed something.
--

  What do you mean I shouldn't do thing like that at my age?
  At my age if you don't do things like that you might die of natural causes!

 
 
 

1. <><><> MOUNTING EXTENDED PARTITION <><><>

I have a 10 GB UDMA IDE drive formatted with Windows.  The first partition
is FAT32, and the second is NTFS.  I can successfully mount the first, but
not the second.  Any ideas?

Suse 7.2 on i86
the drive is mounted on /dev/hdc, and I CAN see hda1, but not hda2

2. Linux on PPC 823 ?

3. Wanted: <><><> Unix Specialist <><><>

4. Printer Cable

5. LILO help <><><><><><>

6. KDE Apps Compile Error

7. >>> System hangs after upgrading to kernel 2.0 <<<

8. network hang after a port scan attack -- need references

9. >>>INFO ON COMPATIBLE DIGIBOARD SERIAL PORTS NEEDED<<<

10. Relaying fails after 2.0.27--> 2.0.34 upgrade

11. A <= ping => B => OK A <= TCP => B => FAILS

12. <Alt>+<key> = <Esc><key> ?

13. *{<><>}*Linux*Screen*Difficulties*{<><>}*