Please help for samsung S3310 Cell phone as Modem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

I have Samsung S3310 cell phone which I want to use for SMS
sending/receiving with SMSlib.
When I connect Phone to my System it is mounted as /dev/ttyACM0 but with minicom
it gives error can not write to /dev/ttyACM0. I tryed creating link to
/dev/ttyS4 still same problem.

I have run scanmodem utility as root and the output is as follows.
Unfortunately I can not
sqeezout useful information out of that. So I need help in this
regard. On windows same
phone is mounted as COM5 and I can query modem AT command and
responses OK there.

Thanks and Regards

Raja

==================================================================
 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.31-20-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=x86_64,  Ubuntu ,  ALSA_version=1.0.20
Linux version 2.6.31-20-generic (buildd@crested) (gcc version 4.4.1
(Ubuntu 4.4.1-4ubuntu8) ) #58-Ubuntu SMP Fri Mar 12 04:38:19 UTC 2010
 scanModem update of:  2010_03_18

Distrib_ID=Ubuntu
DistribCodeName=karmic
AptRepositoryStem=http://archive.ubuntu.com/ubuntu/


The dkms driver upgrade utilities are installed,


Some modem drivers can only be used in 32 bit modem on x86_64 systems,
while some others are competent on x86_64 Systems.  Cases are:
1) http://linmodems.technion.ac.il/bigarch/archive-seventh/msg03119.html
for the snd-hda-intel audio+modem driver. Also applicable to AC97
modem controllers.
In both cases, 32 bit libraries must be installed to support the
slmodemd helper having a precompiled 32 bit component.
2) For USB modems using the slusb.ko driver. 32 bit libraries must be
installed to support the slmodemd helper having a precompiled 32 bit
component
3) The hsfmodem and hcfpcimodem drivers for Conexant chipsest modes
are x86_64 competent.
4) agrsm packages for LSI/AgereSystems softmodems are not competent on
x86_64 systems.

 There are no blacklisted modem drivers in /etc/modprobe*  files

 Potentially useful modem drivers now loaded are:
     cdc_acm snd_hda_intel

Attached USB devices are:
 ID 045e:00cb Microsoft Corp.
 ID 04e8:6795 Samsung Electronics Co., Ltd
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:
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
Controller (rev 03)
High Definition Audio cards can host modem chips.

For candidate card in slot 00:1b.0, firmware information and bootup
diagnostics are:
 PCI slot       PCI ID          SubsystemID     Name
 ----------     ---------       ---------       --------------
 00:1b.0        8086:284b       1028:0275       Audio device: Intel
Corporation 82801H

 Modem interrupt assignment and sharing:
 22:        921          0   IO-APIC-fasteoi   ohci1394, mmc0, HDA Intel
 --- Bootup diagnostics for card in PCI slot 00:1b.0 ----
[    0.432207] pci 0000:00:1b.0: reg 10 64bit mmio: [0xf8300000-0xf8303fff]
[    0.432276] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[    0.432281] pci 0000:00:1b.0: PME# disabled
[   17.376157] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level,
low) -> IRQ 22
[   17.376217] HDA Intel 0000:00:1b.0: setting latency timer to 64
[   17.515922] input: HDA Digital PCBeep as
/devices/pci0000:00/0000:00:1b.0/input/input9

 The PCI slot 00:1b.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.



===== Advanced Linux Sound Architecture (ALSA) diagnostics =====
The ALSA packages provide audio support and also drivers for some modems.
ALSA diagnostics are written during bootup to /proc/asound/ folders.

The modem cards detected by "aplay -l"  are: None


The /proc/asound/pcm file reports:
-----------------------
00-00: ALC268 Analog : ALC268 Analog : playback 1 : capture 1

about /proc/asound/cards:
------------------------
 0 [Intel          ]: HDA-Intel - HDA Intel
                     HDA Intel at 0xf8300000 irq 22

 PCI slot 00:1b.0 has a High Definition Audio Card
 The drivers are in the kernel modules tree at:
 /lib/modules/2.6.31-17-generic/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.31-16-generic/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.31-15-generic/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.31-19-generic/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.31-14-generic/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.31-20-generic/kernel/sound/pci/hda/snd-hda-intel.ko

 The HDA diagnostics did not recognize a modem chip on the audio subsystem,
 though a Conexant chip modem might not be recognized.

=== Finished firmware and bootup diagnostics, next deducing cogent software. ===

A candidate modem is not transparent among the PCI devices:
------------------------------------------------
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio
Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E)
IDE Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM
(ICH8M/ICH8M-E) SATA AHCI Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
01:00.0 VGA compatible controller: nVidia Corporation G86 [GeForce
8600M GS] (rev a1)
06:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
08:05.0 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) (rev 02)
08:05.2 SD Host controller: O2 Micro, Inc. Integrated MMC/SD Controller (rev 02)
08:05.3 Mass storage controller: O2 Micro, Inc. Integrated MS/xD
Controller (rev 01)
------------------------------------------------
 with USB, bridge, and RAM devices not displayed.
If a High Definition Audio card is present, if might be hosted on the Subsystem.

If your modem is an
  external USB type,
  connected by an external serial cable,
  or mounted internally on an ISA card,
then scanModem would not access it.

Try with Root permission
 $ sudo wvdialconf  /etc/wvdial.conf
 to detect these modem types and some USB modems.
 If the detection is successful, read the DOCs/wvdial.txt .
 Edit the /etc/wvdial.conf with Root permission:
       sudo  gedit  /etc/wvdial.conf
 will be able to dial out with Root permission:
       sudo wvdial

 Many modems for which scanModem fails have Conexant chips.
 From http://www.linuxant.com/drivers/modemident.php
 get the ListModem tool, which will report on Conexant chipset modems

 If the above tests fail, please provide any independent information
available on your modem.
 If an alternative boot into Microsoft windows can be done, do mouse
clicks on:
  Start > Settings > Control Panel > Classical View (for Window XP) > System
> Hardware > Device Manager > Modems > Click on the + > Modem. Double click to
expand the graphic. Manufacturer information may be displayed. For example, CXT
stands for Conexant. Click the Diagnostics Tab. Record any hardware ID or vendor
and device information. From the Driver Details TAB, copy out the
VENdor and DEVice information.
Next do the Query Modem and record the ATI specifications displayed such as:
   ATI3 - Agere SoftModem Version 2.1.22
   ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27
Try to identify the modem setup file, with name perhaps MODEM.INF.
If may contain chipset Vendor informaton.


Predictive  diagnostics for card in bus 00:1b.0:
       Modem chipset not detected on
NAME="Audio device: Intel Corporation 82801H "
CLASS=0403
PCIDEV=8086:284b
SUBSYS=1028:0275
IRQ=22
HDA2=00:1b.0
SOFT=8086:284b.HDA

 For candidate modem in:  00:1b.0
  0403 Audio device: Intel Corporation 82801H
     Primary device ID:  8086:284b
   Subsystem PCI_id  1028:0275
   Softmodem codec or chipset from diagnostics:
                              from    Archives:



Support type needed or chipset:

Support can likely be achieved through two mutually exclusive alternatives:
1) The hsfmodem software for Conexant chipset modems: Read DOCs/Conexant.txt
The following ALSA alternative CANNOT work with Conexant modems.

2) An ALSA modem driver plus slmodemd.  Read DOCs/Smartlink.txt for details, and
to test get the package SLMODEMD_gcc4.4_alsa1.0.20.tar.gz from:
       http://linmodems.technion.ac.il/packages/smartlink/


 The base of the UDEV device file system is: /dev/.udev

 Versions adequately match for the compiler installed: 4.4.1
            and the compiler used in kernel assembly: 4.4.1



 Minimal compiling resources appear complete:
  make utility - /usr/bin/make
  Compiler version 4.4
  linuc_headers base folder /lib/modules/2.6.31-20-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 321600 2009-02-20 23:56 /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

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
vmnet1 vmnet8
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/alsa-base.conf:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2
/etc/modprobe.d/blacklist-modem.conf:# Uncomment these entries in
order to blacklist unwanted modem drivers
/etc/modprobe.d/blacklist-modem.conf:# blacklist snd-atiixp-modem
/etc/modprobe.d/blacklist-modem.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 --------

[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux