[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Robin Cornelius wrote:
> Start with the phone unplugged, plug in the USB wait a few seconds
> then issue a "dmseg" command in a terminal window, this will show you
> what the system has detected if it has loaded any drivers for you etc.
> It might also tell you the VID and PID.
This is the tail end of the dmesg, I think with all the relevant bits
to USB:
drivers/usb/input/hid-input.c: event field not found
drivers/usb/input/hid-input.c: event field not found
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
Nvsound: Unable to change the Playback SampleRate 44100, set back to 48000
usb 1-5.2: new full speed USB device using address 7
ehci_hcd 0000:00:02.2: qh f3dff380 (#0) state 1
drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic
usbcore: registered new driver usbserial_generic
usbcore: registered new driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
drivers/usb/serial/usb-serial.c: USB Serial support registered for PL-2303
pl2303 1-5.2:1.0: PL-2303 converter detected
usb 1-5.2: PL-2303 converter now attached to ttyUSB0
usbcore: registered new driver pl2303
drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor
driver v0.11
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
> To find the VID and PID (another way) use the "lsusb" command, if the
> device has a nice friendly string you will be able to see it in the
> list, ("lsusb -v" for loads of info), if you are having a problem
> finding the device do "lsusb" without and with the device plugged in
> and spot the difference.
lsusb gives the same whether it is plugged in or not:
Bus 003 Device 003: ID 1267:0103 Logic3 / SpectraVideo plc
Bus 003 Device 002: ID 046d:c401 Logitech, Inc. TrackMan Marble Wheel
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 007: ID 067b:2303 Prolific Technology, Inc. PL2303
Serial Port
Bus 001 Device 006: ID 041e:401c Creative Technology, Ltd Creative
WebCam NX [PD1110]
Bus 001 Device 005: ID 0c0b:27cb Dura Micro, Inc. (Acomdata) 6-in-1
Flash Reader and Writer
Bus 001 Device 003: ID 05e3:0605 Genesys Logic, Inc.
Bus 001 Device 001: ID 0000:0000
So either it doesn't see the phone or something else is wrong. I'm
going to try in Windows and if it doesn't detect there then something
is wrong, probably with the port and I'll try a different one.
Kind regards,
Julian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEz2xAjs/5IBdCO1ERApM2AJ9xvlShZ96TWXJAPNeTZ0w7GU9QJgCfd9FW
2CLglCLqlvD21b4WQyhpJLc=
=IZqW
-----END PGP SIGNATURE-----
--
The Mailing List for the Devon & Cornwall LUG
http://mailman.dclug.org.uk/listinfo/list
FAQ: http://www.dcglug.org.uk/linux_adm/list-faq.html