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

    IPXE problems with Broadcom netXtreme II

    FOG Problems
    3
    14
    6.6k
    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.
    • E
      emkey
      last edited by

      Hey there,

      as I really like the fog software I am currently trying to use is for more and more types of different machine. And currently I am stuck with trying to get one machine to boot via iPXE. The Network Adapter is a Broadcom netXtreme II. I run fog 1.2.0 on CentOS 6.5.

      I tried several versions of the kpxe file but unfortunately without any success until now.

      With the original [B].kpxe[/B] file it seems to start but then I get this and it’s stuck:
      [CODE]Could not configure console: Input/output error (http://ipxe.org/1d8c2139)
      Could not boot: Input/output error (http://ipxe.org/1d8c2139)
      Could not boot: Input/output error (http://ipxe.org/1d8c2139)

      Broadcom UNDI PXE-2.1 v2.8.5
      Copyright © 2000-2006 Braodcom Corporation
      Copyright © 1997-2000 Intel Corporation
      All rights reserved.[/CODE]

      With the original [B].kkpxe[/B] file I get this and the server continues with the next boot devices:
      [CODE]Could not configure console: Input/output error (http://ipxe.org/1d8c2139)
      Could not boot: Input/output error (http://ipxe.org/1d8c2139)
      Could not boot: Input/output error (http://ipxe.org/1d8c2139)
      PXE-M0F: Exiting Broadcom PXE ROM.[/CODE]

      With the original .kpxe.INTEL i get this (the last line keeps repeating):
      [CODE]CLIENT MAC ADDR: XX XX XX XX XX XX GUID: XXXXXXXX XXXX XXXX XXXX XXXXXXXXXXXX
      CLIENT IP: 192.168.1.22 MASK: 255.255.255.0 DHCP IP: 192.168.1.1
      PXE->EB: !PXE at 9FA.0040, entry point at 95FA.00D6
      UNDI code segment 95FA::4964, data segment 982A.5D00 (576-619kB)
      UNDI device is PCI 06:00.0, type DIX+802.3
      576kB free base memory after PXE unload
      iPXE initialising devices…Ethernet addr: XX:XX:XX:XX:XX:XX
      Broadcom NetXtreme II (B2) PCI-X 64-bit 133MHz
      Valid link not established
      Ethernet addr: XX:XX:XX:XX:XX:XX
      Broadcom NetXtreme II (B2) PCI-X 64-bit 133MHz
      NIC Link is Up, 1000 Mbps full duplex, receive & transmit flow control ON
      WARNING: Using legacy NIC wrapper on XX:XX:XX:XX:XX:XX
      ok

      iPXE 1.0.0+ (e5878) – Open Source Network Boot Firmware – http://ipxe.org
      Features: NFS HTTP HTTPS iSCSI DNS TFTP AoE SRP bzImage ELF MBOOT PXE PXEXT Menu

      Configuring (net0 XX:XX:XX:XX:XX:XX)… ok
      /default.ipxe… ok
      http://192.168.1.1/fog/service/ipxe/boot.php… ok
      http://192.168.1.1/fog/service/ipxe/bg.png… transmit timed out
      transmit timed out
      transmit timed out
      …[/CODE]

      With the undionly.kpxe.INTEL from [URL=‘http://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/undionly.kpxe.INTEL’]this[/URL] link it’s just the same as the file included in the installed package.

      At last I built my own undionly.kpxe from the iPXE git repository, then I got this messages looping again and again:
      [CODE]CLIENT MAC ADDR: XX XX XX XX XX XX GUID: XXXXXXXX XXXX XXXX XXXX XXXXXXXXXXXX
      CLIENT IP: 192.168.1.22 MASK: 255.255.255.0 DHCP IP: 192.168.1.1
      PXE->EB: !PXE at 9FA.0040, entry point at 95FA.00D6
      UNDI code segment 95FA::4964, data segment 982A.5D00 (576-619kB)
      UNDI device is PCI 06:00.0, type DIX+802.3
      576kB free base memory after PXE unload
      iPXE initialising devices…ok

      iPXE 1.0.0+ (a48a) – Open Source Network Boot Firmware – http://ipxe.org
      Features: HTTP iSCSI DNS TFTP AoE bzImage ELF MBOOT PXE PXEXT Menu

      net0: XX:XX:XX:XX:XX:XX using undionly on UNDI-PCI06:00.0 (open)
      [Link:up, TX:0 TXE:0 RX:0 RXE:0]
      Configuring (net0 XX:XX:XX:XX:XX:XX)… ok
      net0: 192.168.1.21/255.255.255.0
      Next server: 192.168.1.1
      Filename: undionly.kpxe
      tftp://192.168.1.1/undionly.kpxe… ok
      …[/CODE]

      So this is the point I ran out of ideas. So can you help me out and point me to where I should look next?

      one-reply-to-this-post Last reply Reply Quote 0
      • Tom ElliottT
        Tom Elliott
        last edited by

        Weird as a request as this may be,

        Can you update to the latest svn? I’ve added components to change how things happen if the console picture part fails.

        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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

        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

        one-reply-to-this-post Last reply Reply Quote 0
        • E
          emkey
          last edited by

          I will do and try again on monday. I’m already on my weekend.

          one-reply-to-this-post Last reply Reply Quote 0
          • E
            emkey
            last edited by

            Okay, so I just tested build 2389 (current svn checkout).

            The good news is that it now boots to the fog menu without any problems.

            The bad news is that this is almost the only thing working.

            Problem 1: On the web interface I can only see hosts created BEFORE the upgrade to the current build. Newer hosts exist in the database and when I try to add them again I get told that they already exist, but I can’t see them.

            Problem 2: Quick Registration got stuck. The database entry still got created (at least the host entry, not sure about the rest).

            Problem 3: Although the host entry exists, it still says Host in NOT registered. Which is probably caused by…

            Problem 4: No network connectivity in FOG menu. In the IP settings there is no address attached to the network interface, therefore ping to the server fails of course.

            Compatibility check tells me I should be fine.

            Any more ideas at this stage? If i have some spare time I will try and do a fresh install instead of an upgrade.

            one-reply-to-this-post Last reply Reply Quote 0
            • Tom ElliottT
              Tom Elliott
              last edited by

              emkey,

              Do you have a gmail address you can share with me and BPSTravis in Convo?

              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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

              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

              one-reply-to-this-post Last reply Reply Quote 0
              • E
                emkey
                last edited by

                Yes, I will send you an address today.

                Meanwhile I tried a fresh installation and during the db schema installation I got the following error:
                [CODE]Update/Install Successful!

                Click here to login.

                The following errors occured
                Update ID: 130 - 5

                Database Error:

                No database selected
                Database SQL:

                INSERT INTO fog.hostMAC (hmMAC,hmHostID,hmPending) (SELECT pmAddress,pmHostID,‘1’ FROM pendingMACS)[/CODE]

                I think there is an error in the db setup script. Can you hint me where I can fidn it?

                one-reply-to-this-post Last reply Reply Quote 0
                • B
                  BPSTravis Developer
                  last edited by

                  If it’s a true fresh install there are no hosts to move so that won’t even matter.

                  [SIZE=12px]signature:[/SIZE]
                  [QUOTE]I think I know things, but I really don't. You shouldn't follow any advice I give. - BPSTravis[/QUOTE]

                  one-reply-to-this-post Last reply Reply Quote 0
                  • E
                    emkey
                    last edited by

                    Yes, it is. The only thing I reused is my datastore I mount as /images folder.

                    After installation again i can log in and everything looks quite fine. But again newly added hosts are not shown in the host list.

                    one-reply-to-this-post Last reply Reply Quote 0
                    • B
                      BPSTravis Developer
                      last edited by

                      Can you pull your /var/log/apache2/error.log? Are there any errors showing when viewing the hos list or searching for the newly added host? Better yet, is there an error when you create the new host(you can use tail-f /var/log/apache2/error.log to watch it real time.

                      Edit: I was able to duplicate this issue on my end, the issue is it’s inserting the mac record with no host id tied to it. We are looking into it and get back to you once we resolve it.

                      [SIZE=12px]signature:[/SIZE]
                      [QUOTE]I think I know things, but I really don't. You shouldn't follow any advice I give. - BPSTravis[/QUOTE]

                      one-reply-to-this-post Last reply Reply Quote 0
                      • B
                        BPSTravis Developer
                        last edited by

                        This is now fixed in svn 2391.

                        [SIZE=12px]signature:[/SIZE]
                        [QUOTE]I think I know things, but I really don't. You shouldn't follow any advice I give. - BPSTravis[/QUOTE]

                        one-reply-to-this-post Last reply Reply Quote 0
                        • E
                          emkey
                          last edited by

                          I will check the new version tomorrow morning, otherwise I will provide you the error log.

                          Also: PM with email. But maybe this might be interesting for other people, too.

                          one-reply-to-this-post Last reply Reply Quote 0
                          • E
                            emkey
                            last edited by

                            Okay, tried the new build. After not being able to add a host via pxe register or manually via the web interface I checked the database and the hostMAC field is missing on table hosts. As it is a fresh installation there still seems to be some faults in your database setup script.

                            Can you tell me where the script is located to check it for errors?

                            one-reply-to-this-post Last reply Reply Quote 0
                            • Tom ElliottT
                              Tom Elliott
                              last edited by

                              emkey,

                              We’re transitioning from multiple points of mac addresses to a single table.

                              That table is called hostMAC.

                              In that table you should notice that your MAC’s are associated by Primary MAC, Pending Mac’s and there’s a couple other fields.

                              There can only be one primary mac per host and it should have the relevant host’s id in the hmHostID field.

                              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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                              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

                              one-reply-to-this-post Last reply Reply Quote 0
                              • E
                                emkey
                                last edited by

                                Hey there,

                                sorry for letting you wait this long. Today I found some time to test a little bit and things look a lot better meanwhile.

                                I did another fresh install from the current svn and now the iPXE boot works without any flaws! I will now test to Up- and Download some images. I will keep you up to date!

                                one-reply-to-this-post Last reply Reply Quote 0
                                • 1 / 1
                                • First post
                                  Last post

                                148

                                Online

                                11.1k

                                Users

                                16.7k

                                Topics

                                152.5k

                                Posts
                                Copyright © 2012-2023 FOG Project