Re: help with Fedora core 7 dial-up connection

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


Antonio Olivares wrote:

Have you checked the LinModems Suport Page. There is a utility called scanModem which you can get

copy it to your linux partition
# gunzip scanModem.gz
# chmod +x scanModem
# ./scanModem

will generate a Modem/ folder in which ModemData.txt gets generated and it will tell you which modem driver you need if there is one for your modem(s). You will need to subscribe to the list [email protected] to send in your ModemData.txt or send it to me off the list so that we can try to help you out.
Only plain text email is forwarded by the  [email protected] List Server.
Do use the following as the email Subject Line:
          SomeName, YourCountry Fedora release 7 (Moonshine)
Kernel kernel 2.6.20-2925.9.fc7xen 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 .
Local Linux experts can be found through:
--------------------------  System information ----------------------------
CPU=i686,  Fedora release 7 (Moonshine)
Kernel Linux version 2.6.20-2925.9.fc7xen ([email protected]) (gcc version 4.1.2 20070502 (Red Hat 4.1.2-12)) #1 SMP Tue May 22 08:53:03 EDT 2007
scanModem update of:  2007_June_06
The modem symbolic link is /dev/modem -> /dev/ttyS3

ALSAversion 1.0.14rc2
USB modem not detected by lsusb

Modem or host audio card candidates have firmware information:

PCI slot	PCI ID		SubsystemID	Name
----------	---------	---------	--------------
02:04.0 12b9:1008 12b9:00d3 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 Modem interrupt assignment and sharing:
--- Bootup diagnositcs for card in PCI slot 02:04.0 ----

PCI slot	PCI ID		SubsystemID	Name
----------	---------	---------	--------------
00:1b.0 8086:2668 103c:2a09 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW Modem interrupt assignment and sharing: 16: 45824 0 Phys-irq-level uhci_hcd:usb4, HDA Intel, [email protected]:0000:00:02.0
--- Bootup diagnositcs for card in PCI slot 00:1b.0 ----
ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1b.0 to 64

=== Finished modem firmware and bootup diagnostics section. ===
=== Next deducing cogent software ===

The modem interrupt (IRQ) is 255 . IRQs of 0 or 255 are not functional!! The CPU cannot control the modem until this situation is corrected!!
Possible corrections are:
  1) Within the boot up BIOS, change from a Windows to a non-PNP/Other Operating System type.
  Instructions for accessing BIOS are at: within:  Additional Resourcces.
  2a) Add an option "pci=routeirq" to the kernel boot up line.
     Here is an example paragraph from  /boot/grub/menu.lst :
	title           Ubuntu, kernel 2.6.15-26-686
	root            (hd0,6)
	kernel          /boot/vmlinuz-2.6.15-26-686 root=/dev/hda7 ro pci=routeirq
	initrd          /boot/initrd.img-2.6.15-26-686
2b) Same as above, but use "pollirq" instead of "pci=routeirq". 3) Within some BIOS setups, IRQ assignments can be changed.
  4) On non-laptop systems, moving the modem card to another slot has helped.
  5) Sometimes upgrading the kernel changes IRQ assignment.

8086:2668 is a High Definition Audio card, possibly hosting a soft modem.
For candidate modem in PCI bus:  00:1b.0
  Class 0403: 8086:2668 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW
     Primary PCI_id  8086:2668
Subsystem PCI_id 103c:2a09 Softmodem codec or Vendor from diagnostics: from Archives: 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:	

Support can likely be achieved through two mutually exclusive alternatives:
1) An ALSA modem driver plus slmodemd.  Read Smartlink.txt for details, and
to test get the package SLMODEMD.gcc4.1.tar.gz from:
2) The hsfmodem software for Conexant chipset modems: Read Conexant.txt

An ALSA (Advanced Linux Sound Architecture) modem driver:  snd-intel8x0m
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 the package SLMODEMD.gcc4.1.tar.gz having a compiled slmodemd. Unpack under Linux with:
	$ tar zxf SLMODEMD.gcc4.1.tar.gz
