Daniel RE: the scanout.00:04.0 file. Is that on purpouse? Yes! Sometimes there are multiple candidates for a modem card, or multiple modem cards. One system had three different modems installed. In addition, the increasingly popular High Definition Audio cards which may/maynot host a modem. Results for each candidate are stored in files with name convention: scanout.PCIbusAddress scanModem has evolved a few functional stages, to cope with the multi-candidate complexities: 1) Analysing features which are not tightly coupled to a particular PCIbusAddress, including information in /proc/asound/ cogent to ALSA supported modems. 2) Identifying and listing candidate modem cards, by their PCIbusAddress 3) For each PCIbusAddress in the list, checking the bootup diagnostics. 4) For each PCIbusAddress in the list, running PCIbusAddress/modem_card specific analyses with results written to a scanout.PCIbusAddress file in the format: Feature=SomeValue 5) Reading each scanout.PCIbusAddress file and outputting the guidance cogent to it. The separation of 4) & 5) (which were initially combined) GREATLY simplified the code structure and its maintenance 6) Final advice, such as completeing compiling support, which is .PCIbusAddress independent. MarvS In a first stage, scanModem does diagnostics and writes a scanout.PCIbusAddress file for each candidate card. The PCIbusAddress like 00:04.0 is just a convenient label to distinguish the scanout.* files representing the distinct cards. In a 2nd stage, scanModem reads each scanout.* card and outputs appropriate guidance in turn. On Jan 10, 2008 8:30 AM, Daniel Victoria <daniel.victoria@xxxxxxxxx> wrote: > Apparently it's doing the same stuff, I mean, I don't see any > difference. I'm still getting the scanout.00:04.0 file. Is that on > purpouse? > > ModemData.txt is attached > > > > On Jan 10, 2008 11:23 AM, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: > > More fixes in scanModem > > > > > > > > On Jan 10, 2008 8:00 AM, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: > > > Jacques > > > > > > Another update > > > > > > Dan, > > > The attached will fix your particular problem > > > PCIBUS= > > > Please test. > > > > > > If there is a failure or warning messages, > > > also send me the DV3.txt from > > > $ bash -x ./scanModem 2>&1 | tee DV3.txt > > > > > > MarvS > > > > > > > > > > > > On Jan 10, 2008 6:29 AM, Daniel Victoria <daniel.victoria@xxxxxxxxx> wrote: > > > > MarvS, > > > > > > > > There must be some grep error in the script. A bunch of grep usage > > > > messages pops up and a file named scanout. gets written. Also a > > > > previous version sent by Jacques would output a file named > > > > SmartLink.txt and your version does not. Did you see the version > > > > Jacques sent, with an URGENT update? > > > > > > > > The ModemData.txt is attached > > > > > > > > > > > > Cheers > > > > Daniel > > > > > > > > > > > > On Jan 9, 2008 11:26 PM, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: > > > > > OK fixes the space error > > > > > Please run scanModem and send me the ModemData.txt again > > > > > > > > > > Mario > > > > > Send me the ALSAmario.tgz (or similar) file also. > > > > > > > > > > MarvS > > > > > > > > > > > > > > >
