On Sun, Nov 19, 2000 at 08:32:31PM -0800, Heather wrote:
> > > As far as I can tell, anyway. It requires specialised drivers under
> > > Win32, fails to expose itself as a serial port and has the right sort of
> > > PCI specs to be a software modem.
>
> Actually, under Windows there will -always- be a driver ... but with a true
> modem, it will be only a couple K, enough to declare the device's name and
> link up to the serial port, basically. The others will have a driver that's
> quite large, perhaps 47k or worse.
Hmmm. what'd be the likely name for this sucker?
>
> > > Not that I will object if you can point me at how to enable it as a real
> > > modem under Linux. :)
> >
> > I can't get it to go under linux. :/ lspci gives mention of a uart in
> > there but setserial don't give me any results. :/
>
> what, exactly, does LSPCI report for it?
00:0d.1 Serial controller: Xircom: Unknown device 00d3 (prog-if 02 [16550])
Subsystem: Intel Corporation: Unknown device 2411
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 10
Region 0: I/O ports at 1470
Region 1: Memory at e8003000 (32-bit, non-prefetchable)
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
it does not appear in /proc/interrupts, ioports or devices though. my 1
real serial port does appear in ioports devices but not interrupts.
the ethernet side of the minipci card goes it works just fine.
--
CaT ([EMAIL PROTECTED])
'We do more then just sing and dance. We've got a brain too.'
-- The Backstreet Boys
