David RE: I tried following the instructions regarding the compiling of drivers, but that ended badly. You don't have to compile, ONLY install. >From http://linmodems.technion.ac.il/packages/smartlink/Ubuntu/ get the slamr-2.6.20-15-386.tar.gz Under Linux unpack with $ tar zxf slamr*.tar.gz Browse the files in the unpacked folder slamr-2.6.20-15-386/ Move into it with: $ cd slamr-2.6.20-15-386 Then run $ sudo ./setup The older Motorola packages are valueless for these newer kernels. But numerous are using these slamr package resources. MarvS MarvS On 9/19/07, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: > 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. > > > Download slamr-2.6.20-15-386.tar.gz from > http://linmodems.technion.il/packages/smartlink/ubunutu > under Linux, open a terminal and unpack with: > $ tar zxvf slamr*.tgz > Move into the unpacked folder > $ cd slamr-2.6.20-15-386 > Look around > $ ls > Run the > $ sudo ./setup > > Afterwards do: > $ slmodemd --help > $ slmodemd --countrylist &> Clist.txt > If not in the USA, look for your COUNTRY_NAME therein. > Do and edit with: > $ sudo gedit /etc/default/sl-modem-daemon > and therein replace the USA in the line: > SLMODEMD_COUNTRY=USA > This will provide for the correct Country setting in the automated: > slmodemd -c COUNTRY /dev/slamr0 > > Read the Smartlink.txt and YourSystem.txt > > > > ---------- Forwarded message ---------- > From: "David Dallas" <davedallas@xxxxxxxxxxxx> > To: <DISCUSS@xxxxxxxxxxxxx> > Date: Wed, 19 Sep 2007 18:00:57 +0200 > Subject: David Dallas, SOUTHAFRICA kernel 2.6.20-15-386 > Hi there. > > My modem is a Motorola SM56 data+fax modem and I'm running Ubuntu Feisty. > I'm having trouble figuring out what to do next. I tried following the > instructions regarding the compiling of drivers, but that ended badly. I > think the files I used were for a much older kernel or for the wrong > chipset. The links to Motorola sites on Linmodem go to pages which only have > windows drivers. On the Linmodem packages site, where the old motorola .rpm > packages are, I read that kernel 2.6 packages were available, but I couldn't > find them. I've read about using alien to convert the old .rpm's to .deb but > I get the feeling that it won't work with the old kernel. > > I'm fairly new at this and really need help. > > Thank you > > David Dallas > > > ---------------------------------------------------------------------------- > -- > > > Only plain text email is forwarded by the DISCUSS@xxxxxxxxxxxxx List > Server. > Do use the following as the email Subject Line: > SomeName, YourCountry kernel 2.6.20-15-386 > This will alert cogent experts, and distinguish cases in the Archives. > YourCountry will enable Country Code guidance. > Occassionally responses are blocked by an Internet Provider mail filters. > So in a day, also check the Archived responses at http://www.linmodems.org > . > Local Linux experts can be found through: > http://www.linux.org/groups/index.html > -------------------------- System information ---------------------------- > CPU=i686, > Linux version 2.6.20-15-386 (root@palmer) (gcc version 4.1.2 (Ubuntu > 4.1.2-0ubuntu4)) #2 Sun Apr 15 07:34:00 UTC 2007 > scanModem update of: 2007_August_28 > > > There are no blacklisted modem drivers in /etc/modprobe* files > USB modem not detected by lsusb > > > Several modems are supported by drivers with ALSA, the Advanced Linux Sound > Architecture software. > Copying ALSA diagnostics to Modem/ALSAroot.tgz > ALSAversion = 1.0.13 > > Modem or candidate host audio card have firmware information and > diagnostics: > > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 00:0a.0 1057:3052 1631:3034 Modem: Motorola Unknown > device 3052 > > Modem interrupt assignment and sharing: > 18: 1549 IO-APIC-fasteoi HDA Intel > --- Bootup diagnostics for card in PCI slot 00:0a.0 ---- > [ 23.375467] ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 17 (level, low) -> > IRQ 18 > [ 23.375607] 0000:00:0a.0: ttyS0 at I/O 0xf808 (irq = 18) is a 16450 > [ 23.375679] 0000:00:0a.0: ttyS1 at I/O 0xf810 (irq = 18) is a 8250 > [ 23.375751] 0000:00:0a.0: ttyS2 at I/O 0xf818 (irq = 18) is a 16450 > [ 23.375823] 0000:00:0a.0: ttyS3 at I/O 0xf820 (irq = 18) is a 8250 > [ 23.375853] Couldn't register serial port 0000:00:0a.0: -28 > > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 80:01.0 1106:3288 1631:e028 Audio device: VIA > Technologies, Inc. VIA High Definition Audio Controller > > Modem interrupt assignment and sharing: > 18: 1549 IO-APIC-fasteoi HDA Intel > --- Bootup diagnostics for card in PCI slot 80:01.0 ---- > [ 40.661154] ACPI: PCI Interrupt 0000:80:01.0[A] -> GSI 17 (level, low) -> > IRQ 18 > [ 40.661168] PCI: Setting latency timer of device 0000:80:01.0 to 64 > > === Finished modem firmware and bootup diagnostics section. === > === Next deducing cogent software === > > 1106:3288 is a High Definition Audio card, possibly hosting a soft modem. > ---ALSA bootup diagnostics --- > and a NEW HDA softmodem controller. > CodecFiles not found > The NotDetermined is not supported by this kernel. >
