Tiago Saboga, Brazil kernel 2.6.26-1-686

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

 



Hi!

I am trying to install a Motorola SM56 Data Fax Modem
[1057:3052]. Following guidelines in [1] and [2] I
have patched the slmodem sources I got from Debian (package
sl-modem-source, in lenny), recompiled the module, but I keep getting
the following error in dmesg:

$ dmesg | grep -C5 slamr
[   12.870681] ACPI: PCI Interrupt 0000:00:0d.0[A] -> Link [AIGP] ->
GSI 22 (level, low) -> IRQ 22
[   12.870794] PCI: Setting latency timer of device 0000:00:0d.0 to 64
[   12.871080] NVRM: loading NVIDIA UNIX x86 Kernel Module  173.14.09
Wed Jun  4 23:43:17 PDT 2008
[   12.909816] device 1057:3052 is grabbed by driver serial: try to
release
[   12.909816] ACPI: PCI interrupt for device 0000:01:06.0 disabled
[   12.931812] slamr: SmartLink AMRMO modem.
[   12.931898] slamr: probe 1057:3052 SL1900 card...
[   12.931960] ACPI: PCI Interrupt 0000:01:06.0[A] -> Link [APC2] ->
GSI 17 (level, low) -> IRQ 17
[   12.932097] PCI: Setting latency timer of device 0000:01:06.0 to 64
[   12.932130] slamr: cannot init card.
[   12.932189] ACPI: PCI interrupt for device 0000:01:06.0 disabled
[   13.024814] device-mapper: uevent: version 1.0.3
[   13.026291] device-mapper: ioctl: 4.13.0-ioctl (2007-10-18)
initialised: dm-devel@xxxxxxxxxx
[   13.912948] kjournald starting.  Commit interval 5 seconds
[   13.912948] EXT3 FS on sda5, internal journal

What should I do now? How do I track the problem?

Attached is my ModemData.txt.

Thanks,

Tiago Saboga.
 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.26-1-686 
 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.26-1-686 (Debian 2.6.26-13lenny2) (dannf@xxxxxxxxxx) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Fri Mar 13 18:08:45 UTC 2009
 scanModem update of:  2009_02_21
The modem symbolic link is /dev/modem -> ttySL0
 There are no blacklisted modem drivers in /etc/modprobe*  files 
 Potentially useful modem drivers now loaded are:
       slamr  snd_hda_intel       

slamrTest=
If a USB modem or cellphone is attached and was not detected, please
provide available information in your request to discuss@xxxxxxxxxxxxx

For candidate card in slot 01:06.0, firmware information and bootup diagnostics are:
 PCI slot	PCI ID		SubsystemID	Name
 ----------	---------	---------	--------------
 01:06.0	1057:3052	1057:3020	Modem: Motorola SM56 Data Fax Modem 

 Modem interrupt assignment and sharing: 
 --- Bootup diagnostics for card in PCI slot 01:06.0 ----
[    1.374709] ACPI: PCI Interrupt 0000:01:06.0[A] -> Link [APC2] -> GSI 17 (level, low) -> IRQ 17
[    1.374994] 0000:01:06.0: ttyS1 at I/O 0xcc08 (irq = 17) is a 16450
[    1.375150] 0000:01:06.0: ttyS2 at I/O 0xcc10 (irq = 17) is a 8250
[    1.375305] 0000:01:06.0: ttyS3 at I/O 0xcc18 (irq = 17) is a 16450
[    1.375397] Couldn't register serial port 0000:01:06.0: -28
[   12.909816] ACPI: PCI interrupt for device 0000:01:06.0 disabled
[   12.931960] ACPI: PCI Interrupt 0000:01:06.0[A] -> Link [APC2] -> GSI 17 (level, low) -> IRQ 17
[   12.932097] PCI: Setting latency timer of device 0000:01:06.0 to 64
[   12.932189] ACPI: PCI interrupt for device 0000:01:06.0 disabled

 The PCI slot 01:06.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	1019:a88d	Audio device: nVidia Corporation MCP61 High Definition Audio 

 Modem interrupt assignment and sharing: 
 23:        353   IO-APIC-fasteoi   ohci_hcd:usb1, HDA Intel
 --- Bootup diagnostics for card in PCI slot 00:05.0 ----
[    1.017803] pci 0000:00:05.0: Enabling HT MSI Mapping
[   10.799880] ACPI: PCI Interrupt 0000:00:05.0[B] -> Link [AAZA] -> GSI 23 (level, low) -> IRQ 23
[   10.800027] PCI: Setting latency timer of device 0000:00:05.0 to 64


