• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    HP 405 G6 deploy error

    Scheduled Pinned Locked Moved
    FOG Problems
    3
    23
    2.8k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      Sebastian Roth Moderator
      last edited by Sebastian Roth

      @Zaqen Please get us the PCI IDs of this network chip! Take a look at the details in Windows device manager or using lspci -nn | grep -i net on a Linux command shell on this machine (e.g. FOS debug session).

      Update: Looks like there is a NIC that is only supported in Linux kernel version 5.15 and newer so far: 10ec:8162 (see https://cateee.net/lkddb/web-lkddb/R8169.html)

      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

      Z 3 Replies Last reply Reply Quote 0
      • george1421G
        george1421 Moderator @Zaqen
        last edited by

        @zaqen said in HP 405 G6 deploy error:

        Hp 405 G6

        Yes I would like to see the hardware IDs of that system either via windows device manager in the form of vend and device ID or from the linux side as Sebastian mentioned.

        As near as I can guess that system was released in Sept 2020. So its been out over a year. I would think the linux kernel would have the driver for this nic. I might think maybe missing firmware. If you go the linux route, once you get the hardware ID stay in the debug mode because we may have you look in syslog for the word firmware.

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

        Z 1 Reply Last reply Reply Quote 0
        • Z
          Zaqen
          last edited by

          hi Sebastian,

          lspci -nn | grep -i net result is :

          08:00.1 Ethernet controller [0200]: Realtek Semicondutor co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ehternet Controller [10ec:8168] (rev 29)

          Cheers

          1 Reply Last reply Reply Quote 0
          • Z
            Zaqen @Sebastian Roth
            last edited by Sebastian Roth

            @sebastian-roth

            Last log to test deploy, file is /var/log/messages

            Nov 29 15:15:14 POMPELUP xinetd[1916]: xinetd Version 2.3.14 started with libwrap loadavg labeled-networking options compiled in.
Nov 29 15:15:14 POMPELUP xinetd[1916]: Started working: 1 available service
Nov 29 15:16:56 POMPELUP xinetd[1916]: START: tftp pid=3591 from=70.45.181.194
Nov 29 15:16:56 POMPELUP in.tftpd[3592]: tftp: client does not accept options
Nov 29 15:16:56 POMPELUP in.tftpd[3593]: Client 70.45.181.194 finished ipxe.efi
Nov 29 15:17:04 POMPELUP in.tftpd[3635]: Client 70.45.181.194 finished default.ipxe
Nov 29 15:18:51 POMPELUP in.tftpd[4528]: tftp: client does not accept options
Nov 29 15:18:51 POMPELUP in.tftpd[4529]: Client 70.45.181.194 finished ipxe.efi
Nov 29 15:19:00 POMPELUP in.tftpd[4612]: Client 70.45.181.194 finished default.ipxe
Nov 29 15:24:40 POMPELUP in.tftpd[7306]: tftp: client does not accept options
Nov 29 15:24:41 POMPELUP in.tftpd[7307]: Client 70.45.181.194 finished ipxe.efi
Nov 29 15:24:49 POMPELUP in.tftpd[7359]: Client 70.45.181.194 finished default.ipxe
Nov 29 15:27:33 POMPELUP in.tftpd[8710]: tftp: client does not accept options
Nov 29 15:27:33 POMPELUP in.tftpd[8711]: Client 70.45.181.221 finished ipxe.efi
Nov 29 15:27:34 POMPELUP in.tftpd[8714]: tftp: client does not accept options
Nov 29 15:27:34 POMPELUP in.tftpd[8715]: Client 70.45.181.220 finished ipxe.efi
Nov 29 15:27:35 POMPELUP in.tftpd[8723]: tftp: client does not accept options
Nov 29 15:27:35 POMPELUP in.tftpd[8724]: Client 70.45.181.224 finished ipxe.efi
Nov 29 15:27:36 POMPELUP in.tftpd[8737]: tftp: client does not accept options
Nov 29 15:27:36 POMPELUP in.tftpd[8738]: Client 70.45.181.222 finished ipxe.efi
Nov 29 15:27:36 POMPELUP in.tftpd[8742]: tftp: client does not accept options
Nov 29 15:27:37 POMPELUP in.tftpd[8743]: Client 70.45.181.226 finished ipxe.efi
Nov 29 15:27:37 POMPELUP in.tftpd[8750]: tftp: client does not accept options
Nov 29 15:27:38 POMPELUP in.tftpd[8751]: Client 70.45.181.223 finished ipxe.efi
Nov 29 15:27:38 POMPELUP in.tftpd[8754]: tftp: client does not accept options
Nov 29 15:27:38 POMPELUP in.tftpd[8755]: Client 70.45.181.225 finished ipxe.efi
Nov 29 15:27:39 POMPELUP in.tftpd[8760]: tftp: client does not accept options
Nov 29 15:27:39 POMPELUP in.tftpd[8761]: Client 70.45.181.228 finished ipxe.efi
Nov 29 15:27:41 POMPELUP in.tftpd[8770]: tftp: client does not accept options
Nov 29 15:27:41 POMPELUP in.tftpd[8771]: Client 70.45.181.230 finished ipxe.efi
Nov 29 15:27:41 POMPELUP in.tftpd[8776]: tftp: client does not accept options
Nov 29 15:27:41 POMPELUP in.tftpd[8777]: Client 70.45.181.229 finished ipxe.efi
Nov 29 15:27:42 POMPELUP in.tftpd[8781]: Client 70.45.181.221 finished default.ipxe
Nov 29 15:27:42 POMPELUP in.tftpd[8785]: tftp: client does not accept options
Nov 29 15:27:42 POMPELUP in.tftpd[8786]: Client 70.45.181.227 finished ipxe.efi
Nov 29 15:27:43 POMPELUP in.tftpd[8789]: Client 70.45.181.220 finished default.ipxe
Nov 29 15:27:44 POMPELUP in.tftpd[8797]: Client 70.45.181.224 finished default.ipxe
Nov 29 15:27:44 POMPELUP in.tftpd[8805]: Client 70.45.181.222 finished default.ipxe
Nov 29 15:27:44 POMPELUP in.tftpd[8807]: tftp: client does not accept options
Nov 29 15:27:45 POMPELUP in.tftpd[8808]: Client 70.45.181.242 finished ipxe.efi
Nov 29 15:27:45 POMPELUP in.tftpd[8821]: Client 70.45.181.226 finished default.ipxe
Nov 29 15:27:46 POMPELUP in.tftpd[8835]: Client 70.45.181.223 finished default.ipxe
Nov 29 15:27:47 POMPELUP in.tftpd[8837]: Client 70.45.181.225 finished default.ipxe
Nov 29 15:27:47 POMPELUP in.tftpd[8841]: tftp: client does not accept options
Nov 29 15:27:47 POMPELUP in.tftpd[8842]: Client 70.45.181.241 finished ipxe.efi
Nov 29 15:27:47 POMPELUP in.tftpd[8844]: tftp: client does not accept options
Nov 29 15:27:48 POMPELUP in.tftpd[8845]: Client 70.45.181.238 finished ipxe.efi
Nov 29 15:27:48 POMPELUP in.tftpd[8848]: Client 70.45.181.228 finished default.ipxe
Nov 29 15:27:48 POMPELUP in.tftpd[8853]: tftp: client does not accept options
Nov 29 15:27:49 POMPELUP in.tftpd[8854]: Client 70.45.181.240 finished ipxe.efi
Nov 29 15:27:49 POMPELUP in.tftpd[8856]: tftp: client does not accept options
Nov 29 15:27:49 POMPELUP in.tftpd[8857]: Client 70.45.181.239 finished ipxe.efi
Nov 29 15:27:49 POMPELUP in.tftpd[8859]: tftp: client does not accept options
Nov 29 15:27:49 POMPELUP in.tftpd[8861]: Client 70.45.181.230 finished default.ipxe
Nov 29 15:27:50 POMPELUP in.tftpd[8860]: Client 70.45.181.236 finished ipxe.efi
Nov 29 15:27:50 POMPELUP in.tftpd[8866]: tftp: client does not accept options
Nov 29 15:27:50 POMPELUP in.tftpd[8869]: Client 70.45.181.229 finished default.ipxe
Nov 29 15:27:50 POMPELUP in.tftpd[8868]: Client 70.45.181.235 finished ipxe.efi
Nov 29 15:27:51 POMPELUP in.tftpd[8873]: Client 70.45.181.227 finished default.ipxe
Nov 29 15:27:53 POMPELUP in.tftpd[8883]: Client 70.45.181.242 finished default.ipxe
Nov 29 15:27:56 POMPELUP in.tftpd[8913]: Client 70.45.181.241 finished default.ipxe
Nov 29 15:27:56 POMPELUP in.tftpd[8917]: Client 70.45.181.238 finished default.ipxe
Nov 29 15:27:57 POMPELUP in.tftpd[8930]: Client 70.45.181.240 finished default.ipxe
Nov 29 15:27:58 POMPELUP in.tftpd[8936]: Client 70.45.181.239 finished default.ipxe
Nov 29 15:27:58 POMPELUP in.tftpd[8939]: Client 70.45.181.236 finished default.ipxe
Nov 29 15:27:59 POMPELUP in.tftpd[8950]: Client 70.45.181.235 finished default.ipxe
Nov 29 15:30:18 POMPELUP in.tftpd[10013]: tftp: client does not accept options
Nov 29 15:30:18 POMPELUP in.tftpd[10014]: Client 70.45.181.194 finished ipxe.efi
Nov 29 15:30:27 POMPELUP in.tftpd[10102]: Client 70.45.181.194 finished default.ipxe
Nov 29 15:34:14 POMPELUP in.tftpd[12018]: tftp: client does not accept options
Nov 29 15:34:14 POMPELUP in.tftpd[12019]: Client 70.45.181.194 finished ipxe.efi
Nov 29 15:34:23 POMPELUP in.tftpd[12100]: Client 70.45.181.194 finished default.ipxe
Nov 29 15:49:23 POMPELUP xinetd[1916]: EXIT: tftp status=0 pid=3591 duration=1947(sec)
Nov 29 16:24:44 POMPELUP kernel: hrtimer: interrupt took 13192931 ns
            1 Reply Last reply Reply Quote 0
            • S
              Sebastian Roth Moderator
              last edited by

              @Zaqen Just ignore those messages you see with the tftp server. The “does no accept options” thing is not an issue and known (search the forums).

              08:00.1 Ethernet controller [0200]: Realtek Semicondutor co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ehternet Controller [10ec:8168] (rev 29)

              Ok I was wrong with my PCI ID guess. The NIC in this system isn’t that new really. I guess we’re just missing some firmware.

              I suppose you got the lspci output in a FOG debug session. Please boot up into it again and run the following command: dmesg | grep -i -e eth -e firmware (take a picture of the screen and post here)

              Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

              Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

              1 Reply Last reply Reply Quote 0
              • Z
                Zaqen
                last edited by

                @Sebastian-Roth

                Restart fog server and typing command :

                [root@POMPELUP ~]# dmesg | grep -i -e eth -e firmware
                [Firmware Bug]: No valid trip found
                eth0: no IPv6 routers present
                [root@POMPELUP ~]#

                1 Reply Last reply Reply Quote 0
                • Z
                  Zaqen @Sebastian Roth
                  last edited by

                  @sebastian-roth

                  Firmware must be in /lib/firmware ? (same directory of all firmware product support ?)

                  1 Reply Last reply Reply Quote 0
                  • S
                    Sebastian Roth Moderator
                    last edited by

                    @zaqen said in HP 405 G6 deploy error:

                    Restart fog server

                    No, we don’t need that information from the FOG server but from the HP 405 G6!

                    Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                    Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                    Z 1 Reply Last reply Reply Quote 0
                    • Z
                      Zaqen @Sebastian Roth
                      last edited by

                      @sebastian-roth said in HP 405 G6 deploy error:

                      Update: Looks like there is a NIC that is only supported in Linux kernel version 5.15 and newer so far: 10ec:8162 (see https://cateee.net/lkddb/web-lkddb/R8169.html)

                      Last kernel available in web fog interface is 5.10.71

                      1 Reply Last reply Reply Quote 0
                      • Z
                        Zaqen @Sebastian Roth
                        last edited by Zaqen

                        @sebastian-roth said in HP 405 G6 deploy error:

                        No, we don’t need that information from the FOG server but from the HP 405 G6!

                        Ok but how i do this on HP 405 G6 ?

                        No system available because i can deploy it ! LOL !
                        I don’t understand

                        1 Reply Last reply Reply Quote 0
                        • Z
                          Zaqen @george1421
                          last edited by

                          @george1421

                          As near as I can guess that system was released in Sept 2020. So its been out over a year. I would think the linux kernel would have the driver for this nic. I might think maybe missing firmware. If you go the linux route, once you get the hardware ID stay in the debug mode because we may have you look in syslog for the word firmware.

                          Sorry don’t understand how to start debug mode on client .

                          1. i start client (after configure it on fog server to deploy it)
                          2. client start on pxe
                          3. and next black screen says :
                            r8169 0000:08:00.1 : unknown chip XID 54b
                            and 5 or 6 lines bellow error message is :
                            No netwok interfaces found, your kernel is most probally missing the correct drivers !

                          I ask you, what must i do ?

                          1 Reply Last reply Reply Quote 0
                          • S
                            Sebastian Roth Moderator
                            last edited by

                            @zaqen said in HP 405 G6 deploy error:

                            after configure it on fog server to deploy it

                            Just before you click the “Create Task” button in the FOG web UI there is a checkbox for debug. Use that and start the machine up as usual. Eventually that should bring you to a command shell on the machine despite the error.

                            If you can’t get to a Linux command shell this way you can use a Live Linux boot CD/DVD/ISO, e.g. Clonezilla and bootup the machine with that to get to a command shell.

                            Run both commands there and post information here (picture):

                            lspci -nn | grep -i net
dmesg | grep -i -e eth -e firmware

                            Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                            Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                            Z 3 Replies Last reply Reply Quote 0
                            • Z
                              Zaqen @Sebastian Roth
                              last edited by

                              @sebastian-roth

                              Ok but i ever do this.

                              Boot on Gparted usb key, open terminal and i put result on this post.

                              I try checkbox for debug today PM.

                              1 Reply Last reply Reply Quote 0
                              • Z
                                Zaqen @Sebastian Roth
                                last edited by

                                @sebastian-roth

                                Sorry it’s ok to dmesg | grep -i -e eth -e firmware command.

                                result is :

                                [ 0.681709] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
                                [ 1.332290] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
                                [ 4.025995] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
                                [ 4.026712] r8169 0000:08:00.1 eth0: RTL8168b/8111b at 0xffffb24600cb1000, 48:9e:bd:4a:81:08, XID 14b00880 IRQ 39
                                [ 4.026714] r8169 0000:08:00.1 eth0: jumbo features [frames: 4080 bytes, tx checksumming: ko]
                                [ 7.095506] Atheros® L2 Ethernet Driver - version 2.2.3
                                [ 7.106510] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 1.712.30-0 (2014/02/10)

                                1 Reply Last reply Reply Quote 0
                                • Z
                                  Zaqen @Sebastian Roth
                                  last edited by

                                  @sebastian-roth

                                  Just before you click the “Create Task” button in the FOG web UI there is a checkbox for debug. Use that and start the machine up as usual. Eventually that should bring you to a command shell on the machine despite the error.
                                  lspci -nn | grep -i net
                                  dmesg | grep -i -e eth -e firmware

                                  Ok i do i take pictures :

                                  FOG1.jpg
                                  FOG2.jpg
                                  FOG3.jpg
                                  FOG4.jpg
                                  FOG5.jpg

                                  1 Reply Last reply Reply Quote 0
                                  • S
                                    Sebastian Roth Moderator
                                    last edited by

                                    @Zaqen said:

                                    Ok i do i take pictures :

                                    Well done! Unfortunately there is not much news to this.

                                    Doing a little more research I found this: https://forum.manjaro.org/t/linux-support-drivers-for-hp-prodesk-405-g6-amd-pro-565-chipset-renoir-ryzen-4750ge-realtek-rtl8111fph-cg/54260/4

                                    So I just compiled a 5.15.x kernel for you to see if that makes a difference: https://fogproject.org/kernels/bzImage-5.15.5 (64 bit kernel)

                                    Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                                    Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                                    Z 2 Replies Last reply Reply Quote 0
                                    • Z
                                      Zaqen @Sebastian Roth
                                      last edited by Zaqen

                                      @sebastian-roth

                                      yes not very lot of solution.

                                      Thank you very much to the kernel (but i prefered do it 😉

                                      i just copy it in /tftpboot/fog/kernel/ ?

                                      Thank’s a lot

                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        Sebastian Roth Moderator
                                        last edited by

                                        @zaqen said in HP 405 G6 deploy error:

                                        i just copy it in /tftpboot/fog/kernel/

                                        No that directory doesn’t exist as far as I know. Kernels on FOG servers go into /var/www/html/fog/service/ipxe/. I suggest you leave the filename including the version number so not ot overwrite the existing kernel. Then edit the host entry for one of your HP 405 G6 test machines and set Host Kernel to bzImage-5.15.5. Schedule a deploy task for this host and PXE boot into it.

                                        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                                        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                                        Z 1 Reply Last reply Reply Quote 0
                                        • Z
                                          Zaqen @Sebastian Roth
                                          last edited by

                                          @sebastian-roth

                                          Sebastian, I copied the kernel to the server and start testing this afternoon or tomorrow morning.
                                          I keep you informed.
                                          Regards

                                          1 Reply Last reply Reply Quote 0
                                          • Z
                                            Zaqen @Sebastian Roth
                                            last edited by

                                            @sebastian-roth
                                            Hello Sebastian
                                            I just did the test everything works fine with kernel 5-15.5.
                                            Is it possible to give the kernel name at group level?
                                            Thank you very much Sebastian

                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 1 / 2
                                            • First post
                                              Last post

                                            155

                                            Online

                                            12.0k

                                            Users

                                            17.3k

                                            Topics

                                            155.2k

                                            Posts
                                            Copyright © 2012-2024 FOG Project