Red Hat Bugzilla – Bug 161754
fc4 won't confgure modem
Last modified: 2007-11-30 17:11:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.0.4-1.3.1 Firefox/1.0.4
Description of problem:
When I try to configure a modem, the system does not detect the pcmcia
usr 56k modem at the com port tty/S3 as was done with fc3. In fact, no
dialog box comes up showing a found modem at all. The laptop, a Dell inspiron 4150 has a winmodem built in and my pcmcia card.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Click on red hat and drag down to system settings->network
2.click on network wizard, and in dialog box, choose "new"
3.click on modem. (note no attempt to locate modem port tty/S3 as was done on fc3)
4. see dialog box for isp, phone number, and password
5 enter info and click done.
Actual Results: When you click "activate" error message comes up ppp0 connection failed, errot 2
Expected Results: A good modem connection should have been established, dialing, answer, and connection with id/password pair and ready for activation of browser
This was an issue for me on the same laptop under Red Hat Linux 9, but I do not know if the cause is the same. I have returned to fc3 and the modem, software and connection work perfectly.
P.S. under fc4 I attempted to activate "minicom -s" and successfully dialed out with it.
I've re-installed fc4 and attempted again to configure "configure internet
wizard." After entering root password, the "Select Device Type" dialog box
appears, where I select "Modem Connection." When the "modem probing" dialog box
disappears, a "Warning" box appears: system-config-network: No Modem was found
on your system. At this point, FC3 would find the pcmcia modem at port tty/S3
and allow me to proceed to the next dialog box where I enter ISP, phone number,
ID and password where Modem device is described as tty/S3 rathere than
/dev/modem under FC4. Now I cancel the process, because going further is pointless.
If I could learn how to handle this whole process with command-line format from
a terminal window, I am sure I could get this to work. However I am command
*** This bug has been marked as a duplicate of 161733 ***