Activation Codes and Methods, Hardware Details, Sniffing
Post Reply
antoniomontag
Posts: 4
Joined: 15 Jan 2010, 08:53

Huawei 1692 and Fedora 12

Post by antoniomontag » 15 Jan 2010, 09:04

I am trying to make a Huawei1692 dongle work in F12. But when I use
usb_modeswitch device is not switched to modem mode and I get the
attached output.
Any hint?? It was working fine with same conf file in F11.
Using kernel 2.6.31.9-174.fc12.i686.PAE
Confused on hints given in other threads
Tnx

______________________________________________________________________---
usb_modeswitch -W
Reading config file: /etc/usb_modeswitch.conf

* usb_modeswitch: handle USB devices with multiple modes
* Version 1.0.5 (C) Josua Dietze 2009
* Based on libusb 0.1.12

DefaultVendor= 0x12d1
DefaultProduct= 0x1446
TargetVendor= 0x12d1
TargetProduct= 0x140c
TargetClass= not set

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
MessageEndpoint=0x01
MessageContent="55534243000000000000000000000011060000000000000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
Interface=0x00

InquireDevice enabled (default)
Success check enabled, max. wait time 5 seconds

usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 002
usb_os_find_busses: Found 007
usb_os_find_busses: Found 005
usb_os_find_busses: Found 001
usb_os_find_busses: Found 003
usb_os_find_busses: Found 004
usb_os_find_busses: Found 006
usb_os_find_devices: Found 004 on 002
skipping descriptor 0xB
skipped 1 class/vendor specific endpoint descriptors
skipped 5 class/vendor specific interface descriptors
skipping descriptor 0x25
skipped 1 class/vendor specific endpoint descriptors
skipped 9 class/vendor specific interface descriptors
usb_os_find_devices: Found 002 on 002
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 007
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 002 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 003
usb_os_find_devices: Found 001 on 004
usb_os_find_devices: Found 001 on 006
usb_os_find_devices: Found 002 on 006
skipped 1 class/vendor specific interface descriptors
error obtaining child information: Inappropriate ioctl for device

Looking for target devices ...
No devices in target mode or class found
Looking for default devices ...
Found default devices (1)
Accessing device 002 on bus 001 ...
Using endpoints 0x01 (out) and 0x81 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
OK, driver found ("usbfs")
OK, driver "usbfs" detached
Check that you have permissions to write to 001/002 and, if you don't,
that you set up hotplug (http://linux-hotplug.sourceforge.net/)
correctly.
USB error: could not claim interface 0: Device or resource busy
Could not claim interface (error -16). Skipping device inquiry
USB error: could not release intf 0: Invalid argument

Device description data (identification)
-------------------------
Manufacturer: HUAWEI Technology
Product: HUAWEI Mobile
Serial No.: not provided


-------------------------
Looking for active driver ...
USB error: could not get bound driver: No data available
No driver found. Either detached before or never attached
Setting up communication with interface 0 ...
Trying to send the message to endpoint 0x01 ...
Sending the message returned error -110. Trying to continue

Checking for mode switch (max. 5 times, once per second) ...
Waiting for original device to vanish ...
Waiting for original device to vanish ...
Waiting for original device to vanish ...
Waiting for original device to vanish ...
Waiting for original device to vanish ...
Original device still present after the timeout

Mode switch most likely failed. Bye.

Josh
Site Admin
Posts: 6570
Joined: 03 Nov 2007, 00:30

Post by Josh » 15 Jan 2010, 09:45

Did you run as root or with sudo ?

antoniomontag
Posts: 4
Joined: 15 Jan 2010, 08:53

Post by antoniomontag » 15 Jan 2010, 09:51

as root, as I did in Fedora 11 where with same setup, dongle is working fine.

I guess that something changed (but what??), as I think that at early stages of Fedora 12, dongle was working.

At the moment when I want to surf mobile, I fire a Fedora 11

Josh
Site Admin
Posts: 6570
Joined: 03 Nov 2007, 00:30

Post by Josh » 15 Jan 2010, 16:47

I'll check tonight on my installation of Fedora 12. As it happens, I bought myself a Huawei E161 which has the same ID and the same switching command.

I hope I'll be able to get the same error. 8)

antoniomontag
Posts: 4
Joined: 15 Jan 2010, 08:53

Post by antoniomontag » 15 Jan 2010, 16:53

tnx

I guess that it is something connected to an old usb_modeswitch release that is fighting with udev-145-14.fc12.i686

waiting for your experiments.Tnx again

Josh
Site Admin
Posts: 6570
Joined: 03 Nov 2007, 00:30

Post by Josh » 17 Jan 2010, 13:19

Sorry for the delay, there were so many pressing issues at the same time ...

Unfortunately (for you) I had no trouble whatsoever getting my E161 to switch properly with Fedora 12.
I use the standard kernel though (2.6.31.5-127.fc12.i686). I run a standard (network) installation with all recent updates included.

There is an entry for our ID (12d1:1446) in
"/lib/udev/rules.d/61-option-modem-modeswitch.rules".
On my system the modem switched even with usb_modeswitch not installed.

For the experiments I disabled the provided entries.


antoniomontag
Posts: 4
Joined: 15 Jan 2010, 08:53

Post by antoniomontag » 17 Jan 2010, 15:11

Josh

it works, after disabling entry in lib/udev/rules.d/61-option-modem-modeswitch.rules for our dongle, as for you suggestion, with no usb_modeswitch (I mean usb_modeswitch is installed, but was not started)

Now I have my provider connection available in my Applet Network Manager.

Tnx for your great help

Post Reply