umass not working with MP3 Player

[Peter Jeremy]

My wife got a MP3 player for mother's day.  Whilst I managed to confirm
that it was a standard USB mass storage device before buying it, it
seems that FreeBSD (6.1-RELEASE) doesn't like it.

It identifies as:
umass0: EM706S EM706S MP3 Player, rev 1.10/10.01, addr 2
umass0: SCSI over Bulk-Only; quirks = 0x0000
umass0:2:0:-1: Attached to scbus2
da0 at umass-sim0 bus 0 target 0 lun 0
da0: <EM706S MP3 Player 0100> Removable Direct Access SCSI-4 device 
da0: 1.000MB/s transfers
da0: 491MB (251456 2048 byte sectors: 64H 32S/T 122C)

usbdevs reports:
 port 3 addr 2: full speed, power 100 mA, config 1, EM706S MP3 Player(0x0706), EM706S(0x067f), rev 10.01

But an attempt to read from it (with hw.usb.umass.debug=0xffff0000) returns:
turion% dd if=/dev/da0 bs=512 count=1 >/dev/null
umass0:2:0:0:XPT_SCSI_IO: cmd: 0x25, flags: 0x40, 10b cmd/8b data/32b sense
umass0: CBW 50: cmd = 10b (0x250000000000...), data = 8b, dir = in
umass0: Handling BBB state 2 (BBB CBW), xfer=0xffffff002a822a00, NORMAL_COMPLETION
umass0: Handling BBB state 3 (BBB Data), xfer=0xffffff002992f800, NORMAL_COMPLETION
umass0: 0x 0003d63f00000800 buffer=0xffffff001aac8240, buflen=8
umass0: Handling BBB state 5 (BBB CSW, 1st attempt), xfer=0xffffff0028b48800, NORMAL_COMPLETION
umass0: CSW 50: sig = 0x53425355 (valid), tag = 50, res = 0, status = 0x00 (good)
umass0:2:0:0:XPT_SCSI_IO: cmd: 0x1e, flags: 0xc0, 6b cmd/0b data/32b sense
umass0: CBW 51: cmd = 6b (0x1e0000000100), data = 0b, dir = out
umass0: Handling BBB state 2 (BBB CBW), xfer=0xffffff002a822a00, NORMAL_COMPLETION
umass0: no data phase
umass0: Handling BBB state 5 (BBB CSW, 1st attempt), xfer=0xffffff0028b48800, NORMAL_COMPLETION
umass0: CSW 51: sig = 0x53425355 (valid), tag = 51, res = 0, status = 0x00 (good)
dd: /dev/da0: Invalid argument
0+0 records in
0+0 records out
0 bytes transferred in 0.000197 secs (0 bytes/sec)

I've tried comparing it with a BBB umass device that works and there
is no immediately obvious difference except that the good device
continues to perform further SCSI commands instead of returning EINVAL.

Any suggestions on how to proceed further?

-- 
Peter Jeremy