![]() ![]() More recent Fedora release includes newer upstream software that fixes ![]() Lifetime, sometimes those efforts are overtaken by events. Version prior this bug is closed as described in the policy above.Īlthough we aim to fix as many bugs as possible during every release's Of Fedora, you are encouraged change the 'version' to a later Fedora To see this bug fixed and are able to reproduce it against a later version Thank you for reporting this issue and we are sorry that we were notĪble to fix it before Fedora 21 is end of life. Plan to fix it in a currently maintained version, simply change the 'version' Package Maintainer: If you wish for this bug to remain open because you This bug will be closed as EOL if it remains open with a Fedora 'version' It is Fedora's policy to close allīug reports from releases that are no longer maintained. This message is a reminder that Fedora 21 is nearing its end of life.Īpproximately 4 (four) weeks from now Fedora will stop maintainingĪnd issuing updates for Fedora 21. workaround somebody has found (will test it when I have time): "official" Linux driver (doesn't build on 4.0): Here are some random infos that might be relevant I found in the internet about this chip: The exact model I have is this one in the photo ("340" can be read on the blue plastics of the DB9 connector): Same configuration works with an FTDI adapter. The minicom configuration is 15200 8N1 without hardware flow control, with software flow control. try using the device with minicom or screen Version-Release number of selected component (if applicable): The same ch340 device works fine on Windows 7 with official driver, so the device isn't broken. Using an FTDI based adapter works perfectly on the contrary. usb 1-1.4.3: ch341-uart converter now attached to ttyUSB0īut opening the device with minicom or screen doesn't produce any input or output. usb 1-1.4.3: New USB device strings: Mfr=0, Product=2, SerialNumber=0 usb 1-1.4.3: New USB device found, idVendor=1a86, idProduct=7523 ![]() usb 1-1.4.3: new full-speed USB device number 15 using xhci_hcd Kernel seems to bring up correctly the driver: I can get it working OK on general linux no problem.I've bought a USB serial adapter which is based on ch340 chipset.īus 001 Device 015: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter The dmesg command tells you the device is /dev/ttyUSB2.Īlternatively, install GeigerLog and run its Help -> Autodiscover connected USB port. If you get more than 1 line, you need to determine which one it is. usb 3-10.3: ch341-uart converter now attached to ttyUSB2īus XXX Device YYY: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapterĬheck available devices with "ls -al /dev/ttyU*" to get something like:Ĭrw-rw- 1 root dialout 188, 0 Dez 16 10:13 /dev/ttyUSB0Ĭrw-rw-rw- 1 root dialout 188, 2 Dez 16 10:05 /dev/ttyUSB2 usb 3-10.3: New USB device strings: Mfr=0, Product=2, SerialNumber=0 usb 3-10.3: New USB device found, idVendor=1a86, idProduct=7523 usb 3-10.3: new full-speed USB device number 87 using xhci_hcd So, unless you use a very strange Linux distribution, the device should be available right after connection without any further installation.Ĭonnect the GMC-300E and type "dmesg" in a terminal window. This USB-to-Serial device is recognized by the kernel since very long. Trying to get it to work on linux need to know what kmod-usb-whatever driver to load for the usb device 1a86/7523/254 latest usb serial driver chip on the gmc300e devices GQ Electronics Technical Support Forum - What kmod-usb driver for gmc300e ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |