Ash,
Your System seems to have some strange features. Do:
$ lspci >> ash.txt
$ cat /proc/interrupts >> ash.txt
$ dmesg >> ash.txt
and send to the List.
Do
$ bash -x ./scanModem 2>&1 | tee ashscan.txt
and send just to me, so I can determine why scanModem quit early.
Run:
$ scanModem fake 10de:00d9 103c:006d
which will access archival information, reporting 10de:00d9 is the
PCI identifier of an AC'97 Modem controller card with an Agere SIL27
modem chip, rather than an audio card.
This could be someone's mistake in a the PCI ID datebase, which is the
simplest explanation. Is your Audio working?
Assuming 103c:006d is in fact your modem, the most immediate problem is:
[ 16.245939] ACPI: PCI interrupt for device 0000:00:06.1 disabled
That is, the card was disabled during the bootup diagnostics.
This is the lead problem to overcome, for which the ash.txt will
provide useful info.
If you do not need USB function, b;ocking loading of the ehci_hcd
driver sharing
interrupt 18
may suffice to enable the modem.
Only AFTER enablement, can the standard guidance for this modem Class be useful.
----------------------
Download from http://linmodems.technion.ac.il/packages/smartlink/
the package SLMODEMD.gcc4.2.tar.gz having a compiled slmodemd. Unpack
under Linux with:
$ tar zxf SLMODEMD.gcc4.2.tar.gz
and read instructions therein. But briefly, the modem is setup with command:
sudo slmodemd -c YOUR_COUNTRY --alsa modem:1
reporting dynamic creation of ports:
/dev/ttySL0 --> /dev/pts/N , with N some number
Read DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow
through guidance
If possible, do the modem diagnostics under Microsoft, and copy us the
ATI output responses. SoftModem.txt has details.
MarvS
scanModem maintainer
On Fri, Aug 8, 2008 at 5:42 AM, Ashley Richley
<a.a.richley@xxxxxxxxxxxxx> wrote:
> Hi all,
>
> I am a very basic linux user and am trying to adapt my knowledge from just
> windows products into linux. Basically I have an install of ubuntu that I
> set up and am now trying to install and configure the dial up modem. I have
> followed the instructions on the beginner page and have go to the point
> where it tells me to submit ModemData.txt to the discussion board. So below
> is the file contents.
>
> ============================================================================
> ===========================
>
> Only plain text email is forwarded by the Discuss@xxxxxxxxxxxxx List
> Server,
> as HTML can contain viruses. Use as the email Subject Line:
> YourName, YourCountry kernel 2.6.24-19-generic
> With this Subject Line cogent experts will be alerted, and useful case
> names left in the Archive.
> YourCountry will enable Country specific guidance. Linux experts in
> YourCountry
> can be found through: http://www.linux.org/groups/index.html.
> They will know your Country's modem code, which may be essential for dialup
> service.
> Responses from Discuss@xxxxxxxxxxxxx are sometimes blocked by an Internet
> Provider mail filters.
> So in a day, also check the Archived responses at http://www.linmodems.org
> -------------------------- System information ----------------------------
> CPU=i686,
> Linux version 2.6.24-19-generic (buildd@terranova) (gcc version 4.2.3
> (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Fri Jul 11 23:41:49 UTC 2008
> scanModem update of: 2008_07_31
>
> There are no blacklisted modem drivers in /etc/modprobe* files
> USB modems not recognized
>
> For candidate card in slot 00:06.1, firmware information and bootup
> diagnostics are:
> PCI slot PCI ID SubsystemID Name
> ---------- --------- --------- --------------
> 00:06.1 10de:00d9 103c:006d Modem: nVidia Corporation
> nForce3 Audio
>
> Modem interrupt assignment and sharing:
> 18: 0 IO-APIC-fasteoi ehci_hcd:usb3
> --- Bootup diagnostics for card in PCI slot 00:06.1 ----
> [ 16.245924] ACPI: PCI Interrupt 0000:00:06.1[B] -> Link [LMCI] -> GSI 22
> (level, low) -> IRQ 18
> [ 16.245939] ACPI: PCI interrupt for device 0000:00:06.1 disabled
>
> The PCI slot 00:06.1 of the modem card may be disabled early in
> a bootup process, but then enabled later. If modem drivers load
> but the modem is not responsive, read DOCs/Bootup.txt about possible
> fixes.
> Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx
> if help is needed.
>
> ============================================================================
> ===========================
>
> Can someone please point me in the right direction from here?
>
> Thankyou in advance
>
> Ash
>
>
