Cannot get Amarok 2 to sync up with my 8GB Sansa View

Asked by Rob

The Sansa View is not exactly groundbreaking and new but it is a nifty and affordable media player.

But I cannot get it to sync with Amarok 2. And I don't know what it is I am doing wrong.

Google is not being friendly and I am hoping to get some help from someone soon, if only to be pointed in the right direction.

RAR

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu amarok Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

Does the devices partition(s) show up in:

sudo fdisk -l

If you reboot, log in and then wait for the system to settle. Once its all ok, connect the device, wait 10 seconds then run:

dmesg | tail

and paste the output here as well as the output of:

mount

Thanks

Revision history for this message
Rob (robert-rinne) said :
#2

actionparsnip wrote:

> Your question #73595 on amarok in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/amarok/+question/73595
>
> Status: Open => Answered
>
> actionparsnip proposed the following answer:
> Does the devices partition(s) show up in:
>
> sudo fdisk -l
>
> If you reboot, log in and then wait for the system to settle. Once its
> all ok, connect the device, wait 10 seconds then run:
>
> dmesg | tail
>
> and paste the output here as well as the output of:
>
> mount
>
> Thanks
>
>
Hello,

Output of sudo fdisk -l

ulysses@ithaka:~$ sudo fdisk -l
[sudo] password for ulysses:

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0003d86a

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 60060 482431918+ 83 Linux
/dev/sda2 60061 60801 5952082+ 5 Extended
/dev/sda5 60061 60801 5952051 82 Linux swap / Solaris

Disk /dev/sdb: 8220 MB, 8220311552 bytes
253 heads, 62 sectors/track, 1023 cylinders
Units = cylinders of 15686 * 512 = 8031232 bytes
Disk identifier: 0x00000000

   Device Boot Start End Blocks Id System
/dev/sdb1 1 1019 7984379 b W95 FAT32
Partition 1 has different physical/logical beginnings (non-Linux?):
     phys=(0, 4, 11) logical=(0, 8, 27)
Partition 1 has different physical/logical endings:
     phys=(669, 23, 0) logical=(1018, 15, 2)
Partition 1 does not end on cylinder boundary.
/dev/sdb2 1019 1024 43008 84 OS/2 hidden C: drive
Partition 2 has different physical/logical beginnings (non-Linux?):
     phys=(157, 24, 1) logical=(1018, 15, 3)
Partition 2 has different physical/logical endings:
     phys=(679, 55, 0) logical=(1023, 137, 24)
Partition 2 does not end on cylinder boundary.

This tells me that it sees it. I can see that here, right?
Disk /dev/sdb: 8220 MB, 8220311552 bytes

But I'm not sure what the rest of it means. I can't tell if it is good
or bad

But, to carry on...
Shut down. Unplugged Sansa View. Confirmed Sansa View in MSC mode.
Turned machine on. Logged in. Waited for desktop to come up. Counted to
twenty. Plugged in Sansa View. Opened terminal and ran dmesg | tail.
And, for the record, new to Ubuntu that I am, I just found out where on
the keyboard the | key was

ulysses@ithaka:~$ dmesg | tail
[ 93.400109] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 93.412422] sd 4:0:0:0: [sdb] 16055296 512-byte hardware sectors:
(8.22 GB/7.65 GiB)
[ 93.417178] sd 4:0:0:0: [sdb] Write Protect is off
[ 93.417186] sd 4:0:0:0: [sdb] Mode Sense: 3f 00 00 08
[ 93.417191] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 93.417204] sdb: sdb1 sdb2
[ 93.427269] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[ 93.427408] sd 4:0:0:0: Attached scsi generic sg2 type 0
[ 93.440771] sd 4:0:0:1: [sdc] Attached SCSI removable disk
[ 93.441170] sd 4:0:0:1: Attached scsi generic sg3 type 0

And then, I ran mount. Here is the output for that.

ulysses@ithaka:~$ mount
/dev/sda1 on / type ext3 (rw,relatime,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,nosuid,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
lrm on /lib/modules/2.6.28-11-generic/volatile type tmpfs (rw,mode=755)
securityfs on /sys/kernel/security type securityfs (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc
(rw,noexec,nosuid,nodev)
gvfs-fuse-daemon on /home/ulysses/.gvfs type fuse.gvfs-fuse-daemon
(rw,nosuid,nodev,user=ulysses)
/dev/sdb1 on /media/Sansa View type vfat
(rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush)

Whatever help you can provide with this would be awesome.

RAR

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#3

Ok looking good

Your disk is /dev/sdb and is 8Gb in size

The first partition (/dev/sdb1) is mounted

/dev/sdb1 on /media/Sansa View type vfat
(rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush)

and is writable so if you tell amarok that /media/Sansa (Capital S is *VERY* important) is your disk then you should be ok, if it wants raw devices then try telling amarok that the device is /dev/sdb, if amarok wants the raw partition name then try /dev/sdb1

I dont use any MP3 players so I have never had to do this personally but I am familiar with the process.

Revision history for this message
Rob (robert-rinne) said :
#4

actionparsnip wrote:

> Your question #73595 on amarok in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/amarok/+question/73595
>
> Status: Open => Answered
>
> actionparsnip proposed the following answer:
> Ok looking good
>
> Your disk is /dev/sdb and is 8Gb in size
>
> The first partition (/dev/sdb1) is mounted
>
> /dev/sdb1 on /media/Sansa View type vfat
> (rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush)
>
> and is writable so if you tell amarok that /media/Sansa (Capital S is
> *VERY* important) is your disk then you should be ok, if it wants raw
> devices then try telling amarok that the device is /dev/sdb, if amarok
> wants the raw partition name then try /dev/sdb1
>
> I dont use any MP3 players so I have never had to do this personally but
> I am familiar with the process.
>
>
Hello

Thank you very much for your help
You can consider this matter closed
I much prefer the look and feel of Amarok, but if anyone were to ask you
which media player to use with the Sansa Media player, tell them to
change their player to auto detect, plug it into their desktop, start up
Rhythmbox and they are off to the races
Zero problem transferring data. No lag. No problems.

But thanks, sir.

RAR

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#5

Please mark as solved if the issue has gone. Thanks

Can you help with this problem?

Provide an answer of your own, or ask Rob for more information if necessary.

To post a message you must log in.