Latest changes

• as many GPL parts as required have been included :
  • pid / vid
  • firmware
• reading CMV file should work (not yet fully tested)
  • enable-cmvs option at configure to compile it
  • edit the file /etc/eagle-usb/CMVep.txt with good values and put Linetype=0000000A in /etc/eagle-usb/eagle-usb.conf
• we did not include latest bnm (waiting for formal approval of ADI / Sagem to distribute them freely in order to do regression testing for other types of modem). See questions below...
  • just copy the bnm in the appropriate directory before compiling the driver
  • the OPTNxx values should be compatible with the Fast 800 E3. See questions below...

Access to cvs

• to download from cvs (in GNU/Linux) : cvs -d:pserver:anonymous@cvs.gna.org:/cvs/eagleusb co eagleusb # press enter as you are logging as anonymous
• to browse cvs changes : http://cvs.gna.org/viewcvs/eagleusb/eagleusb/
• Changelog : see TestEagleUs and https://mail.gna.org/public/eagleusb-cvs/

Making it work

• download eagle-usb-2.0.0
• copy the bnm files in eagle-usb-2.0.0/driver/user/pots/ (already done in versions post-rc2 20041024, not yet done in CVS)
• cd eagle-usb-2.0.0
• ./autogen.sh # can be necessary for cvs versions in order to create the Makefile
• ./configure --enable-cmvs # will compile CMV file support (verify with ./configure -h for all options)
• cd driver ; USE_CMVS=1 make ; cd .. # until sl33p3r automates it (done 20041017, now USE_CMVS is not necessary any more see Changelog)
• make
• make install
• eagleconfig
• startadsl

• that eagle-usb.conf contains the new values (a file /etc/eagle-usb/scripts/eagle-usb.conf.template may have been created)
• change value for Linetype if necessary from 1 to A
• check the file /etc/eagle-usb/CMVep.txt (you may have to create it)
• please report problems on the public ML eagleusb-dev at gna dot org either in English or French, public archive available
• provide the result of eaglediag -msc and interesting lines from /var/log/messages
• latest known errors are available on FeedBack200

Organizational questions

• are all current eagle-usb's functionalities suficient ? Which functionality would be compulsory / nice to add ? (questions welcome)
• Can we freely distribute BNM files ? which licence ? (GPL would be a natural choice)
  • Why does not ADI provide the sourcecode for BNM/firmware ? There could be plenty of reasons, some of them could be trivial to resolve.

Technical questions

• in Spain there are at least two kinds of ISP, do the CMV for Spain work for both ?
  • Telefonica based : using IPoA (RFC 1483 bridge LLCsnap) or PPPoE LLC (RFC2516)
  • "Wanadoo/Eresmas" based : same configuration as in France (PPPoA VCmux)
• does it exist a "default configuration" that works in every country / for every ISP ?
• how will be informed of appropriate configuration when today it's already very difficult to obtain VPI / VCI / Encapsulation for every ISP... Is it depending only on the country or the ISP or the DSLAM ?
• Could we have a list in extenso of CMV options that can be modified and their meaning ? It would be great to understand what each option depends on (throughput, type of DSLAM, ...)
• Is it possible to send commands interactively to the modem once "modem is operationnal" ? Which ones ?
  • for example, could we get the DSPcode version even after modem synchronized ?
  • we are missing a functionality to "restart the modem when in unstable state" : Initializing, Booting. This would permit to get back to a known state avoiding to unplug / replug the modem (which is the only way to do it currently)
  • could we change VPI / VCI "on the fly" and force new synchronization ?
  • if bad CMV have been sent, is it possible to send new ones to replace the erroneous ones ?
  • I hope ADI can tell us some of these features are already available ;-)
