05ad:0fba pl2303 driver not recognizing

[Kevin]

I use for work a usb-serial device from Radio Shack. THe devices recognizes as a pl2303 device, but it does not work. I set my device to look for /dev/ttyUSB0. lsusb displays missing vendor informationT there is already a thread about this in another forum, sort of outdated, but exactly the problem I am having..

http://bugs.centos.org/view.php?id=2954

I expect my serial device to talk to my machine via dnc-x as it does in windows (EASY-DNC).

-------------------

Description: Ubuntu 12.04 LTS
Release: 12.04
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu5
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: kevin 1464 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf0000000 irq 44'
   Mixer name : 'Realtek ALC880'
   Components : 'HDA:10573055,10573055,00100700 HDA:10ec0880,08800000,00100800'
   Controls : 22
   Simple ctrls : 14
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=84e0207c-0808-445a-ae09-e3c0001c612c
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ALIENWARE m5500i-R3
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic-pae root=UUID=57a65fe3-792e-4f82-adff-86b6424e23fb ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-23-generic-pae N/A
 linux-backports-modules-3.2.0-23-generic-pae N/A
 linux-firmware 1.79
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Tags: precise precise
Uname: Linux 3.2.0-23-generic-pae i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
WifiSyslog:

dmi.bios.date: 05/30/2007
dmi.bios.vendor: ALIENWARE
dmi.bios.version: 2.07
dmi.board.name: m5500i-R3
dmi.board.vendor: ALIENWARE
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: ALIENWARE
dmi.chassis.version: Not Applicable
dmi.modalias: dmi:bvnALIENWARE:bvr2.07:bd05/30/2007:svnALIENWARE:pnm5500i-R3:pvrNotApplicable:rvnALIENWARE:rnm5500i-R3:rvrNotApplicable:cvnALIENWARE:ct10:cvrNotApplicable:
dmi.product.name: m5500i-R3
dmi.product.version: Not Applicable
dmi.sys.vendor: ALIENWARE

[Fabio Marconi (fabiomarconi)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1019836

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Kevin (0430kev)]

apport information

[Kevin (0430kev)]

apport information

[Kevin (0430kev)]

apport information

[Kevin (0430kev)]

apport information

[Kevin (0430kev)]

apport information

[Kevin (0430kev)]

apport information

[Kevin (0430kev)]

apport information

[Kevin (0430kev)]

apport information

[Kevin (0430kev)]

apport information

[Kevin (0430kev)]

apport information

[Kevin (0430kev)]

apport information

[Kevin (0430kev)]

apport information

[Kevin (0430kev)]

apport information

[Kevin (0430kev)]

apport information

[Kevin (0430kev)]

apport information

[Kevin (0430kev)]

apport information

[Kevin (0430kev)]

apport information

[Kevin (0430kev)]

apport information

[Kevin (0430kev)]

apport information

[penalvch (penalvch)]

Kevin, thank you for reporting this and helping make Ubuntu better. Could you please unplug all usb devices from your PC, plug in the usb device, execute the following at a terminal and post the results to this report:
lsusb

As well, if you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

[Kevin (0430kev)]

Here is the displayed results of lsusb:

kevin@XXXXX:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 05ad:0fba Y.C. Cable U.S.A., Inc.

I will try the upsream kernel now.

[Kevin (0430kev)]

well it seems the latest upstream kernel is version 3.5 already, mine is:

Ubuntu 3.2.0-23.36-generic-pae 3.2.14

Im not sure which version to use from the mainstream directory..

[Kevin (0430kev)]

Christopher, im unsure which kernel to try, can you point me in the right direction? Thanks

[Kevin (0430kev)]

Ok, I figured it out. here is what it says:

kevin@Aliens:~$ uname -a
Linux Aliens 3.5.0-999-generic #201207030405 SMP Tue Jul 3 08:13:19 UTC 2012 i686 i686 i386 GNU/Linux
kevin@Aliens:~$ lsusb
Bus 005 Device 002: ID 05ad:0fba Y.C. Cable U.S.A., Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

[penalvch (penalvch)]

Kevin, the issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel . If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about the status. Thanks in advance.

[penalvch (penalvch)]

Kevin, could you please provide the full computer model as noted on the sticker (ex. Alienware M17X R2)?