and read instructions therein. But briefly, the modem is setup with command:
slmodemd -c YOUR_COUNTRY --alsa modem:1 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.

Already loaded into the kernel is snd-intel8x0m and audio drivers it depends on,
displayed by:	lsmod | grep snd_intel8x0m
Module                  Size  Used by
snd_intel8x0m 19732 0 snd_ac97_codec 93128 1 snd_intel8x0m
snd_pcm                74156  5 snd_intel8x0m,snd_ac97_codec,snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd                    53956  13 snd_intel8x0m,snd_ac97_codec,snd_hda_intel,snd_hda_codec,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
snd_page_alloc         13832  3 snd_intel8x0m,snd_hda_intel,snd_pcm

The diagnostic outputs for this softmodem section have their raw information in
folders and text files under /proc/asound/ which you can browse. The information
is from files:
00-02: ALC880 Analog : ALC880 Analog : capture 2
00-00: ALC880 Analog : ALC880 Analog : playback 1 : capture 2

0 snd_hda_intel
and from the command:
	aplay -l | grep -i modem

----------------end Softmodem section --------------

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 Intel.txt

Freeware support may be available for a few Conexant chipset modems with support confirmed only for the PCI_id chipset 14f1:2f00.

Otherwise formal support for Conexant chipset modems are available ONLY through Read Conexant.txt for details.
and Modem/YourSystem.txt for follow through guidance.  Driver speed is limited to
14,400 until a key is purchased.  There is NO freeware alternative.
There are two support package types: hsfmodem  and hcflinmodem. reports a
problem and solution in stalling a key, after testing of the free low
speed download.

Read Conexant.txt

Writing Conexant.txt

Writing Smartlink.txt
============ end Smartlink section =====================

For candidate modem in PCI bus:  02:04.0
  Class 0700: 12b9:1008 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610
     Primary PCI_id  12b9:1008
Support type needed or chipset:	USrobotics.serial

Vendor 10b7 3COM Inc. purchased the vendor 12b9 US Robotics modem technology.
Their winmodems have no Linux support. Their controller chipset modems
are supported by the Linux serial drivers.
The PCI id 12b9:1008 modem is Supported.

PCI ID          Name                                    Support status
10b7:1006	3COM 0038TA AC101 - TF Mini-PCI		winmodem, not supported
10b7:1007	3COM 3C556 V.90 Mini-PCI		winmodem, not supported
12b9:1006	US Robotics 3cp803598  Voice		winmodem, not supported
12b9:1007	US Robotics ERL3263A-0 DF GWPCI PC99	winmodem, not supported

12b9:0062	US Robotics erk41926a-0.6 usr 56k	serial driver supported
12b9:1008	US Robotics 3cp803598	                serial driver supported
    wvdialconf wvtest     , should detect the modem. Read Testing.txt
 ====== end 3COM section =======

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

Kernel-header resources needed for compiling are not manifestly ready!

If compiling is necessary packages must be installed, providing:

Checking pppd properties:
	-r-xr-xr-x 1 root root 312332 2006-12-01 04:54 /usr/sbin/pppd

In case of an "error 17" "serial loopback" problem, see:

To enable dialout without Root permission do:
	$ su - root  (not for Ubuntu)
        chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
	 chmod a+x /usr/sbin/pppd

Checking settings of:	/etc/ppp/options

In case of a message like:
  Warning: Could not modify /etc/ppp/pap-secrets: Permission denied

Read Modem/YourSystem.txt concerning other COMM channels: virbr0
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:   lrwxrwxrwx 1 root root 10 2007-06-10 18:47 /dev/modem -> /dev/ttyS3
slmodemd created symbolic link /dev/ttySL0: Within /etc/udev/ files:
/etc/udev/rules.d/50-udev.rules:KERNEL=="modems/mwave*",        NAME="%k", GROUP="uucp", MODE="0660"
    Within /etc/modprobe.conf files:

    Within any ancient /etc/devfs files:

    Within ancient kernel 2.4.n /etc/module.conf files:

--------- end modem support lines --------

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux