I personally don't use Linux, but I have done some mass-googling to find the info for all you new iRiver owners who use Linux.
The following was found on a forum on how to properly "mount" the drive in the case of an h340:
Quote:
1) Connect USB cable to the Data port.
2) Open a terminal window and su to root.
3) do a "tail /var/log/messages" and note that it should say something like this:
Dec 2 19:14:15 XCube kernel: Attached scsi disk sdb at scsi2, channel 0, id 0, lun 0
Dec 2 19:14:15 XCube kernel: Attached scsi generic sg1 at scsi2, channel 0, id 0, lun 0, type 0
Note the sdb (in my case).
4) run the following command
mkdir /mnt/H320
5) run the following command:
mount -t vfat /dev/sdb1 /mnt/H320
Ta dah! It's mounted and ready to interface (suprisingly faster than in Windows, and with all the capabilities of a regular USB hard drive).
Just remember to run umount /mnt/H320 before unplugging!!
|
This is from an hp-120 user, i have ported it from
http://lonelymachines.org/iriver.html
I don't see why this also wouldnt work for an h3xx series, but I don't use Linux, so no idea.
Quote:
This player runs easily enough with no software. Provided you're running a somewhat recent kernel with USB support compiled in, the device should be recognized as soon as you plug it in.
The first step is to find out where your system thinks it is. Right after plugging in the unit, open a terminal and type dmesg. The output should say something like this:
hub.c: new USB device 00:0b.2-5, assigned address 2
usb.c: USB device 2 (vend/prod 0x1006/0x3002) is not claimed by any active driver.
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
scsi2 : SCSI emulation for USB Mass Storage devices
Vendor: TOSHIBA Model: MK2004GAL Rev: JA02
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi disk sdb at scsi2, channel 0, id 0, lun 0
SCSI device sdb: 39063024 512-byte hdwr sectors (20000 MB)
sdb: sdb1
This tells you that the device lives at /dev/sdb1. Next step is to give it a mount point. Create a directory where you want the ihp to live while it's mounted. On my system, it's at /iriver.
Step three is to make an entry in fstab. You'll need to put in a line similar to this:
/dev/sdb1 /iriver vfat noauto,user,rw 0 0
The first column is the device name, the second is where it'll be mounted, and the third is the filesystem type. Make sure to specify vfat (same as FAT32) and not msdos, as the latter will hose your filenames and possibly render the disc on the ihp unresponsive. The fourth column specifies that the device is not automatically mounted on boot (noauto), that individual users can mount it (user), and that it can be read and written (rw). Provided the ihp shows up on your system as it does on mine, you could just copy this whole line into your own fstab.
With the preliminaries out of the way, just plug in the ihp and type mount /iriver, and you're good to go. The /iriver directory will act like any other on your system as far as copying, moving or deleting files.. Make sure to unmount (umount /iriver) the device before disconnecting it.
|
Finally, if you are interested in creating a database(.idb)
Try iRipDB, found here:
http://www.marevalo.net/iRipDB/
or
libiRiverDB, found here:
http://www.bodgit-n-scarper.com/code.html