[speedtouch] Re: 330/Rev 400 (silver modem) Resource temporarily unavailable
Hi,
I've got it working finally and seems that the patch is simple and
acceptable for the moment.
The only place where pusb_endpoint_read procedure is invoked with a 0
timeout parameter is exactly the place under question described below by
Gary. All I did was to replace 0 with DATA_TIMEOUT (all other calls are
using this parameter). This seem to resolve all issues including the
previous timeout. timed_out=0 patch is no longer needed and my modem
connects happily within 15 seconds. The pushb-linux.c file where
pusb_endpoint_read is defined contains two functions (that seem
different to me) - one for timeout = 0 and the other one for all other
cases. I did not investigate the difference between them, but it looks
like the problem is somewhere in the pusb_endpoint_rw_no_timeout.
Back in the modem_run.c the pusb_endpoint_read returns obviously
negative result, because my log is full with the Error reading
interrupts messages. To stop them I simply commented out the lines
below:
/*if(ret 0)
report(0, REPORT_ERROR, Error reading interrupts\n);*/
This obviously means that something is not entirely right, though works
at least.
That's it!
Meanwhile not everything is nice and clear. I've got (seems) unstable
system. I had no any troubles before the kernel recompilation by the
speedbundle.
I am running Redhat 90 distro with 2.4.18 kernel. As far as I can see
there are some specifics (Makefile) either with the distribution or with
the kernel when it comes to speedbundle compilations. Any suggestions?
Thanks for your help. I am expecting your feedback
Regards
Svilen
On Tue, 2004-02-03 at 19:44, Gary Bilkus wrote:
Duncan,
OK, looked a bit further. The underlying problem is that with my silver
modem, the
pusb_endpoint_read call in the child process just hangs when you run
modem_run (new version)
by itself.
Running the old version however causes the call tp pusb_endpint_read to
return,
whereupon the rest of the code gets triggered for the (don't know what
this was) case, and that makes everything work.
Don't know why the new modem doesn't allow pusb_endpoint_read to return.
Will try a (horrible) workaround by removing the read call and replacing
with a timeout...
Gary
Duncan Sands wrote:
This time, modem_run itself seemed happy ( after that annoying timeout
cos the SIGUSRx isn't being generated by the detached process ), but
pppd failed with 'resource temporarily unavailable'
Hi Gary, the code that generates the SIGUSRx also tells the kernel that the firmware
is loaded. From modem_run.c:
if(!up) {
report(1, REPORT_INFO, Sending a signal to
notify the adsl up state\n);
kill(parent, SIGUSR2);
up = 1;
}
if(signal_kernel) {
sleep(1);
pusb_ioctl(fdusb, 1, 1, NULL);
}
What you can do is move the signal_kernel bit somewhere else, for example
just after this line:
modem_start_synchro(fdusb);
I didn't test this but it should work fine.
I hope this helps,
Duncan.
Liste de diffusion modem ALCATEL SpeedTouch USB
Pour se désinscrire : mailto:[EMAIL PROTECTED]
Liste de diffusion modem ALCATEL SpeedTouch USB
Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: PCI Speedtouch
Selon Dan O'Brien [EMAIL PROTECTED]: Is there any support for the PCI speedtouch modem in Linux? I don't have USB! Dan O'Brien The Dancing Ox Company 146 Penmere Drive, Pentire, Newquay (01637) 873 897 www.oxdance.co.uk design with passion Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED] This modem as nothing common to the speedtouch usb except the brand. It is shipped with Itex chip You should google on itex pci linux and you will find info like that http://www.treshna.com/~chefu/itexdsl-pppoa-2.4.19.html Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Thanks some newbie questions
After three frustrating weeks I finally got my silver 330 connected last night thanks to help from everyone on this list. So what next ? I have a few questions that I'm sure are very basic to you guys but would save me a lot of time. Last night I was logged in as root and connected by issuing the modem_run command and then the pppd call adsl command 1) Do I have to kill the connection before I shut down if so how ? 2) Do I have to issue the two commands detailed above each time i want to connect or is there a quicker way ? 3)Will I be able to do this when logged in as a user ? 4)How do I get it to connect automatically on start up and kill automatically on shut down ? I am currently running fedora core 1 Any tips on the above would be gratefully appreciated. -- Squabsy Using Opera, The Bat, K-meleon, or Becky. Trying to use Linux Right Now Using Fastmail when I should be working Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: Thanks some newbie questions
1) Yep. killall pppd (or perhaps killall -9 pppd) 2) I've got an initscript by default... it depends on the distro you run. Check for the availability, or edit a file with these lines: modem_run -m -f /etc/mgmt.o # Where is mgmt.o pppd call adsl # What is the file # to be called Save, for example speedtch, then chmod +x speedtouch, and so, to run your modem, ./speedtch :) But it's better to look for a ready initscript :) 3) Never tried, but probably no, by default. 4) Initscript. I think that fedora should have its initscript for that modem... gentoo has one! Bye Marco Il lun, 2004-02-09 alle 11:57, Squabsy ha scritto: After three frustrating weeks I finally got my silver 330 connected last night thanks to help from everyone on this list. So what next ? I have a few questions that I'm sure are very basic to you guys but would save me a lot of time. Last night I was logged in as root and connected by issuing the modem_run command and then the pppd call adsl command 1) Do I have to kill the connection before I shut down if so how ? 2) Do I have to issue the two commands detailed above each time i want to connect or is there a quicker way ? 3)Will I be able to do this when logged in as a user ? 4)How do I get it to connect automatically on start up and kill automatically on shut down ? I am currently running fedora core 1 Any tips on the above would be gratefully appreciated. -- Attached file included as plaintext by Listar -- -- File: signature.asc -- Desc: Questa parte del messaggio =?ISO-8859-1?Q?=E8?= firmata -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBAJ2oJyz5jYFefjkwRAoBHAJ45urV7+/gH6eGMw1qq1MP9k6dqnQCfS2A4 WQ9FA/VAclBckaJP+NdoXAY= =tPTI -END PGP SIGNATURE- Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] problem with driver - see config.log
Hi, when I have been trying to install modem driver under my Slackware 9.1 I reach this problem: C compiler cannot create executeable files see config.log I'va goe gcc 3.2 installed on my system - USB connection works well so what is going on? -- Pozdrawiam / Best regards Piotr Kaczor http://www.welet.pl Welet Company Sp. z o.o. Liste de diffusion modem ALCATEL SpeedTouch USB Pour se dsinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] problem with driver - see config.log
Hi,
when I have been trying to install modem driver under my Slackware 9.1 I
reach this problem:
C compiler cannot create executeable files see config.log
I'va goe gcc 3.2 installed on my system - USB connection works well so what
is going on?
--
Pozdrawiam / Best regards
Piotr Kaczor
http://www.welet.pl
Welet Company Sp. z o.o.
-- Attached file included as plaintext by Listar --
-- File: config.log
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by speedtouch configure 1.2-beta3, which was
generated by GNU Autoconf 2.58. Invocation command line was
$ ./configure
## - ##
## Platform. ##
## - ##
hostname = wd
uname -m = i686
uname -r = 2.4.22
uname -s = Linux
uname -v = #6 Tue Sep 2 17:43:01 PDT 2003
/usr/bin/uname -p = unknown
/bin/uname -X = unknown
/bin/arch = i686
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /usr/local/sbin
PATH: /usr/sbin
PATH: /sbin
PATH: /usr/local/bin
PATH: /usr/bin
PATH: /bin
PATH: /usr/X11R6/bin
PATH: /usr/games
PATH: /opt/kde/bin
PATH: /usr/lib/qt-3.2.1/bin
## --- ##
## Core tests. ##
## --- ##
configure:1351: checking build system type
configure:1369: result: i686-pc-linux-gnuoldld
configure:1377: checking host system type
configure:1391: result: i686-pc-linux-gnuoldld
configure:1446: checking for gcc
configure:1462: found /usr/bin/gcc
configure:1472: result: gcc
configure:1716: checking for C compiler version
configure:1719: gcc --version /dev/null 5
gcc (GCC) 3.2.3
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
configure:1722: $? = 0
configure:1724: gcc -v /dev/null 5
Reading specs from /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/specs
Configured with: ../gcc-3.2.3/configure --prefix=/usr --enable-shared
--enable-threads=posix --enable-__cxa_atexit --disable-checking --with-gnu-ld
--verbose --target=i486-slackware-linux --host=i486-slackware-linux
Thread model: posix
gcc version 3.2.3
configure:1727: $? = 0
configure:1729: gcc -V /dev/null 5
gcc: argument to `-V' is missing
configure:1732: $? = 1
configure:1755: checking for C compiler default output file name
configure:1758: gccconftest.c 5
gcc: installation problem, cannot exec `as': No such file or directory
configure:1761: $? = 1
configure: failed program was:
| /* confdefs.h. */
|
| #define PACKAGE_NAME speedtouch
| #define PACKAGE_TARNAME speedtouch
| #define PACKAGE_VERSION 1.2-beta3
| #define PACKAGE_STRING speedtouch 1.2-beta3
| #define PACKAGE_BUGREPORT [EMAIL PROTECTED]
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:1800: error: C compiler cannot create executables
See `config.log' for more details.
## ##
## Cache variables. ##
## ##
ac_cv_build=i686-pc-linux-gnuoldld
ac_cv_build_alias=i686-pc-linux-gnuoldld
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_host=i686-pc-linux-gnuoldld
ac_cv_host_alias=i686-pc-linux-gnuoldld
ac_cv_prog_ac_ct_CC=gcc
## - ##
## Output variables. ##
## - ##
CC='gcc'
CFLAGS=''
CPP=''
CPPFLAGS=''
CWARN=''
DEFS=''
DOCDIR=''
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
EXEEXT=''
INSTALL_DATA=''
INSTALL_PROGRAM=''
INSTALL_SCRIPT=''
LDFLAGS=''
LIBOBJS=''
LIBS=''
LTLIBOBJS=''
MAKE_INSTALL_SCRIPT=''
OBJEXT=''
PACKAGE_BUGREPORT='[EMAIL PROTECTED]'
PACKAGE_NAME='speedtouch'
PACKAGE_STRING='speedtouch 1.2-beta3'
PACKAGE_TARNAME='speedtouch'
PACKAGE_VERSION='1.2-beta3'
PATH_SEPARATOR=':'
PUSB_SOURCE=''
PWD='/tmp/rozpakowane/speedtouch-1.2-beta3'
RPM_ROOT=''
SET_MAKE=''
SHELL='/bin/sh'
THREAD_LIBS=''
USE_SYSLOG=''
VERSION='1.2-beta3'
ac_configure_args=''
ac_ct_CC='gcc'
bindir='${exec_prefix}/bin'
build='i686-pc-linux-gnuoldld'
build_alias=''
build_cpu='i686'
build_os='linux-gnuoldld'
build_vendor='pc'
datadir='${prefix}/share'
exec_prefix='NONE'
host='i686-pc-linux-gnuoldld'
host_alias=''
host_cpu='i686'
host_os='linux-gnuoldld'
host_vendor='pc'
includedir='${prefix}/include'
infodir='${prefix}/info'
installuser=''
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
link_opts=''
localstatedir='${prefix}/var'
mandir='${prefix}/man'
oldincludedir='/usr/include'
prefix='NONE'
program_transform_name='s,x,x,'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
[speedtouch] Re: problem with driver - see config.log
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The problem is nothing to do with the drivers. As config.log reports, you're missing `as', which is the GNU assembler. Reinstall/compile GCC and it's dependencies. Regards, Martin -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAJ8/P3bF34WXq1XsRArdXAKC5Xw6dciwZ95X24eEwYyAhnzHfZgCgoid8 rttLpF6RJsgB6oTxg8rLDzA= =hdv9 -END PGP SIGNATURE- Liste de diffusion modem ALCATEL SpeedTouch USB Pour se dsinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: help needed with testing auto-detect Rev patch
I'm thinking about the timeout for kernel mode. What if I let the subprocess
time out at the same time as the external timeout (which isn't my code, I
just picked it up from the CVS) then there wouldn't be a zombie hanging
around, but neither would there be anything looping with errors.
I have managed to borrow a Rev 0400 modem (thanks Brian) and am posting this
while using it.
What I get is this
20:06:46 modem_run[46] modem_run version 1.2-john5 started by root uid 0
20:06:46 modem_run[46] Found ALCATEL SpeedTouch USB modem
20:06:46 modem_run[46] Rev 0400 detected, revision 4 chosen
20:06:47 modem_run[46] Best offset 0 with probability 75%
20:06:47 modem_run[46] Best offset 775501 with probability 75%
20:06:48 modem_run[46] Firmware information (CRC:0x0223733c, Size:775509,
1.0.10 - Win32 Rev 0400 SACHU3)
20:06:50 kernel: usb_control/bulk_msg timeout
20:06:50 kernel: usbdevfs USBDEVFS_BULK failed dev 2 ep 0x85 len 512
ret -110
20:06:50 modem_run[46] BLOCK1 : 935 bytes uploaded : OK
20:06:50 modem_run[46] BLOCK2 : 511 bytes downloaded : OK
20:06:53 modem_run[46] BLOCK3 : 775509 bytes uploaded : OK
20:06:53 modem_run[46] BLOCK4 : 511 bytes downloaded : OK
20:06:54 modem_run[46] Modem reference : 35720370..
20:07:54 modem_run[46] ADSL synchronization has been obtained
20:07:54 modem_run[46] ADSL line is up (576 kbit/s down | 288 kbit/s up)
20:08:02 pppoa3[166] pppoa3 version 1.2-john5 started by nobody (uid 99)
20:08:02 pppoa3[166] Control thread ready
20:08:02 pppoa3[168] host -- pppoa3 -- modem stream ready
20:08:02 pppoa3[169] modem -- pppoa3 -- host stream ready
which means the same modem_run works for Rev and Rev 0400. Anyone
willing to test on Rev 0200?
As you can see it waits for exactly 60 seconds before announcing sync has
been obtained on Rev 0400, whether it has or not.
A question for people who use usermode pppoa3... Do you use the -e 1
parameter with Rev 0400 silver modems, because I am not setting it and the
modem is working OK.
- Original Message -
From: Gary Bilkus [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, February 08, 2004 5:55 PM
Subject: [speedtouch] Re: help needed with testing auto-detect Rev patch
That might work. What I actually did was put a timeout in the subprocess:
(from line 1090 of original file)
memset(prevbuf, 0, TOTAL);
static int timeoutfirsttime = 25000;
while(1) {
int ret;
unsigned char lbuf[6];
/* We can try reading the int endpoint */
ret = pusb_endpoint_read(ep_int, lbuf, sizeof(lbuf),
timeoutfirsttime);
timeoutfirsttime=0;
/* Ok we failed, perhaps the device has been disconnected */
if(ret 0 errno == ENODEV) {
report(0, REPORT_INFO, Device disconnected, shutting
down);
break;
}
Your version has the advantage that the timeout is settable rather than
hard coded, but the disadvantage that the code relating to the first
read in the child process will be triggered whenever a read does
eventually occur, and that is probably not a good thing, so you should
probably also make that entire section of the child process conditional
on not v4
Gary
John Hysted wrote:
Would it be likely to work if I replaced
if (revision==4)
timed_out = 0;
which is an arbitrary hack which assumes everything worked for Rev 0400
after timeout seconds, with
if (revision==4) {
if (timed_out) {
if(signal_kernel) {
pusb_ioctl(fdusb, 1, 1, NULL);
}
timed_out = 0;
}
}
which does the same thing, but adds the command the subprocess will never
run. Or is the subprocess still running and causing trouble?
- Original Message -
From: Gary Bilkus [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, February 08, 2004 4:11 PM
Subject: [speedtouch] Re: help needed with testing auto-detect Rev patch
John,
I don't think your patched version will work with a silver rev 4 modem
in kernel driver mode.
As per the thread involving myself and others last week, the v4 software
doesn't report status back after connecting, as a result of which the
subprocess after fork() will not
signal the main process to continue, but, more seriously, it will never
execute the pusb_ioctl(fdusb,1,1,NULL) which is necessary to free the
driver to attach to the pppoatm code.
As I understand it, this doesn't matter if you are using the pppoa
userspace code, so many users of the driver won't care. However, for
those of us usuing 2.6 kernels, only the kernel space driver currently
works.
Rgds,
Gary
Liste de diffusion modem ALCATEL SpeedTouch USB
Pour se désinscrire :
mailto:[EMAIL PROTECTED]
Liste de diffusion modem ALCATEL SpeedTouch USB
Pour se désinscrire :
mailto:[EMAIL PROTECTED]
Liste de diffusion modem ALCATEL SpeedTouch USB
Pour se désinscrire : mailto:[EMAIL
[speedtouch] Re: help needed with testing auto-detect Rev patch
I read the info on your page and I agree with you and others that my connection behave better with speedtouch driver user mode when I was using V1.1 than V1.2x but many other packages have changed and I use a different hardware in my box so I was not able to know what was the root cause. I know one other guy which have reversed to V1.1 driver on IPCop V1.3 and found the same reliability improvement with the old driver. Because now I can use user and kernel mode driver on IPCop, I saw the same trouble (that I named EMI bug) like you with both drivers so modem_run may be the guilty. This is with a green stingray rev0 and kernel mode driver with rp-pppoe plugin Feb 9 22:02:30 adsl modem_run[4021]: modem_run version 1.2-beta3 started by root uid 0 Feb 9 22:02:30 adsl modem_run[4021]: Found ALCATEL SpeedTouch USB modem Feb 9 22:02:30 adsl modem_run[4021]: Rev detected, revision 0 chosen Feb 9 22:02:30 adsl modem_run[4021]: Best offset 0 with probability 100% Feb 9 22:02:30 adsl modem_run[4021]: Best offset 671645 with probability 100% Feb 9 22:02:31 adsl modem_run[4021]: Firmware information (CRC:0x3b4a5854, Size:671653, 1.6.1 - MacOSX - Win32(1.0.1800)) Feb 9 22:02:33 adsl kernel: usb_control/bulk_msg: timeout Feb 9 22:02:33 adsl kernel: usbdevfs: USBDEVFS_BULK failed dev 3 ep 0x85 len 512 ret -110 Feb 9 22:02:33 adsl modem_run[4021]: BLOCK1 :883 bytes uploaded : OK Feb 9 22:02:33 adsl modem_run[4021]: BLOCK2 :511 bytes downloaded : OK Feb 9 22:02:36 adsl modem_run[4021]: BLOCK3 : 671653 bytes uploaded : OK Feb 9 22:02:36 adsl modem_run[4021]: BLOCK4 :511 bytes downloaded : OK Feb 9 22:02:37 adsl modem_run[4021]: Found kernel mode driver Feb 9 22:02:37 adsl modem_run[4021]: Modem reference : 3EC18607CAAA08 Feb 9 22:02:49 adsl modem_run[4022]: Sending a signal to notify the adsl up state Feb 9 22:02:49 adsl modem_run[4021]: ADSL synchronization has been obtained Feb 9 22:02:49 adsl modem_run[4021]: ADSL line is up (608 kbit/s down | 160 kbit/s up) This is with a purple rev 200 and kernel mode driver with rp-pppoe plugin Feb 9 22:09:09 adsl modem_run[4236]: modem_run version 1.2-beta3 started by root uid 0 Feb 9 22:09:09 adsl modem_run[4236]: Found ALCATEL SpeedTouch USB modem Feb 9 22:09:09 adsl modem_run[4236]: Rev 0200 detected, revision 2 chosen Feb 9 22:09:09 adsl modem_run[4236]: Best offset 0 with probability 100% Feb 9 22:09:10 adsl modem_run[4236]: Best offset 671645 with probability 100% Feb 9 22:09:10 adsl modem_run[4236]: Firmware information (CRC:0x3b4a5854, Size:671653, 1.6.1 - MacOSX - Win32(1.0.1800)) Feb 9 22:09:12 adsl kernel: usb_control/bulk_msg: timeout Feb 9 22:09:12 adsl kernel: usbdevfs: USBDEVFS_BULK failed dev 4 ep 0x85 len 512 ret -110 Feb 9 22:09:12 adsl modem_run[4236]: BLOCK1 :883 bytes uploaded : OK Feb 9 22:09:13 adsl modem_run[4236]: BLOCK2 :511 bytes downloaded : OK Feb 9 22:09:16 adsl modem_run[4236]: BLOCK3 : 671653 bytes uploaded : OK Feb 9 22:09:16 adsl modem_run[4236]: BLOCK4 :511 bytes downloaded : OK Feb 9 22:09:17 adsl modem_run[4236]: Found kernel mode driver Feb 9 22:09:17 adsl modem_run[4236]: Modem reference : 3EC3665601 Feb 9 22:09:29 adsl modem_run[4237]: Sending a signal to notify the adsl up state Feb 9 22:09:29 adsl modem_run[4236]: ADSL synchronization has been obtained Feb 9 22:09:29 adsl modem_run[4236]: ADSL line is up (608 kbit/s down | 160 kbit/s up) This is with a purple rev 200 and user mode driver with pppoa3 in PPPoA mode (I haven't anything for -e switch and it work) Feb 9 22:27:35 adsl ipcop: AlcatelUSB: Uploading firmware to modem Feb 9 22:27:35 adsl modem_run[4524]: modem_run version 1.2-beta3 started by root uid 0 Feb 9 22:27:35 adsl modem_run[4524]: Found ALCATEL SpeedTouch USB modem Feb 9 22:27:35 adsl modem_run[4524]: Rev 0200 detected, revision 2 chosen Feb 9 22:27:35 adsl modem_run[4524]: Best offset 0 with probability 100% Feb 9 22:27:35 adsl modem_run[4524]: Best offset 671645 with probability 100% Feb 9 22:27:36 adsl modem_run[4524]: Firmware information (CRC:0x3b4a5854, Size:671653, 1.6.1 - MacOSX - Win32(1.0.1800)) Feb 9 22:27:38 adsl kernel: usb_control/bulk_msg: timeout Feb 9 22:27:38 adsl kernel: usbdevfs: USBDEVFS_BULK failed dev 6 ep 0x85 len 512 ret -110 Feb 9 22:27:38 adsl modem_run[4524]: BLOCK1 :883 bytes uploaded : OK Feb 9 22:27:38 adsl modem_run[4524]: BLOCK2 :511 bytes downloaded : OK Feb 9 22:27:41 adsl modem_run[4524]: BLOCK3 : 671653 bytes uploaded : OK Feb 9 22:27:41 adsl modem_run[4524]: BLOCK4 :511 bytes downloaded : OK Feb 9 22:27:42 adsl modem_run[4524]: Modem reference : 3EC3665601 Feb 9 22:27:54 adsl modem_run[4525]: Sending a signal to notify the adsl up state Feb 9 22:27:54 adsl modem_run[4524]: ADSL synchronization has been obtained Feb 9 22:27:54 adsl modem_run[4524]: ADSL line is up (608 kbit/s down | 160 kbit/s up) This is with a green stingray rev0 and user mode driver
[speedtouch] Re: 330/Rev 400 success
Hello Martin, I finally got my own patch to work today! So, I'm free once again. http://www.nemohackers.org/speedtouch.php If I apply this patch to modem_run will it still work with the original 330? If so did you add it to CVS? If not, how do you expect to merge it? An extra command line switch? 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: 330/Rev 400 success
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 09 February 2004 09:59 pm, Leonard den Ottolander wrote: Hello Martin, I finally got my own patch to work today! So, I'm free once again. http://www.nemohackers.org/speedtouch.php If I apply this patch to modem_run will it still work with the original 330? If so did you add it to CVS? If not, how do you expect to merge it? An extra command line switch? Bye, Leonard. No, it wont work with any 330 before the Rev 0400, which is what I explicitly stated on the page, and one of the reasons why it _isn't_ committed to CVS. A command line switch would be possible, though the thread help needed with testing auto-detect Rev patch is working on automatic detection -- the better option. If this happens, the ARM bytes from the patch on the site above can be merged with theirs, and finally merged with CVS. Regards, Martin - -- Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAKAQz3bF34WXq1XsRAqagAKDs+CE/tc/GpXD0VKlTbAC2yao4HQCg6t40 43Q46dNX1z/PMBbIhOeLaUY= =Qfnh -END PGP SIGNATURE- Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: 330/Rev 400 success
Martin Galpin ([EMAIL PROTECTED]) wrote:
Until a real fix is made, I wrote a short page for new users on how to
get the Rev 400 modem to work.
This mail is just posted to show i'm not ignoring this nice thread and
that i'm porting attention to it. It's just i have not so much time
left to code these days. So i'll explain my plan.
Ok i started hacking a new firmware extractor. Here i sumarize the
needed steps:
1 - Reverse the modem_run design to old 1.1 design, as this works with
both new versions and old versions.
2 - Write a new firmware extractor.
1 and 2 are pretty independent when it comes to old modems. New modems
would need 2 *and* 1.
Basically, the new firmware extractor will look into the firmware file
for two ARM codes, the bootstrap code and the proper firmware. This will
work well for old firmware files that shipped both codes. With newer
releases, thomson separated the codes in two files, so i'll extend the
command line so you can tell the firmware loader to load the two pieces
of code from two different files.
I'll also add a bootstrap code CRC checking to detect if we try to
bootstrap a rev 4 with a rev 4 bootstrap code, and vice versa. This
will be a very similar code to the one that checks the big firmware.
It will all use a struct like:
typedef struct
{
unsigned char *phase1; /* Boostrap code */
unsigned char *phase2; /* Firmware */
unsigned long phase1_length;
unsigned long phase2_length;
} stusb_firmware_image_t;
The function i'm coding will extend the current firmware loader and
will look like:
stusb_firmware_image_t *firmware_load(char *phase1_filename,
char *phase2_filename);
The function behavior will be as follow:
- if phase1_filename == NULL then phase1_filename = phase2_filename;
(old firmware used to contain both codes)
- allocate a stusb_firmware_image_t *img;
- search boostrap code into phase1_filename, if not found
img-phase1 = NULL, if copy the data block and set its size.
- same for phase2
- return img
Then in modem_run, if img-phase1 is null, we set it to the free
bootstrap code that we can distribute safely in our code.
Then, step 3, check the modem revision, and identify the boostrap code
to determine which version it can bootstrap. If the modem revision
doesn't match the boostrap code, shout loud and exit, else continue.
I think that's all i have in mind atm. Ah Thomson is probably going to
change the firmware files formats in next releases, so this design
should help in supporting this new type of files in the future (unless
thomson decides to back the file format change).
Ok i threw the main ideas, now i must find the time to code it
correctly. Cry and shout loud on this ML if i did nothing until the end
of the week.
--
Edouard Gomez
Liste de diffusion modem ALCATEL SpeedTouch USB
Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: 330/Rev 400 success
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ok i threw the main ideas, now i must find the time to code it correctly. Cry and shout loud on this ML if i did nothing until the end of the week. Sounds good to me. Don't think that was a dig, I totally understand if you don't have so much time -- I experience that too :-). Out of interest, do Thomson notify you of the changes, or do they rely on the community to reverse engineer it? I get the impression that for a product which sports a Supported in GNU/Linux they don't do much to help it. I must say I dream of a day when we have completely non-proprietary firmware... Regards, Martin - -- Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAKAwQ3bF34WXq1XsRAoq4AKC87sr4GmhLG7lAcnKqcmBGDNx0TwCfcKX2 sievJfgLkYYAZH21mkP54Vk= =HoYD -END PGP SIGNATURE- Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: 330/Rev 400 success
Martin Galpin ([EMAIL PROTECTED]) wrote: Out of interest, do Thomson notify you of the changes, or do they rely on the community to reverse engineer it? I get the impression that for a product which sports a Supported in GNU/Linux they don't do much to help it. Since the first 330 is out, a thomson person contacted me with a patch for our modem_run program and pppoa3. And for this last speedtouch revision, benoit, francois, duncan and I have received sample modems from thomson to test our changes. If all goes well, we'll even have some striped down specs so we finally understand all the voodoo behind the usb control/interface usb code. Last year thomson did fail in providing us these docs, but i still hope, thomson will finally provide us these important docs. I don't have a ready version yet, because the last patches they provided us are just incompatible with old revisions, and their firmware extractor is only adpated to the new file format they'll probably adopt. At this moment, they asked me not to publish it, as they didn't make their choice yet on the format adoption (and it would not be so useful to end users if the fileformat isn't used ;-) I'd say, they support us enough so the modems work. It's not the ideal solution, but they support GNU/linux (and indirectly FreeBSD) more than some others USB ADSL modem manufacturers. -- Edouard Gomez Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
