Hi,
I'm trying to get a BT voyager 105 working with a current etch install.
I have previously had this working easily with an earlier verison of etch,
but I seem to be banging my head against it right now :-(
I've modified /lib/udev/eciadsl to log profusely as follows:
--- eciadsl.dist 2006-01-03 22:55:05.000000000 +0000
+++ eciadsl 2006-05-24 14:52:52.000000000 +0100
@@ -10,7 +10,7 @@
SYNC_ATTEMPTS=1
# modem firmware
FIRMWARE_FILE1="/usr/local/lib/eciadsl/firmware00.bin"
-FIRMWARE_FILE2="/usr/local/lib/eciadsl/synch01.bin"
+FIRMWARE_FILE2="/usr/local/lib/eciadsl/synch03.bin"
# a PPP peer to call
PPPD_PEER=""
# an interface to start with ifup
@@ -21,6 +21,11 @@
# no user-serviceable parts below this line
##############################################################################
+
+. /lib/udev/hotplug.functions
+
+mesg "eciadsl $* parent=$PPID ACTION=$ACTION PRODUCT=$PRODUCT SEQNUM=$SEQNUM"
+
case "$ACTION" in
add)
;;
@@ -29,8 +34,6 @@
;;
esac
-. /lib/udev/hotplug.functions
-
if [ ! -e "$FIRMWARE_FILE1" ]; then
mesg "Cannot find $FIRMWARE_FILE1."
exit 1
@@ -62,6 +65,7 @@
if [ "$STAGE" = "stage1" ]; then
# stage 1: try to upload the loader firmware
+ mesg "calling eciadsl-firmware $ECI_LOAD1_OPTIONS 0x$VID 0x$PID 0xFFFF
0xEEEE $FIRMWARE_FILE1"
if ! eciadsl-firmware $ECI_LOAD1_OPTIONS \
0x$VID 0x$PID 0xFFFF 0xEEEE $FIRMWARE_FILE1; then
mesg "Cannot initialize the modem."
@@ -80,6 +84,7 @@
COUNT=1
while [ $COUNT -le "$SYNC_ATTEMPTS" ]; do
RC=0
+ mesg "calling eciadsl-synch $ECI_LOAD2_OPTIONS -alt $IFACE_SYNCH -mc
$MODEM_CHIPSET 0x$VID 0x$PID $FIRMWARE_FILE2"
eciadsl-synch $ECI_LOAD2_OPTIONS -alt $IFACE_SYNCH -mc $MODEM_CHIPSET \
0x$VID 0x$PID $FIRMWARE_FILE2 || RC=$?
[ $RC -eq 0 ] && break
@@ -103,5 +108,7 @@
ifup $NET_IF
fi
+mesg "eciadsl done."
+
exit 0
synch003 is documented as the correct file for this modem on the eciadsl site
and elsewhere.
and switched on the hotplug logging as you advised in this bug.
with those two I see:
May 24 15:57:11 racoon kernel: usb 1-1: new full speed USB device using
uhci_hcd and address 8
May 24 15:57:11 racoon eciadsl[8391]: eciadsl stage2 0 GS7470 parent=8385
ACTION=add PRODUCT= SEQNUM=2249
May 24 15:57:11 racoon eciadsl[8391]: $PRODUCT is not defined! This script
should be run by hotplug.
May 24 15:57:12 racoon eciadsl[8403]: eciadsl stage2 0 GS7470 parent=8396
ACTION=add PRODUCT=1690/215/100 SEQNUM=2250
May 24 15:57:12 racoon eciadsl[8403]: calling eciadsl-synch -alt 0 -mc
GS7470 0x1690 0x215 /usr/local/lib/eciadsl/synch03.bin
May 24 15:57:12 racoon eciadsl[8403]: eciadsl done.
May 24 15:57:12 racoon eciadsl[8422]: eciadsl stage2 0 GS7470 parent=8415
ACTION=add PRODUCT= SEQNUM=2251
May 24 15:57:12 racoon eciadsl[8422]: $PRODUCT is not defined! This script
should be run by hotplug.
and in the hotplug.log
HOTPLUG_TIME='Wed May 24 15:57:11 BST 2006'
SUBSYSTEM=usb
OLDPWD=/
DEVPATH=/devices/pci0000:00/0000:00:07.2/usb1/1-1
ACTION=add
UDEV_LOG=3
UDEVD_EVENT=1
PHYSDEVDRIVER=usb
PHYSDEVBUS=usb
SEQNUM=2249
HOTPLUG_TIME='Wed May 24 15:57:12 BST 2006'
SUBSYSTEM=usb
OLDPWD=/
DEVPATH=/devices/pci0000:00/0000:00:07.2/usb1/1-1/1-1:1.0
ACTION=add
MODALIAS=usb:v1690p0215d0100dcFFdscFFdpFFicFFiscFFipFF
UDEV_LOG=3
UDEVD_EVENT=1
DEVICE=/proc/bus/usb/001/008
INTERFACE=255/255/255
PRODUCT=1690/215/100
TYPE=255/255/255
PHYSDEVBUS=usb
SEQNUM=2250
HOTPLUG_TIME='Wed May 24 15:57:12 BST 2006'
PHYSDEVPATH=/devices/pci0000:00/0000:00:07.2/usb1/1-1
SUBSYSTEM=usb_device
OLDPWD=/
DEVPATH=/class/usb_device/usbdev1.8
MINOR=7
ACTION=add
UDEV_LOG=3
MAJOR=189
UDEVD_EVENT=1
DEVNAME=/dev/bus/usb/001/008
PHYSDEVDRIVER=usb
PHYSDEVBUS=usb
SEQNUM=2251
Aside from that this may help to clarify what is going on with $PRODUCT,
the main thing that jumps out at me is the lack of a stage1 call.
Does stage1 come before stage2 ???
I have also tried loading the firmware from the command line with what I
hope to be the correct commands:
racoon:~# eciadsl-firmware -v 0x1690 0x0215 0xFFFF 0xEEEE
/usr/local/lib/eciadsl/firmware00.bin
block 1: addr 0x7f92 - length 1: failed
ERROR eciadsl-firmware: failed
eciadsl-firmware: success
(it seems a little odd that it reports failure and success)
racoon:~# eciadsl-synch -v -alt 0 -mc GS7470 0x1690 0x215
/usr/local/lib/eciadsl/synch03.bin
timeout set to 300sec
RETRY : 1 (until 10)
urb data file : /usr/local/lib/eciadsl/synch03.bin
Block 1: request_type=c0 request=de value=0000 index=0000 size=000d
failed r=-1
ERROR eciadsl-synch SYNCHING: failed
ERROR eciadsl-synch: failed
at some point I saw an error like the EZ-USB one below, and I had a dig
around in the source package, tracking down the line. I'm guessing that
it's not important, but if it is I could find it again.
I have also tried
racoon:~# fxload -vvv -s /usr/share/usb/a3load.hex -I
/usr/local/lib/eciadsl/synch03.bin -D /proc/bus/usb/001/008
microcontroller type: fx
1st stage: load 2nd stage loader
open RAM hexfile image /usr/share/usb/a3load.hex
stop CPU
can't modify CPUCS: Broken pipe
and I've even tried some old image I found lying around:
racoon:~/old_eci# ./eci-load1 --version
ECIADSL USB modem driver (ECIADSL) 0.6 (Feb 7 2003 17:03:27)
racoon:~/old_eci# ./eci-load1 0x1690 0x215 0xFFFF 0xEEEE
/usr/local/lib/eciadsl/firmware00.bin
can't find your EZUSB USB ADSL Loader
ECI load 1: failed
right now I would just like to get this to work, and I'm about to start
throwing other distros at it.
Longer term I'd be keen to see this work and be well supported in debian
as this seems to be the modem used by BT engineers in the UK for testing
lines. The value of this becomes clear in my current situation, where
I am asked to consider a possible modem incompatibility.
You say you have no equipment of this sort? If I were to ship you one,
would that help?
Regards,
Paddy
--
Perl 6 will give you the big knob. -- Larry Wall
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
