On 24-Jul-2000 Tomasz Barszczak wrote:
> Well, too soon to be happy.
> cron runs periodically rmmod -a .
> Then when I want to use the modem again serial driver is re-loaded:
> Serial driver version 4.13 with no serial options enabled
> tty00 at 0x03f8 (irq = 4) is a 16550A
> tty01 at 0x02f8
A long time ago, in a galaxy far, far way, someone said...
> Well, too soon to be happy.
> cron runs periodically rmmod -a .
> Then when I want to use the modem again serial driver is re-loaded:
> Serial driver version 4.13 with no serial options enabled
> tty00 at 0x03f8 (irq = 4) is a 16550A
Tom,
Try feeding the IO port and IRQ you see from lspci into setserial. Or try
building a 2.4.0-pre4 kernel, which has PCI serial support.
I've heard that some PCI hardware DSP modems might not even use an uart,
but I've never seen anything specific.
On Sun, 23 Jul 2000, Tomasz Barszczak wrote:
On Sun, Jul 23, 2000 at 11:53:02AM -0700, Tomasz Barszczak wrote
> > Having the modem recognize the Hayes AT command language is not a reliable
> > indicator. Many winmodem drivers have an AT command interpreter to
> > satisfy older programs.
>
> When I bought the modem I was assured it is not a
Well, too soon to be happy.
cron runs periodically rmmod -a .
Then when I want to use the modem again serial driver is re-loaded:
Serial driver version 4.13 with no serial options enabled
tty00 at 0x03f8 (irq = 4) is a 16550A
tty01 at 0x02f8 (irq = 3) is a 16550A
And the modem is inaccessible
A long time ago, in a galaxy far, far way, someone said...
> Thank you. It worked. I can talk to the modem in minicom now.
> For the reference: I got IRQ and address number from Windows.
> The magic command was:
> setserial -v /dev/ttyS4 uart 16550A port 0xD400 irq 5 session_lockout
> ^fourport
A long time ago, in a galaxy far, far way, someone said...
> > Having the modem recognize the Hayes AT command language is not a reliable
> > indicator. Many winmodem drivers have an AT command interpreter to
> > satisfy older programs.
>
> When I bought the modem I was assured it is not a winmo
Thank you. It worked. I can talk to the modem in minicom now.
For the reference: I got IRQ and address number from Windows.
The magic command was:
setserial -v /dev/ttyS4 uart 16550A port 0xD400 irq 5 session_lockout ^fourport
> Having the modem recognize the Hayes AT command language is not a reliable
> indicator. Many winmodem drivers have an AT command interpreter to
> satisfy older programs.
When I bought the modem I was assured it is not a winmodem
(software modem) but a hardware modem.
I also searched the web and
On Sun, 23 Jul 2000, Tomasz Barszczak wrote:
> Hi,
>
> I have just installed slink on my AMD Athlon PC.
> I have an internal USR 56K modem model 2977.
> It is not a winmodem, it uses Hayes AT language.
> Under Windows 98 it is recognized at COM5 and works fine.
>
> First problem was that in /d
A long time ago, in a galaxy far, far way, someone said...
> Hi,
>
> I have just installed slink on my AMD Athlon PC.
> I have an internal USR 56K modem model 2977.
> It is not a winmodem, it uses Hayes AT language.
> Under Windows 98 it is recognized at COM5 and works fine.
Having the modem rec
Hi,
I have just installed slink on my AMD Athlon PC.
I have an internal USR 56K modem model 2977.
It is not a winmodem, it uses Hayes AT language.
Under Windows 98 it is recognized at COM5 and works fine.
First problem was that in /dev there were only ttyS0-ttyS3 (COM1-COM4)
with major number 4 a
12 matches
Mail list logo
