Bug 15035 - Devices screen shows "none" for USB and SD card
: Devices screen shows "none" for USB and SD card
Status: CLOSED FIXED
Product: SB Touch
Classification: Unclassified
Component: UI
: unspecified
: Other Other
: P1 normal (vote)
: 7.5.0
Assigned To: Mickey Gee
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-11-03 13:48 UTC by Mickey Gee
Modified: 2010-04-08 17:25 UTC (History)
4 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mickey Gee 2009-11-03 13:48:01 UTC
Running 7.5.0 r7984 firmware, when I look at the Settings->Advanced->USB & SD Storage->Devices screen, I see "none" under "USB Disk:" and "SD Card:".

What is this supposed to mean? They don't change when you attach a USB disk or SD card, so it's not whether a volume is attached or not. Is this the volume name?
Comment 1 Felix Mueller 2009-11-05 02:12:11 UTC
Andy: I'll take this one, it's part of bug 11952.

Mickey: I implemented that according to the wiki page: Settings - version 1 http://embargo.wiki.slimdevices.com/index.php/TinySC#Settings

They are supposed to change when you attach a device and show the volume name if the device has one.

1) Could you please check if it has a volume name set using your PC / Mac?
2) What format is your device formatted with: FAT, NTFS, EXT3, ..?
3) When you attach the device in question do Size & Free change?
4) Also, could you please type the 'blkid' command on Touch in a serial console and post the output here. You should get something like this:

# blkid
/dev/sda1: LABEL="KINGSTON" UUID="4728-1673"
/dev/mmcblk0p1: LABEL="LOGISTUFF" UUID="10E5-A2CA"
#

First line is for USB, second line is for SD card.

Thanks
Felix
Comment 2 Mickey Gee 2009-11-19 13:42:46 UTC
Looks great to me!


# blkid
/dev/mmcblk0p1: LABEL="SNOW PHOTOS" UUID="B84D-3FB3"
/dev/sda1: LABEL="TOSHIBA_EXT" UUID="0FE2-3943"
Comment 3 Mickey Gee 2009-11-19 13:45:08 UTC
Checked out on FAT16 and FAT32 only.
Comment 4 Chris Owens 2010-04-08 17:25:42 UTC
This bug has been marked fixed in a released version of Squeezebox Server or the accompanying firmware or mysqueezebox.com release.

If you are still seeing this issue, please let us know!