Posts made by sarge_212

@Sebastian-Roth Sorry! Yeah I can do that.

@sarge_212 Here is some video output of the pxe boot and kernel panic. Hope this helps!

https://www.youtube.com/watch?v=YvzswksAOUg

@Sebastian-Roth I’ve done the manual registration and pushed the bzImage_epk to the host with the kernel arguments and it did give a lot of text printing before the kernel panic. Video coming soon…

@Sebastian-Roth So I can manually register the host in the WebGUI with the MAC address? I will try that out.

@Tom-Elliott So I tried that, with the USB network-adapter, and it just added a device in the output of lsusb. Not sure where to go from here.

@Tom-Elliott
Correct, the surface pro 4 does not have an onboard nic. Let me compare output but I think the USB nic is plugged in when I ran this. I might be able to boot from the USB stick in the dock and with the 2.0 USB network adapter plugged in, would that be helpful?

@Tom-Elliott Here is the output from those 2 commands:

Let me know what else I can do, thanks!

@Tom-Elliott In which OS should I do this? Will I do this in the Flogger OS or in the ubuntu live image or where should I run this command?

I “wgot” the kernels and inits. I sha’d them to make sure they were okay and they both checked out. Chown’d them to fog:apache and the UEFI booted the surface. Here is what I have:

This second picture is a Optiplex 9020 on the new kernels and inits. It seems there is an issue when I try to go to the new kernels and inits with the stable FOG 1.2.0 and grab the undionly.kpxe. So in order to image the other machines we have in production(Optiplex 9020 and Latitude E7450, E7470) I drop back down to the other kernels. Thoughts?

@Sebastian-Roth I understand that I “may” have gone in circles. Thanks to @george1421 I’m documenting all the changes I’m doing from here on out so we don’t have that problem. I will do this now, thanks again for all your awesome suggestions and indications of where its going wrong, I really do appreciate it!!

Just playing with the Flogger os, and looking around at things. When I’m connected to the surface dock using the ethernet cable, I get this before the fog prompt:

r8152 2-2.2:1.0 eth0: v 1.08.2

I don’t know if that helps at all?

@Sebastian-Roth The other eth device some hours ago was the USB 2.0 usb-ethernet adapter I was using. This helped us some how in the testing but I can’t remember how. I did go back to an older kernel. Here is the current config:

Surface Dock (ethernet cable plugged into that)
Older kernel
USB booting of flogger os in usb port ON surface

I can test a variety of other configs, I can’t remember what we were doing yesterday with the ethernet-usb adapter though…

Okay. Here is something else. I have the ethernet cable in the surface dock. I put the ipxe usb boot only, eg only thing on flash drive is /efi/boot/bootx64.efi into the single usb port and booted. Was able to get to a registration menu. Keyboard didn’t work, but surface touch did. Arrowed down to perform full host registration and inventory and received the following:

This is using the kernel with FOG 1.2.0, I believe 3.19.8 but I can check that if needed.

So, I think part of the problem is the surface doesn’t have hard wire ethernet, be nice if it did. I’m using a surface dock. Here is what I’m seeing (using the ethernet adapter on the dock, because I can’t use the usb 2.0 network-ethernet adapter on the surface because the usb FLOGGER is in that port) oh surface woes.

anyhow, I’m going to try and find a usb hub to plug them all in to the one single port on the surface. Anything else I can check while in the Flogger OS?

@Tom-Elliott That is a better one. FLOGGER it is, Tom.

@Sebastian-Roth I like flos better, no offense @Tom-Elliott. I’ll boot into that and get you all the output of those 2 commands. may come in cell phone selfie form, but hey, that’s okay, right?

@Sebastian-Roth do this in the FLOS usb? (the one debug Fog Live OS I created?)

@george1421 Yep 1.2.0 stable with some mods though, eg playing with kernels and the like and I’ve pulled the /tftpboot directory from a recent trunk version but I don’t know how much of an effect that will have. At this point it all seems to be working normally, eg still imaging other hardware without issue.

@george1421 ip addr show indicates the following:

1: lo loopback
2: eth0 <NO-CARRIER, BROADCAST,MULTICAST,UP> but doesn’t indicate an IP
3: eth1 gives information that I would think would be on eth0, such as an IP address on my network

So according to this and your response, I think the fog live boot OS (FLOS fog-live-oS, good name?) will work. So, where do we go from here?

@george1421 Make and model of network adapter is a Linksys 200M ver 2 USB to ethernet adapter.(just like this one: http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=1030257) How do I tell where I’m pulling the IP address from? I believe it is from the fog client OS. This is booting off the fog debug USB stick I’ve made earlier.