Re: I bought a CX11252-11 modem used it with registered linuxant driver; only connects using V.34

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

the HSF driver version 7.60.00.09 supports the 2.6.21 kernel, there is no pre-compiled packages for the 2.6.21 kernel on our web site at the moment simply because the Linux distributions we officially support at the moment doesn't ship 2.6.21 kernels yet.

The HSF driver requires a valid license to be installed in order to unlock the modulations that can achieve faster connections. The license can be purchased at:

https://www.linuxant.com/store

and installed using the 'hsfconfig --license' command in a root shell. The modulation currently in use by the driver and other interesting data about the connection in progress can be obtained with the 'cat /proc/driver/h*/0/lastcallstatus' command in a root shell. The speed reported by dialing programs can be misleading, they often report the speed of the serial port (which is virtual for the HSF driver) instead of the actual connection speed. The data from 'lastcallstatus' is more accurate.

It is also important to note that even if a valid license is installed, you will very rarely obtain a 56kbps connection. As Jacques already mentioned, it is dependent on the phone line quality and if the remote modem also have the necessary modulation as well. Please also read point 7 in the HSF license available at:

http://www.linuxant.com/drivers/hsf/downloads-license.php

for more details.

Regards,


Jonathan
Technical specialist / Linuxant
www.linuxant.com
support@xxxxxxxxxxxx



Jacques Goldberg wrote:
LINUXANT PEOPLE: something for you well marked below.

Nick,

Was it such a log from wvdial which lead you to state that you cannot use V.92? The log shows the speed, 29333 bauds, not the protocole under which this speed was achieved. I have an other model of HSF modem on my laptop. It does work at close to 50kbauds,never 56k, and advertising always says "UP TO 56k", on the average 48, with good phone lines, but it often drops down to even less than yours for example in country hotels far from a major city.

Now to what is likely the cause of your trouble.

Guess why these idiots keep repeating that we NEED ModemData.txt when trying to help you.
A lot of time could have been saved, to you and to me.

You use a kernel 2.6.21

Linuxant does not provide any off the shelf HSF installer for Gentoo,
which by the way is why you had to compile your driver.

But from their Web page referenced in ModemData.txt, http://www.linuxant.com/drivers , in the HSF region, under Downloads, you may see that there is not one single installer for kernels above 2.6.20.

 From there on, you should talk to support@xxxxxxxxxxxx
Perhaps they have not tried their most recent driver with that kernel, or perhaps they know that it does not work sufficiently well to warrant creating the set of self installers.


LINUXANT PEOPLE:  (Jonathan, I guess):

This tedious thread started because Nick purchased a modem using
chipset CX11252-11 with a Linuxant license, PCI Device 14f1:2f00 , and asked who knows why he is limited to V.34.
The rest is obvious from what I wrote above.
Please comment!
Thanks in advance - Jacques

nick01 X wrote:
 Ok, sorry, must have missed your request to post that somehow. :S
ModemData.txt:


Only plain text email is forwarded by the DISCUSS@xxxxxxxxxxxxx List Server.
Do use the following as the email Subject Line:
          SomeName, YourCountry
This is  kernel 2.6.21-gentoo-r2
This will alert cogent experts, and  distinguish cases in the Archives.
YourCountry will enable Country Code guidance.
Occassionally responses are blocked by an Internet Provider mail filters.
So in a day, also check the Archived responses at http://www.linmodems.org .
Local Linux experts can be found through:
http://www.linux.org/groups/index.html
-------------------------- System information ----------------------------
CPU=i686,
This is
Linux version 2.6.21-gentoo-r2 (root@T72) (gcc version 4.1.2 (Gentoo
4.1.2)) #1 PREEMPT Mon May 28 14:46:13 EEST 2007
scanModem update of:  2007_April_23
The modem symbolic link is /dev/modem -> ttySHSF0

USB modem not detected by lsusb

Modem or host audio card candidates have firmware information:

PCI slot    PCI ID        SubsystemID    Name
----------    ---------    ---------    --------------
02:02.0 14f1:2f00 14f1:2004 Communication controller: Conexant HSF
56k HSFi Modem

Modem interrupt assignment and sharing:
11:     739658    XT-PIC-XT        hsfpcibasic2

--- Bootup diagnositcs for card in PCI slot 02:02.0 ----
ACPI: PCI Interrupt 0000:02:02.0[A] -> Link [LNKH] -> GSI 11 (level,
low) -> IRQ 11

=== Finished modem firmware and bootup diagnostics section. ===
=== Next deducing cogent software ===

For candidate modem in PCI bus:  02:02.0
Class 0780: 14f1:2f00 Communication controller: Conexant HSF 56k HSFi Modem
     Primary PCI_id  14f1:2f00
Support type needed or chipset:    hsfmodem



Formal support for Conexant chipset modems are available ONLY through
http://www.linuxant.com/drivers.  Read Conexant.txt for details.
and Modem/YourSystem.txt for follow through guidance.  Driver speed
is limited to
14,400 until a key is purchased.  There is NO freeware alternative.
There are two support package types: hsfmodem  and hcflinmodem.
http://www.lorenzobettini.it/linux/LinuxSonyVaioVGN-S5VP_B reports a
problem and solution in stalling a key, after testing of the free low
speed download.

The hsfmodem package serves a great variety of Conexant chipset modems.
Start at  http://www.linuxant.com/drivers/hsf for
eventually download of a hsfmodem-SomeVersion.zip  package with
SomeVersion containing your kernel_version 2.6.21-gentoo-r2  in the
filename if possible.
These packages have compiled drivers. Otherwise download the generic
hsfmodem-Version.tar.gz  package. Its usage will require compiling.

