Red Hat Bugzilla – Bug 163446
System locks when creating a modem device
Last modified: 2008-02-18 18:21:45 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; es-AR; rv:1.7.5) Gecko/20041108 Firefox/1.0
Description of problem:
I order to dial-up to my ISP I have to create a network device to hook it up with the ISP dial info. I am presented a few options: ISDN, Ethernet and Modem. I choose modem and fill in the info (I know the modem is in /dev/ttyS1), when I choose OK, the system locks and stops responding. No action can be done except pressing reset.
The same happens if I open KPPP, it locks before all of its window is finished drawing.
This worked on FC 2 on the same hardware.
If I run setserial -bg /dev/ttyS1 I see the detected modem with its memory address and the IRQ. If I run wvdiaconf it sais the modem was detected on /dev/ttyS1.
I also tried ttyS2 and ttyS3
I have disabled the motheboard's build-im serial port from the BIOS.
I ran wvdial --chat and after issuing the modem init strings it sais modem is not responding.
The modem appears in the hardare browser as unrecognized device, as it did on FC2.
Version-Release number of selected component (if applicable):
The FC4's original version of system-config-network
Steps to Reproduce:
1. Try to create the modem device in system-config-network
2. Fill in bauds, /dev/ttyS1
2. Press OK
Actual Results: I locks. Forces you to press reset since ctr-alt-backspace, numlock or anything else does not work. Mouse stays freezed. No messages in /var/log/messages regarding anything related before the lock-up.
Expected Results: It should create the modem configuration and alow me to create the ISP configuration.
I know the modem works, since I using it to file the this bug report. I have SELinux enabled. All default services Up, this is a newly installed FC 4. /dev/modem does not exist, but /dev/ttyS[1-3] do exist.
/etc/wvdial.conf seems ok, and issuing command wvdialconf /etc/wvdial.conf reports all succesfull messages telling the modem is there.
The modem is a ISA 3Com U.S.Robotis Voice Faxmodem. V.90. Not a winmodem. I know people are not using these hardware a lot anymore, but this worked fine under FC2 so it is a pity for modem users to have to go back. Besides the lock-up seems strange.
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?
Fedora Core 4 is no longer maintained.
Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.