Bug 6523

Summary:	problems communicating to external modem
Product:	[Retired] Red Hat Linux	Reporter:	rhopkins
Component:	setserial	Assignee:	Tim Waugh <twaugh>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1	CC:	herscheld
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	1999-11-26 04:12:36 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description rhopkins 1999-10-30 04:38:28 UTC

I've been running RH 5.0, 5.1, 5.2, and 6.0, and i have
never had any problems with it and my Zoom 56K data/fax
external modem.  Instead of simply upgrading to 6.1 on my
box, i wiped my drives and installed it fresh, and now i
can't get my modem to work at all.  After checking around
some, I noticed that there wasn't a rc.serial file in
the /etc/rc.d directory.  I simply copied the the file from
the setserial doumentation files, set it up according to
the docs, and still nothing.  What else can i do?  I
haven't tried to recompile a kernel yet though, I don't
want to do that except as a last resort.  Maybe something
fishy in the stock kernel??  i did notice on boot that it
reports the serial devices as /dev/ttyS00 and /dev/ttyS01,
instead of ttyS0 ans ttyS1.  i'm not a kernel whiz though.
contact me if ya need more info.

Comment 1 rhopkins 1999-11-26 04:12:59 UTC

Ok i got my modem to work, it was one of those slap the forehead and go duh!
mistakes.  For some reason, i had my modem connected to my /dev/ttys1 (com 2)
port, so i set /dev/modem to that and i can actually do something with my modem
now.  Wierd thing is though is that I had set /dev/modem to ttys0 in RH60 and
it worked there. I have come across another problem though.  When i try to dial
out using ppp, it hangs right when wvdial or chat scripts send the ATDT line to
the modem.  Now i know the modem works because i can properly dial out with it
to my ISP using mimicom.  Should i file another bug report on this?

Comment 2 David Lawrence 2000-08-08 15:35:58 UTC

Please file another report for his problem against wvdial if this problem still
persists in 6.2.