Will fix the scanModem output for Intel536/537 case soon. When there are two potential PCIs, the logic in scanModem does not always separate the cases automagically. In a couple of months, should have time for the rewrite required, but am too busy now. MarvS scanModem maintainer On Thu, Dec 23, 2010 at 3:31 PM, Antonio Olivares <olivares14031@xxxxxxxxx> wrote: > Jacques & Aran, > > You seem to be correct that scanModem does not output like it did > before, perhaps there are too many pci dev ices? or modems connected? > It does not show Phillipe Vouters page/drivers recommended? > > One page that could help out? > https://help.ubuntu.com/community/DialupModemHowto/Intel536EP > > Or go and get latest driver from > http://vouters.dyndns.org/Intel/intel-536EP-537EP_2010_07_19.tar.bz2 > extract it > $ tar -zxvf intel-536EP-537EP_2019_07_19.tar.bz2 > $ cd intel* > $ sudo make clean > $ sudo Âmake 536 > $ sudo make install > > then run > $ sudo wvdialconf /etc/wvdial.conf > > Aran please report back to see if t this helped or not? > > Regards, > > Antonio > > > On Thu, Dec 23, 2010 at 2:01 PM, Jacques Goldberg > <Jacques.Goldberg@xxxxxxx> wrote: >> Dear friends, >> >> I have received the request below and translated it into English, calling >> for your help. >> I have not yet digested this new scanModem output format, and I do not find >> in it a clear cut answer to the following questions: >> -is there an Intel 536EP chipset in the computer? >> -if true indeed, which would match the announced Dynamode M56PCI H-I Modem >> because the I in H-I is Dynamode's way to flag Intel chipset (alternate is R >> for Rockwell-Conexant), why doesn't scanModem direct the user to Philippe's >> driver? Kernel 2.6.35 too recent under Ubuntu? >> -is there a second or alternate ATI chipset based modem? >> -if true indeed, depending on the chip model this may need slmodem or a >> Linuxant driver, but again I found scanModem mute on the subject. The list >> Âof drivers preloaded by Ubuntu is not of great help. >> >> Thanks, in Aran's name too, not only mine. >> >> -------- Original Message -------- >> Subject:   Modem >> Date:   Thu, 23 Dec 2010 12:54:34 +0200 >> From:   Aran Patinkin <apatinkin@xxxxxxxxx> >> To: >> ÂI believe that I have a Dynamode M56PCI H-I Modem >> ÂscanModem output follows. >> Thanks for help >> Aran >> >> Â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.35-24-generic-pae >> Â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, ÂUbuntu , ÂALSA_version=1.0.23 >> Linux version 2.6.35-24-generic-pae (buildd@vernadsky) (gcc version 4.4.5 >> (Ubuntu/Linaro 4.4.4-14ubuntu5) ) #42-Ubuntu SMP Thu Dec 2 03:21:31 UTC 2010 >> ÂscanModem update of: Â2010_12_12 >> >> Distrib_ID=Ubuntu >> DistribCodeName=maverick >> AptRepositoryStem=http://il.archive.ubuntu.com/ubuntu/ >> >> >> The dkms driver upgrade utilities are installed, >> >> ÂThere are no blacklisted modem drivers in /etc/modprobe* Âfiles >> >> ÂPotentially useful modem drivers now loaded are: >> Âsnd_atiixp_modem snd_via82xx_modem snd_intel8x0m  snd_hda_intel  slamr >> >> Attached USB devices are: >> ÂID 1970:0000 Dane-Elec Corp. USA >> ÂID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer >> ÂID 058f:9254 Alcor Micro Corp. Hub >> ÂID 15d9:0a33 Trust International B.V. Optical Mouse >> ÂID 552d:4348 >> ÂID 046d:0990 Logitech, Inc. QuickCam Pro 9000 >> 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:03.0 Communication controller: Intel Corporation 4 Series Chipset HECI >> Controller (rev 02) >> 04:02.0 Communication controller: Intel Corporation 536EP Data Fax Modem >> 00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio >> Controller >> 01:00.1 Audio device: ATI Technologies Inc HD48x0 audio >> High Definition Audio cards can host modem chips. >> >> For candidate card in slot 00:03.0, firmware information and bootup >> diagnostics are: >> ÂPCI slot PCI ID SubsystemID Name >> Â---------- --------- --------- -------------- >> Â00:03.0 8086:2e24 8086:0024 Communication controller: Intel Corporation 4 >> Series Chipset HECI Controller >> >> ÂModem interrupt assignment and sharing: >> Â--- Bootup diagnostics for card in PCI slot 00:03.0 ---- >> [  Â0.367894] pci 0000:00:03.0: reg 10: [mem 0xd0125900-0xd012590f 64bit] >> [  Â0.367951] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold >> [  Â0.367955] pci 0000:00:03.0: PME# disabled >> [  Â0.369321] pci 0000:03:00.0: reg 10: [io Â0xd040-0xd047] >> [  Â0.369330] pci 0000:03:00.0: reg 14: [io Â0xd030-0xd033] >> [  Â0.369338] pci 0000:03:00.0: reg 18: [io Â0xd020-0xd027] >> [  Â0.369346] pci 0000:03:00.0: reg 1c: [io Â0xd010-0xd013] >> [  Â0.369354] pci 0000:03:00.0: reg 20: [io Â0xd000-0xd00f] >> [  Â0.369412] pci 0000:03:00.0: disabling ASPM on pre-1.1 PCIe device. ÂYou >> can enable it with 'pcie_aspm=force' >> [  Â3.650521] pata_acpi 0000:03:00.0: PCI INT A -> GSI 19 (level, low) -> >> IRQ 19 >> [  Â3.650545] pata_acpi 0000:03:00.0: setting latency timer to 64 >> [  Â3.650556] pata_acpi 0000:03:00.0: PCI INT A disabled >> [  Â4.566448] pata_jmicron 0000:03:00.0: PCI INT A -> GSI 19 (level, low) >> -> IRQ 19 >> [  Â4.566477] pata_jmicron 0000:03:00.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 discuss@xxxxxxxxxxxxx >> Âif help is needed. >> >> >> For candidate card in slot 04:02.0, firmware information and bootup >> diagnostics are: >> ÂPCI slot PCI ID SubsystemID Name >> Â---------- --------- --------- -------------- >> Â04:02.0 8086:1040 8086:1000 Communication controller: Intel Corporation >> 536EP Data Fax Modem >> >> ÂModem interrupt assignment and sharing: >> Â45:     14     Â9     18     19  PCI-MSI-edge >> Âhda_intel >> Â--- Bootup diagnostics for card in PCI slot 04:02.0 ---- >> [  Â0.369474] pci 0000:04:02.0: reg 10: [mem 0xd0400000-0xd07fffff] >> [  Â0.369517] pci 0000:04:02.0: supports D2 >> [  Â0.369518] pci 0000:04:02.0: PME# supported from D2 D3hot D3cold >> [  Â0.369522] pci 0000:04:02.0: PME# disabled >> >> ÂThe PCI slot 04:02.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:1b.0, firmware information and bootup >> diagnostics are: >> ÂPCI slot PCI ID SubsystemID Name >> Â---------- --------- --------- -------------- >> Â00:1b.0 8086:3a3e 8086:0024 Audio device: Intel Corporation 82801JI >> >> ÂModem interrupt assignment and sharing: >> Â44:    Â952    Â959    Â133    Â131  PCI-MSI-edge >> Âhda_intel >> Â--- Bootup diagnostics for card in PCI slot 00:1b.0 ---- >> [  Â0.368340] pci 0000:00:1b.0: reg 10: [mem 0xd0120000-0xd0123fff 64bit] >> [  Â0.368376] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold >> [  Â0.368379] pci 0000:00:1b.0: PME# disabled >> [  21.719336] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> >> IRQ 22 >> [  21.719397] HDA Intel 0000:00:1b.0: irq 44 for MSI/MSI-X >> [  21.719417] 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 discuss@xxxxxxxxxxxxx >> Âif help is needed. >> >> >> For candidate card in slot 01:00.1, firmware information and bootup >> diagnostics are: >> ÂPCI slot PCI ID SubsystemID Name >> Â---------- --------- --------- -------------- >> Â01:00.1 1002:aa30 18bc:aa30 Audio device: ATI Technologies Inc HD48x0 audio >> >> ÂModem interrupt assignment and sharing: >> Â45:     14     Â9     18     19  PCI-MSI-edge >> Âhda_intel >> Â--- Bootup diagnostics for card in PCI slot 01:00.1 ---- >> [  Â0.369140] pci 0000:01:00.1: reg 10: [mem 0xd0030000-0xd0033fff 64bit] >> [  Â0.369169] pci 0000:01:00.1: supports D1 D2 >> [  21.776947] HDA Intel 0000:01:00.1: PCI INT B -> GSI 17 (level, low) -> >> IRQ 17 >> [  21.777009] HDA Intel 0000:01:00.1: irq 45 for MSI/MSI-X >> [  21.777031] HDA Intel 0000:01:00.1: setting latency timer to 64 >> >> === Finished firmware and bootup diagnostics, next deducing cogent software. >> === >> >> Predictive Âdiagnostics for card in bus 04:02.0: >> Modem chipset Âdetected on >> NAME="Communication controller: Intel Corporation 536EP Data Fax Modem" >> CLASS=0780 >> PCIDEV=8086:1040 >> SUBSYS=8086:1000 >> IRQ=5 >> IDENT=INTEL536EP >> >> ÂFor candidate modem in: Â04:02.0 >>  0780 Communication controller: Intel Corporation 536EP Data Fax Modem >>   ÂPrimary device ID: Â8086:1040 >> ÂSupport type needed or chipset: INTEL536EP >> >> >> >> >> Predictive Âdiagnostics for card in bus 00:03.0: >> Modem chipset not detected on >> NAME="Communication controller: Intel Corporation 4 Series Chipset HECI >> Controller " >> CLASS=0780 >> PCIDEV=8086:2e24 >> SUBSYS=8086:0024 >> IRQ=11 >> HDA2=00:1b.0 >> HDA2=01:00.1 >> >> ÂFor candidate modem in: Â00:03.0 >>  0780 Communication controller: Intel Corporation 4 Series Chipset HECI >> Controller >>   ÂPrimary device ID: Â8086:2e24 >> ÂSupport type needed or chipset: >> >> >> >> Predictive Âdiagnostics for card in bus 00:1b.0: >> Modem chipset not detected on >> NAME="Audio device: Intel Corporation 82801JI " >> CLASS=0403 >> PCIDEV=8086:3a3e >> SUBSYS=8086:0024 >> IRQ=44 >> >> ÂFor candidate modem in: Â00:1b.0 >>  0403 Audio device: Intel Corporation 82801JI >>   ÂPrimary device ID: Â8086:3a3e >> ÂSupport type needed or chipset: >> >> >> >> Predictive Âdiagnostics for card in bus 01:00.1: >> Modem chipset not detected on >> NAME="Audio device: ATI Technologies Inc HD48x0 audio" >> CLASS=0403 >> PCIDEV=1002:aa30 >> SUBSYS=18bc:aa30 >> IRQ=45 >> >> ÂFor candidate modem in: Â01:00.1 >>  0403 Audio device: ATI Technologies Inc HD48x0 audio >>   ÂPrimary device ID: Â1002:aa30 >> ÂSupport type needed or chipset: >> >> >> ÂCompleted candidate modem analyses. >> >> ÂThe base of the UDEV device file system is: /dev/.udev >> >> ÂVersions adequately match for the compiler installed: 4.4.5 >>       and the compiler used in kernel assembly: 4.4.5 >> >> Âlinux-headers-2.6.35-24-generic-pae resources needed for compiling are not >> manifestly ready! >> >> ÂIf compiling is necessary packages must be installed, providing: >> linux-headers-2.6.35-24-generic-pae >> >> >> 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 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 >> 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.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 >> /etc/modprobe.d/sl-modem.conf:install slamr /sbin/modprobe -qb >> ungrab-winmodem; /sbin/modprobe --ignore-install slamr; test -e /dev/slamr0 >> && (chmod 660 /dev/slamr0 && chgrp dialout /dev/slamr0) || (/bin/mknod -m >> 660 /dev/slamr0 c 242 0 2>/dev/null && chgrp dialout /dev/slamr0) >> /etc/modprobe.d/sl-modem.conf:install slusb /sbin/modprobe -qb >> ungrab-winmodem; /sbin/modprobe --ignore-install slusb; test -e /dev/slusb0 >> && (chmod 660 /dev/slusb0 && chgrp dialout /dev/slusb0) || (/bin/mknod -m >> 660 /dev/slusb0 c 243 0 2>/dev/null && chgrp dialout /dev/slusb0) >> /etc/modprobe.d/alsa-base.conf:options snd-atiixp-modem index=-2 >> /etc/modprobe.d/alsa-base.conf: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 -------- >> >> >> >
