Bug#574270: usb-modeswitch-data: MF636 not working after upgrade

2010-03-19 Thread Josua Dietze

lkml,

can you try to replace the 19d2:2000 file by copying the 
19d2:2000:uPr=USB_ZTE file to 19d2:2000?


This will result in a different switching command.
The trouble with eject is that sometimes you have to wait 
for the storage device being ready to use, and often desktop 
environments do mount the storage, further complicating the 
switch.


BTW, I never had a ZTE device to test and sometimes the 
reports were contradicting ...



Josua Dietze




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#574270: usb-modeswitch-data: MF636 not working after upgrade

2010-03-18 Thread lkml
  Hi,

# I don't entirely get your bugreport… did it work with previous versions of 
usb-
# modeswitch-data ? 
It once worked. Unsure whether that was with a previous usb-modeswitch-data 
version
or even before installing usb-modeswitch-data at all.

# What have you done to make your device work ? Did you delete 
# /etc/usb_modeswitch.d/19d2\:2000 ?
Yep, /etc/usb_modeswitch.d/19d2\:2000 must be out of tree.

# The changelog contains several changes about those devices (that seem to be 
the 
# most problematic one):
# 
# usb-modeswitch-data (20100221-1) unstable; urgency=low
#   * New upstream release.
# + New devices
#   (…)
#   [19d2:2000] ZTE MF626 and others
I'm suspecting this change to have introduced the discontinuity. But I am not 
100%
sure about it.
 
# usb-modeswitch-data (20100203-1) unstable; urgency=low
#   * New upstream release.
# × Devices updates
#   [19d2:2000] Re-arrange target product lists
This was too early. Isn't probably it.

The specified device in my report works w/o any usb modeswitching it seems. 

Behaviour:
- plug it in.
- red LED
- NoCD feature active
- a second later NoCD is removed by the stick itself
- LED off
- red LED
- usb storage device comes up (microSD)
- roughly 10 seconds past
- ttyUSB? creation time
- roughly 15 seconds past
- wvdial sets PIN
- blue LED
- wvdial dialin
- blue LED flashing

Thanks for your prompt response.

Cheers




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#574270: usb-modeswitch-data: MF636 not working after upgrade

2010-03-18 Thread Didier 'OdyX' Raboud
Le Jeudi 18 Mars 2010 15:50:59 l...@think-future.de, vous avez écrit :
 # What have you done to make your device work ? Did you delete
 # /etc/usb_modeswitch.d/19d2\:2000 ?
 Yep, /etc/usb_modeswitch.d/19d2\:2000 must be out of tree.
 
 # The changelog contains several changes about those devices (that seem to
 be the # most problematic one):
 #
 # usb-modeswitch-data (20100221-1) unstable; urgency=low
 #   * New upstream release.
 # + New devices
 #   (…)
 #   [19d2:2000] ZTE MF626 and others
 I'm suspecting this change to have introduced the discontinuity. But I am
 not 100% sure about it.

Hi again, 

I investigated a bit, and it happends that udev (installed on your system) 
ships 
two files:

/lib/udev/modem-modeswitch
/lib/udev/rules.d/61-option-modem-modeswitch.rules

which happen to switch the 19d2:2000 devices. So we have a clear functionality 
overlap here, which in turn makes your device not switch at the end.

I discussed this with the udev maintainer over IRC and he confirmed me that 
modem-modeswitch is meant to be removed soon. He asked me to rise this to 
upstream, which will be done right now.

Nevertheless, I don't know how to fix this bug without breaking the 19d2\:2000 
switching facility.

 Thanks for your prompt response.
 
 Cheers

Could you please try to plus your device in within the 4 cases below

1) /lib/udev/rules.d/61-mobile-action.rules present 
   /etc/usb_modeswitch.d/19d2\:2000 present
   (should fail as you reported)

2) /lib/udev/rules.d/61-mobile-action.rules present 
   /etc/usb_modeswitch.d/19d2\:2000 removed
   (should work as you reported)

3) /lib/udev/rules.d/61-mobile-action.rules absent 
   /etc/usb_modeswitch.d/19d2\:2000 present
   (I guess it should work)

4) /lib/udev/rules.d/61-mobile-action.rules absent
   /etc/usb_modeswitch.d/19d2\:2000 absent
  (I guess it should not work)

Thanks in advance, best regards, 

OdyX

-- 
Didier Raboud, proud Debian Maintainer (DM).
CH-1020 Renens
did...@raboud.com


