Umutay Both ungrad-winmodem.ko and slamr.ko modules must be compiled and installed.After a new bootup. $ su root# mknod -m 660 /dev/slamr0 c 242 0Check with:# ls -l /dev/slamr0 Load the drivers in order:# modprobe ungrab-winmodem# modprobe slamr Activate the modem (use USA for testing)# slmodemd -c USA /dev/slamr0should announce creation of ports /dev/ttySL0 --> /dev/pts/N If this works, open a 2nd console, and therein:# wvdialconf /etc/wvdial.confshould find the modem Read the wvdial.txt on info how to edit /etc/wvdial.conf , beforetrying to dialout with:# vwdial Automation can be achieved later MarvS On Jan 2, 2008 6:56 PM, Umutay Midinova <mumutay@xxxxx> wrote:> Marvin Stodolsky пишет:>> > Antonio,> >> > Please manage this case. This Motorala chipset is slamr supported.> >> > Umutay,> > Follow:> > compiling drivers is necessary. As of October 2007 the current packages at> > http://linmodems.technion.ac.il/packages/smartlink/ are the> > ungrab-winmodem-20070505.tar.gz and slmodem-2.9.11-20070813.tar.gz> >> > read the Smartlink.txt> >> > MarvS> > scanModem maintainer> >> >> > On Dec 28, 2007 1:04 PM, Umutay Midinova <mumutay@xxxxx> wrote:> >> >> Hello,> >>> >> I need help with installation of Winmodem at Linux,> >> I am a beginner to Linux.> >>> >> Thank you in advance> >>> >> Umutay> >>> >>> >> 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 PCLinuxOS release 2007 (PCLinuxOS) for i586> >> Kernel 2.6.18.8.tex5.lgc on an i686 / kernel 2.6.18.8.tex5.lgc> >> 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> >> 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, PCLinuxOS release 2007 (PCLinuxOS) for i586> >> Kernel 2.6.18.8.tex5.lgc on an i686 /> >> Linux version 2.6.18.8.tex5.lgc (vaughan@localhost) (gcc version 4.1.1 20060724 (prerelease) (4.1.1-4pclos2007)) #1 Thu May 10 11:55:36 WST 2007> >> scanModem update of: 2007-12-07> >>> >>> >> There are no blacklisted modem drivers in /etc/modprobe* files> >>> >> The Advanced Linux Sound Architecture (ALSA) packages providing audio support on your System,> >> also includes drivers for some modems. High Definition Audio (HDA) cards can themselves host> >> a softmodem chipset, with both audio+modem supported by a snd-hda-intel driver.> >> The ALSA diagnostics are written during bootup to /proc/asound/ folders.> >>> >>> >> Modem not detected though HDA card diagnostics, though not excluding> >> a possible Conexant modem chip impervious to ALSA diagnostics.> >> Proceeding through alternative possibilties.> >>> >> Summary card and chipset information is in:> >> /proc/asound/cards:> >> --- no soundcards ---> >>> >> /proc/asound/pcm:> >>> >>> >> A copy of /proc/asound had been copied to Modem/ALSAumutay.tgz> >> USB modem not detected by lsusb> >>> >> For candidate card, firmware information and bootup diagnostics are:> >>> >> PCI slot PCI ID SubsystemID Name> >> ---------- --------- --------- --------------> >> 01:07.0 1057:3052 1057:3020 Modem: Motorola SM56 Data Fax Modem> >>> >> Modem interrupt assignment and sharing:> >> --- Bootup diagnostics for card in PCI slot 01:07.0 ----> >>> >> === Finished modem firmware and bootup diagnostics section. ===> >> === Next deducing cogent software ===> >>> >>> >> There is candidate modem software.> >>> >> For candidate modem in PCI bus: 01:07.0> >> Class 0703: 1057:3052 Modem: Motorola SM56 Data Fax Modem> >> Primary PCI_id 1057:3052> >> Support type needed or chipset: slamr> >>> >>> >>> >> 1057:3052 has a Motorola chipset, poorly supported by Motorola itself> >> However Zello discovered that drivers written to support Smartlink modems do support the 1057:3052 chipset!!> >> It sufficed to add 1057:3052 to the list of modem cards recognized by the Smartlink slamr driver.> >> There is a ungrab-winmodem driver used in conjunction with slamr, which must have 1057:3052> >> similarly added. See messages from Zello:> >> http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00846.html> >> http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00848.html> >> and Alvaro Aguirre about the ungrab-winmodem fix:> >> http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00990.html> >> For general guidance on ungrab-winmodem + slamr usage, read the Smartlink.txt> >>> >> The modem is supported by the Smartlink slamr driver> >> plus the slmodemd helper utility. Read the> >> Smartlink.txt and Modem/YourSystem.txt for follow through guidance.> >>> >>> >> For 2.6.18.8.tex5.lgc compiling drivers is necessary. As of October 2007 the current packages at> >> http://linmodems.technion.ac.il/packages/smartlink/ are the> >> ungrab-winmodem-20070505.tar.gz and slmodem-2.9.11-20070813.tar.gz> >>> >> Writing Smartlink.txt> >> ============ end Smartlink section =====================> >>> >> Completed candidate modem analyses.> >>> >> The base of the UDEV device file system is: /dev/.udev> >> /dev/.udevdb> >>> >> Versions adequately match for the compiler installed: 4.1.1> >> and the compiler used in kernel assembly: 4.1.1> >>> >>> >>> >> Minimal compiling resources appear complete:> >> make utility - /usr/bin/make> >> Compiler version 4.1> >> linuc_headers base folder /lib/modules/2.6.18.8.tex5.lgc/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.> >>> >>> >>> >> 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 pacakage> >> 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-t 1 root root 304536 Nov 7 2006 /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)> >> chmod a+x /usr/sbin/pppd> >> or under Ubuntu related Linuxes> >> chmod a+x /usr/sbin/pppd> >>> >> Checking settings of: /etc/ppp/options> >>> >>> >> 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> >>> >>> >> 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 --------> >>> >>> >>> >>> >> >> Hello I am again,>> I did everything following given instructions, but I didn't compile> driver, coundn't figure out what it is. Anyhow I got the result ending> with the text: modem 'slamr0' created. But that is all. No signs of> modem anywhere. Not in dmesg, wwvdial reads as no modem detected,> minicom - couldn't open dev/ modem (after doing symbolic link). Having> made setserial assinging port - no results.> Do you think is there a proper modem driver in the system or not.> Suppose the fact that I am a quite beginner to Linux I did things> without figuring out what is really going on.>> What kind of modems really will help me, I mean something that will work> without compiling drivers and so on?>> I am looking forward to your answer.>> Thank you in advance>> Kind regards,>> Umutay>>>