The primary PCI & Subsystem pair  is novel and 
the Subsystem ID is not alone decisive for modem codec identification.


===== 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 ALSA verion is 1.0.16
The modem cards detected by "aplay -l"  are: None


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

about /proc/asound/cards:
------------------------
 0 [NVidia         ]: HDA-Intel - HDA NVidia
                      HDA NVidia at 0xfe028000 irq 23

 PCI slot 00:05.0 has a High Definition Audio Card
 The drivers are in the kernel modules tree at:
 /lib/modules/2.6.18-4-486/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.20-1-k7/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.20pedra-01/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.26-1-486/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.26-1-686/kernel/sound/pci/hda/snd-hda-intel.ko
UNEXPECTED HDA diagnostic outcome.
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===

Predictive  diagnostics for card in bus 01:06.0:
	Modem chipset  detected on
NAME="Modem: Motorola SM56 Data Fax Modem "
CLASS=0703
PCIDEV=1057:3052
SUBSYS=1057:3020
IRQ=17
SOFT=1057:3052.MC97
NEW=1057:3020
IDENT=mc97

 For candidate modem in:  01:06.0
   0703 Modem: Motorola SM56 Data Fax Modem 
      Primary device ID:  1057:3052
    Subsystem PCI_id  1057:3020 
    Softmodem codec or chipset from diagnostics: 
                               from    Archives: 
                        
      


The soft modem is in the ac97/mc97 category. However the diagnostics were not effective,
and an archival record for is lacking for the modem codec of pair:
	1057:3052 1057:3020
Try to acquire more information by running the modem diagnostics under a Microsoft boot,
as described in SoftModem.txt

----------------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



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=1019:a88d
IRQ=23
HDA=10de:03f0
SOFT=10de:03f0.HDA


 High Definition Audio (HDA) cards MAY host a modem chip in their Subsystem, 
 and many are supported by the ALSA audio+modem driver snd-hda-intel
 A modem was not detected on HDA card 10de:03f0.
 If another modem card is present, then most likely 10de:03f0 does not host a modem.
 If another modem card has not been detected, then possibilities are:
	1) A Conexant modem chip is present on 10de:03f0, as Conexant chips
 are frequently not detectable by ALSA diagnostics
	2) The modem may be of the older non-PCI Controller Chipset (hardware) type.
Try detection with Root permission:
	 wvdialconf  /etc/wvdial.conf

 For candidate modem in:  00:05.0
   0403 Audio device: nVidia Corporation MCP61 High Definition Audio 
      Primary device ID:  10de:03f0
    Subsystem PCI_id  1019:a88d 
    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.1.tar.gz from:
	http://linmodems.technion.ac.il/packages/smartlink/

----------------end Softmodem section --------------
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.1.3
             and the compiler used in kernel assembly: 4.1.3


 
 Minimal compiling resources appear complete:
   make utility - /usr/bin/make
   Compiler version 4.1
   linuc_headers base folder /lib/modules/2.6.26-1-686/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.


Compressed files at: /usr/src/linux-source-2.6.20.tar.bz2 /usr/src/nvidia-kernel.tar.bz2 /usr/src/sl-modem.tar.bz2

For Debian and some related distributions, a package kernel-kbuild-2.6-26 may be needed to support driver compiling.


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 269156 Nov 28 15:48 /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
auth
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: eth2
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:   lrwxrwxrwx 1 root root 6 Mar 27 09:52 /dev/modem -> ttySL0
slmodemd created symbolic link /dev/ttySL0:  
     Within /etc/udev/ files:
/etc/udev/rules.d/80-drivers.rules:SUBSYSTEM=="atm",				RUN+="dsl-modem.agent"
     Within /etc/modprobe.conf files:
/etc/modprobe.d/sl-modem-daemon.modutils:install slamr modprobe --ignore-install ungrab-winmodem ;  modprobe --ignore-install slamr; test -e /dev/slamr0 || (/bin/mknod -m 660 /dev/slamr0 c 242 0 2>/dev/null && chgrp dialout /dev/slamr0) 
/etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2
/etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2
/etc/modprobe.d/alsa-base-blacklist:# Uncomment these entries in order to blacklist unwanted modem drivers
/etc/modprobe.d/alsa-base-blacklist:# blacklist snd-atiixp-modem
/etc/modprobe.d/alsa-base-blacklist:# blacklist snd-via82xx-modem
     Within any ancient /etc/devfs files:

     Within ancient kernel 2.4.n /etc/module.conf files:

--------- end modem support lines --------

 For Debian users, the linux-headers-2.6.26-1-686.deb can be used instead of kernel-source/


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

  Powered by Linux