Any thoughts or ideas yet? I am completely at a loss. Once again, I updated versions to see if that would fix. No go.
Posts made by Scott Adams
-
RE: Surface Pro 4 unable to image
-
RE: Surface Pro 4 unable to image
@Tom-Elliott This is the same issue I reported on a few weeks ago.
https://forums.fogproject.org/topic/7276/after-upgrade-to-trunk-7324-no-settings-available-under-fog-configuration-fog-settings -
RE: Surface Pro 4 unable to image
@Tom-Elliott I did. I then received the attached errors when I approved.
I have since logged in and am able to navigate the webui. However, I am still unable to save any changes within FOGSettings.When I re-run the show create table fog.globalSettings, all settings look the same, only the AUTO_INCREMENT has changed to 188
-
RE: Surface Pro 4 unable to image
@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.
-
RE: Surface Pro 4 unable to image
@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.
-
RE: Surface Pro 4 unable to image
@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.
-
RE: Surface Pro 4 unable to image
@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.
-
RE: Surface Pro 4 unable to image
@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.
-
RE: Surface Pro 4 unable to image
@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.
-
RE: Surface Pro 4 unable to image
@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.
-
RE: Surface Pro 4 unable to image
@fry_p Thanks for the response. I would just hate to have to buy yet something else in order to get the functionality back. Imaging functionality did work many trunks ago (can’t remember the version we were on when we originally imaged, but I did create a thread on that as well back then).
-
RE: Surface Pro 4 unable to image
Ok. So, checking BIOS on “new” Surface Pro 4, there is no option for USB Legacy models or anything like that. I have turned off Secure Boot and TPM as we have done previously.
I have also updated to 7543.
Now, I can’t even get to the screen in my original post. It just goes to a black screen.
Now, after I select Quick Image and put in my username/password, the following screen shows up before going to the image selection screen.
It only sits on thet screen for just a second or two, but this was not there before the update to 7543.
-
RE: Surface Pro 4 unable to image
I obviously added the photo in the wrong place.
Th last sentence should be, “The keyboard works as I can use it in the PXE menu.”
-
Surface Pro 4 unable to image
Running Ubuntu 14.04, on trunk 7386.
Was able to image Surface Pro 3s and 4s on an older trunk version. Just got in a new Pro 4, tried to image and am unable to do so. I have manually created the host (we are using the certified Surface usb ethernet adapters which worked previously). Added the has_usb_nic=1 paramater to the host kernel arguments. Changed boot file to a variety of different ones (snp.efi, snponly.efi, and ipxe.efi). Can get to the PXE menu, select Quick Image, and I get the attached screenshot.
The keyboard become unresponsive. I’ve unplugged nic as stated and press Enter…nothing. Left USB nic plugged in, pressed Enter…nothing.
The keyboard works as I can use it in the PXE menu.
Ideas?
-
RE: Invalid host certificate
I am experiencing this as well, running trunk 7346. Did updating to a newer trunk fix it for you?
-
RE: After upgrade to trunk 7324, no settings available under FOG Configuration - FOG Settings
@Tom-Elliott The upgrade to 7330 gives me all the options again under FOG Settings. YAY!
However, I am still having the issue where I cannot update any of the settings under FOG Settings using the Web UI. I can change other items with FOG Configuration (iPXE config, iPxe menu, etc). Just nothing under FOG Settings. In particular, I am trying to change the kernel I am using under the TFTP Server section. I make the changes, click save. I get the notification that the changes were stored successfully. However, none of the changes actually get made. Any thoughts?
-
After upgrade to trunk 7324, no settings available under FOG Configuration - FOG Settings
I was having an issue with trunk 7320 where I could not change the kernel under TFTP Server in FOG Settings. I would change it and hit Save. It would say that settings were store successfully, but the kernel name never changed. In fact, any change I made to anything under FOG Settings did not change.
So, I upgraded to trunk 7324 and now I have no settings, with the exception of Active Directory. I have rebooted several times, restarted mysql service and apache2, but to no avail.
Any ideas?
I am on ubuntu 14.04