Re: PCI bridge...?

["Adam Williams" <awilliam@xxxxxxxxxxxxx>]

>
> yup, it's a PCI modem, Rockwell chipset.  the dmesg output is as follows:
>

Anyone know if the Rockwell chipset is Real or a Winmodem?

> Starting kswapd v 1.4.2.2
> Serial driver version 4.13 with no serial options enabled
> tty00 at 0x03f8 (irq = 4) is a 16550A
> Real Time Clock Driver v1.09
> Sound initialization started
> Sound initialization complete

So the Modem is not found.

>
> at least i think that's the pertinent part.  this is consistent with my

Yes.

> CMOS settings, in which COM1 is turned on and COM2 is not, because the PCI
> card, bridge, whatever eats up COM2 in some kind of software fashion, and
> couldn't do this if it was taken by the bios (thus spake the tech support
> guy for my computer, anyway).
> In windows, once the PCI-bridge-patch-thingy has been enabled, the modem
> information is as follows:

Hmmm, this could be bad.  We don't know exactly what the PCI bridge thingy is
doing.  Is it a program to reprogram initially broken hardware,  or a patch to
a buggy driver in windows?  I'm wagering we don't know.

>
> COM2
> IRQ 10
> 0x2F8
> UART: NS 16550AN
> 115Kbaud

Try a  "setserial /dev/ttyS2 port 0x2f8 irq 10 uart 16550A"

>
> which shows up in the "Modem" control panel.  Note that COM2 is *not* found
> in the "serial ports" section of the "system" control panel.
>

Uh Oh.  I'm thinking we have a Winmodem here.  Do a "pnpdump" and see what you
see.

> anyway, sorry for bringing up M$ products so extensively in this post; just
> thought some of this diagnostic info could maybe help contextualize.  yeah,
> that.
>

Alright,  we may have an M$ modem here.