RE : Should I simply respond to the latter , "discuss@xxxxxxxxxxxxx". and then all will see each response? YES please do. MarvS On 9/26/07, mic <mikrose@xxxxxxx> wrote: > Hi Jacques and thanks for the response. When I get emails they have the > senders name and I have been replying to the individual email because I > get different suggestions on how to proceed. I have been trying to > answer each suggestion by replying to each person, but I guess that > isn't how it works. Since my initial post to "discuss@xxxxxxxxxxxxx", I > have been reading and responding to the emails, not to > "discuss@xxxxxxxxxxxxx". Should I simply respond to the latter and then > all will see each response? > > Marv has sent me an email today also and tells me that I have done > things correctly to a point, just needing to eliminate three "< >" and > retry. Sorry for the confusion, you both are a great influence and have > helped me chip away at this issue. Since I'm reading the posts on-line > using the Dapper distribution, then going to the 7.04 distribution > (off-line) to implement, it is taking me awhile try each suggestion. I > know I'm making more work for myself than necessary because I take a few > medications which slow me down a little, but you are making a difference. > > Jacques Goldberg wrote: > > Mic, > > > > You have sent out a lot of mails. Sometimes you write to Marv, sometimes > > to me, and perhaps some have been lost unless you not always wrote to > > discuss@xxxxxxxxxxxxx > > I received the following from you where I cannot see which modem you > > tried to identify out of the three. > > On the other hand I found a slightly earlier mail from Marv answering an > > other such report from you for a modem which has been recognized and > > just needed correct definition of the ISP parameters. > > > > What should I do with the mail from you reproduced below? > > > > Sorry, I cannot sort out this mess. > > > > Jacques > > > > mic wrote: > >> Hi Jacques. > >> Here are the results from "sudo wvdialconf /etc/wvdial.conf" > >> > >>> mic@mic-desktop:~$ sudo wvdialconf /etc/wvdial.conf > >>> Password: > >>> Editing `/etc/wvdial.conf'. > >>> > >>> Scanning your serial ports for a modem. > >>> > >>> ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud > >>> ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud > >>> ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. > >>> ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud > >>> ttyS1<*1>: ATQ0 V1 E1 -- > >>> ttyS1<*1>: failed with 9600 baud, next try: 115200 baud > >>> ttyS1<*1>: ATQ0 V1 E1 -- > >>> ttyS1<*1>: and failed too at 115200, giving up. > >>> Modem Port Scan<*1>: S2 S3 S4 S5 S6 S7 S8 S9 > >>> Modem Port Scan<*1>: S10 S11 S12 S13 S14 S15 S16 S17 > >>> Modem Port Scan<*1>: S18 S19 S20 S21 S22 S23 S24 S25 > >>> Modem Port Scan<*1>: S26 S27 S28 S29 S30 S31 S32 S33 > >>> Modem Port Scan<*1>: S34 S35 S36 S37 S38 S39 S40 S41 > >>> Modem Port Scan<*1>: S42 S43 S44 S45 S46 S47 > >>> > >>> > >>> Sorry, no modem was detected! Is it in use by another program? > >>> Did you configure it properly with setserial? > >>> > >>> Please read the FAQ at http://open.nit.ca/wiki/?WvDial > >>> > >>> If you still have problems, send mail to <wvdial-list@xxxxxxxxxxxx>. > >>> mic@mic-desktop:~$ > >> > >> > >> > >> > >> Jacques Goldberg wrote: > >>> Mic, > >>> scanModem being EXCLUSIVELY intended for internal PCI-bus modems, > >>> it by construction cannot find any external modem. > >>> Most frequently but not always, external serial modems (NOT USB, only > >>> RS232 connection, using a cable for a trapeze-shaped plus with 9 or > >>> 15 pins at both ends) do not need any driver and will work immediately > >>> if > >>> 1-you connect the modem to the PC and to the phone socket > >>> 2-power up the modem > >>> 3-use the command > >>> sudo wvdialconf /etc/wvdial.conf > >>> which will detect your modem > >>> You have then to edit the file /etc/wvdial.conf to make it match the > >>> parameters given to you by your ISP (three, obvious). > >>> See http://linmodems.technion.ac.il/wvdial.html for details. > >>> This will work for sure for your Trendnet modem, but for the "Best > >>> Data" you provide no model so I cannot check what hardware it contains. > >>> Furthermore, the Linuxant driver does support Conexant modems with > >>> your Dapper operating system, surprisingly associated with failure in > >>> your case unless your modem has been damaged. > >>> The Linuxant HCF driver will support both your Dapper and your Feisty > >>> operating systems. Let me insist on the HCF driver, not the HSF. > >>> For details how to install it see the file Conexant.txt which has > >>> been written on your disk by scanModem, next to ModemData.txt. > >>> > >>> Do I need to write that with one telephone outlet you will be able to > >>> use only one modem at a time. > >>> > >>> Jacques > >>> > >>> mic wrote: > >>>> * Need a little help, still learning my way around Linux. > >>>> * I used MS XP for a few years with an internal Conexant modem. > >>>> * Switched to Linux Dapper 6.06 seven months ago and had to buy an > >>>> external serial Best Data V.92 modem and I've had no trouble > >>>> getting on-line. > >>>> * I ordered the newer Linux Feisty 7.04 a month ago and have been > >>>> trying to set up the modem but not having any luck. * I > >>>> purchased another external TrendNet TFM 560X serial modem, and > >>>> can't get on-line. > >>>> > >>>> > >>>> I have tried to follow the instructions for your scanModem but not > >>>> having much luck. From what I can tell it detects my Conexant > >>>> modem, but not the external modem. I'd like to get either the > >>>> Conexant or either of the external modems to work so I can use > >>>> 7.04. I also have a Linux Christian Edition (CE) that is based on > >>>> 7.04, which will be my primary System. > >>>> > >>>> CPU=i686, Linux version 2.6.15-29-386 (buildd@terranova) (gcc > >>>> version 4.0.3 (Ubuntu 4.0.3-1ubuntu5)) #1 PREEMPT Wed Aug 29 > >>>> 13:20:33 UTC 2007 > >>>> scanModem update of: 2007_Sept_07 > >>>> > >>>> There are no blacklisted modem drivers in /etc/modprobe* files > >>>> USB modem not detected by lsusb > >>>> > >>>> Several modems are supported by drivers with ALSA, the Advanced > >>>> Linux Sound Architecture software. > >>>> Copying ALSA diagnostics to Modem/ALSAroot.tgz > >>>> ALSAversion = 1.0.10 > >>>> > >>>> Modem or candidate host audio card have firmware information and > >>>> diagnostics: > >>>> > >>>> PCI slot PCI ID SubsystemID Name > >>>> ---------- --------- --------- -------------- > >>>> 0000:00:0b.0 14f1:1036 13e0:0209 Communication controller: > >>>> Conexant HCF 56k Data/Fax/Voice/Spkp Modem > >>>> > >>>> Modem interrupt assignment and sharing: > >>>> 11: 1900884 XT-PIC uhci_hcd:usb5, uhci_hcd:usb6, > >>>> ehci_hcd:usb7 > >>>> --- Bootup diagnostics for card in PCI slot 0000:00:0b.0 ---- > >>>> > >>>> === Finished modem firmware and bootup diagnostics section. === > >>>> === Next deducing cogent software === > >>>> > >>>> For candidate modem in PCI bus: 0000:00:0b.0 > >>>> Class 0780: 14f1:1036 Communication controller: Conexant HCF 56k > >>>> Data/Fax/Voice/Spkp Modem > >>>> Primary PCI_id 14f1:1036 > >>>> 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 > >>>> (I DO NOT HAVE A DELL COMPUTER) > >>>> > >>>> Read Conexant.txt > >>>> > >>>> Writing Conexant.txt > >>>> > >>>> Completed candidate modem analyses. > >>>> > >>>> The base of the UDEV device file system is: /dev/.udev > >>>> > >>>> The kernel was compiled with gcc version 4.0.3 and a compiler is not > >>>> installed > >>>> > >>>> If compiling a modem driver proves to be necessary, one of the two > >>>> procedures must be followed. > >>>> If not yet on the Internet, put the Dapper install CD in the drive > >>>> Open a terminal and therein: > >>>> $ sudo apt-get install gcc-4.0 make > >>>> Additionally the package linux-headers-2.6.15-29-386 must be > >>>> downloaded. Go to http://packages.ubuntu.com/ and search for > >>>> linux-headers-2.6.15-29-386 > >>>> After downloading, it can be installed with: > >>>> $ sudo dpkg -i linux-header*.deb > >>>> > >>>> Or alternatively if online through Ethernet do: > >>>> $ sudo apt-get update > >>>> $ sudo apt-get install build-essential > >>>> will do all the necessary installations mentioned above. > >>>> > >>>> In either installation case, set a symbolic link which will be > >>>> expected later: > >>>> $ sudo ln -s /usr/bin/gcc-4.0 /usr/bin/gcc > >>>> After check with: > >>>> $ ls -l /usr/bin/gcc* > >>>> which should display: > >>>> lrwxrwxrwx 1 root root 16 2006-07-09 21:53 /usr/bin/gcc -> > >>>> /usr/bin/gcc-4.0 > >>>> -rwxr-xr-x 1 root root 93584 2006-04-20 18:22 /usr/bin/gcc-4.0 > >>>> -rwxr-xr-x 1 root root 16245 2006-04-20 18:13 /usr/bin/gccbug-4.0 > >>>> > >>>> linux-headers-2.6.15-29-386 resources needed for compiling are not > >>>> manifestly ready! > >>>> > >>>> If compiling is necessary packages must be installed, providing: > >>>> gcc-4.0 make linux-headers-2.6.15-29-386 > >>>> > >>>> > >>>> If a driver compilation files with message including some lack of > >>>> some FileName.h (stdio.h for example. > >>>> Some additional kernel-header files need installation to /usr/include. > >>>> For Debian/Ubuntu related distributions, run the following command > >>>> to display the needed package list: > >>>> $ sudo apt-get -s install linux-kernel-devel > >>>> While some of the files may be on the install CD, others may have to > >>>> be found through http://packages.ubuntu.com > >>>> > >>>> For Ubuntu Feisty, additional packages required were: > >>>> libc6-dev linux-libc-dev > >>>> available through http://packages.ubuntu.com/ , if not on the > >>>> install CD. > >>>> Such packages may have different names for other Linux distributions. > >>>> Try installing just the libc6-dev, then test the compile again. > >>>> > >>>> > >>>> Checking pppd properties: > >>>> -rwsr-xr-- 1 root dip 257720 2006-07-05 06:00 /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) > >>>> 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 > >>>> auth > >>>> 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 > >>>> > >>>> Read Modem/YourSystem.txt concerning other COMM channels: eth0 ppp0 > >>>> 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: slmodemd created symbolic link > >>>> /dev/ttySL0: Within /etc/udev/ files: > >>>> /etc/udev/rules.d/60-symlinks.rules:# Create /dev/modem symlink > >>>> /etc/udev/rules.d/60-symlinks.rules:KERNEL=="ttyLTM[0-9]*", > >>>> SYMLINK+="modem" > >>>> Within /etc/modprobe.conf files: > >>>> /etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2 > >>>> /etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2 > >>>> /etc/modprobe.d/blacklist-modem:# Uncomment these entries in order > >>>> to blacklist unwanted modem drivers > >>>> /etc/modprobe.d/blacklist-modem:# blacklist snd-atiixp-modem > >>>> /etc/modprobe.d/blacklist-modem:# blacklist snd-via82xx-modem > >>>> Within any ancient /etc/devfs files: > >>>> > >>>> Within ancient kernel 2.4.n /etc/module.conf files: > >>>> > >>>> --------- end modem support lines -------- > >>>> > >>>> Thanks > >>> > >>> > > > > >
