Hi Ben, you wrote: > Here is a maintenance version of eagle-usb named eagle-usb-2.3.2 that > brings :
Congratulations and thanks! I was going to suggest you post an announcement on freshmeat.net, but just saw that the entry has been updated. But why on earth was 2.3.1 announced? ;-))) Because 2.3.2 is not yet available on sf.net? I would also like to share the success story of this driver. Until recently, I used eagleusb-de, the German derivate of this driver, which is now very very outdated. (I think it was based on early 0.9.x eagle-usb.) I had had quite a few instabilities (the line broke down when VMware accessed the network, or when I attached a USB hard drive, only to be revived by a reboot). Going towards kernel 2.6.x, I decided to switch to the newest eagle-usb-2.3.1, and it works like a charm! The modem now synchronizes much faster at boot, and I can't see any of the problems I had seen before. And I don't need any of the German-ized junk from eagleusb-de anyway. (The modem was so very cheap at eBay, that I'm very happy that it's so stable now.) The only problem which remains: The hotplug mechanism doesn't seem to work on 2.6.x, while it's fine on 2.4.x. I need to manually load the module. It's the identical system (Fedora Core 2 plus tidbits), same environment, just booted with a different kernel. I'll post a separate e-mail about this on the list. By the way, I ignored all the fancy Makefile stuff you built into the package and tried to handle it like a standard autotools thing. I built an RPM which obviously _doesn't_ ask for your ISP details. This means you need to manually fix the encapsulation entries and such in the eagle-usb.conf file after installation (or calling eagleconfig). On the other hand, in Fedora, you just use the "system-config-network" GUI, add a new xDSL connection, select the eagle-usb Ethernet device, type in your ISP parameters, and off you go! :-))) Kind regards, Moritz
