[Gllug] suse 12.1 not connect online

[John Hearns]

unable to enumerate usb device number on port 2 using ehci hcd


I think I have seen something similar - forgive me if I'm wrong, I'm
trying to find the trouble ticket I filed on it.
When you remove USB devices, such as keyboards and micem  and re-plug
them in with some varieties of USB the devices are not

The fix is to add this parameter to the kernel options in grub
usbcore.use_both_schemes=1


>From /usr/src/linux/drivers/usb/core/hub.c

*
 * As of 2.6.10 we introduce a new USB device initialization scheme which
 * closely resembles the way Windows works.  Hopefully it will be compatible
 * with a wider range of devices than the old scheme.  However some previously
 * working devices may start giving rise to "device not accepting address"
 * errors; if that happens the user can try the old scheme by adjusting the
 * following module parameters.
 *
 * For maximum flexibility there are two boolean parameters to control the
 * hub driver's behavior.  On the first initialization attempt, if the
 * "old_scheme_first" parameter is set then the old scheme will be used,
 * otherwise the new scheme is used.  If that fails and "use_both_schemes"
 * is set, then the driver will make another attempt, using the other scheme.
 */

Actually, that is a different message. But you are definitely having
USB problems.



Does this modem requite the usb modeswitch commands to switch it from
being a mass storage device to acting as a modem?


On 23/04/2012, Ian Northeast <ian at house-from-hell.demon.co.uk> wrote:
> Ken Smith wrote:
>
>> It used to be the case that Virgin Media's DHCP would only issue an IP
>> address to the machine whose MAC address they had seen before. So if you
>> swap the connected device VM's DHCP won't give it an IP address.
>> Nonsense to my thinking, but seemingly if you shut down VM's modem and
>> leave it for half an hour or so and then start it up again it appears to
>> forget the previous MAC address and allow a new device to connect. I had
>> thought that had dispensed with this but in some areas it might still
>> happen.
>
> IME it's necessary to restart the cable modem to attach a new client but
> there's no need to leave it off for any length of time. Just restarting
> it does it. This has been the case for a few years now, it did indeed
> used to (mis)behave as you say. I'm not sure why it's necessary to
> restart it at all, I think it may be a rather crude way to ensure that
> only one client can be connected at a time.
>
> Someone mentioned VM being useless earlier. Also IME, they are not. The
> actual service is pretty good, and I normally get my full 20Mb/s. If you
> are unfortunate enough to have to call their support line they are
> totally useless though.
>
> In response to another previous comment, I have been connecting to VM
> with OpenBSD and now Linux for 10 years now and I've not had any issue
> with that. Of course, I've never actually mentioned what I'm using, I
> just say "router".
>
> Regards, Ian
> --
> Gllug mailing list  -  Gllug at gllug.org.uk
> http://lists.gllug.org.uk/mailman/listinfo/gllug
>
--
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug