Donna, The usbserial driver(kernel built in) should do the job. Please try the following: Open up a terminal and type $ sudo wvdialconf /etc/wvdial.conf and it should scan and find a modem port something like found a modem on port /dev/ttyACM0 or something similar. It will produce a file /etc/wvdial.conf which will have modem information and some lines with a ";" in front like phone, username, password edit the file $ sudo gedit /etc/wvdial.conf and remove the ";" and add your ISP's phone no. and your username, and password, save the file then try to dialout and see if you can achieve a connection $ sudo wvdial and see if you can connect. Report back. Regards, Antonio On Fri, May 22, 2009 at 8:53 AM, Donna I. <cloudyskies@xxxxxxxxx> wrote: > Hello, > > I've been trying to dial out on my analog line for about a month now. I > purchased a Dell (Mini) Inspiron 910 with Ubuntu as the operating system. > I've purchased a USRobotics 56K USB Modem (which I read was compatible with > Linux). It feels like I've tried everything (including contacting Dell > support). I am familiar with some of Linux programs (which I've used under > Windows) -- but I feel I am very in the dark when it comes to this problem. > I checked out (at the library) Ubuntu For Non-Geeks 3rd Edition -- reading > and following the instructions (pages 55-58) -- I downloaded the > scanModem.gz (on my main computer), transfered it (via thumbnail drive) over > to my Dell Mini and ran it. > I'm attaching a copy of my ModemData.txt report for you -- I am hoping there > is a simple solution to this problem. > > Thank you in advance for your help! > Donna > > 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.24-19-lpia > 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.24-19-lpia (root@macbook) (gcc version 4.2.3 (Ubuntu > 4.2.3-2ubuntu7)) #1 SMP Mon Nov 3 15:25:26 UTC 2008 > scanModem update of: 2009_05_12 > > There are no blacklisted modem drivers in /etc/modprobe* files > Potentially useful modem drivers now loaded are: > snd_hda_intel > > Attached USB devices are: > ID 0951:1603 Kingston Technology > ID 0baf:0303 U.S. Robotics > ID 046d:c408 Logitech, Inc. Marble Mouse (4-button) > If a cellphone is not detected, see > http://ubuntuforums.org/archive/index.php/t-878554.html > > If a USB modem or cellphone is attached and was not detected, please > provide available information in your request to discuss@xxxxxxxxxxxxx > > 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 1028:02b0 Audio device: Intel > Corporation 82801G > > Modem interrupt assignment and sharing: > 21: 1140 0 IO-APIC-fasteoi HDA Intel > --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- > [ 18.776506] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> > IRQ 21 > [ 18.776549] PCI: Setting latency timer of device 0000:00:1b.0 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.16 > The modem cards detected by "aplay -l" are: None > > > The /proc/asound/pcm file reports: > ----------------------- > 00-04: ALC268 Analog : ALC268 Analog : capture 1 > 00-00: ALC268 Analog : ALC268 Analog : playback 1 : capture 1 > > about /proc/asound/cards: > ------------------------ > 0 [Intel ]: HDA-Intel - HDA Intel > HDA Intel at 0xf0540000 irq 21 > > PCI slot 00:1b.0 has a High Definition Audio Card > The drivers are in the kernel modules tree at: > /lib/modules/2.6.24-19-lpia/ubuntu/sound/alsa-driver/pci/hda/snd-hda-intel.ko > UNEXPECTED HDA diagnostic outcome. > === Finished firmware and bootup diagnostics, next deducing cogent software. > === > > Predictive diagnostics for card in bus 005: > Modem chipset detected on > SLOT="Bus 005 Device 004:" > NAME="U.S. Robotics " > bus=005 > USBmodemID=0baf:0303 > IDENT=usbserial > Driver=usbserial > > For a detailed USB cellphone usage report, see > http://linmodems.technion.ac.il/bigarch/archive-eighth/msg03240.html > For candidate modem in: 005 > U.S. Robotics > Primary device ID: 0baf:0303 > Support type needed or chipset: usbserial > > > > Writing DOCs/Intel.txt > > > 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=1028:02b0 > 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 1028:02b0 > 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.2.tar.gz from: > http://linmodems.technion.ac.il/packages/smartlink/ > > 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.2.3 > and the compiler used in kernel assembly: 4.2.3 > > linux-headers-2.6.24-19-lpia resources needed for compiling are not > manifestly ready! > The patch utility is needed and is needed for compiling ALSA drivers, and > possibly others. > > If compiling is necessary packages must be installed, providing: > linux-headers-2.6.24-19-lpia > > > 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 261032 2007-10-04 15:37 /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 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: > /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 -------- >
