Qualcomm Atheros PCIE Ethernet Controller v2.1.1.5 - AlienWare VXFFH



  • Hy

    We have just acquired several AlienWare VXFHH and we would like to use the deployment of the machines via Fog except that I can not start the application. Every time I start the AlienWare network I have several error messages according to the kernel I use we will try to solve the one with the kernels 4.1.2 with FOG 1.2.0

    So here’s the message:

    i8042: No controller found
    

    I did my research and it seems that it concerns the keyboard like explain by
    @george1421

    @george1421 said in Fog and Intel NUC 6i5SYK : i8042 no controller found:

    Do I know what that error means? Yes I do, but its because I’m old.

    The keyboard controllers on the early mobos used an embedded intel controller 8051. The 8042 is just a newer and significantly smaller version of the 8051. So the FOS kernel has thrown the error above because it can’t find something that resembles it.

    In simple english, the FOS kernel can’t find the keyboard controller.

    I assume you are using fog 1.2.0 stable. (You should see 1.2.0 posted on the FOG Cloud on the WebGUI management page).

    How to fix: One way would be to upgrade to the trunk version of FOG to get the latest kernels. The other way is to manually update the kernels on 1.2.0 to the trunk version. NOTE: Only update the kernels not the kernels + inits.

    1. You can download the new kernels from here. The latest ones are 4.6.2 (or newer)
      https://fogproject.org/kernels/bzImage
      https://fogproject.org/kernels/bzImage32

    2. Rename the existing files in /var/www/html/fog/service/ipxe

    3. Then place the downloaded files in that folder path

    4. Reboot your target computer

    I got error message to disappeared but I ended up with an Attempting to register infinite host. I followed the advice of @Amir But it has no effect

    @Amir said in *Attempting to send inventory............ FOREVER?:

    Chavenor, [/B]
    The cause of this issue might be related to the configuration file located at /tftpboot/pxelinux.cfg/default. Take a look at the parameter under FULL HOST REGISTRATION sub menu and make sure the IP address of the FOG Server that the host is trying to resister is the correct IP address of your FOG Server. in order to do this go to Terminal and type: sudo vi /tftpboot/pxelinux.cfg/default. If the IP address of your FOG Server is not what its suppose to be then make the changes, save your config, exit and then type: sudo /etc/init.d/networking restart.
    Hope this helped.

    When I run Fog on the client machine I can access the Client System Information (Compatibility) but the MAC address of the machine is not detected and there is no IP address assigned to this step then That the DHCP works correctly because I can load the FOG client interface

    Do you have an idea ?

    Thank you for your help


    Bonjour

    Nous venons de faire l’acquisition de plusieurs AlienWare VXFHH et nous voudrions utiliser le déploiement des machines via Fog sauf que je n’arrive pas à démarrer l’application. A chaque fois que je démarre l’AlienWare en réseau j’ai plusieurs message d’erreur selon le kernel que j’utilise nous allons essayer de résoudre celui avec le kernels 4.1.2 avec FOG 1.2.0

    Donc voici le message:

    i8042: No controller found
    

    J’ai fait mes recherches et il semblerait que cela concerne le clavier comme expliquer par @george1421

    @george1421 said in Fog and Intel NUC 6i5SYK : i8042 no controller found:

    Do I know what that error means? Yes I do, but its because I’m old.

    The keyboard controllers on the early mobos used an embedded intel controller 8051. The 8042 is just a newer and significantly smaller version of the 8051. So the FOS kernel has thrown the error above because it can’t find something that resembles it.

    In simple english, the FOS kernel can’t find the keyboard controller.

    I assume you are using fog 1.2.0 stable. (You should see 1.2.0 posted on the FOG Cloud on the WebGUI management page).

    How to fix: One way would be to upgrade to the trunk version of FOG to get the latest kernels. The other way is to manually update the kernels on 1.2.0 to the trunk version. NOTE: Only update the kernels not the kernels + inits.

    1. You can download the new kernels from here. The latest ones are 4.6.2 (or newer)
      https://fogproject.org/kernels/bzImage
      https://fogproject.org/kernels/bzImage32

    2. Rename the existing files in /var/www/html/fog/service/ipxe

    3. Then place the downloaded files in that folder path

    4. Reboot your target computer

    Je message d’erreur à disparue mais je me suis retrouvé avec un Attempting to register host infini. J’ai suivi les conseille de @Amir mais cela ne fait aucun effet.

    @Amir said in *Attempting to send inventory............ FOREVER?:

    Chavenor, [/B]
    The cause of this issue might be related to the configuration file located at /tftpboot/pxelinux.cfg/default. Take a look at the parameter under FULL HOST REGISTRATION sub menu and make sure the IP address of the FOG Server that the host is trying to resister is the correct IP address of your FOG Server. in order to do this go to Terminal and type: sudo vi /tftpboot/pxelinux.cfg/default. If the IP address of your FOG Server is not what its suppose to be then make the changes, save your config, exit and then type: sudo /etc/init.d/networking restart.
    Hope this helped.

    Lors du lancement de Fog sur la machine client j’arrive à accéder au Client System Information (Compatibility) mais l’adresse MAC de la machine n’est pas détecté et on ne vois pas d’adresse IP d’attribué à cette étape alors que le DHCP fonctionne correctement car j’arrive à charger l’interface client de FOG

    Auriez-vous une idée ?

    Merci de votre aide


  • Moderator

    @melvinpaz I’m a little concerned that it appears the ethernet controller isn’t supported with the newer kernel. But from the disk information you supplied I can guess that if you continue using 1.2.0 you will have issues there once the nic controller issue has been resolved too.

    I would spin up a new FOG server using fog 1.3.0RCx to test to see if you get better hardware support with 1.3.0 before you upgrade your production server. Also FOG 1.3.0 will give us a few more debugging tools than 1.2.0.

    If you want to continue to test with 1.2.0, I would recommend that you create a debug capture (from the host configuration advanced menu, if I remember correctly). The debug capture/deploy will allow you to interact with the customized linux OS on the target computer. Once you get to the command line prompt then we can key in lspce -nn to give us a list of hardware that the FOS engine (linux OS that runs on the target computer) sees. We are looking for the ethernet adapter and something that looks like this

    00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network Connection [8086:1502] (rev 04)
    

    In this case we need to know the numbers in the square brackets like [8086:1502]. We can look up these numbers to see if they are supported in the current linux kernels.


  • Senior Developer

    I think updating to the 1.3.0 RC series will certainly not “hurt” anything especially considering you have these NVMe disks (which are supported natively in 1.3.0, but were not with 1.2.0 and earlier versions). It may also help get your Network working. The network checking in 1.2.0 was a “guessing” game more than anything and I think it had essentially tried using the network only if it had an IP address associated to it (which many constraints might prevent from happening).

    Of course, if updating to 1.3.0 - RC doesn’t work for you, it doesn’t mean you cannot use 1.3.0 and it’s benefits, and will give us (the FOG team) a potential towards gaining more support for your particular systems (among others that may acquire these systems as well).



  • Hy

    Yes I access the PXE boot menu and here are the screenshots of the FOG compatibility test

    0_1480498969491_IMG_3618.JPG 0_1480498989667_IMG_3617.JPG 0_1480499000010_IMG_3615.JPG 0_1480499007729_IMG_3618.JPG

    I have already tried the 4.8.x kernels with Fog 1.2.0 and the network card was powered. But the one that gave more conclusive results was the kernels “Kernel.TomElliott.4.7.1.64”

    I just checked in the bios and the hard drive type is PM951 NVMe SAMSUNG … Does this mean I have to switch to FOG 1.3.0?

    Thank you for your help.


    Bonjour

    Oui j’accède au PXE boot menu et voici les captures d’écran du FOG compatibility test

    0_1480498969491_IMG_3618.JPG 0_1480498989667_IMG_3617.JPG 0_1480499000010_IMG_3615.JPG 0_1480499007729_IMG_3618.JPG

    J’ai déjà essayé les kernels 4.8.x avec Fog 1.2.0 et la carte réseau était alimenté. Mais celui qui a donné des résultat plus concluant était le kernels “Kernel.TomElliott.4.7.1.64”

    Je viens de vérifier dans le bios et le type de disque dur est PM951 NVMe SAMSUNG … Cela veut dire que je suis obligé de passer sur FOG 1.3.0 ?

    Merci de votre aide.


  • Moderator

    There is a lot of details here, but I want to clarify.

    1. You can pxe boot into the fog menu, correct?
    2. When you run the FOG compatibility test, you get success for both the disk and network?

    As you noted, the i8042 error is not an error, just a warning. So not an issue here. I’m going to guess your network adapter is not supported by the FOS kernel of 4.1.2. We can try 4.8.x to see if that will work. But if your systems use uefi firmware, gpt disks or NVMe disks you will need to upgrade to FOG 1.3.0 to get that support.


Log in to reply
 

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.