Re: Antonio Rodulfo, Spain, kernel 2.6.38-11-generic, amd64 distro

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

 



AR

for x86_64 systems you can use hsfmodem-7.80.02.06x86_64full.tar.gz
found near the bottom of http://www.linuxant.com/drivers/hsf/full/downloads.php
Unpack with
$ tar zxf hsf*.tar.ggz
and follow the instructions in the new folder exposed.

You way be informed that it is also necessary to install  from
http://www.linuxant.com/alsa-driver/ the
	alsa-driver-linuxant_1.0.23.1_all.deb.zip ,  in which case.
$ unzip driver*.zip
$ dpkg -i driver *. deb
and again start the hsfmodem install.

If the is a mismatch between ALSA versions of the Linuxant and
packages, you may lose audio support.
But let's deal with that later.

MarvS
scanModem maintainer

On Thu, Oct 6, 2011 at 2:08 PM, Antonio Rodulfo
<antonio.rodulfo@xxxxxxxxx> wrote:
> Dear Antonio,
>
> Thank you so much for your quick answer.
> I have reviewed the options available at Linuxant's and, sadly,
> there's no exact package for 2.38.11. In fact, the latest available
> package seems to match 2.31.17.
> Moreover, it seems to correspond to the x86, i.e., 32 bits kernel.
>
> As far as the web is concerned, I have two options: on the one hand, I
> can download the available package and try to install and use it
> (maybe I should cross my fingers?); on the other hand, I can download
> the generic package and do my best (not that much, for the time being,
> given my small experience) to get a proper driver compiled /
> installed.
> What would you recomend?
>
> In case I decide to use the generic package:
> * is it enough for me to have the proper headers installed or do I
> need to have the full kernel source?
> * given the fact I'm using the 64 bits system, shouldn't I use the
> x86_64 generic package?
>
> Thanks a lot in advance.
>
> --
> Un saludo,
> Kind regards,
>
> Antonio Rodulfo
> Ingeniero Industrial, Consultor de Proyectos
> Industrial Engineer, Project Consultant
>
>
>
> 2011/10/6 Antonio Olivares <olivares14031@xxxxxxxxx>:
>> Antonio,
>>
>> scanModem reports that your modem is supported by hsfmodem drivers.
>> The snd_hda_intel driver is for sound and for certain modems supported
>> by SLMODEMD variants.
>>
>> Predictive  diagnostics for card in bus 00:1b.0:
>>        Modem chipset  detected on
>> NAME="Audio device: Intel Corporation N10/ICH 7 Family High Definition
>> Audio Controller "
>> CLASS=0403
>> PCIDEV=8086:27d8
>> SUBSYS=152d:0753
>> IRQ=46
>> HDA2=00:1b.0
>> SOFT=8086:27d8.HDA
>> ArchivedChip=0x14f12bfa
>> CodecClass=14f1
>> IDENT=hsfmodem
>> Driver=hsfmodem-drivers
>>
>>  For candidate modem in:  00:1b.0
>>   0403 Audio device: Intel Corporation N10/ICH 7 Family High
>> Definition Audio Controller
>>      Primary device ID:  8086:27d8
>>    Subsystem PCI_id  152d:0753
>>    Softmodem codec or chipset from diagnostics:
>>                               from    Archives: 0x14f12bfa
>>
>>
>>
>> Support type needed or chipset: hsfmodem
>>
>>
>> Writing DOCs/Intel.txt
>>
>> For owners of a Dell PCs with Conexant HSF modems, a driver source
>> package with full speed enabled is available, but requires driver
>> compiling. Read DOCs/Conexant.txt
>>
>>
>> Modem support packages from Linuxant include resources for compiling drivers.
>> If an installer package matching your kernel_version  is not provided,
>> just install a generic code package.
>>
>>  From  http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
>>  download hsfmodem-7.80.02.05full_k2.6.38_11_generic_ubuntu_i386.deb.zip
>>  Under Linux unpack with:
>>  $ unzip hsfmodem*.zip
>>  Then install with:
>>  $ sudo dpkg -i hsfmodem*.deb
>>  Subsequently, the modem should be found with
>>  $ sudo wvdialconf /etc/wvdial.conf
>>  Edit in your personal information with:
>>  $ sudo gedit /etc/wvdial.conf
>>  and try dialing out with:
>>  $ sudo wvdial.
>>  See DOCs/Testing.txt  for details.
>>
>> Download generic package:
>>
>> http://www.linuxant.com/drivers/hsf/full/archive/hsfmodem-7.80.02.06full/hsfmodem_7.80.02.06full_i386.deb.zip
>> and follow instructions provided
>>
>> METHOD B: DEBIAN PACKAGE (*.deb)
>> If you have obtained the driver package in DEBIAN format:
>>
>> 1. install the package with "dpkg -i hsfmodem_{version}_{arch}.deb",
>> if apt-get or some other tool hasn't already done it for you.
>>
>> 2. if necessary, run "hsfconfig" to complete the installation, enter
>> license information, or to change your modem's configuration.
>>
>> If you need to rebuild the Debian generic package from source, you can
>> get the TAR package, and from the top directory run: "make debdist". A
>> pre-compiled DEB package for the currently running kernel can be built
>> using "make debprecomp" instead.
>>
>> http://www.linuxant.com/drivers/hsf/install.php
>>
>> Sadly you appear to also have a Modem Interrupt assignment which may
>> affect the drivers, if you install the driver and your modem is
>> nonresponsive please send us output of dmesg as it says here:
>>
>> For candidate card in slot 00:1b.0, firmware information and bootup
>> diagnostics are:
>>  PCI slot       PCI ID          SubsystemID     Name
>>  ----------     ---------       ---------       --------------
>>  00:1b.0        8086:27d8       152d:0753       Audio device: Intel Corporation N10/ICH 7
>> Family High Definition Audio Controller
>>
>>  Modem interrupt assignment and sharing:
>>  46:        449          0   PCI-MSI-edge      hda_intel
>>  --- Bootup diagnostics for card in PCI slot 00:1b.0 ----
>> [    0.421621] pci 0000:00:1b.0: [8086:27d8] type 0 class 0x000403
>> [    0.421621] pci 0000:00:1b.0: reg 10: [mem 0xde300000-0xde303fff 64bit]
>> [    0.421621] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
>> [    0.421621] pci 0000:00:1b.0: PME# disabled
>> [   13.536785] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level,
>> low) -> IRQ 22
>> [   13.536846] HDA Intel 0000:00:1b.0: irq 46 for MSI/MSI-X
>> [   13.536874] HDA Intel 0000:00:1b.0: setting latency timer to 64
>> [46062.850301] HDA Intel 0000:00:1b.0: PCI INT A disabled
>> [46062.870026] PM: freeze of drv:HDA Intel dev:0000:00:1b.0 complete
>> after 129.960 msecs
>> [46063.320332] HDA Intel 0000:00:1b.0: restoring config space at
>> offset 0x1 (was 0x100006, writing 0x100002)
>> [46063.419918] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level,
>> low) -> IRQ 22
>> [46063.419930] HDA Intel 0000:00:1b.0: setting latency timer to 64
>> [46063.420029] HDA Intel 0000:00:1b.0: irq 46 for MSI/MSI-X
>> [51232.280187] HDA Intel 0000:00:1b.0: PCI INT A disabled
>> [51232.300025] PM: freeze of drv:HDA Intel dev:0000:00:1b.0 complete
>> after 128.907 msecs
>> [51232.750333] HDA Intel 0000:00:1b.0: restoring config space at
>> offset 0x1 (was 0x100006, writing 0x100002)
>> [51232.849917] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level,
>> low) -> IRQ 22
>> [51232.849929] HDA Intel 0000:00:1b.0: setting latency timer to 64
>> [51232.850033] HDA Intel 0000:00:1b.0: irq 46 for MSI/MSI-X
>> [76807.210217] HDA Intel 0000:00:1b.0: PCI INT A disabled
>> [76807.230028] PM: freeze of drv:HDA Intel dev:0000:00:1b.0 complete
>> after 126.607 msecs
>> [76807.760333] HDA Intel 0000:00:1b.0: restoring config space at
>> offset 0x1 (was 0x100006, writing 0x100002)
>> [76807.858066] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level,
>> low) -> IRQ 22
>> [76807.858078] HDA Intel 0000:00:1b.0: setting latency timer to 64
>> [76807.858155] HDA Intel 0000:00:1b.0: irq 46 for MSI/MSI-X
>> [87584.890190] HDA Intel 0000:00:1b.0: PCI INT A disabled
>> [87584.910024] PM: freeze of drv:HDA Intel dev:0000:00:1b.0 complete
>> after 122.420 msecs
>> [87585.370333] HDA Intel 0000:00:1b.0: restoring config space at
>> offset 0x1 (was 0x100006, writing 0x100002)
>> [87585.461165] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level,
>> low) -> IRQ 22
>> [87585.461176] HDA Intel 0000:00:1b.0: setting latency timer to 64
>> [87585.461254] HDA Intel 0000:00:1b.0: irq 46 for MSI/MSI-X
>> [123722.470213] HDA Intel 0000:00:1b.0: PCI INT A disabled
>> [123722.490027] PM: freeze of drv:HDA Intel dev:0000:00:1b.0 complete
>> after 125.325 msecs
>> [123723.030325] HDA Intel 0000:00:1b.0: restoring config space at
>> offset 0x1 (was 0x100006, writing 0x100002)
>> [123723.125473] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level,
>> low) -> IRQ 22
>> [123723.125486] HDA Intel 0000:00:1b.0: setting latency timer to 64
>> [123723.125563] HDA Intel 0000:00:1b.0: irq 46 for MSI/MSI-X
>> [171941.990190] HDA Intel 0000:00:1b.0: PCI INT A disabled
>> [171942.010031] PM: freeze of drv:HDA Intel dev:0000:00:1b.0 complete
>> after 129.819 msecs
>> [171942.540332] HDA Intel 0000:00:1b.0: restoring config space at
>> offset 0x1 (was 0x100006, writing 0x100002)
>> [171942.639816] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level,
>> low) -> IRQ 22
>> [171942.639828] HDA Intel 0000:00:1b.0: setting latency timer to 64
>> [171942.639901] HDA Intel 0000:00:1b.0: irq 46 for MSI/MSI-X
>> [219683.870202] HDA Intel 0000:00:1b.0: PCI INT A disabled
>> [219683.890029] PM: freeze of drv:HDA Intel dev:0000:00:1b.0 complete
>> after 123.755 msecs
>> [219684.470333] HDA Intel 0000:00:1b.0: restoring config space at
>> offset 0x1 (was 0x100006, writing 0x100002)
>> [219684.570243] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level,
>> low) -> IRQ 22
>> [219684.570255] HDA Intel 0000:00:1b.0: setting latency timer to 64
>> [219684.570328] HDA Intel 0000:00:1b.0: irq 46 for MSI/MSI-X
>> [271116.110195] HDA Intel 0000:00:1b.0: PCI INT A disabled
>> [271116.130029] PM: freeze of drv:HDA Intel dev:0000:00:1b.0 complete
>> after 129.850 msecs
>> [271116.630347] HDA Intel 0000:00:1b.0: restoring config space at
>> offset 0x1 (was 0x100006, writing 0x100002)
>> [271116.727148] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level,
>> low) -> IRQ 22
>> [271116.727160] HDA Intel 0000:00:1b.0: setting latency timer to 64
>> [271116.727233] HDA Intel 0000:00:1b.0: irq 46 for MSI/MSI-X
>> [298911.650215] HDA Intel 0000:00:1b.0: PCI INT A disabled
>> [298911.670027] PM: freeze of drv:HDA Intel dev:0000:00:1b.0 complete
>> after 128.981 msecs
>> [298912.220335] HDA Intel 0000:00:1b.0: restoring config space at
>> offset 0x1 (was 0x100006, writing 0x100002)
>> [298912.310282] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level,
>> low) -> IRQ 22
>> [298912.310294] HDA Intel 0000:00:1b.0: setting latency timer to 64
>> [298912.310367] HDA Intel 0000:00:1b.0: irq 46 for MSI/MSI-X
>> [350457.090193] HDA Intel 0000:00:1b.0: PCI INT A disabled
>> [350457.110027] PM: freeze of drv:HDA Intel dev:0000:00:1b.0 complete
>> after 123.903 msecs
>> [350457.570330] HDA Intel 0000:00:1b.0: restoring config space at
>> offset 0x1 (was 0x100006, writing 0x100002)
>> [350457.663155] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level,
>> low) -> IRQ 22
>> [350457.663167] HDA Intel 0000:00:1b.0: setting latency timer to 64
>> [350457.663241] HDA Intel 0000:00:1b.0: irq 46 for MSI/MSI-X
>> [401399.270191] HDA Intel 0000:00:1b.0: PCI INT A disabled
>> [401399.290040] PM: freeze of drv:HDA Intel dev:0000:00:1b.0 complete
>> after 125.578 msecs
>> [401399.750334] HDA Intel 0000:00:1b.0: restoring config space at
>> offset 0x1 (was 0x100006, writing 0x100002)
>> [401399.850097] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level,
>> low) -> IRQ 22
>> [401399.850109] HDA Intel 0000:00:1b.0: setting latency timer to 64
>> [401399.850180] HDA Intel 0000:00:1b.0: irq 46 for MSI/MSI-X
>>
>>  The PCI slot 00:1b.0 of the modem card may be disabled early in
>>  a bootup process,  but then enabled later. If modem drivers load
>>  but the  modem is not responsive, read DOCs/Bootup.txt about possible fixes.
>>  Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx
>>  if help is needed.
>>
>>
>> Regards,
>>
>> Antonio
>>
>> On Thu, Oct 6, 2011 at 9:54 AM, Antonio Rodulfo
>> <antonio.rodulfo@xxxxxxxxx> wrote:
>>> Dear all,
>>>
>>> I've just dowloaded scanModem from your web page, uncompressed and
>>> executed it in my system.
>>> Attached you'll find the ModemData.txt it has just produced.
>>>
>>> I'm not "afraid" of the file and its contents. However, I can't
>>> properly interpret it. It says "Potentially useful modem drivers now
>>> loaded are: snd_hda_intel", but it doesn't conclude if the driver is
>>> properly supporting the modem or not, nor have I any clue on how to
>>> actually test it.
>>>
>>> Please help!
>>> --
>>> Un saludo,
>>> Kind regards,
>>>
>>> Antonio Rodulfo
>>> Ingeniero Industrial, Consultor de Proyectos
>>> Industrial Engineer, Project Consultant
>>>
>>
>



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

  Powered by Linux