Fwd: Ayuda configurar Modem pci

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

 



---------- Forwarded message ----------
From: pedro fernadez <honterhad@xxxxxxxxx>
Date: Sat, 2 Aug 2008 15:47:58 -0400
Subject: Ayuda configurar Modem pci
To: gzsuniq@xxxxxxxxxxxxx, jmanuecb@xxxxxxxxx

Este es le resultado del scanModem

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.24-19-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.24-19-generic (buildd@palmer) (gcc version 4.2.3
(Ubuntu 4.2.3-2ubuntu7)) #1 SMP Wed Jun 18 14:43:41 UTC 2008
 scanModem update of:  2008_07_31
The modem symbolic link is /dev/modem -> ttySL0
 There are no blacklisted modem drivers in /etc/modprobe*  files
Attached USB devices are:
 ID 090c:1000 Feiya Technology Corp. Memory Bar
 ID 03f0:7604 Hewlett-Packard Deskjet 3940

USB modems not recognized

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

 Modem interrupt assignment and sharing:
 16:          0   IO-APIC-fasteoi   sata_sis
 --- Bootup diagnostics for card in PCI slot 00:07.0 ----
[   22.907772] ACPI: PCI Interrupt 0000:00:07.0[A] -> GSI 17 (level,
low) -> IRQ 16
[   22.908153] 0000:00:07.0: ttyS2 at I/O 0xd808 (irq = 16) is a 16450
[   22.908381] 0000:00:07.0: ttyS3 at I/O 0xd810 (irq = 16) is a 8250
[   22.908452] Couldn't register serial port 0000:00:07.0: -28

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

Predictive diagnostics for card in bus 00:07.0:
	Modem chipset  detected on
NAME="Modem: Motorola SM56 Data Fax Modem "
CLASS=0703
PCIDEV=1057:3052
SUBSYS=1057:3020
IRQ=16
IDENT=slamr

 For candidate modem in:  00:07.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.24-19-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.2.3
             and the compiler used in kernel assembly: 4.2.3



 Minimal compiling resources appear complete:
   make utility - /usr/bin/make
   Compiler version 4.2
   linuc_headers base folder /lib/modules/2.6.24-19-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 n. 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 269256 2007-10-04 15:57 /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.
==========================================================

# start/stop the daemon when the USB modem is connected
KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
 Checking for modem support lines:
 --------------------------------------
     /device/modem symbolic link:   lrwxrwxrwx 1 root root 6
2008-08-02 15:17 /dev/modem -> ttySL0
slmodemd created symbolic link /dev/ttySL0:
     Within /etc/udev/ files:
/etc/udev/rules.d/030_sl-modem-daemon.rules:# start/stop the daemon
when the USB modem is connected
/etc/udev/rules.d/030_sl-modem-daemon.rules:KERNEL=="slusb[0-9]*",
GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
/etc/udev/sl-modem-daemon.rules:# start/stop the daemon when the USB
modem is connected
/etc/udev/sl-modem-daemon.rules:KERNEL=="slusb[0-9]*",
GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
     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
/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)
     Within any ancient /etc/devfs files:

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

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




Y Esta es Cuando Ejecuto este Comando:

Editing `/etc/wvdial.conf'.

Scanning your serial ports for a modem.

ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS2<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS2<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS2<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS3<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS3<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS3<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
 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.24-19-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.24-19-generic (buildd@palmer) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Wed Jun 18 14:43:41 UTC 2008
 scanModem update of:  2008_07_31
The modem symbolic link is /dev/modem -> ttySL0
 There are no blacklisted modem drivers in /etc/modprobe*  files 
Attached USB devices are:
 ID 090c:1000 Feiya Technology Corp. Memory Bar
 ID 03f0:7604 Hewlett-Packard Deskjet 3940

USB modems not recognized

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

 Modem interrupt assignment and sharing: 
 16:          0   IO-APIC-fasteoi   sata_sis
 --- Bootup diagnostics for card in PCI slot 00:07.0 ----
[   22.907772] ACPI: PCI Interrupt 0000:00:07.0[A] -> GSI 17 (level, low) -> IRQ 16
[   22.908153] 0000:00:07.0: ttyS2 at I/O 0xd808 (irq = 16) is a 16450
[   22.908381] 0000:00:07.0: ttyS3 at I/O 0xd810 (irq = 16) is a 8250
[   22.908452] Couldn't register serial port 0000:00:07.0: -28

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

Predictive diagnostics for card in bus 00:07.0:
	Modem chipset  detected on
NAME="Modem: Motorola SM56 Data Fax Modem "
CLASS=0703
PCIDEV=1057:3052
SUBSYS=1057:3020
IRQ=16
IDENT=slamr

 For candidate modem in:  00:07.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.24-19-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.2.3
             and the compiler used in kernel assembly: 4.2.3


 
 Minimal compiling resources appear complete:
   make utility - /usr/bin/make
   Compiler version 4.2
   linuc_headers base folder /lib/modules/2.6.24-19-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 n. 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 269256 2007-10-04 15:57 /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.
==========================================================

# start/stop the daemon when the USB modem is connected
KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
 Checking for modem support lines:
 --------------------------------------
     /device/modem symbolic link:   lrwxrwxrwx 1 root root 6 2008-08-02 15:17 /dev/modem -> ttySL0
slmodemd created symbolic link /dev/ttySL0:  
     Within /etc/udev/ files:
/etc/udev/rules.d/030_sl-modem-daemon.rules:# start/stop the daemon when the USB modem is connected
/etc/udev/rules.d/030_sl-modem-daemon.rules:KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
/etc/udev/sl-modem-daemon.rules:# start/stop the daemon when the USB modem is connected
/etc/udev/sl-modem-daemon.rules:KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon"
     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
/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) 
     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