Rajiv, scanModem does not detect any PCI modem(s) present in your system. Nor does it detect a usb/serial device. A candidate modem is not transparent among the PCI devices: ------------------------------ ------------------ 00:00.0 Class 0600: 8086:7124 (rev 03) 00:01.0 Class 0300: 8086:7125 (rev 03) 00:1e.0 Class 0604: 8086:2418 (rev 02) 00:1f.0 Class 0601: 8086:2410 (rev 02) 00:1f.1 Class 0101: 8086:2411 (rev 02) 00:1f.2 Class 0c03: 8086:2412 (rev 02) 00:1f.3 Class 0c05: 8086:2413 (rev 02) 01:00.0 Class 0200: 10ec:8139 (rev 10) 01:0a.0 Class 0c03: 1106:3038 (rev 62) 01:0a.1 Class 0c03: 1106:3038 (rev 62) 01:0a.2 Class 0c03: 1106:3104 (rev 65) ------------------------------------------------ with USB, bridge, and RAM devices not displayed. If a High Definition Audio card is present, if might be hosted on the Subsystem. If your modem is an external USB type, connected by an external serial cable, or mounted internally on an ISA card, then scanModem would not access it. Try with Root permission $ 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: gedit /etc/wvdial.conf will be able to dial out with Root permission: wvdial In any case, Puppy Linux usually supports most pci modems. So your system appears to lack a modem device. Best Regards, Antonio On Sun, Aug 18, 2013 at 9:46 PM, sansriraj@xxxxxxxxx <sansriraj@xxxxxxxxx> wrote: > 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 TEENpup Linux > Linux 2.6.25.16 [i686 arch] kernel 2.6.25.16 > 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, TEENpup > Linux , ALSA_version= > Linux version 2.6.25.16 (root@(none)) (gcc version 4.2.2) #1 Tue Aug 26 > 10:45:53 GMT-8 2008 > scanModem update of: 2011_08_08 > The modem symbolic link is /dev/modem -> ttyS0 > /etc/lsb-release not found > > > 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: > > Checking /proc/bus/usb/devices > USB modem not detected among /proc/bus/usb/devices. > > Candidate PCI devices with modem chips are: > High Definition Audio cards can host modem chips. > > === Finished firmware and bootup diagnostics, next deducing cogent software. > === > > A candidate modem is not transparent among the PCI devices: > ------------------------------------------------ > 00:00.0 Class 0600: 8086:7124 (rev 03) > 00:01.0 Class 0300: 8086:7125 (rev 03) > 00:1e.0 Class 0604: 8086:2418 (rev 02) > 00:1f.0 Class 0601: 8086:2410 (rev 02) > 00:1f.1 Class 0101: 8086:2411 (rev 02) > 00:1f.2 Class 0c03: 8086:2412 (rev 02) > 00:1f.3 Class 0c05: 8086:2413 (rev 02) > 01:00.0 Class 0200: 10ec:8139 (rev 10) > 01:0a.0 Class 0c03: 1106:3038 (rev 62) > 01:0a.1 Class 0c03: 1106:3038 (rev 62) > 01:0a.2 Class 0c03: 1106:3104 (rev 65) > ------------------------------------------------ > with USB, bridge, and RAM devices not displayed. > If a High Definition Audio card is present, if might be hosted on the > Subsystem. > > If your modem is an > external USB type, > connected by an external serial cable, > or mounted internally on an ISA card, > then scanModem would not access it. > > Try with Root permission > $ 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: > gedit /etc/wvdial.conf > will be able to dial out with Root permission: > 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 base of the UDEV device file system is: /dev/.udev > > The kernel was compiled with gcc version 4.2.2 and a compiler is not > installed > > linux-headers-2.6.25.16 resources needed for compiling are not manifestly > ready! > The code linking utility, ld, may be needed and is provided in the binutils > package > The patch utility is needed for compiling ALSA drivers, and possibly others. > > If compiling is necessary packages must be installed, providing: > gcc-4.2 make kernel-source-2.6.25.16 > > > 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: > -r-xr-xr-x 1 root root 318816 2007-10-19 01:44 /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 > defaultroute > noipdefault > noauth > usepeerdns > modem > 115200 > crtscts > debug > asyncmap 0 > name "barney" > > 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: eth0 > Which can interfere with Browser naviagation. > > Don't worry about the following, it is for experts should trouble shooting > be necessary. > ========================================================== > > #v413 Loads modules for modems not autodetected by kernel > > #Intel Corporation 536EP Data Fax Modem > SYSFS{vendor}=="0x8086", SYSFS{device}=="0x1040", > RUN+="/sbin/pup_event_backend_modprobe Intel536" > > #Intel Corporation 537EP Data Fax Modem > SYSFS{vendor}=="0xe159", SYSFS{device}=="0x0001", > RUN+="/sbin/pup_event_backend_modprobe Intel537" > > #Mwave modems > SYSFS{vendor}=="0x1014", SYSFS{device}=="0x007d", > RUN+="/sbin/pup_event_backend_modprobe mwave" > > #Agere modems > SYSFS{vendor}=="0x11c1", SYSFS{device}=="0x048[cf]", > RUN+="/sbin/pup_event_backend_modprobe agrserial" > > > #Lucent Integrated ISA modems - implied by presence of PC-to-ISA bridge > #If you need this rule, remove the "#" from the next line. Some PCs might > show a modem installed even though not actually present. Uncomment the line > only if you know you have a built-in Lucent modem that is not already > recognized. > #SYSFS{vendor}=="0x8086", SYSFS{device}=="0x7110", > RUN+="/sbin/pup_event_backend_modprobe ltserial" > > > Checking for modem support lines: > -------------------------------------- > /device/modem symbolic link: lrwxrwxrwx 1 root root 5 2013-08-15 20:58 > /dev/modem -> ttyS0 > slmodemd created symbolic link /dev/ttySL0: Within /etc/udev/ files: > /etc/udev/rules.d/60-udev-modem.rules:#v413 Loads modules for modems not > autodetected by kernel > /etc/udev/rules.d/60-udev-modem.rules:#Mwave modems > /etc/udev/rules.d/60-udev-modem.rules:#Agere modems > /etc/udev/rules.d/60-udev-modem.rules:#Lucent Integrated ISA modems - > implied by presence of PC-to-ISA bridge > /etc/udev/rules.d/60-udev-modem.rules:#If you need this rule, remove the "#" > from the next line. Some PCs might show a modem installed even though not > actually present. Uncomment the line only if you know you have a built-in > Lucent modem that is not already recognized. > Within /etc/modprobe.conf files: > > Within any ancient /etc/devfs files: > > Within ancient kernel 2.4.n /etc/module.conf files: > /etc/modules/firmware.dep.2.6.25.16:#a firmware pkg can have a post-install > script -- see slmodem example. > /etc/modules/firmware.dep.2.6.25.16:#analog modem drivers... > /etc/modules/firmware.dep.2.6.25.16:dgcmodem:dgcusbdcp.ko > /etc/modules/firmware.dep.2.6.25.16:ltmodem:ltserial.ko > /etc/modules/firmware.dep.2.6.25.16:slmodem:slamr.ko,slusb.ko,snd-via82xx-modem.ko,snd-atiixp-modem.ko,snd-intel8x0m.ko,snd-hda-intel.ko > --------- end modem support lines -------- >