Timeline for ttyUSB serial device not being created in Ubuntu18.04
Current License: CC BY-SA 4.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 19 at 8:52 | vote | accept | steve | ||
| Jan 12 at 12:47 | answer | added | steve | timeline score: 0 | |
| Jan 12 at 11:52 | comment | added | ChanganAuto | Just a note: Ubuntu 18.04 is EoL, you should upgrade to a supported release. | |
| Jan 12 at 10:54 | history | edited | steve | CC BY-SA 4.0 |
added 12 characters in body
|
| Jan 12 at 10:19 | history | edited | steve | CC BY-SA 4.0 |
added 6 characters in body
|
| Jan 12 at 10:16 | comment | added | steve | Thanks. I'm seeing using lsmod that the drivers appear to be loaded, so from my newbie perspective it looks OK ( obviously its not....). What steps would you suggest to determine what would be the correct driver please, if I've loaded what I think is the corresponding drivers for the kernel version? | |
| Jan 12 at 10:13 | history | edited | steve | CC BY-SA 4.0 |
added 1146 characters in body
|
| Jan 12 at 9:32 | comment | added | sawdust | Those kernel message should be edited into your post (so that it's readable), rather than entered as comments. The kernel messages (as expected) report that the host has detected a newly attached USB device. Those messages are from the USB Host controller driver. The next set of messages should be from the USB gadget driver, in this case, the Prolific driver. The typical reason for no driver initialized for the gadget after the USB Host finds the device is that the proper driver is not installed (in the filesystem). | |
| Jan 12 at 8:43 | comment | added | steve | So my question now would be - what is the relevence of a missing "pl2303 converter detected" message and how we would fix it? | |
| Jan 12 at 8:18 | comment | added | steve | Thnak you, thats really helpful! | |
| Jan 12 at 8:14 | comment | added | sawdust | "When I run dmesg however ..." - Little-known (newbie) fact: of all the things you've done, analyzing the syslog (e.g. retrieving kernel messages using the dmesg command) needs to be the first step in trying to solve this type of problem. Since you have one system that you claim success, and another that has issues, you need to capture the kernel messages when the USB adapter is inserted on each system, and compare them. | |
| Jan 12 at 4:32 | history | edited | steve | CC BY-SA 4.0 |
added 6 characters in body
|
| Jan 12 at 4:20 | history | edited | steve | CC BY-SA 4.0 |
added 512 characters in body
|
| S Jan 12 at 4:15 | review | First questions | |||
| Jan 12 at 4:43 | |||||
| S Jan 12 at 4:15 | history | asked | steve | CC BY-SA 4.0 |