Re: login problems

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Morris,

Please send to the List, not direct to me.  At
http://linmodems.technion.ac.il read the PostInstall Howto.
I'm not under Linux now.  Do:
$ man pppd
and error messages are described near the bottom, see "Error 2"

MarvS


On Mon, Mar 16, 2009 at 12:46 PM, Morris Lee <flydog_38@xxxxxxxxx> wrote:
>   Marvin
>
> Thanks for your help.  We're making progress at least!  Tried your fix and
> it got it through the "can't open ppp-secrets" .   Had to use  chmod a+rw on
> the chap-secrets file to get it to open.  However, the ppp daemon still dies
> and disconnects.  Here's what it says:
>
> Pid of pppd: 6608
> Disconnecting at (date and time)
> The PPP daemon has died:  pppd options error (exit code = 2)
>
> BTW, my kernel is 2.6.27-11-generic.
>
> Thanks again for your help!
>
> Morris
>
> --- On Sun, 3/15/09, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote:
>
> From: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>
> Subject: Re: login problems
> To: "Morris Lee" <flydog_38@xxxxxxxxx>
> Date: Sunday, March 15, 2009, 9:33 PM
>
> Morris
>
> Known problem with fix.
>
> In case of a message like:
>    Warning: Could not modify /etc/ppp/pap-secrets: Permission denied
> see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html
>
> MarvS
>
> On Sun, Mar 15, 2009 at 7:25 PM, Morris Lee <flydog_38@xxxxxxxxx> wrote:
>>   Marvin
>>
>> First,, I'm using whatever kernel that comes with Ubuntu 8.10 (Intrepid
>> Ibex), and my modem uses an Intel driver.  I'm afraid that I'm ignorant of
>> how to call the specific information up.  I used both the slmodemd-daemon
>> and modprobed the slmodemd that was in the linmodems gz package.
>>
>> We/re making progress, but I ran into some more problems with permissions.
>> The files ppp-secrets and chap-secrets didn't open because of permission
>> violations.   Attached is a file of my latest terminal session.  Sorry to
>> send it as an attachment, but I have to use my Windows desktop at home as
>> I
>> don't have and can't get broadband where I live.
>>
>> When I started installing the package, I did it from my home folder, not
>> the
>> root, and I think that' is what's messing things up.  Should I move the
>> tar
>> file to root, extract it and try the installation again from there, or do
>> I
>> have to remove all the stuff I installed?
>>
>> Thanks for your help,
>> Morris
>>
>> --- On Fri, 3/13/09, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote:
>>
>> From: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>
>> Subject: Re: login problems
>> To: "Morris Lee" <flydog_38@xxxxxxxxx>
>> Cc: discuss@xxxxxxxxxxxxx
>> Date: Friday, March 13, 2009, 6:27 PM
>>
>> Morris
>>
>> To obtain syntax guidance, run:
>> $ slmodemd --help
>> which relates to either specify ALSA mode either with:
>>   -a  OR   --alsa
>>
>> The /dev/pts/N ports  slmodemd creates have not yet been equipped with
>> sound competence.  That is why the:
>> Carrier Check  =  no
>> line is necessary in /etc/wvdial.conf
>>
>> On  my System, permissions are
>> $ ls -l /usr/sbin/pppd
>> -rwsr-xr-- 1 root dip 269256 2007-10-04 15:57 /usr/sbin/pppd
>>
>> But if with root permission you:
>>   chmod a+x  /usr/sbin/pppd
>> You can start
>>   wvdial
>> as an ordinary User, rather that root.
>> Please relate what your modem specs, kernel and driver are when you report
>> back.
>>
>> MarvS
>>
>>
>> On Fri, Mar 13, 2009 at 3:52 PM, Morris Lee <flydog_38@xxxxxxxxx> wrote:
>>>
>>> Hello everyone,
>>>
>>> I installed the slmodemd package, but couldn't get alsa to work.  The
>>> instructions said to put two hyphens in front of alsa on the command line
>>> when only one is the right syntax, and I think that's what messed things
>>> up.
>>> However, I can live without sound.  What I can't accept is not being able
>>> to
>>> log on to my ISP.  The modem goes though its initialization commands,
>>> dials
>>> the number, the user name and password are accepted, and then I get this
>>> message over and over:
>>>
>>> --> Looks like a welcome message.
>>> --> Unable to run /usr/sbin/pppd.
>>> --> Check permissions, or specify a "PPPD Path" option in wvdial.conf.
>>>
>>> I checked the properties of both wvdial.conf and /usr/sbin/pppd and they
>>> are both root.  I did use the chmod 666 command on wvdial.conf to allow
>>> me
>>> to edit it.
>>>
>>> What do I do now?
>>>
>>> Thanks for your help,
>>> Morris
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>


[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux