Bug 7179 - Robotics 56k is not detected
Robotics 56k is not detected
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: dev (Show other bugs)
6.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-11-20 11:22 EST by jd
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-11-22 13:29:39 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description jd 1999-11-20 11:22:08 EST
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 13:29:59 EST
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 14:18:59 EST
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 !

Note You need to log in before you can comment on or make changes to this bug.