Will >From your ModemData.txt ------------------------------------- For candidate card in slot 00:03.0, firmware information and bootup diagnostics are: PCI slot PCI ID SubsystemID Name ---------- --------- --------- -------------- 00:03.0 10b9:5457 10cf:1130 Modem: ALi Corporation M5457 AC'97 Modem Controller Modem interrupt assignment and sharing: 11: 146 XT-PIC-XT yenta, yenta, yenta, yenta, ehci_hcd:usb1, ohci_hcd:usb2, ohci_hcd:usb3, firewire_ohci, ALI 5451, eth0, radeon@pci:0000:01:05.0 --- Bootup diagnostics for card in PCI slot 00:03.0 ---- ACPI: PCI Interrupt 0000:00:03.0[A] -> Link [LNKG] -> GSI 11 (level, low) -> IRQ 11 ACPI: PCI interrupt for device 0000:00:03.0 disabled ACPI: PCI Interrupt 0000:00:03.0[A] -> Link [LNKG] -> GSI 11 (level, low) -> IRQ 11 ACPI: PCI interrupt for device 0000:00:03.0 disabled ---------------------- that is, the modem card is DISABLED during bootup due to some resource conflict. So nothing can work until that is cured. What are the 4 yenta (for PCMCIA support) doing.!?! Try detaching all auxilliaries and retest, after reboot You can check for enablement simply with: $ dmesg | grep 00:03.0 which is what the codelet in scanModem does. Once enabled, do run the entire ./scanModem as the 10cf:1130 Subsystem specs will then report the chip type. 1) Read Bootup.txt on alternatives to remedy this disablement situation. Nothing else can work until then. 2) 10b9:5457 cards sometimes have a Conexant chip Install the hsfmodem package from www.linuxant.com and see what it's very good diagnostics reports. 3) Get modem diagnostic info under Microsoft if possible. Report back presently. MarvS scanModem maintainer On Jan 28, 2008 8:03 PM, William Estrada <MrUmunhum@xxxxxxxxxxx> wrote: > Hi group, > I have just installed slmodemd on my new FC8 system on my Fujitsu > LifeBook laptop and > I can't get it to work right. I have run scanModem and put the output at: > http://64.124.13.3/SLmodem/ > Also, the output from wvdial, a script Modem run to setup slmodemd and > my /etc/modules.conf. > I have read everything and I am lost about what is wrong. I did get > minicom to work almost. > It found the modem but could not dial out, "NO CARRIER", but that was a > day ago. > > Any help? >
