All,
here are results and status of latest tests for this thread.
- Installation of ALSA 1.0.14rc1 went smoothly. The system configuration
reports
Sound Driver:3.8.1a-980706 (ALSA v1.0.14rc1 emulation code)
and sound system is functioning.
- I installed then the latest version of linuxant driver,
hsfmodem_7.60.00.02full_k2.6.17_10_generic_ubuntu_i386.deb .
Unfortunately the results are the same as previously; I tried also loading
ungrab-winmodem before driver installation, reboot, and several repetitions
of "hsfstop; hsfconfig -i", nothing different.
Jonathan,
I have two questions:
- do you have any idea on the possible next driver release addressing this
bug?
- as I described, it was only once but the modem was recognized by
hsfconfig -i; I would like to understand why. It seems to me that such fact
would indicate the issue is more related to module loading sequence, and
thus should have a relatively simple solution.
Marv,
when I run scanModem after the ALSA upgrade, I found that it still reports
the original distribution driver, i.e. "ALSAversion 1.0.11".
I thought also to try anyway the slmodem approach, by downloading and
installing slamr-2.6.17-10-generic.tar.gz . Following the terminal output:
============================
$ sudo ./setup
When asked about your country, Enter:
USA
Installing the Debian packages supporting autoloading
Selecting previously deselected package sl-modem-daemon.
(Reading database ... 81151 files and directories currently installed.)
Unpacking sl-modem-daemon (from sl-modem-daemon_2.9.10+2.9.9
d+e-pre2-5build1_i386.deb) ...
Setting up sl-modem-daemon (2.9.10+2.9.9d+e-pre2-5build1) ...
FATAL: Module slamr not found.
Starting SmartLink Modem driver for: auto.
Creating /dev/modem symlink, pointing to: /dev/ttySL0.
Copying over newer files
cp: cannot stat `sl-modem-daemon.modutils': No such file or directory
Making folder /lib/modules/2.6.17-10-generic/extra
Copying drivers to /lib/modules/2.6.17-10-generic/extra
Checking driver install
slamr.ko slusb.ko ungrab-winmodem.ko
Finished installs.
Informing the System
Starting function tests, loading drivers:
Running diagnostic:
[17186809.896000] slamr: SmartLink AMRMO modem.
ports should be created by:
slmodemd -c USA /dev/slamr0
error: mdm setup: cannot open dev `/dev/slamr0': No such device
error: cannot setup device `/dev/slamr0'
Checking for success
Port creation with slmodemd failed.
Read the Slamr.txt record, other 1st_Read.txt CountryList.txt wvdial.txt
files and the sample wvdial.conf.
============================
I have noted three issues, I don't know if they are real or simply an
effect of the driver being incorrect for the modem (I apologize if that
should be the case).
- for my case scanModem doesn't provide the device specification N to use
for slmodemd --alsa hw:0,N
- there is the message "FATAL: Module slamr not found." but the module is
there, as output a few lines after; in fact when loading slamr before $
sudo ./setup I get the same output as before except that there are two
instances of the module, the second one being
[17187467.824000] slamr: SmartLink AMRMO modem.
- the last indication is "Read the Slamr.txt record", but I was not able to
find the file.
Thanks to all for the follow up so far.
Regards
Antonio
"Linuxant
support To: Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>
(Jonathan)" cc: "arinaldi@xxxxxxx" <arinaldi@xxxxxxx>, discuss@xxxxxxxxxxxxx
<support@linuxan Subject: Re: Fw: Re2: Antonio, Italy, Ubuntu 6.06 / 6.10, kernel 2.6.15 / 2.6.17, HSF
t.com> Conexant
09/03/2007 19:40
Hi,
the version of ALSA currently being used by the driver can be determined
with the changelog available at:
http://www.linuxant.com/drivers/hsf/changes.php
If the version of ALSA used by the driver really becomes a problem, we
could display it in the output of the 'hsfconfig --info' command for
example. However, fixing the actual problem(s) is a better solution.
Regards,
Jonathan
Technical specialist / Linuxant
www.linuxant.com
support@xxxxxxxxxxxx
Marvin Stodolsky wrote:
> Jonathan,
> Thanks. It would be usefull if the ALSA version used in the
> hsfmodem packages was posted somewhere and also output by hsfmodem
> during its installation.
>
> Antonio,
> You can follow the same update instructions
> http://linmodems.technion.ac.il/archive-seventh/msg00282.html
> Just use the version 1.0.14rc1 lib and driver package rather than the
> 1.0.13
> I initially suggested.
>
> MarvS
>
> On 3/8/07, Linuxant support (Jonathan) <support@xxxxxxxxxxxx> wrote:
>> Hi,
>>
>> the current version of the HSF driver, 7.60.00.02 is based on ALSA
>> 1.0.14rc1. Even if the user changes the version of ALSA used by the
>> kernel, since the HSF driver will replace the HDA related modules
>> (snd-hda-intel and snd-hda-codec), it will have no effect.
>>
>> Regards,
>>
>>
>> Jonathan
>> Technical specialist / Linuxant
>> www.linuxant.com
>> support@xxxxxxxxxxxx
>>
>>
>>
>> Marvin Stodolsky wrote:
>> > Antonio
>> >
>> > There are instructions for upgrading snd-hda-intel and its
>> > dependent driver set at
>> > http://linmodems.technion.ac.il/archive-seventh/msg00282.html
>> > You can try upgrading to the version 1.0.13
>> > Perhaps this will bring a fix to the problem.
>> >
>> > MarvS
>> >
>> > On 3/7/07, Linuxant support (Jonathan) <support@xxxxxxxxxxxx> wrote:
>> >> Hi,
>> >>
>> >> we can see a lot of these error messages in your 'dmesg':
>> >>
>> >> ---
>> >> [17179987.384000] hda_codec: invalid dep_range_val 0:7fff
>> >> [17179987.800000] cnxthsf_OsEventWaitTime(d9ef38e0/HDA
>> >> CodecUnsolicitedmessage, 40): returning OSEVENT_WAIT_TIMEOUT
>> >> ---
>> >>
>> >> This is a known issue on some systems with HDA modems. As far as we
>> >> know, this is a HDA probing issue in the ALSA code shipped with the
>> >> driver and we hope that it will be fixed in a future release of the
>> >> driver.
>> >>
>> >> As you have mentioned, doing multiple times this command:
>> >>
>> >> ---
>> >> sudo hsfstop; sudo hsfconfig -i
>> >> ---
>> >>
>> >> can be used as a workaround but it doesn't work on all systems
>> >> unfortunately.
>> >>
>> >> Since you have a HDA sound device and since the HSF driver did
replace
>> >> the complete HDA driver, it is normal that sound is no longer
working.
>> >> For the time being, if you want to recover your sound, please
>> uninstall
>> >> the driver with the 'sudo hsfconfig --uninstall' command and reboot
>> your
>> >> system.
>> >>
>> >> Regards,
>> >>
>> >>
>> >> Jonathan
>> >> Technical specialist / Linuxant
>> >> www.linuxant.com
>> >> support@xxxxxxxxxxxx
>> >>
>> >>
>> >>
>> >> Marvin Stodolsky wrote:
>> >> > Jonathan
>> >> >
>> >> > This is an:
>> >> >> PCI slot PCI ID SubsystemID Name
>> >> >> ---------- --------- --------- --------------
>> >> >> 00:14.2 1002:437b 1025:009f Audio device: ATI
>> Technologies Inc
>> >> >
>> >> >> /proc/asound/SB/codec#1:Vendor Id: 0x14f12bfa
>> >> >> /proc/asound/card0/codec#1:Vendor Id: 0x14f12bfa
>> >> > System which is not being recogized by your hsfmodem package.
>> >> > Details below.
>> >> >
>> >> > MarvS
>> >> >
>> >> >
>> >> > On 3/5/07, arinaldi@xxxxxxx <arinaldi@xxxxxxx> wrote:
>> >> >>
>> >> >> Dear all,
>> >> >>
>> >> >> following the details according to the instructions of Jacques.
>> >> >>
>> >> >> - accurate removal of previous driver installation;
>> >> >>
>> >> >> - downloaded latest scanModem;
>> >> >>
>> >> >> - run it and appending below ModemData.txt;
>> >> >>
>> >> >> - installed
>> hsfmodem_7.60.00.01full_k2.6.17_10_generic_ubuntu_i386.deb
>> >> >> installation OK with the quite normal message:
>> >> >>
>> >> >> Warning: no device detected by hsf driver - HDA modems may require
>> >> reboot
>> >> >> Note: kernel module snd-via82xx-modem overridden by hsfmc97via
>> >> >> Note: kernel module snd-intel8x0m overridden by hsfmc97ich
>> hsfmc97sis
>> >> >> Note: kernel module snd-atiixp-modem overridden by hsfmc97ati
>> >> >>
>> >> >> and sound system stopped functioning;
>> >> >>
>> >> >> - full system reboot but nothing changed;
>> >> >>
>> >> >> - tried as instructed by Linuxant:
>> >> >>
>> >> >> disabling the sound system,
>> >> >> sudo hsfstop
>> >> >> sudo hsfconfig -i
>> >> >>
>> >> >> the system spends more time in executing the second instruction
>> but no
>> >> >> way
>> >> >> to have modem recognized (repeated also after reboot).
>> >> >>
>> >> >> - Removing the driver the sound system is working again (after
>> >> reboot).
>> >> >>
>> >> >> - For completness I am appending below part of hsfdiag.txt.
>> >> >>
>> >> >> - This modem appears however to be a conexant, as windows drivers
>> >> >> state so
>> >> >> (I added that output to my first mail, but I have seen now that
>> it was
>> >> >> truncated on pasting by my mail client); I can resend it if
>> required.
>> >> >>
>> >> >>
>> >> >> Marvin,
>> >> >>
>> >> >> sorry for the inconvenience of the html format, I was sending
those
>> >> two
>> >> >> mails from a different location and was not aware of the setting.
>> >> Hope it
>> >> >> is OK now.
>> >> >>
>> >> >>
>> >> >> Thanks for your attention. Regards
>> >> >> Antonio
>> >>
>>
