ScanModem was not able to identify your modem.
Is it INTERNAL in the computer box? Or USB? Or EXTERNAL?
If internal, is it an ISA card?
Your ModemData.txt below says how to easily get informarion on your
modem if you have Windows on the same machine (replies to ATI commands
given in a Windows modem terminal (screen)).
Jacques
Ajnos Abeeklmor wrote:
> To whom it may concern,
>
> Hi my name is Jason. I am from New Zealand and am new to Linux. I
cannot
> get my 56k modem functioning with Linux. Here is a copy of the Modem
> data from scanModem. Please help me get my modem working!
>
> Regards,
> Jason
>
> _________________________________________________________________
> Live Search delivers results the way you like it. Try live.com now!
> http://www.live.com
> Only plain text email is forwarded by the DISCUSS@xxxxxxxxxxxxx List
> Server.
> Do use the following as the email Subject Line:
> SomeName, YourCountry Ubuntu 6.10 kernel 2.6.17-10-generic
> This will alert cogent experts, and distinguish cases in the Archives.
> YourCountry will enable Country Code guidance.
> Occassionally responses are blocked by an Internet Provider mail
filters.
> So in a day, also check the Archived responses at
> http://www.linmodems.org .
> Local Linux experts can be found through:
> http://www.linux.org/groups/index.html
> -------------------------- System information
----------------------------
> CPU=i686, Ubuntu 6.10
> Linux version 2.6.17-10-generic (root@vernadsky) (gcc version 4.1.2
> 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5)) #2 SMP Fri Oct 13
> 18:45:35 UTC 2006 (Ubuntu 2.6.17-10.33-generic)
> scanModem update of: 2007_March_05
>
>
> USB modem not detected by lsusb
>
> New HDA card type:
>
>
>
> Modem or host audio card candidates have firmware information:
>
> PCI slot PCI ID SubsystemID Name
> ---------- --------- --------- --------------
> 02:01.0 1106:3288 1043:818f Audio device: VIA Technologies,
> Inc. VIA High Definition Audio Controller
>
> Modem interrupt assignment and sharing:
>
> --- Bootup diagnositcs for card in PCI slot 02:01.0 ----
> [17179591.548000] PCI: Enabling device 0000:02:01.0 (0000 -> 0002)
> [17179591.548000] ACPI: PCI Interrupt 0000:02:01.0[A] -> GSI 17 (level,
> low) -> IRQ 225
> [17179591.548000] PCI: Via IRQ fixup for 0000:02:01.0, from 0 to 1
> [17179591.548000] PCI: Setting latency timer of device 0000:02:01.0
to 64
> [17179591.580000] ACPI: PCI interrupt for device 0000:02:01.0 disabled
>
> The PCI slot 02: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 Bootup.txt about possible fixes.
> Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx
> if help is needed.
>
>
> === Finished modem firmware and bootup diagnostics section. ===
> === Next deducing cogent software ===
>
> ALSAversion 1.0.11
> The audio card is not a modem hosting type.
>
> A modem was not detected among the PCI devices:
> ------------------------------------------------
> 00:0f.0 IDE interface: VIA Technologies, Inc. VT8251 AHCI/SATA 4-Port
> Controller
> 00:0f.1 IDE interface: VIA Technologies, Inc.
> VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07)
> 00:11.5 Multimedia audio controller: VIA Technologies, Inc.
> VT8233/A/8235/8237 AC97 Audio Controller (rev 70)
> 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II]
> (rev 7c)
> 01:00.0 VGA compatible controller: VIA Technologies, Inc. UniChrome Pro
> IGP (rev 01)
> 02:01.0 Audio device: VIA Technologies, Inc. VIA High Definition Audio
> Controller
> ------------------------------------------------
> with USB and bridge devices not displayed.
> Please provide any independent information available on your modem.
>
> If your modem is mounted on an ISA card, scanModem could not
access it.
> 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.
>
> Checking for audio+modem support in /proc/asound/pcm
> 00-01: VIA 8251 : VIA 8251 : playback 1 : capture 1
> 00-00: VIA 8251 : VIA 8251 : playback 4 : capture 1
>
> For candidate modem in PCI bus: 02:01.0
> Class 0403: 1106:3288 Audio device: VIA Technologies, Inc. VIA High
> Definition Audio Controller
> Primary PCI_id 1106:3288
> 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.
>
>
> Completed candidate modem analyses.
>
> The base of the UDEV device file system is: /dev/.udev
>
> Versions adequately match for the compiler installed: 4.1.2
> and the compiler used in kernel assembly: 4.1.2
>
>
>
> Compiling resources appear complete:
> make utility - /usr/bin/make
> Compiler version 4.1
> kernel_headers base folder /lib/modules/2.6.17-10-generic/build
>
>
> Checking pppd properties:
> -rwsr-xr-- 1 root dip 260920 2006-07-11 07:13 /usr/sbin/pppd
>
> In case of an "error 17" "serial loopback" problem, see:
> http://phep2.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
> auth
> 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
>
>
> 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/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 --------
>
>
