Roger, The documentation is fully understood, though the Class=0700 is a readout from the modem firmware and SHOULD not be Linux distribution/update dependent. However we have encountered strange hacks upon modem hardware by assemblers. If your modem did work previously, If should work again. But while /dev/ttyS4 was tested by wvdialconf, the modem did not respond! >From the diagnostic: slmodemd created symbolic link /dev/ttySL0: <------------------ ? not ttyS4 ? there may be a slmodem/slmodemd package installed, whose drivers could be interferring with the function of your 3COM modem. These packages are completely inappropriate to hardware modems. These packages could include (ignore the qunatal, yours is Precise): ========== Package sl-modem-daemon quantal (misc): SmartLink software modem daemon [restricted] 2.9.11~20110321-8: amd64 i386 Package sl-modem-dkms quantal (misc): SmartLink software modem driver - module building source [multiverse] 2.9.11~20110321-8: amd64 i386 Package sl-modem-source quantal (misc): SmartLink software modem driver (dummy transitional package) [multiverse] 2.9.11~20110321-8: all ==== These can be uninstalled with: $ sudo apt-get remove sl-modem-daemon sl-modem-source sl-modem-dkms Then reboot and rerun $ sudo wvdial If there is still a problem, some fiddling with the setserial utility may help. Also Linux is backward compatible with prior kernels generally. So under your current update, you could still install the last linux-image package that supported your modem. In fact if you didn't explcitly remove it following your last update, you should be able to boot with that older kernel now. Use the prior/older kernels option upon bootup to find it. Run the diagnostics again under the compatible kernel and report back. MarvS You can get the package names with: $ sudo apt-cache search slmodem Then the uninstall command will be something like: $ sudo apt-get remove s-lmodem-source On Tue, Feb 12, 2013 at 1:17 AM, Roger Davis <rogerdavis@xxxxxxxxxxx> wrote: > > From: Roger Davis > Date: Feb 11, 2013 10:16:18 PM > Subject: Re: Re: Re: Persistant Modem Problem > To: marvin.stodolsky@xxxxxxxxx, discuss@xxxxxxxxxxxxx > > > This is a full hardware modem! Please read ALL below... > > http://reviews.ebay.com/WinFax-PRO-READ-THIS-1st?ugid=10000000003656539 > > > All external modems which use the serial port connection (usually 9pin or 25pin) are Controller based modems. Also often called "Hardware Modem". The processing is done all within the modem itself, and not the computer. These modems have the DPU & MCU built into the hardware so you don't have the computer worry about these tasks. These are the best types of modems. You can also purchase internal versions of these modems in PCI or PCIe format, but they are a rare find as few manufacturers make these. Found new at around $50 and up for external, internal hardware modems PCI/PCIe $70 and up. U.S. Robotics 5610 is a controller based internal fax modem. > (emphasis added) > http://www.xpheads.com/forums/630890-post33.html Controller-based modems have both the DPU and MCU built-in. All external modems that connect to a computer over a serial cable are full controller-based modems. It is RARE to find a full controller-based hardware modem in PCI or PCIe format. The U.S. Robotics 5610 is a controller based PCI internal fax modem. (emphasis added) > > Definition of a soft modem is: A Softmodem, or software modem, is a modem with minimal hardware capacities, designed to use a host computer's resources (mostly CPU power and RAM but sometimes even audio hardware) to perform most of the tasks performed by dedicated hardware in a traditional modem. This is exactly the opposite, a FULL hardware modem, even including it's own serial port. It's basically a full external modem on a card with it's own serial port built in. It's NOT a Winmodem OR a softmodem. Look at http://en.wikipedia.org/wiki/Softmodem for proof. > > Also see specifications at http://www.usr.com/products/modem/modem-product.asp?type=specs&sku=USR5610C . Part of that page is: > Standards and Specifications > V.92, V.90, V.34, V.32bis, V.32, V.22bis, V.22, V.23, and V.21 > V.42/MNP 2-4 error correction, V.42 bis/ MNP 5 compression > V.80 video conferencing support > Fax: EIA 578 (Class 1) and EIA 592 (Class 2.0) with V.17, V.29, V.27ter ITU recommendations > Caller ID and distinctive ring (require service from your local phone company/Caller ID may not be supported in some countries)It has Linux support, please see page at http://www.usr.com/support/product-template.asp?prod=5610c . Here is part of that page, showing supported OS's and other info. > USR5610C 56K Performance Pro Modem (PCI Internal)USR325610C, USR5610C-VAR-20, 64-005610-02R > OS Compatibility > > > Win8, 2011, Win7, 2008, Vista, Vista 64, XP 64, 2003, XP, 2K, Me, 98 SE, 98 FE, 95, Linux > > > Red Hat Package ManagerUSRobotics Corporation is pleased to provide the following Red Hat Package Manager (.rpm) support file. This RPM package has been tested under Red Hat Linux 6.0 and higher. It should also work with other Linux distributions supporting the RPM utility. > > Install the RPM file by entering the rpm -i 3ComMdm-1.0-1.i386.rpm command at the command prompt. > > This file can also be used as a basis to write your own script for UNIX/LINUX hybrids. If you make your own scripts for a hybrid, it would be appreciated if you could send this script to USRobotics so that we may post it so that others may benefit as well. > > Maybe Ubuntu now thinks it's a soft modem, and that could be the problem - but it DID work before an Ubuntu update a few months back. > > Please reevaluate your position. > > > On 02/11/13, Marvin Stodolsky<marvin.stodolsky@xxxxxxxxx> wrote: > > > > It is thus a soft modern without Linux support. > > Sorry > > MarvS > On Feb 11, 2013 8:36 PM, "Roger Davis" <rogerdavis@xxxxxxxxxxx> wrote: > > Yes, that is the modem. Here is the output from sudo wvdialconf > ======================================== > roger@roger-desktop:~$ sudo wvdialconf > [sudo] password for roger: > Editing `/etc/wvdial.conf'. > > Scanning your serial ports for a modem. > > Modem Port Scan<*1>: S0 S1 S2 S3 > ttyS4<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud > ttyS4<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud > ttyS4<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. > Modem Port Scan<*1>: S5 S6 S7 S8 > Modem Port Scan<*1>: S9 S10 S11 S12 S13 S14 S15 S16 > Modem Port Scan<*1>: S17 S18 S19 S20 S21 S22 S23 S24 > Modem Port Scan<*1>: S25 S26 S27 S28 S29 S30 S31 > > Sorry, no modem was detected! Is it in use by another program? > Did you configure it properly with setserial? > > Please read the FAQ at http://alumnit.ca/wiki/?WvDial > > > ----------------------------------------------------------------------------------------------------------------- > This isn't a Linmodem, it's a pci slot full modem, very much like a USR external full modem, only on a card with it's own serial port built in. > > If you saw the info at https://bugs.launchpad.net/ubuntu/+bug/1087519 , you might have noticed that the modem works fine in Windoze in the same machine, different drive, and the breakdown seems to be in communication with Ubuntu. It used to work until some update killed it. Lots more info there. > > Thanks! > > > > The reasonable man adapts himself to the world. > The unreasonable man persists in trying to adapt the world to himself. > Therefore, all progress depends on the unreasonable man. > > ,-._,-. > \/)"(\/ > (:o:) > (!) > > On 02/11/13, Marvin Stodolsky<marvin.stodolsky@xxxxxxxxx> wrote: > > On Mon, Feb 11, 2013 at 9:15 PM, Marvin Stodolsky > <marvin.stodolsky@xxxxxxxxx> wrote: >> >> Roger, >> >> Assuming that your only modem is the: >> ------- >> card in bus 04:01.0: >> NAME="Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 >> " >> CLASS=0700 >> PCIDEV=12b9:1008 >> SUBSYS=12b9:00d3 >> IRQ=17 >> IDENT=USrobotics.serial >> ------- >> The Class=0700 is for softmodems >> and US Robotics has never provided Linux support for them. >> >> However it will do no harm to try: >> $ sudo wvdialconf >> which will only be successful if instead the modem is a chipset >> Class=0780 >> type, which would be supported by the serial driver included in the >> kernel. >> >> Sincerely: >> >> MarvS >> scanModem maintainer >> >> On Mon, Feb 11, 2013 at 8:01 PM, Roger Davis <rogerdavis@xxxxxxxxxxx> >> wrote: >>> >>> >>> From: Roger Davis >>> Date: Feb 11, 2013 4:54:16 PM >>> Subject: Persistant Modem Problem >>> To: discuss@xxxxxxxxxxxxx >>> >>> Here is the output from ScanModem: >>> >>> Please especially look at <----- points . I added comments / questions >>> after <----------- ? . >>> >>> Much more info at https://bugs.launchpad.net/ubuntu/+bug/1087519 . >>> >>> THANKS!!!!! >>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>> >>> >>> -------------------------- System information >>> ---------------------------- >>> CPU=x86_64, Ubuntu , ALSA_version=1.0.24 >>> Linux version 3.2.0-38-generic (buildd@allspice) (gcc version 4.6.3 >>> (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #59-Ubuntu SMP Tue Feb 5 17:53:03 UTC 2013 >>> scanModem update of: 2011_08_08 >>> >>> Distrib_ID=Ubuntu >>> DistribCodeName=precise >>> AptRepositoryStem=http://us.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, >>> <-------- ? this is a 64 bit system, but not linmodem >>> 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: >>> snd_hda_intel <------------------ ? >>> >>> Attached USB devices are: >>> ID 8087:0024 Intel Corp. Integrated Rate Matching Hub >>> ID 8087:0024 Intel Corp. Integrated Rate Matching Hub >>> ID 057b:0000 Y-E Data, Inc. FlashBuster-U Floppy >>> ID 051d:0002 American Power Conversion Uninterruptible Power Supply >>> ID 058f:6366 Alcor Micro Corp. Multi Flash Reader >>> ID 046d:c52b Logitech, Inc. Unifying Receiver >>> 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:16.0 Communication controller: Intel Corporation Panther Point MEI >>> Controller #1 (rev 04) <------------------ wifi ? >>> 04:01.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model >>> 5610 (rev 01) <------------------ my modem >>> 00:1b.0 Audio device: Intel Corporation Panther Point High Definition >>> Audio Controller (rev 04) >>> 01:00.1 Audio device: Advanced Micro Devices [AMD] nee ATI Device aab0 >>> High Definition Audio cards can host modem chips. >>> >>> For candidate card in slot 00:16.0, firmware information and bootup >>> diagnostics are: >>> PCI slot PCI ID SubsystemID Name >>> ---------- --------- --------- -------------- >>> 00:16.0 8086:1e3a 8086:2040 Communication controller: Intel Corporation >>> Panther Point MEI Controller #1 >>> >>> Modem interrupt assignment and sharing: >>> 54: 15 0 0 0 0 0 0 0 IR-PCI-MSI-edge mei >>> --- Bootup diagnostics for card in PCI slot 00:16.0 ---- >>> [ 1.047828] pci 0000:00:16.0: [8086:1e3a] type 0 class 0x000780 >>> [ 1.047849] pci 0000:00:16.0: reg 10: [mem 0xf7f3b000-0xf7f3b00f 64bit] >>> [ 1.047919] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold >>> [ 1.047922] pci 0000:00:16.0: PME# disabled >>> [ 9.966807] mei 0000:00:16.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 >>> [ 9.966813] mei 0000:00:16.0: setting latency timer to 64 >>> [ 9.966875] mei 0000:00:16.0: irq 54 for MSI/MSI-X >>> >>> The PCI slot 00:16.0 of the modem card may be disabled early in >>> <------------------ ? not my modem, wifi? >>> 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:01.0, firmware information and bootup >>> diagnostics are: <------------------ my modem >>> PCI slot PCI ID SubsystemID Name >>> ---------- --------- --------- -------------- >>> 04:01.0 12b9:1008 12b9:00d3 Serial controller: 3Com Corp, Modem Division >>> 56K FaxModem Model 5610 >>> >>> Modem interrupt assignment and sharing: >>> --- Bootup diagnostics for card in PCI slot 04:01.0 ---- >>> [ 1.054714] pci 0000:04:01.0: [12b9:1008] type 0 class 0x000700 >>> [ 1.054758] pci 0000:04:01.0: reg 10: [io 0xd000-0xd007] >>> [ 1.054963] pci 0000:04:01.0: supports D2 >>> [ 1.054964] pci 0000:04:01.0: PME# supported from D0 D2 D3hot D3cold >>> [ 1.054972] pci 0000:04:01.0: PME# disabled >>> [ 1.424176] serial 0000:04:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ >>> 17 >>> [ 1.445144] 0000:04:01.0: ttyS4 at I/O 0xd000 (irq = 17) is a 16550A >>> >>> The PCI slot 04:01.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:1e20 8086:2040 Audio device: Intel Corporation Panther >>> Point High Definition Audio Controller >>> >>> Modem interrupt assignment and sharing: >>> 55: 2206 0 0 0 0 0 0 0 IR-PCI-MSI-edge snd_hda_intel >>> --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- >>> [ 1.048194] pci 0000:00:1b.0: [8086:1e20] type 0 class 0x000403 >>> [ 1.048208] pci 0000:00:1b.0: reg 10: [mem 0xf7f30000-0xf7f33fff 64bit] >>> [ 1.048270] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold >>> [ 1.048273] pci 0000:00:1b.0: PME# disabled >>> [ 9.998776] snd_hda_intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) >>> -> IRQ 22 >>> [ 9.998829] snd_hda_intel 0000:00:1b.0: irq 55 for MSI/MSI-X >>> [ 9.998850] snd_hda_intel 0000:00:1b.0: setting latency timer to 64 >>> [ 10.048400] input: HDA Intel PCH Line as >>> /devices/pci0000:00/0000:00:1b.0/sound/card0/input4 >>> [ 10.048456] input: HDA Intel PCH Front Mic as >>> /devices/pci0000:00/0000:00:1b.0/sound/card0/input5 >>> [ 10.048499] input: HDA Intel PCH Rear Mic as >>> /devices/pci0000:00/0000:00:1b.0/sound/card0/input6 >>> [ 10.048532] input: HDA Intel PCH Front Headphone as >>> /devices/pci0000:00/0000:00:1b.0/sound/card0/input7 >>> [ 10.048563] input: HDA Intel PCH Line-Out CLFE as >>> /devices/pci0000:00/0000:00:1b.0/sound/card0/input8 >>> [ 10.048629] input: HDA Intel PCH Line-Out Surround as >>> /devices/pci0000:00/0000:00:1b.0/sound/card0/input9 >>> [ 10.048683] input: HDA Intel PCH Line-Out Front as >>> /devices/pci0000:00/0000:00:1b.0/sound/card0/input10 >>> >>> 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:aab0 174b:aab0 Audio device: Advanced Micro Devices [AMD] >>> nee ATI Device aab0 >>> >>> Modem interrupt assignment and sharing: >>> --- Bootup diagnostics for card in PCI slot 01:00.1 ---- >>> [ 1.049233] pci 0000:01:00.1: [1002:aab0] type 0 class 0x000403 >>> [ 1.049243] pci 0000:01:00.1: reg 10: [mem 0xf7e60000-0xf7e63fff 64bit] >>> [ 1.049299] pci 0000:01:00.1: supports D1 D2 >>> [ 10.048868] snd_hda_intel 0000:01:00.1: PCI INT B -> GSI 17 (level, low) >>> -> IRQ 17 >>> [ 10.048929] snd_hda_intel 0000:01:00.1: irq 56 for MSI/MSI-X >>> [ 10.048943] snd_hda_intel 0000:01:00.1: setting latency timer to 64 >>> [ 10.568736] snd_hda_intel 0000:01:00.1: PCI INT B disabled >>> [ 10.568742] snd_hda_intel: probe of 0000:01:00.1 failed with error -16 >>> >>> The PCI slot 01:00.1 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. >>> >>> === Finished firmware and bootup diagnostics, next deducing cogent >>> software. === >>> >>> Predictive diagnostics for card in bus 04:01.0: >>> Modem chipset detected on >>> NAME="Serial controller: 3Com Corp, Modem Division 56K FaxModem Model >>> 5610 " >>> CLASS=0700 >>> PCIDEV=12b9:1008 >>> SUBSYS=12b9:00d3 >>> IRQ=17 >>> IDENT=USrobotics.serial >>> >>> For candidate modem in: 04:01.0 >>> 0700 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model >>> 5610 >>> Primary device ID: 12b9:1008 >>> Support type needed or chipset: USrobotics.serial >>> >>> Predictive diagnostics for card in bus 00:16.0: >>> Modem chipset not detected on >>> NAME="Communication controller: Intel Corporation Panther Point MEI >>> Controller #1 " >>> CLASS=0780 >>> PCIDEV=8086:1e3a >>> SUBSYS=8086:2040 >>> IRQ=54 >>> HDA2=00:1b.0 >>> HDA2=01:00.1 >>> >>> For candidate modem in: 00:16.0 >>> 0780 Communication controller: Intel Corporation Panther Point MEI >>> Controller #1 >>> Primary device ID: 8086:1e3a >>> Support type needed or chipset: >>> >>> Predictive diagnostics for card in bus 00:1b.0: >>> Modem chipset not detected on >>> NAME="Audio device: Intel Corporation Panther Point High Definition Audio >>> Controller " >>> CLASS=0403 >>> PCIDEV=8086:1e20 >>> SUBSYS=8086:2040 >>> IRQ=55 >>> >>> For candidate modem in: 00:1b.0 >>> 0403 Audio device: Intel Corporation Panther Point High Definition Audio >>> Controller >>> Primary device ID: 8086:1e20 >>> Support type needed or chipset: >>> >>> Predictive diagnostics for card in bus 01:00.1: >>> Modem chipset not detected on >>> NAME="Audio device: Advanced Micro Devices [AMD] nee ATI Device aab0" >>> CLASS=0403 >>> PCIDEV=1002:aab0 >>> SUBSYS=174b:aab0 >>> IRQ=17 >>> >>> For candidate modem in: 01:00.1 >>> 0403 Audio device: Advanced Micro Devices [AMD] nee ATI Device aab0 >>> Primary device ID: 1002:aab0 >>> 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.6.3 >>> and the compiler used in kernel assembly: 4.6 >>> >>> linux-headers-3.2.0-38-generic resources needed for compiling are not >>> manifestly ready! <------------------ ?!? >>> >>> If compiling is necessary packages must be installed, providing: >>> <------------------ ?!? >>> linux-headers-3.2.0-38-generic >>> >>> 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-sr-- 1 root dip 325744 Feb 4 2011 /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 >>> 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: <------------------ ? not >>> ttyS4 ? >>> 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: >>> >>> >>> The reasonable man adapts himself to the world. >>> The unreasonable man persists in trying to adapt the world to himself. >>> Therefore, all progress depends on the unreasonable man. >>> >>> ,-._,-. >>> \/)"(\/ >>> (:o:) >>> (!) >> >> >
