headers
Marvin Stodolsky | 1 Mar 2010 02:38
Picon

Re: from Lázaro

Lazaro,

In this case, the modem is not associated with the Texas instruments
card rather:
CPU=i686,  Ubuntu ,  ALSA_version=1.0.20
Linux version 2.6.31-14-generic (buildd <at> rothera) (gcc version 4.4.1
with audio:
 PCI slot	PCI ID		SubsystemID	Name
 ----------	---------	---------	--------------
 00:1b.0	8086:27d8	103c:30b1	Audio device: Intel Corporation 82801G

 Modem interrupt assignment and sharing:
 16:       3637          0   IO-APIC-fasteoi   i915, HDA Intel
 --- Bootup diagnostics for card in PCI slot 00:1b.0 ----
[    0.289161] pci 0000:00:1b.0: reg 10 64bit mmio: [0xf4780000-0xf4783fff]
[    0.289224] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[    0.289229] pci 0000:00:1b.0: PME# disabled
[   13.568067] HDA Intel 0000:00:1b.0: power state changed by ACPI to D0
[   13.568079] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level,
low) -> IRQ 16
[   13.568106] HDA Intel 0000:00:1b.0: setting latency timer to 64
[   13.661488] input: HDA Digital PCBeep as
/devices/pci0000:00/0000:00:1b.0/input/input8

is mostly the host for the
HDAchipVendorID=11c1
CHIP=0x11c13026
IDENT=slmodemd
SLMODEMD_DEVICE=hw:0,6
Driver=snd-hda-intel
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marvin Stodolsky | 1 Mar 2010 02:52
Picon

Re: wvdial and scanModem

Nikolay,

Good idea, I'll make the wvdial recommendation more prominent and per
Antonio's suggestion, will broaden the search path for it wvdial.

Incidentally, the wvdial package may currently to be without a formal
maintainer, which may be contributing to some of the failures we are
encountering.  If someone has the time/skills, wvdial/wvdialconf's
whole source code should be checked.
More on this later when I'm back under Linux

MarvS

On Sat, Feb 27, 2010 at 6:25 PM, Nikolay Zhuravlev <xxor <at> mail.ru> wrote:
> Marvin/All,
>
> It seem to happen pretty often that people need to be reminded
> here in the list about installing the wvdial package first.
> Maybe scanModem could be modified to instruct a user to
> install the wvdial and then rerun the scanModem.
> This important bit of info seems to get lost in ModemData.txt
>
> And then scanModem could recognize the Ubuntu system and
> provide some more specific info like this:
>
> <<<
> if [ -f /etc/issue ] && grep -q Ubuntu /etc/issue; then cat <<EOF
>
> For Ubuntu users, there are at the bottom of
> http://linmodems.technion.ac.il/packages/
(Continue reading)

Permalink | Reply | 0 comments |
headers
Arturo Neri | 1 Mar 2010 10:48
Picon

Re: Arturo, Italy, Kernel 2.6.31.12-174.2.22.fc12.i686

