[speedtouch] Re: modem_run problem
It's an old green revision 0. I've used several different versions of the firmware with modem_run, it's not usually an issue. On the computer upstairs we have a burgundy 330 (revision 2?) and that one is more fussy about the firmware. About a year ago it was dropping packets and giving slow download speeds but changing the firmware fixed it. Thanks for your help. With the kernel/hotplug loading the firmware it's a lot quicker to connect. It reminds me of how quick it was with a 2.4 kernel. I think you are having problems with firmware now for your green mantaray because of boot.bin (speedtch-1.bin). modem_run used to have boot firmware for these modems built in, so only speedtch-2.bin ever caused problems. The in-kernel loader has no firmware built in. It deals with multiple modem versions needing different firmware by trying to load firmware from a file based on the firmware revision numbers as I described in another message. It would be nice if the firmware extractor automatically put the firmware in the right file (speedtch-2.bin.4 for example), but sadly AFAIK the firmware files supplied by Alcatel/Thomson don't have any revision information in them so it can't be done. All the best, Duncan. Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: modem_run problem
[*] I know of a bug in the kernel module which might bite you, but probably not. It's been really stable so far and no more errors in the logs. I was getting the errors below with 2.6.10-rc1-mm1 and I'm now using 2.6.10-rc2-mm3 without modem_run and no more erors. Nov 22 10:01:28 gandalf kernel: usb 3-1: control timeout on ep0in Nov 22 10:01:28 gandalf kernel: SpeedTouch: Error -110 fetching device status Nov 22 10:04:53 gandalf kernel: usb 3-1: control timeout on ep0in Nov 22 10:04:53 gandalf kernel: SpeedTouch: Error -110 fetching device status I'm still trying to auto start pppd on boot. The problem with /etc/hotplug/usb/speedtouch is that its run 3 times I thought of trying udev but I can't find speedtch in /sys/block or /sys/class the only instances I can find are /sys/module/speedtch and /sys/bus/usb/drivers/speedtch. I think I'll got back to /etc/init.d/speedtouch Regards Nick Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: modem_run problem
Duncan Sands wrote: Try doing this: echo 8 /proc/sys/kernel/printk Also, what kernel/module version are you using? Well with a 2.6.9 kernel, plugging in the modem puts this in /var/log/sys.log Nov 23 14:24:23 hame kernel: ehci_hcd :00:1d.7: GetStatus port 6 status 001803 POWER sig=j CSC CONNECT Nov 23 14:24:23 hame kernel: hub 1-0:1.0: port 6, status 0501, change 0001, 480 Mb/s Nov 23 14:24:23 hame kernel: hub 1-0:1.0: debounce: port 6: total 100ms stable 100ms status 0x501 Nov 23 14:24:23 hame kernel: hub 1-0:1.0: port 6 not reset yet, waiting 50ms Nov 23 14:24:23 hame kernel: ehci_hcd :00:1d.7: port 6 full speed -- companion Nov 23 14:24:23 hame kernel: ehci_hcd :00:1d.7: GetStatus port 6 status 003801 POWER OWNER sig=j CONNECT Nov 23 14:24:23 hame kernel: uhci_hcd :00:1d.2: port 2 portsc 0083 Nov 23 14:24:23 hame kernel: hub 4-0:1.0: port 2, status 0101, change 0001, 12 Mb/s Nov 23 14:24:23 hame kernel: uhci_hcd :00:1d.2: wakeup_hc Nov 23 14:24:24 hame kernel: hub 4-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x101 Nov 23 14:24:24 hame kernel: usb 4-2: new full speed USB device using address 2 Nov 23 14:24:24 hame kernel: uhci_hcd :00:1d.2: uhci_result_control: failed with status 44 Nov 23 14:24:24 hame kernel: [dfd4d240] link (1fd4d1e2) element (1fd4c040) Nov 23 14:24:24 hame kernel: 0: [dfd4c040] link (1fd4c080) e0 Stalled CRC/Timeo Length=7 MaxLen=7 DT0 EndPt=0 Dev=0, PID=2d(SETUP) (buf=1ededc40) Nov 23 14:24:24 hame kernel: 1: [dfd4c080] link (0001) e3 IOC Active Length=0 MaxLen=7ff DT1 EndPt=0 Dev=0, PID=69(IN) (buf=) Nov 23 14:24:24 hame kernel: Nov 23 14:24:24 hame kernel: uhci_hcd :00:1d.2: uhci_result_control: failed with status 44 Nov 23 14:24:24 hame kernel: [dfd4d240] link (1fd4d1e2) element (1fd4c040) Nov 23 14:24:24 hame kernel: 0: [dfd4c040] link (1fd4c080) e0 Stalled CRC/Timeo Length=7 MaxLen=7 DT0 EndPt=0 Dev=0, PID=2d(SETUP) (buf=1ededc40) Nov 23 14:24:24 hame kernel: 1: [dfd4c080] link (0001) e3 IOC Active Length=0 MaxLen=7ff DT1 EndPt=0 Dev=0, PID=69(IN) (buf=) Nov 23 14:24:24 hame kernel: Nov 23 14:24:24 hame kernel: usb 4-2: device not accepting address 2, error -71 Nov 23 14:24:24 hame kernel: usb 4-2: new full speed USB device using address 3 Nov 23 14:24:24 hame kernel: usb 4-2: new device strings: Mfr=1, Product=2, SerialNumber=3 Nov 23 14:24:24 hame kernel: usb 4-2: default language 0x0409 Nov 23 14:24:24 hame kernel: usb 4-2: Product: Speed Touch USB Nov 23 14:24:24 hame kernel: usb 4-2: Manufacturer: ALCATEL Nov 23 14:24:24 hame kernel: usb 4-2: SerialNumber: 0090D07664E7 Nov 23 14:24:24 hame kernel: usb 4-2: hotplug Nov 23 14:24:24 hame kernel: usb 4-2: adding 4-2:1.0 (config #1, interface 0) Nov 23 14:24:24 hame kernel: usb 4-2:1.0: hotplug Nov 23 14:24:24 hame kernel: speedtch 4-2:1.0: usb_probe_interface Nov 23 14:24:24 hame kernel: speedtch 4-2:1.0: usb_probe_interface - got id Nov 23 14:24:24 hame kernel: drivers/usb/misc/speedtch.c: udsl_usb_probe: trying device with vendor=0x6b9, product=0x4061, ifnum 0 Nov 23 14:24:24 hame kernel: usb 4-2: adding 4-2:1.1 (config #1, interface 1) Nov 23 14:24:24 hame kernel: usb 4-2:1.1: hotplug Nov 23 14:24:24 hame kernel: speedtch 4-2:1.1: usb_probe_interface Nov 23 14:24:24 hame kernel: speedtch 4-2:1.1: usb_probe_interface - got id Nov 23 14:24:24 hame kernel: drivers/usb/misc/speedtch.c: udsl_usb_probe: trying device with vendor=0x6b9, product=0x4061, ifnum 1 Nov 23 14:24:24 hame kernel: drivers/usb/misc/speedtch.c: udsl_usb_probe: device accepted Nov 23 14:24:24 hame kernel: usb 4-2: adding 4-2:1.2 (config #1, interface 2) Nov 23 14:24:24 hame kernel: usb 4-2:1.2: hotplug Nov 23 14:24:24 hame kernel: speedtch 4-2:1.2: usb_probe_interface Nov 23 14:24:24 hame kernel: speedtch 4-2:1.2: usb_probe_interface - got id Nov 23 14:24:24 hame kernel: drivers/usb/misc/speedtch.c: udsl_usb_probe: trying device with vendor=0x6b9, product=0x4061, ifnum 2 The firmware doesn't load, no flashing lights. uhci_result_control: failed with status 44 looks important. It wasn't printing that without the echo 8 /proc/sys/kernel/printk. With a 2.6.10-rc2 kernel things go slightly better. Nov 23 14:27:13 hame kernel: hub 1-0:1.0: state 5 ports 6 chg ffc0 evt 0040 Nov 23 14:27:13 hame kernel: ehci_hcd :00:1d.7: GetStatus port 6 status 001803 POWER sig=j CSC CONNECT Nov 23 14:27:13 hame kernel: hub 1-0:1.0: port 6, status 0501, change 0001, 480 Mb/s Nov 23 14:27:13 hame kernel: hub 1-0:1.0: debounce: port 6: total 100ms stable 100ms status 0x501 Nov 23 14:27:13 hame kernel: ehci_hcd :00:1d.7: port 6 full speed -- companion Nov 23 14:27:13 hame kernel: ehci_hcd :00:1d.7: GetStatus port 6 status 003801 POWER OWNER sig=j CONNECT Nov 23 14:27:13 hame kernel: uhci_hcd :00:1d.2: wakeup_hc Nov 23 14:27:13 hame kernel: hub 4-0:1.0: state 5 ports 2 chg fffc evt 0004 Nov 23 14:27:13 hame kernel: uhci_hcd
[speedtouch] Re: modem_run problem
Hi Andrew, try adding the following line to speedtch.c: #include linux/config.h Add it before the other includes: #include linux/config.h == here #include linux/module.h #include linux/moduleparam.h ... Then recompile and reload the speedtch module. You should then get tons of messages in your logs. Ciao, Duncan. Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: modem_run problem
Yo, yo! Good news. I decided to try different firmware (an old mgmt.o from a speedmgmt tarball that gave a 513.9 KB speedtch-2.bin) with the 2.6.10 kernel and yay! The lights did flash, this was printed in the logs Nov 23 15:29:03 hame kernel: usb 4-2: found stage 1 firmware speedtch-1.bin Nov 23 15:29:03 hame kernel: usb 4-2: found stage 2 firmware speedtch-2.bin Nov 23 15:29:03 hame kernel: ADSL line is synchronising Nov 23 15:29:03 hame kernel: DSL line goes up Nov 23 15:29:03 hame kernel: ADSL line is up (576 Kib/s down | 288 Kib/s up) I just had to run pppd call speedtch to connect with Wanadoo, so it's looking good. Duncan Sands wrote: Hi Andrew, try adding the following line to speedtch.c: #include linux/config.h Add it before the other includes: #include linux/config.h == here #include linux/module.h #include linux/moduleparam.h ... Then recompile and reload the speedtch module. You should then get tons of messages in your logs. Ciao, Duncan. Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED] I've been building Linux From Scratch without using the raw kernel headers for a while now. /usr/include/linux/config.h looks like this #error Compilation aborted. Please read the FAQ for linux-libc-headers package. #error (can be found at http://ep09.pld-linux.org/~mmazur/linux-libc-headers/doc/) I could move it out of the way and temporarily replace it with a symbolic link pointing at /usr/src/linux/include/linux/config.h, but when you say speedtch module, do you mean the kernel driver? I build that into the kernel, so do you mean recompile the kernel? Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: modem_run problem
On Tuesday 23 November 2004 15:47, Andrew Benton wrote: Yo, yo! Good news. I decided to try different firmware (an old mgmt.o from a speedmgmt tarball that gave a 513.9 KB speedtch-2.bin) with the 2.6.10 kernel and yay! The lights did flash, this was printed in the logs Yeah, thats the firmware I used as well and it's working brilliantly for me. ~/dev/speedtouch/speedtouch-1.3.1/src$ ./firmware ../../mgmt.o Firmware info (CRC:0xd80bf9f7, Size:991, Checked: Yes, Alcatel/Thomson Boot block (old)) Firmware info (CRC:0x94a45435, Size:526187, Checked: Yes, 1.3.3 - GNU/Linux - Win32) ** Boot block from ../../mgmt.o: CRC: 0xd80bf9f7 Length: 991 ** Firmware block from ../../mgmt.o: CRC: 0x94a45435 Length: 526187 Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: modem_run problem
On Tuesday 23 November 2004 16:47, Andrew Benton wrote: Yo, yo! Good news. I decided to try different firmware (an old mgmt.o from a speedmgmt tarball that gave a 513.9 KB speedtch-2.bin) with the 2.6.10 kernel and yay! The lights did flash, this was printed in the logs Good news! I thought it might be wrong firmware, but that seemed strange because I guess you were using the same firmware as with modem_run? What revision modem do you have? All the best, Duncan. Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: modem_run problem
Nick Sanders wrote: I'm still trying to auto start pppd on boot. Are you using Fedora Core? Does Fedora have an /etc/rc.d/rc.local script? If so, put something like this on a line in it. pppd call speedtch Change speedtch to whatever the file in /etc/ppp/peers is called. It may try to run the script before the kernel has loaded the firmware and stabilised the line so you may need to make it wait by putting a sleep command on the line before it. Nov 22 10:01:28 gandalf kernel: usb 3-1: control timeout on ep0in Nov 22 10:01:28 gandalf kernel: SpeedTouch: Error -110 fetching device status Nov 22 10:04:53 gandalf kernel: usb 3-1: control timeout on ep0in Nov 22 10:04:53 gandalf kernel: SpeedTouch: Error -110 fetching device status The problem with /etc/hotplug/usb/speedtouch is that its run 3 times I've seen that too. The first time it connects but the next two try (and fail) twenty times. The first modem_run has the modem/interface. I don't know what the answer to that is so I've always used a bootscript. Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: modem_run problem
Actually, with the latest fedora (and vanilla 2.6 kernel for that matter) you don't need modem_run at all since David Woodhouse and I implemented in-kernel firmware loading... You need to put the stage 1 and stage 2 firmware files somewhere in the firmware path (mine are in /usr/local/lib/firmware). The (small) stage 1 firmware should be called speedtch-1.bin; the stage 2 firmware should be called speedtch-2.bin. In order to cater for different modem revisions, you can give the files a more complicated name that includes the major (and optionally minor) modem revision. For example, if you have a stage 2 firmware file that is only for revision four modems, then append .4 to the end: speedtch-2.bin.4 If it is only for revision 4 modems with minor revision 0, then append .4.0: speedtch-2.bin.4.0 The kernel looks first for a file which matches exactly your modems major and minor revision number (.4.0 for example); if not found it tries for one that matches just the major (.4 for example); if not found it tries for one with no revision information. So if you only have one modem, you can simply call the two firmware blobs speedtch-1.bin and speedtch-2.bin and all will be well. I have two modems and in my firmware path I have: speedtch-1.bin speedtch-1.bin.4 speedtch-2.bin speedtch-2.bin.4 All the best, Duncan. Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: modem_run problem
Duncan Sands wrote: Actually, with the latest fedora (and vanilla 2.6 kernel for that matter) you don't need modem_run at all since David Woodhouse and I implemented in-kernel firmware loading... That's great news. But I guess the ppp libatm.so problem wasn't solved, am I right (for Fedora, I mean)? Cheers, Giacomo. Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: modem_run problem
Duncan Sands wrote: Actually, with the latest fedora (and vanilla 2.6 kernel for that matter) you don't need modem_run at all since David Woodhouse and I implemented in-kernel firmware loading... You need to put the stage 1 and stage 2 firmware files somewhere in the firmware path (mine are in /usr/local/lib/firmware). Where is the firmware path defined? Is it hardcoded into the kernel? The (small) stage 1 firmware should be called speedtch-1.bin; the stage 2 firmware should be called speedtch-2.bin. Where can we get the (small) stage 1 firmware? At the moment I'm using the KQD6_3.012 from the Thompson SpeedTouch330_firmware_3012.zip. I have an old green modem and I've only ever needed one firmware file. I'd like to try this kernel firmware loading as modem_run doesn't always succeed in loading the firmware. It used to, but lately (since the 2.6.7 kernel?) it sometimes fails. Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: modem_run problem
On Monday 22 November 2004 10:23, Andrew Benton wrote:
Duncan Sands wrote:
Actually, with the latest fedora (and vanilla 2.6 kernel for
that matter) you don't need modem_run at all since David Woodhouse
and I implemented in-kernel firmware loading... You need to put
the stage 1 and stage 2 firmware files somewhere in the firmware
path (mine are in /usr/local/lib/firmware).
Where is the firmware path defined? Is it hardcoded into the kernel?
See FIRMWARE_DIR in /etc/hotplug/firmware.agent
The (small) stage 1
firmware should be called speedtch-1.bin; the stage 2 firmware
should be called speedtch-2.bin.
Where can we get the (small) stage 1 firmware? At the moment I'm using
the KQD6_3.012 from the Thompson SpeedTouch330_firmware_3012.zip. I have
an old green modem and I've only ever needed one firmware file. I'd like
to try this kernel firmware loading as modem_run doesn't always succeed
in loading the firmware. It used to, but lately (since the 2.6.7
kernel?) it sometimes fails.
Compile the following program (consisting of firmware.h and firmware.c) using
gcc -o firmware firmware.c -DSTANDALONE_EXTRACTER
Then do
./firmware KQD6_3.012
This will create speedtch-1.bin and speedtch-2.bin.
All the best,
Duncan.
=== firmware.h:
#ifndef __FIRMWARE_H__
#define __FIRMWARE_H__
typedef struct
{
unsigned long crc;
unsigned long length;
const char *id;
} stusb_firmware_id_t;
typedef struct
{
unsigned char *phase1;
unsigned char *phase2;
unsigned long phase1_length;
unsigned long phase2_length;
} stusb_firmware_t;
stusb_firmware_t *
extract_firmware(const char *boot_file, const char *firm_file, int rev4);
void
free_firmware(stusb_firmware_t *f);
#endif
=== firmware.c:
/*
* ALCATEL SpeedTouch USB modem microcode extract utility
* Copyright (C) 2001 Benoit PAPILLAULT
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License
* as published by the Free Software Foundation; either version 2
* of the License, or (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, write to the Free Software
* Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
*
* Author : Edouard Gomez [EMAIL PROTECTED]
* Creation : 14/02/2004
*
* Searching for the microcode is done in a two step process:
* - the boot code.
* - the main firmware.
*
* The bootcode is always loaded at 0x in the modem RAM, so we look for
* this base address mixed in a special file format signature. The end of the
* boot code is marked by a command that tells the ARM to jump at the base
* address and execute (aka boot)
*
* The base address of the main firmware depends on the modem revision (as of
* 2004-02-14, only rev4 is different). The end pattern is also a jump command.
*
* $Id: firmware.c,v 1.1 2004/10/15 15:00:56 duncan Exp $
*/
#ifndef _FIRMWARE_C_
#define _FIRMWARE_C_
#ifndef STANDALONE_EXTRACTER
#include pppoa3.h
#endif
#include crc.h
#include firmware.h
#include stdio.h
#include stdlib.h
#include string.h
#include unistd.h
#include fcntl.h
#include sys/stat.h
/*
* Local Prototypes
*/
static stusb_firmware_t *
extract_firmware_phase(const char *file,
const unsigned char *start_pattern,
const unsigned char *end_pattern,
const int pattern_length,
const stusb_firmware_id_t *ids);
static int
search_pattern(const unsigned char *buffer,
const unsigned char *pattern,
const int buffer_length,
const int pattern_length);
static unsigned char *
load_file(const char * file, int * size);
/**
* Main Lib Function
**/
/*
* Function: check_firmware
* Results : return 1 if the firmware is OK, 0 otherwise.
* Description : check that the firmware found is valid
*/
int check_firmware(unsigned char * buf, int len)
{
unsigned char * current_block;
int remaining_len;
unsigned int addr;
unsigned int size, extra_size;
int boot_block_seen = 0;
int last_block_seen = 0;
current_block = buf;
remaining_len = len;
while (remaining_len 0) {
if (remaining_len 8) {
[speedtouch] Re: modem_run problem
andy:~$ gcc -o firmware firmware.c -DSTANDALONE_EXTRACTER firmware.c:43:17: crc.h: No such file or directory firmware.c:529:17: crc.c: No such file or directory andy:~$ Looks like it needs crc.c and crc.h. Yes, sorry about that. I've included all needed files at the end of this email. So I untarred the speedtouch-1.3.1, cd'd into speedtouch-1.3.1/src and then did gcc -o firmware firmware.c -DSTANDALONE_EXTRACTER That worked fine. Except that it's not quite the same firmware.c... Then do ./firmware KQD6_3.012 This will create speedtch-1.bin and speedtch-2.bin. I copied the KQD6_3.012 into speedtouch-1.3.1/src and then did andy:~/Desktop/speedtouch-1.3.1/src$ ./firmware KQD6_3.012 Firmware info (CRC:0xd80bf9f7, Size:991, Checked: Yes, Alcatel/Thomson Boot block (old)) Firmware info (CRC:0x78039fed, Size:762650, Checked: Yes, 3.0.6 - MacOSX - Win32) ** Boot block from KQD6_3.012: CRC: 0xd80bf9f7 Length: 991 ** Firmware block from KQD6_3.012: CRC: 0x78039fed Length: 762650 andy:~/Desktop/speedtouch-1.3.1/src$ That made two files, boot.bin and firmware.bin. Were these the speedtch-1.bin and speedtch-2.bin that you were referring to? Yes. The difference between the firmware.c I supplied and the one from the user space driver is simply that it names the files speedtch-1.bin etc. I renamed them speedtch-1.bin (the small one, 991 bytes) and speedtch-2.bin and copied them to /lib/firmware. But when I reboot, no joy, the firmware doesn't load. I think I'm getting close here but I'm not sure. Perhaps the problem is with hotplug? If you compile your kernel with CONFIG_USB_DEBUG=y then you will get a pile of maybe helpful messages in your system logs. Even without this config setting, various messages are printed so please check the logs. Ciao, Duncan. === crc.h /* * ALCATEL SpeedTouch USB modem utility : CRC lib * Copyright (C) 2001 Edouard Gomez * * This program is free software; you can redistribute it and/or * modify it under the terms of the GNU General Public License * as published by the Free Software Foundation; either version 2 * of the License, or (at your option) any later version. * * This program is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU General Public License for more details. * * You should have received a copy of the GNU General Public License * along with this program; if not, write to the Free Software * Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. * * Author : Edouard Gomez ([EMAIL PROTECTED]) * Creation : 08/08/2001 * * $Id: crc.h,v 1.1 2004/10/15 15:00:56 duncan Exp $ */ #ifndef _CRC_H_ #define _CRC_H_ /** * Constants **/ #define AAL5_CRC32_REMAINDER 0xCBF43926 #define AAL5_CRC32_INITIAL 0x #define ATM_HEADER_REMAINDER 0x107 #define ATM_HEADER_COSET_LEADER 0x055 /** * Prototype **/ extern unsigned int aal5_calc_crc(unsigned char *mem, int len, unsigned int initial); extern unsigned char atm_calc_hec(unsigned char *header); #endif === crc.c /* * ALCATEL SpeedTouch USB modem utility : CRC lib * Copyright (C) 2001 Edouard Gomez * * This program is free software; you can redistribute it and/or * modify it under the terms of the GNU General Public License * as published by the Free Software Foundation; either version 2 * of the License, or (at your option) any later version. * * This program is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the * GNU General Public License for more details. * * You should have received a copy of the GNU General Public License * along with this program; if not, write to the Free Software * Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. * * Author : Edouard Gomez ([EMAIL PROTECTED]) * Creation : 08/08/2001 * * $Id: crc.c,v 1.1 2004/10/15 15:00:56 duncan Exp $ */ #ifndef _CRC_C_ #define _CRC_C_ /* Some stuff */ #include crc.h /** * Macros (This is used to speedup code in the calc_crc first while loop) **/ #define DO1(c, crc) ((crc) = crc32tab[((unsigned int)((crc)24) ^ (*c++)) 0xff] ^ ((crc) 8)) #define DO2(c, crc) DO1(c, crc); DO1(c, crc); #define DO4(c, crc) DO2(c, crc); DO2(c, crc); #define DO8(c, crc) DO4(c, crc); DO4(c,
[speedtouch] Re: modem_run problem
Duncan Sands wrote: Yes. The difference between the firmware.c I supplied and the one from the user space driver is simply that it names the files speedtch-1.bin etc. Hmm...they're still coming out as boot.bin and firmware.bin... If you compile your kernel with CONFIG_USB_DEBUG=y then you will get a pile of maybe helpful messages in your system logs. Even without this config setting, various messages are printed so please check the logs. I had already compiled the kernel with those settings and I checked the system log before I sent my last message but none of it looked relevant. I was going to copy and paste a load of it but they were all normal messages. They are there when I reboot and run modem_run with a bootscript, except in that case there are the extra messages concerned with modem_run connecting Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: modem_run problem
On Monday 22 November 2004 08:02, Duncan Sands wrote: Actually, with the latest fedora (and vanilla 2.6 kernel for that matter) you don't need modem_run at all since David Woodhouse and I implemented in-kernel firmware loading... You need to put the stage 1 and stage 2 firmware files somewhere in the firmware path (mine are in /usr/local/lib/firmware). The (small) stage 1 firmware should be called speedtch-1.bin; the stage 2 firmware should be called speedtch-2.bin. Thank you this worked brilliantly. What's the best way of starting pppd automatically? I was starting it through /etc/hotplug/speedtouch. Are there any disadvantages to doing it this way compared using modem_run? Thanks Nick Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: modem_run problem
Are there any disadvantages to doing it this way compared using modem_run? I don't know of any [*]. All the best, Duncan. [*] I know of a bug in the kernel module which might bite you, but probably not. Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: modem_run problem
On Monday 22 November 2004 18:18, Andrew Benton wrote: Duncan Sands wrote: Yes. The difference between the firmware.c I supplied and the one from the user space driver is simply that it names the files speedtch-1.bin etc. Hmm...they're still coming out as boot.bin and firmware.bin... Hmmm, yes it looks like I only dreamt I made that change. Anyway, boot.bin becomes speedtch-1.bin, firmware.bin becomes speedtch-2.bin. If you compile your kernel with CONFIG_USB_DEBUG=y then you will get a pile of maybe helpful messages in your system logs. Even without this config setting, various messages are printed so please check the logs. I had already compiled the kernel with those settings and I checked the system log before I sent my last message but none of it looked relevant. I was going to copy and paste a load of it but they were all normal messages. They are there when I reboot and run modem_run with a bootscript, except in that case there are the extra messages concerned with modem_run connecting This is what I see when plugging in a revision 0 modem: usb 4-1: new full speed USB device using uhci_hcd and address 4 usb 4-1: ep0 maxpacket = 8 usb 4-1: new device strings: Mfr=1, Product=2, SerialNumber=3 usb 4-1: default language 0x0409 usb 4-1: Product: Speed Touch USB usb 4-1: Manufacturer: ALCATEL usb 4-1: SerialNumber: 0090D02C2C5A usb 4-1: hotplug usb 4-1: adding 4-1:1.0 (config #1, interface 0) usb 4-1:1.0: hotplug usb 4-1: adding 4-1:1.1 (config #1, interface 1) usb 4-1:1.1: hotplug usb 4-1: adding 4-1:1.2 (config #1, interface 2) usb 4-1:1.2: hotplug speedtch 4-1:1.0: usb_probe_interface speedtch 4-1:1.0: usb_probe_interface - got id speedtch 4-1:1.1: usb_probe_interface speedtch 4-1:1.1: usb_probe_interface - got id usb 4-1: modprobe timed out on ep0in speedtch 4-1:1.2: usb_probe_interface speedtch 4-1:1.2: usb_probe_interface - got id usbcore: registered new driver speedtch usb 4-1: found stage 1 firmware speedtch-1.bin usb 4-1: found stage 2 firmware speedtch-2.bin Note the last two lines. The are printed with priority KERN_INFO, so may not make it to your log files depending on how you configured your machine. Try doing this: echo 8 /proc/sys/kernel/printk Also, what kernel/module version are you using? Ciao, Duncan. Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: modem_run problem
Selon [EMAIL PROTECTED] [EMAIL PROTECTED]: Hi everyone, I want to thank everybody who helped me and especially Aad: I'm writing this mail from my Fedora system!! Thank you a lot! I used linux-atm-2.4.1-1.i386.rpm (thank you Gilles Espinasse) and I have not intalled the ppp daemon that comes with the speedbundle, I'm using the one that comes with Fedora. But... there's another problem: I have my /var/log/messages continuosly filled by this two lines: Nov 18 12:22:50 localhost modem_run[1720]: Error reading interrupts Nov 18 12:22:50 localhost kernel: usb 3-1: usbfs: process 1720 (modem_run) did not claim interface 0 before use They even fill the screen during the boot. I found a dirty solution: kill -9 modem_run pid. Does somebody know which is the cause of this problem and a better solution for this? Regards, Marco Antonelli Did you have another peripheral connected on the same usb controller? Gilles Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: modem_run problem
Gilles wrote: Did you have another peripheral connected on the same usb controller? Gilles No, the speedtouch modem is the only USB device I have Libero ADSL: navighi gratis a 1.2 Mega, senza canone e costi di attivazione. Abbonati subito su http://www.libero.it Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: modem_run problem
Hi, I have the same problem with messages during boot and shutdown (and probably also during operation): Nov 18 12:22:50 localhost kernel: usb x-y: usbfs: process (modem_run) did not claim interface 0 before use So if somebody knows how to get rid if them, please let us know... Aad On Thu, 2004-11-18 at 12:50, [EMAIL PROTECTED] wrote: Hi everyone, I want to thank everybody who helped me and especially Aad: I'm writing this mail from my Fedora system!! Thank you a lot! I used linux-atm-2.4.1-1.i386.rpm (thank you Gilles Espinasse) and I have not intalled the ppp daemon that comes with the speedbundle, I'm using the one that comes with Fedora. But... there's another problem: I have my /var/log/messages continuosly filled by this two lines: Nov 18 12:22:50 localhost modem_run[1720]: Error reading interrupts Nov 18 12:22:50 localhost kernel: usb 3-1: usbfs: process 1720 (modem_run) did not claim interface 0 before use They even fill the screen during the boot. I found a dirty solution: kill -9 modem_run pid. Does somebody know which is the cause of this problem and a better solution for this? Regards, Marco Antonelli Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: modem_run problem
Aad Rijnberg wrote: I have the same problem with messages during boot and shutdown (and probably also during operation): Nov 18 12:22:50 localhost kernel: usb x-y: usbfs: process (modem_run) did not claim interface 0 before use So if somebody knows how to get rid if them, please let us know... What version of modem_run are you using? The one in the speedtouch-1.2.tar.gz tarball http://sourceforge.net/project/showfiles.php?group_id=32758package_id=28264 is working well for me. If you're using the speedbundle package you can untar the speedtouch-1.2 folder, rename it firmware_loader and use it to replace the firmware_loader folder in the speedbundle. Or if you've got the speedbundle compiled and installed you can configure and make the speedtouch package and copy modem_run and pppoa3 from speedtouch-1.2/src into /usr/sbin to replace the ones installed by the speedbundle Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: modem_run problem in mandrake 10.0
I've got the same problem with Mdk 10.0, I had de restart hotplug service and then launch speedtouch script, and it work It's only work with kernel 2.4, with 2.6 kernel, the system crash when trying to restart hotplug service Le sam 26/06/2004 à 20:04, David Bennell a écrit : Hi I am new to linux and I have mandrake 10.0 Iam trying to setup my usb speed touch green frog/stingray adsl modem (Actualy I am trying to set up two and follow the nildram bonded adsl thingy but I must not get ahead of my self) When i run: modem_run -d /proc/bus/usb/004/003 -m -f /usr/lib/firmware -a /usr/lib/bootcode I get this in my syslog: Jun 26 19:45:01 server modem_run[3758]: modem_run version 1.2 started by root uid 0 Jun 26 19:45:01 server kernel: usb 4-2.2: usbfs: interface 1 claimed while 'modem_run' sets config #1 Jun 26 19:45:01 server kernel: usb 4-2.2: usbfs: interface 2 claimed while 'modem_run' sets config #1 Jun 26 19:45:23 server kernel: usb 4-2.2: bulk timeout on ep5in Jun 26 19:45:23 server kernel: usb 4-2.2: usbfs: USBDEVFS_BULK failed ep 0x85 len 512 ret -110 Jun 26 19:45:27 server kernel: usb 4-2.2: usbfs: interface 0 claimed while 'modem_run' sets config #1 Jun 26 19:45:27 server kernel: usb 4-2.2: usbfs: interface 1 claimed while 'modem_run' sets config #1 Jun 26 19:45:27 server kernel: usb 4-2.2: usbfs: interface 2 claimed while 'modem_run' sets config #1 Jun 26 19:45:27 server modem_run[3758]: Another program/driver is already accessing the modem (interface 1 cannot be claimed)... I assume something tryed to access the modem while starting up the system? how do i kill it off? is there something in my kernel i need to change? this was from a fresh re-boot. Thank you, Dave 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: modem_run problem
I've got a problem with my modem_run, i've installed evrything, and i have a script for starting the adsl when the computer turns on. The only problem is that i need to run modem-run twice in order to make it work. The first time i run it, evrything seems to work, the led blinks and then stops..., but pppd says he don't find the device. So i run again modem_run, it makes a time out because the microcode is already loaded, but after when i run ppd, it finally work... What is the problem? I wanna solve it because i want an automatic connection on boot up. Try sleeping for a few seconds before running pppd. Ciao, Duncan. PS: I thought an init script was supplied with the driver... Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]?subject=unsubscribe
[speedtouch] Re: modem_run problem
While reading my own post, i noticed that one of my sentences was a little bit confusing. When i said that my modem led stops, i wanted to said that it stopped blinking and just stayed turnd on. So evrything is normal on that side. About waiting for a while, i've tryied lunching pppd many times after the modem_rum. The only way to make it work is to launch modem-run again. franky _ MSN Messenger : discutez en direct avec vos amis ! http://www.msn.fr/msger/default.asp Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]?subject=unsubscribe
[speedtouch] Re: modem_run problem
On Thursday 06 February 2003 17:41, Francois Saidi wrote: While reading my own post, i noticed that one of my sentences was a little bit confusing. When i said that my modem led stops, i wanted to said that it stopped blinking and just stayed turnd on. So evrything is normal on that side. About waiting for a while, i've tryied lunching pppd many times after the modem_rum. The only way to make it work is to launch modem-run again. Distribution? Kernel? USB controller? Mother's maiden name? Duncan. Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]?subject=unsubscribe
[speedtouch] Re: modem_run problem
Kernel = 2.4.19 Distr = MDK9 USB: T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor= ProdID= Rev= 0.00 S: Product=USB OHCI Root Hub S: SerialNumber=c684 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=ff(vend.) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=06b9 ProdID=4061 Rev= 0.00 S: Manufacturer=ALCATEL S: Product=Speed Touch USB S: SerialNumber=0090D02DEC38 C:* #Ifs= 3 Cfg#= 1 Atr=80 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=00 Driver=usbdevfs E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=50ms I: If#= 1 Alt= 0 #EPs= 0 Cls=ff(vend.) Sub=00 Prot=00 Driver=usbdevfs I: If#= 1 Alt= 1 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=usbdevfs E: Ad=06(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=07(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=87(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms I: If#= 1 Alt= 2 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=usbdevfs E: Ad=06(O) Atr=02(Bulk) MxPS= 32 Ivl=0ms E: Ad=07(O) Atr=02(Bulk) MxPS= 32 Ivl=0ms E: Ad=87(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms I: If#= 1 Alt= 3 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=usbdevfs E: Ad=06(O) Atr=02(Bulk) MxPS= 16 Ivl=0ms E: Ad=07(O) Atr=02(Bulk) MxPS= 16 Ivl=0ms E: Ad=87(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) E: Ad=05(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms E: Ad=85(I) Atr=02(Bulk) MxPS= 8 Ivl=0ms T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor= ProdID= Rev= 0.00 S: Product=USB UHCI Root Hub S: SerialNumber=d800 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms As you can see i've got two usb controller, one on the motherborad the uhci which i don't use ( i could'nt disable it from the bios) and a pci card with an usb controller the ohci on which the modem is linked. I've tried to unload the module (rmmod usb-uhci) of the unused usb controller, but it didn't seem to help franky _ MSN Messenger : discutez en direct avec vos amis ! http://www.msn.fr/msger/default.asp Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]?subject=unsubscribe
