[gentoo-user] Conexant chip

[gentoo-user] Conexant chip

[millerhe1]

Has anyone gotten the conexant chip modem to work under linux?
Sent via BlackBerry from Cingular Wireless  
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Conexant chip

[Mick]

[-- Attachment #1: Type: text/plain, Size: 288 bytes --]

On Wednesday 11 October 2006 06:33, millerhe1@verizon.net wrote:
> Has anyone gotten the conexant chip modem to work under linux?

Yes, I have running hcfpci for some years now.  You need to rebuild it every 
time you compile a new kernel.  What's your problem?
-- 
Regards,
Mick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] Conexant chip

[millerhe1]

It locks up everytime I attempt to query the modem. Kpp by the way. Sorry for top post blackberry only allow that.
Sent via BlackBerry from Cingular Wireless  

-----Original Message-----
From: Mick <michaelkintzios@gmail.com>
Date: Wed, 11 Oct 2006 07:42:31 
To:gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Conexant chip

On Wednesday 11 October 2006 06:33, millerhe1@verizon.net wrote:
> Has anyone gotten the conexant chip modem to work under linux?

Yes, I have running hcfpci for some years now.  You need to rebuild it every 
time you compile a new kernel.  What's your problem?
-- 
Regards,
Mick


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Conexant chip

[Mick]

[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]

On Wednesday 11 October 2006 18:01, millerhe1@verizon.net wrote:
> It locks up everytime I attempt to query the modem. Kpp by the way. Sorry
> for top post blackberry only allow that. Sent via BlackBerry from Cingular
> Wireless

You need to emerge hcfpcimodem; run hcfpci-config (I think this happens 
automatically by the ebuild script these days).

Assuming all of this completes without errors you should either reboot and 
check what dmesg says, or run udevstart.  Run /etc/init.d/hcfpci start.  
Assuming again that starting the script did not reveal any errors (both on 
the command line and on /var/log/messages) you should be good to add hcfpci 
to your default runlevel.  When you fire up kppp choose /dev/modem, 
or /dev/ttySHCF0 (I think one should be a link to the other).

All things being equal the above should just work.  The symptom of a hanging 
kppp is probably an indication that the device you selected under the modem 
tab in the kppp, can't be found.  If your problem is caused by a clash 
between serial devices, (IRQs and what have you) rather than you selecting 
the wrong one in kppp, then you may need to use the setserial command first 
to define a serial port (COM port) for your modem.

I hope the above helps.
-- 
Regards,
Mick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]