Dear Marv & Ahmed & et. all,
I left one of my machines which had the smartlink modem at work(cdrom
died and my friend was going to install another one), but I had
another one at home and I confirm that the patch indeed works :)
Great Job by Jair. We were in a difficult situation and you came
through for many smartlink modem users :)
I used slax remix v04 since it has 2.6.32 kernel whereas old SLax
6.1.2 has 2.6.27.27 kernel :)
root@slax:~# uname -r
2.6.32-zen6
root@slax:~/slmodem-2.9.11-20100303# make clean
make -C modem clean && make -C drivers clean && echo "done."
make[1]: Entering directory `/root/slmodem-2.9.11-20100303/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 `/root/slmodem-2.9.11-20100303/modem'
make[1]: Entering directory `/root/slmodem-2.9.11-20100303/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 `/root/slmodem-2.9.11-20100303/drivers'
done.
root@slax:~/slmodem-2.9.11-20100303# make
KERNEL_DIR=/lib/modules/`uname -r`/build
make -C modem all
make[1]: Entering directory `/root/slmodem-2.9.11-20100303/modem'
rebuild profile...
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_main.o -c modem_main.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_cmdline.o -c modem_cmdline.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem.o -c modem.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_datafile.o -c
modem_datafile.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_at.o -c modem_at.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_timer.o -c modem_timer.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_pack.o -c modem_pack.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_ec.o -c modem_ec.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_comp.o -c modem_comp.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_param.o -c modem_param.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_debug.o -c modem_debug.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o homolog_data.o -c homolog_data.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o dp_sinus.o -c dp_sinus.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o dp_dummy.o -c dp_dummy.c
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o sysdep_common.o -c sysdep_common.c
gcc -o slmodemd modem_main.o modem_cmdline.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
dsplibs.o sysdep_common.o
gcc -Wall -g -O -I. -DCONFIG_DEBUG_MODEM -o modem_test.o -c modem_test.c
gcc -o modem_test modem_test.o modem_cmdline.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 dsplibs.o sysdep_common.o
make[1]: Leaving directory `/root/slmodem-2.9.11-20100303/modem'
make -C drivers KERNEL_DIR=/lib/modules/2.6.32-zen6/build
make[1]: Entering directory `/root/slmodem-2.9.11-20100303/drivers'
doing kernel-ver::
cc -I/lib/modules/2.6.32-zen6/build/include -o kernel-ver kernel-ver.c
make all KERNEL_VER=2.6.32-zen6
make[2]: Entering directory `/root/slmodem-2.9.11-20100303/drivers'
obj-m=slamr.o
slamr-objs=amrmo_init.o sysdep_amr.o amrlibs.o
make modules -C /lib/modules/2.6.32-zen6/build
SUBDIRS=/root/slmodem-2.9.11-20100303/drivers
make[3]: Entering directory `/usr/src/linux-2.6.32'
WARNING: Symbol version dump /usr/src/linux-2.6.32/Module.symvers
is missing; modules will have no dependencies and modversions.
CC [M] /root/slmodem-2.9.11-20100303/drivers/amrmo_init.o
CC [M] /root/slmodem-2.9.11-20100303/drivers/sysdep_amr.o
LD [M] /root/slmodem-2.9.11-20100303/drivers/slamr.o
Building modules, stage 2.
MODPOST 1 modules
CC /root/slmodem-2.9.11-20100303/drivers/slamr.mod.o
LD [M] /root/slmodem-2.9.11-20100303/drivers/slamr.ko
make[3]: Leaving directory `/usr/src/linux-2.6.32'
finished all:
make[2]: Leaving directory `/root/slmodem-2.9.11-20100303/drivers'
make[1]: Leaving directory `/root/slmodem-2.9.11-20100303/drivers'
root@slax:~/slmodem-2.9.11-20100303# make
make -C modem all
make[1]: Entering directory `/root/slmodem-2.9.11-20100303/modem'
make[1]: Leaving directory `/root/slmodem-2.9.11-20100303/modem'
make -C drivers KERNEL_DIR=/lib/modules/2.6.32-zen6/build
make[1]: Entering directory `/root/slmodem-2.9.11-20100303/drivers'
doing kernel-ver::
cc -I/lib/modules/2.6.32-zen6/build/include -o kernel-ver kernel-ver.c
make all KERNEL_VER=2.6.32-zen6
make[2]: Entering directory `/root/slmodem-2.9.11-20100303/drivers'
obj-m=slamr.o
slamr-objs=amrmo_init.o sysdep_amr.o amrlibs.o
make modules -C /lib/modules/2.6.32-zen6/build
SUBDIRS=/root/slmodem-2.9.11-20100303/drivers
make[3]: Entering directory `/usr/src/linux-2.6.32'
WARNING: Symbol version dump /usr/src/linux-2.6.32/Module.symvers
is missing; modules will have no dependencies and modversions.
Building modules, stage 2.
MODPOST 1 modules
make[3]: Leaving directory `/usr/src/linux-2.6.32'
finished all:
make[2]: Leaving directory `/root/slmodem-2.9.11-20100303/drivers'
make[1]: Leaving directory `/root/slmodem-2.9.11-20100303/drivers'
root@slax:~/slmodem-2.9.11-20100303# make install
make -C modem all
make[1]: Entering directory `/root/slmodem-2.9.11-20100303/modem'
make[1]: Leaving directory `/root/slmodem-2.9.11-20100303/modem'
make -C drivers KERNEL_DIR=/lib/modules/2.6.32-zen6/build
make[1]: Entering directory `/root/slmodem-2.9.11-20100303/drivers'
doing kernel-ver::
cc -I/lib/modules/2.6.32-zen6/build/include -o kernel-ver kernel-ver.c
make all KERNEL_VER=2.6.32-zen6
make[2]: Entering directory `/root/slmodem-2.9.11-20100303/drivers'
obj-m=slamr.o
slamr-objs=amrmo_init.o sysdep_amr.o amrlibs.o
make modules -C /lib/modules/2.6.32-zen6/build
SUBDIRS=/root/slmodem-2.9.11-20100303/drivers
make[3]: Entering directory `/usr/src/linux-2.6.32'
WARNING: Symbol version dump /usr/src/linux-2.6.32/Module.symvers
is missing; modules will have no dependencies and modversions.
Building modules, stage 2.
MODPOST 1 modules
make[3]: Leaving directory `/usr/src/linux-2.6.32'
finished all:
make[2]: Leaving directory `/root/slmodem-2.9.11-20100303/drivers'
make[1]: Leaving directory `/root/slmodem-2.9.11-20100303/drivers'
make install -C drivers KERNEL_DIR=/lib/modules/2.6.32-zen6/build
make[1]: Entering directory `/root/slmodem-2.9.11-20100303/drivers'
doing kernel-ver::
cc -I/lib/modules/2.6.32-zen6/build/include -o kernel-ver kernel-ver.c
mkdir -p /dev
mknod -m 600 /dev/slamr0 c 242 0 ; mknod -m 600 /dev/slamr1 c 242 1
; mknod -m 600 /dev/slamr2 c 242 2 ; mknod -m 600 /dev/slamr3 c
242 3 ; echo -n
make install KERNEL_VER=2.6.32-zen6
make[2]: Entering directory `/root/slmodem-2.9.11-20100303/drivers'
install -D -m 644 slamr.ko /lib/modules/2.6.32-zen6/extra/slamr.ko
/sbin/depmod -a
make[2]: Leaving directory `/root/slmodem-2.9.11-20100303/drivers'
make[1]: Leaving directory `/root/slmodem-2.9.11-20100303/drivers'
install -D -m 755 modem/slmodemd /usr/sbin/slmodemd
rm -f -rf /var/lib/slmodem
install -d -D -m 755 /var/lib/slmodem
root@slax:~/slmodem-2.9.11-20100303# cd ..
root@slax:~# modprobe ungrab-winmodem
root@slax:~# modprobe slamr
root@slax:~# slmodemd -c USA /dev/slamr0
SmartLink Soft Modem: version 2.9.11 Mar 7 2010 13:06:49
symbolic link `/dev/ttySL0' -> `/dev/pts/2' created.
modem `slamr0' created. TTY is `/dev/pts/2'
Use `/dev/ttySL0' as modem device, Ctrl+C for termination.
The following part of scanModem can be edited to match the new results:
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 01:07.0:
Modem chipset detected on
NAME="Modem: Smart Link Ltd. SmartLink SmartPCI562 56K Modem "
CLASS=0703
PCIDEV=163c:3052
SUBSYS=163c:3052
IRQ=17
HDA2=00:05.0
IDENT=slamr
For candidate modem in: 01:07.0
0703 Modem: Smart Link Ltd. SmartLink SmartPCI562 56K Modem
Primary device ID: 163c:3052
Support type needed or chipset: slamr
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 kernels 2.8.31 the slamr driver is not (yet) functional, failing
within at the
Carrier Check
function. Thus for service, retain a 2.8.30 or earlier kernel. For
Ubuntu users this
can be done by downloading the kernel from
http://packages.ubuntu.com/jaunty/linux-image-2.6.28-16-generic
and from http://linmodems.technion.ac.il/packages/smartlink/Ubuntu/
the slamr-2.6.28-16-generic.tar.gz
For 2.6.32-zen6 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 =====================
Change it TO something like
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 01:07.0:
Modem chipset detected on
NAME="Modem: Smart Link Ltd. SmartLink SmartPCI562 56K Modem "
CLASS=0703
PCIDEV=163c:3052
SUBSYS=163c:3052
IRQ=17
HDA2=00:05.0
IDENT=slamr
For candidate modem in: 01:07.0
0703 Modem: Smart Link Ltd. SmartLink SmartPCI562 56K Modem
Primary device ID: 163c:3052
Support type needed or chipset: slamr
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 kernels 2.6.31 or greater, special thanks go out to Yair for
sending us patches, Marv for packing the changes, and Ahmed for making
the changes for Ubuntu users. Now we can have working smartlink
modems under newer kernels :)
For 2.6.32-zen6 compiling drivers is necessary. As of March 2010 the
current packages at
http://linmodems.technion.ac.il/packages/smartlink/ are the
ungrab-winmodem-20090716.tar.gz and slmodem-2.9.11-200100303.tar.gz
Writing DOCs/Smartlink.txt
============ end Smartlink section =====================
Regards,
Antonio
scanModem follows:
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
===============================================================================
Welcome to Slax 6.1.2
===============================================================================
The system is up and running now.
Login as "root" with password "toor", both without quotes, lowercase.
If you're new to Slax, visit http://www.slax.org/ for more info.
After you login, try the following commands:
mc ....... to start Midnight Commander (edit/copy/move/create/delete files)
startx ... to run Xwindow system with KDE in VESA mode 1024x768 at 75Hz
xconf .... to autoconfigure your graphics card for better performance
Other commands you may find useful (for experts only!):
activate ..... to insert (install) Slax module into the system on the fly
deactivate ... to remove (uninstall) Slax module from the root filesystem
mkfileswap ... to create a special file on your harddisk for virtual RAM
When finished, use "poweroff" or "reboot" command and wait until it completes
===============================================================================
kernel 2.6.32-zen6
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,
===============================================================================
===============================================================================
==============================================================================
, ALSA_version=1.0.21
Linux version 2.6.32-zen6 (root@slax) (gcc version 4.4.3 (GCC) ) #1
ZEN SMP PREEMPT Tue Feb 2 17:27:26 UTC 2010
scanModem update of: 2010_02_25
The slmodemd set symbolic link is /dev/ttySL0 -> /dev/pts/2
/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
Modem drivers blocked from loading during bootup are listed in
/etc/modprobe* file lines:
/etc/modprobe.d/blacklist.conf:blacklist snd-atiixp-modem
/etc/modprobe.d/blacklist.conf:blacklist snd-via82xx-modem
/etc/modprobe.d/blacklist.conf:blacklist snd-intel8x0m
Potentially useful modem drivers now loaded are:
snd_hda_intel slamr
slamrTest=
Attached USB devices are:
ID 058f:6387 Alcor Micro Corp. Transcend JetFlash Flash Drive
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:
01:07.0 Modem: Smart Link Ltd. SmartLink SmartPCI562 56K Modem (rev 04)
00:05.0 Audio device: nVidia Corporation MCP61 High Definition Audio (rev a2)
High Definition Audio cards can host modem chips.
For candidate card in slot 01:07.0, firmware information and bootup
diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
01:07.0 163c:3052 163c:3052 Modem: Smart Link Ltd.
SmartLink SmartPCI562 56K Modem
Modem interrupt assignment and sharing:
17: 50 92752 IO-APIC-fasteoi SL1900
--- Bootup diagnostics for card in PCI slot 01:07.0 ----
pci 0000:01:07.0: reg 10 32bit mmio: [0xfb000000-0xfb000fff]
pci 0000:01:07.0: reg 14 io port: [0xb000-0xb0ff]
pci 0000:01:07.0: PME# supported from D0 D3hot D3cold
pci 0000:01:07.0: PME# disabled
serial 0000:01:07.0: PCI INT A -> Link[APC2] -> GSI 17 (level, low) -> IRQ 17
0000:01:07.0: ttyS1 at I/O 0xb008 (irq = 17) is a 16450
0000:01:07.0: ttyS2 at I/O 0xb010 (irq = 17) is a 8250
0000:01:07.0: ttyS3 at I/O 0xb018 (irq = 17) is a 16450
Couldn't register serial port 0000:01:07.0: -28
serial 0000:01:07.0: PCI INT A disabled
slamr 0000:01:07.0: PCI INT A -> Link[APC2] -> GSI 17 (level, low) -> IRQ 17
The PCI slot 01:07.0 of the modem card may be disabled early in
a bootup process, but then enabled later. If modem drivers load
but the modem is not responsive, read DOCs/Bootup.txt about possible fixes.
Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx
if help is needed.
For candidate card in slot 00:05.0, firmware information and bootup
diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:05.0 10de:03f0 1458:a002 Audio device: nVidia
Corporation MCP61 High Definition Audio
Modem interrupt assignment and sharing:
23: 0 1478 IO-APIC-fasteoi sata_nv, HDA Intel
--- Bootup diagnostics for card in PCI slot 00:05.0 ----
pci 0000:00:05.0: reg 10 32bit mmio: [0xfb100000-0xfb103fff]
pci 0000:00:05.0: PME# supported from D3hot D3cold
pci 0000:00:05.0: PME# disabled
HDA Intel 0000:00:05.0: PCI INT B -> Link[AAZA] -> GSI 23 (level, low) -> IRQ 23
HDA Intel 0000:00:05.0: setting latency timer to 64
The PCI slot 00:05.0 of the modem card may be disabled early in
a bootup process, but then enabled later. If modem drivers load
but the modem is not responsive, read DOCs/Bootup.txt about possible fixes.
Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx
if help is needed.
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 01:07.0:
Modem chipset detected on
NAME="Modem: Smart Link Ltd. SmartLink SmartPCI562 56K Modem "
CLASS=0703
PCIDEV=163c:3052
SUBSYS=163c:3052
IRQ=17
HDA2=00:05.0
IDENT=slamr
For candidate modem in: 01:07.0
0703 Modem: Smart Link Ltd. SmartLink SmartPCI562 56K Modem
Primary device ID: 163c:3052
Support type needed or chipset: slamr
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 kernels 2.8.31 the slamr driver is not (yet) functional, failing
within at the
Carrier Check
function. Thus for service, retain a 2.8.30 or earlier kernel. For
Ubuntu users this
can be done by downloading the kernel from
http://packages.ubuntu.com/jaunty/linux-image-2.6.28-16-generic
and from http://linmodems.technion.ac.il/packages/smartlink/Ubuntu/
the slamr-2.6.28-16-generic.tar.gz
For 2.6.32-zen6 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 =====================
Predictive diagnostics for card in bus 00:05.0:
Modem chipset not detected on
NAME="Audio device: nVidia Corporation MCP61 High Definition Audio "
CLASS=0403
PCIDEV=10de:03f0
SUBSYS=1458:a002
IRQ=23
For candidate modem in: 00:05.0
0403 Audio device: nVidia Corporation MCP61 High Definition Audio
Primary device ID: 10de:03f0
Support type needed or chipset:
Completed candidate modem analyses.
The base of the UDEV device file system is: /dev/.udev
Versions adequately match for the compiler installed: 4.4.3
and the compiler used in kernel assembly: 4.4.3
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.4
linuc_headers base folder /lib/modules/2.6.32-zen6/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.
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:
-rwxr-xr-x 1 root root 366440 Feb 5 06:32 /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
crtscts
lock
modem
proxyarp
lcp-echo-interval 30
lcp-echo-failure 4
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.
Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 ppp0
Which can interfere with Browser naviagation.
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: lrwxrwxrwx 1 root root 10
Mar 7 13:07 /dev/ttySL0 -> /dev/pts/2
Within /etc/udev/ files:
Within /etc/modprobe.conf files:
/etc/modprobe.d/blacklist.conf:# ALSA modules to support sound modems.
These should be loaded manually
/etc/modprobe.d/blacklist.conf:blacklist snd-atiixp-modem
/etc/modprobe.d/blacklist.conf:blacklist snd-via82xx-modem
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
On 3/7/10, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote:
> Antonio,
>
> Please let us know when you have tested the slmodem-2.9.11-20100303 update.
> Report to the List too.
>
> MarvS
>
> 2010/3/6 أحمد المحمودي <aelmahmoudy@xxxxxxxxxx>:
>> On Sat, Mar 06, 2010 at 09:14:27PM -0500, Marvin Stodolsky wrote:
>>> Yair's modem_diff_1.txt patch is applied in the slmodem.tar.gz files,
>>> which will bring the slmodem source upto 2.9.11-20100303 level.
>>>
>>> Would you please inform me when your revised packages are available in
>>> the Ubuntu repository? , Now that DKMS support is in the standard
>>> install, my preference is certainly to recommend Ubuntu users to your
>>> packages, rather than those (previously assembled for) Linmodems at
>>> Technion.
>>
>> Was the patch tested by someone other than Yair ? I remember that
>> Antonio tried sl-modem several times with 2.6.31, but with no sucess.
>> Did he try again with Yair's patch ? I just need a second confirmation
>> that it really solves the "NO CARRIER" issue.
>>
>>> Second issue. Even though the modem/ code components are not called
>>> for driver compilation in your sl-modem-source package, it would be
>>> useful if the modem/ code components were included therein, for the
>>> benefit of Cuban users.
>>>
>>> The reason is that international Internet access is severely
>>> constrained in Cuba, and there may be similar situations for other
>>> countries I am not aware of. But there is allowed access to some
>>> Ubuntu repositories. So a complete modem/ folder follow would provide
>>> a vehicle for Cuban (other) Users to get the complete slmodem code
>>> package. Current Lazaro and a couple of other Cubans haveing more
>>> priviledged international access, are serving as relay people for new
>>> Cuban users. We should try to diminish that load upon them.
>>
>> If they have access to Ubuntu repositories, then they can download the
>> sl-modem *source* package in order to get the modem/ code components:
>>
>> apt-get source sl-modem
>>
>> Of course they must enable the "Source code" repositories, than can be
>> easily done from System menu->Administration->Software Sources
>>
>> --
>> أحمد المحمودي (Ahmed El-Mahmoudy)
>> Digital design engineer
>> GPG KeyID: 0xEDDDA1B7
>> GPG Fingerprint: 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7
>>
>
