[speedtouch] Test version available in my arch/tla archive.
Edouard Gomez ([EMAIL PROTECTED]) wrote:
> As promised i'm working on the 330 rev4 support. I've seen some fairly
> complete patches to get this new revision working.
I meant to say, good work boys :-)
> On my side, i've already completed the new firmware extraction
> code/API. For legal reasons i'm going to remove the proprietary data1
> source. I'm also going to provide the free version in a standalone file
> that will install in ${datadir}/speedtouch/boot.v123.bin (sources
> included for the curious people).
I commited these changes to my arch/tla archive, this patch will be
commited to CVS if RFC answers are positive about it. I cannot post a
diff file because this patch renames and adds files, there is no easy
way to export such a patchset to flat diff files from arch/tla atm.
Btw here is the firmware extracter in action:
$ ./firmware_extract /usr/share/speedtouch/firmware.v123.bin
** Boot block from /usr/share/speedtouch/firmware.v123.bin:
CRC: 0xd3e33990
Length: 883
** Firmware block from /usr/share/speedtouch/firmware.v123.bin:
CRC: 0x61914198
Length: 527093
Or with a revision 4 firmware file (lacking the boot block) from
http://www.hystedjp.pwp.blueyonder.co.uk/ (i bookmarked this url during
the rev4 thread ;-):
$ ./firmware_extract 300_ZZZLP2.eni
** Boot block from 300_ZZZLP2.eni:
Not found
** Firmware block from 300_ZZZLP2.eni:
CRC: 0x0223733c
Length: 775509
The changelog entry:
2004-02-15 01:14:13 GMT Edouard Gomez <[EMAIL PROTECTED]> patch-2
Summary:
New firmware extractor API.
Revision:
speedtouch--trunk--1.2--patch-2
* Reworked the complete extracter module. It now checks for both boot
code and main firmware code. It is now possible to specify a separated
boot file code.
* Added firmware_extract rule to build a standalone firmware extracter
to test the firmware extraction utility functions.
* Droped the proprietary boot code and dumped the Ian's free version in a
separate bin/encapsulated file with its associated source.
* Updated/reworked the modem_run's man page.
Here is a log output with ian's boot code concatenated with a windows
driver file:
[modem_run] modem_run version 1.2-beta3 started by root uid 0
[modem_run] Found ALCATEL SpeedTouch USB modem
[modem_run] Best offset 0 with probability 100%
[modem_run] Best offset875 with probability 100%
[modem_run] Firmware information (CRC:0xd3e33990, Size:883, Ian's Free Software
Boot block)
[modem_run] Best offset883 with probability 100%
[modem_run] Best offset 527085 with probability 100%
[modem_run] Firmware information (CRC:0x61914198, Size:527093, 1.4.0 -
Win32(3.0.1800))
Note how boot blocks are now identified just as main firmware block.
new files:
src/boot.v123.S src/boot.v123.bin
modified files:
ChangeLog Makefile.in debian/dirs debian/rules
doc-linux/man/modem_run.1 src/Makefile.in src/firmware.c
src/firmware.h src/modem_run.c
renamed files:
src/extract.c
==> src/firmware.c
src/extract.h
==> src/firmware.h
--
Edouard Gomez
Liste de diffusion modem ALCATEL SpeedTouch USB
Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] [RFC] 330 rev4 support
Hello,
As promised i'm working on the 330 rev4 support. I've seen some fairly
complete patches to get this new revision working.
On my side, i've already completed the new firmware extraction
code/API. For legal reasons i'm going to remove the proprietary data1
source. I'm also going to provide the free version in a standalone file
that will install in ${datadir}/speedtouch/boot.v123.bin (sources
included for the curious people).
So my RFC is about:
How hard is it to identify the boot code from recent
windows/macosx drivers ? Is this a separated file ? or is it still
"merged" with the main part as in old alcaudsl.sys files ?
I ask this, because in the case, boot and main part are separated, the
new modem_run will fail to start unless it is told where the boot block
is. And i wonder if this UI change will cause trouble to users. IMO, i
think it's a sane change.
Btw a simple command like that solves the problem:
$ cat /usr/share/speedtouch/boot.v123.bin ${thomson_main_firmware} > \
/usr/share/speedtouch/firmware.bin
$ modem_run -f /usr/share/speedtouch/firmware.bin
This will concatenate the boot and main parts, so the -f option is
enough. Or this can be done with the new -a option (sorry -b, for boot,
was already used for software *B*uffering mode):
$ modem_run -a /usr/share/speedtouch/boot.v123.bin \
-f /usr/share/speedtouch/firmware.bin
So troublesome change or acceptable change ?
PS: thomson is refusing me TCP connections on all their domain, so i
need your feedback.
--
Edouard Gomez
Liste de diffusion modem ALCATEL SpeedTouch USB
Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: help needed with testing auto-detect Rev patch
Hi John, > Version 6 now available from the same location > (http://www.hystedjp.pwp.blueyonder.co.uk). Version 6 compiles and seems to run fine with my 330 rev.2 as well. Bye, Leonard. -- mount -t life -o ro /dev/dna /genetic/research Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: speedtouch + laptop : ppp0 and eth0 together: how to ?
This is really outside the remit of this list; it is an issue with your network configuration software of your GNU/Linux distribution. In future you might try the #debian channel on irc.freenode.net or the debian-users mailing list. However: 1- Yes, nothing except packets destined for the remote endpoint will get routed over the ppp0 interface if it is not set. 2- You need to remove the default route from your eth0 interface; on Debian this is typically in /etc/network/interfaces: 'gateway' statement. 3- That depends on what you are connecting to on your eth0 and ppp0 interfaces. You can't have two default routes, especially if they are going through different IP addresses. If eth0 is just going to a local network, you can change the route to a more specific one. If you have different connection based on where you are you might try one of the automagic network configurators, like 'intuitively'. Matthew W. S. Bell On 2004.02.14 11:00, Raphaël MAVILLE wrote: > >PLEASE HELP. > >Thompson Alcatel speedtouch ADSL modem Manta + laptop computer. > >CONTEXT: > >I installed a Linux 2.4.18-bf2.4 Debian 3.0 on a laptop computer. > >like you can see below in "plog", my computer can connect to the internet, > but > >it doesn't work: every "ping" or "mozilla" fail: I cannot use it. > >I think it is because "default route" is set to eth0 also on my laptop >computer. > >And of course, I want to keep a "standard" connection when I travel with it. > >QUESTIONS: > >-1- Is the "default route" set to eth0 responsible of this ? > >-2- If yes, How can I change it ? Which "conf" file have I to modify and > how ? > >-3- Can I keep together eth0 and ppp0 ? How ? > >Perhaps the answers are easy but Which are they ? Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] speedtouch + laptop : ppp0 and eth0 together: how to ?
PLEASE HELP. Thompson Alcatel speedtouch ADSL modem Manta + laptop computer. CONTEXT: I installed a Linux 2.4.18-bf2.4 Debian 3.0 on a laptop computer. like you can see below in "plog", my computer can connect to the internet, but it doesn't work: every "ping" or "mozilla" fail: I cannot use it. I think it is because "default route" is set to eth0 also on my laptop computer. And of course, I want to keep a "standard" connection when I travel with it. QUESTIONS: -1- Is the "default route" set to eth0 responsible of this ? -2- If yes, How can I change it ? Which "conf" file have I to modify and how ? -3- Can I keep together eth0 and ppp0 ? How ? Perhaps the answers are easy but Which are they ? JOINED: "LOG" FILES...: - plog - ifconfig - uname -a - modem_run --help for Version - /cat/proc/pci - lspci - lsusb - syslog * This is my "plog": - Feb 14 11:07:18 rm pppd[404]: Using interface ppp0 Feb 14 11:07:18 rm pppd[404]: Connect: ppp0 <--> /dev/pts/0 Feb 14 11:07:24 rm pppd[404]: Remote message: CHAP authentication success, unit 1017 Feb 14 11:07:24 rm pppd[404]: not replacing existing default route to eth0 [192.168.1.2] Feb 14 11:07:24 rm pppd[404]: local IP address 80.14.137.172 Feb 14 11:07:24 rm pppd[404]: remote IP address 80.14.137.1 Feb 14 11:07:24 rm pppd[404]: primary DNS address 80.10.246.130 Feb 14 11:07:24 rm pppd[404]: secondary DNS address 80.10.246.3 *** This is my "ifconfig": --- eth0 Lien encap:Ethernet HWaddr 00:40:D0:21:93:57 inet adr:192.168.1.1 Bcast:192.168.1.255 Masque:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:100 RX bytes:0 (0.0 b) TX bytes:720 (720.0 b) Interruption:10 Adresse de base:0xa000 lo Lien encap:Boucle locale inet adr:127.0.0.1 Masque:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:12 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:0 RX bytes:864 (864.0 b) TX bytes:864 (864.0 b) ppp0 Lien encap:Protocole Point-à-Point inet adr:80.14.137.172 P-t-P:80.14.137.1 Masque:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:17 errors:0 dropped:0 overruns:0 frame:0 TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:3 RX bytes:1594 (1.5 KiB) TX bytes:54 (54.0 b) *** This is my "uname" -a data: (Debian bf24) --- Linux rm 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i686 unknown ** This is my "modem_run version" (from modem_run --help) -- modem_run version 1.1rc1 This is my vpi vci data: (Wanadoo France) vpi: 8 vci: 35 * This is the "/cat/proc/pci" data: - PCI devices found: Bus 0, device 0, function 0: Host bridge: Intel Corp. 82845 845 (Brookdale) Chipset Host Bridge (rev 4). Prefetchable 32 bit memory at 0xa000 [0xa3ff]. Bus 0, device 1, function 0: PCI bridge: Intel Corp. 82845 845 (Brookdale) Chipset AGP Bridge (rev 4). Master Capable. Latency=128. Min Gnt=10. Bus 0, device 30, function 0: PCI bridge: Intel Corp. 82820 820 (Camino 2) Chipset PCI (rev 5). Master Capable. No bursts. Min Gnt=2. Bus 0, device 31, function 0: ISA bridge: Intel Corp. 82820 820 (Camino 2) Chipset ISA Bridge (ICH2) (rev 5). Bus 0, device 31, function 1: IDE interface: Intel Corp. 82820 820 (Camino 2) Chipset IDE U100 (rev 5). I/O at 0x1100 [0x110f]. Bus 0, device 31, function 2: USB Controller: Intel Corp. 82820 820 (Camino 2) Chipset USB (Hub A) (rev 5). IRQ 10. I/O at 0x1200 [0x121f]. Bus 0, device 31, function 3: SMBus: Intel Corp. 82820 820 (Camino 2) Chipset SMBus (rev 5). IRQ 5. I/O at 0x1400 [0x140f]. Bus 0, device 31, function 4: USB Controller: Intel Corp. 82820 820 (Camino 2) Chipset USB (Hub B) (rev 5). IRQ 6. I/O at 0x1600 [0x161f]. Bus 0, device 31, function 5: Multimedia audio controller: Intel Corp. 82820 820 (Camino 2) Chipset AC'97 Audio Controller (rev 5). IRQ 5. I/O at 0xe000 [0xe0ff]. I/O at 0xe100 [0xe13f]. Bus 0, device 31, function 6: Modem: Intel Corp. 82820 820 (Camino 2) Chipset AC'97 Modem Controller (rev 5). IRQ 5. I/O at 0xe200 [0xe2ff]. I/O at 0xe300 [0xe37f]. Bus 1, device 0, function 0: VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY (rev 0). IRQ 11. Master Capable. Latency=64. Min Gnt=8. Prefetchable 32 bit memory at 0x9000 [0x97ff]. I/O at 0xc000 [0xc0ff]. Non-prefetchable 32 bit memory at 0xe000 [0xe000]. Bus 2, device 2, function 0: Ethernet con
[speedtouch] Rev 4 330 Problems
Hi all, Apologies if all of these queries have been answered before, but I would appreciate some help. I have downloaded the new tarball from Martin Galpin's site, and compiled them (patches weren't working for me either), and followed the HOWTO (as I did with my previous speedtouch that this silver ufo replaced!!!), and I get the following messages in /var/log/messages and /var/log/syslog. I am using a recompiled kernel 4.22 with all neccesary support on a debian sarge system. Regards, Kehan /var/log/messages _ Feb 11 23:17:06 www kernel: PPP generic driver version 2.4.2 Feb 11 23:17:06 www kernel: HDLC line discipline: version $Revision: 3.7 $, maxframe=4096 Feb 11 23:17:06 www kernel: N_HDLC line discipline registered. Feb 11 23:17:07 www modem_run[1227]: modem_run version 1.2-beta3 started by root uid 0 Feb 11 23:17:42 www modem_run[1276]: modem_run version 1.2-beta3 started by root uid 0 Feb 11 23:17:42 www modem_run[1276]: Found ALCATEL SpeedTouch USB modem Feb 11 23:17:42 www modem_run[1276]: Best offset 0 with probability 75% Feb 11 23:17:42 www modem_run[1276]: Best offset 775501 with probability 75% Feb 11 23:17:42 www modem_run[1276]: Firmware information (CRC:0x 223733c, Size:775509, Unknown revision - Please report the CRC and size with the revision number to [EMAIL PROTECTED]) Feb 11 23:17:44 www kernel: usb_control/bulk_msg: timeout Feb 11 23:17:44 www kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x85 len 512 ret -110 Feb 11 23:17:44 www modem_run[1276]: BLOCK1 :935 bytes uploaded : OK Feb 11 23:17:44 www modem_run[1276]: BLOCK2 :511 bytes downloaded : OK Feb 11 23:17:47 www modem_run[1276]: BLOCK3 : 775509 bytes uploaded : OK Feb 11 23:17:47 www modem_run[1276]: BLOCK4 :511 bytes downloaded : OK Feb 11 23:17:48 www modem_run[1276]: Modem reference : 35720370.. Feb 11 23:18:18 www modem_run[1276]: ADSL synchronization has been obtained Feb 11 23:18:18 www modem_run[1276]: ADSL line is up (576 kbit/s down | 288 kbit/s up) Feb 11 23:19:45 www pppd[1461]: pppd 2.4.2b3 started by root, uid 0 Feb 11 23:19:45 www pppd[1461]: Using interface ppp0 Feb 11 23:19:45 www pppd[1461]: Connect: ppp0 <--> /dev/pts/2 Feb 11 23:19:45 www pppd[1461]: Modem hangup Feb 11 23:19:45 www pppd[1461]: Connection terminated. Feb 11 23:19:45 www pppd[1461]: Using interface ppp0 Feb 11 23:19:45 www pppd[1461]: Connect: ppp0 <--> /dev/pts/2 Feb 11 23:19:45 www pppd[1461]: Modem hangup Feb 11 23:19:45 www pppd[1461]: Connection terminated. Feb 11 23:19:45 www pppd[1461]: Using interface ppp0 Feb 11 23:19:45 www pppd[1461]: Connect: ppp0 <--> /dev/pts/2 Feb 11 23:19:45 www pppd[1461]: Modem hangup Feb 11 23:19:45 www pppd[1461]: Connection terminated. Feb 11 23:19:45 www net.agent[1492]: unregister event not handled Feb 11 23:19:45 www pppd[1461]: Using interface ppp0 Feb 11 23:19:45 www pppd[1461]: Connect: ppp0 <--> /dev/pts/2 Feb 11 23:19:45 www pppd[1461]: Modem hangup Feb 11 23:19:45 www pppd[1461]: Connection terminated. Feb 11 23:19:46 www pppd[1461]: Using interface ppp0 Feb 11 23:19:46 www pppd[1461]: Connect: ppp0 <--> /dev/pts/2 /var/log/syslog Feb 11 23:17:06 www kernel: PPP generic driver version 2.4.2 Feb 11 23:17:06 www kernel: HDLC line discipline: version $Revision: 3.7 $, maxframe=4096 Feb 11 23:17:06 www kernel: N_HDLC line discipline registered. Feb 11 23:17:07 www modem_run[1227]: modem_run version 1.2-beta3 started by root uid 0 Feb 11 23:17:42 www modem_run[1276]: modem_run version 1.2-beta3 started by root uid 0 Feb 11 23:17:42 www modem_run[1276]: Found ALCATEL SpeedTouch USB modem Feb 11 23:17:42 www modem_run[1276]: Best offset 0 with probability 75% Feb 11 23:17:42 www modem_run[1276]: Best offset 775501 with probability 75% Feb 11 23:17:42 www modem_run[1276]: Firmware information (CRC:0x 223733c, Size:775509, Unknown revision - Please report the CRC and size with the revision number to [EMAIL PROTECTED]) Feb 11 23:17:44 www kernel: usb_control/bulk_msg: timeout Feb 11 23:17:44 www kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x85 len 512 ret -110 Feb 11 23:17:44 www modem_run[1276]: BLOCK1 :935 bytes uploaded : OK Feb 11 23:17:44 www modem_run[1276]: BLOCK2 :511 bytes downloaded : OK Feb 11 23:17:47 www modem_run[1276]: BLOCK3 : 775509 bytes uploaded : OK Feb 11 23:17:47 www modem_run[1276]: BLOCK4 :511 bytes downloaded : OK Feb 11 23:17:48 www modem_run[1276]: Modem reference : 35720370.. Feb 11 23:18:01 www /USR/SBIN/CRON[1301]: (root) CMD (/root/adsl/check.sh >/dev/null 2>&1) Feb 11 23:18:01 www /USR/SBIN/CRON[1303]: (root) CMD (/root/adsl/check.sh >/dev/null 2>&1) Feb 11 23:18:01 www /USR/SBIN/CRON[1306]: (root) CMD (/root/adsl/check.sh >/dev/null 2>&1) Feb 11 23:18:01 www /USR/SBIN/CRON[1304]: (root) CMD (/root/adsl/check.sh >/dev/null 2>&1) Feb 11 23:18:18 www modem_run[1276]: ADSL synchronization has bee
