Surface Pro 4 unable to image
-
Similar thread: https://forums.fogproject.org/topic/6515/surface-pro-4-won-t-get-to-registration-menu/157
If I remember right the solution was to use an external usb ethernet adapter and/or the surface docking station. But I find it strange that the older surface pro 4s worked, and the new one doesn’t. I guess the question is did FOG change so that the older surface pro 4 now no longer image or did the firmware get changed on the new surface pro 4 and that has caused imaging to fail.
-
Not hijacking, hope to be adding too.
Using snponly.efi & Surface Pro4 + pro4 docking station for LAN -
@ITCC Does the keyboard not work, or you’re just noticing it can’t detect an uplink/ip address on that particular NIC?
-
keyboard works.
I have gone through the fog login and selected something from the menu. (using keyboard to nav)
it’s when it drops out to complete the task, this comes up. -
just updated to SVN 7561 and now there is no output at this time.
I have set an upload job from the GUI and it gets to the
init.xz…OK -
@ITCC That is where I am at as well. Updated yesterday to SVN 7543. Seems to load the bzImage and init.xz, and then it just hangs. I am using the Microsoft Surface Ethernet USB adapter and have tried multiple .efi boot files. I’m going to try to get my hands on one our prior Surface Pro 4s and see what happens with it.
-
@Scott-Adams and @ITCC Can you both please crank up the log level and enable kernel debug messages (FOG Configuration -> FOG Settings -> expand all and search for ‘DEBUG’ or ‘LOG’)? Hope we can get some more output.
-
These are both USB Nics, but my question about keyboard working is if it works in the FOS environment.
These units, most assuredly, need the kernel arguments with
has_usb_nic=1until we can figure out a proper fix. -
@Sebastian-Roth I have set the kernel debug and have tried to start another task. Now, where do I get the logs that will help you? I’ve looked under log viewer in FOG configuration, but am not seeing anything specific for this job.
-
@Tom-Elliott I manually entered the host and added the has_usb_nic=1 argument. That will indeed get rid of the DHCP error that @ITCC was getting. My original issue of the image not attempting to start is still present. I have set the kernel debug check mark under FOG Configuration and trying to get some logs to help, but am not seeing anything specific to this particular task under Log Viewer in the WebUI.
-
@Tom-Elliott I should also add that I had the argument there from the beginning, as this was the fix the last time I had a thread on the surface (about 3 months ago). I have also set this host to use the kernel we were using at the time to see if that would help, and it did not.
-
@Scott-Adams The KERNEL_DEBUG and CONSOLE LOG LEVEL stuff will only impact the information printed on the client machine. There will be NO logs as we don’t store that information on the server. First it would BOG the server down especially when dealing with many tasks. Second, it would be quite difficult to filter out which log to actually look at.
If you up the levels and enable the DEBUG option, the simplest method to get us info is to take a picture and upload that here.
-
@Tom-Elliott Ok. So, apparantly my changes are not being saved in the FOG Configuration > FOG Boot Settings. I select FOG_KERNEL_DEBUG and up my FOG_KERNEL_LOGLEVEL to 7, click Save Changes. It says that the settings were saved, but then I notice the check is not checked and the log level is still set to 4.
-
-
@Scott-Adams What version of MySQL are you running? (5.7?)?
-
@Tom-Elliott 5.5.49-0ubuntu0.14.04.1
-
@Tom-Elliott Do I need to update? Are there credentials for mysql stored in the WEBui somewhere that I need to check?
If I log into mysql on my FOG server, I can manually edit tables and contents. Just can’t do it from the WebUI.
-
@Scott-Adams Can you get the output of mysql command:
show create table fog.globalSettings -
-
@Tom-Elliott I have also checked .fogsettings, config.class.php and sql username/passwords match. I also tested the storage node mysql username/password (following the troubleshooting mysql wiki) and credentials worked. It is just something with the WebUI itself or how the WebUI communicates to the mysql database.
