Portal Home > Knowledgebase > VMware Knowledge Base > "No such device errors" in /var/log/messages.l when booting ESX Server 3.5 and later

"No such device errors" in /var/log/messages.l when booting ESX Server 3.5 and later

Details

Upon booting hosts with ESX Server 3.5 and later versions, error messages similar to the following are seen in /var/log/messages.l:

Aug 3 20:05:21 myserv-222 kernel: ppdev: user-space parallel port driver
Aug 3 20:05:21 myserv-222 insmod: /lib/modules/2.4.21-57.ELvmnix/kernel/drivers/parport/parport_pc.o: init_module: No such device
Aug 3 20:05:21 myserv-222 insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg
Aug 3 20:05:21 myserv-222 insmod: /lib/modules/2.4.21-57.ELvmnix/kernel/drivers/parport/parport_pc.o: insmod parport_lowlevel failed
Aug 3 20:05:21 osdc-esxst222 kernel: lp: driver loaded but no devices found

Solution

This error occurs when no parallel port is found on the host during the boot check and is expected for hosts without parallel ports or for hosts where the parallel port has been disabled in BIOS setup. The message can be safely ignored if you do not need the parallel port.  If you do need to use the parallel port, check to make sure that the port is enabled in BIOS setup. Note that some newer servers are designed without a parallel port (legacy-free) and have no related settings in the BIOS.
Based on VMware KB 1007304


Also Read

Language: