FC4 problems compiling the smartlink modem driver on a toshiba satellite

Hungry ghost · 07-12-2005, 07:38 AM

ok, I'm using FC4 with the default kernel too (2.6.11-1.1369_FC4). What I did is downloaded the slmodem-2.9.9e-pre1.tar.gz compiled it with no alsa support, downloaded the ungrab-winmodem module and install both the module and the driver. then I added this lines to /etc/rc.d/rc.local:

Code:

/sbin/modprobe -r slamr
/sbin/modprobe ungrab-winmodem
sleep 2
/sbin/modprobe slamr > /modprobeErrors
sleep 1
/usr/sbin/slmodemd /dev/slamr0 & > /slmodemErrors

in my case, for some reason the module slamr seems to be somehow loaded on boot (I'm not sure) so I have to unload it before loading ungrab-winmodem. Try compiling the driver without alsa ssupport to see what happens (I had no look with alsa, I didn't find the device or it was being used by the soundcard, I'm not sure, so try compiling the driver without alsa support, but in this case you will need the ungrab-winmodem module)

mrechte · 07-12-2005, 09:08 AM

Hi,

I am having many similar troubles setting-up the smartlink modem. I am trying to set it up on a FC4 2.6.12-1.1390_FC4 on a Nec Versa 500e (notebook).

1) having moved in the modem.c the offending declaration above the function call, it solves the problem but then brings many more messages during compilation starting with:
[mrechte@portable slmodem-2.9.9e-pre1]$ make
make -C modem all
make[1]: Entering directory `/home/mrechte/slmodem-2.9.9e-pre1/modem'
make[1]: Leaving directory `/home/mrechte/slmodem-2.9.9e-pre1/modem'
make -C drivers KERNEL_DIR=/usr/src/kernels/2.6.12-1.1390_FC4
make[1]: Entering directory `/home/mrechte/slmodem-2.9.9e-pre1/drivers'
cc -I/usr/src/kernels/2.6.12-1.1390_FC4/include -o kernel-ver kernel-ver.c
make all KERNEL_VER=2.4.20
make[2]: Entering directory `/home/mrechte/slmodem-2.9.9e-pre1/drivers'
cc -Wall -pipe -O3 -fomit-frame-pointer -D__KERNEL__ -DMODULE -DEXPORT_SYMTAB -DMODVERSIONS --include /usr/src/kernels/2.6.12-1.1390_FC4/include/linux/modversions.h -I/usr/src/kernels/2.6.12-1.1390_FC4/include -I. -I./../modem -o old_st7554.o -c old_st7554.c
cc1: error: /usr/src/kernels/2.6.12-1.1390_FC4/include/linux/modversions.h: Aucun fichier ou répertoire de ce type
In file included from /usr/include/linux/module.h:10,
from old_st7554.c:48:

I checked the /usr/src/kernels/2.6.12-1.1390_FC4/include/linux/ directory and there is no modversions.h.

Anyhow I entered to the drivers directory and issue a make. It generated a slamr.ko module.

When loading it (insmod slamr.ko) I get in dmesg:
slamr: module license 'Smart Link Ltd.' taints kernel.
slamr: SmartLink AMRMO modem.
slamr: device 8086:24c6 is grabbed by another driver

I followed the istructions on this therad on using ungrab-winmodem: I remove slamr.ko (rmod slamr) load ungrab-modem (modprobe ungrab-winmodem) and laod slamr (insmod slamr.ko): no change I still get the same message:

slamr: SmartLink AMRMO modem.
slamr: device 8086:24c6 is grabbed by another driver

Any suggestion ?

Regards

Marc.

Hungry ghost · 07-12-2005, 09:23 AM

mrechte, try the slmodem-2.9.9e-pre1.tar.gz it compiles fine under FC4, you'll also need the ungrab-winmodem module to prevent the 'slamr: device 8086:24c6 is grabbed by another driver' error. You can find them here. Compile and configure the driver as usual. Before loading slamr try '/sbin/modprobe -r slamr' then loaad ungrab-winmodem ('/sbin/modprobe ungrab-winmodem') then load slamr ('/sbin/modprobe slamr) or slusb if it's what you're using. Then run the slmodemd command. I hope it works.

mrechte · 07-12-2005, 09:31 AM

Thanks for your answer odiseo but if you check well my first message you will see that I am using the version you suggest and also the ungrab-winmodem...

Hungry ghost · 07-12-2005, 10:05 AM

hmm, It's weird, you should have no problems compiling this driver, it compiled fine on my FC4 with gcc 4.0. Sorry if I can't help there.

