Antonio, Thanks for bringing this to my attention. Within the scanModem internal archive, there is an entry in the 11c11040 chipset lone of 1043:1339 However Eric's on PC diagnostic: /proc/asound/card0/codec#1 -------------------------------------------------------- Codec: Motorola Si3054 Address: 1 Vendor Id: 0x10573055 is unquestionable more reliable than the archive. There are now two cases of this conflict type in the archive for Subsystems under the primary PCI ID , 8086:284b of the High Definition Audio (HDA) card. # 17aa:384e assigned to both 10573055 and 11c11040 modem chips # 1043:1339 assigned to both 10573055 and 11c11040 modem chips. ----------- To me this indicates that the HDA card Assembler is primary concerned with a consistent identification of the Audio components, and doesn't care about the more minor modem component. After finishing his batch of modem 10573055 chips, the Assembler likely switched to the newer 11c11040 modem chips. So long as the Audio chip component of the Subsystem was not yet changed, likely Assembler didn't both changing the SubSystem ID The modem chip identifier: Vendor Id: 0x10573055 is read from firmware on the HDA card subsystem , and suffices for calls of the correct software under Microsoft. As Sasha long ago related, the diverse softmodem chips have only minor functionality beyond calling the correct software. It is the called software running on the CPU that does the major work. This is why Sasha's single slmodemd modem helper under Linux is competent for a broad array of softmodem chips, even though under Microsoft each different softmodem chip calls for software from its own manufacturer. I'll write a scanModem subroutine to explicit relate these conflicts in the future. MarvS MarvS On Thu, Aug 7, 2008 at 12:38 AM, Antonio Olivares <olivares14031@xxxxxxxxx> wrote: > Marv, > > Something is fishy here. Now it starts looking like the 11c11040 part > of scanModem was true. > > I ran scanModem with the pci id's of the modem and I got the following: > > Predictive diagnostics for card in bus fake: > Modem chipset detected on > NAME="FakeName" > CLASS=FakeClass > PCIDEV=8086:284b > SUBSYS=1043:1339 > IRQ=fake > HDA=8086:284b > SOFT=8086:284b.HDA > ArchivedChip=0x11c11040 > IDENT=11c11040 > Driver=agrmodem+agrserial > DRIVER=agrmodem+agrserial > > For candidate modem in: fake > FakeClass FakeName > Primary device ID: 8086:284b > Subsystem PCI_id 1043:1339 > Softmodem codec or chipset from diagnostics: > from Archives: 0x11c11040 > > I am not 100% sure here, but I had the same thing happen one time when > I tried the SLMODEMD code with this type of modem(11c11040), > everything seemed correct all was fine. The bad part the looping of > No Carrier, like in your message. > > It is very strange that SLMODEMD.gcc4.tar.gz was serving and then you > updated the kernel and now it does not work. Why can't you change the > default behavior to have at least two working kernels so that you have > something to fall back on. *This should not be the case with > SLMODEMD, but this appears to be a special case* > > Regards, > > Antonio > > > On Wed, Aug 6, 2008 at 10:38 PM, Eric <dragon.wind@xxxxxxxxxxxx> wrote: >> after installing Marvin new slmodemd and >> carring out Antonio instructions >> >> Eric, >> >> You might want to change >> Init string here >> >> Put a "#" in front of the following one >>> Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 >> >> And remove it from here. >>> # Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 >> >> Test out conection. Does it get to connect? >> >> It seems strange that after a kernel upgrade that SLMODEMD does not work >> any more since it is kernel independent. >> >> Regards, >> >> >> Antonio >> >> I still get >> >> [sudo] password for eric: >> --> WvDial: Internet dialer version 1.60 >> --> Cannot get information for serial port. >> --> Initializing modem. >> --> Sending: ATZ >> ATZ >> OK >> --> Sending: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 >> ATQ0 V1 E1 S0=0 X3 &C1 &D2 +MS=90 >> OK >> --> Modem initialized. >> --> Please enter password (or empty password to stop): >> --> Sending: ATDT0198333966 >> --> Waiting for carrier. >> ATDT0198333966 >> NO CARRIER >> --> No Carrier! Trying again. >> --> Sending: ATDT0198333966 >> --> Waiting for carrier. >> ATDT0198333966 >> --> Timed out while dialing. Trying again. >> --> Sending: ATDT0198333966 >> --> Waiting for carrier. >> NO CARRIER >> ATDT0198333966 >> --> No Carrier! Trying again. >> --> Sending: ATDT0198333966 >> --> Waiting for carrier. >> NO CARRIER >> ATDT0198333966 >> --> No Carrier! Trying again. >> --> Sending: ATDT0198333966 >> --> Waiting for carrier. >> NO CARRIER >> ATDT0198333966 >> --> No Carrier! Trying again. >> --> Sending: ATDT0198333966 >> --> Waiting for carrier. >> NO CARRIER >> ATDT0198333966 >> --> No Carrier! Trying again. >> --> Sending: ATDT0198333966 >> --> Waiting for carrier. >> NO CARRIER >> ATDT0198333966 >> --> No Carrier! Trying again. >> --> Sending: ATDT0198333966 >> --> Waiting for carrier. >> NO CARRIER >> ATDT0198333966 >> --> No Carrier! Trying again. >> --> Sending: ATDT0198333966 >> --> Waiting for carrier. >> NO CARRIER >> ATDT0198333966 >> --> No Carrier! Trying again. >> --> Sending: ATDT0198333966 >> --> Waiting for carrier. >> NO CARRIER >> ATDT0198333966 >> --> No Carrier! Trying again. >> --> Sending: ATDT0198333966 >> --> Waiting for carrier. >> NO CARRIER >> ATDT0198333966 >> --> No Carrier! Trying again. >> --> Sending: ATDT0198333966 >> --> Waiting for carrier. >> NO CARRIER >> ATDT0198333966 >> --> No Carrier! Trying again. >> --> Sending: ATDT0198333966 >> --> Waiting for carrier. >> NO CARRIER >> ATDT0198333966 >> --> No Carrier! Trying again. >> --> Sending: ATDT0198333966 >> --> Waiting for carrier. >> NO CARRIER >> ATDT0198333966 >> --> No Carrier! Trying again. >> --> Sending: ATDT0198333966 >> --> Waiting for carrier. >> NO CARRIER >> ATDT0198333966 >> --> No Carrier! Trying again. >> --> Sending: ATDT0198333966 >> --> Waiting for carrier. >> NO CARRIER >> ATDT0198333966 >> --> No Carrier! Trying again. >> --> Sending: ATDT0198333966 >> --> Waiting for carrier. >> NO CARRIER >> ATDT0198333966 >> --> No Carrier! Trying again. >> --> Sending: ATDT0198333966 >> --> Waiting for carrier. >> NO CARRIER >> ATDT0198333966 >> --> No Carrier! Trying again. >> --> Sending: ATDT0198333966 >> --> Waiting for carrier. >> NO CARRIER >> ATDT0198333966 >> --> No Carrier! Trying again. >> --> Sending: ATDT0198333966 >> --> Waiting for carrier. >> NO CARRIER >> ATDT0198333966 >> --> No Carrier! Trying again. >> Caught signal 2: Attempting to exit gracefully... >> --> Disconnecting at Thu Aug 7 13:21:14 2008 >> >> On Wed, 2008-08-06 at 20:48 -0400, Marvin Stodolsky wrote: >>> Try replacing your slmodemd with the attached >>> >>> >> >> >> >> >
