Help - Search - Members - Calendar
Full Version: Conexant V90 56k Modem
Linuxhelp > Support > Hardware Support
richessence
I installed & tried initializing this modem in X but it gave me:
“failed to activate with error 6”

The modem does not include any helpful info about the chipset in the documentation.
So from a combo of books & online info I did the following:


This is the output of my lspci-v
01:08.0 comm controller: conexant HSF 56k HSFi modem (rev 01)
sybsystem: zoom telephonics inc: unknown device 8d88
flags: bus master, medium devsel, latency 64, IRQ 11
memory at 40000000 (32-bin, non-prefetchable) [size=64k]
I/O ports at 14c0 [size=8]
Capabilities: [40] power management version 2

Kudzu has added this to hwconf
-
class: MODEM
bus: PCI
detached: 0
driver: unknown
desc: "Conexant HSF 56k HSFi Modem"
vendorId: 14f1
deviceId: 2f00
subVendorId: 141b
subDeviceId: 8d88
pciType: 1
pcidom: 0
pcibus: 1
pcidev: 8
pcifn: 0
-

Then I did the following & got no errors
Cd /dev
Test –c ttyS3
./MAKEDEV ttyS3
chmod 666 /dev/ttyS3
setserial /dev/ttyS3 uart 16550 port 0x2460 irq 11
ln –sf /dev/ttyS3 /dev/modem

NOTE: I got the port & irq addresses as a result from cat /proc/pci
They were the first port & irq listed.

But then when I run minicom, it says it’s initializing but then does not give me the “ok” prompt.
Also, on the shell, I get no “ok” when I do an echo “atdt” > /dev/ttyS3

So, I’m wondering if the output of the lspci & contents of hwconf indicate that this modem has it’s own controller & should be working.

If linux is recognizing this & if the modem does have it’s own controller, the only thing I can see wrong is the “unknown device 8d88” in the lspci message & the “driver: unknown” in the hwconf file.

I’m wondering maybe based on the info I have listed here the modem is recognized & should work, & if that’s the case what am I not doing/doing wrong?

Or, if I need the driver, how can I:
1. Locate a proper driver on the Linmodem site when there are several pertaining to conexant?
2. How do I install the driver & associate it with /dev/ttyS3?
3. If it’s recognizing the controller/chipset can I use a generic driver, & how?

Thank you for your input,

Mark
richessence
PS I'm using Core 3 kernel 2.6.12
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2017 Invision Power Services, Inc.