2010/2/28 Antonio Olivares <olivares14031 <at> gmail.com>:
> Arturo,
>
> Sadly as scanModem explains here, the slamr code does not work with
> 2.6.31.X kernels :(
>
> It says 2.8 (it is a typo, means 2.6.31
> For kernels 2.8.31 the slamr driver is not (yet) functional, failing
> within at the
>   Carrier Check
>  function.  Thus for service, retain a 2.6.30 or earlier kernel.
>
> For kernels 2.6.31 the slamr driver is not (yet) functional, failing
> within at the
>   Carrier Check
>  function.  Thus for service, retain a 2.6.30 or earlier kernel.
>
> Also, the part about ungrab-winmodem-20090716.tar.gz and
> slmodemd-2.9.11-20090222.tar.gz was not updated, that is why it says
> as of October 2007, the packages are:
>
> \begin{quote}
> For 2.6.31.12-174.2.22.fc12.i686 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
> \end{quote}
>
> If you want to give it a try and compile the newer sources for both
> slmodemd and slamr and see in case that it might work, go right ahead
(Continue reading)

Permalink | Reply | 1 comment |
headers
Arturo Neri | 1 Mar 2010 10:51
Picon

Arturo, Italy, Kernel 2.6.31.12-174.2.22.fc12.i686

Hi Antonio, this is what is happened, and really I understand not at all

[root <at> Fedora12 ungrab-winmodem-20090716]# make
make modules -C /lib/modules/2.6.31.12-174.2.22.fc12.i686/build
SUBDIRS=/home/Ciornj/Documents/ungrab-winmodem-20090716
make[1]: Entering directory `/usr/src/kernels/2.6.31.12-174.2.22.fc12.i686'
  CC [M]  /home/Ciornj/Documents/ungrab-winmodem-20090716/ungrab-winmodem.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /home/Ciornj/Documents/ungrab-winmodem-20090716/ungrab-winmodem.mod.o
  LD [M]  /home/Ciornj/Documents/ungrab-winmodem-20090716/ungrab-winmodem.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.31.12-174.2.22.fc12.i686'

[root <at> Fedora12 ungrab-winmodem-20090716]# make install
make modules -C /lib/modules/2.6.31.12-174.2.22.fc12.i686/build
SUBDIRS=/home/Ciornj/Documents/ungrab-winmodem-20090716
make[1]: Entering directory `/usr/src/kernels/2.6.31.12-174.2.22.fc12.i686'
  Building modules, stage 2.
  MODPOST 1 modules
make[1]: Leaving directory `/usr/src/kernels/2.6.31.12-174.2.22.fc12.i686'
install -D -m 644 ungrab-winmodem.ko
/lib/modules/2.6.31.12-174.2.22.fc12.i686/extra/ungrab-winmodem.ko
/sbin/depmod -a
[root <at> Fedora12 ungrab-winmodem-20090716]#

[root <at> Fedora12 slmodem-2.9.11-20090222]# make clean
make -C modem clean &&  make -C drivers clean &&  echo "done."
make[1]: Entering directory
`/home/Ciornj/Documents/slmodem-2.9.11-20090222/modem'
rm -f slmodemd modem_test modem_main.o modem_cmdline.o modem_test.o
(Continue reading)

Permalink | Reply | 0 comments |
headers
Arturo Neri | 1 Mar 2010 11:11
Picon

Re: Arturo, Italy, Kernel 2.6.31.12-174.2.22.fc12.i686

I send un other time to discuss because in my copy first send are
uncomplete. Sorry.

Hi Antonio, this is what is happened, and really I understand not at all

[root <at> Fedora12 ungrab-winmodem-20090716]# make
make modules -C /lib/modules/2.6.31.12-174.2.22.fc12.i686/build
SUBDIRS=/home/Ciornj/Documents/ungrab-winmodem-20090716
make[1]: Entering directory `/usr/src/kernels/2.6.31.12-174.2.22.fc12.i686'
  CC [M]  /home/Ciornj/Documents/ungrab-winmodem-20090716/ungrab-winmodem.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /home/Ciornj/Documents/ungrab-winmodem-20090716/ungrab-winmodem.mod.o
  LD [M]  /home/Ciornj/Documents/ungrab-winmodem-20090716/ungrab-winmodem.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.31.12-174.2.22.fc12.i686'

[root <at> Fedora12 ungrab-winmodem-20090716]# make install
make modules -C /lib/modules/2.6.31.12-174.2.22.fc12.i686/build
SUBDIRS=/home/Ciornj/Documents/ungrab-winmodem-20090716
make[1]: Entering directory `/usr/src/kernels/2.6.31.12-174.2.22.fc12.i686'
  Building modules, stage 2.
  MODPOST 1 modules
make[1]: Leaving directory `/usr/src/kernels/2.6.31.12-174.2.22.fc12.i686'
install -D -m 644 ungrab-winmodem.ko
/lib/modules/2.6.31.12-174.2.22.fc12.i686/extra/ungrab-winmodem.ko
/sbin/depmod -a
[root <at> Fedora12 ungrab-winmodem-20090716]#

[root <at> Fedora12 slmodem-2.9.11-20090222]# make clean
make -C modem clean &&  make -C drivers clean &&  echo "done."
(Continue reading)

Permalink | Reply | 12 comments |
headers
Antonio Olivares | 1 Mar 2010 14:09
Picon

Re: Arturo, Italy, Kernel 2.6.31.12-174.2.22.fc12.i686

Arturo,

Installation of ungrab-winmodem appears to be installed correctly, it
is the slmodem-2.9.11-20090222/ code that is not

Here:

[root <at> Fedora12 slmodem-2.9.11-20090222]# make clean
after you run
make clean

run

make KERNEL_VER=/lib/modules/2.6.31.12-174.2.22.fc12.i686/build/
make
make install

then test it with
# modprobe ungrab-winmodem
# modprobe slamr
then
# slmodemd -c ITALY /dev/slamr0

if you get the error again, try to login with (su -) and not (su) by itself.

There have been little to no success reports, maybe you can report
back with a success report?

Regards,
(Continue reading)

Permalink | Reply | 11 comments |
headers
Arturo Neri | 1 Mar 2010 15:09
Picon

Re: Arturo, Italy, Kernel 2.6.31.12-174.2.22.fc12.i686

Hi Antonio, GOAL!!!!!!!!!!!!!!
Excuse me if I continue with un other question.
Now that the modules are installable can you explain me how can I
automatically install these two modules and run slmodemd. Like I wrote
in previous msg, into /Modem/DOCS/Scripts/ there are slmodemd scripts
but I don't know if one is useful and where put it
Thanks Arturo

[root <at> Fedora12 slmodem-2.9.11-20090222]# make clean
make -C modem clean &&  make -C drivers clean &&  echo "done."
make[1]: Entering directory
`/home/Ciornj/Documents/slmodem-2.9.11-20090222/modem'
rm -f slmodemd modem_test modem_main.o modem_cmdline.o modem_test.o
modem.o modem_datafile.o modem_at.o modem_timer.o modem_pack.o
modem_ec.o modem_comp.o modem_param.o modem_debug.o homolog_data.o
dp_sinus.o dp_dummy.o sysdep_common.o
rm -f *~ *.orig *.rej
make[1]: Leaving directory
`/home/Ciornj/Documents/slmodem-2.9.11-20090222/modem'
make[1]: Entering directory
`/home/Ciornj/Documents/slmodem-2.9.11-20090222/drivers'
rm -f kernel-ver slamr.o  slamr.ko *st7554.o amrmo_init.o sysdep_amr.o
*.mod.* .*.cmd *~ slusb.*
rm -f -r .tmp_versions
make[1]: Leaving directory
`/home/Ciornj/Documents/slmodem-2.9.11-20090222/drivers'
done.
[root <at> Fedora12 slmodem-2.9.11-20090222]# make
KERNEL_VER=/lib/modules/2.6.31.12-174.2.22.fc12.i686/build/
make -C modem all
(Continue reading)

Permalink | Reply | 10 comments |
headers
Antonio Olivares | 1 Mar 2010 15:29
Picon

Re: Arturo, Italy, Kernel 2.6.31.12-174.2.22.fc12.i686

Arturo,

In the folder scripts, as root user (su -)
# cp slmodemd /etc/rc.d/init.d/

# chkconfig slmodemd --add
 # chkconfig slmodemd on

# cd /etc/rc.d/

 type exactly as this appears.  When you get to 6 press Enter you
 should see a ">" continue with the numbers and type everything there
 pressing enter everytime till you get to done and press Enter you
 should see what is in the above example or something similar.

 # for i in 0 1 2 3 4 5 6
 > do
 > ls rc$i.d/*slmodemd*
 > done

Here's slmodemd script

#!/bin/sh
#
# slmodemd:    Starts the SmartLink Modem Daemon
#
# chkconfig: 345 90 10
# description: This is the user space part of the SmartLink Modem driver
# processname: slmodemd
# config: /etc/sysconfig/slmodem
(Continue reading)

Permalink | Reply | 9 comments |
headers
Arturo Neri | 1 Mar 2010 15:59
Picon

Re: Arturo, Italy, Kernel 2.6.31.12-174.2.22.fc12.i686

Antonio at a time I don't understand. Please look:

[root <at> Fedora12 scripts]# cp slmodemd /etc/rc.d/init.d/
[root <at> Fedora12 scripts]# chkconfig slmodemd --add
[root <at> Fedora12 scripts]# chkconfig slmodemd on
[root <at> Fedora12 scripts]# cd /etc/rc.d/
[root <at> Fedora12 rc.d]# for i in 0 1 2 3 4 5 6
> 7
-bash: syntax error near unexpected token `7'
[root <at> Fedora12 rc.d]# for i in 0 1 2 3 4 5 6
> 1
-bash: syntax error near unexpected token `1'
[root <at> Fedora12 rc.d]# for i in 0
> 1
-bash: syntax error near unexpected token `1'
[root <at> Fedora12 rc.d]# for i in 0 1 2 3 4 5 6
> do
> ^C
[root <at> Fedora12 rc.d]#
Arturo

2010/3/1 Antonio Olivares <olivares14031 <at> gmail.com>:
> Arturo,
>
> In the folder scripts, as root user (su -)
> # cp slmodemd /etc/rc.d/init.d/
>
> # chkconfig slmodemd --add
>  # chkconfig slmodemd on
>
(Continue reading)

Permalink | Reply | 8 comments |
headers
Antonio Olivares | 1 Mar 2010 17:52
Picon

Re: Arturo, Italy, Kernel 2.6.31.12-174.2.22.fc12.i686

Arturo,

This part

# for i in 0 1 2 3 4 5 6
  > do
  > ls rc$i.d/*slmodemd*
  > done

Is to check if the symbolic links exist or not
As root user (su -) type the commands exactly as they appear.  Then
you should see if they got created or not.

As an example in my case (when slmodemd worked):

root <at> localhost rc.d]# for i in 0 1 2 3 4 5 6
 > do
 > ls rc$i.d/*slmodemd*
 > done
 rc0.d/K10slmodemd
 rc1.d/K10slmodemd
 rc2.d/S90slmodemd
 rc3.d/S90slmodemd
 rc4.d/S90slmodemd
 rc5.d/S90slmodemd
 rc6.d/K10slmodemd
 [root <at> localhost rc.d]#

 [root <at> localhost rc.d]# chkconfig slmodemd --list
 slmodemd        0:off   1:off   2:on    3:on    4:on
(Continue reading)

Permalink | Reply | 7 comments |

Gmane