Bug 7179

Summary:	Robotics 56k is not detected
Product:	[Retired] Red Hat Linux	Reporter:	jd <donnelly>
Component:	dev	Assignee:	Michael K. Johnson <johnsonm>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1
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-22 18:29:39 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description jd 1999-11-20 16:22:08 UTC

On a new installation of 6.1 , a robotics V.90, 56k modem
 configured as "com 5" was not recognized or installed during
 the install/ppp process.

 in fact, ppp dialup utility  seems to always default to
 /dev/ttyS0 .

 the fix:

 determine the modem settings:

 less /proc/pci    "find modem", look at /etc/sysconfig/hwconfig for hints

  run:

   setserial /dev/ttyS0 uart 16650A port <io-addr> irq <irq#>

   ln  /dev/modem /dev/ttyS0

  run minicom to test

Comment 1 Michael K. Johnson 1999-11-22 18:29:59 UTC

The Linux kernel, by default, only scans the first 4 serial ports.
To scan more, you have to use the setserial program, as you show
in this report.

rp3 only defaults to ttyS0 if it can't find a modem on the first
4 ports and whatever /dev/modem points to.

Comment 2 jd 1999-11-22 19:18:59 UTC

I still think it is a  bug. I figured it out cause I'm
 already a unix hack. A novice user would have never
 found it. If we want to kick MS ass with linux, we
 can't ignore these annoying problems with "it's not
 a problem " attitude !

 BTW - winshit 98 found it !