mrechte · 07-12-2005, 11:09 AM

Some more developments:

I checked the ungrab-winmodem.c source code to discover that if it succeeds it should print "device xxx is grabbed by driver yyyy: try to release" in dmesg. When checking my dmesg I was having nothing.

In fact my modem is shown as pci device 8086:24c6 (VENDOR is INTEL) and it is no listed in the header of that source code. So I added the lines:
/* 8086:24C6 */
{PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_24C6, PCI_ANY_ID, PCI_ANY_ID },
in the struct definition and:
#define PCI_VENDOR_ID_INTEL 0x8086
#define PCI_DEVICE_ID_24C6 0x24C6
in the define section, recompiled, reloaded and checked dmesg:
device 8086:24c6 is grabbed by driver Intel ICH Modem: try to release
codec_semaphore: semaphore is not ready [0x1][0x701300]
codec_write 1: semaphore is not ready for register 0x26
slamr: SmartLink AMRMO modem.
slamr: probe 8086:24c6 ICH4 card...
ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link [LNKB] -> GSI 5 (level, low) -> IRQ 5
PCI: Setting latency timer of device 0000:00:1f.6 to 64
slamr: mc97 codec is SIL22
slamr: slamr0 is ICH4 card.

So far so good...

I created a new connection using /dev/ttySL0 using system-config-network (I just add to manually edit the /etc/sysconfig/network-scripts/ifcfg-myISP because the ttySL0 was TTYSL0 !)

ifup myISP silently (can we get some sound ?) dialed to my ISP !!!!

Now it seems there areproblems with the sleep functions: this is what shows my /var/log/mesages:
Jul 12 17:57:44 portable pppd[11314]: pppd 2.4.2 started by root, uid 0
Jul 12 17:57:45 portable wvdial[11315]: WvDial: Internet dialer version 1.54.0
Jul 12 17:57:45 portable wvdial[11315]: Initializing modem.
Jul 12 17:57:45 portable wvdial[11315]: Sending: ATZ
Jul 12 17:57:45 portable wvdial[11315]: ATZ
Jul 12 17:57:45 portable wvdial[11315]: OK
Jul 12 17:57:45 portable wvdial[11315]: Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Jul 12 17:57:45 portable wvdial[11315]: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Jul 12 17:57:45 portable wvdial[11315]: OK
Jul 12 17:57:45 portable wvdial[11315]: Sending: ATM1L2
Jul 12 17:57:45 portable wvdial[11315]: ATM1L2
Jul 12 17:57:45 portable wvdial[11315]: OK
Jul 12 17:57:45 portable wvdial[11315]: Modem initialized.
Jul 12 17:58:43 portable wvdial[11315]: Sending: ATDT0860888080
Jul 12 17:58:43 portable wvdial[11315]: Waiting for carrier.
Jul 12 17:58:43 portable kernel: Debug: sleeping function called from invalid context at arch/i386/lib/usercopy.c:601
Jul 12 17:58:43 portable kernel: in_atomic():0, irqs_disabled():1
Jul 12 17:58:43 portable kernel: [<c021345c>] copy_to_user+0x18/0x60
Jul 12 17:58:43 portable kernel: [<ced062de>] amrmo_read+0x52/0x66 [slamr]
Jul 12 17:58:43 portable kernel: [<ced0628c>] amrmo_read+0x0/0x66 [slamr]
Jul 12 17:58:43 portable kernel: [<c017b678>] vfs_read+0x9c/0x10e
Jul 12 17:58:43 portable kernel: [<c017b927>] sys_read+0x41/0x6a
Jul 12 17:58:43 portable kernel: [<c0103a51>] syscall_call+0x7/0xb
Jul 12 17:58:44 portable wvdial[11315]: ATDT0860888080
Jul 12 17:58:44 portable kernel: Debug: sleeping function called from invalid context at arch/i386/lib/usercopy.c:601
...

Linmodems definetely have to be natively handled by Linux...

Thanks to all !

Marc

wneumann · 07-12-2005, 11:31 AM

After

/sbin/modprobe ungrab-winmodem

lsmod shows that ungrab-winmodem is loaded and slamr is not. Then I do

/sbin/modprobe slamr

and lsmod shows both ungrab-winmodem and slamr loaded. But dmesg shows

slamr: SmartLink AMRMO modem.
slamr: device 1039:7013 is grabbed by another driver

and

/usr/sbin/slmodemd /dev/slamr0 &

gives the error

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

So ungrab-winmodem is simply not working for me.

wneumann · 07-12-2005, 11:52 AM

