SOLVED iMac: 'i8042: No controller found'
I have server installed FOG 1.2.0 on CentOS.
My clients are iMac computers old, the years 2009, 2010 and 2011. I’ve managed to start a team with the client, ipxe.
But when I start any menu option of the client, gives me error at the start
The error is The following when you go to a registrar the team of ‘Fast and Inventory Log’:
i8042: No controller found
Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(1,0)
Kernel Offset: 0x0 from 0xfffffffff81000000 (recolocation range 0x… …fff)
—[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
I have searched the forum, but I have not found the solution.
Wayne Workman last edited by
I have updated the version and now it does not give the error.
Many thanks for your help.
Ah, I installed version 1.2.0 because I followed the instructions from the wiki:
I don’t know why I installed the 1.2.0
I’m going to upgrade to the version 1.5.0 and see if that resolves the problem.
Thanks a lot
@mileguito Well 1.2.0 is old but if I remember correctly some kernel parameter was missing or EFI_STUB has not been compiled into the kernel. Not sure, but using the latest FOG should definitely fix this.
I have to tell you that 1.2.0 is about 4 years old and is no longer supported by the developers. The latest version of FOG is 1.5.0.
From your error:
Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(1,0) Kernel Offset: 0x0 from 0xfffffffff81000000 (recolocation range 0x… …fff) —[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
This tells me that the kernel you are using (bzImage) is not the same version as required by the virtual disk (init.xz). In simple terms the kernel (bzImage) can’t connect to the vhd (init.xz). Did you happen to update the kernel for FOG 1.2.0 with the newest kernel intended for a later version of FOG?
I can also tell you we’ve seen this error message with newer installs of FOG (newer than 1.2.0) if the FOG admin uses the ipxe boot file defined in dhcp option 67, of ipxe.0 (or any .0 file) instead of undionly.kpxe.
Lastly this error message “i8042: No controller found”, is only a warning and not an error.