Connecting voice recorder to Ubuntu 10.10

Asked by Chris Els on 2012-11-01

I have a Philips Voice Tracer LFH0612 which I tried to connect to my Mecer laptop via usb cable.
The manual for the Philips states that it should automatically show up on the laptop. It does not.
The Philips displays "PC" when connected.
Do I need a special driver? If so, where do I get it and how do I install it?
I am a newbie and mainly use the notebook for word processing with OpenOffice.

Any help, please?

Regards,
Chris

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu util-linux Edit question
Assignee:
No assignee Edit question
Solved by:
Chris Els
Solved:
2012-11-01
Last query:
2012-11-01
Last reply:
2012-11-01
Warren Hill (warren-hill) said : #1

1. I have had a quick look on a few websites and it looks like it should appear as a drive when its plugged in.

Open the file manager and see if it's there. If not we need some more information.

Open a terminal by pressing CTRL, ALT and T then with the device unplugged enter the following command

lsusb; sudo fdisk -l

Now plug the device in wait 10 seconds or so to give it time to be recognised and enter these commands again

lsusb; sudo fdisk -l

Copy all the results and paste them back here we should be able to help further.

2. Ubuntu 10.10 is no longer supported I suggest you consider upgrading to 12.04

Maverick is dead, please upgrade. It's been dead for a long time too (More than a year now). Why are you using a dead release?

Chris Els (chrisels1951) said : #3

After carrying out the instructions above, I get the following output:

chris@chris-M7x0S:~$ lsusb; sudo fdisk -l
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 19d2:0063 ONDA Communication S.p.A.
Bus 001 Device 002: ID 5986:0241 Acer, Inc BisonCam, NB Pro
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[sudo] password for chris:
Sorry, try again.
[sudo] password for chris:

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 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: 0x000f30aa

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 59272 476097536 83 Linux
/dev/sda2 59272 60802 12285953 5 Extended
/dev/sda5 59272 60802 12285952 82 Linux swap / Solaris

Disk /dev/sdb: 1977 MB, 1977614336 bytes
64 heads, 63 sectors/track, 957 cylinders
Units = cylinders of 4032 * 512 = 2064384 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot Start End Blocks Id System
/dev/sdb1 1 957 1929244+ 6 FAT16
chris@chris-M7x0S:~$ lsusb; sudo fdisk -l
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 19d2:0063 ONDA Communication S.p.A.
Bus 001 Device 002: ID 5986:0241 Acer, Inc BisonCam, NB Pro
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 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: 0x000f30aa

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 59272 476097536 83 Linux
/dev/sda2 59272 60802 12285953 5 Extended
/dev/sda5 59272 60802 12285952 82 Linux swap / Solaris

Disk /dev/sdb: 1977 MB, 1977614336 bytes
64 heads, 63 sectors/track, 957 cylinders
Units = cylinders of 4032 * 512 = 2064384 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot Start End Blocks Id System
/dev/sdb1 1 957 1929244+ 6 FAT16
chris@chris-M7x0S:~$

Hope this helps.
Thanks,
Chris

Maverick is dead

Warren Hill (warren-hill) said : #5

I would certainly agree with Andrew that you should update. Especially if these two results are with the device unplugged first then connected. Since this suggests your computer can not see the device.

It sees a 500GB drive and a 2GB drive in both cases nothing is changing so it cant be seeing the device.

Chris Els (chrisels1951) said : #6

Thanks.

I'll upgrade and try again.