signature.asc
Description: This is a digitally signed message part.


Bug#574270: usb-modeswitch-data: MF636 not working after upgrade

2010-03-18 Thread lkml
  Hi,

# /lib/udev/modem-modeswitch
# /lib/udev/rules.d/61-option-modem-modeswitch.rules

I didn't investigate further, and here you lost me. Why do these affect this 
19d2:2000 
device version here? /lib/udev/rules.d/61-option-modem-modeswitch.rules has no 
19d2 context here.
And (w/o having fully disected) modem-modeswitch doesn't seem to get called 
when plugging the
device. I mean, can't see a logical path in udev where modem-modeswitch gets 
called, when
this device is plugged. Maybe I didn't bother too hard to find one..

# Nevertheless, I don't know how to fix this bug without breaking the 
19d2\:2000 
# switching facility.
I don't have a switching problem w/o the one file I needed to remove. W/o 
usb-modeswitch 
everything worked flawlessly to the point. Once usb-modeswitch got on the disk 
everything broke. So basically I don't need it. And the time is near where my 
disk 
will be lighter bit of bits by the size of usb-modeswitch..

# Could you please try to plus your device in within the 4 cases below
Well, ok, let's work this out..

# 1) /lib/udev/rules.d/61-mobile-action.rules present 
#/etc/usb_modeswitch.d/19d2\:2000 present
#(should fail as you reported)
Not working. 

usb 1-3: new high speed USB device using ehci_
hcd and address 73
usb 1-3: New USB device found, idVendor=19d2,idProduct=2000
usb 1-3: New USB device strings: Mfr=3, Product=2, SerialNumber=4
usb 1-3: Product: ONDA WCDMA Technologies MSM
usb 1-3: Manufacturer: ONDA,Incorporated
usb 1-3: SerialNumber: P673M2ODCD01 
scsi78 : usb-storage 1-3:1.0 
usb-modeswitch: switching 19d2:2000 (ONDA,Incorporated: ONDA WCDMA Technologies 
MSM)

No storage device, no modem device.

# 2) /lib/udev/rules.d/61-mobile-action.rules present 
#/etc/usb_modeswitch.d/19d2\:2000 removed
#(should work as you reported)
Working.

usb 1-3: new high speed USB device using ehci_hcd and address 74
usb 1-3: New USB device found, idVendor=19d2, idProduct=2000
usb 1-3: New USB device strings: Mfr=3, Product=2, SerialNumber=4
usb 1-3: Product: ONDA WCDMA Technologies MSM
usb 1-3: Manufacturer: ONDA,Incorporated
usb 1-3: SerialNumber: P673M2ODCD01
scsi79 : usb-storage 1-3:1.0
scsi 79:0:0:0: CD-ROMONDA USB SCSI CD-ROM  2.31 PQ: 0 ANSI: 2
sr0: scsi-1 drive
sr 79:0:0:0: Attached scsi CD-ROM sr0
sr 79:0:0:0: Attached scsi generic sg1 type 5
usb 1-3: USB disconnect, address 74
usb 1-3: new high speed USB device using ehci_hcd and address 75
usb 1-3: New USB device found, idVendor=19d2, idProduct=0037
usb 1-3: New USB device strings: Mfr=3, Product=2, SerialNumber=4
usb 1-3: Product: ONDA WCDMA Technologies MSM
usb 1-3: Manufacturer: ONDA,Incorporated
usb 1-3: SerialNumber: P673M2ODCD01
option 1-3:1.0: GSM modem (1-port) converter detected
usb 1-3: GSM modem (1-port) converter now attached to ttyUSB0
option 1-3:1.1: GSM modem (1-port) converter detected
usb 1-3: GSM modem (1-port) converter now attached to ttyUSB1
scsi80 : usb-storage 1-3:1.2
option 1-3:1.3: GSM modem (1-port) converter detected
usb 1-3: GSM modem (1-port) converter now attached to ttyUSB2
scsi 80:0:0:0: Direct-Access ONDA MMC Storage  2.31 PQ: 0 ANSI: 2
sd 80:0:0:0: Attached scsi generic sg1 type 0
sd 80:0:0:0: [sde] Write Protect is off
sd 80:0:0:0: [sde] Mode Sense: 0f 0e 00 00
sd 80:0:0:0: [sde] Assuming drive cache: write through
sd 80:0:0:0: [sde] Assuming drive cache: write through
 sde: sde1
