Bug 11662 - wvdial created account fails with pppd modprobe error
wvdial created account fails with pppd modprobe error
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: ppp (Show other bugs)
6.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-05-25 13:18 EDT by Jim Williams
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: 2000-05-25 13:32:47 EDT
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 Jim Williams 2000-05-25 13:18:23 EDT
I just got a new 56K Modem from Creative Labs called a ModemBlaster. It is
automatically detected at the proper serial port by wvDial but when I
attempt to activate the connection I see a load of garbage in the log
window and then pppd dies. Upon reviewing /var/log/messages I see a series
of errors as follows:

modprobe: can't locate module char-major-108
pppd[9814]: The remote system is required to authenticate itself but I
pppd[9814]: couldn't find any secret (password) which would let it use an
IP address.

Not sure whats causing this but I know that locate can't find ANY
char-major-108 anywhere on system. Does it need to be aliased in
conf.modules?

Thanks for Help
Comment 1 Nalin Dahyabhai 2000-05-25 13:32:59 EDT
The modprobe message isn't an error; pppd supports features in the 2.3 series of
kernels, and that's the message you'll see when it tests for those features and
finds that they're not there.

Please get the initscripts update from http://www.redhat.com/errata/, which will
fix the second message.  The quick workaround is to add "noauth" to your
/etc/ppp/options file.

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