I'm having a disappearing modem problem. I put in the computer, it gets recognized by kudzu, and it comes up working. I use it to dial in to an old mainframe. Kermit sees it, and I have ProComm for DOS running under dosemu. All seems well. I shut down the computer, and when it comes back up, it has disappeared. So far, I've only been able to recover it by removing it and rebooting, and then reinstalling it and rebooting. It seemed to be a problem with a lockfile earlier on, but, that's no longer the case. Can anyone offer an idea? I've searched the list and read the configuration manuals from Redhat, but there is precious little said about modems for old-style dialup.
Claude Jones wrote:
I'm having a disappearing modem problem. I put in the computer, it gets recognized by kudzu, and it comes up working. I use it to dial in to an old mainframe. Kermit sees it, and I have ProComm for DOS running under dosemu. All seems well. I shut down the computer, and when it comes back up, it has disappeared. So far, I've only been able to recover it by removing it and rebooting, and then reinstalling it and rebooting. It seemed to be a problem with a lockfile earlier on, but, that's no longer the case. Can anyone offer an idea? I've searched the list and read the configuration manuals from Redhat, but there is precious little said about modems for old-style dialup.
I reply to myself - the modem is not disappearing. By doing a kudzu -p I was able to determine that the modem is still configured and is set to ttyS14 - when I used that to connect via Kermit and ProComm just now, I got in. So, does anyone know why, is it called the 'symbolic link' /dev/modem?, keeps disappearing?
Claude Jones wrote:
Claude Jones wrote:
I'm having a disappearing modem problem. I put in the computer, it gets recognized by kudzu, and it comes up working. I use it to dial in to an old mainframe. Kermit sees it, and I have ProComm for DOS running under dosemu. All seems well. I shut down the computer, and when it comes back up, it has disappeared. So far, I've only been able to recover it by removing it and rebooting, and then reinstalling it and rebooting. It seemed to be a problem with a lockfile earlier on, but, that's no longer the case. Can anyone offer an idea? I've searched the list and read the configuration manuals from Redhat, but there is precious little said about modems for old-style dialup.
I reply to myself - the modem is not disappearing. By doing a kudzu -p I was able to determine that the modem is still configured and is set to ttyS14 - when I used that to connect via Kermit and ProComm just now, I got in. So, does anyone know why, is it called the 'symbolic link' /dev/modem?, keeps disappearing?
Claude, I do not recall seeing your issue raised on the list before. It may have been and I just did not see the thread or do not remember it.
The absence of any respoonses to your query, though, suggests that readers of the messagee have not come up with any answers to your question(s). Have you considered filing a bugzilla report on the issue?
David Curry wrote:
Claude Jones wrote:
Claude Jones wrote:
I'm having a disappearing modem problem. I put in the computer, it gets recognized by kudzu, and it comes up working. I use it to dial in to an old mainframe. Kermit sees it, and I have ProComm for DOS running under dosemu. All seems well. I shut down the computer, and when it comes back up, it has disappeared. So far, I've only been able to recover it by removing it and rebooting, and then reinstalling it and rebooting. It seemed to be a problem with a lockfile earlier on, but, that's no longer the case. Can anyone offer an idea? I've searched the list and read the configuration manuals from Redhat, but there is precious little said about modems for old-style dialup.
I reply to myself - the modem is not disappearing. By doing a kudzu -p I was able to determine that the modem is still configured and is set to ttyS14 - when I used that to connect via Kermit and ProComm just now, I got in. So, does anyone know why, is it called the 'symbolic link' /dev/modem?, keeps disappearing?
Claude, I do not recall seeing your issue raised on the list before. It may have been and I just did not see the thread or do not remember it.
The absence of any respoonses to your query, though, suggests that readers of the messagee have not come up with any answers to your question(s). Have you considered filing a bugzilla report on the issue?
David: I am very new to Linux, and have never filed a bugzilla report. It hadn't occurred to me. I'm not sure I have enough confidence to know I'm doing everything correctly, and that there isn't something I've done that's causing the problem. You're right, though - no one else seems to be having this specific problem. Just to put a few more details on the subject - the modem is a USR 5610 and was recommended on some Linux site I visited. It is a real modem, not a winmodem. It works just fine except for this disappearing problem with the link - I'm reading through the UDEV pages suggested by someone else earlier today to deal with a dev/ttyS0 permission denied problem. There's some promise, there. I'll keep bugzilla in mind.
On 03/30/2005 08:56:09 PM, Claude Jones wrote:
David: I am very new to Linux, and have never filed a bugzilla report. It hadn't occurred to me. I'm not sure I have enough confidence to know I'm doing everything correctly, and that there isn't something I've done that's causing the problem. You're right, though - no one else seems to be having this specific problem. Just to put a few more details on the subject - the modem is a USR 5610 and was recommended on some Linux site I visited. It is a real modem, not a winmodem. It works just fine except for this disappearing problem with the link - I'm reading through the UDEV pages suggested by someone else earlier today to deal with a dev/ttyS0 permission denied problem. There's some promise, there. I'll keep bugzilla in mind.
It definitely sounds like udev is not keeping track of the symlink. Unfortunately I do not use a dialup modem anymore, when I still had it installed - FC3 did keep track of the symlink properly. It was a US Robotics hardware modem on a PCI card.
Is your udev up to current patch level? That's always the first thing before filing a bug report - make sure your system is up to date - there have been a lot of patches, and some to fix udev issues.
If the size of the update download is an issue with your dialup connection, and if you have a DVD drive, I can mail you the updates on DVD - maybe it will resolve your issue.
If your system isn't updated, you can try (from CLI as r00t)
yum update udev hal
That will just pull in udev and hal updates and their dependencies and may be all that you need to resolve this issue.
Michael A. Peters wrote:
On 03/30/2005 08:56:09 PM, Claude Jones wrote:
David: I am very new to Linux, and have never filed a bugzilla report. It hadn't occurred to me. I'm not sure I have enough confidence to know I'm doing everything correctly, and that there isn't something I've done that's causing the problem. You're right, though - no one else seems to be having this specific problem. Just to put a few more details on the subject - the modem is a USR 5610 and was recommended on some Linux site I visited. It is a real modem, not a winmodem. It works just fine except for this disappearing problem with the link - I'm reading through the UDEV pages suggested by someone else earlier today to deal with a dev/ttyS0 permission denied problem. There's some promise, there. I'll keep bugzilla in mind.
It definitely sounds like udev is not keeping track of the symlink. Unfortunately I do not use a dialup modem anymore, when I still had it installed - FC3 did keep track of the symlink properly. It was a US Robotics hardware modem on a PCI card.
Is your udev up to current patch level? That's always the first thing before filing a bug report - make sure your system is up to date - there have been a lot of patches, and some to fix udev issues.
If the size of the update download is an issue with your dialup connection, and if you have a DVD drive, I can mail you the updates on DVD - maybe it will resolve your issue.
If your system isn't updated, you can try (from CLI as r00t)
yum update udev hal
That will just pull in udev and hal updates and their dependencies and may be all that you need to resolve this issue.
Michael: I think you may have missed my early discussion of this problem, namely: "I use it to dial in to an old mainframe." My internet connection is via broadband so I do have all the latest patches installed. I appreciate your offer, tho. From my reading so far, UDEV is good, but still prone to some problems. I shall keep investigating, but at least for now, I can live with using ttyS14 when I have to refer to the modem -- there's still a chance that will stop working, I suppose, since I didn't try a reboot after I made that discovery. I'll have to wait till morning to see.
On Wed, Mar 30, 2005 at 08:31:56PM -0500, Claude Jones wrote:
Claude Jones wrote:
I'm having a disappearing modem problem. I put in the computer, it gets recognized by kudzu, and it comes up working. I use it to dial in to an old mainframe. Kermit sees it, and I have ProComm for DOS running under dosemu. All seems well. I shut down the computer, and when it comes back up, it has disappeared. So far, I've only been able to recover it by removing it and rebooting, and then reinstalling it and rebooting. It seemed to be a problem with a lockfile earlier on, but, that's no longer the case. Can anyone offer an idea? I've searched the list and read the configuration manuals from Redhat, but there is precious little said about modems for old-style dialup.
I reply to myself - the modem is not disappearing. By doing a kudzu -p I was able to determine that the modem is still configured and is set to ttyS14 - when I used that to connect via Kermit and ProComm just now, I got in. So, does anyone know why, is it called the 'symbolic link' /dev/modem?, keeps disappearing?
You don't say, but is your modem external? Fedora has a poor record in recognizing external modems. Modems are removed in my experience at random, it seems, for no reason whatsoever. If kudzu thinks the modem has disappeared then I ma nor surprised the /dev/modem disappears. Using the /dev/ttySx has always worked better for me.
akonstam@trinity.edu wrote: | Claude Jones wrote: || I reply to myself - the modem is not disappearing. By doing a || kudzu -p I was able to determine that the modem is still || configured and is set to ttyS14 - when I used that to connect || via Kermit and ProComm just now, I got in. So, does anyone || know why, is it called the 'symbolic link' /dev/modem?, keeps || disappearing? || | You don't say, but is your modem external? Fedora has a poor | record in recognizing external modems. Modems are removed in my | experience at random, it seems, for no reason whatsoever. If | kudzu thinks the modem has disappeared then I ma nor surprised | the /dev/modem disappears. Using the /dev/ttySx has always | worked better for me. -- |
It's an internal PCI recommended for Linux. Someone suggested a driver had been made available by USR and I installed it - that 'may' have fixed the problem. I'm doing so many things today to this box that I'm having a hard time keeping track of them all.
Claude Jones Levit & James, Inc./WTVS Leesburg, VA, USA
Claude Jones wrote:
akonstam@trinity.edu wrote: | Claude Jones wrote: || I reply to myself - the modem is not disappearing. By doing a || kudzu -p I was able to determine that the modem is still || configured and is set to ttyS14 - when I used that to connect || via Kermit and ProComm just now, I got in. So, does anyone || know why, is it called the 'symbolic link' /dev/modem?, keeps || disappearing? || | You don't say, but is your modem external? Fedora has a poor | record in recognizing external modems. Modems are removed in my | experience at random, it seems, for no reason whatsoever. If | kudzu thinks the modem has disappeared then I ma nor surprised | the /dev/modem disappears. Using the /dev/ttySx has always | worked better for me. -- |
It's an internal PCI recommended for Linux. Someone suggested a driver had been made available by USR and I installed it - that 'may' have fixed the problem. I'm doing so many things today to this box that I'm having a hard time keeping track of them all.
And once again, I reply to myself. The modem, a USR 5610, seems to be stable following the install of the driver package from the USR website. I can't say for sure that that is what fixed the problem, since I've worked on so many things today, but it's probably worth installing that driver just because it was written by the manufacturer specifically for Linux. I've rebooted the computer many times today and not once has /dev/modem disappeared since the driver install.
-
akonstam＠trinity.edu -
Claude Jones -
David Curry -
Michael A. Peters