Marc's reply was posted before I noticed.

I tried editing ungrab-winmodem.c as he suggests to add my device 1039:7013.

Now it works fine (on the first try "modprobe ungrab-winmodem" simply hung after writing to dmesg, but it worked after a complete restart -- Bill Gates is smiling).

mrechte · 07-12-2005, 12:29 PM

Hi again,

I just had a very useful discussion at discuss@linmodems.org, showing that was heading in the wrong direction...

My problem is not yet fully solved, but I think we are moving ahead !

*****************************
With 8086:24c6 ICHx AC97 modem you don't need 'ungrabber' (it even
doesn't help), and you don't need 'slamr' as well - use native alsa
driver 'snd-intel8x0m' (most likely it is loaded already) and 'slmodemd'
in ALSA mode.

Sasha.

Marc

At http://linmodems.technion.ac.il/packages/smartlink/
there is a slmodemd-2.9.9e-pre1-alsa.tar.gz
containing slmodemd compiled with alsa support.
Download and follow the directions. Then per Sasha's guidance
# su - root
# modprobe snd-intel8x0m
# slmodemd --alsa -c FRANCE hw:1 &
should create the ports. First test is
# wvdialconf /etc/wvdial.conf
edit wvdial.conf adding
Carrier Check = no
and try a dialout with
# wvdial &

MarvS
**********************************

wneumann · 07-12-2005, 12:52 PM

The "slmodemd --alsa" option should work with any winmodem handled by slmodemd (after first making slmodemd with Alsa support). It does for me -- only problem is that since upgrading to FC4 it won't load from an init file for me; only by hand after I have logged on (but no-one else reports this problem).

If the snd-intel8x0m module is not loaded automatically you can add it to your modprobe.conf. I have the lines

alias snd-card-1 snd-intel8x0m
options snd-intel8x0m index=1
options snd cards_limit=2

in my modprobe.conf for this.

NAC · 05-09-2006, 04:43 AM

HI guys
I have a question is, it seems must install kernel-headers before

Code:

make install

my kernel is 2.6.15-1.2054_FC5
i can find a folder names "build" but cannot open it and only 64KB.
so does that mean i need to install kernel-header first?

here is my problem.
http://img152.imageshack.us/my.php?i...10100157wz.gif

I have no idea how to make my modem works under Linux right now..

osvaldomarques · 05-09-2006, 06:46 AM

Hi NAC,

The problem you are showing is probably caused by the gcc 4.X. It doesn't like prototypes inside a function. Edit the file modem.c by moving the line 1701 to 1698.

This may resolve your problem.

Good luck!

NAC · 05-09-2006, 07:54 AM

hi osvaldomarques, thanks a lot 4 ur response.newbie always gets trouble and questions. ^^
and i am very new to Linux and i just followed by the "readme" file
so could you point out how can i edit it? how can i move the line 1701 to 1698

Thanks in adv.

osvaldomarques · 05-09-2006, 10:29 AM

Hi NAC,

Here it comes that talk of "using your preferred editor". There are several editors in the "*nix/*nux" world.

If you don't have one, I suggest you to use "vi". It's the most ancient editor; you may feel a bit lost with it until you get familiar with it. However, after you know it, you will ask yourself how could you live until today without knowing it.

There are several tutorials of it on the internet.

For this operation, basically you have to know that vi, different of other editors, has 2 modes of operation: command and edit. Every time you open a vi session you are in command mode; there are several ways to enter the edit mode, depending on your purpose, but you will return into command mode pressing "Esc" key.

After you go into the directory where is the file modem.c, type

Code:

vi +1701 modem.c

You will see a page with the line 1701 near the middle of it; the cursor will be on that line. Type

Code:

:set number

You will see the line numbers at the left of the line. Type

Code:

dd

The line will be deleted and copied into the vi buffer. Use the upper arrow key to go over the line 1698; type upper case

Code:

and the line will appear over the sequence 1698.

Now, if you are confident of the result, type

Code:

:wq

to save and exit; if not type

Code:

:q!

to exit without save.

It's important, as reference, you use vi with "caps lock" off. Every time you use a commands started with ":", the cursor will jump to the bottom line of the screen and it will wait for <enter> before proceed. Other commands will not appear as you type it and will execute as soon as you type it.

For instance, the line which must be moved is like this

Code:

static int sregs_init(unsigned char sregs[]);

Don't be afraid and good luck!

NAC · 05-09-2006, 06:02 PM

Hey osvaldomarques, thank you so much for your tut.
and the details are very clear.
I m goin to try it soon.

thanks again.