Posts made by dustindizzle11

@Sebastian-Roth

@Sebastian-Roth I added “has_usb_nic=1” to the Host Kernel Arguments section and it did the same thing it would do before, which is just zip to a black screen. This is the behavior I get when I don’t get an address. I am using the 4.6.2 Kernel. I didn’t get any messages about re-plugging the USB NIC in though. Let me know if you need to me try anything else.

@Sebastian-Roth Original

@Sebastian-Roth When imaging it just zips to a black screen. I am not able to see any error messages. All I did to the init.xz was just modifying the /etc/network/interfaces and adding eth0 to the list to make it work.

@Tom-Elliott Thanks for the response! So I got some mixed results with the commands you gave me, specifically the “awk” commands. It seems that capitalization does matter. To make sense of the picture below…

First I ran “ip -0 -o link show”, which lists eth0 as a network device.

Next I ran “ip -0 -o addr show | awk -F’[: ]+’ ‘/link[/]?ether/ && !/<MACOFHOST>/ {print $2}’” with the MACOFHOST in all Capitals (notice the mac only has one letter to capitalize in the picture). This gave me “eth0” in return.

After that I ran the same exact command as above, but with the MACOFHOST being lowercase (the “f” is lowercase). In return I got nothing. So lowercase did not output anything for me in this case.

Then I ran the version without the exclamation point, (which I’m assuming means NOT command wise), with the MAC being CAPITALIZED “ip -0 -o addr show | awk -F’[: ]+’ ‘/link[/]?ether/ && /<MACOFHOST>/ {print $2}’”. In return I got nothing.

Finally, I ran the above command again, but lowercase instead. In return I got “eth0” again.

So it seems that capitalizing does the opposite for each command. With the “!” before the MACOFHOST, having the MAC be Capitalized provides “eth0” in return. Without the “!” before MACOFHOST, having the MAC be Lowercase provides “eth0” in return. Hopefully this helps troubleshoot the issue in some way.

@Sebastian-Roth @Tom-Elliott @george1421

I took your advice and modified the init.xz to make a custom init, and all I did was just add “auto eth0” and “auto iface eth0 inet dhcp” to the interfaces file. It brings up eth0 and it images after adding this. So at this point it works. The fix is probably not the best fix in the world, but hey, it works!

@george1421 The problem seems to lie with “eth0” not being present in the interfaces file itself. Once it is added and the network is restarted, we get an address. I am definitely open to creating a custom init, it doesn’t look too complicated. I just need to figure out what specific things I would need to do to bring it up.

@Sebastian-Roth Yes I am willing to modifying the init.xz, I just need to make some time to do it.

@Tom-Elliott Thanks for the script! Ill have to take a look at that.

@Sebastian-Roth I totally understand if not much can be done, if anything, I just want to give people a heads of that this NIC or NIC/MB combo does not play nicely with Fog at the moment. We were able to image the whole lab, but in involved entering debug mode for all the machines and manually bringing up the interface, then typing “fog” to image them. Thanks everyone for your time and help trying to figure this out. If I find anything else out in the future I will add it here.

Dustin

@george1421 Just want to add, we just tested a different fog server that has it’s own network (hands out dhcp) and only a dumb switch sits between this fog server and one of these models. Still the same exact result.

@Tom-Elliott Yes we have other systems with the same model MB. This happens in the same way for all systems that have this MB. Thanks again for trying to help with this, I appreciate the time you guys take to help troubleshoot. It is strange that it is not auto configuring eth0. Btw, when in debug mode just adding eth0 to the interfaces file then restarting the network is all that needs to be done to get an address and fog the computer. Just mentioning that because I mentioned in an earlier comment what I did to get an address, which was more than I needed to do.

@george1421

We have port fast enabled on all ports

@Tom-Elliott

There is currently already a dummy switch in between. I can image any other model from the same spot, just this model behaves this way.

@Tom-Elliott

If I go into debug mode and manually enable the interface, then restart networking it works (after getting eth0 added and typing “fog” in debug mode, the computer images fine). The problem is that for some reason, eth0 is not setup as an interface.

So all I did manually was…

ifconfig eth0 up

added to /etc/network/interfaces

auto eth0
iface eth0 inet dhcp

then /etc/init.d/S40network restart

I probably could have just added it to the interfaces file and restarted to get it an address, but wanted to show what I did above. Also I am not sure that the name was “S40network”, i just remember it being called S40"something".

Anyone have any ideas as to why it is not getting added automatically?

@Tom-Elliott
It is bridged.

@george1421
one “-n” gives me the same thing … “ip link show” lists eth0 though for some reason.

Also, Side note, I am using the 4.6.2 Kernel at the moment with debug on.

@george1421

I don’t get the expected output from running lspci -nn (or by using the -vv option which displays the same thing. Pic below)

Thanks for the response. It is not spanning tree, so I have eliminated that.

I have tried lots of kernels, but here is a list of a few…

4.6.2.64
4.7.0.64
4.7.3.64
latest bzImage

If I do a download debug task, when at the shell prompt I noticed that if I run “ifconfig” to see my interface and ip address, there is no interface listed and therefore no address. Just the loopback device (just seemed odd)…I can see that eth0 is an option from the command “ip link show”. What can I do to debug this? Thanks for your time.

Dustin

Not sure if anyone has ran into this, but I have not been able to get these CTL computers to image. As the title states, they have a i219LM NIC, on an ASUS Q170M-C Motherboard. The computers will grab ipxe fine initially, but hit a black screen when trying to send an image or register them with FOG. I have checked the FOG Compatibility checker within the menu, and it states that these computers are not compatible with FOG. I use Fog 1.2… Things I have tried are…

• Trying a bunch of different Kernels (including the latest from https://fogproject.org/kernels/). I am positive that the newer kernels were being used too,. I gave them totally different names in the /var/www/fog/service/ipxe/ directory, and I can see them loading when booting.

• Trying different ipxe files (I use undionly.kkpxe, but tried the others in tftpboot, along with the latest trunk ipxe files in combination with the above latest kernels)

• Made sure that it is legacy booting, not UEFI…

I have used FOG for quite a while, and as the compatibility checker states, I think it is a kernel issue. Does anyone have any ideas or experience with this NIC? I I appreciate any help. If anything, I am just letting others know that this NIC is giving me issues. Thanks!

@Wayne-Workman

Thanks for the explanation, makes sense. If that is the functionality, It would be cool to have the “multiple domains” set in the fogsettings or something. Then fog could have a simple dropdown to select the domain that will be added upon adding the host in the web gui.

@Tom-Elliott @ch3i @Wayne-Workman

Thanks for the responses! The “autofill” was the issue. The real issue though, is not that the browsers (Chrome and Firefox) had saved passwords, it is that when check-box is clicked for AD when creating a new host, nothing happens if any sort of “autofill” or “saved passwords” exist for the site. (picture below showing the portion I am talking about. BTW - The forums only let me upload files, the icon to insert pictures doesn’t function). Maybe this is just normal behavior, but I would expect fog to “fill in” the correct defaults once the check-box is hit regardless of any saved passwords or auto fill from the browsers. It works correctly (fills in the defaults) if autofill is turned off and if I delete my saved passwords for the site. It won’t function (fill in anything), if the autofill or saved passwords exist.