Re: haven't gotten drivers to work

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

 



If the Dell drivers failed, unintstall them.
Then from http://www.linuxant.com/drivers/hsf/full/downloads.php  try the newer:
hsfmodem-7.68.00.10x86_64full-1.x86_64.rpm.zip

Under Linux
$ unzip hsf*.zip
Then use the SuSE tools to install the
hsfmodem-7.68.00.10x86_64full-1.x86_64.rpm

MarvS
scanModem maintainer

On Wed, Jun 11, 2008 at 8:52 PM, Brad McManigal <bjmnet@xxxxxxxxx> wrote:
> Predictive diagnostics for card in bus 02:00.0:
>        Modem chipset  detected on
> CLASS="Class 0780: 14f1:2f20"
> NAME="Communication controller: Conexant HSF 56k Data/Fax Modem"
> SUBSYS=14f1:2000
> PCIDEV=14f1:2f20
> IRQ=11
> IDENT=hsfmodem
>
>  For candidate modem in:  02:00.0
>   Class 0780: 14f1:2f20 Communication controller: Conexant HSF 56k Data/Fax
> Modem
>      Primary device ID:  14f1:2f20
>  Support type needed or chipset:        hsfmodem
>
>
> I have downloaded and run scanmodem as you can see with the output file.  I
> then went to the dell website as recommended in modemdata.txt, or one of the
> other output files. I retrieved the 64bit drivers from there, got them
> unpacked and tried to install them but I still have nothing.  I looked into
> getting the driver from the linuxant site but it seemed to be the same as on
> dell's.  I am pretty new, so maybe I unpacked it in the wrong spot or
> installed it impropperly, or need a 32bit driver.
> Any help is greatly appreciated and include as many details about directory
> locations and exact commands as possible.
> Thanks,
> Brad
>
>  Only plain text email is forwarded by the  Discuss@xxxxxxxxxxxxx List
> Server,
>  as HTML can contain viruses. Use as the email Subject Line:
>           YourName, YourCountry
> Welcome to openSUSE 10.3 (X86-64) - Kernel  kernel 2.6.22.5-31-default
>  With this Subject Line cogent experts will be alerted, and useful case
> names left in the Archive.
>  YourCountry will enable Country specific guidance. Linux experts in
> YourCountry
>  can be found through: http://www.linux.org/groups/index.html.
> They will know your Country's modem code, which may be essential for dialup
> service.
> Responses from Discuss@xxxxxxxxxxxxx are sometimes blocked by an Internet
> Provider mail filters.
>  So in a day, also check the Archived responses at http://www.linmodems.org
> --------------------------  System information ----------------------------
> CPU=x86_64,
> Welcome to openSUSE 10.3 (X86-64) - Kernel
> Linux version 2.6.22.5-31-default (geeko@buildhost) (gcc version 4.2.1 (SUSE
> Linux)) #1 SMP 2007/09/21 22:29:00 UTC
>  scanModem update of:  2008_06_05
>
>
> Some modem drivers can only be used in 32 bit modem on x86_64 systems,
> while some others are competent on x86_64 Systems.  Cases are:
> 1) http://linmodems.technion.ac.il/bigarch/archive-seventh/msg03119.html
> for the snd-hda-intel audio+modem driver. Also applicable to AC97 modem
> controllers.
> In both cases, 32 bit libraries must be installed to support the slmodemd
> helper having a precompiled 32 bit component.
> 2) For USB modems using the slusb.ko driver. 32 bit libraries must be
> installed to support the slmodemd helper having a precompiled 32 bit
> component
> 3) The hsfmodem and hcflinmodem drivers for Conexant chipsest modes are
> x86_64 competent.
>
>  There are no blacklisted modem drivers in /etc/modprobe*  files
> Attached USB devices are:
>  ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
>  ID 058f:9360 Alcor Micro Corp.
>
> USB modems not recognized
>
> For candidate card in slot 02:00.0, firmware information and bootup
> diagnostics are:
>  PCI slot       PCI ID          SubsystemID     Name
>  ----------     ---------       ---------       --------------
>  02:00.0        14f1:2f20       14f1:2000       Communication controller:
> Conexant HSF 56k Data/Fax Modem
>
>  Modem interrupt assignment and sharing:
>  --- Bootup diagnostics for card in PCI slot 02:00.0 ----
>
> For candidate card in slot 00:14.2, firmware information and bootup
> diagnostics are:
>  PCI slot       PCI ID          SubsystemID     Name
>  ----------     ---------       ---------       --------------
>  00:14.2        1002:437b       1462:7248       Audio device: ATI
> Technologies Inc SB450 HDA Audio
>
>  Modem interrupt assignment and sharing:
>  16:      13994          0   IO-APIC-fasteoi   sata_sil, HDA Intel
>  --- Bootup diagnostics for card in PCI slot 00:14.2 ----
> ACPI: PCI Interrupt 0000:00:14.2[A] -> GSI 16 (level, low) -> IRQ 16
> ACPI: PCI interrupt for device 0000:00:14.2 disabled
> PM: Writing back config space on device 0000:00:14.2 at offset f (was 10a,
> writing a)
> PM: Writing back config space on device 0000:00:14.2 at offset 1 (was
> 4100006, writing 4100002)
> ACPI: PCI Interrupt 0000:00:14.2[A] -> GSI 16 (level, low) -> IRQ 16
>
>  The PCI slot 00:14.2 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.
>
>
>
> ===== Advanced Linux Sound Architecture (ALSA) diagnostics =====
> The ALSA packages provide audio support and also drivers for some modems.
> ALSA diagnostics are written during bootup to /proc/asound/ folders.
>  PCI slot 00:14.2 has a High Definition Audio Card
>  ---ALSA bootup diagnostics ---
>
> The ALSA verion is 1.0.14
> The modem cards detected by "aplay -l"  are: None
>
>
> The /proc/asound/pcm file reports:
> -----------------------
> 00-00: ALC861 Analog : ALC861 Analog : playback 1 : capture 2
>
> about /proc/asound/cards:
> ------------------------
>  0 [SB             ]: HDA-Intel - HDA ATI SB
>                      HDA ATI SB at 0xfdff4000 irq 16
> === Finished firmware and bootup diagnostics, next deducing cogent software.
> ===
>
> Predictive diagnostics for card in bus 02:00.0:
>        Modem chipset  detected on
> CLASS="Class 0780: 14f1:2f20"
> NAME="Communication controller: Conexant HSF 56k Data/Fax Modem"
> SUBSYS=14f1:2000
> PCIDEV=14f1:2f20
> IRQ=11
> IDENT=hsfmodem
>
>  For candidate modem in:  02:00.0
>   Class 0780: 14f1:2f20 Communication controller: Conexant HSF 56k Data/Fax
> Modem
>      Primary device ID:  14f1:2f20
>  Support type needed or chipset:        hsfmodem
>
>
>
> 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
>
>  Start at  http://www.linuxant.com/drivers/hsf/full for
>  eventually download of a hsfmodem-7.68.00.07full_k.???.zip package
>  with ??? the package type (deb, rpm, tar etc)
>  These packages have compiled drivers but will also compile a driver,
>  if there is a mismatch between the resident kernel and provided driver.
>  The generic hsfmodem-7.68.00.07full.tar.gz package only provides compiling
> support
>
>  Read DOCs/Conexant.txt
>
> Writing DOCs/Conexant.txt
>
>
>
> Predictive diagnostics for card in bus 00:14.2:
>        Modem chipset not detected on
> CLASS="Class 0403: 1002:437b"
> NAME="Audio device: ATI Technologies Inc SB450 HDA Audio "
> SUBSYS=1462:7248
> PCIDEV=1002:437b
> IRQ=16
> HDA=1002:437b
> SOFT=1002:437b.HDA
>
>
>  High Definition Audio (HDA) cards MAY host a modem chip in their Subsystem,
>  and many are supported by the ALSA audio+modem driver snd-hda-intel
>  A modem was not detected on HDA card 1002:437b.
>  If another modem card is present, then most likely 1002:437b does not host
> a modem.
>  If another modem card has not been detected, then possibilities are:
>        1) A Conexant modem chip is present on 1002:437b, as Conexant chips
>  are frequently not detectable by ALSA diagnostics
>        2) The modem may be of the older non-PCI Controller Chipset
> (hardware) type.
> Try detection with Root permission:
>         wvdialconf  /etc/wvdial.conf
>
>  For candidate modem in:  00:14.2
>   Class 0403: 1002:437b Audio device: ATI Technologies Inc SB450 HDA Audio
>      Primary device ID:  1002:437b
>    Subsystem PCI_id  1462:7248
>    Softmodem codec or chipset from diagnostics:
>                               from    Archives:
>
>
>
> Support type needed or chipset:
>
> Support can likely be achieved through two mutually exclusive alternatives:
> 1) The hsfmodem software for Conexant chipset modems: Read DOCs/Conexant.txt
> The following ALSA alternative CANNOT work with Conexant modems.
>
> 2) An ALSA modem driver plus slmodemd.  Read DOCs/Smartlink.txt for details,
> and
> to test get the package SLMODEMD.gcc4.2.tar.gz from:
>        http://linmodems.technion.ac.il/packages/smartlink/
>
> ----------------end Softmodem section --------------
> Writing DOCs/Smartlink.txt
> ============ end Smartlink section =====================
>
>  Completed candidate modem analyses.
>
>  The base of the UDEV device file system is: /dev/.udev
>
>  The kernel was compiled with gcc version 4.2.1 and a compiler is not
> installed
>
>  linux-headers-2.6.22.5-31-default resources needed for compiling are not
> manifestly ready!
>
>  If compiling is necessary packages must be installed, providing:
>        gcc-4.2  kernel-source-2.6.22.5-31-default
>
>
> If a driver compilation fails, with message including some lack of some
> FileName.h (stdio.h for example), then
> Some additional kernel-header files need installation to /usr/include. The
> minimal additional packages are libc6-dev
> and any of its dependents, under Ubuntu linux-libc-dev
>
> If an alternate ethernet connection is available,
> $  apt-get update
> $  apt-get -s install linux-kernel-devel
> will install needed packages.
> For Debian/Ubuntu related distributions, run the following command to
> display the needed package list:
>
> Otherwise packages have to be found through http://packages.ubuntu.com
> Once downloaded and transferred into a Linux partition,
> they can be installed alltogether with:
> $ sudo dpkg -i *.deb
>
>
> Checking pppd properties:
>        -rwxr-xr-x 1 root dialout 347008 2007-09-21 12:51 /usr/sbin/pppd
>
> In case of an "error 17" "serial loopback" problem, see:
>    http://linmodems.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
> noipdefault
> noauth
> crtscts
> lock
> modem
> asyncmap 0
> nodetach
> lcp-echo-interval 30
> lcp-echo-failure 4
> lcp-max-configure 60
> lcp-restart 2
> idle 600
> noipx
> file /etc/ppp/filters
>
> 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/DOCs/YourSystem.txt concerning other COMM channels: eth0
> Which can interfere with Browser naviagation.
>
>  Don't worry about the following, it is for experts should trouble shooting
> be necessary.
> ==========================================================
>
>  Checking for modem support lines:
>  --------------------------------------
>     /device/modem symbolic link:
> slmodemd created symbolic link /dev/ttySL0:
>     Within /etc/udev/ files:
> /etc/udev/rules.d/50-udev-default.rules:KERNEL=="mwave",
>  NAME="modems/%k", GROUP="uucp"
> /etc/udev/rules.d/77-network.rules:SUBSYSTEM=="net",
> ENV{INTERFACE}=="ppp*|ippp*|isdn*|plip*|lo*|irda*|dummy*|ipsec*|tun*|tap*|bond*|vlan*|modem*|dsl*",
> GOTO="skip_ifup"
>     Within /etc/modprobe.conf files:
>
>     Within any ancient /etc/devfs files:
>
>     Within ancient kernel 2.4.n /etc/module.conf files:
>
> --------- end modem support lines --------
>
>
>

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

  Powered by Linux