>From Gilles
>Usually this is because no IRQ is attributed for usb.
>It should be allowed in the bios settings.
    
The IRQ's are enabled for usb use in BIOS

I have a PC with 2 usb socket and using the modem on Windows with no probelm.I tested 
the modem on both hubs and using only 1 usb device.So the possibility of broken hub or 
modem is excluded.
Not enough power ONLY in Relation to Linux driver, its perhaps an incompatibility 
between Linux driver/software and hardware.On windows everything is fine.
I believe the problem is software related(hotplug etc) not being able to correctly 
initialise the usb device/modem.

>There is no trace of the Speedtouch kernel driver either, but then
>whether i should be there depends on whether you are using it or 'pppoa3'

No i didn't use the Kernel driver,i just followed the HOWTO at speedtouch.sourceforge

Thanks again for all your help Piercarlo 


----- Original Message ----- 
From: "Piercarlo Grandi" <[EMAIL PROTECTED]>
To: "Linux SpeedTouch" <[EMAIL PROTECTED]>
Sent: Wednesday, December 24, 2003 6:11 PM
Subject: [speedtouch] Re: Modem not found error!


> 
> >>> On Tue, 23 Dec 2003 10:42:10 +0400, "Nawaaz Meerun"
> >>> <[EMAIL PROTECTED]> said:
> 
> [ ... ]
> 
> nmeerun> The device is already mounted: [ ... ]
> 
> Just to make sure: that's a filesystem, which maps devices onto
> ``virtual'' files.
> 
> nmeerun> When i type lsusb,this is the output
> nmeerun> [EMAIL PROTECTED] root]# lsusb
> nmeerun> Unknown line at line 58
> nmeerun> Unknown line at line 2296
> 
> [ ... ]
> 
> Thats sound like unrelated bad news, because probably the errors occur
> while scanning the USB device id table, and that means that you 'lsusb'
> setup is a bit broken. But even so it should _not_ affect the Speedtouch.
> 
>   And tangentially another one of my whines: the above error message
>   don't say which program is emitting the error message, and the name of
>   the file containing the error, and don't even contain the line itself.
>   This reminds me of the famous MS Windows error message "Cannot open
>   file.".  Dim programmers write shoddy open source software too,
>   unfortunately.
> 
> nmeerun> Bus 001 Device 001: ID 0000:0000 [ ... ]
> 
> There is no device id line other than the USB hub. The Speedtouch has
> not successfully attached itself to the USB hub, as this also indicates:
> 
> nmeerun> Nothing happens with this command: grep "Vendor=06b9" /proc/bus/usb/devices
> 
> nmeerun> The contents of /proc/bus/usb/drivers shows this: [ ... ]
> 
> There is no trace of the Speedtouch kernel driver either, but then
> whether i should be there depends on whether you are using it or 'pppoa3'.
> 
> nmeerun> And for /proc/bus/usb/devices: [ ... ]
> nmeerun> P:  Vendor=0000 ProdID=0000 Rev= 0.00
> nmeerun> S:  Product=USB UHCI Root Hub [ ... ]
> 
> No Speedtouch either.
> 
> When I use 'lsusb' the output is:
> 
>   ----------------------------------------------------------------------
>   base# lsusb | sort
>   Bus 001 Device 001: ID 0000:0000  
>   Bus 001 Device 002: ID 044f:b305 ThrustMaster, Inc. 
>   Bus 001 Device 004: ID 06b9:4061 Alcatel Telecom Speed Touch ISDN
>   Bus 002 Device 001: ID 0000:0000  
>   Bus 003 Device 001: ID 0000:0000  
>   Bus 004 Device 001: ID 0000:0000  
>   ----------------------------------------------------------------------
> and with 'grep' the output is:
> 
>   ----------------------------------------------------------------------
>   P:  Vendor=06b9 ProdID=4061 Rev= 0.00
>   ----------------------------------------------------------------------
> 
> (your prodID would be different as your Speedtouch is a different
> model).
> 
> nmeerun> For power supply,when i plug the modem in the usb the 2 lights
> nmeerun> (on modem) blink Red for a moment then stops.So power have to
> nmeerun> be flowing..
> 
> But not necessarily enough to successfully power up the device. Also
> when the device is not yet initialized the two lights ought to be solid
> green.
> 
> nmeerun> And look at the logs: [ ... ]
> nmeerun> Dec 23 09:43:03 localhost kernel: usb_control/bulk_msg: timeout
> nmeerun> Dec 23 09:43:03 localhost kernel: usb.c: USB device not accepting new
> nmeerun> address=2 (error=-110) [ ... ]
> 
> These don't look good either.
> 
> It looks like you have some kind of hardware problem in getting the
> Speedtouch to properly register iself with the USB bus.
> 
> As such, this is a problem that should not be discussed on this mailing
> list, which is about Speedtouch software problems.
> 
> However, just because we are at it: I still think that the most likely
> cause is insufficient power supplied by the USB socket; it could be a
> bad cable, or just a broken Speedtouch, or a broken USB hub.
> 
> The general things to do to sort out a USB registration problem would be:
> 
> * Detach all other USB devices, if any, and try with just the Speedtouch.
>   Perhaps all together they draw more current than is available.
> 
> * Try to plug the Speedtouch into another socket belonging to a
>   different hub. Usually desktop PCs have at least two hubs.
> 
> * Try to buy/borrow a PCI USB card, or a powered external USB hub.
> 
> But, but, now that I think of it, your 'lsusb' output seems to imply
> that your computer has only one USB hub.  Usually desktop systems have
> at least two (for a total of four sockets), and so do PCI USB cards.
> 
> Just about the only computers that have a single hub are laptops.
> Laptops just don't supply enough power to their USB sockets for larger
> devices like a Speedtouch.
> 
> 
> 
> 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]

        

Reply via email to