X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from mail-ie0-f170.google.com (mail-ie0-f170.google.com [209.85.223.170]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id 53BC5DC0088 for ; Sat, 4 May 2013 07:10:19 +0000 (UTC) Received: by mail-ie0-f170.google.com with SMTP id aq17so2607182iec.1 for ; Sat, 04 May 2013 00:10:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=qUH3VJbtnN1z5qlYZ7hWx/CbRe6TIs8tyiTcA/1iaDk=; b=sLnbbQRsSnXwbkoBu7rwD4fL3FzPbaKbC4yZM8/ws3KIL75hYp2UmZPvrE7K1gicZm 5H+17NSPvhK2eH9wtWRaMfhESMJPjp8NJ0HM6xW+vMPDVNLvtILQPyy56ZJTliEJK8nu 2PewXQwzN3NpaZFA7x706WBVncjgseDXvdwJcalAI9jl1F00jLCCFNdLQUnhG5mv4zs3 xfqFGgO5x+exbSEp++/S5qlV739RFMQGV3CPolyvhGAVg2fTtUlVnocQs41VstcIJ03f 4YS88zACihWXOhfwJzLIYW7oBJVUhF9aOyNQ++iNs9d1AXpGvi8ss9zE6nKz1UUzzl5+ 5JKA== X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 X-Received: by 10.50.120.102 with SMTP id lb6mr348152igb.103.1367651418880; Sat, 04 May 2013 00:10:18 -0700 (PDT) Received: by 10.64.20.45 with HTTP; Sat, 4 May 2013 00:10:18 -0700 (PDT) In-Reply-To: <5183C53A.5030300@arcor.de> References: <5183C53A.5030300@arcor.de> Date: Sat, 4 May 2013 09:10:18 +0200 Message-ID: Subject: Re: [alpine-devel] [2.6rc2] USB 3G Modems Not Working, Anymore From: Carlo Landmeter To: Der Tiger Cc: alpine-devel@lists.alpinelinux.org Content-Type: multipart/alternative; boundary=047d7bd756deffbfc904dbdf2801 --047d7bd756deffbfc904dbdf2801 Content-Type: text/plain; charset=ISO-8859-1 On Fri, May 3, 2013 at 4:10 PM, Der Tiger wrote: > Hi, > > Looks like there is a problem with USB modems (in my case a Huawei > E372) on 2.6rc1 and 2.6rc2. The modem is recognized and listed in > /var/log/messages, as well as with 'lsusb', but no /dev/ttyUSB* special > files are created. I had no such troubles on 2.5. Between the working > 2.5 and the current, non-operating state there where only two 'sudo apk > -U upgrade' (to 2.6rc1 and later 2.6rc2, both with reboot afterwards) > and no other changes to the Alpine system. > > At this stage, I cannot pinpoint the problem. Kernel module 'usbserial' > is loaded and a generic USB-to-serial adapter is recognized and the > corresponding special file created. My educated guess therefore is an > issue with 'usb_modeswitch' which can access the USB modem, but exits with: > > > 8<------------------------------------------------------->8 > alpine:~$ sudo usb_modeswitch -v 12d1 -p 1505 -H > > Looking for default devices ... > found matching product ID > adding device > Found device in default mode, class or configuration (1) > Accessing device 003 on bus 005 ... > Getting the current device configuration ... > OK, got current device configuration (1) > Using interface number 0 > Using endpoints 0x01 (out) and 0x81 (in) > Inquiring device details; driver will be detached ... > Looking for active driver ... > OK, driver found; name unknown, limitation of libusb1 > OK, driver "unkown" detached > > SCSI inquiry data (for identification) > ------------------------- > Vendor String: HUAWEI > Model String: Mass Storage > Revision String: 2.31 > ------------------------- > > USB description data (for identification) > ------------------------- > Manufacturer: Huawei Technologies > Product: HUAWEI Mobile > Serial No.: not provided > ------------------------- > Sending Huawei control message ... > Error: sending Huawei control message failed (error -32). Aborting. > 8<------------------------------------------------------->8 > > I can't tell, if this is caused by the kernel or the usb_modeswitch > tool. The modem itself is working flawlessly as proofed by connecting it > to my laptop. A different type of Huawei modem (namely E169) causes the > same problem on Alpine 2.6rc*. > > I'll gladly provide any information required to solve the problem. > > Any idea, what's causing this? > Do you try this with udev? > > Kind Regards, Tiger > > > --- > Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org > Help: alpine-devel+help@lists.alpinelinux.org > --- > > --047d7bd756deffbfc904dbdf2801 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Fri, May 3, 2013 at 4:10 PM, Der Tige= r <der.tiger.alpine@arcor.de> wrote:
Hi,

Looks like there is a problem with USB modems (in my case a Huawei
E372) =A0on 2.6rc1 and 2.6rc2. The modem is recognized and listed in
/var/log/messages, as well as with 'lsusb', but no /dev/ttyUSB* spe= cial
files are created. I had no such troubles on 2.5. Between the working
2.5 and the current, non-operating state there where only two 'sudo apk=
-U upgrade' (to 2.6rc1 and later 2.6rc2, both with reboot afterwards) and no other changes to the Alpine system.

At this stage, I cannot pinpoint the problem. Kernel module 'usbserial&= #39;
is loaded and a generic USB-to-serial adapter is recognized and the
corresponding special file created. My educated guess therefore is an
issue with 'usb_modeswitch' which can access the USB modem, but exi= ts with:


8<------------------------------------------------------->8
alpine:~$ sudo usb_modeswitch -v 12d1 -p 1505 -H

Looking for default devices ...
=A0 =A0found matching product ID
=A0 =A0adding device
=A0Found device in default mode, class or configuration (1)
Accessing device 003 on bus 005 ...
Getting the current device configuration ...
=A0OK, got current device configuration (1)
Using interface number 0
Using endpoints 0x01 (out) and 0x81 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
=A0OK, driver found; name unknown, limitation of libusb1
=A0OK, driver "unkown" detached

SCSI inquiry data (for identification)
-------------------------
=A0 Vendor String: HUAWEI
=A0 =A0Model String: Mass Storage
Revision String: 2.31
-------------------------

USB description data (for identification)
-------------------------
Manufacturer: Huawei Technologies
=A0 =A0 =A0Product: HUAWEI Mobile
=A0 Serial No.: not provided
-------------------------
Sending Huawei control message ...
Error: sending Huawei control message failed (error -32). Aborting.
8<------------------------------------------------------->8

I can't tell, if this is caused by the kernel or the usb_modeswitch
tool. The modem itself is working flawlessly as proofed by connecting it to my laptop. A different type of Huawei modem (namely E169) causes the
same problem on Alpine 2.6rc*.

I'll gladly provide any information required to solve the problem.

Any idea, what's causing this?

Do y= ou try this with udev?

=A0

Kind Regards, Tiger


---
Unsubscribe: =A0alpine-devel+unsubscribe@lists.alpinelinux.org
Help: =A0 =A0 =A0 =A0 alpine-devel+help@lists.alpinelinux.org
---


--047d7bd756deffbfc904dbdf2801-- --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---