• The windows driver (http://castet.matthieu.free.fr/eagle/win.log) send SET2183DATA 000049c3 command (control packet, Value=4,index=49c3) : is it usefull and what does it mean ?
• Is there a way to realy know that the modem is hang : sometimes the modem act like everything is ok, it receive paquet from internet, but everything you send to modem seem dropped. It like there is the LOOPBACK activated only on send mailbox. It's doesn't happen at the first boot but more often after unloading/lodaing the module et rebooting the modem several times.

• Why the bulk mode produce lot's of missing atm cell, and invalid packet (even with the windows driver http://castet.matthieu.free.fr/eagle/stat.png) ? What the meaning of the command SET_TIMEOUT (control packet, value=11,index=1) in bulk mode. Is there a speed limit with bulk mode ? What the recomand setting for usb : number of urb, .... Windows driver use 22 urb of 64*atm_cell Byte.
• Why iso mode produce EILSEQ error (at least on some machine) ?
  • What are the recommended setting for usb. Windows driver use 16 urb of 12 packets and adapt the size with the line speed.

Questions / Answers

Are those BNM backward compatible ?

• yes, they work on modems based on Eagle I, Eagle II, Eagle III

BNM valid on any kind of modem ?

• yes they work, with specific CMV eventually. Previous BNM versions are not compatible with latest modems : it's alway better to use latest BNM

Which CMV values work correctly ?

• list of values provided by country (to be detailed, as some values are ISP specific)
• France, Italy, Spain
• I put everything obtained on page ConfigFiles and began a documentation Faq:InfoCMVEn (interwiki)
  • could we have more details ?

question for ADI : only the following lines are defined for OPTNxx, what should we put for missing values ?

static eu_cmv_msg_t MsgOPTN0 = { PREAMBLE, WRITE_TO_MODEM, 0x1111, 'O','P','T','N', 0, 0x80020066 };
static eu_cmv_msg_t MsgOPTN2 = { PREAMBLE, WRITE_TO_MODEM, 0x2222, 'O','P','T','N', 2, 0 };
static eu_cmv_msg_t MsgOPTN4 = { PREAMBLE, WRITE_TO_MODEM, 0x3333, 'O','P','T','N', 4, 0 };
static eu_cmv_msg_t MsgOPTN7 = { PREAMBLE, WRITE_TO_MODEM, 0x2222, 'O','P','T','N', 7, 0 };
static eu_cmv_msg_t MsgOPTN3 = { PREAMBLE, WRITE_TO_MODEM, 0x2222, 'O','P','T','N', 3, 0 };
static eu_cmv_msg_t MsgOPTN5 = { PREAMBLE, WRITE_TO_MODEM, 0x2222, 'O','P','T','N', 5, 0 };
static eu_cmv_msg_t MsgOPTN6 = { PREAMBLE, WRITE_TO_MODEM, 0x2222, 'O','P','T','N', 6, 0 };
static eu_cmv_msg_t MsgOPTN15 = { PREAMBLE, WRITE_TO_MODEM, 0x2222, 'O','P','T','N',15, 0 };

• confirmed, use 0x2222 => to be implemented
• known bug : only OPTN0 to OPTN15 are taken into account currently in eagle-usb-2.0.0
• see ConfigFiles for discussion of implement values of OPTNxx where xx > 15

Doesn't it exist default CMV values that always work ?

• it's currently identified as depending on country
• to be tested : currently it's ko => depends on ISP

Do CMV work depending on the modem model or only ISP configuration ?

• only ISP configuration
• to be confirmed : may depend on DSLAM ?

EagleUsb III brings some improvements

• is it true or is it a bug in computing the value ? see eaglestat result TestEagleUsbIIIbaud123 (25 dB -> 16 dB), theorical value is 24 dB (at 2035 meters from DSLAM) does it depend on CMV values ? Now I've got 26 dB
• I"ve got less messages "97th threshold" "SM LOS Defect" from the driver in my /var/log/messages => does it mean the modem has better signal / noise ratio resolution ?

a draft version of documentation about CMV : Faq:InfoCMVEn (interwiki)

• wouldn't it be better to have a directive FILEPOTS / FILEISDN in /etc/eagle-usb/eagle-usb.org to indicate which CMV file to use ?
• or eagleconfig can make a symbolic link on the appropriate file (that could be put in /usr/share/eagle-usb... well to be defined to be compliant with LSB, I'm not the specialist in this area)=> symbolic link chosen