[Fwd: Re: [SLE] Winmodems]
Fred Miller wrote:
I didn't expect to have to get 9.0 pro. running on an "old" box with a USRobotics PCI winmodem. 'Anyone care to tell me how to get it to work? 9.0 doesn't even see the modem. Hi Fred,
Unfortunately it is the fact that the item is PCI that will cause the most problems. When I had to check if my ISA USR winmodem was compatible with linux I had to physically test each tty option in the modem setup in order for it to be assigned the right IRQ and actually work. The problem with PCI is that each rail is assigned a IRQ and finding that IRQ, which is not normally written anywhere, entails a similar process to the one I described above for ISA modems. Good luck and let us know what your final solution is. -- The Little Helper ======================================================================== Hylton Conacher - Linux user # 229959 at http://counter.li.org Currently using SuSE 9.0 Professional with KDE 3.1 Licenced Windows user ======================================================================== -- The Little Helper ======================================================================== Hylton Conacher - Linux user # 229959 at http://counter.li.org Currently using SuSE 9.0 Professional with KDE 3.1 Licenced Windows user ========================================================================
Hylton Conacher (ZR1HPC) wrote:
Fred Miller wrote:
I didn't expect to have to get 9.0 pro. running on an "old" box with a USRobotics PCI winmodem. 'Anyone care to tell me how to get it to work? 9.0 doesn't even see the modem.
Hi Fred,
Unfortunately it is the fact that the item is PCI that will cause the most problems. When I had to check if my ISA USR winmodem was compatible with linux I had to physically test each tty option in the modem setup in order for it to be assigned the right IRQ and actually work. The problem with PCI is that each rail is assigned a IRQ and finding that IRQ, which is not normally written anywhere, entails a similar process to the one I described above for ISA modems.
Good luck and let us know what your final solution is.
Every PCI internal modem I'd had was always configured by default to be on Com3 (unless there was the means to set it to whatever COM via jumpers [I had such a modem]). I wonder if I was just "lucky" that they were all set to COM3. The other thing is that in the BIOS there ought to be a setting - which I have always wondered about as to why it's there - where you assign the IRQ to the modem. Cheers. -- Douglass's Law: Clutter tends to expand to fill the space available for its retention.
Basil Chupin wrote:
<SNIP> Every PCI internal modem I'd had was always configured by default to be on Com3 (unless there was the means to set it to whatever COM via jumpers [I had such a modem]). I wonder if I was just "lucky" that they were all set to COM3.
The other thing is that in the BIOS there ought to be a setting - which I have always wondered about as to why it's there - where you assign the IRQ to the modem.
Cheers.
Most motherboards have two serial ports, com1 and com2 or ttyS0 and ttyS1. Your modem gets set to com3 because that is the next in line after the two on the motherboard. In the days of serial mice I would have to set my BIOS to make my on board ports com1 and com3. This way my modem would become com2 and no matter which port I plugged my mouse into, there would not be an IRQ conflict. Not a big problem anymore as most people are not even using the serial ports on the motherboard. Ports and IRQs for these ports are generally like this: DOS LINUX PORT IRQ ----------------------------------------- com1 ttyS0 0x3f8 4 com2 ttyS1 0x2f8 3 com3 ttyS2 0x3e8 4 com4 ttyS3 0x2e8 3 HTH Louis
On Saturday July 24 2004 10:08 am, Basil Chupin wrote:
Hylton Conacher (ZR1HPC) wrote:
Fred Miller wrote:
I didn't expect to have to get 9.0 pro. running on an "old" box with a USRobotics PCI winmodem. 'Anyone care to tell me how to get it to work? 9.0 doesn't even see the modem.
Hi Fred,
Unfortunately it is the fact that the item is PCI that will cause the most problems. When I had to check if my ISA USR winmodem was compatible with linux I had to physically test each tty option in the modem setup in order for it to be assigned the right IRQ and actually work. The problem with PCI is that each rail is assigned a IRQ and finding that IRQ, which is not normally written anywhere, entails a similar process to the one I described above for ISA modems.
Good luck and let us know what your final solution is.
I couldn't get 9.0 to see it on any port.....NADA.
Every PCI internal modem I'd had was always configured by default to be on Com3 (unless there was the means to set it to whatever COM via jumpers [I had such a modem]). I wonder if I was just "lucky" that they were all set to COM3.
The other thing is that in the BIOS there ought to be a setting - which I have always wondered about as to why it's there - where you assign the IRQ to the modem.
That wasn't in the setup. I got tired of the nonsense, and since the 'puter was given to my son, I had an external URR modem that I hadn't used in sometime and have forgotten about. I rummaged through my "stash" of parts and found it......timely find. 9.0 did see it instantly on bootup and had him online in mins. Winmodems ought to be outlawed. :) Fred -- "Ballmer is no more designed for the art of persuasion than the Abrams tank is for delivering meals on wheels."
participants (4)
-
Basil Chupin -
Fred Miller -
Hylton Conacher (ZR1HPC) -
Louis Richards