Chris, After objdump'ing intel-536-537/coredrv/537core.lib on my Linux, it ought to appear the code is all there ready to work correctly for your board. The only matter which I am concerned with is if your PCI bus fulfills the hardware limitation of the chip I mentioned in both my mails to you AND my Intel-Readme. If you look carefully at your board, it should contain such a component. -- sip:Vouters.Philippe@xxxxxxxxx IM: philvout (Yahoo!) http://vouters.dyndns.org/ Philippe Vouters (Fontainebleau/France) -------- Message initial -------- De: Chris Tracy <chris.t.tracy@xxxxxxxxx> À: Bjorn Wielens <Uniacke1@xxxxxxxx> Cc: Philippe Vouters <Philippe.Vouters@xxxxxxxxxxx>, Antonio Olivares <olivares14031@xxxxxxxxx>, discuss@xxxxxxxxxxxxx, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> Sujet: Re: Intel 537EP - driver loads but cannot use modem Date: Mon, 8 Mar 2010 11:38:00 -0500 Bjorn, Good question -- the board in question that I am dealing with does indeed say "537EPG" on it, not "537EP". -Chris On Mar 7, 2010, at 3:30 PM, Bjorn Wielens wrote: > I wonder if this is the same issue I ran in to last year when I picked > up such a modem... > Also identified as a 537, but the board itself was from a Dell system, > and branded "537EPG". > > Chris, can you examine the back of your board? Does it say "537EP" or > "537EPG"? > > If there are distinguishing marks, it will at least be easier to > determine whether this is a hardware or a software limitation. > > Bjorn. > > > On 03/07/2010 04:11 PM, Philippe Vouters wrote: >> >> Antonio, >> >>> From intel-536-537/makefile_537, PCIDEV=8086:1080 well corresponds to a >> 537EP modem absolutely handled by the >> http://vouters.dyndns.org/Intel/intel-536EP-537EP_2010_01_06.tar.bz2 >> What brings an uncertainty between 536EP and 537SP is PCIDEV=8086:1040 >> >> Now Chris is facing a problem with his 537EP modem in modem_init (see >> kernel stack trace). >> >> There is not much I can do to help as the code involved resides in >> 537_core.lib which has always been Intel's proprietary code and shipped >> in binary format. This is all the problem with Winmodems. >> >> Regards, >
