Posts made by SeqSupportEdkey

[quote=“Uncle Frank, post: 45539, member: 28116”]Hmmm, seems like you end up with a (ipxe) shell. Could you please try again and enter the following command on that shell:
[CODE]ifstat[/CODE]
For more information see here: [url]http://ipxe.org/cmd/ifstat[/url]

I am wondering if you see “RX:0” or “RX:4” …?? If you see zero it means that it was unable to receive the DHCP answers (although we see that they are on the network).

Next step could be to build iPXE with realtek driver only:
[CODE]make bin/realtek.kpxe EMBED=… DEBUG=realtek:3[/CODE]

For further posts please specify what ipxe binary you were exactly using, to prevent that we all get confused when re-reading the thread…

[B]Edit: I just tried to lookup your MAC address. [URL=‘http://www.macvendorlookup.com’]www.macvendorlookup.com[/URL] is telling me that it is “QUANTA COMPUTER INC.”. Maybe I am wrong with realtek NIC?? Could you please boot that machine with a live CD or something else and tell me which NIC is in that 11e. Best would be if you can find out about the PCI ID!![/B][/quote]

[SIZE=16px][FONT=Calibri][COLOR=#000000]03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 10)[/COLOR][/FONT][/SIZE]

[FONT=Calibri][COLOR=#000000][SIZE=16px]With a debug it does not get past initializing device. I was able to get dhcp to work with the device by using gPXE which is odd because it is discontinued.[/SIZE][/COLOR][/FONT]

[quote=“Uncle Frank, post: 45479, member: 28116”]Unfortunately I am not able to see what’s going on by looking at the packet dump. I see a full DHCP conversation (discover, offer, request, ack). That’s probably when the NIC itself requests and IP (and PXE) on boot up. After that I can see another DHCP discover and offer. But the client does not seem to handle the offer coming from the DHCP server. Anyone else got an idea what might be wrong here?

Could you please build your own iPXE binary and add “DEBUG=dhcp” to the make call?? Might be interesting to see the output. Please take a picture![/quote]

[ATTACH=full]1870[/ATTACH]

[url=“/_imported_xf_attachments/1/1870_Debug.jpg?:”]Debug.jpg[/url]

Here is the wireshark capture.

[url=“/_imported_xf_attachments/1/1868_Wireshark Capture.zip?:”]Wireshark Capture.zip[/url]

[quote=“Uncle Frank, post: 45403, member: 28116”]Is it possible to connect DHCP (windows), FOG and the client to a small office switch just for testing?? If you don’t see a difference then we know it’s a real iPXE/FOG issue. But I am pretty sure you don’t run into DHCP timeout in a small setup.

To see what’s really going on you can use wireshark and tcpdump to capture the packets on the network.

Either you install wireshark on your windows DHCP server (not sure if you are allowed to do this but if might come in handy again). Or you can use a hub to connect in front of the client (your normal switch - hub - client) or configure a monitoring port on that switch where your client is connected.
Use a laptop to capture the traffic on that hub. You’ll see a lot of stuff, I am sure. Try display filters ‘bootp’ (DHCP) and ‘tftp’. You are welcome to upload the saved pcap file for us to inspect.[/quote]

We have a portable laptop we use as a fog server for imaging networks which do not have a dhcp server. We installed a fresh copy of Debian and Fog 1.2.0 and updated to the latest SVN. Tested both undionly.kkpxe and .kpxe plus .efi and uefi and still the same result. I will do a wireshark on the fog laptop and see what I get.

[quote=“Tom Elliott, post: 45394, member: 7271”]Also, do you have STP (Spanning Tree Protocol) on your network? If you do, is there anyway you can disable it or use Rapid STP/PortFast?[/quote]

I would have to speak to the boss about the network related issue. We started from scratch and have not updated to the newest SVN. Would this possibly make a difference? We did upgrade the tftpboot folder but that is all.

[quote=“Uncle Frank, post: 45391, member: 28116”]Not sure if understand your question. As Tom already noted, place the compiled binary into your TFTP root directory. If you were asking where the debug output will end up! That you will see right on the screen when booting up the client… no file output.[/quote]

So we have figured out that there is an option in the bios that protects the memory from malicious attacks and that was blocking ipxe. But unfortunately it gets to configuring net0 and errors out with a 0x040ee119 now. Seeing what debug info I can get off of the undionly.kkpxe I built.

[quote=“Uncle Frank, post: 45333, member: 28116”]So iPXE is initializing the device but we don’t know which one it is. I tried to find out which NIC is in that 11e and it took me at least 20 minutes. I really hate all those websites where you read “Tech specs… CPU … Gigabit-Ethernet …”!! No NIC brand or model name, arrgh!

Found it: Should be RTL8111/8168B, right?? This NIC is should be supported by iPXE from what I can see in the source code. Seems like we need mode debugging to get this working. The easier step (I think) is to capture a packet dump to see if iPXE is sending any packets after initializing the device. The first packet should be a broadcast (DHCP request) so you should see it everywhere on your network. Please install wireshark on one of your PCs, connect it to the same net with FOG server and client and capture while booting up the 11e Thinkpad. You should see DHCP request when the NIC itself greps an IP first, then iPXE comes up. Do you see another DHCP request after that??

Second, you need to build a custom iPXE binary with debug enabled. I just added a section to the existing wiki article about debugging, see here: [url]http://fogproject.org/wiki/index.php/Building_undionly.kpxe#Debugging[/url]

In your case I’d start with adding ‘DEBUG=undi,dhcp’. Hopefully you can see where it stucks. Please post a picture of it.

I really wonder why ipxe.kpxe is not working for you. To explain: undionly uses the general UNDI interface to communicate with the NIC. If you want to use real iPXE drivers you need to use one of the ipxe.xxx binaries. You can give that a try with debugging enabled (DEBUG=realtek) too!!

Edit: I just found a couple of threads about iPXE and realtek 8111… Most are saying that they got it working with that NIC.
[url]http://fogproject.org/forum/threads/realtek-8111-8168-undionly-kpxe-hangs-on-initialising-devices.10453/[/url]
[url]http://lists.ipxe.org/pipermail/ipxe-devel/2014-October/003837.html[/url][/quote]

Once I have created a debug kpxe where does the debug file get dropped?

No luck. Tom do you have any suggestions?

[quote=“Wayne Workman, post: 45318, member: 28155”]Optionally,

You can also turn UEFI back on, and try every .efi file.

You might have better luck than I did.[/quote]

Alright I will try this next.

We have a windows server that runs our DHCP. We are not using dnsmasq. All of the ipxe.pxe/kpxe/kkpxe produce the initializing device issue. The undionly.kkpxe produces the initializing device issue as well and the undionly.kpxe makes it past the initializing device but gets stuck at the screen of the image I posted. This laptop is the only laptop we have had problems with so far from Lenovo. Every other machine we have works just fine with fog and undionly.kkpxe.

[quote=“Wayne Workman, post: 45310, member: 28155”]The screenshot you posted,

There should be a message after that… it will only show briefly.
Can you take a video, and then play back and pause on that message? And then tell us what it says?[/quote]
No message shows. It just sits there with a blinking cursor. It does not go past that point in the image.

EDIT: If we set it to use the undionly.pxe versus .kpxe it loops back to the boot device screen but there is still no screen with a message.

[quote=“Wayne Workman, post: 45308, member: 28155”]I had a similar issue yesterday at home.

It turned out to be permissions on this folder: /var/www/html/fog

To test, go here: [URL=‘http://10.0.0.3/fog/service/ipxe/boot.php’]http://x.x.x.x/fog/service/ipxe/boot.php[/URL]

If you see “permission denied” or anything like that, it’s permissions.

Those should be set to: chmod -R 755 /var/www/html/fog

Of course, that’s the location in [U][B]Fedora.[/B][/U]

For us to tell you where it is for you, we need to know [B]what OS[/B] you’re running.[/quote]

Sorry Debian 7, and I have access to that location. I do not get a permission denied.

[ATTACH=full]1861[/ATTACH] [quote=“Tom Elliott, post: 45305, member: 7271”]According to what I’m seeing on that screen. You’re definitely NOT running 3225, at least not in the TFTPBOOT folder.[/quote]

Sorry trunk now updated to r3225, still getting the same screen though.

[url=“/_imported_xf_attachments/1/1861_20150410_083016.png?:”]20150410_083016.png[/url]

[quote=“Uncle Frank, post: 45262, member: 28116”]From what I can read here ([url]http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/thinkpad_11e_yoga_11e_hmm_sp40f29949_01.pdf[/url]), I am pretty sure this is UEFI…

Please try to switch to legacy BIOS mode and hopefully undionly.(k)kpxe will work for you then!!

Edit: Didn’t see your post…
[B]Well then you need to provide more information about what exactly you tried and the error messages you got! Let’s start from scratch: Please use undionly.kpxe and boot uo the machine. What do you see? Errors? Reboot? Hangup? Take a picture/video and upload so we see what you see…[/B][/quote]

Fog 1.2.0, SVN Trunk r3225, undionly.kpxe(.kkxpe hangs on intializing devices) , TFTP Enabled, Tom Elliot Unofficial Kernal 3.19.3 (x86_x64). We were able to get it past initializing devices but it does not go any further. Here is a picture of where it stops. These are the only machines that this has occurred with so far. We have other uefi based machines that have not had any issues.
[ATTACH=full]1860[/ATTACH]

[url=“/_imported_xf_attachments/1/1860_20150410_074417.jpg?:”]20150410_074417.jpg[/url]

Machines are uefi based machines. Machines are prepped for windows 7. Secure boot disabled, Legacy mode enabled, optimized OS defaults disabled. So it is booting to the NIC in legacy and not uefi.

We are having issues with a set of brand new Lenovo Thinkpad 11e’s that will not network boot. We have tried all of the .pxe’s and none of them work. We also tried the chain loading method into pxelinux and failed. We are at a loss. Is this a kernal issue or a ipxe issue? Do we need to look at creating a custom .pxe for these machines?

Still did not work. What is odd is that the image was working just fine until I set up fog correctly for renaming the computer and joining it to the domain. Kaspersky is not even attempting to install. It just skips right over it and goes straight into windows. I am at a loss. Need a day to think.

Alright I put the delay command in the SetupComplete script, then created a .cmd file with the net start “FOG Service” in it which was then added as a reg value in run once. Phew… We will see if that works. Been trying so many different things over the past few days.

[QUOTE]SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx

REG ADD %KEY% /V TITLE /D “Finishing Post Image” /f

REG ADD %KEY%\001 /VE /D “OCS Agent” /f
REG ADD %KEY%\001 /V 1 /D “%systemdrive%\Post_Image\ocs\ocspackage-generic.exe” /f

REG ADD %KEY%\005 /VE /D “Alertus” /f
REG ADD %KEY%\005 /v 1 /D “%systemdrive%\Post_Image\alertus\alertus-desktopalert-3.0.12.165.msi /quiet” /f

REG ADD %KEY%\010 /VE /D “ScreenConnect” /f
REG ADD %KEY%\010 /V 1 /D “%systemdrive%\Post_Image\ScreenConnect\Elsinore.ScreenConnect.ClientSetup.msi /quiet” /f

REG ADD %KEY%\015 /VE /D “DriverPacks” /f
REG ADD %KEY%\015 /V 1 /D “%systemdrive%\Post_Image\SAD3-130825\DP_Install_Tool.cmd -s” /f

REG ADD %KEY%\020 /VE /D “Kaspersky” /f
REG ADD %KEY%\020 /V 1 /D “%systemdrive%\Post_Image\Kaspersky.exe /s” /f

exit[/QUOTE]

This is what it currently looks like. How would I go about adding it into there. I am using Secondrun in order to install my software. Do I need to put the delayed-auto command into the SetupComplete Script in the scripts folder?

My SetupComplete script contains

del /q /f c:\windows\system32\sysprep\Unattend.xml
del /q /f c:\windows\panther\Unattend.xml
START C:\Post_Image\Secondrun.cmd

See thats the problem is I want to completely automate the process. Our networking/server guy is out for the week. We will be upgrading to 1.2.0 to help resolve some of these issues with automation.