mp3 player sansa e280 automatically mount
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned | ||
Bug Description
Hello,
my mp3 player (SanDisk Sansa e280 8GB) does not automatically mount on plug-in. Nothing happens if i plug in the mp3 player.
I use Karmic Koala with the newest updates.
ProblemType: Bug
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/pcmC0D0p: hal9000 1715 F...m pulseaudio
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'V8237'/'VIA 8237 with ALC658D at 0xe600, irq 22'
Mixer name : 'Realtek ALC658D'
Components : 'AC97a:414c4781'
Controls : 45
Simple ctrls : 31
Card1.Amixer.info:
Card hw:1 'CX8801'/'Conexant CX8801 at 0xdd000000'
Mixer name : 'CX88'
Components : ''
Controls : 3
Simple ctrls : 2
DKDisksMonitorLog: Monitoring activity from the disks daemon. Press Ctrl+C to cancel.
Date: Mon Oct 5 02:42:55 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=
HotplugNewDevices:
HotplugNewMounts:
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
eth1 no wireless extensions.
NonfreeKernelMo
Package: linux-image-
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.20
RfKill:
SourcePackage: linux
Symptom: storage
UdevMonitorLog:
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
Uname: Linux 2.6.31-11-generic i686
dmi.bios.date: 01/09/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: AX8 Series(VIA K8T890-8237)
dmi.board.vendor: http://
dmi.board.version: 1.x
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixT
Changed in linux (Ubuntu): | |
status: | Won't Fix → New |
Changed in linux (Ubuntu): | |
status: | New → In Progress |
Changed in linux (Ubuntu): | |
status: | In Progress → Triaged |
assignee: | Colin King (colin-king) → nobody |
Hi hmc8,
can you plug in the device, wait 15 seconds and then do the following command:
dmesg > dmesg.log
and attach that to this bug report. Thanks!