Hi All, Thanks for the replies. I think that I had better supply some more information about the problem and what I am trying to achieve. The modem in question is a Pace 56K internal one. This device is a jumperless pnp modem, most definitely not a win modem. It works fine under dos and win95/98. Now here is the rub. Under dos com2 IRQ 3 at 0x2f8h it works fine. In win95/98 it moves address to com3 IRQ 15 at 0x3e8h and also works fine. Incidentally this info comes from modem properties in win. In SuSe, using yast it I have set it to dos-com2 without success. I have also used isapnp which referred me to the man page. So from that I used pnpdump to produce a isapnp.conf file which I edited and placed in /etc/. This file is run when the machine is booted, and seems to place the modem on com2, 0x2f8h, IRQ3. But I still don't seem to be able to communicate with the modem. Actually I have tried every com port address and IRQ and still no luck. It seems that the modem refuses to talk to SuSe, which is why I was trying to initialise it at boot time before anything else got to it. At the end of the day I am trying to get a demonstration machine running so that I can show and make comparisons to prospective clients. Once again thankyou for your assistance. Regards Derrick S - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Derrick Simpson. wrote:
Hi All,
Thanks for the replies. I think that I had better supply some more information about the problem and what I am trying to achieve. The modem in question is a Pace 56K internal one. This device is a jumperless pnp modem, most definitely not a win modem. It works fine under dos and win95/98.
Now here is the rub. Under dos com2 IRQ 3 at 0x2f8h it works fine. In win95/98 it moves address to com3 IRQ 15 at 0x3e8h and also works fine. Incidentally this info comes from modem properties in win.
irqs 3 and 15 usually cause conflicts in Linux, 3 is the mouse and 15 usually a pci video card. i don't know if this'll work, but you might try changing the irq for the modem in win95 to, say, irq 10 (works on my machine). if win95 makes the change stick then you're getting somewhere. then all you have to do is <setserial cua 2 irq 10> (i think, read the setserial man for better instructions - also cua 2 = com3 etc.). and also make sure to have your ppp script look at your cua x for the modem or set /dev/modem to cua x.
In SuSe, using yast it I have set it to dos-com2 without success. I have also used isapnp which referred me to the man page. So from that I used pnpdump to produce a isapnp.conf file which I edited and placed in /etc/.
This file is run when the machine is booted, and seems to place the modem on com2, 0x2f8h, IRQ3. But I still don't seem to be able to communicate with the modem. Actually I have tried every com port address and IRQ and still no luck.
it's odd, in win95 you said that it put your modem on com3 but in dos it ended up at com2. hmm, actually, it doesn't look like my solution will fix your problem, but it might be worth trying. good luck, dave - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
"Derrick Simpson." <derricksimpsonATintonetDOTcoDOTuk@intonet.co.uk> writes:
Hi All,
Thanks for the replies. I think that I had better supply some more information about the problem and what I am trying to achieve. The modem in question is a Pace 56K internal one. This device is a jumperless pnp modem, most definitely not a win modem. It works fine under dos and win95/98.
Now here is the rub. Under dos com2 IRQ 3 at 0x2f8h it works fine. In win95/98 it moves address to com3 IRQ 15 at 0x3e8h and also works fine. Incidentally this info comes from modem properties in win.
In SuSe, using yast it I have set it to dos-com2 without success. I have also used isapnp which referred me to the man page. So from that I used pnpdump to produce a isapnp.conf file which I edited and placed in /etc/.
This file is run when the machine is booted, and seems to place the modem on com2, 0x2f8h, IRQ3. But I still don't seem to be able to communicate with the modem. Actually I have tried every com port address and IRQ and still no luck.
It seems that the modem refuses to talk to SuSe, which is why I was trying to initialise it at boot time before anything else got to it.
At the end of the day I am trying to get a demonstration machine running so that I can show and make comparisons to prospective clients.
Once again thankyou for your assistance.
Regards Derrick S
Check in /sbin/init.d/serial to make sure that Yast uncommented the correct command line for setserial (I do things like that by hand myself) You might also add a -v to the command line (or do a etserial -v /dev/cua1 spd_vhi port 0x2f8h irq 3 at the command line of a running system.) Also note that /dev/cua0 (and /dev/ttyS0) are dos COM1, /dev/cua1 (and /dev/ttyS1) are dos COM2 (just thought I'd mention that in case you didn't know that already.) - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
participants (3)
-
bfootdav＠bellsouth.net -
derricksimpsonATintonetDOTcoDOTuk＠intonet.co.uk -
markgray＠iago.nac.net