0e8d:0002 [SiS-661GX] phone won't mount

[Thufir]

I have no idea why the phone won't mount. see
http://askubuntu.com/questions/284214/cannot-mount-cell-phone-as-usb-mass-storage-device

where I was told to file as a bug. A bug of what, I don't know. "something" has a bug.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-27-generic 3.5.0-27.46
ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
Uname: Linux 3.5.0-27-generic i686
ApportVersion: 2.6.1-0ubuntu10
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: thufir 2608 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory: 'iw'
CurrentDmesg:
 [ 48.557787] vesafb: scrolling: redraw
 [ 48.557791] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
 [ 48.560536] vesafb: framebuffer at 0xd8000000, mapped to 0xf8880000, using 3072k, total 3072k
 [ 48.560867] Console: switching to colour frame buffer device 128x48
 [ 48.560899] fb0: VESA VGA frame buffer device
Date: Mon Apr 22 15:14:07 2013
HibernationDevice: RESUME=UUID=1b76e749-4b13-4187-969f-082ad3721f43
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 eth1 no wireless extensions.
Lsusb:
 Bus 004 Device 002: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-27-generic root=/dev/mapper/hostname-root ro splash quiet vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-27-generic N/A
 linux-backports-modules-3.5.0-27-generic N/A
 linux-firmware 1.95
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/19/2005
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: SiS-661GX
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd05/19/2005:svn:pn:pvr:rvn:rnSiS-661GX:rvr:cvn:ct3:cvr:

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of the introduction of a regression, and when this regression was introduced.

[Thufir (hawat-thufir)]

I installed ubuntu 12.10 (I think) and was able to mount the phone.
Then, I had some problems, formatted and did a clean install of 12.10
server.

I think there's just a missing component, or something, but I'm not sure.

I appreciate your interest, thank you.

Pardon, I don't have specifics on kernel versions or upgrades, it's a
fuzzy recollection.

-Thufir

On 04/22/2013 04:09 PM, Joseph Salisbury wrote:
> Did this issue start happening after an update/upgrade? Was there a
> kernel version where you were not having this particular problem? This
> will help determine if the problem you are seeing is the result of the
> introduction of a regression, and when this regression was introduced.
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>

[Thufir (hawat-thufir)]

Here's the info from askUbuntu:

Before voting to close the question, a comment would be appreciated.

I'm running xubuntu-destop from 12.10 server and am trying to mount my cell phone as a USB mass storage device. I have mounted the device before, but that was before I did a clean install of the OS.

Here's what's mounted currently:

thufir@dur:~$ mount
/dev/mapper/dur-root on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
/dev/sdb1 on /boot type ext2 (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
gvfsd-fuse on /run/user/thufir/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,user=thufir)
thufir@dur:~$

I don't see where my phone is located:

[ 4705.040060] usb 2-3: new full-speed USB device number 2 using ohci_hcd
[ 4705.255258] usb 2-3: New USB device found, idVendor=0e8d, idProduct=0002
[ 4705.255269] usb 2-3: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 4705.255274] usb 2-3: Product: MT6225
[ 4705.255278] usb 2-3: Manufacturer: MediaTek Inc
[ 4705.255281] usb 2-3: SerialNumber: 537117509177320
[ 4705.395914] Initializing USB Mass Storage driver...
[ 4705.404167] scsi4 : usb-storage 2-3:1.0
[ 4705.404353] usbcore: registered new interface driver usb-storage
[ 4705.404356] USB Mass Storage support registered.
[ 4706.418064] scsi 4:0:0:0: Direct-Access MEDIATEK FLASH DISK 6225 PQ: 0 ANSI: 0 CCS
[ 4706.425059] scsi 4:0:0:1: Direct-Access MEDIATEK FLASH DISK 6225 PQ: 0 ANSI: 0 CCS
[ 4706.428973] sd 4:0:0:0: Attached scsi generic sg4 type 0
[ 4706.430297] sd 4:0:0:1: Attached scsi generic sg5 type 0
[ 4706.438130] sd 4:0:0:0: [sdc] 7829504 512-byte logical blocks: (4.00 GB/3.73 GiB)
[ 4706.449032] sd 4:0:0:0: [sdc] Write Protect is off
[ 4706.449043] sd 4:0:0:0: [sdc] Mode Sense: 03 00 00 00
[ 4706.456082] sd 4:0:0:1: [sdd] 256 512-byte logical blocks: (131 kB/128 KiB)
[ 4706.463052] sd 4:0:0:0: [sdc] No Caching mode page present
[ 4706.463064] sd 4:0:0:0: [sdc] Assuming drive cache: write through
[ 4706.470046] sd 4:0:0:1: [sdd] Write Protect is off
[ 4706.470058] sd 4:0:0:1: [sdd] Mode Sense: 03 00 00 00
[ 4706.481034] sd 4:0:0:1: [sdd] No Caching mode page present
[ 4706.481046] sd 4:0:0:1: [sdd] Assuming drive cache: write through
[ 4706.529002] sd 4:0:0:0: [sdc] No Caching mode page present
[ 4706.529013] sd 4:0:0:0: [sdc] Assuming drive cache: write through
[ 4706.547100] sdc: sdc1
[ 4706.554004] sd 4:0:0:1: [sdd] No Caching mode page present
[ 4706.554016] sd 4:0:0:1: [sdd] Assuming drive cache: write through
[ 4706.571131] sdd:
[ 4706.636997] sd 4:0:0:0: [sdc] No Caching mode p...

[Thufir (hawat-thufir)]

Hi,

If I may inquire, how did you confirm the bug? Pardon, I'm still thinking
it's not a bug.

On Mon, Apr 22, 2013 at 4:09 PM, Joseph Salisbury <
<email address hidden>> wrote:

> Did this issue start happening after an update/upgrade? Was there a
> kernel version where you were not having this particular problem? This
> will help determine if the problem you are seeing is the result of the
> introduction of a regression, and when this regression was introduced.
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1171638
>
> Title:
> phone won't mount
>
> Status in “linux” package in Ubuntu:
> Confirmed
>
> Bug description:
> I have no idea why the phone won't mount. see
>
> http://askubuntu.com/questions/284214/cannot-mount-cell-phone-as-usb-mass-storage-device
>
> where I was told to file as a bug. A bug of what, I don't know.
> "something" has a bug.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.10
> Package: linux-image-3.5.0-27-generic 3.5.0-27.46
> ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
> Uname: Linux 3.5.0-27-generic i686
> ApportVersion: 2.6.1-0ubuntu10
> Architecture: i386
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: thufir 2608 F.... pulseaudio
> CRDA: Error: [Errno 2] No such file or directory: 'iw'
> CurrentDmesg:
> [ 48.557787] vesafb: scrolling: redraw
> [ 48.557791] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
> [ 48.560536] vesafb: framebuffer at 0xd8000000, mapped to 0xf8880000,
> using 3072k, total 3072k
> [ 48.560867] Console: switching to colour frame buffer device 128x48
> [ 48.560899] fb0: VESA VGA frame buffer device
> Date: Mon Apr 22 15:14:07 2013
> HibernationDevice: RESUME=UUID=1b76e749-4b13-4187-969f-082ad3721f43
> IwConfig:
> lo no wireless extensions.
>
> eth0 no wireless extensions.
>
> eth1 no wireless extensions.
> Lsusb:
> Bus 004 Device 002: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical
> Wheel Mouse
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> MarkForUpload: True
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcFB: 0 VESA VGA
> ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-27-generic
> root=/dev/mapper/hostname-root ro splash quiet vt.handoff=7
> RelatedPackageVersions:
> linux-restricted-modules-3.5.0-27-generic N/A
> linux-backports-modules-3.5.0-27-generic N/A
> linux-firmware 1.95
> RfKill:
>
> SourcePackage: linux
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 05/19/2005
> dmi.bios.vendor: Phoenix Technologies, LTD
> dmi.bios.version: 6.00 PG
> dmi.board.name: SiS-661GX
> dmi.chass...

[Thufir (hawat-thufir)]

What exactly is the problem? I know that it's worked in the past. I don't think the phone is strange or unusual in any way, so don't see why it won't mount.

[Thufir (hawat-thufir)]

It's a confirmed bug, by Brad-Figg, so let's leave it there. As to the history, I don't recall any updates or anything like that. I've since done a clean install.

It worked for a bit under 12.10 and then stopped working. I did a clean install, partly for this reason, and am now running 13.04 (server) with this above bug still effecting me. Pardon that I cannot narrow down the regression better.

[penalvch (penalvch)]

Thufir, could you please test for this in Saucy via http://cdimage.ubuntu.com/daily-live/current/ and advise on if this is reproducible?

[Thufir (hawat-thufir)]

I'm unfamiliar with Saucy. I can say that the phone mounts fine in Ubuntu 12.04.2 LTS installed onto new hardware. I'll look into saucy. I think the bug's been confirmed by another user.

[Ralph Janke (txwikinger)]

I have the same issue:

[681443.320409] usb 2-1.4: new full-speed USB device number 8 using ehci-pci
[681443.415519] usb 2-1.4: New USB device found, idVendor=0e8d, idProduct=0002
[681443.415528] usb 2-1.4: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[681443.415550] usb 2-1.4: Product: MT6225
[681443.415555] usb 2-1.4: Manufacturer: MediaTek Inc
[681443.415559] usb 2-1.4: SerialNumber: 53655820515862f
[681443.417380] scsi11 : usb-storage 2-1.4:1.0
[681444.416872] scsi 11:0:0:0: Direct-Access MEDIATEK FLASH DISK 6225 PQ: 0 ANSI: 0 CCS
[681444.417402] scsi 11:0:0:1: Direct-Access MEDIATEK FLASH DISK 6225 PQ: 0 ANSI: 0 CCS
[681444.418406] sd 11:0:0:0: Attached scsi generic sg2 type 0
[681444.418671] sd 11:0:0:1: Attached scsi generic sg3 type 0
[681444.420182] sd 11:0:0:0: [sdb] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB)
[681444.422763] sd 11:0:0:0: [sdb] Write Protect is off
[681444.422768] sd 11:0:0:0: [sdb] Mode Sense: 03 00 00 00
[681444.424605] sd 11:0:0:0: [sdb] No Caching mode page present
[681444.424610] sd 11:0:0:0: [sdb] Assuming drive cache: write through
[681444.425041] sd 11:0:0:1: [sdc] 100 512-byte logical blocks: (51.2 kB/50.0 KiB)
[681444.425913] sd 11:0:0:1: [sdc] Write Protect is off
[681444.425917] sd 11:0:0:1: [sdc] Mode Sense: 03 00 00 00
[681444.426781] sd 11:0:0:1: [sdc] No Caching mode page present
[681444.426784] sd 11:0:0:1: [sdc] Assuming drive cache: write through
[681444.430037] sd 11:0:0:0: [sdb] No Caching mode page present
[681444.430042] sd 11:0:0:0: [sdb] Assuming drive cache: write through
[681444.439014] sdb: sdb1
[681444.441762] sd 11:0:0:1: [sdc] No Caching mode page present
[681444.441767] sd 11:0:0:1: [sdc] Assuming drive cache: write through
[681444.450513] sdc:
[681444.454779] sd 11:0:0:0: [sdb] No Caching mode page present
[681444.454800] sd 11:0:0:0: [sdb] Assuming drive cache: write through
[681444.454804] sd 11:0:0:0: [sdb] Attached SCSI removable disk
[681444.456878] sd 11:0:0:1: [sdc] No Caching mode page present
[681444.456898] sd 11:0:0:1: [sdc] Assuming drive cache: write through
[681444.456900] sd 11:0:0:1: [sdc] Attached SCSI removable disk
[681449.100091] usb 2-1.4: USB disconnect, device number 8
[681459.591209] usb 2-1.4: new full-speed USB device number 9 using ehci-pci
[681459.685371] usb 2-1.4: New USB device found, idVendor=0e8d, idProduct=0002
[681459.685398] usb 2-1.4: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[681459.685403] usb 2-1.4: Product: MT6225
[681459.685424] usb 2-1.4: Manufacturer: MediaTek Inc
[681459.685429] usb 2-1.4: SerialNumber: 53655820515862f
[681459.688687] scsi12 : usb-storage 2-1.4:1.0
[681460.687830] scsi 12:0:0:0: Direct-Access MEDIATEK FLASH DISK 6225 PQ: 0 ANSI: 0 CCS
[681460.689013] scsi 12:0:0:1: Direct-Access MEDIATEK FLASH DISK 6225 PQ: 0 ANSI: 0 CCS
[681460.696333] sd 12:0:0:0: [sdb] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB)
[681460.696921] sd 12:0:0:0: [sdb] Write Protect is off
[681460.696945] sd 12:0:0:0: [sdb] Mode Sense: 03 00 00 00
[681460.698202] sd 12:0:0:0: [sdb] No Caching mode page present
[681460.698210] sd 12:0:0:0: [sdb] Assuming drive cache: write...

[Ralph Janke (txwikinger)]

Changing the line in /etc/usb_modeswitch.conf to

DisableSwitching=0

to

DisableSwitching=1

solved the problem

[penalvch (penalvch)]

Ralph Janke, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Marcin Osowski (f-marcin)]

Apart from completely disabling usb_modeswitch (Ralph's suggestion in comment #12), it is also possible to disable usb_modeswitch for this particular device, by commenting out this line:

# MediaTek MT6276M, MediaTek MT6276M
ATTR{idVendor}=="0e8d", ATTR{idProduct}=="0002", RUN+="usb_modeswitch '%b/%k'"

in the file /lib/udev/rules.d/40-usb_modeswitch.rules

Solves the problem in my case.

[penalvch (penalvch)]

Marcin Osowski, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]