Re: [newbie] Modem Config!
I just check the compatiblity chart at: http://www.idir.net/~gromitkc/20010604b.html and I'm afraid it's listed as not compatible. I was afraid so when windows called it an enumerator. :-( -s On Thursday 09 August 2001 11:32 am, you wrote: > On Thursday 09 August 2001 12:33 am, you wrote: > > Aopen PCI Modem Enumerator (from windows system report) > > AOpen FM56-PM Fax/modem/Voice (from package) >
Re: [newbie] Modem Config!
On Thursday 09 August 2001 12:33 am, you wrote: > Aopen PCI Modem Enumerator (from windows system report) > AOpen FM56-PM Fax/modem/Voice (from package) Could you check at http://www.linmodem.org and make sure it's a hardware modem and not a software modem? It's weird that 8.0 didn't recognize it and set it up for you automagically. I have three different modems and 5 different ethernet cards and 8.0 set them all up for me. Makes me suspect yours may be a software modem. If so, it is possible that there are drivers available found thru that same site. > > After rebooting, I saw that the information I changed, had been changed > back, no com3 listingI typed in all in again. That's why I wanted you to reboot, to change it back. Reboot and go into a terminal and type: cat /proc/pci and look for a communications device. Get the irq and ioport. Are you sure of the com3 thing? If setserial don't work this time with the numbers from /proc/pci, try experimenting with the other com ports. Linux and windows don't always correspond. > > The first couple of times, I'm not sure if I typed an "0" by accident, > but that's what the irq in com3 kept showing. The second time I did it, > I was careful to press "9" for irq but it still showed "0." The third > time it finally said "9". Still busy modem. > > Haven't booted back up yet but I'm going to after this message. See if > changes have been changed back again. > > I'll check email back in a few. Hope this isn't getting to out of hand! > It took me a week to get my modem to work when I first tried out any linux! Then almost another week to get sound. :-) I had to wait until 2.4.x for graphics acceleration (mobo issue). So, this is a learning process. :-) -s
Re: [newbie] Modem Config!
Oh, another thing I forgot to mention, when you type your ioport portion of the setserial command, place an 0x (that's a zero) in front of it. For example here's mine: setserial /dev/ttyS4 uart 16550A port 0xb800 irq 5 -s hope all this works for ya.
Re: [newbie] Modem Config!
On Wednesday 08 August 2001 10:03 pm, you wrote: > Thanks for the information. > > Been playing around in KDE systems control looking at everything > listed. I went through each device in the list but I'm still not sure > which one to use. > > If it's located under "Communication Controllers," it is listed as an > "unknown device." It still gives the I/O Area and Interrupt though. That's it. > > Under "Connectors" is listed Com1 and Com2 only! Com3 will show up once you associate your modem to it. > > ??? -s
Re: [newbie] modem config
ATS0 I think. Something like that. - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, February 07, 2001 12:22 AM Subject: [newbie] modem config > Can anyone tell me what the commands to give to my modem would be to > bypass the voicemail tones?? > > Because I have tried to insert pauses into my script to wait til it gets > to the dial tone but that still doesnt work... > > Any ideas?? > > > Perseus > > > > > >
Re: [newbie] Modem Config
I have a USR Courier internal. It would not work under Linux if jumpered for PnP. To have it properly installed, I: 1) logged in Windows, checked under "System Settings" which COM and IRQ Win98 was using through PnP; 2) jumpered the modem for the proper COM and IRQ, disabling PnP. 3) under linux, I used setserial and modemtool to properly finish my setup. Hope it helps, /Gustavo. On dom, 19 set 1999, you wrote: > Jeremy Kersenbrock wrote: > > > > OK, I am now down to one piece of hardware to configure. It's a USRobotics > > Sportster internal modem. It is PnP with jumpers, although I currently have > > it jumpered for PnP. I have isapnp running at startup, but I must need to > > do something else. By the way, I have read the Modem HOW-TO and the > > isapnptools documentation and both are highly technical and unclear. Both > > explain very thoroughly what is happening, but neither explain how to make > > the modem work! > > > > It appears that isapnp has it configured as ttys3 with a IO of 03f8-03ff. > > But when I select /dev/modem in the setup for kppp, I get the message > > "Sorry, can't open modem." So I select /dev/ttyS3 and get the message > > "Sorry, modem is busy." > > > > That might be true. But have you ran "setserial"? > > Linux seems to be defaulted to com 1, com 2. > If this is indeed ttyS3 ( com 4 ) you need to run setserial. > > At a terminal type " man setserial " and read it. > Then fix it. :) > ALan > > === > [EMAIL PROTECTED] ( [EMAIL PROTECTED] ) > Coming to you with Linux-Mandrake 6.0
