I upgraded from 11.2 to 11.3 yesterday, using a 64-bit Dell 1535 laptop.
With the new version, I find that the Device Notifier no longer detects my mp3 player through any of the USB ports. Neither does Dolphin.
Similar threads that I’ve read through have not done the trick, so any help would be appreciated.
Open a terminal, and plug in your device. Then type
dmesg |tail
Note what is reported.
Here it is:
1086.986869] st: Version 20081215, fixed bufsize 32768, s/g segs 256
3690.144658] usb 2-3: USB disconnect, address 4
3711.500431] hub 2-0:1.0: unable to enumerate USB device on port 3
3712.952085] usb 2-3: new high speed USB device using ehci_hcd and address 6
3713.085847] usb 2-3: New USB device found, idVendor=0781, idProduct=74d0
3713.085861] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
3713.085869] usb 2-3: Product: SanDisk Sansa Clip+
3713.085875] usb 2-3: Manufacturer: SanDisk
3713.085879] usb 2-3: SerialNumber: 5614FA139992B6A80000000000000000
3713.093117] scsi4 : usb-storage 2-3:1.0
Now you may need to configure the Device notifier. I found that, on upgrading, the new Device notifier needed configuring but the Configuration dialogue only appears when something is plugged in. So, if it won’t respond to the USB stick, try something else and, when you have configured it, try the USB stick again.
Thank you for the follow-up.
My Linux experience is limited – could someone walk me through the Device Notifier configuration process?
Okay… I just followed John’s advice (having given it a closer reading – sorry for being such a noob). I plugged in a flash drive and it was recognized by Device Notifier, so I was able to access the configuration window. I told it to work for both removable and non-removable media – that did not work.
Is there another setting that needs to be changed?
Ok, the dmesg results confirmed the device is working ok.
I would have thought adjusting the Device Notifier settings should have worked for you. Is the device formatted ok? Does it work in another OS etc?
Plug the device in, open a terminal, and become root with
su -
Enter your root password, then type
fdisk -l
This will tell us about the formatting.
Here it is, deano:
Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x7a13694d
Device Boot Start End Blocks Id System
/dev/sda1 1 5 40131 de Dell Utility
/dev/sda2 6 1280 10240000 7 HPFS/NTFS
/dev/sda3 1280 20342 153115515 7 HPFS/NTFS
/dev/sda4 * 20343 38913 149171557+ f W95 Ext'd (LBA)
/dev/sda5 20343 20603 2096451 82 Linux swap / Solaris
/dev/sda6 20604 21882 10273536 83 Linux
/dev/sda7 21883 38913 136801476 83 Linux
Is that fdisk info with a device connected?
Apologies – here it is again, device plugged-in for certain:
Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x7a13694d
Device Boot Start End Blocks Id System
/dev/sda1 1 5 40131 de Dell Utility
/dev/sda2 6 1280 10240000 7 HPFS/NTFS
/dev/sda3 1280 20342 153115515 7 HPFS/NTFS
/dev/sda4 * 20343 38913 149171557+ f W95 Ext'd (LBA)
/dev/sda5 20343 20603 2096451 82 Linux swap / Solaris
/dev/sda6 20604 21882 10273536 83 Linux
/dev/sda7 21883 38913 136801476 83 Linux
It’s not there obviously, you didn’t need me to tell you that.
And presumably it works fine in windows? If it were mine I would probably format it in windows, be sure to safely remove, and then try again in Linux?
If that is out of the question, scan it in windows for errors.
It works in Windows, and it worked great in OpenSuse 11.2. Something happened with the upgrade.
You assume that, but I very much doubt it. Hence my recommendation.
What about Yast - Partitioner: Is it seen in there?
I don’t see it there, but it did show up in the fdisk check further up-thread.
Quote it to me, because as hard as I try I can’t see what you mean. Am I stupid or blind?
or
Are you meaning:
dmesg |tail
Thanks for the correction – it was dmesg | tail.
Have you tried as I suggested earlier?
My Son has one of the mp3 players (same make) and honestly, I wouldn’t give it the time of day.
Also he use a USB pen drive of mine in his windows machine, and every so often, I have to format it.
The one he uses with a Linux machine is fine.
Thanks to everyone for all your help and suggestions.
I went onto the Sandisk support page and found out that their devices on Linux and Mac work with the USB set to MSC rather than MTD, which is the Windoze default setting. I made the change and Device Notifier immediately recognized my mp3 player.
I also figured out how to reformat and reinstall the firmware, if it ever comes to that, so thanks again…
Thanks for the info on the Sandisk Sansa Fuze. I went into the settings on mine and switched the USB settings and i connected right away. I don’t connect it to a Windows box much unless I want to rip a video and put it on there.
Now if I could get my Blackberry to be recognized I’d be really good.
Yeah, Sandisk apparently defaults to auto-detect for its USB setting. The Admin guy on their forum wrote (quoting), “Under no circumstances should you use auto-detect.” This explains (to me, anyway) why the device was working just fine with 11.2, but stopped working when I went to 11.3 – the auto-detect decided not to mesh with the new version.
I keep Windows for a few programs that don’t run on Wine, but for the most part I also avoid it. Next box, I’m going to dedicate most of the HD to OpenSuse…
Glad this thread addressed your problem, as well – nice to know I’m not the only one!