Oleksandr RE: 02:0c.0 Modem: Motorola SM56 Data Fax Modem (rev 04) ---- Please return the output of $ lspci -s 02:0c.0 -n scanModem should have done this automatically! Please do: # bash -x ./scanModem 2.>&1 | tee olek # gzip olek and send me the olek.gz MarvS scanModem maintainer On Tue, Apr 22, 2008 at 4:48 PM, Oleksandr Osypenko <os-oleksandr@xxxxxxx> 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 > Welcome to openSUSE 10.3 (i586) - Kernel kernel 2.6.22.5-31-default > With this Subject Line cogent experts will be alerted, and useful case > names left in the Archive. > YourCountry will enable Country specific guidance. Your contry's local > Linux experts > 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, > Welcome to openSUSE 10.3 (i586) - Kernel > Linux version 2.6.22.5-31-default (geeko@buildhost) (gcc version 4.2.1 > (SUSE Linux)) #1 SMP 2007/09/21 22:29:00 UTC > scanModem update of: 2008_04_16 > > There are no blacklisted modem drivers in /etc/modprobe* files > Checking /proc/bus/usb/devices > /proc/bus/usb/devices file not present, barring USB modem query. > > === Finished firmware and bootup diagnostics, next deducing cogent > software. === > > A candidate modem is not evident among the PCI devices: > ------------------------------------------------ > 00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 Controller (rev > 05) > 00:1f.3 SMBus: Intel Corporation 82801BA/BAM SMBus Controller (rev 05) > 00:1f.5 Multimedia audio controller: Intel Corporation 82801BA/BAM AC'97 > Audio Controller (rev 05) > 01:00.0 VGA compatible controller: nVidia Corporation NV44A [GeForce 6200] > (rev a1) > 02:09.0 Multimedia controller: Philips Semiconductors SAA7134/SAA7135HL > Video Broadcast Decoder (rev 01) > 02:0a.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev > 10) > 02:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. > RTL-8139/8139C/8139C+ (rev 10) > 02:0c.0 Modem: Motorola SM56 Data Fax Modem (rev 04) > ------------------------------------------------ > 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 > $ wvdialconf /etc/wvdial.conf > to detect these modem types and some USB modems. > If the detection is successful, read the 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. > 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/ALSAsandr.tgz > > A UDEV device file system is not active. > > The kernel was compiled with gcc version 4.2.1 and a compiler is not > installed > > linux-headers-2.6.22.5-31-default resources needed for compiling are not > manifestly ready! > > If compiling is necessary packages must be installed, providing: > gcc-4.2 kernel-source-2.6.22.5-31-default > > > 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 package > 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: > -rwxr-xr-x 1 root dialout 298784 2007-09-22 02:41 /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 > noipdefault > noauth > crtscts > lock > modem > asyncmap 0 > nodetach > lcp-echo-interval 30 > lcp-echo-failure 4 > lcp-max-configure 60 > lcp-restart 2 > idle 600 > noipx > file /etc/ppp/filters > > 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 modem0 > 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: > > Within /etc/modprobe.conf files: > > Within any ancient /etc/devfs files: > > Within ancient kernel 2.4.n /etc/module.conf files: > > --------- end modem support lines -------- > > >