🚀 go-pugleaf

Linux will only detect standard com ports .... you have to use "setserial"
command
to tell the kernel what irq to use (irq sharing is generally a bad thing try
to avoid it).
Use minicom or kermit to test the port is communicating ok with the modem.

andersen@mweb.co.za wrote:

> Hi, a little while ago I posted a help, a few people replied for which I am
> grateful. Thanks!  But still the thing don't work none! I have since dug
> deeper to the
> source of the problem, this is what I've discovered so far:
>
> UART Unkown
> ttyS3, IRQ 3 (these are also physically set on my isa Duxbury 56K V.90
> internal modem)
>
> The problem I get is something like 'device busy'. The modem-HOWTO
> suggests...
> "This problem can arise when DCD or DTR are not implemented correctly" -
> what the heck does this mean? Or there is an IRQ conflict, but I am under
> the
> impression that Kernels greater than ver 2.2 support IRQ sharing...
>
> Do I need to physically change my modem jumpers to IRQ 5?
>
> Any ideas? (before I clear my desk and take my pc apart) Windows somehow
> manages to run my modem on IRQ 11, is this possible under Linux?
>
> Thanks in advance...
> Erik