Arch Linux

sacarde

Member

Registered: 2006-07-14

Posts: 389

problem module slmodem

helo,
in case of fault of my ADSL, I have old internel modem: motorola SM56.
I read it have chipset smlink

I found and install arch packages slmodem and slmodem-utility

but when I run:

slmodemd --country=ITALY /dev/slamr0

I have :

error: mdm setup: cannot open dev `/dev/slamr0': No such device or address
error: cannot setup device `/dev/slamr0'

p.s.
I remark this
if I run:
modprobe slamr

I have:

FATAL: Error inserting slamr (/lib/modules/2.6.18-viper/kernel/drivers/net/slamr.ko): Invalid module format

this error in kernel beyond too

cheer

Member

From: Russia, St. Petersburg

Registered: 2006-08-02

Posts: 131

Re: problem module slmodem

On russian Arch forum there was also such a problem. It's a possible bug in Archlinux, someone said that compiling module from sources helps. Try it.

byte

Member

From: Düsseldorf (DE)

Registered: 2006-05-01

Posts: 2,046

Re: problem module slmodem

http://archlinux.org/packages/search/?q=slmodem

You'll notice that there is no package for a -viper kernel, so take a look at the PKGBUILD and build it yourself.

---

1000

sacarde

Member

Registered: 2006-07-14

Posts: 389

Re: problem module slmodem

I install and reboot with beyond

and I have:

modprobe slamr
OK

slmodemd --country=ITALY /dev/slamr0

error: mdm setup: cannot open dev `/dev/slamr0': No such device
error: cannot setup device `/dev/slamr0'

p.s.
I have
pci bus 0x0000 cardnum 0x09 function 0x00: vendor 0x11d4 device 0x1805
Analog Devices SM56 PCI modem

sacarde

Member

Registered: 2006-07-14

Posts: 389

Re: problem module slmodem

I ask for my problem in  site www.linmodems.org

they reply:

1)
A driver is NOT available for this kernel 2.6.17-beyond.

Motorola seems to be only providing source code to some equipment mnaufacturers,
who may provide particular compiled Linux drivers with their products.
See details in Motorola.txt

There was however success with a 2.6.9-1.667 kernel under Fedora Core 3. Search the archives, maybe you can try and make it work. Your best bet is to look for another modem.

2)
SM56 modem is not compatible with SmartLink driver.

3)
For Underground Desktop 022 (
Linux version 2.6.17-beyond (root@sara) (gcc version 4.1.1)
there is no driver. The single driver for Motorola hardware under 2.6
kernels is for
Fedora kernel 2.6.9-1.667 and only rare updates can be anticipated.

For facile service under Linux, another modem will be needed.
Read InfoGeneral.txt about alternatives.

Jacob

Member

Registered: 2005-03-19

Posts: 52

Re: problem module slmodem

I have similar problem... the slmodem package is borked... I can't imagine the package working for anyone, and I can't imagine how to compile it myself.  This is what I get:

[root@fluke slmodem]# makepkg
==> Making package: slmodem 2.9.11-21 (Mon Feb 19 20:22:19 EST 2007)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
==>     Using local copy of slmodem-2.9.11-20051101.tar.gz
==>     Using local copy of ungrab-winmodem.tar.gz
==>     Found 2.6.16.patch in build dir
==>     Found module-parm.patch in build dir
==>     Found 2.6.18-utsrelease.patch in build dir
==>     Found 2.6.18-devfs.patch in build dir
==>     Found kernel-2.6.19.patch in build dir
==> Validating source files with MD5sums
    slmodem-2.9.11-20051101.tar.gz ... Passed
    ungrab-winmodem.tar.gz ... Passed
    2.6.16.patch ... Passed
    module-parm.patch ... FAILED
    2.6.18-utsrelease.patch ... Passed
    2.6.18-devfs.patch ... Passed
    kernel-2.6.19.patch ... FAILED
==> ERROR: One or more files did not pass the validity check!
[root@fluke slmodem]#         

If I fudge the md5sums of the two above files I get this:

[root@fluke slmodem]# makepkg
==> Making package: slmodem 2.9.11-21 (Mon Feb 19 20:23:28 EST 2007)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
==>     Using local copy of slmodem-2.9.11-20051101.tar.gz
==>     Using local copy of ungrab-winmodem.tar.gz
==>     Found 2.6.16.patch in build dir
==>     Found module-parm.patch in build dir
==>     Found 2.6.18-utsrelease.patch in build dir
==>     Found 2.6.18-devfs.patch in build dir
==>     Found kernel-2.6.19.patch in build dir
==> Validating source files with MD5sums
    slmodem-2.9.11-20051101.tar.gz ... Passed
    ungrab-winmodem.tar.gz ... Passed
    2.6.16.patch ... Passed
    module-parm.patch ... Passed
    2.6.18-utsrelease.patch ... Passed
    2.6.18-devfs.patch ... Passed
    kernel-2.6.19.patch ... Passed
==> Extracting Sources...
==>     tar --use-compress-program=gzip -xf slmodem-2.9.11-20051101.tar.gz
==>     tar --use-compress-program=gzip -xf ungrab-winmodem.tar.gz
==> Removing existing pkg/ directory...
==> Starting build()...
patching file ungrab-winmodem/ungrab-winmodem.c
can't find file to patch at input line 13
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- slmodem-2.9.11-20061021/drivers/amrmo_init.c~      2006-10-17 19:08:16.000000000 +0200
|+++ slmodem-2.9.11-20061021/drivers/amrmo_init.c       2006-10-17 19:08:27.000000000 +0200
--------------------------
File to patch:                             

And that's where it hangs...  Plus I am not sure how important the "ungrab-winmodem" and "kernel-2.6.19" patches are?

My $0.02,

Jacob