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

Realtek 8111\8168 & undionly.kpxe -> hangs on Initialising Devices...

Scheduled Pinned Locked Moved
Hardware Compatibility
14
69
45.3k
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.
  • A
    Andy Abplanalp Developer
    last edited by May 10, 2014, 3:42 AM

    I haven’t seen any other forum posts on this exact issue but I don’t like what I read when I Google it. Has anyone used a different file/method to get this NIC successfully working in 1.0.0? It’s hard to believe that there isn’t a solution for this…the Realtek GbE family has a pretty pervasive presence to my knowledge.

    Thanks!

    1 Reply Last reply Reply Quote 0
    • T
      Tom Elliott
      last edited by May 10, 2014, 1:05 PM

      TO my knowledge, this driver does already exist within the kernel. I don’t know of any issues with this device and undionly.kpxe though. How does it hang? Everytime you start the dive, or everytime the device is restarted? By start, I mean from a powered off state, where restart is still powered the ntire time.

      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

      1 Reply Last reply Reply Quote 0
      • A
        Andy Abplanalp Developer
        last edited by May 10, 2014, 5:25 PM

        Tom,

        Thanks much for the reply.

        FOG 1.0.0 (I believe revision 1650), Ubuntu 13.10 server

        I have checked the wiki and forums and don’t see my exact issue anywhere. Updating the kernel seems one step ahead as the kernel never loads. It hangs and doesn’t reboot. Same behavior whether I restart or start cold. Picture attached.

        Here’s what I see in apache error log today repeatedly (not much help IMO):
        PHP Warning: date_default_timezone_get(): It is not safe to rely on the system’s timezone settings. You are required to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone ‘UTC’ for now, but please set date.timezone to select your timezone. in /var/www/fog/commons/system.php on line 11, referer: [url]http://10.0.0.51/fog/management/index.php?node=home[/url]

        Andy[ATTACH=full]725[/ATTACH]

        [url=“/_imported_xf_attachments/0/725_realtekhangs.jpg?:”]realtekhangs.jpg[/url]

        1 Reply Last reply Reply Quote 0
        • A
          Andy Abplanalp Developer
          last edited by May 11, 2014, 2:39 AM

          I apologize - this was a different undionly.kpxe file in the picture. BUT my results were exactly the same for iPXE.

          1 Reply Last reply Reply Quote 0
          • A
            Andy Abplanalp Developer
            last edited by May 11, 2014, 4:19 AM

            Tom,

            I recompiled a new undionly.kpxe using this site: rom-o-matic.eu and with help from these forums on chainloading default.ipxe, I was able to upload an image into FOG 1.0.0.

            Is there a way to remove (or reduce) the 60 second wait time on the “i2c-parport-light adapter type unspecified” message before the kernel is finally loaded?

            Embedded script:#!ipxe
            dhcp
            chain default.ipxe

            Thanks again,

            Andy

            1 Reply Last reply Reply Quote 0
            • T
              Tom Elliott
              last edited by May 11, 2014, 4:41 AM

              Again, I’m not aware of anything wrong with the undionly.kpxe file. The kernel however is a different beast. The kernel is simply trying to load the drivers. The only way to remove something is to remove the related item from the kernel in its entirety. This i2c-parport-light adapter isn’t necessarily the thing taking a period of time but rather the last message you see while the rest of the drivers are loading.

              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

              1 Reply Last reply Reply Quote 0
              • A
                Andy Abplanalp Developer
                last edited by May 12, 2014, 12:37 PM

                Just to add some more notes to the thread - my test machines include a Biostar A880GB+ motherboard with the Realtek NIC I referenced earlier. The other is an Asus laptop - a K60IJ with an Atheros AR8121/AR8113/AR8114 pci-e NIC along with an Atheros wireless card. Again, the “stock” FOG undionly.kpxe file didn’t work with the AR8121. I got a “insert boot media” error.

                I decided to try using the undionly.kpxe file that I compiled for the Realtek NIC. Full host registration seemed to go fine but if I told FOG to image the computer upon reboot, undionly.kpxe would see the wireless NIC (identified as net0) and bypass that with an error. It would then identify the AR8121 (as net1) and boot into the FOG menu with a “Not a registered host” error. On a hunch, I yanked the wireless card and then imaging could take place properly if the AR8121 was identified as net0. I’m sure what this all means yet, but I wanted to note my experience.

                These two hosts worked fine in 0.32 from start to finish, including snapins & multicasting.

                Andy

                1 Reply Last reply Reply Quote 0
                • A
                  Andy Abplanalp Developer
                  last edited by May 12, 2014, 7:52 PM

                  I’m trying to get more familiar with iPXE. Am I OK to assume that I can (attempt to) build an all-drivers ipxe.kpxe file and use it with FOG as long as the script to chainload to default.ipxe happens? I’m trying to figure out why undionly.kpxe is being used by default in FOG. Thanks for any feedback.

                  Andy

                  1 Reply Last reply Reply Quote 0
                  • J
                    Junkhacker Developer
                    last edited by May 12, 2014, 8:20 PM

                    undionly.kpxe is used by fog because it is compatible with more network cards. .pxe versions dump the UNDI and require recompiling with additional drivers to support new cards

                    signature:
                    Junkhacker
                    We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

                    1 Reply Last reply Reply Quote 0
                    • A
                      Andy Abplanalp Developer
                      last edited by May 13, 2014, 10:49 PM

                      This dirty hack in my default.ipxe file seemed to do the trick:

                      #!ipxe
                      cpuid --ext 29 && set arch x86_64 || set arch i386
                      isset ${net1/mac} && chain [url]http://10.0.0.50/fog/service/ipxe/boot.php?mac=${net1/mac}[/url] ||
                      params
                      param mac ${net0/mac}
                      param arch ${arch}
                      chain [url]http://10.0.0.50/fog/service/ipxe/boot.php##params[/url]

                      1 Reply Last reply Reply Quote 0
                      • T
                        Tom Elliott
                        last edited by May 13, 2014, 11:30 PM

                        Why are you sending net1 instead of net0, are you booting from another nic, or is ipxe booting from another nic?

                        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

                        1 Reply Last reply Reply Quote 0
                        • A
                          Andy Abplanalp Developer
                          last edited by May 14, 2014, 2:10 AM

                          ipxe.kpxe (and undionly.kpxe for that matter) is identifying the wireless NIC as net0. I had to get to net1 somehow.

                          1 Reply Last reply Reply Quote 0
                          • J
                            Junkhacker Developer
                            last edited by May 15, 2014, 2:35 AM

                            fyi, you can associate more then one MAC address with a host.
                            add additional MACs to a host on the host management page for that host.

                            signature:
                            Junkhacker
                            We are here to help you. If you are unresponsive to our questions, don't expect us to be responsive to yours.

                            1 Reply Last reply Reply Quote 0
                            • A
                              Andy Abplanalp Developer
                              last edited by May 15, 2014, 3:21 AM

                              Thanks. All these years using FOG and I’d completely forgotten about that feature.

                              1 Reply Last reply Reply Quote 0
                              • B
                                Baite
                                last edited by May 27, 2014, 2:50 PM

                                [quote=“tamatech, post: 26861, member: 24111”]Tom,

                                I recompiled a new undionly.kpxe using this site: rom-o-matic.eu and with help from these forums on chainloading default.ipxe, I was able to upload an image into FOG 1.0.0.

                                Is there a way to remove (or reduce) the 60 second wait time on the “i2c-parport-light adapter type unspecified” message before the kernel is finally loaded?

                                Embedded script:#!ipxe
                                dhcp
                                chain default.ipxe

                                Thanks again,

                                Andy[/quote]
                                Tamatech:

                                Could you please be gentle enough to show how you did it (or share your working undionly.pxe)?

                                1 Reply Last reply Reply Quote 0
                                • A
                                  Andy Abplanalp Developer
                                  last edited by May 28, 2014, 5:50 PM

                                  Baite:

                                  Here’s my ipxe.kpxe.

                                  Andy

                                  [url=“/_imported_xf_attachments/0/843_ipxe.zip?:”]ipxe.zip[/url]

                                  1 Reply Last reply Reply Quote 0
                                  • T
                                    Tom Elliott
                                    last edited by May 28, 2014, 5:54 PM

                                    [quote=“Baite, post: 28277, member: 24308”]Tamatech:

                                    Could you please be gentle enough to show how you did it (or share your working undionly.pxe)?[/quote]

                                    You can also use any of the ipxe.*pxe files in trunk and this should work for you as well as it’s basically the same.

                                    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

                                    1 Reply Last reply Reply Quote 0
                                    • B
                                      Baite
                                      last edited by May 30, 2014, 12:00 PM

                                      [quote=“tamatech, post: 28445, member: 24111”]Baite:

                                      Here’s my ipxe.kpxe.

                                      Andy[/quote]
                                      Thank you, Tamatech

                                      1 Reply Last reply Reply Quote 0
                                      • B
                                        Baite
                                        last edited by May 30, 2014, 12:00 PM

                                        [quote=“Tom Elliott, post: 28446, member: 7271”]You can also use any of the ipxe.*pxe files in trunk and this should work for you as well as it’s basically the same.[/quote]
                                        Thank you, Tom.

                                        1 Reply Last reply Reply Quote 0
                                        • B
                                          Baite
                                          last edited by May 30, 2014, 3:37 PM

                                          [quote=“Tom Elliott, post: 28446, member: 7271”]You can also use any of the ipxe.*pxe files in trunk and this should work for you as well as it’s basically the same.[/quote]
                                          For me to use any of those files, I just need to replace the undionly.kpxe file with that one, right?

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

                                          219

                                          Online

                                          12.0k

                                          Users

                                          17.3k

                                          Topics

                                          155.2k

                                          Posts
                                          Copyright © 2012-2024 FOG Project