A problem I have had in the past with ISA modems, is the motherboard's
COM2 is enabled and thus prevents the modem from obtaining it, but I wouldn't
think that a PCI modem would need to obtain a COM port at all.  Typically, 
you can find this value in your BIOS setup, but I have seen it located on the
motherboard itself.

dizzy writes:
 > Hello,
 > 
 > After reading the Modem-HOWTO and still not managing to get my PCI modem
 > to work I decided to send you the details of this beast - hope you'll be
 > able to help me.
 > 
 > I am running a 2.2.13 kernel and the modem is called Conexant HCF V90
 > 56K Data Fax RTAD PCI Modem (at least this is what wingodz95 is saying).
 > 
 > In the device manager it also has something called 'Conexant PCI Modem
 > Enumerator'.
 > Moving on... it should have a rockwell chipset and it should also be a
 > 'hardware modem' , and if it is of any relevance this is what ATI6
 > returns:
 > V90    SPX RAM Ver 04
 > V90    CTL RAM Ver 04
 > K56FLEX SPX RAM Ver 47
 > K56FLEX CTL RAM Ver 47
 > 
 > 
 > and lspci -vv:
 > 00:0a.0 Communication controller: Unknown device 14f1:1034 (rev 08)
 >         Subsystem: Unknown device 13e0:0231
 >         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-
 >         Latency: 248 set
 >         Interrupt: pin A routed to IRQ 10
 >         Region 0: Memory at ee000000 (32-bit, non-prefetchable)
 >         Region 1: I/O ports at e800
 >         Capabilities: [40] Power Management version 2
 >                 Flags: PMEClk- AuxPwr- DSI+ D1- D2- PME+
 >                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 > 
 > 
 > I tried all both with pnp os set to on and of in BIOS and no result at
 > all. Also it appears that in win95 the modem uses com2, but there is no
 > com2 listed in the device manager.
 > Setserial could not detect the uart for the port (ttyS1). In win95 it is
 > reported as NS 16550AN.
 > 
 > Is there any hope?
 > TIA
 > 
 > dizzy
 > 
 > PS I have tried to email the maintainer of the serial driver but I've
 > got no answer as yet (I sent the email a couple of weeks ago)
 > 
 > 
 > -- 
 > To unsubscribe:
 > mail -s unsubscribe [EMAIL PROTECTED] < /dev/null

-- 
To unsubscribe:
mail -s unsubscribe [EMAIL PROTECTED] < /dev/null

Reply via email to