Re: Intel 537EP - driver loads but cannot use modem

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

 



Chris,

It seems to me that this Modem is not really an Intel 537 Modem, but
one disguised as one.  Here's another user having difficulties:

http://ubuntuforums.org/showthread.php?t=1183881

I run scanModem fake the PCI IDS you have sent and it reports Intel 537:

=== Finished firmware and bootup diagnostics, next deducing cogent software. ===

Predictive  diagnostics for card in bus fake:
        Modem chipset  detected on
NAME="FakeName"
CLASS=FakeClass
PCIDEV=8086:1080
SUBSYS=1028:1000
IRQ=fake
IDENT=INTEL537EP

 For candidate modem in:  fake
   FakeClass FakeName
      Primary device ID:  8086:1080
 Support type needed or chipset:        INTEL537EP



 Since 2006, Intel appears to have ceased its modem code updates for Linux.
 The outdated official Intel support packages can be accessed through:
       http://developer.intel.com/design/modems/support/drivers.htm
 Beneficially, Philippe Vouters has been provided updates as the Linux
kernel evolves.
 But intensive personal support is not feasible, see:
http://archives.linmodems.org/24939
 The code for the INTEL537 and INTEL536 chipset modems is now at:
      http://vouters.dyndns.org/Intel/ , previously http://x9000.fr
Copies are also stored at:
       http://linmodems.technion.ac.il/packages/intel/Philippe.Vouters/
For Ubuntu Linux users with Intel 536 and 537 chipsets, there are driver
installation packages available thru
http://groups.google.com/group/ubuntu-modems

 Read DOCs/Intel.txt and Modem/DOCs/YourSystem.txt for follow through guidance.

Which is a bit different from what you have sent:

NAME="Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax Modem PCI "

When I see "FA82537EP 56K ", I have seen reports that sadly this modem
is unsupported.  Marv and/or Phillppe can confirm this, hope that they
can let you know if this is sadly true.

Regards,

Antonio

