Hi Philippe,
Below is the output of lspci (Both modems are there.)
It looks like the 537 is the same model as the one below, so we'll see
where it goes (the driver builds and loads, detecting the board, but
same behaviour as before) I'm almost certain its an IRQ issue now - I
will do some research, and see where it goes. If I don't have time
during the week, then this coming weekend for sure. Thanks for all your
help so far.
Best,
Bjorn.
05:00.0 Communication controller [0780]: Intel Corporation 536EP Data
Fax Modem [8086:1040]
Subsystem: Intel Corporation Device [8086:1000]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 11
Region 0: Memory at fe800000 (32-bit, non-prefetchable) [size=4M]
Capabilities: [e0] Power Management version 2
Flags: PMEClk- DSI- D1- D2+ AuxCurrent=375mA
PME(D0-,D1-,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
05:02.0 Modem [0703]: Intel Corporation FA82537EP 56K V.92 Data/Fax
Modem PCI [8086:1080] (rev 04) (prog-if 00 [Generic])
Subsystem: Dell Device [1028:1000]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping+ SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64 (250ns min, 15500ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 18
Region 0: Memory at fe7ff000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at e800 [size=256]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: serial
Philippe Vouters wrote:
> Dear Bjorn,
>
> Before testing the driver with a 537 family modem, would you please
> check the output of the corresponding $ lspci -nn -vvvv. This is
> currently tested (looks successful) with:
>
> 01:01.0 Modem [0703]: Intel Corporation FA82537EP 56K V.92 Data/Fax
> Modem
> PCI [8086:1080] (rev 04)
> Subsystem: Dell Device [1028:1000]
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr-
> Stepping+ SERR+ FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort-
> <MAbort- >SERR- <PERR- INTx-
> Latency: 64 (250ns min, 15500ns max), Cache Line Size: 64 bytes
> Interrupt: pin A routed to IRQ 22
> Region 0: Memory at feafe000 (32-bit, non-prefetchable) [size=4K]
> Region 1: I/O ports at de00 [size=256]
> Capabilities: <access denied>
> Kernel driver in use: serial
>
> This person is running Linux kernel 2.6.28 and has still a NO DIALTONE
> issue with wvdial. I think this is caused because he set +FCLASS=0
> (Class 1 modem that the 536EP modem belongs to whereas he owns a 537EP
> modem which belongs to Class 2). My today's suggestion to him was to set
> +FCLASS=2 in his modem initialisation AT strings.
>
> I have another issue with a Silicon 537 [Winmodem] modem owner in India.
> The correct driver used to be the SM56K driver but this Winmodem driver
> has only worked under Fedora Core 1 (2.4 kernel) and could not follow
> the kernel upgrades. As efax is correctly responding the third time, I
> am still in the hope I can find a solution using the 537 driver for him.
> However making the 537 driver work with such a modem board will require
> very hard work.
>
> Yours sincerely,
> -
> http://vouters.dyndns.org:8080/
> Philippe Vouters (Fontainebleau/France)
>
>
> Le lundi 06 juillet 2009 à 19:12 -0300, Bjorn Wielens a écrit :
>> Okay, it does seem to be an IRQ conflict. After booting, lspci reports
>> the modem with IRQ 5 (by itself).
>> However, after the first use attempt, this changes to 18, which is
>> shared with 3 USB controllers and an SMBUS controller.
>> I'll try a different PCI slot tomorrow and report what happens- I've
>> already tried some kernel parameters, but it doesn't seem to have any
>> effect.
>> BTW Philippe, I can get access to a 537 modem - I can also test those
>> drivers for you.
>> Best,
>> Bjorn.
>>
>> Philippe Vouters wrote:
>>> Dear Bjorn,
>>>
>>> Read carefully this
>>> http://www.kernel.org/pub/linux/kernel/people/gregkh/lkn/lkn_pdf/ch09.pdf
>>> document. Setting appropriate kernel boot parameters may eventually help
>>> you workaround IRQ conflicts issues.
>>>
>>> Yours sincerely,
>>> -
>>> http://vouters.dyndns.org:8080/
>>> Philippe Vouters (Fontainebleau/France)
>>>
>>>
>>> Le lundi 06 juillet 2009 à 03:14 -0700, Bjorn Wielens a écrit :
>>>> Hi,
>>>> Thanks for the replies.
>>>> I was already using the latest driver (July 4th/09). I'll try your tips and do a few tests, then report back. An IRQ issue seems logical, considering other problems I've had.
>>>> Best,
>>>> Bjorn.
>>>>
>>>> --- On Mon, 7/6/09, Philippe Vouters <Philippe.Vouters@xxxxxxxxxxx> wrote:
>>>>
>>>>> From: Philippe Vouters <Philippe.Vouters@xxxxxxxxxxx>
>>>>> Subject: Re: 536ep Slow to respond, openSuSE 11.1
>>>>> To: "Bjorn Wielens" <Uniacke1@xxxxxxxx>
>>>>> Cc: "Antonio Olivares" <olivares14031@xxxxxxxxx>, "Linmodems" <discuss@xxxxxxxxxxxxx>
>>>>> Received: Monday, July 6, 2009, 4:22 AM
>>>>> Dear Bjorn,
>>>>>
>>>>> I know of three magic commands which entirely fitted my
>>>>> case and which
>>>>> may eventually apply to yours :
>>>>> $ lscpi -vvv | grep IRQ
>>>>> $ sudo cat /proc/interrupts
>>>>> $ dmesg | grep IRQ
>>>>> Do you eventually notice IRQ conflicts ?
>>>>>
>>>>> To forward support you, would be please be so kind as to
>>>>> download the
>>>>> latest 536EP/537EP driver and efax.zip from my Web site
>>>>> (URL below) ?
>>>>> Carefully read the Intel-Readme.html.
>>>>> With efax you have to:
>>>>> $ unzip -aa efax
>>>>> $ cd efax
>>>>> $ make -f Makefile.orig
>>>>> and you run the just built efax with ./efax
>>>>>
>>>>> Yours sincerely,
>>>>> -
>>>>> http://vouters.dyndns.org:8080/
>>>>> Philippe Vouters (Fontainebleau/France)
>>>>>
>>>>>
>>>>> Le dimanche 05 juillet 2009 à 20:41 -0300, Bjorn Wielens a
>>>>> écrit :
>>>>>> I have an Intel 536EP modem that I'm trying to get
>>>>> working.
>>>>>> The drivers load, and work fine, but the modem is
>>>>> behaving strangely- it
>>>>>> is very slow to respond to commands. For example, when
>>>>> using wvdial, it
>>>>>> will 'hang' at 'Sending ATZ' for a good 5 seconds
>>>>> before continuing on.
>>>>>> It will then proceed to dial, but there will be other
>>>>> problems, such as
>>>>>> refusing to disconnect, and the modem then being
>>>>> unable to dial out
>>>>>> anymore for that boot.
>>>>>>
>>>>>> While the modem does work partially, wvdial does not
>>>>> detect it.
>>>>>> I also cannot find any sort of errors in the dmesg
>>>>> output.
>>>>>> As a result, vgetty does not work either, giving a
>>>>> 'timeout while
>>>>>> reading char from modem'.
>>>>>> I would really like to get the voice function going-
>>>>> lately we've been
>>>>>> swamped with fake credit card telemarketing scams... I
>>>>> thought I'd have
>>>>>> the modem play the 'disconnected line' tone when the
>>>>> telemarketers call.
>>>>>> Thougts/help appreciated.
>>>>>>
>>>>>> Bjorn.
>>>>>>
>>>>>
>>>> __________________________________________________________________
>>>> Connect with friends from any web browser - no download required. Try the new Yahoo! Canada Messenger for the Web BETA at http://ca.messenger.yahoo.com/webmessengerpromo.php
>>>>
>>>
>>>
>
>
>
Attachment:
signature.asc
Description: OpenPGP digital signature
