
 A modem device/card may be disabled at bootup, due to a variety of causes.
 Look at the bootup diagnostics record dmesg.txt  and try to garner some 
 understanding from it. Attach it to your query to  discuss@linmodems.org
 Possibilities therein are too  diverse to be automagically processed by 
 scanModem. A line including the PCI
 bus slot 00:0a.0 of your modem, and "disable" or "disabling" predicts problems,
 though sometimes corrected later in the bootup.  Similarly a line with "@"
 in the interrupt (IRQ) for your 00:0a.0 slot is predictive of problems. 

 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) Blacklist as many drivers as possible. See
         http://linmodems.technion.ac.il/bigarch/archive-eighth/msg01593.html
 6) Sometimes upgrading the kernel solves the problem.
 7) Sometimes downgrading the kernel solves the problem.
 8) Sometimes changing the Linux distribution solves the problem.
 9) Get unloading.gz from http://linmodems.technion.ac.il/linmodems/
 This script unloads excess drivers which may be competing for resources. 
 Before trying to set up the modem, do:
 $ gunzip unloading.gz
 $ chmod +x unloading
 $ su - root 
 # ./unloading
 Or for Ubuntu related Distros
 $ sudo ./unloading