On 3/7/10, Chris Tracy <chris.t.tracy@xxxxxxxxx> wrote:
> Hi everybody,
>
> I am hoping that somebody might be able to offer some advice on the
> problems I am having with my Intel 537EP modem.  PCI device ID is
> 8086:1080.  Output of scanout.01:00.0 is below.
>
> Please note that this modem came out of a Dell system -- I am not sure
> if that matters, but the lspci output does pick up on this:
>
> $ lspci -vvv | grep -A 1 537
> 01:00.0 Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax Modem PCI
> (rev 04) (prog-if 00 [Generic])
>         Subsystem: Dell Unknown device 1000
>
> The system is running Debian lenny/sid with a vanilla kernel (2.6.24.7
> from kernel.org).  I've managed to get the Intel537 driver compiled
> and loaded:
>
> $ lsmod | grep 537
> Intel537             4316324  1
>
> However, the modem does not work when I load up minicom or kermit,
> point it to /dev/modem (or /dev/537ep) and type 'ATZ'.  kermit
> actually gives me a backtrace whenever I try to do anything with that
> device...(see below).
>
> I ran the latest 'scanModem' and the problem seems to be related to
> this:
> ACPI: PCI interrupt for device 0000:01:00.0 disabled
>
> This message appears in dmesg _after_ the Intel537 driver loads.  For
> example:
>
> ===
> $ egrep -e "(537ep|01:00.0)" dmesg.txt
> ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 17 (level, low) -> IRQ 20
> ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 17 (level, low) -> IRQ 20
> 0000:01:00.0: ttyS5 at I/O 0xa008 (irq = 20) is a 16450
> 0000:01:00.0: ttyS6 at I/O 0xa010 (irq = 20) is a 8250
> 0000:01:00.0: ttyS7 at I/O 0xa018 (irq = 20) is a 16450
> 0000:01:00.0: ttyS8 at I/O 0xa020 (irq = 20) is a 8250
> 0000:01:00.0: ttyS9 at I/O 0xa028 (irq = 20) is a 8250
> 537ep:softcore_init_struct: driver serial already allocated device.
> 537ep:softcore_init_struct: Unregistering serial driver.
> ACPI: PCI interrupt for device 0000:01:00.0 disabled
> ===
>
> As suggested in Bootup.txt, I've tried adding "pci=routeirq", which
> didn't help. Tried "pollirq", that didn't help either.  The BIOS on my
> system (SuperMicro SuperServer 5013G-M motherboard) doesn't have an
> option to turn PNP on/off.  This is a 1U box, so I am somewhat
> restricted to which slot I can use...(I could remove the cover and PCI
> riser card and try some other slots, but would not be able to put the
> top back on...)  I've also tried booting with/without
> '8250.nr_uarts=10', but I think that would only matter if I was using
> the native serial driver...(which is being unloaded when I load the
> Intel537, if I understand correctly...)
>
> I haven't tried other kernel versions...if I should, any
> recommendations on a specific version...?
>
> Here is the kermit backtrace, in case it helps at all:
> ===
> Feb 27 16:53:46 snoopy kernel: Pid: 4839, comm: kermit Not tainted
> (2.6.24.7 #1)
> Feb 27 16:53:46 snoopy kernel: EIP: 0060:[<f90b5549>] EFLAGS:
> 00010283CPU: 0
> Feb 27 16:53:46 snoopy kernel: EIP is at read8+0x19/0x20 [Intel537]
> Feb 27 16:53:46 snoopy kernel: EAX:00000000 EBX: 00000000 ECX:
> f943ffe8 EDX: 00000006
> Feb 27 16:53:46 snoopy kernel: ESI: f9486480 EDI: ffffffed EBP:
> f3e55df8 ESP: f3e55df8
> Feb 27 16:53:46 snoopy kernel:  DS: 007b ES: 007b FS: 00d8 GS: 0033
> SS: 0068
> Feb 27 16:53:46 snoopy kernel: Process kermit (pid: 4839, ti=f3e54000
> task=f7c4a070 task.ti=f3e54000)
> Feb 27 16:53:46 snoopy kernel: Stack: f3e55e28 f90b3a80 f9486480
> 00000006f3e55e28 f90b3e27 f3e55e88 00000000
> Feb 27 16:53:46 snoopy kernel:        f94889e0 f943ffd8 f74d6680
> ffffffed f3e55e78 f90b2a73 f9486480 f76c400c
> Feb 27 16:53:46 snoopy kernel:        f76c400c f3e55e60 f3ea0000
> f3e55e58 f3e98000 c021d888 c031facb 00000011
> Feb 27 16:53:46 snoopy kernel: Call Trace:
> Feb 27 16:53:46 snoopy kernel:  [<f90b3a80>] si3052Init+0x40/0x370
> [Intel537]
> Feb 27 16:53:46 snoopy kernel:  [<f90b3e27>] si3052Res+0x37/0x90
> [Intel537]
> Feb 27 16:53:46 snoopy kernel:  [<f90b2a73>] afe_init+0x123/0x1a0
> [Intel537]
> Feb 27 16:53:46 snoopy kernel:  [<c021d888>] acpi_pci_irq_enable
> +0x1f5/0x201
> Feb 27 16:53:46 snoopy kernel:  [<f90b095d>] modem_init+0x12d/0x1a0
> [Intel537]
> Feb 27 16:53:46 snoopy kernel:  [<f90ad6fc>] open+0xac/0x170 [Intel537]
> Feb 27 16:53:46 snoopy kernel:  [<f90b037e>] softserial_open+0x12e/
> 0x150 [Intel537]
> Feb 27 16:53:46 snoopy kernel:  [<c022abac>] tty_open+0x18c/0x299
> Feb 27 16:53:46 snoopy kernel:  [<c017bd9d>] chrdev_open+0x122/0x13d
> Feb 27 16:53:46 snoopy kernel:  [<c017bc7b>] chrdev_open+0x0/0x13d
> Feb 27 16:53:46 snoopy kernel:  [<c0177ee7>] __dentry_open+0xce/0x185
> Feb 27 16:53:46 snoopy kernel:  [<c0178018>] nameidata_to_filp+0x24/0x33
> Feb 27 16:53:46 snoopy kernel:  [<c0178059>] do_filp_open+0x32/0x39
> Feb 27 16:53:46 snoopy kernel:  [<c0177db0>] get_unused_fd_flags
> +0x54/0xb6
> Feb 27 16:53:46 snoopy kernel:  [<c01780a4>] do_sys_open+0x44/0xc4
> Feb 27 16:53:46 snoopy kernel:  [<c017815d>] sys_open+0x1c/0x1e
> Feb 27 16:53:46 snoopy kernel:  [<c0103ed2>] sysenter_past_esp+0x6b/0xa1
> Feb 27 16:53:46 snoopy kernel:  =======================
> Feb 27 16:53:46 snoopy kernel: Code: fc b801 00 00 00 89 ec 5d c3 90
> 8d b4 26 00 00 00 00 55 89 e5 8b 55 0c 31 c0 83 fa 64 77 10 8b 45 08
> 8b 40 0c 8b 80 8c 00 00 00 <0f> b6 04 02 5d c3 90 55 89 e5 8b 55 08 8b
> 45 0c 8b 52 0c 8b 8a
> Feb 27 16:53:46 snoopy kernel: EIP: [<f90b5549>] read8+0x19/0x20
> [Intel537] SS:ESP 0068:f3e55df8
> Feb 27 16:53:46 snoopy kernel: ---[ end trace bde7999b84603aa7 ]---
> ===
>
> ===
> # cat scanout.01\:00.0
> CLASS=0703
> NAME="Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax Modem PCI "
> PCIDEV=8086:1080
> SUBSYS=1028:1000
> IRQ=20
> CodecDiagnosed=
> slamrTest=
> CodecClass=
> IDENT=INTEL537EP
> SLMODEMD_DEVICE=
> OPTS=
> Driver=
> ===
>
> Thanks!
> -Chris
>

[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux