Dennis, In more detail: from http://www.linuxant.com/drivers/hsf/full/downloads.php download the hsfmodem_7.68.00.12full_i386.deb.zip > Downloaded packages must be moved into the Linux partition (home folder is OK) > and unzipped with: > unzip hsf*.zip > The installation command for a .deb suffic packages is, with root/adm permission: > dpkg -i hsf*.deb etc. Send to the list if help is needed. Be sure to read the wvdial.txt before attempting a dialout. Shutdown the wireless before trying to dial out, or you may CONNECT for browsing (DNS service) will fail. Check with: # ifconfig then as necessary # ifconfig wlan0 down or whatever is your wireless designation instead of wlan0 Also # ifconfig eth0 down if that is up. Only then # wvdial MarvS scanModem maintainer On Sun, Aug 24, 2008 at 4:34 PM, Antonio Olivares <olivares14031@xxxxxxxxx> wrote: > Dennis, > > Follow the instructions from scanModem: > > 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 > > > Start at http://www.linuxant.com/drivers/hsf/downloads-license.php to find the > hsfmodem package matching your System. For several Linux distros, there are > precompiled drivers matched to specific kernels. These have within the FileName, > your KernelVersion: 2.6.18.8.tex5 > They can be found through http://www.linuxant.com/drivers/hsf/full/downloads.php > A more precise location may be given a few paragraphs below. > If an EXACT Match with your your KernelVersion is not found, one of the > "Generic packages with source" near the bottom of the page must be used. > Downloaded packages must be moved into the Linux partition (home folder is OK) > and unzipped with: > unzip hsf*.zip > The installation command for a .deb suffic packages is, with root/adm permission: > dpkg -i hsf*.deb > while for .rpm suffix it is, with: > rpm -i hsf*.rpm > Start at http://www.linuxant.com/drivers/hsf/full for > eventually download of a hsfmodem-7.68.00.12full_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.12full.tar.gz package only provides compiling support > > Read DOCs/Conexant.txt > > If you have problems after following the directions, please write back to list asking for help. > > Regards, > > Antonio > > > --- On Sun, 8/24/08, Dennis <burgersplus@xxxxxxxxx> wrote: > >> From: Dennis <burgersplus@xxxxxxxxx> >> Subject: Dennis Smith, Canada, PCLinuxOS release 2007 (PCLinuxOS) for i586,Kernel 2.6.18.8.tex5 on an i686 / kernel 2.6.18.8.tex5 >> To: Discuss@xxxxxxxxxxxxx >> Date: Sunday, August 24, 2008, 12:21 PM >> I am following the instructions on the New Installation >> Page. Winmodem >> Not Recognized. >> I am a newbie at Linux and appreciate the help. I am >> connected with my >> Broadcam internal Wireless Adapter but the dial up is not >> recognized or >> installed properly. >> >> 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 PCLinuxOS release 2007 >> (PCLinuxOS) for i586 >> Kernel 2.6.18.8.tex5 on an i686 / kernel 2.6.18.8.tex5 >> 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=i686, PCLinuxOS release 2007 (PCLinuxOS) for i586 >> Kernel 2.6.18.8.tex5 on an i686 / >> Linux version 2.6.18.8.tex5 (vaughan@localhost) (gcc >> version 4.1.1 20060724 (prerelease) (4.1.1-4pclos2007)) #1 >> SMP Thu May 10 11:36:58 WST 2007 >> scanModem update of: 2008_08_09 >> >> There are no blacklisted modem drivers in /etc/modprobe* >> files >> Attached USB devices are: >> ID 0d49:7250 Maxtor >> ID 0409:0059 NEC Corp. HighSpeed Hub >> ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse 6000 >> Reciever >> >> USB modems not recognized >> >> For candidate card in slot 00:1f.6, firmware information >> and bootup diagnostics are: >> PCI slot PCI ID SubsystemID Name >> ---------- --------- --------- -------------- >> 00:1f.6 8086:24c6 107b:0360 Modem: Intel Corporation >> 82801DB/DBL/DBM >> >> Modem interrupt assignment and sharing: >> 5: 6212 XT-PIC Intel 82801DB-ICH4, Intel >> 82801DB-ICH4 Modem >> --- Bootup diagnostics for card in PCI slot 00:1f.6 ---- >> PCI: Enabling device 0000:00:1f.6 (0000 -> 0001) >> ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link [LNKB] -> >> GSI 5 (level, low) -> IRQ 5 >> PCI: Setting latency timer of device 0000:00:1f.6 to 64 >> >> >> ===== 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. >> >> The ALSA verion is 1.0.13 >> The modem cards detected by "aplay -l" are: >> card 1: Modem [Intel 82801DB-ICH4 Modem], device 0: Intel >> ICH - Modem [Intel 82801DB-ICH4 Modem - Modem] >> >> The /proc/asound/pcm file reports: >> ----------------------- >> 00-04: Intel ICH - IEC958 : Intel 82801DB-ICH4 - IEC958 : >> playback 1 >> 00-03: Intel ICH - ADC2 : Intel 82801DB-ICH4 - ADC2 : >> capture 1 >> 00-02: Intel ICH - MIC2 ADC : Intel 82801DB-ICH4 - MIC2 ADC >> : capture 1 >> 00-01: Intel ICH - MIC ADC : Intel 82801DB-ICH4 - MIC ADC : >> capture 1 >> 00-00: Intel ICH : Intel 82801DB-ICH4 : playback 1 : >> capture 1 >> 01-00: Intel ICH - Modem : Intel 82801DB-ICH4 Modem - Modem >> : playback 1 : capture 1 >> >> about /proc/asound/cards: >> ------------------------ >> 0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4 >> Intel 82801DB-ICH4 with unknown codec >> at 0xe0100c00, irq 5 >> 1 [Modem ]: ICH-MODEM - Intel 82801DB-ICH4 Modem >> Intel 82801DB-ICH4 Modem at 0x2400, >> irq 5 >> Lines in: /proc/asound/card1/codec97#0/mc97#0-0+regs >> ------------------------------- >> 0:7c = 4358 and 0:7e = 5430 >> are translated from hexadecimal code into the modem chip >> identifier: CXT30 >> >> Support is provided only through hsfmodem drivers. Read >> DOCs/Conexant.txt >> === Finished firmware and bootup diagnostics, next deducing >> cogent software. === >> >> Predictive diagnostics for card in bus 00:1f.6: >> Modem chipset detected on >> NAME="Modem: Intel Corporation 82801DB/DBL/DBM " >> CLASS=0703 >> PCIDEV=8086:24c6 >> SUBSYS=107b:0360 >> IRQ=5 >> SOFT=8086:24c6.MC97 >> CodecDiagnosed=CXT30 >> CodecClass=CXT >> IDENT=hsfmodem >> Driver=hsfmodem-drivers >> >> For candidate modem in: 00:1f.6 >> 0703 Modem: Intel Corporation 82801DB/DBL/DBM >> Primary device ID: 8086:24c6 >> Subsystem PCI_id 107b:0360 >> Softmodem codec or chipset from diagnostics: CXT30CXT, >> a Conexant type using hsfmodem software. >> from Archives: >> CXTnn is a generic for all CXTnumbers, with >> Linuxant hsfmodem software support. >> >> >> This is a NEW softmodem case! Please send the output >> ModemData.txt >> to DISCUSS@xxxxxxxxxxxxx to enrich the Archive and help >> others! >> If further assistance is not needed, please use email >> Subject: >> New Case Only >> ------------------------------------------- >> 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 >> >> >> Start at >> http://www.linuxant.com/drivers/hsf/downloads-license.php to >> find the >> hsfmodem package matching your System. For several Linux >> distros, there are >> precompiled drivers matched to specific kernels. These have >> within the FileName, >> your KernelVersion: 2.6.18.8.tex5 >> They can be found through >> http://www.linuxant.com/drivers/hsf/full/downloads.php >> A more precise location may be given a few paragraphs >> below. >> If an EXACT Match with your your KernelVersion is not >> found, one of the >> "Generic packages with source" near the bottom of >> the page must be used. >> Downloaded packages must be moved into the Linux partition >> (home folder is OK) >> and unzipped with: >> unzip hsf*.zip >> The installation command for a .deb suffic packages is, >> with root/adm permission: >> dpkg -i hsf*.deb >> while for .rpm suffix it is, with: >> rpm -i hsf*.rpm >> Start at http://www.linuxant.com/drivers/hsf/full for >> eventually download of a hsfmodem-7.68.00.12full_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.12full.tar.gz package only >> provides compiling support >> >> Read DOCs/Conexant.txt >> >> Writing DOCs/Conexant.txt >> >> >> Completed candidate modem analyses. >> >> The base of the UDEV device file system is: /dev/.udev >> /dev/.udevdb >> >> Versions adequately match for the compiler installed: >> 4.1.1 >> and the compiler used in kernel assembly: >> 4.1.1 >> >> >> >> Minimal compiling resources appear complete: >> make utility - /usr/bin/make >> Compiler version 4.1 >> linuc_headers base folder >> /lib/modules/2.6.18.8.tex5/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 n. The >> also required headers of package libc6 are commonly >> installed by default. >> Compiling hsfmodem drivers does require linux-libc-dev and >> libc6-dev packages, for kernels 2.6.24 and later versions. >> In not included on your install CD, search for them at >> http://packages.ubuntu.com >> or comparable Repository for other Linux distros. >> When compiling ALSA drivers, the utility "patch" >> will also be needed. >> >> >> >> >> 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: >> -rwsr-xr-t 1 root root 304536 Nov 6 2006 /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 >> lock >> noauth >> noipdefault >> usepeerdns >> >> 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 eth1 >> 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: >> >> 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 -------- > > > >
