Unsubscribe Sent from my Verizon Wireless BlackBerry -----Original Message----- From: Jacques Goldberg <goldberg@xxxxxxxxxxxxxxxxxxxx> Date: Tue, 21 Sep 2010 09:50:06 To: Jeff Hunt<jeffhunt90@xxxxxxxxx> Reply-To: Jacques.Goldberg@xxxxxxx Cc: <Discuss@xxxxxxxxxxxxx> Subject: Re: Jeff Hunt, New Zealand, kernel 2.6.32-24-generic [Now basic operations under Linux] Jeff, Please see my comments in line below: On 09/21/2010 08:50 AM, Jeff Hunt wrote: > Thanks so much guys, you are great. I have been trying to do winmodems > for years now and always gave up before I got there. General: what is the purpose of your mail? To obtain direct replies or suggest better information on our Web site? > Some points to ponder if you care to. > 1. Where are the full controller modems, including external modems. It > seems oddly difficult to buy anything that just works. I use aging > Dynalink and US-Robotics external modems when I can find them. > Is this a question to us about documenting full controller modems, or an expression of nostalgy towards the good days where you could buy them? > 2. Gnome-ppp has an autodetect for modems. Just as I was on the point > of giving up yet again I tried to autodetect and it found my new > driver. This might be worth mentioning in the documentation. This autodetect is using wvdial . There are two cases: -The trivial case when this autodetect works, hiding from your eyes the job which wvdial does -The very frequent non trivial case where it does not, forcing users to ask us for help (which we are pleased to deliver). Furthermore some problems sometimes pop up with selected ISP's such as DNS definitions or security (such as pap/chap issues), where autodetect has worked but nothing works beyond it and the user does not know where to try to intervene. This is why we simply recommend users to use wvdial at least during first installation and debugging. Later below you ask about logs: a feature of gnome-ppp autodetect is to hide the log from you while wvdial has exactly the opposite approach. wvdial is in the spirit of Linux while gnome-ppp is in the spirit of "the other" operating system. > 3. What are the files that affect ppp and what rights should they have > to work. It seems that every time I try to get a modem running I come > up against another unwritable file. Are these files documented? > pap-secrets and chap-secrets are two troublesome ones. The files which you may have to dig in are in /etc/ppp , in particular /etc/ppp/options . If you change any of their permissions you also widely open your computer to hacking, so you should NEVER change any of these permissions. Linux not like "the other" O.S. is a multiuser O.S. As soon as you connect to a network your computer can be accesses from the network, and the hackers have no rest until they break in. That's why Linux locks the accesses, and why you better not unlock them. Always use su or sudo, not unlocking protections, and then sleep in Peace. The documentation follows the general Unix/Linux rule. Every program/application should be documented by a man file. "man" stands for MANUAL (you know, manual from Read The Manual First). For example the command line ls issues a list of files. To learn how to use ls you need to type command man ls For ppp you would thus try man ppp No man ppp ? Start with command apropos ppp and you get a list of all ppp related manuals. Including /etc/ppp/options Where you will find (almost) everything you may want to know about pap and chap Almost, because some ISP (or rather, the softwares they use, such as mschap , guess what ms means there, do not respect standards). > 4. Related to the above. Where are the logs. I found a really good one > and then rebooted and forgot what I had been reading. Duuh (!?) > Normally, unless somebody in some Linux distribution decided otherwise, the place is /var/log > 5. I tried with an intel chip modem and gave up (no dialtone even > though it initialised and I knew there was a dialtone) so I put in a > Conexant and (of course) got a hardware conflict. I solved this by > moving the Conexant to another slot. How do I remove the intel driver > and free the slot/interrupt? Interesting, at last a modem related issue, because so far what I typed here is barely something else from a part of a very basic introduction to Linux, not to modems, to answer this we would need the scanModem output generated with the "Intel chip modem" and a report from you of exactly which driver file you installed for it. When you installed the driver for your "Intel chip modem" (where, short of is ModemData.txt, it remains to be seen how much an Intel modem this is .... and I know why I write this) a loadable kernel module was installed and activated. The command lsmod will show it. The command rmmod will remove it. In order to avoid the system to reload it at next boot once you know the name of this loadable module (often more than one, such as with Linuxant drivers) you have to find it on disk, using the Linux find command ( use man find to learn how to use find), not forgetting to append .ko at the end of the module name. Then you delete this file with the Linux command rm ( man rm to learn it). > Anyway really impressed with the people who helped. Many thanks. One of th things I did to try to help was to write most of the pages in http://linmodems.technion.ac.il , including the main page and advice in there which covers most of what you asked. Further suggestions welcome. Thanks for them in advance. Jacques > On 9/19/10, Antonio Olivares<olivares14031@xxxxxxxxx> wrote: >> Marv, >> >> Jeff cannot find the package in question: >> >> hfsmodem-7.80.02.06full_k2.6.32_24_generic_ubuntu_i386.deb.zip >> because it does not exist. For a while now, Linuxant has left the job >> to the generic modem source that now needs to be used: >> >> Alternatively, 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: >> sudo dpkg -i hsf*.deb >> while for .rpm suffix it is, with: >> rpm -i hsf*.rpm >> Read DOCs/Conexant.txt >> >> >> He needs to download: >> >> http://www.linuxant.com/drivers/hsf/full/archive/hsfmodem-7.80.02.06full/hsfmodem_7.80.02.06full_i386.deb.zip >> >> and do : >> >> 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. >> >> From: >> >> http://www.linuxant.com/drivers/hsf/install.php >> >> The process has changed a bit since Ubuntu pushes too many kernels, >> and Linuxant *got tired* of pushing too many updates for newly >> released kernels. Now it is up to the user to build his/her own >> drivers. >> >> Hope this helps clear the situation. >> >> Regards, >> >> Antonio >> >> On 9/18/10, Marvin Stodolsky<marvin.stodolsky@xxxxxxxxx> wrote: >>> Jeff, >>> >>> Following the directions below is still OK. The hsfmodem packages >>> have compiling capability, used if there is not a kernel-version match >>> Just choose the most recent hsfmodem*.deb.zip package or the generic >>> package from the prior download page and all should work. >>> >>> MarvS >>> scanModem maintainer >>> ------------------- >>> From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php >>> download hsfmodem-7.80.02.06full_k2.6.32_24_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. >>> >>> On Fri, Sep 17, 2010 at 10:35 PM, Jeff Hunt<jeffhunt90@xxxxxxxxx> wrote: >>>> I have a Dell Dimension 4600 and I cannot find a download for the >>>> hsfmodem that I seem to need. >>>> I have internet access on an external modem and home network on >>>> ethernet all working fine but I just want to be able to use my >>>> internal modem and help other users do the same. Where do I get a >>>> driver? It seems that all the information on the net is out of date. >>>> Many thanks in anticipation. >>>> >>>> My Modem Data is: >>>> >>>> CPU=i686, Ubuntu , ALSA_version=1.0.21 >>>> Linux version 2.6.32-24-generic (buildd@palmer) (gcc version 4.4.3 >>>> (Ubuntu 4.4.3-4ubuntu5) ) #42-Ubuntu SMP Fri Aug 20 14:24:04 UTC 2010 >>>> scanModem update of: 2010_05_29 >>>> >>>> Distrib_ID=Ubuntu >>>> DistribCodeName=lucid >>>> AptRepositoryStem=http://nz.archive.ubuntu.com/ubuntu/ >>>> >>>> >>>> Presently install your Linux Distributions dkms package. It provides >>>> for automated driver updates, >>>> following upgrade of your kernel. For details see >>>> http://linux.dell.com/projects.shtml#dkms >>>> >>>> There are no blacklisted modem drivers in /etc/modprobe* files >>>> >>>> Potentially useful modem drivers now loaded are: >>>> >>>> >>>> Attached USB devices are: >>>> ID 046d:c016 Logitech, Inc. M-UV69a/HP M-UV96 Optical Wheel Mouse >>>> If a cellphone is not detected, see >>>> http://ubuntuforums.org/archive/index.php/t-878554.html >>>> A sample report is: >>>> http://linmodems.technion.ac.il/bigarch/archive-nineth/msg00578.html >>>> >>>> If a USB modem or cellphone is attached and was not detected, please >>>> provide available information in your request to discuss@xxxxxxxxxxxxx >>>> >>>> Candidate PCI devices with modem chips are: >>>> 02:01.0 Communication controller: Conexant Systems, Inc. Device 2702 (rev >>>> 01) >>>> High Definition Audio cards can host modem chips. >>>> >>>> For candidate card in slot 02:01.0, firmware information and bootup >>>> diagnostics are: >>>> PCI slot PCI ID SubsystemID Name >>>> ---------- --------- --------- -------------- >>>> 02:01.0 14f1:2702 1043:8d88 Communication controller: >>>> Conexant >>>> Systems, Inc. Device 2702 >>>> >>>> Modem interrupt assignment and sharing: >>>> --- Bootup diagnostics for card in PCI slot 02:01.0 ---- >>>> [ 0.266802] pci 0000:02:01.0: reg 10 32bit mmio: >>>> [0xfe8f0000-0xfe8fffff] >>>> [ 0.266813] pci 0000:02:01.0: reg 14 io port: [0xcf38-0xcf3f] >>>> [ 0.266861] pci 0000:02:01.0: PME# supported from D3hot D3cold >>>> [ 0.266868] pci 0000:02:01.0: PME# disabled >>>> >>>> The PCI slot 02:01.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. >>>> >>>> >>>> === Finished firmware and bootup diagnostics, next deducing cogent >>>> software. === >>>> >>>> Predictive diagnostics for card in bus 02:01.0: >>>> Modem chipset detected on >>>> NAME="Communication controller: Conexant Systems, Inc. Device 2702 " >>>> CLASS=0780 >>>> PCIDEV=14f1:2702 >>>> SUBSYS=1043:8d88 >>>> IRQ=10 >>>> IDENT=hsfmodem >>>> Driver=hsfmodem-drivers >>>> >>>> For candidate modem in: 02:01.0 >>>> 0780 Communication controller: Conexant Systems, Inc. Device 2702 >>>> Primary device ID: 14f1:2702 >>>> 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 >>>> >>>> >>>> For all code packages from Linuxant.com, either a driver set matching >>>> the boot kernel will be installed, >>>> or the drivers will first be compiled and then installed. The expert >>>> on modem software for Linux is >>>> "Support (Jonathan)"<modem.support@xxxxxxxxxxxx> >>>> >>>> From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php >>>> download hsfmodem-7.80.02.06full_k2.6.32_24_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. >>>> >>>> The directions following below need only be pursued, if the above >>>> procedures are not adequate. >>>> >>>> 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.32_24_generic >>>> 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, the needed >>>> drivers >>>> will be auto compiled anyway. Alternatively, 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: >>>> sudo dpkg -i hsf*.deb >>>> while for .rpm suffix it is, with: >>>> rpm -i hsf*.rpm >>>> Read DOCs/Conexant.txt >>>> >>>> Writing DOCs/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.4.3 >>>> and the compiler used in kernel assembly: 4.4.3 >>>> >>>> The patch utility is needed for compiling ALSA drivers, and possibly >>>> others. >>>> >>>> >>>> Minimal compiling resources appear complete: >>>> make utility - /usr/bin/make >>>> Compiler version 4.4 >>>> linuc_headers base folder /lib/modules/2.6.32-24-generic/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 needed. 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-xrwx 1 root dip 273312 2010-03-07 16:59 /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) >>>> sudo chmod a+x /usr/sbin/pppd >>>> or under Ubuntu related Linuxes >>>> sudo chmod a+x /usr/sbin/pppd >>>> >>>> Checking settings of: /etc/ppp/options >>>> asyncmap 0 >>>> noauth >>>> crtscts >>>> lock >>>> hide-password >>>> modem >>>> proxyarp >>>> lcp-echo-interval 30 >>>> lcp-echo-failure 4 >>>> noipx >>>> >>>> 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 >>>> >>>> For guidance on FAX usage, get from >>>> http://linmodems.technion.ac.il/packages/ get faxing.tar.gz >>>> It has samples for a modem using port /dev/ttySL0, which must be >>>> changed to match your modem's port. >>>> >>>> Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth3 >>>> 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: >>>> /etc/modprobe.d/alsa-base.conf:options snd-atiixp-modem index=-2 >>>> /etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2 >>>> /etc/modprobe.d/blacklist-modem.conf:# Uncomment these entries in >>>> order to blacklist unwanted modem drivers >>>> /etc/modprobe.d/blacklist-modem.conf:# blacklist snd-atiixp-modem >>>> /etc/modprobe.d/blacklist-modem.conf:# blacklist snd-via82xx-modem >>>> Within any ancient /etc/devfs files: >>>> >>>> Within ancient kernel 2.4.n /etc/module.conf files: >>>> >>>> --------- end modem support lines -------- >>>>
