Re: help with Fedora core 7 dial-up connection

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

 



----- Original Message ----
From: E. Robert Tisdale <edwin@xxxxxxxxxxx>
To: For users of Fedora <fedora-list@xxxxxxxxxx>
Sent: Sunday, June 10, 2007 10:15:10 PM
Subject: Re: help with Fedora core 7 dial-up connection

Antonio Olivares wrote:

>   Have you checked the LinModems Suport Page.  There is a utility called 
> scanModem which you can get
>
> http://linmodems.technion.ac.il/packages/scanModem.gz
>
> 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 discuss@xxxxxxxxxxxxx to 
> send in your ModemData.txt or send it to me off the list so that we can 
> try to help you out.


Robert, 

The modem symbolic link is /dev/modem -> /dev/ttyS3

The diffuculty here is that there is a modem interrupt assignment and sharing 

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, i915@pci: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:
      http://linmodems.technion.ac.il/resources.html 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
    savedefault
   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.
=====================================


 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 =======


Your modem is indeed supported by the serial driver and 
# wvdialconf /etc/wvdial.conf 

should find it.  scanModem says it should be /dev/ttyS3.  You only need to overcome the modem interupt and sharing issue.  Try doing what is in the middle of 

===================================
           HERE!!  but on the above lines.  
===================================

Should you still have troubles, I'll foward your posts where you have tried to fix the modem interrupt and sharing issue to discuss@xxxxxxxxxxxxx for further guidance.

Hope this helps,

Antonio





 
____________________________________________________________________________________
Food fight? Enjoy some healthy debate 
in the Yahoo! Answers Food & Drink Q&A.
http://answers.yahoo.com/dir/?link=list&sid=396545367


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

  Powered by Linux