Le dimanche 10 octobre 2004 à 19:53 +0200, Didier Spaier a écrit : > Le dim 10/10/2004 à 18:00, baud a écrit : > > Hello, > Hello, > > We are preparing the official release of eagle-usb-2.0.0 > > http://baud123.free.fr/eagle-usb/eagle-usb-2.0.0/ > > Be quick to report problems as I'm preparing the official release on > > main web site and I will be propagating it on sourceforge / gna. > Report for Mandrake 10.0 Official, fast800, kernel 2.6.3-19mdk, Free > dégroupé static > > 1) Installation && eagleconfig OK but I could'nt make as didier, only > as root (see make_didier appended) I had no problem compiling as a normal user : ls -al /usr/src/linux/include/asm-i386/|grep -E "asm|\./" drwxr-xr-x 10 root root 4096 oct 2 23:13 ./ drwxr-xr-x 22 root root 4096 oct 2 23:13 ../ -rw-r--r-- 1 root root 2179 oct 1 12:55 asm_offsets.h
> 2) After first reboot, modem took more time than usual to get > operational yes, that may be caused by new values for OPTNxx, in /etc/eagle-usb/eagle-usb.conf we hope to work with Sagem in order to obtain correct (better) values. I took them from the CMVep.txt file given in 2.0.31 sagem driver and they are quoted in this post : http://forum.eagle-usb.org/viewtopic.php?t=2727 > 3) After following reboots, modem never could get operational ; after > unplug / replug I got bad messages in /var/log/messages (see replug_pb > appended) check files in /etc/eagle-usb/ /etc/eagle-usb/eagle-usb.conf /etc/eagle-usb/scripts/eagle-usb.conf.template do the OPTNxx values differ ? Before running eagleconfig it would be necessary to rename eagle-usb.conf to eagle-usb.conf_20041010 (in order to take newer content of template) Provide result of md5sum /etc/eagle-usb/dsp/*.bin > Oct 10 19:20:28 localhost logger: Wow .. eagle-usb driver should have > transform this in post-firmware... I've already seen this as well : did you unplug a suficiently long time the modem ?? (the usb plug) > 4) Then instead of unplug / replug I issued an eaglectrl -w ; it did'nt > work either (output eaglectrl appended) Which is (exactly) your model ? (Fast 800 AB for me : check last letters of reference at the back) That's normal : 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 Sl33p3r did not implement (yet) reading all OPTNxx (only 16 first from 0 to 15). What is the content of your lines in /etc/eagle-usb/eagle-usb.conf ? Thanks for reporting Ben'. aka baud123
