Lee, If you want to get the Motorola modem functioning install the package sl-modem-daemon, which will automate port setup MarvS scanModem maintainer On Mon, Oct 18, 2010 at 4:42 PM, Lee Hinkleman <leehinkleman@xxxxxxxxx> wrote: > Hi Jacques: > The USR Serial Controller modem is in perfect condition, and dialed now. > The Motorola SM56 modem almost worked, in Debian 5 minutes ago, but 'script > timed out' during initialization, and there was no init 2 command...only ATZ > for Âinit 1, so maybe init 2 was needed. > And you were absolutely correct to say that I 'forgot' that keystrokes Ctl+C > terminated slmodemd, and I should have used Alt+F2 for a new shell, which I > used this morning, to see > wvdialconf /etc/wvdial.conf > find the slmodem OK. > When I rebooted into Debian Etch, then the /dev/ttySL0 symbolic link and its > target /dev/pts/0 again were missing, but I decided not to re-install it > again, and will use just the USR serial modem for now. > Also, I saw several of those PCI slot USR serial controller modems on ebay > last week, and they didn't seem expensive... > Te SM56 modem was brought to me in a 'retired' office computer last week, > and I really just wanted to see if it could work in Debian Etch. > Thanks very much for your help. > Regards, > Lee > ----- Original Message ----- From: "Jacques Goldberg" > <Jacques.Goldberg@xxxxxxx> > To: "Antonio Olivares" <olivares14031@xxxxxxxxx> > Cc: "Linmodems" <discuss@xxxxxxxxxxxxx> > Sent: 19 October, 2010 2:07 AM > Subject: Re: Lee Hinkleman, NZ, 2.6.18-6-686 > > >> >> >> Lee >> >> >> Earlier, I directly answered the question about missing files/pseudofiles >> >> >> You are the lucky owner of a true hardware controller internal modem, not >> a winmodem. >> >> This modem does not need any linmodems driver. >> >> It works with the standard serial driver built in all Linux distributions. >> >> This modem is probably quite old and might however not be in running >> condition. >> >> In any case, please use wvdial tools and not kppp when you debug a modem. >> >> Remove the slmodemd installation, it can only cause trouble when you do >> not need it. >> >> >> sudo wvdialconf   Âshould recognize your modem. >> >> If it does not, move the modem to some other PCI slot of the PC. >> >> But please remember, if my guess is right, it is likely about 5-10 years >> old and might be out of order. >> >> >> The reason why we recommend the wvdial tools is that you see a lot of >> progress messages, hidden by kppp. >> >> If kppp is not properly configured, you won't see it, and believe that the >> modem is not detected.. >> >> >> Jacques >> >> >> >> On 10/18/2010 02:58 PM, Antonio Olivares wrote: >> >>> Lee, >>> >>> For the modem that you are working with, if you loaded the >>> ungrab-winmodem and slamr modules all you need is to run >>> >>> $ sudo wvdialconf /etc/wvdial.conf >>> >>> Also you might not consider working with the drivers above if you have >>> a supported driver via serial driver: >>> >>> Predictive Âdiagnostics for card in bus 05:09.0: >>> Modem chipset Âdetected on >>> NAME="Serial controller: 3Com Corp, Modem Division 56K FaxModem Model >>> 5610 " >>> CLASS=0700 >>> PCIDEV=12b9:1008 >>> SUBSYS=12b9:00a2 >>> IRQ=209 >>> IDENT=USrobotics.serial >>> >>> For candidate modem in: Â05:09.0 >>> Â0700 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model >>> 5610 >>>   Primary device ID: Â12b9:1008 >>> Support type needed or chipset: USrobotics.serial >>> >>> >>> Vendor 10b7 3COM Inc. purchased the vendor 12b9 US Robotics modem >>> technology. >>> Their winmodems have no Linux support. Their controller chipset modems >>> are supported by the Linux serial drivers. >>> The PCI id 12b9:1008 modem is Supported. >>> >>> PCI ID     ÂName                  ÂSupport status >>> >>> ------------------------------------------------------------------------------- >>> 10b7:1006 3COM 0038TA AC101 - TF Mini-PCI Âwinmodem, not supported >>> 10b7:1007 3COM 3C556 V.90 Mini-PCI Âwinmodem, not supported >>> 12b9:1006 US Robotics 3cp803598 ÂVoice Âwinmodem, not supported >>> 12b9:1007 US Robotics ERL3263A-0 DF GWPCI PC99 winmodem, not supported >>> >>> 12b9:0062 US Robotics erk41926a-0.6 usr 56k serial driver supported >>> 12b9:1008 US Robotics 3cp803598         serial driver supported >>>  Âwvdialconf wvtest   , should detect the modem. Read DOCs/Testing.txt >>> Â====== end 3COM section ======= >>> >>> $ sudo wvdialconf /etc/wvdial.conf >>> might find it. ÂTry it and report back. >>> >>> Regards, >>> >>> Antonio >>> >>> On Sun, Oct 17, 2010 at 10:08 PM, Lee Hinkleman<leehinkleman@xxxxxxxxx> >>> wrote: >>>> >>>> Hi Antonio and Marvin: >>>> My Motorola modem seemed to install, and modprobe ungrab-winmodem, >>>> followed >>>> by modprobe slamr, followed by slmodemd -c NZ /dev/slamr0 produced a >>>> 'Bad >>>> country!' warning, so I changed to USA, and /dev/ttySL0 as a symbolic >>>> link >>>> from /dev/pts/0 seemed to be made OK. >>>> But ls -l in /dev never showed either /dev/ttySL0 or /pts/0... >>>> /dev/pts seemed to be always empty. >>>> I've attached ModemData.txt. >>>> Thanks for your help. >>>> Sincerely, >>>> Lee Hinkleman >>>> >>>> >>>> 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.18-6-686 >>>> 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, Âdebian , ÂALSA_version=1.0.12 >>>> Linux version 2.6.18-6-686 (Debian 2.6.18.dfsg.1-22) (dannf@xxxxxxxxxx) >>>> (gcc >>>> version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Tue Jun 17 >>>> 21:31:27 UTC 2008 >>>> scanModem update of: Â2010_05_29 >>>> >>>> /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: >>>> >>>> >>>> Attached USB devices are: >>>> ID 058f:6369 Alcor Micro Corp. >>>> If a cellphone is not detected, see >>>> http://ubuntuforums.org/archive/index.php/t-878554.html >>>> A sample report is: >>>> http://linmodems.technion.ac.il/bigarch/archive-nineth/msg00578.html >>>> >>>> If a USB modem or cellphone is attached and was not detected, please >>>> provide available information in your request to discuss@xxxxxxxxxxxxx >>>> >>>> Candidate PCI devices with modem chips are: >>>> 05:04.0 Modem: Motorola Unknown device 3052 (rev 04) >>>> 05:09.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model >>>> 5610 >>>> (rev 01) >>>> High Definition Audio cards can host modem chips. >>>> >>>> For candidate card in slot 05:04.0, firmware information and bootup >>>> diagnostics are: >>>> PCI slot PCI ID ÂSubsystemID Name >>>> ---------- --------- --------- -------------- >>>> 05:04.0 1057:3052 1057:3020 Modem: Motorola Unknown device 3052 >>>> >>>> Modem interrupt assignment and sharing: >>>> --- Bootup diagnostics for card in PCI slot 05:04.0 ---- >>>> ACPI: PCI Interrupt 0000:05:04.0[A] -> ÂGSI 16 (level, low) -> ÂIRQ 201 >>>> 0000:05:04.0: ttyS1 at I/O 0x1008 (irq = 201) is a 16450 >>>> 0000:05:04.0: ttyS2 at I/O 0x1010 (irq = 201) is a 8250 >>>> 0000:05:04.0: ttyS3 at I/O 0x1018 (irq = 201) is a 16450 >>>> Couldn't register serial port 0000:05:04.0: -28 >>>> >>>> For candidate card in slot 05:09.0, firmware information and bootup >>>> diagnostics are: >>>> PCI slot PCI ID ÂSubsystemID Name >>>> ---------- --------- --------- -------------- >>>> 05:09.0 12b9:1008 12b9:00a2 Serial controller: 3Com Corp, Modem Division >>>> 56K >>>> FaxModem Model 5610 >>>> >>>> Modem interrupt assignment and sharing: >>>> 209:     Â0  IO-APIC-level Âuhci_hcd:usb2 >>>> --- Bootup diagnostics for card in PCI slot 05:09.0 ---- >>>> ACPI: PCI Interrupt 0000:05:09.0[A] -> ÂGSI 18 (level, low) -> ÂIRQ 209 >>>> Couldn't register serial port 0000:05:09.0: -28 >>>> >>>> === Finished firmware and bootup diagnostics, next deducing cogent >>>> software. >>>> === >>>> >>>> Predictive Âdiagnostics for card in bus 05:04.0: >>>> Modem chipset Âdetected on >>>> NAME="Modem: Motorola Unknown device 3052 " >>>> CLASS=0703 >>>> PCIDEV=1057:3052 >>>> SUBSYS=1057:3020 >>>> IRQ=201 >>>> IDENT=slamr >>>> >>>> For candidate modem in: Â05:04.0 >>>> Â0703 Modem: Motorola Unknown device 3052 >>>>   Primary device 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 >>>> DOCs/Smartlink.txt >>>> >>>> The modem is supported by the Smartlink >>>> plus the slmodemd helper utility. ÂRead the >>>> DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through >>>> guidance. >>>> >>>> >>>> For 2.6.18-6-686 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-20080126.tar.gz >>>> >>>> Writing DOCs/Smartlink.txt >>>> ============ end Smartlink section ===================== >>>> Vendor 10b7 3COM Inc. purchased the vendor 12b9 US Robotics modem >>>> technology. >>>> Their winmodems have no Linux support. Their controller chipset modems >>>> are supported by the Linux serial drivers. >>>> The PCI id 1057:3052 modem is Uncertain_support_status. >>>> >>>> PCI ID     ÂName                  ÂSupport status >>>> >>>> ------------------------------------------------------------------------------- >>>> 10b7:1006 3COM 0038TA AC101 - TF Mini-PCI Âwinmodem, not supported >>>> 10b7:1007 3COM 3C556 V.90 Mini-PCI Âwinmodem, not supported >>>> 12b9:1006 US Robotics 3cp803598 ÂVoice Âwinmodem, not supported >>>> 12b9:1007 US Robotics ERL3263A-0 DF GWPCI PC99 winmodem, not supported >>>> >>>> 12b9:0062 US Robotics erk41926a-0.6 usr 56k serial driver supported >>>> 12b9:1008 US Robotics 3cp803598         serial driver supported >>>> >>>> Â====== end 3COM section ======= >>>> >>>> >>>> Predictive Âdiagnostics for card in bus 05:09.0: >>>> Modem chipset Âdetected on >>>> NAME="Serial controller: 3Com Corp, Modem Division 56K FaxModem Model >>>> 5610 " >>>> CLASS=0700 >>>> PCIDEV=12b9:1008 >>>> SUBSYS=12b9:00a2 >>>> IRQ=209 >>>> IDENT=USrobotics.serial >>>> >>>> For candidate modem in: Â05:09.0 >>>> Â0700 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model >>>> 5610 >>>>   Primary device ID: Â12b9:1008 >>>> Support type needed or chipset: USrobotics.serial >>>> >>>> >>>> Vendor 10b7 3COM Inc. purchased the vendor 12b9 US Robotics modem >>>> technology. >>>> Their winmodems have no Linux support. Their controller chipset modems >>>> are supported by the Linux serial drivers. >>>> The PCI id 12b9:1008 modem is Supported. >>>> >>>> PCI ID     ÂName                  ÂSupport status >>>> >>>> ------------------------------------------------------------------------------- >>>> 10b7:1006 3COM 0038TA AC101 - TF Mini-PCI Âwinmodem, not supported >>>> 10b7:1007 3COM 3C556 V.90 Mini-PCI Âwinmodem, not supported >>>> 12b9:1006 US Robotics 3cp803598 ÂVoice Âwinmodem, not supported >>>> 12b9:1007 US Robotics ERL3263A-0 DF GWPCI PC99 winmodem, not supported >>>> >>>> 12b9:0062 US Robotics erk41926a-0.6 usr 56k serial driver supported >>>> 12b9:1008 US Robotics 3cp803598         serial driver supported >>>>  Âwvdialconf wvtest   , should detect the modem. Read >>>> DOCs/Testing.txt >>>> Â====== end 3COM section ======= >>>> >>>> Completed candidate modem analyses. >>>> >>>> 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.18-6-686/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 needed. 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. >>>> >>>> >>>> Compressed files at: /usr/src/linux-source-2.6.18.tar.bz2 >>>> >>>> For Debian and some related distributions, a package >>>> kernel-kbuild-2.6-18 >>>> may be needed to support driver compiling. >>>> >>>> >>>> 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 260920 2007-03-18 10:52 /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 >>>> asyncmap 0 >>>> auth >>>> 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 >>>> >>>> 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. >>>> >>>> >>>> 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: >>>> >>>>  ÂWithin any ancient /etc/devfs files: >>>> >>>>  ÂWithin ancient kernel 2.4.n /etc/module.conf files: >>>> >>>> --------- end modem support lines -------- >>>> >>>> For Debian users, the linux-headers-2.6.18-6-686.deb can be used instead >>>> of >>>> kernel-source/ >>>> >>>> >>>> >> > >
