• 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
    46.0k
    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.
    • JunkhackerJ
      Junkhacker Developer
      last edited by

      then try the version in the svn trunk, they’ve been updated since 1.2.0 came out

      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
      • E
        Excel Group
        last edited by

        [quote=“Tom Elliott, post: 30923, member: 7271”]It sounds like you’re doing it “right” persay, but doing a lot of extra work.

        Really, you can “cheatify it” as such.

        No need to stop tftp-hpa or tftpd-hpa or isc-dhcp-server
        Doing the first few steps just as you did:
        [code]mv /tftpboot /tftpboot.bak
        mkdir /tftpboot
        cd /tftpboot
        wget -r ftp https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/*
        [/code]

        Then move the undionly.kpxe file to undionly.kpxe_MAIN
        [code]mv /tftpboot/undionly.kpxe /tftpboot/undionly.kpxe_MAIN[/code]

        Then just create symbolic links to undionly.kpxe from the file you want to try out. For example:
        [code]ln -s /tftpboot/undionly.kkpxe /tftpboot/undionly.kpxe[/code]

        You don’t have to keep rebooting services to test it. When you’re ready to try another file you simply:
        [code]rm /tftpboot/undionly.kpxe; ln -s /tftpboot/<NEWFILETOTEST> /tftpboot/undionly.kpxe[/code][/quote]
        When I try this im getting error 404 not found on the wget stage

        1 Reply Last reply Reply Quote 0
        • JunkhackerJ
          Junkhacker Developer
          last edited by

          i’m guessing it’s the https:// try http://

          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
          • E
            Excel Group
            last edited by

            Nope did exactly the same, I can click on the link no issue and it comes up in firefox

            1 Reply Last reply Reply Quote 0
            • D
              drjam
              last edited by

              [quote=“Excel Group, post: 35168, member: 18178”]Nope [/quote]

              Damn. I have just tried a different motherboard using realtec NIC hardware…FFS it wont even SEE the fog server now.
              Is there a way to simply:
              [LIST=1]
              []download the hardware vendor driver (what driver would that be??)
              [
              ]inject that driver into Fog somewhere (where?)
              [/LIST]

              if not, i need to do my work-around that works for the new Fog:

              put the new hard drive into an OLD pc.
              fog that hdd.
              put that HDD into the new pc i WANT to work.
              run

              Seems a bit painful but it works at least lol.

              1 Reply Last reply Reply Quote 0
              • D
                drjam
                last edited by

                whoa whoa whoa!!!
                The latest issues was a gigabit cable not being compatible with our network…carry on citizens!
                (but initial problem stands lol)

                1 Reply Last reply Reply Quote 0
                • JunkhackerJ
                  Junkhacker Developer
                  last edited by

                  [quote=“Excel Group, post: 35168, member: 18178”]Nope did exactly the same, I can click on the link no issue and it comes up in firefox[/quote]

                  then download it with firefox and upload it to the server. sorry if the instructions i gave were inaccurate, but i just copied/pasted them from another thread on the forum.

                  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
                  • E
                    eroneree
                    last edited by

                    @junkhacker This was exactly my issue. All I had to do was boot the offending laptops into Windows, shut down, and reboot. The “Initialising devices” hang was gone. My thanks, more than 3 years after the original post!

                    george1421G 1 Reply Last reply Reply Quote 0
                    • george1421G
                      george1421 Moderator @eroneree
                      last edited by

                      @eroneree What version of fog are you running? I understand the mechanics behind why that worked, but 3 years later those (pita) Realtek nics should be working correctly.

                      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!

                      E 1 Reply Last reply Reply Quote 0
                      • E
                        eroneree @george1421
                        last edited by

                        @george1421 Running Fog 1.4.4. They mostly work correctly but once in a while I get the “Initialising devices” hang.

                        1 Reply Last reply Reply Quote 1
                        • P
                          philippe.willems
                          last edited by

                          I have the same issue on the Realtek 8168. But this is all under hyper-v. On my old pc, with intel NIC, everything worked fine, but now on my new PC with the Realtek 8168 I am running FOG as a virtual machine and a PXE client on. All on hyper-v. It looks like hyper-v inherits the properties of the host system, even with private networks. When using EFI it all works, just not on a legacy NIC.

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

                          192

                          Online

                          12.0k

                          Users

                          17.3k

                          Topics

                          155.2k

                          Posts
                          Copyright © 2012-2024 FOG Project