Sai, Assuming you are trying to transmit through >> ID 1004:6000 LG Electronics, Inc. VX4400/VX6000 Cellphone Bill has recently worked through these issues and can likely help more than me without comparable hardware. BIll, Still intend to polish your draft below. But am overworked Marv >From Bill Randle =============== I have a MotoQ9m cellphone by Motorola with Verizon as my data provider, and you helped me to get online. I connect with a USB cable. The Phone is ID 22b8:7000 Motorola PCS. I sent the scanmodem file to you and you said: Do: $ sudo modprobe usb-serial Then try detecting the cellphone with: $ sudo wvdialconf /etc/wvdial.conf and report back. That done, I next followed your directions to:, So next: $ sudo gedit /etc/wvdial.conf to enter the settings needed for dialout Delete the ; < > symbols as you add in your personal info, and cogent cell phone CONNECT codes. Then dialout with: $ sudo wvdial I did edit the wvconf file as follows, resulting in this output. OK ATZ OK --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 --> Modem initialized. --> Configuration does not specify a valid phone number. --> Configuration does not specify a valid login name. --> Configuration does not specify a valid password. bill@bill-laptop:~$ [Dialer Defaults] Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 Modem Type = USB Modem Baud = 460800 New PPPD = yes Modem = /dev/ttyACM0 ISDN = 0 ; Phone = #777 ; Password = vzw ; Username = mynumberhere@xxxxxxxxx I had forgotten to delete the (;) before my phone, password and username. After deleting them, I was able to get online, but only about 2 minutes per session, getting this error. --> Disconnecting at Mon Jun 2 22:07:10 2008 --> The PPP daemon has died: Lack of LCP echo responses (exit code = 15) --> man pppd explains pppd error codes in more detail. --> I guess that's it for now, exiting --> Provider is overloaded(often the case) or line problem. --> The PPP daemon has died. (exit code = 15) So I, ..... $ sudo gedit /etc/ppp/optiions to try mods within the sections below. #lcp-echo-interval 30 (this was an active option) I just added the # sign in front of this line. #lcp-echo-failure 4 (this was an active option) I just added the # sign in front of this line. I have used these directions with open GEU, Knoppix, Ubuntu, several latest versions. egrep -v '#|^ *$' /etc/ppp/options are, bill@bill-laptop:~$ egrep -v '#|^ *$' /etc/ppp/options asyncmap 0 noauth crtscts lock hide-password modem proxyarp noipx bill@bill-laptop:~$ Thank You Marvin On Sun, Jun 29, 2008 at 9:36 AM, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: > Sai, > > Please explain Dial up(BSNL-CDMA) better. > Are you doing dialup through your cellphone > or is there an internal modem. > > If the cellphone, try detecting it with: > $ sudo wvdialconf /etc/wvdial.conf > > MarvS > > On Sun, Jun 29, 2008 at 9:04 AM, sai <saivinod.muthu@xxxxxxxxx> wrote: >> Hi, >> >> I am from India and I have a Dial up(BSNL-CDMA) internet connection in my >> PC(Windows XP) at home. Now I want to setup the same dial up connection in >> my Kubuntu Linux.As per the guidance stated in the linmodem.org and >> help.ubuntu.com sites, I ran the 'scanmodem' in my linux and attached the >> generated 'Modem.txt' herewith. >> >> Please assist me further to setup dialup connection in my Kubuntu linux >> successfully. >> Thanks in advance. >> Sai. >> >> >> 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 kernel 2.6.20-15-generic >> 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, >> Linux version 2.6.20-15-generic (root@palmer) (gcc version 4.1.2 (Ubuntu >> 4.1.2-0ubuntu4)) #2 SMP Sun Apr 15 07:36:31 UTC 2007 >> scanModem update of: 2008_06_17 >> >> There are no blacklisted modem drivers in /etc/modprobe* files >> Attached USB devices are: >> ID 0e5e:6622 >> ID 1004:6000 LG Electronics, Inc. VX4400/VX6000 Cellphone >> >> USB modems not recognized >> >> For candidate card in slot 00:1b.0, firmware information and bootup >> diagnostics are: >> PCI slot PCI ID SubsystemID Name >> ---------- --------- --------- -------------- >> 00:1b.0 8086:27d8 8086:d606 Audio device: Intel >> Corporation 82801G >> >> Modem interrupt assignment and sharing: >> 21: 34930 0 IO-APIC-fasteoi HDA Intel >> --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- >> >> >> ===== 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:1b.0 has a High Definition Audio Card >> The drivers are in the kernel modules tree at: >> /lib/modules/2.6.20-15-generic/kernel/sound/pci/hda/snd-hda-intel.ko >> >> The ALSA verion is 1.0.13 >> The modem cards detected by "aplay -l" are: None >> >> >> The /proc/asound/pcm file reports: >> ----------------------- >> 00-02: ALC883 Analog : ALC883 Analog : capture 2 >> 00-00: ALC883 Analog : ALC883 Analog : playback 1 : capture 2 >> >> about /proc/asound/cards: >> ------------------------ >> 0 [Intel ]: HDA-Intel - HDA Intel >> HDA Intel at 0x301c0000 irq 21 >> === Finished firmware and bootup diagnostics, next deducing cogent software. >> === >> >> A candidate modem is not evident among the PCI devices: >> ------------------------------------------------ >> 00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated >> Graphics Controller (rev 02) >> 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition >> Audio Controller (rev 01) >> 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller >> (rev 01) >> 00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family) Serial >> ATA Storage Controller IDE (rev 01) >> 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev >> 01) >> 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B >> PCI Express Gigabit Ethernet controller (rev 01) >> ------------------------------------------------ >> with USB and bridge devices not displayed. >> >> If your modem is connected by an external serial cable, >> or mounted internally on an ISA card, scanModem would not access it. >> Try with Root permission >> $ sudo wvdialconf /etc/wvdial.conf >> to detect these modem types and some USB modems. >> If the detection is successful, read the DOCs/wvdial.txt . >> Edit the /etc/wvdial.conf with Root permission: >> sudo gedit /etc/wvdial.conf >> will be able to dial out with Root permission: >> sudo wvdial >> >> Many modems for which scanModem fails have Conexant chips. >> From http://www.linuxant.com/drivers/modemident.php >> get the ListModem tool, which will report on Conexant chipset modems >> >> If the above tests fail, please provide any independent information >> available on your modem. >> If an alternative boot into Microsoft windows can be done, do mouse >> clicks on: >> Start > Settings > Control Panel > Classical View (for Window XP) > System >>> Hardware > Device Manager > Modems > Click on the + > Modem. Double click >>> to >> expand the graphic. Manufacturer information may be displayed. For example, >> CXT >> stands for Conexant. Click the Diagnostics Tab. Record any hardware ID or >> vendor >> and device information. From the Driver Details TAB, copy out the VENdor and >> DEVice information. >> Next do the Query Modem and record the ATI specifications displayed such as: >> ATI3 - Agere SoftModem Version 2.1.22 >> ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27 >> Try to identify the modem setup file, with name perhaps MODEM.INF. >> If may contain chipset Vendor informaton. >> >> The /proc/asound/ audio+modem diagostics are being copied. >> Finished copy to Modem/ALSAroot.tgz >> >> Predictive diagnostics for card in bus 00:1b.0: >> Modem chipset not detected on >> NAME="Audio device: Intel Corporation 82801G " >> CLASS=0403 >> PCIDEV=8086:27d8 >> SUBSYS=8086:d606 >> IRQ=21 >> HDA=8086:27d8 >> SOFT=8086:27d8.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 8086:27d8. >> If another modem card is present, then most likely 8086:27d8 does not host >> a modem. >> If another modem card has not been detected, then possibilities are: >> 1) A Conexant modem chip is present on 8086:27d8, 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: >> sudo wvdialconf /etc/wvdial.conf >> >> For candidate modem in: 00:1b.0 >> 0403 Audio device: Intel Corporation 82801G >> Primary device ID: 8086:27d8 >> Subsystem PCI_id 8086:d606 >> 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.1.tar.gz from: >> http://linmodems.technion.ac.il/packages/smartlink/ >> >> ----------------end Softmodem section -------------- >> >> 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 >> >> From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php >> download hsfmodem-7.68.00.07full_k2.6.20_15_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. >> >> Read DOCs/Conexant.txt >> >> Writing DOCs/Conexant.txt >> >> Writing DOCs/Smartlink.txt >> ============ end Smartlink section ===================== >> >> >> 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.20-15-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 libc6-dev (and for >> Debian/Ubuntu, >> linux-libc-dev). 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-- 1 root dip 269224 2007-04-05 09:11 /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 >> >> Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 >> eth0:avah >> 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: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 -------- >> >> >> >> >
