Raman, Jonathan is the expert on the HCF modems MarvS On Dec 13, 2007 12:42 PM, Raman Gupta <rocketraman@xxxxxxxxxxx> wrote: > Installed driver from linuxant. Driver compiles and modules load successfully. Modem AT commands > work, but when the modem dials out, the telco does not seem to recognize the dial tones, and > eventually returns a busy signal, resulting in the modem returning "BUSY". > > Dialing in to the modem (from a regular phone) and using ATA does seem to at least start carrier > negotiation, but I haven't tried this with a remote modem. > > AT&V > ACTIVE PROFILE: > E1 L1 M1 Q0 T V1 X4 W0 &C1 &D2 > S00:000 S01:000 S02:043 S03:013 S04:010 S05:008 S06:002 S07:045 S08:002 > S10:014 S12:050 S16:000 S18:000 S29:070 > > > -------------------------- System information ---------------------------- > CPU=i686, Fedora Core release 6 (Zod) > Kernel > Linux version 2.6.22.14-72.fc6 (brewbuilder@xxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.2 20070626 > (Red Hat 4.1.2-13)) #1 SMP Wed Nov 21 15:12:59 EST 2007 > scanModem update of: 2007-20-07 > The modem symbolic link is /dev/modem -> ttySHCF0 > > There are no blacklisted modem drivers in /etc/modprobe* files > > The Advanced Linux Sound Architecture (ALSA) packages providing audio support on your System, > also includes drivers for some modems. High Definition Audio (HDA) cards can themselves host > a softmodem chipset, with both audio+modem supported by a snd-hda-intel driver. > The ALSA diagnostics are written during bootup to /proc/asound/ folders. > > > Modem not detected though HDA card diagnostics, though not excluding > a possible Conexant modem chip impervious to ALSA diagnostics. > Proceeding through alternative possibilties. > > Summary card and chipset information is in: > /proc/asound/cards: > 0 [Live ]: EMU10K1 - SBLive! Value [CT4780] > SBLive! Value [CT4780] (rev.8, serial:0x80221102) at 0xdc60, irq 21 > > /proc/asound/pcm: > 00-03: emu10k1 : Multichannel Playback : playback 1 > 00-02: emu10k1 efx : Multichannel Capture/PT Playback : playback 8 : capture 1 > 00-01: emu10k1 mic : Mic Capture : capture 1 > 00-00: emu10k1 : ADC Capture/Standard PCM Playback : playback 32 : capture 1 > > A copy of /proc/asound had been copied to Modem/ALSAraman.tgz > USB modem not detected by lsusb > > For candidate card, firmware information and bootup diagnostics are: > > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 04:0f.0 14f1:10b6 a0a0:00c2 Communication controller: Conexant Unknown device 10b6 > > Modem interrupt assignment and sharing: > 16: 1443213 IO-APIC-fasteoi uhci_hcd:usb1, hcfpcihw > --- Bootup diagnostics for card in PCI slot 04:0f.0 ---- > ACPI: PCI Interrupt 0000:04:0f.0[A] -> GSI 19 (level, low) -> IRQ 16 > ACPI: PCI interrupt for device 0000:04:0f.0 disabled > ACPI: PCI Interrupt 0000:04:0f.0[A] -> GSI 19 (level, low) -> IRQ 16 > ACPI: PCI interrupt for device 0000:04:0f.0 disabled > ACPI: PCI Interrupt 0000:04:0f.0[A] -> GSI 19 (level, low) -> IRQ 16 > ACPI: PCI interrupt for device 0000:04:0f.0 disabled > ACPI: PCI Interrupt 0000:04:0f.0[A] -> GSI 19 (level, low) -> IRQ 16 > ACPI: PCI interrupt for device 0000:04:0f.0 disabled > ACPI: PCI Interrupt 0000:04:0f.0[A] -> GSI 19 (level, low) -> IRQ 16 > > The PCI slot 04:0f.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 Bootup.txt about possible fixes. > Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx > if help is needed. > > > === Finished modem firmware and bootup diagnostics section. === > === Next deducing cogent software === > > > There is candidate modem software. > > For candidate modem in PCI bus: 04:0f.0 > Class 0780: 14f1:10b6 Communication controller: Conexant Unknown device 10b6 > Primary PCI_id 14f1:10b6 > Support type needed or chipset: hcflinmodem > > > > 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 Conexant.txt > > 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 > > > > Minimal compiling resources appear complete: > make utility - /usr/bin/make > Compiler version 4.1 > linuc_headers base folder /lib/modules/2.6.22.14-72.fc6/build > > However some compilations and executable functions may need additional files, > in the FileNames.h (so called kernel "h"eaders) collection installed in /usr/include/ . > For martian_modem, additional required packages are libc6-dev (and for Debian/Ubuntu, > linux-libc-dev). The also required headers of package libc6 are commonly installed by 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 pacakage > 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: > -r-xr-xr-x 1 root root 312492 Dec 1 2006 /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 tun0 > 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 Dec 12 04:06 /dev/modem -> ttySHCF0 > slmodemd created symbolic link /dev/ttySL0: > Within /etc/udev/ files: > /etc/udev/rules.d/00-hcfpci.rules:KERNEL=="ttySHCF0", SYMLINK="modem" > /etc/udev/rules.d/50-udev.rules:KERNEL=="modems/mwave*", NAME="%k", GROUP="uucp", MODE="0660" > Within /etc/modprobe.conf files: > /etc/modprobe.conf:alias /dev/modem /dev/ttySHCF > Within any ancient /etc/devfs files: > > Within ancient kernel 2.4.n /etc/module.conf files: > alias /dev/modem /dev/ttySHCF > --------- end modem support lines -------- > >
