@Wayne-Workman figured it out after asking google, seems as if it’s a common bug on debian.

You have to change the TFTP_ADDRESS from “0.0.0.0:69” to “:69”
( /etc/default/tftp-hpa)

Now tftp service loads up during boot.

@Wayne-Workman i wasn’t really clever in browsing this forum with my phone, so I thought hey Google may just pop with the answer quicker but I will certainly use that link for my reference for future mishap.

Thanks bud (Y)

@george1421 thank you, yes we use win 2012 r2. I did set this up in the past partially never really got to testing it as all our machines within the organisation are on legacy mode. certainly will now try it.

okay figured it out. it seems the DELL Venue Pro 11 does not like legacy mode. (well realtek RTL8153 doesn’t like legacy mode)

What you have to do is change the boot option 67 to snponly.efi and boot via UEFI ipv4. I didnt test to see if it registered the host as i manually entered the mac address & host details on the web management service and set the task via the web management console.

Thank you for your help @george1421 & @Sebastian-Roth

UPDATE: I was using Fog 1.3.0-RC-8 & i had to reinstall OS from scratch after changing bios to UEFI as Fog looks for a gpt scheme on HDD (in the venue’s case a eMMC) or it will fail.

@george1421 yes, i only have one running at a time. Never really tried it lol would certain make the server confused. Joking a side, I already have option 67 on undionly.KKpxe not Kpxe but i will certain give ipxe.kpxe a go and see how it responds.

No need to apologies mate am glad your someone who’s responding to my fault, so Thank you.

@george1421 I have two VM’s (one with fog 1.2.0 & another 1.3.0) and their both have the same ip address (10.0.21.0) I have checked the tftp config file and it’s pointing to the right IP.

Option 67 is set to undionly.kkpxe, my venue bios is on legacy mode and my Fog trunk version is the latest 1.3.0-rc8.

Technically there is nothing wrong with the fog server as i have re-imaged a laptop and uploaded a image (which has a built in NIC not a venue) and it worked fine on both servers (fog 1.2.0 & 1.3.0)

It just right now the problem is when am on the boot menu and i try registering the host the venue either restarts or the screen stays blank. If i register the device before hand & then try set a task to lets say download (re-image) it freeze’s the moment it reads the kernal (bzImage)

@Sebastian-Roth I checked most of the forum & wiki page bud & yes there is quite a lot of issue with this model (chip) i just assumed there might have been a fix now as this problem dated back to many years. Thank you for iPXE binaries.

how strange, when i pressed the enter button on the keyboard the percentage went from 90% to a 100% and went onto the next command line…http://my-ip-address/fog/service/ipxe/bg.png and then the same thing is occuring where i have to press the enter button after a few seconds to get the percentage up.

Update: i can now get to the boot menu screen however it hangs on the bzimage…i just need a workaround so if there’s a method please me know.

Note: am a beginner on linux so if there;s any specific config file change that i need to then could you please tell me via steps.

Thank you

Hi all,

Am trying to image a few Dell Venue 11’s using the official DELL USB Ethernet adaptor which is a Realtek RTL8153 model.

When i first tried it, it hanged on iPXE initialising devices, after going through the forum i realised that i was to change my option 67 to undionly.kkpxe.

I changed my option 67 and i got happy to soon and the system started to hang on
http://my-ip-address//fog/service/ipxe/boot.php....90%…

My project is on version 1.2.0 however for test purposes i made a clone vm and upgraded the fog 1.2.0 to the trunk version and this time the same thing happens but hangs on 36%

Any ideas anyone, in whats wrong?

Thank you.

@Wayne-Workman i wasn’t really clever in browsing this forum with my phone, so I thought hey Google may just pop with the answer quicker but I will certainly use that link for my reference for future mishap.

Thanks bud (Y)

@Wayne-Workman figured it out after asking google, seems as if it’s a common bug on debian.

You have to change the TFTP_ADDRESS from “0.0.0.0:69” to “:69”
( /etc/default/tftp-hpa)

Now tftp service loads up during boot.

@Wayne-Workman

no problem, I’ll have a look.
Damn the letter “n” grrr… thank you

@Wayne-Workman haha these are the moment that you want to start laughing due to stupidity … You was right Wayne my option 67 had the “n” missing.

However when I loaded up debian the initial boot screen states tftp hpa: failed

I had to restart the service in order to get it running. Any ideas?

Thank you also for pointing out my error. I now have a sigh of relief.