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

    Microsoft Surface Pro 4

    Scheduled Pinned Locked Moved
    Hardware Compatibility
    4
    33
    11.7k
    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.
    • george1421G
      george1421 Moderator @mwarner
      last edited by

      @mwarner I got them from the following links.

      wget https://fogproject.org/inits/init.xz
      wget https://fogproject.org/inits/init_32.xz
      wget https://fogproject.org/kernels/bzImage
      wget https://fogproject.org/kernels/bzImage32
      

      Just make sure you save your current files before overwriting them

      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!

      mwarnerM 1 Reply Last reply Reply Quote 0
      • mwarnerM
        mwarner @george1421
        last edited by

        @george1421 Good news and bad news!

        I was able to get the DHCP working using the new inits/kernels. I was able to register the host and run the compatibility settings option just fine.

        Unfortunately, I was not able to run a capture task. Below is an image of the result.

        0_1513884609130_error.jpg

        I have no clue what could be going on, should I run another tcpdump?

        I should also add that there is a substantially long pause between where it says “OK” and where the error starts - I’d say maybe 30-60 seconds.

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

          @mwarner One question, are you booting via the USB stick? If so, you MUST schedule a task on the FOG server before you attempt to boot with usb stick. While the error is a bit cryptic, that is the typically the error.

          If you ARE booting via the usb stick, why? I was able to pxe boot the surface book and capture without issue.

          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!

          mwarnerM 1 Reply Last reply Reply Quote 0
          • mwarnerM
            mwarner @george1421
            last edited by

            @george1421 I am booting via USB stick. I tried PXE and it didn’t seem to work - same errors as before. I created the task before booting.

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

              @mwarner And so it works now?

              The error message basically translates to I tried to deploy an image but there wasn’t anything for me to do (i.e. request type: null [nothing to do]). Same error as before as in your are still deploying the old bzImage from your fog server?

              [Edit] Oh I see you updated to fog 1.5.0RC10 a few posts ago. So you should have the latest kernel on your fog server. There may be an issue with the usb boot and fog 1.5.0. I have to look at it, but the developers change (in 1.5.0 to add the ability to deal with http and https installs of fog). That maybe why its returning an invalid null type.

              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!

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

                Looking at the code in the grub.cfg file, lets try to update it as such.

                change

                <snip> ramdisk_size=127000 keymap= web=$myfogip/fog/ boottype=usb
                

                to

                <snip>ramdisk_size=127000 keymap= web=http://$myfogip/fog/ boottype=usb
                

                Note the http:// inserted just before $myfogip. You need to do that for every row that has web=$myfogip/fog/ in it.

                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!

                mwarnerM 1 Reply Last reply Reply Quote 0
                • mwarnerM
                  mwarner @george1421
                  last edited by

                  @george1421 Yes, the DHCP works now when I use the USB stick. I’d still prefer to go without it, but it can suffice for now.

                  What do you recommend the next step should be for me? Should I wait for the next stable version of FOG to be released? In the meantime, should I go back to bzImage 4.13.4?

                  1 Reply Last reply Reply Quote 0
                  • mwarnerM
                    mwarner @george1421
                    last edited by

                    @george1421 where should this grub.cfg file be located?

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

                      @mwarner Grub.cfg is on the usb stick. Its in the boot/grub/grub.cfg path.

                      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!

                      mwarnerM 1 Reply Last reply Reply Quote 0
                      • mwarnerM
                        mwarner @george1421
                        last edited by

                        @george1421 Unfortunately that didn’t seem to fix anything. Should I revert my kernel back to 4.13.4?

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

                          @mwarner You can or leave it at 4.13.6 since that has proven to work with the surface devices. When 1.5.0 stable is eventually released it will contain that or a later kernel anyway.

                          I guess I need to look into why 1.5.0RC10 is giving us an issue with USB booting.

                          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!

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

                          143

                          Online

                          12.0k

                          Users

                          17.3k

                          Topics

                          155.2k

                          Posts
                          Copyright © 2012-2024 FOG Project