Marvin,
Thanks again for your help. I feel guilty depending upon your help so
I'm keeping on trying to solve the problem by myself (while I wait).
I discovered an interesting section in ModemData.txt:
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!!
Thus, I tried my hand at Smartlink, but it is smarter than I am..... I
went and got ungrab-winmodem and tried to compile it, but it coming
back with errors. I could be off in the wrong direction, which is why
I'm so grateful for your help.
I'll attach the ModemData.Txt
On Tue, Dec 16, 2008 at 4:10 PM, Marvin Stodolsky
<marvin.stodolsky@xxxxxxxxx> wrote:
> Ilan,
>
> The 1057:3052 chipset is supported, but drivers must match the kernel
> version of the host computer. Please send us the entire
> ModemData.txt output done on the host computer.
>
> MarvS
>
> On Tue, Dec 16, 2008 at 3:39 AM, Ilan Tal <ilan.tal@xxxxxxxxx> wrote:
>> Hello to Jacques and Marvin,
>> I've got the real computer which needs the modem, and I tried to do things
>> by myself, but I need help. On this system it correctly identifies the modem
>> as:
>>
>> Predictive diagnostics for card in bus 00:09.0:
>> Modem chipset detected on
>> NAME="Modem: Motorola SM56 Data Fax Modem "
>> CLASS=0703
>> PCIDEV=1057:3052
>> SUBSYS=1057:3020
>> IRQ=18
>> IDENT=slamr
>>
>> For candidate modem in: 00:09.0
>> 0703 Modem: Motorola SM56 Data Fax Modem
>> Primary device ID: 1057:3052
>> Support type needed or chipset: slamr
>>
>> I looked in /dev but there is no directory /dev/modem
>> so clearly something needs to be correctly defined.
>>
>> I tried to use smartlink instructions:
>>
>> Smartlink modem setup.
>> -----------------------------------------------------------
>> The modem should setup with:
>> sudo modprobe ungrab-winmodem
>> sudo modprobe slamr
>> sudo slmodemd -c YOUR_COUNTRY /dev/slamr0
>> which should announce creation of ports:
>> /dev/ttySL0 --> /dev/pts/N , N some number
>> Specify the symbolic link /dev/ttySL0 as the port to be used by dailer
>> software.
>>
>> but I got the following error:
>>
>> miri@ubuntu:~/Desktop$ sudo modprobe ungrab-winmodem
>> FATAL: Module ungrab_winmodem not found.
>>
>> In short, I'm still missing some basic instructions and I would be very
>> grateful to know what I'm doing wrong.
>>
>> Thanks,
>> Ilan
>> On Mon, Dec 15, 2008 at 11:21 AM, Jacques Goldberg
>> <Jacques.Goldberg@xxxxxxx> wrote:
>>>
>>> שלום אילן !
>>>
>>> In view of what you wrote, since you just want to make the modem work for
>>> the fun/sport, you may consider using an older Ubuntu Live CD. Just follow
>>> the instructions which I sent you.
>>> With an 8 GB disk on key you can use the Live CD keeping files when you
>>> power off.
>>>
>>> Jacques
>>> יעקב גולדברג, הטכניון, חיפה
>>>
>>> Ilan Tal wrote:
>>>>
>>>> Marvin and Jacques,
>>>> First of all, thanks for the detailed answers.
>>>> It is a great feeling that there are humans behind all these computers.
>>>> I am trying to learn as much as I can from your instructions.
>>>>
>>>> If I understand correctly, this works only on the old kernel.
>>>> My guy feeling is to stay with the latest kernel and not drop back.
>>>> Perhaps I don't understand enough to know how it all fits together.
>>>>
>>>> In any case, I don't really need the modem on my laptop.
>>>> It is just an exercise to help a friend with his computer (a totally
>>>> different computer
>>>> with an actual physical PCI modem card).
>>>> I tell my friends that when they get fed up with Windows and all its
>>>> nonsense,
>>>> I'll help them to install a real operating system where they can enjoy
>>>> the computer.
>>>> In this particular case they want Open Office to have Hebrew menus.
>>>> This is no problem for Ubuntu, but it doesn't work for XP (English
>>>> version).
>>>> I couldn't make Linux modem dial, but I said there is no way where
>>>> Ubuntu would fall down on such an issue. I didn't know what the answer
>>>> was
>>>> but there were good people who would help me.
>>>>
>>>> To start the process I decided to see if I could get my laptop to dial
>>>> and then
>>>> progress on to his machine. If I have to drop back to an old kernel on my
>>>> laptop
>>>> (this may not be a serious problem, but I don't have enough experience to
>>>> know),
>>>> then I will stop the exercise on my laptop and continue with his
>>>> computer.
>>>>
>>>> Thanks again, and please let me know if my gut feelings are wrong.
>>>>
>>>> Ilan
>>>>
>>>>
>>>> On Sun, Dec 14, 2008 at 9:26 PM, Marvin Stodolsky
>>>> <marvin.stodolsky@xxxxxxxxx> wrote:
>>>>>
>>>>> Jacques and Antonio,
>>>>>
>>>>> Please copy the additional information below to any further cases of
>>>>> the 11c11040 under Ubuntu Intrepid, with 2.6.27 series kernels.
>>>>> Returning home to my Linux box tomorrow,
>>>>> I'll soon do a scanModem update which will output this temporary
>>>>> guidance automatically. Bjorn is traveling for a couple of weeks and
>>>>> will thus not be responding much to the 11c11040 chipset sector
>>>>>
>>
>>
>
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 kernel 2.6.27-9-generic
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,
Linux version 2.6.27-9-generic (buildd@rothera) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11) ) #1 SMP Thu Nov 20 21:57:00 UTC 2008
scanModem update of: 2008_11_06
There are no blacklisted modem drivers in /etc/modprobe* files
Attached USB devices are:
ID 1d6b:0001 Linux Foundation 1.1 root hub
ID 1d6b:0001 Linux Foundation 1.1 root hub
ID 1d6b:0001 Linux Foundation 1.1 root hub
ID 1d6b:0001 Linux Foundation 1.1 root hub
ID 1d6b:0002 Linux Foundation 2.0 root hub
USB modems not recognized
For candidate card in slot 00:09.0, firmware information and bootup diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:09.0 1057:3052 1057:3020 Modem: Motorola SM56 Data Fax Modem
Modem interrupt assignment and sharing:
--- Bootup diagnostics for card in PCI slot 00:09.0 ----
[ 0.501899] PCI: 0000:00:09.0 reg 10 32bit mmio: [fdfff000, fdffffff]
[ 0.501909] PCI: 0000:00:09.0 reg 14 io port: [fc00, fcff]
[ 0.501958] pci 0000:00:09.0: PME# supported from D0 D3hot D3cold
[ 0.501964] pci 0000:00:09.0: PME# disabled
[ 9.942048] serial 0000:00:09.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 9.943458] 0000:00:09.0: ttyS2 at I/O 0xfc08 (irq = 18) is a 16450
[ 9.944394] 0000:00:09.0: ttyS3 at I/O 0xfc10 (irq = 18) is a 8250
[ 9.944748] Couldn't register serial port 0000:00:09.0: -28
The PCI slot 00:09.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 00:09.0:
Modem chipset detected on
NAME="Modem: Motorola SM56 Data Fax Modem "
CLASS=0703
PCIDEV=1057:3052
SUBSYS=1057:3020
IRQ=18
IDENT=slamr
For candidate modem in: 00:09.0
0703 Modem: Motorola SM56 Data Fax Modem
Primary device ID: 1057:3052
Support type needed or chipset: slamr
----------------end Softmodem section --------------
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 DOCs/Smartlink.txt
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 2.6.27-9-generic 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 =====================
Completed candidate modem analyses.
The base of the UDEV device file system is: /dev/.udev
Versions adequately match for the compiler installed: 4.3.2
and the compiler used in kernel assembly: 4.3.2
Minimal compiling resources appear complete:
make utility - /usr/bin/make
Compiler version 4.3
linuc_headers base folder /lib/modules/2.6.27-9-generic/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:
-rwsr-xr-- 1 root dip 277160 2008-11-20 22:58 /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)
sudo chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
sudo chmod a+x /usr/sbin/pppd
Checking settings of: /etc/ppp/options
asyncmap 0
noauth
crtscts
lock
hide-password
modem
proxyarp
lcp-echo-interval 30
lcp-echo-failure 4
noipx
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
Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0
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:
Within /etc/udev/ files:
Within /etc/modprobe.conf files:
/etc/modprobe.d/blacklist-modem:# Uncomment these entries in order to blacklist unwanted modem drivers
/etc/modprobe.d/blacklist-modem:# blacklist snd-atiixp-modem
/etc/modprobe.d/blacklist-modem:# blacklist snd-via82xx-modem
/etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
