Re Luca, I'm still CCing our ML, answers (and identified bugs) in the text Le mercredi 13 octobre 2004 à 20:46 +0200, Luca Sollazzo a écrit : > > -----Messaggio originale----- > > Da: Benoît Audouard [mailto:[EMAIL PROTECTED] > > Hi TailGunner, > > I cc our mailing-list, for information (see attached mail), > > Anyone interested in IPv6 ? > > Have a look at > > http://dev.eagle-usb.org/wakka.php?wiki=TailGunner > > patch from Robert Siemer works well once again. > > > ... and attached mail? :) it is below (well ok, not really attached :-? )as shown on the archive : https://mail.gna.org/public/eagleusb-dev/2004-10/msg00169.html
> if you want, i can explain more in > detail the steps to set up the ipv6.... (now it works very > fine :) ) That would be kind of you, so that I know how to plug my fridge on my LAN ;-) You may create a page on the FaqEagle : http://faq.eagle-usb.org (as you did last time : login with ParametresUtilisateurs as this is another wiki) For example create the new pa clicking : http://faq.eagle-usb.org/wakka.php?wiki=InstallationIPv6 do not hesitate to add URL to useful articles to you (even if they are in italian). It's always interesting to have a real example. > > With eagle-usb-2.0.0, it seems we'll have to > > determine which values of > > OPTNxx work better in Italy (for example). This is > > not really a problem, > > as it's only configuration in a text file > > (/etc/eagle-usb/eagle-usb.conf)... > > A new feature for eagleconfig ;-) (in 2.0.1...) > > we'll try to document it for the time being... > > see http://dev.eagle-usb.org/wakka.php?wiki=ConfigFiles > > and this thread : > > http://forum.eagle-usb.org/viewtopic.php?t=2617&high > > light=optn2 > > to verify that it corresponds to the values you have in > > /etc/eagle-usb/eagle-usb.conf with BNM files from 2.0.31 > sagem driver. > > BTW it seems I made a big mistake in the CVS version by > adding this OPTN1 > > (this has already been reported) :-( (patch necessary for > Mandrake...) > > I've done more tests about that (see my page on wiki) [quote]mmmh i've reinstalled cvs version after renaming /etc/eagle-usb directory...... and now all works (with new bnm files....) now i don't know why, but i think that the cvs installation didn't overwrote the existing eagle-usb.conf file (?????)[/quote] you are right, that's a problem I identified, but we did not implement it : - before make install : mv /etc/eagle-usb/eagle-usb.conf /etc/eagle-usb/eagle-usb.conf.old20041013 - the problem is that it's not easy to see that it is a change of version requiring change to eagle-usb.conf and we do not want to overwrite it (in case the user has changed values by him/herself) That would be the work of packaging to change this (for example for rpm : a .rpmnew is created and etc-update enables the user to change it manually... quite awkward but no better idea till now...) - make uninstall keeps the config files as the user may want to keep them (I do not the option of make to erase them, Tux ??) [quote]Now i'm testing for dsp autoload, when i unplug-replug the modem, hotplug doesn't load automatically the dspcode, and i must send eaglectrl -d command.... the automatic connection at startup ("service" eagle-usb) also don't work and now i want to see if it depend by hotplug, (my system) or by script....[/quote] ah ?! we may have broken the "service" eagle-usb on Mandrake... (in 10.1 a "network service" is used...). I really do not remember what Tux did to this... perhaps the fact that now /etc/hotplug/usb.usermap does not contain any more pid/vid ??? (I'm not sure we had documented this part... usual answer : maybe in the code of previous version :-? ... sorry) > and now > the new dspcode works... i leaved eagle-usb.conf as is in the > cvs tree, (OPTN1=00000994) just for a try... and no > problem..... ah ?! so it may depend on the modem or the ISP : some users have had their download throughput divided by 10 with this option... > but... when i send eaglectrl -d i receive output > > Unknown option on line 27 > Unknown option on line 28 > Unknown option on line 29 > Unknown option on line 30 > Unknown option on line 31 > Unknown option on line 32 > Options successfully sent to driver > > corrensponding to options: > > OPTN18=820200FF > OPTN19=80000000 > OPTN20=11900002 > OPTN70=218280AA > OPTN72=006F06EB > OPTN73=00010060 > > obiouvsly, i don't know what these means..... this is only a warning (Sl33p3r should have written in "warning : Unknown option on line %d" ...) We currently do not know what to send for OPTNxx with xx>15 as Sagem has not yet answered us on this point : maybe only ADI will be able to as sl33p3r told me he did not find it in their new driver see Ben'. aka baud123
