AMIGOS: YA PASE EL SCANMODEM SIN PROBLEMAS Y ESTE ES EL RESUMEN DEL MISMO, AHORA PUEDEN DECIRME SI ALGUIEN TIENE ALGUN DRIVERS PARA MI MODEM O DONDE PUEDO BAJARLO.
Only plain text email is forwarded by the [email protected] List Server, as HTML can contain viruses. Use as the email Subject Line: YourName, YourCountry kernel 2.6.27-7-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 [email protected] 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-7-generic (bui...@rothera) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu10) ) #1 SMP Fri Oct 24 06:42:44 UTC 2008 scanModem update of: 2009_04_28 There are no blacklisted modem drivers in /etc/modprobe* files Potentially useful modem drivers now loaded are: snd_hda_intel Attached USB devices are: ID 6253:0100 TwinHan Technology Co., Ltd Ir reciver f. remote control ID 0424:2504 Standard Microsystems Corp. USB 2.0 Hub ID 13ba:0017 ID 0572:1234 Conexant Systems (Rockwell), Inc. Typhoon Redfun Modem V90 56k If a cellphone is not detected, see http://ubuntuforums.org/archive/index.php/t-878554.html If a USB modem or cellphone is attached and was not detected, please provide available information in your request to [email protected] For candidate card in slot 00:03.0, firmware information and bootup diagnostics are: PCI slot PCI ID SubsystemID Name ---------- --------- --------- -------------- 00:03.0 8086:29c4 8086:5044 Communication controller: Intel Corporation 82G33/G31/P35/P31 Express MEI Controller Modem interrupt assignment and sharing: 16: 4 4 IO-APIC-fasteoi heci --- Bootup diagnostics for card in PCI slot 00:03.0 ---- [ 0.469271] PCI: 0000:00:03.0 reg 10 64bit mmio: [e4525900, e452590f] [ 0.469271] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold [ 0.469271] pci 0000:00:03.0: PME# disabled [ 0.469532] PCI: 0000:03:00.0 reg 10 io port: [2018, 201f] [ 0.472034] PCI: 0000:03:00.0 reg 14 io port: [2024, 2027] [ 0.472041] PCI: 0000:03:00.0 reg 18 io port: [2010, 2017] [ 0.472048] PCI: 0000:03:00.0 reg 1c io port: [2020, 2023] [ 0.472055] PCI: 0000:03:00.0 reg 20 io port: [2000, 200f] [ 0.472063] PCI: 0000:03:00.0 reg 24 32bit mmio: [e4300000, e43001ff] [ 0.472091] pci 0000:03:00.0: supports D1 [ 0.472093] pci 0000:03:00.0: PME# supported from D0 D1 D3hot [ 0.472097] pci 0000:03:00.0: PME# disabled [ 4.738409] pata_acpi 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 4.738425] pata_acpi 0000:03:00.0: setting latency timer to 64 [ 4.738434] pata_acpi 0000:03:00.0: PCI INT A disabled [ 5.618589] pata_marvell 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 5.618611] pata_marvell 0000:03:00.0: setting latency timer to 64 [ 11.801664] heci 0000:00:03.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 11.801668] heci 0000:00:03.0: setting latency timer to 64 The PCI slot 00:03.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 [email protected] if help is needed. For candidate card in slot 00:1b.0, firmware information and bootup diagnostics are: PCI slot PCI ID SubsystemID Name ---------- --------- --------- -------------- 00:1b.0 8086:293e 8086:3001 Audio device: Intel Corporation 82801I Modem interrupt assignment and sharing: 22: 1301 1330 IO-APIC-fasteoi HDA Intel --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- [ 0.469271] PCI: 0000:00:1b.0 reg 10 64bit mmio: [e4520000, e4523fff] [ 0.469271] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold [ 0.469271] pci 0000:00:1b.0: PME# disabled [ 13.090614] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 [ 13.090636] HDA Intel 0000:00:1b.0: setting latency timer to 64 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 [email protected] 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 ALSA verion is 1.0.17 The modem cards detected by "aplay -l" are: None The /proc/asound/pcm file reports: ----------------------- 00-00: X-Fi 20k1 : WaveOut/WaveIn : playback 8 : capture 1 01-01: STAC92xx Digital : STAC92xx Digital : playback 1 01-00: STAC92xx Analog : STAC92xx Analog : playback 1 : capture 3 about /proc/asound/cards: ------------------------ 0 [XFi ]: CTALSA - Creative X-Fi Creative ALSA Driver X-Fi 1 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xe4520000 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.27-7-generic/kernel/sound/pci/hda/snd-hda-intel.ko UNEXPECTED HDA diagnostic outcome. === Finished firmware and bootup diagnostics, next deducing cogent software. === A candidate modem is not evident among the PCI devices: ------------------------------------------------ 00:03.0 Communication controller: Intel Corporation 82G33/G31/P35/P31 Express MEI Controller (rev 02) 00:19.0 Ethernet controller: Intel Corporation 82566DC-2 Gigabit Network Connection (rev 02) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02) 00:1f.2 IDE interface: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 4 port SATA IDE Controller (rev 02) 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02) 00:1f.5 IDE interface: Intel Corporation 82801I (ICH9 Family) 2 port SATA IDE Controller (rev 02) 01:00.0 VGA compatible controller: ATI Technologies Inc RV515 [Radeon X1300] 01:00.1 Display controller: ATI Technologies Inc RV515 [Radeon X1300] (Secondary) 03:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6101 single-port PATA133 interface (rev b2) 07:00.0 Multimedia audio controller: Creative Labs SB X-Fi 07:03.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) ------------------------------------------------ with USB and bridge devices not displayed. If your modem is connected by an external serial cable, or mounted internally on an ISA card, 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:03.0: Modem chipset not detected on NAME="Communication controller: Intel Corporation 82G33/G31/P35/P31 Express MEI Controller " CLASS=0780 PCIDEV=8086:29c4 SUBSYS=8086:5044 IRQ=16 For candidate modem in: 00:03.0 0780 Communication controller: Intel Corporation 82G33/G31/P35/P31 Express MEI Controller Primary device ID: 8086:29c4 Support type needed or chipset: scanModem could not identify the Support Type needed from diagnosics or archives. 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. 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. Writing DOCs/Intel.txt Predictive diagnostics for card in bus 00:1b.0: Modem chipset not detected on NAME="Audio device: Intel Corporation 82801I " CLASS=0403 PCIDEV=8086:293e SUBSYS=8086:3001 IRQ=22 HDA=8086:293e SOFT=8086:293e.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 8086:293e. If another modem card is present, then most likely 8086:293e does not host a modem. If another modem card has not been detected, then possibilities are: 1) A Conexant modem chip is present on 8086:293e, 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: sudo wvdialconf /etc/wvdial.conf For candidate modem in: 00:1b.0 0403 Audio device: Intel Corporation 82801I Primary device ID: 8086:293e Subsystem PCI_id 8086:3001 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.3.tar.gz from: http://linmodems.technion.ac.il/packages/smartlink/ Writing DOCs/Smartlink.txt ============ end Smartlink section ===================== 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 The patch utility is needed and is needed for compiling ALSA drivers, and possibly others. Minimal compiling resources appear complete: make utility - /usr/bin/make Compiler version 4.3 linuc_headers base folder /lib/modules/2.6.27-7-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 273064 2008-10-16 03:51 /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/alsa-base:options snd-atiixp-modem index=-2 /etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2 /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 Within any ancient /etc/devfs files: Within ancient kernel 2.4.n /etc/module.conf files: --------- end modem support lines -------- _______________________________________________ Cancelar suscripción https://listas.softwarelibre.cu/mailman/listinfo/linux-l Buscar en el archivo http://listas.softwarelibre.cu/buscar/linux-l
