Justin,
The archival information:
Primary PCI_id 1002:437b
Subsystem PCI_id 1043:13d7
Softmodem codec or chipset from diagnostics:
from Archives: 10573055, residing on
a HDA Subsystem with support by slmodemd and driver snd-hda-intel
The HDA card softmodem chip is 0x10573055
is consistent with your info:
Asus a9rs laptop with an internal Motorola sm56 voice modem.
Others on this List have good service from this modem.
The problem under your Mephis Linux is likely that the addition of the
modem support to the snd-hda-intel driver began after ALSA verion
1.0.1.
Wth a modemi competent snd-hda-intel, the 0x10573055 chip would have
been reported by ALSA diagnostics written in your /proc/asound/
folders, that scanModem parses.
Your choices are
1) switch to a Linux distro and release using a more recent kernel+modules
than your 2.6.15-26-386, such as 2.6.20 or more recent.
2) Compile a new set of snd-hda-intel + dependent drivers, install and
retest,following
http://linmodems.technion.ac.il/archive-seventh/msg00282.html
MarvS
scanModem maintainer
On Fri, Feb 29, 2008 at 5:58 PM, Justin Hardy
<justinhardy@xxxxxxxxxxxxxxx> wrote:
> G'day,
> I have an Asus a9rs laptop with an internal Motorola sm56 voice
> modem which works with Windows XP pro (com port 3). Ubuntu (running on
> a dual instalation) will not recognise this even chasing it through to
> the number 127.0.0.1 (giving the port its connected to I assume).
> Running a live cd of mepis 6.0 I can get it to tell me the modem is busy
> (when its not) but I cannot find the port reference.
> I have run the scanModem software and the results above.
> My knowlege of the workings of operating systems and things is limited,
> any help will be much appreciated.
>
> Thanks
> Justin
>
> 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.15-26-386
> With this Subject Line cogent experts will be alerted, and useful case names left in the Archive.
> YourCountry will enable Country specific guidance. Your contry's local Linux experts
> 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.15-26-386 (root@mepis-party) (gcc version 4.0.3 (Ubuntu 4.0.3-1ubuntu5)) #1 PREEMPT Wed Jul 19 12:14:26 EDT 2006
> scanModem update of: 2008_02_25
>
>
> There are no blacklisted modem drivers in /etc/modprobe* files
>
> The Advanced Linux Sound Architecture (ALSA) packages providing audio support,
> also includes drivers for some modems. The ALSA diagnostics are written during
> bootup to /proc/asound/ folders.
>
> The /proc/asound/ audio+modem diagostics are being copied.
> Finished copy to Modem/ALSAroot.tgz
>
> The ALSA verion is 1.0.10
> The modem cards detected by "aplay -l" are:
>
>
> The /proc/asound/pcm file reports:
> -----------------------
> 00-00: ALC861 Analog : ALC861 Analog : playback 1 : capture 2
>
> about /proc/asound/cards:
> ------------------------
> 0 [SB ]: HDA-Intel - HDA ATI SB
> HDA ATI SB at 0xfebf8000 irq 185
>
> USB modem not detected by lsusb
>
> For candidate card in slot 0000:00:14.2, firmware information and bootup diagnostics are:
> PCI slot PCI ID SubsystemID Name
> ---------- --------- --------- --------------
> 0000:00:14.2 1002:437b 1043:13d7 0403: ATI Technologies Inc: Unknown device 437b
>
> Modem interrupt assignment and sharing:
> 185: 42398 IO-APIC-level HDA Intel, yenta
> --- Bootup diagnostics for card in PCI slot 0000:00:14.2 ----
> [17179609.676000] ACPI: PCI Interrupt 0000:00:14.2[A] -> GSI 16 (level, low) -> IRQ 185
>
>
> === Finished modem firmware and bootup diagnostics section. ===
> === Next deducing cogent software ===
>
>
> Predictive diagnostics for card in bus 0000:00:14.2:
> Modem chipset detected on
> CLASS="Class 0403: 1002:437b"
> NAME="0403: ATI Technologies Inc: Unknown device 437b "
> PCIDEV=1002:437b
> SUBSYS=1043:13d7
> SUBven=1043
> IRQ=185
> CODECp=10573055
> IDENT=slmodemd
> CODECp=10573055
> HDA=1002:437b
> CHIP=0x10573055
> SOFT=1002:437b.HDA
>
> For candidate modem in: 0000:00:14.2
> Class 0403: 1002:437b 0403: ATI Technologies Inc: Unknown device 437b
> Primary PCI_id 1002:437b
> Subsystem PCI_id 1043:13d7
> Softmodem codec or chipset from diagnostics:
> from Archives: 10573055, residing on a HDA Subsystem with support by slmodemd and driver snd-hda-intel
> The HDA card softmodem chip is 0x10573055
>
>
> Lacking a dsp (digital signal processing) chip, the modem is a software
> intensive or "softmodem" type. Its primary controller manages the traffic
> with the CPU. But the software needed is specified in the Subsystem.
> -----------------------------------------
> Support type needed or chipset: slmodemd
>
> An ALSA (Advanced Linux Sound Architecture) modem driver:
> provides Low Level support enabling contact with the modem hardware.
> For all BUT Conexant chip soft modems (using hsfmodem software)
> complementary High Level support is through a Smartlink utility: slmodemd
>
> Download from http://linmodems.technion.ac.il/packages/smartlink/
> the package SLMODEMD.gcc4.0.tar.gz having a compiled slmodemd. Unpack under Linux with:
> $ tar zxf SLMODEMD.gcc4.0.tar.gz
> and read instructions therein. But briefly, the modem is setup with command:
> sudo slmodemd -c YOUR_COUNTRY --alsa hw:0,1_or_hw:0,6
> reporting dynamic creation of ports:
> /dev/ttySL0 --> /dev/pts/N , with N some number
> Read Smartlink.txt and Modem/YourSystem.txt for follow through guidance.
>
> ----------------end Softmodem section --------------
> Writing 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.0.3
> and the compiler used in kernel assembly: 4.0.3
>
> linux-headers-2.6.15-26-386 resources needed for compiling are not manifestly ready!
>
> If compiling is necessary packages must be installed, providing:
> linux-headers-2.6.15-26-386
>
>
> 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 package
> 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 257720 2006-07-05 09:00 /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
> noipdefault
> passive
> 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/YourSystem.txt concerning other COMM channels: eth0
> Which can interfere with Browser naviagation.
>
> Don't worry about the following, it is for the 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:
> /etc/udev/mepis.rules:# modems
> /etc/udev/mepis.rules:KERNEL="ttyLTM0", SYMLINK="modem"
> /etc/udev/mepis.rules:KERNEL="536ep0", SYMLINK="modem"
> /etc/udev/rules.d/010_mepis.rules:# modems
> /etc/udev/rules.d/010_mepis.rules:KERNEL="ttyLTM0", SYMLINK="modem"
> /etc/udev/rules.d/010_mepis.rules:KERNEL="536ep0", SYMLINK="modem"
> /etc/udev/rules.d/60-symlinks.rules:# Create /dev/modem symlink
> /etc/udev/rules.d/60-symlinks.rules:KERNEL=="ttyLTM[0-9]*", SYMLINK+="modem"
> 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 --------
>
>
>
