Dec 21, 2020 • Filed to: USB Recovery • Proven solutions
I have a new computer and run Windows 8 Professional. Two days ago Printer HP Officejet 6700 Premium was working fine. Tried to print today and pop said 'Unable to communicate with printer'. Everything checks out with the printer. When into devices and found a problem with the desk top, 'PCI Serial Port doesn't have a driver'.
- I use LabView 8.0 and want to read out the values from the aboved named system from Keyence. I use it with 2 laser to make the hight measuring of a coated film. For this I want to use the RS 232 port from the Keyence measuring device I did all the wiring with the special connectors from Keyence. So its connected to my LPT1 port at my computer.
- Update Device Driver: Open Disk Management Expand 'Universal Serial Bus Controllers' Right-click 'Generic USB Hub'.Full steps: Fix 4. Fix Root Hub: Open Device Manager Expand Universal Serial Bus Controllers Right-click USB Root Hub.Full steps: Fore More Fixes: Change USB settings and reinstall USB driver to make USB recognized (in Fix 5 and 6).
Have you ever had difficulty connecting your devices to your computer using a Prolific USB to Serial adapter? If yes you are lucky to find this page, it will give you all the information need to fix an unresponsive Serial driver adapter. You may have noticed a yellow exclamation mark hovering over or beside the USB to Serial Driver when searching your Device Manager and if you have we can all agree that it signifies a prevailing problem.
Overview of the Error
If you are not able to connect your device to your PC using a USB to Serial adapter it may be that
- The USB driver is outdated
- The USB Driver is missing
- Or even a corrupted driver
While you can't be so sure what the exact problem is there are solutions you can adopt to fix the issue once and for all. Read on to find quick fixes to resolve the problem.
1# Fix Prolific USB to Serial Driver not Working
Solution: Roll your Prolific USB to Serial Driver back to an older version
Updating your drivers often work wonders for your system because it makes sure that it runs on the latest features that guarantee maximum functionality. Unfortunately updating your drivers can cause this kind of error especially if your latest update does not work too well with your hardware. Once you upgrade your PC to the latest Windows version your Prolific USB to Serial Driver also updates to the latest driver software and if the driver is not compatible with your Hardware issues may arise. To correct the error, you will have to download the driver again by following these steps.
- Right-click on your PC Start button and open Device Manager
- Double click LPT and COM ports then locate the Prolific USB to Serial Driver and right-click it so you can select Update Driver
- For driver software click My computer
- From My computer select 'Let me pick from a list of drivers available'
- Choose an older version from the list then click Next
- The driver you selected will be installed automatically
- Once it has been downloaded reconnect the driver to see if it works.
2# Fix Prolific USB to Serial Driver 'Coder 10'
Driver issues reveal themselves in so many ways or through messages such as
- This device will not start (Code 10)
- There is no driver installed in this device
- The driver was not successfully installed
A code 10 error may arise because the chip you are using is not an original one. If you are using a fake, the manufacturer has a way of disabling it due to copy write infringement and the copy write takes effect once you download a recent update. To protect your PC from getting this code, you will have to make sure that your Windows 10 never updates a driver without approval. Updates come in the form of 64 bit and 32-bit drivers. Below we will show you how to work your way around the problem.
Window 64 bit Fix
To fix Windows 64 bit OS including Prolific USB to Serial Adapter, follow through these steps.
- Download 'PL2303_64bit_Installer.exe and Save
- Remove every USB to Serial adapter from your PC and double click the 'PL2303_64bit_installer.exe
- Follow the prompt by plugging in one USB to Serial adapter the click on Continue
- Reboot your PC to get Windows up and running
If you have followed these process through and you still see the same error go to your device manager
- Open the control panel and navigate to Device Manager
- From your control panel navigate to the System category and click the Hardware tab
- Scroll to the LPT/COM port and double click Prolific USB to Serial Comm Port
- Click Drivers in the Properties section
- The Driver you choose should read '3.3.2.102 with an appropriate date attached
- If the date is wrong then it means the wrong driver was installed
- Unplug the Serial adapter and run the steps again to install the correct driver
Window 32-bit
For Windows 32-bit OS systems follow these steps
- You will have to download the 'PL-2303_Driver_Installer.exe and save from Microsoft download link
- Run the program and eradicate the driver if you can
- Run the installer once more to install a correct driver
To Troubleshoot for error if your device still does not work
- Go to Control panel, enter System to access your Device Manager
- Scroll down to the LPT/ COM port then double click Prolific USB to Serial Comm Port
- Click Driver in the Windows Properties section
- The driver must be numbered as '2.0.2.8' and dates accordingly
If the driver was not installed, remove the Serial adapter then run 'PL2303_Driver_Installer.exe' again. Follow directions in Device Manager to download the correct driver
The three solutions listed in this article have proven to be quite helpful in fixing a Prolific USB to Serial driver not working on Windows 10. They may appear confusing at first but if you follow each step in detail you can resolve the issue.
Video Tutorial on How to Fix USB Device Not Recognized
USB Solution
- Recover USB Drive
- Format USB Drive
- Fix/Repair USB Drive
- Know USB Drive
Once you find your hardware, the same program that found it usuallytells you how it's configured. So finding out how it's configured isusually the same procedure as finding the hardware.
Here 'configuration' means the assignment of PnP bus-resources(addresses, IRQs, and DMAs). For each device, there are two parts tothe configuration question:
- What does the driver think the hardware configuration is?
- What configuration (if any) is actually set in the devicehardware?
Another problem is that when you view configuration messages on thescreen you need to know whether the reported configuration isthat of the device driver, the device hardware, or both. If thedevice driver has either set the configuration in the hardware or hasotherwise checked the hardware then the driver should have the correctinformation.
But sometimes the driver has been provided incorrect resources by ascript, configuration file, by incorrect resource parameters given toa module, or perhaps just hasn't been told what the resources are andtries to use incorrect default resources. For example, one can uses'setserial' to tell the serial port driver an incorrect resourceconfiguration and the driver accepts it without question. But theserial port doesn't work right (if at all).
A common problem is that the software doesn't detect your deviceand/or determine the right driver for it. For PnP devices, detectingthem is easy via PnP software except for the unusual case where thehardware has been disabled. The BIOS can sometimes be set to disablePnP devices or a jumper/switch on the physical device itself coulddisable it. In such a cases, the hardware can't be detected at alluntil you either reconfigure the BIOS or change a jumper/switch.
Since the PCI bus is inherently PnP, there are no hidden devices.Even though PnP devices are easy to find by PnP methods, if the driverdoesn't use PnP methods but uses the old method of probing for them atlikely address, they may not be found. This is because that, until theresources are set in a PnP device (by the BIOS or Linux), the devicemay have no address at all, so probing at likely address yieldsnothing. For the old ISA bus, some of the devices may be non-PnP andthus the old probing methods may find them. So many drivers stillprobe at likely address, in addition to using PnP methods (= PnPprobing which is sometimes also just called 'probing').
Ways to Find Hardware Devices (and their configurations): (follow linkto more details)
- Check the BIOS to make sure they are not disabled
- Watch the Boot-time Messages onthe screen
- Look in The /proc Directory Tree
- Tools for Detecting and/or Configuring all Hardware lsdev, hwinfo, discover, kudzu
- PCI: PCI Bus Inspection
- ISA Bus: ISA Bus Introduction
- ISA Bus: PnP cards
- ISA Bus: For Non-PnP Cards
- ISA Bus: For Cards with jumpers
- ISA Bus: If Neither PnP nor jumpers
Significant info on the configuration may be obtained by readingthe messages from the BIOS and from Linux that appear on the screenwhen you first start the computer. These messages often flash by toofast to read but once they stop type Shift-PageUp a few times toscroll back to them. To scroll forward thru them type Shift-PageDown.Typing 'dmesg' at any time to the shell prompt will show only theLinux kernel messages and may miss some of the most important ones(including ones from the BIOS). The messages from Linux may sometimesonly show what the device driver thinks the configuration is, perhapsas told it via an incorrect configuration file. Checking log files in/var/log may also be useful.
For the PCI bus, the notation: 00:1a:0 means the PCI bus 00 (the mainPCI bus), PCI card (or chip) 1a, and function 0 (the first device) onthe card or chip. The 2nd device on the card (or chip) 08 would be:00:08:1.
The BIOS messages display first and will show the actual hardwareconfiguration at that time, but isapnp, or pci utilities, or devicedrivers may change it later. In some cases it doesn't show devicesthat the BIOS didn't configure.
If the BIOS messages don't show as you back up tothe start of the BIOS messages using Shift-PageUp, try freezing themas they flash by, by hitting the 'Pause' key as soon as the firstwords flash on the screen. Press any key to resume. It's oftentricky to hit Pause exactly at the right time. Be sure to hold downthe 'Shift' key before hitting 'Pause' since 'Pause' is a shifted key.If you miss, hit Ctrl-Alt-Del when Linux starts booting to reboot andtry again. Once the messages from Linux start to appear, it's toolate to use 'Pause' since it will not freeze the messages from Linux.
To set things in the BIOS such as IRQs reserved for legacy hardware,serial port addresses, etc. you need to get into the BIOS (CMOS) setupmenus at boot time. Each BIOS brand has different keys you need tohold down to do this. There are lists on the Internet. Sometimes byfreezing the BIOS messages or watching the screen, the key you need topress will be indicated in a message such as 'Press DEL for setup'.But it may flash by so fast that you miss it. Of course, you don't setstuff in the BIOS that you don't understand, or your PC may becomedisabled.
Messages from the BIOS at boot-time tell you how the hardwareconfiguration was then. The current configuration may still be thesame since Linux should hopefully accept what the BIOS has done ifit's OK. Messages from Linux may be from drivers that used kernel PnPfunctions to inspect and/or set bus-resources. These should becorrect, but beware of messages that only show what the driver wastold from a configuration file. It could be wrong. Of course, if thedevice works fine, then it's likely configured the same as the driver.
Starting with Kernel 2.6, in addition to the /proc directory tree,there's also a /sys tree See The /sys Tree. These trees are useful for finding resourceconfigurations and devices. The 'files' in them represent data in thekernel memory and don't exist at all on you harddrive. Programs suchas lspci get their info from the /proc tree so such programs shoulddisplay the results in more readable form than directly inspecting the'files' in /proc. Here are 4 /proc 'files' that show resources whichhave been registered in the kernel by device drivers.
Since Linux's plug-and-play works by letting device drivers allocateresources for their device, there may be no listing of resources usedby some of your hardware if the driver hasn't yet requested that suchresources be reserved. For the case of kernel modules (loadabledevice drivers), if the module hasn't loaded yet, the kernel doesn'tknow about any resources it needs. Sometimes, the module only loadswhen you start an application that needs it. So if certain hardwareis missing from these 'files' in /proc, it may mean that the hardwarehasn't yet been used. For example, even though your floppy drive hasa floppy disk in it and is ready to use, the interrupt for it willnot show up unless its in use.
/pts shows I/O addresses. If there's a mistake (wrongaddress) it means trouble since the device will not get bytes sent toit.
/proc/iomem shows registered IO memory addresses.
/proc/interrupts shows the interrupts currently in use.
/proc/dma shows the dma (Direct Memory Access) ISA dma channel allocations.
In the past, the author observed the listing of interrupts that didn'texist. In some cases it showed that a few such interrupts wereactually sent. This could be due to the issuing of erroneousinterrupts due to hardware defects.
/proc/bus/ has subdirectories (subfolders) input/, pci/, andisapnp/. The format of most of the files in this directory is verycryptic, often just a copy of the bytes in the configuration space.So, use them only as a last resort. The input/ subdirectory hasinformation on input devices such as the keyboard and mouse. It's notas cryptic as the other directories under /proc/bus/ and might yieldsome useful information about input devices that are PS2 or on the LPCbus (See LPC Bus). Unfortunately, what I'veseen doesn't say that it's on the LPC bus when it likely is. In/pci/00/ there is one binary file for each pci device where the filenames are the pci-slot-numbers (also called pci-slot-names). The 00means pci bus 0.
Starting with kernel 2.6 there's a new /sys directory for PnPconfiguration. It's a sysfs type of file system and it's somethinglike the /proc filesystem since the 'files' represent information inthe kernel memory and are not on your harddrive. But it's not asuseful as the /proc filesystem. Originally (in the 2.5 kernels) itwas called 'driver file system' of type 'driverfs'.
In the sysfs, each device which exists on your system has it's owndirectory which contains files showing the resources allocated to it.Such device directories have names like 0000:00:12.0@ or 00:06@. Whatdevices are these? The first is a PCI card in 'slot' 12 of your PC.The slot may actually be labeled PCI2 inside your PC (2 instead of12). That's because low numbered 'slots' are used for built-indevices on the motherboard that don't use any physical slots. In thisexample, 'slots' 1-10 would be built-in and actual slots 11-14 arelabeled 1-4. By typing 'lspci' you'll be able to match the numbers(like 0000:00:12.0) to names (like IDE interface). Type 'lspci -v'or 'lspci -vv' to see more.
Well then, what is 00:06 ? It's an ISA card (or built-in device) butit's not ISA slot 6 (like the PCI numbering). When a search was madefor ISA-PNP devices, it was the 6th one found. More precisely, it wasthe 7th one found since there's a device numbered: 00:00. So how doesone identify them? Well, you could type: 'cat */*' and display allthe files for all the devices, but even then you don't see the devicenames (but do see info from which you can identify them). Thisinconvenience will hopefully be fixed in the future.
Not only do these files supply information on the bus-resourceconfiguration (in somewhat cryptic format) and drivers (in 'driver'directories), but in the future, you should be able to use them tochange the resource configuration. Right now (Aug 2004) you can'tconfigure the PCI bus with it. A serious limitation is that per thepresent 'driver model' you can't change the resource of a device thathas been assigned to a driver which likely means that you'll need tounload the driver module in order to use it. If the driver is builtin, there's no hope. These serious limitations will hopefully beeliminated in the future. In the kernel documentation is a file:'pnp.txt' telling how to configure. As of Aug. 2004, it was muchout-of-date but the author is working on an update. Using the /systree to configure resources is known as the 'Linux Plug and Play UserInterface'.
The other part of 'Linux Plug and Play' is the kernel interface usedby device drivers. This has changed a lot starting with kernel 2.6but most drivers are still using the old interface (as of Aug. 2004).It's possible also for drivers (or you) to use the 'user interface'which needs improvement.
It's easy to find out what bus-resources have been assigned todevices on the PCI bus with the 'lspci' and/or 'scanpci' commandsThe options -v or -vv will show more detail. In some cases, 'scanpci'will find a device that 'lspci' can't find. That's because 'scanpci'directly searches for devices on the pci bus (via the configurationspace) and doesn't use data obtained by the kernel (where it could bewrong due to a kernel bug --I've just found such a case).
This info in more cryptic format is found in 'files' located in the/sys and /proc trees. In/sys/bus/pci/devices the file vendor will contain thevendor id number such as 0x4B8C, etc. In still more cryptic formatit's in /proc/bus/pci. Such information in older kernelsprior to kernel 2.6, was in /proc/pci (non-cryptic but IRQsin hexadecimal) or in /proc/buspci/devices (cryptic display).
In most cases for PCI you will only see how the hardware is nowconfigured and not what resources are required. In some cases youonly see the base addresses (the starting addresses of the range) butnot the ending addresses. If you see the entire range then you candetermine how many bytes of address resources are needed.
Keyence Port Devices Driver Download
For cards on the ISA bus, it's not as simple as for the PCI buswhich is inherently PnP. Later ISA cards were PnP but older ones werenot. Also, some cards that are PnP had their PnP disabled byspecial software which runs only on MS. The non PnP cards areconfigured by jumpers on the card or by MS software.
If it's a PnP card you may try running pnpdump --dumpregsbut it's not a sure thing. The results may be seem cryptic but theycan be deciphered. Don't confuse the read-port address whichpnpdump uses for communication with PnP cards with the I/Oaddress of the found device. They are not the same.
LPC (Low Pin Count) is a bus-like interface often used on laptopsand increasingly used on desktops too. To find out if you have LPCtype 'lspci' and look for 'LPC'. There are other words next to 'LPC'such as 'ISA Bridge .. LPC Interface Controller' or 'LPC Bridge',etc. LPC is not really ISA but it substitutes for an ISA bus.
The old ISA bus was slow and devices that needed more speed were puton the newer PCI but. But devices that didn't need high speed wereoften implemented by chips on the motherboard and remained on the ISAbus even though there were no slots for any ISA cards. Then the LPCbus came along to replace what remained of the ISA bus. LPC is muchsmaller than ISA and just as fast since it runs at 4 times the clockspeed of ISA. Its multiplexed bus for data/address and control isonly 4 bits wide. To send a byte requires splitting the byte into 2half-bytes and then putting them back together. So its clear why it's'Low Pin Count' = LPC. There's also a few other lines in the bus.
This small LPC interface is used for slow 'legacy' devices such asserial ports, parallel ports, and floppy drives. So a computer usingLPC will have all fast devices on the PCI bus, etc. and slow (legacy)devices on the LPC bus interface. All LPC devices will be on-board;there are no LPC slots.
LPC has no standards for Plug-and-Play configuring but says that theBIOS or ACPI should do the configuring. Devices on this bus sometimesuse isapnp. Linux support for LPC as of late 2004 was very muchincomplete but Linux has some support for the configuring aspects ofACPI. Sometimes a BIOS menu lets one manually PnP-configure deviceson the LPC bus but it may not tell you that the device resides on LPC.
Keyence Port Devices Driver
A major chip on the LPC bus is the superio chip which contains legacyIO devices: serial and parallel ports, floppy controller, keyboardcontroller, mice, etc. BIOS data may also reside on the LPC bus. Thekeyboard and mouse (input devices) should be listed in/proc/bus/input/devices but instead of seeing 'lpc' it seems to show'isa0060/serio0, etc. even though it's on the lpc bus and not the isabus.
Before the LPC bus became popular, there was an 'X-bus' (notcovered in this HOWTO) which served the same purpose as the LPC busbut wasn't so compact as LPC. Some PCs have both LPC and an X-bus.
Keyence Port Devices Driver Windows 10
In contrast to PnP cards, non-PnP cards always have their resourcesset in the hardware. That is they always have an address and IRQunless there is a jumper setting, etc. for disabling the device.Sometimes the resources used can be found by probing done by thedevice driver or by other software that does probing. For example'scanport' (Debian only ??) probes most IO port address and may findISA devices. But be warned that it might hang your PC. Sometimes itwill fail to find hardware that's actually there (since the hardwarehas the default 0xff in it's registers). Even if It finds thehardware it will not show the IRQ nor will it positively identify thehardware.
So one way to try to find such hardware is to start a driver, whichmay probe for such hardware. By looking at the boot-time messages,you might see a driver start and find the hardware. Otherwise, youmay need to find a driver and start it (for example, by having it loadas a module).
Finding the right driver may be difficult. Sometimes there just isn'tany driver since some devices aren't (yet ?) supported by Linux. Todetermine which driver you need, look at any documentation which mightidentify the card. If this fails, look on the card itself, includingimportant names/numbers on the chips. But the identification of thedriver module you need may not be anywhere on the card. You couldfind the FCC id on the card and then search the Internet with the FCCid number to try to find more information about the card (or the chipson it).
If the card has jumpers to set the resources (configuration) thenone may look at how the jumpers are set. There are some cards thathad both PnP and jumpers. They worked like jumper cards if PnP wassomehow disabled. Sometimes a card has labels on it showing how toset the jumpers (or at least gives some clue). You may need thedocumentation that came with the card (either printed or on a floppydisk). Perhaps you can find it on the Internet.
One the most difficult cases is where software running under MS hasbeen used to configure either a non-PnP card or a PnP card where PnPhas been disabled by the same MS software. So you can't configure itby PnP nor by jumpers. In this case your only hope is to probe foraddresses as described in Non-PnP Cards. Ortry to find the MS software that configured it. Drivers langchao laptops hp pavilion.
In a duplication of effort, various major distributions of Linuxdeveloped their own tools for detection and/or configuration ofhardware. This configuring is usually a lot more than just theresource type configuring of Plug-and-Play. It's configuring ingeneral which is mostly beyond the scope of this howto.
Then other distributions, such as Debian, might obtain copies of thetool and offer it to their users as an option, or as a troubleshootingtool. These tools likely make use of the standard Linux tools fordetecting hardware such as 'lspci'. In the following list of tools,the name of the distribution that developed it is in parentheses, butthe tool is likely available also in other distributions.
Keyence Port Devices Driver Wireless
- hardinfo
- hwinfo (SuSE) detects move stuff than discover
- discover (Progeny, used by Debian)
- Kudzu (RedHat) detects and configures
- lsdev (standard Linux command)
- hwsetup-knoppix (Knoppix, based on Kudzu)
There are various tools available to find and possibly configure various type of devices. This configuring is configuring in generalwhich is not covered by this howto.
- read-edid (get-edid): gets parameters of VESA monitors (exceptvery old ones)
- sndconfig: for soundcards
- printtool: printers, must have X-window running
- pconf-detect: parallel ports
- gpm-mouse-test:detects and tests mice
- mdetect: detects and configures mice Does it know about the mice devices in /dev/input/?
- nictools-pci (and nictools-nopci) for ethernet cards
- hdparm: configure hard drive hardware
- hotplug: used by kernel
- xvidtune: tune video for use with Xwindows (SeeXFree86-Video-Timings-HOWTO)
Some people have attempted to use Windows to see how bus-resourceshave been set up. Unfortunately, since PnP hardware forgets itsbus-resource configuration when powered down, the configuration maynot be the same under Linux. For non PnP hardware (or where someonehas disabled PnP inside the device by jumpers or Windows software),then using Windows should work OK. Even for PnP, it often turns outto be the same because in many cases both Windows and Linux simplyaccept what the BIOS has set. But where Windows and/or Linux do theconfiguring, they may do it differently. So don't count on PnPdevices being configured the same.
NextPreviousContents