Ann,
ScanModem reports a Modem Interrupt assignment and sharing:
<quote>
Modem interrupt assignment and sharing:
===================================
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.
=====================================
--- Bootup diagnostics for card in PCI slot 01:09.0 ----
For candidate card in slot 01:0b.0, firmware information and bootup
diagnostics are:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
01:0b.0 14f1:2013 155d:8850 Communication controller: Conexant HSF
56k Data/Fax Modem
Modem interrupt assignment and sharing:
===================================
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.
=====================================
</quote>
With this you will have to try to follow the advice given by
scanModem. When this is resolved you can get a working driver from
linuxant
From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
and follow the link given in the quote.
<quote>
--- Bootup diagnostics for card in PCI slot 01:0b.0 ----
=== Finished firmware and bootup diagnostics, next deducing cogent software. ===
Predictive diagnostics for card in bus 01:0b.0:
Modem chipset detected on
CLASS="Class 0780: 14f1:2013"
NAME="Communication controller: Conexant HSF 56k Data/Fax Modem "
SUBSYS=155d:8850
PCIDEV=14f1:2013
IRQ=255
IDENT=hsfmodem
For candidate modem in: 01:0b.0
Class 0780: 14f1:2013 Communication controller: Conexant HSF 56k
Data/Fax Modem
Primary device ID: 14f1:2013
Support type needed or chipset: hsfmodem
For owners of a Dell PCs with Conexant HSF modems, a driver source
package with full speed enabled is available, but requires driver
compiling. Read Conexant.txt
From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php
download hsfmodem-7.68.00.07full_k2.6.24_16_generic_ubuntu_i386.deb.zip
Under Linux unpack with:
$ unzip hsfmodem*.zip
Then install with:
$ sudo dpkg -i hsfmodem*.deb
Subsequently, the modem should be found with
$ sudo wvdialconf /etc/wvdial.conf
Edit in your personal information with:
$ sudo gedit /etc/wvdial.conf
and try dialing out with:
$ sudo wvdial.
See Testing.txt for details.
Read Conexant.txt
</quote>
While you are closer you will need to resolve the Modem Interrupt and
sharing and then you can use the hsfmodem from linuxant and your modem
should work.
Regards,
Antonio
On 5/10/08, Ann <tate886@xxxxxxxxx> wrote:
>
>
>