sd 80:0:0:0: [sde] Assuming drive cache: write through
sd 80:0:0:0: [sde] Attached SCSI removable disk

Storage device present, modem device present.

# 3) /lib/udev/rules.d/61-mobile-action.rules absent 
#/etc/usb_modeswitch.d/19d2\:2000 present
#(I guess it should work)

Not working!

usb 1-3: new high speed USB device using ehci_hcd and address 77
usb 1-3: New USB device found, idVendor=19d2, idProduct=2000
usb 1-3: New USB device strings: Mfr=3, Product=2, SerialNumber=4
usb 1-3: Product: ONDA WCDMA Technologies MSM
usb 1-3: Manufacturer: ONDA,Incorporated
usb 1-3: SerialNumber: P673M2ODCD01
scsi82 : usb-storage 1-3:1.0
usb-modeswitch: switching 19d2:2000 (ONDA,Incorporated: ONDA WCDMA Technologies 
MSM)

No storage device, no modem device.

Interesting. The explicit eject in /lib/udev/rules.d/61-mobile-action.rules 
seems to be 
required. So the device itself didn't remove the NoCD but this eject effected 
this?
That's fine with me. But this tiny 19d2:2000 file is a blocker. Not fine with 
me.
 
# 4) /lib/udev/rules.d/61-mobile-action.rules absent
#/etc/usb_modeswitch.d/19d2\:2000 absent
#   (I guess it should not work)

Not working.

usb 1-3: new high speed USB device using ehci_hcd and address 76
usb 1-3: New USB device found, idVendor=19d2, idProduct=2000
usb 1-3: New USB device strings: Mfr=3, Product=2, SerialNumber=4
usb 1-3: Product: ONDA WCDMA Technologies MSM
usb 1-3: Manufacturer: ONDA,Incorporated
usb 1-3: SerialNumber: P673M2ODCD01
scsi81 : usb-storage 1-3:1.0
scsi 81:0:0:0: CD-ROMONDA USB SCSI CD-ROM 

Bug#574270: usb-modeswitch-data: MF636 not working after upgrade

2010-03-17 Thread lkml
Package: usb-modeswitch-data
Version: 20100221-1
Severity: important

Reporting this here for the draisberghof bb requires registration. It's just a 
bad thing to have to get registrated with dozens of boards, wikis, trac or 
whatever and keeping track of software. I seek to contribute but not
waste effort and energy in useless regs and get humbled by 1k more of spam
messages.

Having that said, here's the report:

Device:
- Model: MC503HSA
- Type: MF636

After an usb-modeswitch-data update the modem was unusable as 
usb-modeswitch-data matched idVendor=19d2, idProduct=0037 in 
/etc/usb_modeswitch.d/19d2:2000, no ttyUSB? devices being created.

l /dev/ttyU*
ls: impossibile accedere a /dev/ttyU*: No such file or directory


Logging enabled in /lib/udev/usb_modeswitch: /var/log/usb_modeswitch_1-3\:1.0
The log shows a couple of tentatives exposing the problem with the 
/etc/usb_modeswitch.d/19d2:2000 file. 

Once this file was removed the ttyUSB? devices where created again.

Using debian, usb-modeswitch-data:
dpkg -l usb-modeswitch-data
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ NomeVersioneDescrizione
+++-===-===-==
ii  usb-modeswitch-data 20100221-1  mode switching data 
for usb-modeswitch

dmesg output:
[686354.596155] usb 1-3: new high speed USB device using ehci_hcd and address 52
[686354.713111] usb 1-3: New USB device found, idVendor=19d2, idProduct=0037
[686354.713120] usb 1-3: New USB device strings: Mfr=3, Product=2, 
SerialNumber=4
[686354.713127] usb 1-3: Product: ONDA WCDMA Technologies MSM
[686354.713132] usb 1-3: Manufacturer: ONDA,Incorporated
[686354.713137] usb 1-3: SerialNumber: P673M2ODCD01
[686354.715352] option 1-3:1.0: GSM modem (1-port) converter detected
[686354.715583] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB0
[686354.715758] option 1-3:1.1: GSM modem (1-port) converter detected
[686354.715936] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB1
[686354.717048] scsi54 : usb-storage 1-3:1.2
[686354.717509] option 1-3:1.3: GSM modem (1-port) converter detected
[686354.717770] usb 1-3: GSM modem (1-port) converter now attached to ttyUSB2

Content of /var/log/usb_modeswitch_1-3\:1.0 :

USB_ModeSwitch log from Wed Mar 17 01:43:48 CET 2010

raw args from udev: 1-3:1.0/1-3:1.0
USB dir exists: /sys/bus/usb/devices/1-3

USB values from sysfs:
  manufacturer  ONDA,Incorporated
  product   ONDA WCDMA Technologies MSM
  serialP673M2ODCD01

SCSI attributes not needed, moving on
checking config: /etc/usb_modeswitch.d/19d2:2000:uPr=ZTE_WCDMA
matching usb(product)
  match string: ZTE WCDMA
 device string: ONDA WCDMA Technologies MSM
* no match, not switching with this config
checking config: /etc/usb_modeswitch.d/19d2:2000:uPr=ZTE_CDMA
matching usb(product)
  match string: ZTE CDMA
 device string: ONDA WCDMA Technologies MSM
* no match, not switching with this config
checking config: /etc/usb_modeswitch.d/19d2:2000:uPr=USB_ZTE
matching usb(product)
  match string: USB ZTE
 device string: ONDA WCDMA Technologies MSM
* no match, not switching with this config
checking config: /etc/usb_modeswitch.d/19d2:2000
! matched, now switching
 (running command: /usr/sbin/usb_modeswitch -I -W -c 
/etc/usb_modeswitch.d/19d2:2000)

verbose output of usb_modeswitch:

usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 003
usb_os_find_busses: Found 006
usb_os_find_busses: Found 005
usb_os_find_busses: Found 001
usb_os_find_busses: Found 004
usb_os_find_busses: Found 002
usb_os_find_devices: Found 032 on 003
skipped 1 class/vendor specific interface descriptors
usb_os_find_devices: Found 003 on 003
usb_os_find_devices: Found 001 on 003
error obtaining child information: Inappropriate ioctl for device
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 001 on 006
usb_os_find_devices: Found 001 on 005
usb_os_find_devices: Found 048 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 004
usb_os_find_devices: Couldn't open /dev/bus/usb/002/065
usb_os_find_devices: Found 001 on 002
Reading config file: /etc/usb_modeswitch.d/19d2:2000

 * usb-modeswitch: handle USB devices with multiple modes
 * Version 1.1.0 (C) Josua Dietze 2010
 * Based on libusb 0.1.12

 ! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor=  0x19d2
DefaultProduct= 0x2000
TargetVendor=   0x19d2
TargetProduct=  not set
TargetProductList=0001,0002,0015,0031,0037,0052,0055,0063
TargetClass=not set

DetachStorageOnly=0
HuaweiMode=0
SierraMode=0

Bug#574270: usb-modeswitch-data: MF636 not working after upgrade

2010-03-17 Thread Didier 'OdyX' Raboud
Le Mercredi 17 Mars 2010 10:32:45 l...@think-future.de, vous avez écrit :
 Package: usb-modeswitch-data
 Version: 20100221-1
 Severity: important
 
 Reporting this here for the draisberghof bb requires registration. It's
 just a bad thing to have to get registrated with dozens of boards, wikis,
 trac or whatever and keeping track of software. I seek to contribute but
 not waste effort and energy in useless regs and get humbled by 1k more of
 spam messages.

Hi,

I understand that. No problem. We'll handle your bugreport here.

 Having that said, here's the report:
 
 Device:
 - Model: MC503HSA
 - Type: MF636
 
 After an usb-modeswitch-data update the modem was unusable as
 usb-modeswitch-data matched idVendor=19d2, idProduct=0037 in
 /etc/usb_modeswitch.d/19d2:2000, no ttyUSB? devices being created.

I don't entirely get your bugreport… did it work with previous versions of usb-
modeswitch-data ? 

What have you done to make your device work ? Did you delete 
/etc/usb_modeswitch.d/19d2\:2000 ?

The changelog contains several changes about those devices (that seem to be the 
most problematic one):

usb-modeswitch-data (20100221-1) unstable; urgency=low
  * New upstream release.
+ New devices
  (…)
  [19d2:2000] ZTE MF626 and others

usb-modeswitch-data (20100203-1) unstable; urgency=low
  * New upstream release.
× Devices updates
  [19d2:2000] Re-arrange target product lists

Thanks in advance for your answers,

OdyX

-- 
Didier Raboud, proud Debian Maintainer (DM).
CH-1020 Renens
did...@raboud.com



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org