Bug 109101 - kppp hangs on initializing modem...
Summary: kppp hangs on initializing modem...
Status: RESOLVED WORKSFORME
Alias: None
Product: kppp
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 2.2.0
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: Harri Porten
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-14 21:43 UTC by Scott Thatcher
Modified: 2023-01-05 05:26 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Thatcher 2005-07-14 21:43:42 UTC
Version:           2.2.0 (using KDE KDE 3.3.2)
Installed from:    Debian stable Packages
OS:                Linux

Sorry if this is a repeat, but all similar bugs I saw were closed, and none seemed exactly the same in how they were reported or how they were fixed.

After I have configured kppp with isp and modem information, KPPP hangs on "Initializing Modem..."  The log window contains "Expecting: OK" at the bottom, but nothing else is printed in the log window.  In all other ways, KPPP seems to communicate with the modem.
"Querry Modem..." returns what seems to be useful information.  The terminal inside KPPP is able to initialize the modem, and the modem responds with OK.  After reading other bug reports, I made sure my modem volume control strings were empty, but that didn't make a difference. I've tried configuring the modem with and without the "Use lock file" option.  Every other modem access program I've tried---like minicom or pppconfig/pon/poff had worked fine.

I've never had a problem with KPPP in the past, and this behavior was very surprising to me.

My modem is a PCI controller modem (MultiTech MultiModem ZPX) which has worked fine answering the phone and communicating with other modems in the past.  The only strange thing I've noted about this modem is that it wants to be at /dev/ttyS14 (which I had to create).  However, I've created a link from /dev/modem/ to /dev/ttyS14, and that link works fine as the serial device for my other modem-using programs.

When I run KPPP from the command line, the following is printed up to when the modem hangs...

  Opener: received SetSecret
  Opener: received SetSecret
  Opener: received OpenLock

  Opener: received OpenDevice

Here is what lspci says about my modem:
  0000:00:0a.0 Communication controller: Lucent Microelectronics Venus Modem (V90,
   56KFlex)
          Subsystem: Lucent Microelectronics: Unknown device 5656
          Flags: bus master, medium devsel, latency 0, IRQ 18
          Memory at ea000000 (32-bit, non-prefetchable) [size=256]
          I/O ports at b000 [size=256]
          I/O ports at b400 [size=256]
          I/O ports at b800 [size=8]
          Capabilities: [f8] Power Management version 2

Thanks for a very nice product, and please let me know if I can provide more information.

Scott Thatcher
Comment 1 Andrew Crouthamel 2018-11-02 04:27:51 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-16 02:35:57 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2022-12-03 09:01:35 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Scott Thatcher 2022-12-06 16:17:43 UTC
Sorry, no longer own the modem, so can't test!
Comment 5 Bug Janitor Service 2022-12-21 05:17:15 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2023-01-05 05:26:26 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!