Read Conexant.txt

Writing Conexant.txt


Completed candidate modem analyses.

The base of the UDEV device file system is: /dev/.udev

Versions adequately match for the compiler installed: 4.1.2
            and the compiler used in kernel assembly: 4.1.2



Compiling resources appear complete:
  make utility - /usr/bin/make
  Compiler version 4.1
  kernel_headers base folder /lib/modules/2.6.21-gentoo-r2/build


Checking pppd properties:
    -r-s--x--x 1 root root 249324 2007-05-29 14:12 /usr/sbin/pppd

In case of an "error 17" "serial loopback" problem, see:
   http://phep2.technion.ac.il/linmodems/archive-sixth/msg02637.html

To enable dialout without Root permission do:
    $ su - root  (not for Ubuntu)
        chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
     chmod a+x /usr/sbin/pppd

Checking settings of:    /etc/ppp/options
lock

In case of a message like:
  Warning: Could not modify /etc/ppp/pap-secrets: Permission denied
see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html

Read Modem/YourSystem.txt concerning other COMM channels: eth0 eth1
Which can interfere with Browser naviagation.

Don't worry about the following, it is for the experts
should trouble shooting be necessary.
==========================================================

Checking for modem support lines:
--------------------------------------
    /device/modem symbolic link:   lrwxrwxrwx 1 root root 8
2007-05-29 15:36 /dev/modem -> ttySHSF0
slmodemd created symbolic link /dev/ttySL0:
    Within /etc/udev/ files:
/etc/udev/rules.d/hsf.rules:KERNEL=="ttySHSF0", SYMLINK="modem", GROUP="dialout"
/etc/udev/rules.d/00-hsf.rules:KERNEL=="ttySHSF0", SYMLINK="modem"
    Within /etc/modprobe.conf files:
alias /dev/modem /dev/ttySHSF
    Within any ancient /etc/devfs files:

    Within ancient kernel 2.4.n /etc/module.conf files:
/etc/modules.conf:alias /dev/modem /dev/ttySHSF
/etc/modules.d/hsf:alias /dev/modem /dev/ttySHSF
--------- end modem support lines --------




 Output of dialing with wvdial:

nick01@T72 ~ $ wvdial pulse
WvDial<*1>: WvDial: Internet dialer version 1.56
WvDial<*1>: Initializing modem.
WvDial<*1>: Sending: ATZ
WvDial Modem<*1>: ATZ
WvDial Modem<*1>: OK
WvDial<*1>: Sending: ATQ0 V1 E1 S0=0 &C1 &D2 W2 +FCLASS=0
WvDial Modem<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 W2 +FCLASS=0
WvDial Modem<*1>: OK
WvDial<*1>: Modem initialized.
WvDial<*1>: Sending: ATDP0870222222
WvDial<*1>: Waiting for carrier.
WvDial Modem<*1>: ATDP0870222222
WvDial Modem<*1>: CONNECT 29333
WvDial<*1>: Carrier detected.  Waiting for prompt.
WvDial Modem<*1>: ~[7f]}#@!}!=} }9}"}&} }*} }
}#}%B#}%}%}&[05]qZ[1e]}'}"}(}"I1~~[7f]}#@!}!>} }9}"}&} }*} }
}#}%B#}%}%}&[05]qZ[1e]}'}"}(}"[05]\~~[7f]}#@!}!?} }9}"}&} }*} }
}#}%B#}%}%}&[05]qZ[1e]}'}"}(}"A}'~~[7f]}#@!}!@} }9}"}&} }*} }
}#}%B#}%}%}&[05]qZ[1e]}'}"}(}"V ~~[7f]}#@!}!A} }9}"}&} }*} }
}#}%B#}%}%}&[05]qZ[1e]}'}"}(}"}2R~~[7f]}#@!}!B} }9}"}&} }*} }
}#}%B#}%}%}&[05]qZ[1e]}'}"}(}"^?~
WvDial<*1>: PPP negotiation detected.
WvDial<Notice>: Starting pppd at Tue May 29 15:37:48 2007
WvDial<Notice>: Pid of pppd: 16263
WvDial<*1>: Using interface ppp0
WvDial<*1>: pppd: Ȭ[06][08]��[06][08]
WvDial<*1>: pppd: Ȭ[06][08]��[06][08]
WvDial<*1>: pppd: Ȭ[06][08]��[06][08]
WvDial<*1>: pppd: Ȭ[06][08]��[06][08]
WvDial<*1>: pppd: Ȭ[06][08]��[06][08]
WvDial<*1>: pppd: Ȭ[06][08]��[06][08]
WvDial<*1>: pppd: Ȭ[06][08]��[06][08]
WvDial<*1>: local  IP address 86.34.73.49
WvDial<*1>: pppd: Ȭ[06][08]��[06][08]
WvDial<*1>: remote IP address 86.34.90.2
WvDial<*1>: pppd: Ȭ[06][08]��[06][08]
WvDial<*1>: primary   DNS address 193.231.100.134
WvDial<*1>: pppd: Ȭ[06][08]��[06][08]
WvDial<*1>: secondary DNS address 193.231.100.130
WvDial<*1>: pppd: Ȭ[06][08]��[06][08]


I haven't yet tried this modem in windows but I can connect with
another V.90 modem at 48000; I'll have to put it in another windows pc
and see. I'll post the results.

[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux