Ubuntu
linux package

Sansa E280 MP3 mplayer not detected (regression)

Bug #355317 reported by Francis J. Lacoste on 2009-04-04

This bug report is a duplicate of: Bug #355998: usb-storage: waiting for device to settle before scanning. Edit Remove

2

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	New	Undecided	Unassigned

Bug Description

I have a Sansa E280 MP3 mplayer that doesn't seem detected when I mount it. I upgraded from Hardy and in that version, the device was properly mounted on the desktop.

I know that Ubuntu doesn't automount devices anymore, but i would expect it to appear in the device notifier applet (like my other NextStar external USB drive does.)

Here are the messages appearing in kern.log when I plug it in:

[ 284.680142] usb 1-6: new high speed USB device using ehci_hcd and address 5
[ 284.732428] hub 1-0:1.0: unable to enumerate USB device on port 6
[ 293.072071] usb 1-6: new high speed USB device using ehci_hcd and address 6
[ 293.936426] usb 1-6: configuration #128 chosen from 1 choice
[ 293.955246] scsi3 : SCSI emulation for USB Mass Storage devices
[ 293.955638] usb-storage: device found at 6
[ 293.955642] usb-storage: waiting for device to settle before scanning

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
MachineType: Dell Inc. MXC061
Package: linux-image-2.6.28-11-generic 2.6.28-11.40
ProcCmdLine: root=UUID=86b94072-9e71-4dad-8def-f559d24dc1c0 ro splash
ProcEnviron:
LANGUAGE=fr_CA.UTF-8:fr_FR:fr:en_GB:en
PATH=(custom, user)
LANG=fr_CA.UTF-8
LC_MESSAGES=en_CA.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-11.40-generic
SourcePackage: linux

Tags:

Revision history for this message

Francis J. Lacoste (flacoste) wrote on 2009-04-04:

#1

BootDmesg.txt Edit (42.8 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (2.7 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (990 bytes, text/plain; charset="utf-8")
HalComputerInfo.txt Edit (2.9 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (12.3 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (532 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.6 KiB, text/plain; charset="utf-8")

Revision history for this message

Rick Spencer (rick-rickspencer3) wrote on 2009-04-07:

#2

seb128 - can you please take a look?

Changed in linux (Ubuntu):
assignee:	nobody → seb128
importance:	Undecided → High

Revision history for this message

Alexander Sack (asac) wrote on 2009-04-07:

#3

please check one of the 2.6.29 kernels available here: http://kernel.ubuntu.com/~kernel-ppa/mainline/

Changed in linux (Ubuntu):
assignee:	seb128 → nobody
importance:	High → Undecided

Revision history for this message

Alexander Sack (asac) wrote on 2009-04-07:

#4

if that doesnt help please check whether you can get it working with older kernels.

Revision history for this message

Francis J. Lacoste (flacoste) wrote on 2009-04-07:

#5

I forgot to specify, but I cannot mount it manually either since the device doesn't appear in /dev (it usually appears as /dev/scd, and I also have sda and sdb there).

Revision history for this message

Francis J. Lacoste (flacoste) wrote on 2009-04-07:

#6

Tried with the latest 2.6.29.1 with the same results:

    usb 1-6: new high speed USB device using ehci_hcd and address 9
    hub 1-0:1.0: unable to enumerate USB device on port 6
    usb 1-6: new high speed USB device using ehci_hcd and address 10
    usb 1-6: configuration #128 chosen from 1 choice
    scsi5 : SCSI emulation for USB Mass Storage devices
    usb-storage: device found at 10
    usb-storage: waiting for device to settle before scanning
    usb 1-6: USB disconnect, address 10

Do you have any suggestions on which older kernel I should try? And are talking about older kernel from that same location?

Revision history for this message

Sebastien Bacher (seb128) wrote on 2009-04-07:

#7

could you run "lshal --monitor", connect the device and copy the log to the bug?

Revision history for this message

Francis J. Lacoste (flacoste) wrote on 2009-04-08:

#8

lshal-monitor.log Edit (1.5 KiB, text/plain)

Here it is.

Revision history for this message

Dan Lenski (lenski) wrote on 2009-05-24:

#9

I believe this bug is the same as this one: https://bugs.launchpad.net/ubuntu/+bug/345916

It turns out it is due to the "gphoto" process (which handles MTP mode) attempting to take over access to the Sansa as soon as it is plugged in *EVEN IN MSC MODE*. If you look at the report for that bug, you can fix it by disabling gphoto, by patching gphoto, or by editing its configuration file to prevent it from accessing the Sansa in MSC mode.

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #355998 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.