Antonio,
I forward your problem to discuss@xxxxxxxxxxxxx
I am quite confused by your message and suggest a complete reset.
Download the most recent scanModem from
http://linmodems.technion.ac.il/packages
Run again, and send ModemData.txt to discuss@xxxxxxxxxxxxx with a copy
directly to me.
In addition, please report EXACTLY the COMPLETE name of the driver file
which you are trying to use. If you try to install again, make SURE to
have erased any earlier installation of any HSF driver.
FOLKS,
Please read this message. The author says that this thread never reached
the list (true in my archive at least). Please read all his stuff, not
only my answer.
The Saga starts in December 2006 with
http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04938.html
to which my reply was
http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04940.html
based on the following quote in ModemData.txt using scanModem update of:
2006_November_07
"BEGIN
Modem or host audio card candidates have firmware information:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
0000:00:14.2 1002:437b 1025:009f 0403: ATI Technologies Inc:
Unknown device 437b
Modem interrupt assignment and sharing:
209: 15377 0 IO-APIC-level HDA Intel
--- Bootup diagnositcs for card in PCI slot 0000:00:14.2 ----
=== Finished modem firmware and bootup diagnostics section. ===
=== Next deducing cogent software ===
1002:437b is a High Definition Audio card, possibly hosting a soft modem.
For candidate modem in PCI bus: 0000:00:14.2
Class 0403: 1002:437b 0403: ATI Technologies Inc: Unknown device 437b
Primary PCI_id 1002:437b
Subsystem PCI_id 1025:009f
Softmodem codec or Vendor from diagnostics: 14f1, a Conexant type,
from Archives:
"END
Thus all his efforts are based on the asumption that 1002:437b +
1025:009f is a Coenxant device.
NOW ANTONIO'S THREAD:
=====================
ARinaldi@xxxxxxx wrote:
> Dear Jacques,
>
> as you can see I tried to send this follow up two times to the list but it
> did not succeed.
>
> Regards
> Antonio
>
>
> To: discuss@xxxxxxxxxxxxx
> cc:
> bcc:
> Subject: Fw: Re2: Antonio, Italy, Ubuntu 6.06 / 6.10, kernel
> 2.6.15 / 2.6.17, HSF Conexant
> Antonio Maria Rinaldi
>
> 02/22/2007 02:02 PM
> <font size=-1></font>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Dear all,
>
> checking on the discussion list I didn't find my mail, so I'm just
> resending it.
>
> I am however puzzled by the fact that at least one time the modem was
> recognized, and that (searching in the archives) there are many cases of
> same 0x14f12bfa ID modems working, even with older patched drivers.
>
> Best regards
> Antonio
>
>
> ----- Forwarded by Antonio Maria Rinaldi/NOV/MEMC on 22/02/2007 13:57 -----
>
> Antonio Maria Rinaldi
> 21/02/2007 23:00
> To: discuss@xxxxxxxxxxxxx
> cc:
> Subject: Re2: Antonio, Italy, Ubuntu 6.06 / 6.10, kernel
> 2.6.15 / 2.6.17, HSF Conexant
>
> Dear all,
>
> I am resuming an old post of mid december 2006 (original text at the end),
> with a modified subject.
>
> Unfortunately, because of personal issues, I could not follow up with the
> required tests and keeping you updated.
>
> So with the help of scanModem and of Jacques I identified my modem
> (conexant 0x14f12bfa) and installed the linuxant driver, but it didn't work
> even following their troubleshooting, so I wrote to support@xxxxxxxxxxxxx
>
> Following the answer:
>
> -------------------------
>
> Hi,
>
> according to the dump you have provided, it seems that you have HDA
> modem in your system. HDA support in the HSF driver is only enabled on
> 2.6.16 or later kernel but unfortunately, you are running a 2.6.15 kernel.
>
> We recommend that you upgrade to Ubuntu 6.10 (Edgy), you will get a
> 2.6.17 kernel which is supported by the current HDA support in the HSF
> driver.
>
> Regards,
>
> Jonathan
> Technical specialist / Linuxant
> www.linuxant.com
> support@xxxxxxxxxxxx
>
>
> -------------------------
>
> When I got an Ubuntu 6.10 DVD, it was only 32 bit, so I could not simply
> upgrade. Here a few other mails:
>
>
> -------------------------
>
>
> Jonathan,
>
> there was some lapse of time since last, because of personal issues.
> However I downloaded again the appropriate drivers, made room for a new
> partition and installed them on a fresh new setup of Kubuntu 6.10.
> Unfortunately the results were the same. I tried both the deb package and
> the tar one, with installation/compilation ok, but the modem is not
> recognized.
> Below, after preceding mails, find pasted the last hsfdiag output.
>
> This time however I noticed these facts.
>
> - After the installation of the modem drivers, the sound mixer was
> "corrupted" and no sound was available anymore.
>
> - Once, by trying to open the Kmixer, I got again sound functionalities; by
> chance I run hsfdiag -i and the modem was recognized! but I had to leave
> for other business and shutdow an apparently working system.
>
> - At next boot I was in trouble again, and never succeded to get back
> sound.
>
> Thank you for your support.
> Best regards
> Antonio
>
>
> -------------------------
>
>
> Hi,
>
> you have hit a known issue with the driver, we can see these error
> message that flooded your 'dmesg':
>
> ---
> [17180002.468000] hda_codec: invalid dep_range_val 0:7fff
> [17180003.040000] cnxthsf_OsEventWaitTime(e7e8ea00/HDA
> CodecUnsolicitedmessage, 40): returning OSEVENT_WAIT_TIMEOUT
> ---
>
> The problem is sporadic and involves ALSA while probing the HDA bus and
> we hope that this problem will be resolved in the future.
>
> To solve this problem, please make sure that you close all applications
> which are trying to use the sound, this includes the sound mixing applet
> which is often running on desktops system tray. You should run the
> following commands until the problem is resolved:
>
> ---
> sudo hsfstop
> sudo hsfconfig -i
> ---
>
> Regards,
>
> Jonathan
>
>
> -------------------------
>
>
> Jonathan,
>
> thank you for the reply, but it didn't work.
> I tried it a few times, also waiting more than a minute after closing the
> sound mixer (because of the setup that frees the sound resources after some
> inactivity) and no other programs running, nothing changed in the hsfconfig
> info.
> Please note however that the only time that I described it was with the
> sound functioning (an that now I can open he mixer but it doesn't work).
>
> Regards
> Antonio
>
>
> -------------------------
>
>
> Hi,
>
> the workaround I have described is not effective on all system
> unfortunately. We hope that this problem will be resolved in a future
> version of the driver.
>
> Regards,
>
> Jonathan
>
>
> -------------------------
>
>
> The latest driver version used in these tests is hsfmodem_7.60.00.01
> full_k2.6.17_10.
>
> At the end let me a few annotations:
>
> - my appreciations again to linmodems (and Jacques being the direct
> contact) for the detailed and speedy support; now scanModem recognises also
> this modem;
>
> - even if the driver does not work for my case, linuxant was also
> supportive and Jonathan answered each time within a day;
>
> - I will keep an eye on those drivers and keep posted the group should
> anything new happen;
>
> - if I get time I will try the driver cited in Ubuntu
> DialupModemHowto/Conexant (it appears not at working level, I found a
> thread in kubuntuforum with patches etc.);
>
> - hope all this may be of help to somebody else!
>
> Regards
> Antonio
>
>
>
>
> -----------------------------------------------------------
>
> Jacques Goldberg <Jacques.Goldberg@xxxxxxx>
> 14/12/2006 18:54
> Please respond to discuss
> To: arinaldi@xxxxxxx
> cc: DISCUSS@xxxxxxxxxxxxx
> Subject: Re: Antonio, Italy Ubuntu 6.06 LTS kernel
> 2.6.15-23-amd64-generic
>
>
> Dear Antonio
>
> Not trivial but not terrible.
> You need the Linuxant HSF driver (details attached)
> But there is no precompiled driver ready to install for your amd64
> processor.
> If you follow the instructions which I have attached you will reach
> SOURCES by selecting Download from the HSF menu of the Linuxant page
> quoted in the attachment,
> There you will find the following file, last in the "Generic packages
> with source" list:
> TAR x86_64 hsfmodem-7.47.00.05x86_64full.tar.gz
> (for other 64-bit systems with AMD64/EM64T extensions)
> which you have to compile following the instructions given in that file
> and under the Installation link of the HSF menu.
> To use the file after downloading you just type
> tar zxf hsfmodem-7.47.00.05x86_64full.tar.gz
> and cd hsfmodem-7.47.00.05x86_64full
> You will find what you need.
> What I do not know is whether you do have the EM64T extensions.
> In the worst case that you do not know either, just try!
> You will need to install some kernel sources if not already done.
>
> If you fail, you will let we know for sure.
> Please do the same if you succeed, for the next user in the same situation.
>
> Ciao - Jacques
>
> arinaldi@xxxxxxx wrote:
>>
> If you do not already know, find out in your ModemData.txt if your modem
> is of
> type HSF or of type HCF.
> In the following, HxF stands for the one to be used.
> Note down your distribution, your processor, and your kernel (shown in the
> System Information section of ModemData.txt).
> -Go to http://www.linuxant.com/drivers
> -Find the HxF menu in the left part of the screen.
> -Read README.
> -Read INSTALLATION.
> -Click DOWNLOAD.
> -Accept conditions.
> -Find text: "You can download HxF modem packages from the driver
> download page." and click on that link.
> -I very strongly recommend NOT TO LET YOURSELF BE ATTRACTED BY THE
> AUTOMATIC
> INSTALLER cnxtinstall.run. Just think: you need a connection to be able to
> use
> it, and this is what you do not have yet. Use the direct download page.
> Its address is http://www.linuxant.com/drivers/hsf/full/downloads.php
> Using it will not save you any time, on the contrary, because you will not
> know
> what to look for and do with it.
> -Since you have noted your distribution, your processor, and your kernel
> (shown in the System Information section of ModemData.txt), identify the
> matching file.
> -Download the matching file.
> -Read again and, if you read this text under Windows, print the
> installation
> instructions matching the kind of driver file which you downloaded.
> -If downloaded elsewhere (Windows on same computer or using an other
> computer),
> copy the downloaded file to your Linux working space.
> -Now, under Linux, just follow the Linuxant installation instructions.
>
> NOTE: the space on a floppy disk is sufficient for the driver file. This
> is the simplest way to download under Windows on the same computer or to
> download on an other computer.
> More tips to transfer files are available in
> http://linmodems.technion.ac.il/first.html
>
>
>
>
>
>
