The converter is identified by the system that the mos module is loaded. Right now I’m not sure if its due to a problem with the driver or my clientapplication, since it has been upgraded since my last try. Comment on this change optional. See below for log extracts from dmesg from my server running Gutsy and Hardy. Martin Kossick hacktick wrote on I tested with another computer and had the same problem.
|Date Added:||14 April 2004|
|File Size:||46.38 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
With Intrepid the mos seams to install correctly; [ When running Gutsy everything worked fine. Thank you for taking the time to report this bug and helping to make Ubuntu better.
Linux Kernel Driver DataBase: CONFIG_USB_SERIAL_MOS USB Moschip / USB Serial Driver
See full activity log. Please reopen if this is still an issue in the current Ubuntu release http: Martin Kossick hacktick wrote on As a result this bug is being closed. I’ve moschio included an verbose listing of lsusb on the converter. Hi, thank you for reporting this bug.
Right now I’m not sure if its due to a problem with the driver or my clientapplication, since it has been upgraded since my last try. Other bug subscribers Subscribe someone else. Output from dmesg in Gutsy: But when the module should identify the converter I get the message “probe of Comment on this change optional.
Also, please be sure to provide any requested information that may have been missing. Still working on it. Email me about changes to this bug report. Apologies if it has reached you inappropriately; please just reply to omschip message indicating so. Andreas andreas-dahlen wrote on Jeremy Foshee jeremyfoshee wrote on Most of my applications is still working eventhough some fixes where needed.
Moschip does provide the code for a driver but I have msochip unable to get it to compile.
MCS7840 — USB 2.0 to Quad Serial Controller
The converter is identified by the system that the mos module is loaded. To reopen the bug, click on the current status under the Status column and change the status back to “New”.
It would help us a moachip if you could test it, and if it is still an issue, we would appreciate if you could upload updated logs and any other logs that are relevant for this particular issue. To post a comment you must log in. See below for log extracts from dmesg from my server running Gutsy and Hardy. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
I believe I have the same device reported above.
iMX6.Q7A-551Board USB remote Desktop Wakeup from MEM power state
I tested with another computer and had the same problem. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. Output from dmesg in Hardy: Bus Device You need to log in to change this bug’s status. You are not directly subscribed to this bug’s notifications.