@Blsmith said in Need USB to Ethernet Adapter that works with Ipxe:

Thanks everyone for their help. I have purchased the official USB-to-Ethernet adapters from Microsoft and Lenovo and are going to try them out since they state that they support LAN or pxe boot. Once they come in I will let you know if they work with the guides you have posted. Thanks again for your assistance.

This is what we are finding is the best solution (purchase the recommended ones from the hardware mfg). WIth UEFI the firmware has to support the ethernet driver (usb or otherwise) for pxe booting to work with uefi systems. Without the supported network adapter the firmware will simply not see the network adapter.

The Shuttle-Bios doesn’t have these features.
The Dell-Bios is running in Legacy-Mode.

@george1421
Yes i have just tried that and the result is the same.

@george1421 I downloaded a copy from the kernel directory on a different PC and copied it over. They were just called bzImage and bzImage32. I will get the version in the morning and report back.

I did run the test before I left and it did fail network. I also wasn’t able to see the mac address or IP through the menu.

EDIT:

Also, running Ubuntu 14-04 LTS
I get bzImage: x86 boot sector

And I got the bzImage from here https://fogproject.org/kernels/

EDIT 2: Not sure why the edit from my main post vanished. Let me put that here again.

I took a video of the newest message. From reading the blurry video, this is what I can read before the fog text logo comes up.

mmc0: Unknown controller version (3). You may experience problems.
usb 1-5: device descriptor read\64, error -71
EXT4-fs (read): couldn’t mount as ext3 due to feature incompatibles
Starting logging: OK
Populating /dev using udev: udev[2612]: error creating spell? fd: Function not implemented
done

EDIT 3: Took bzImage files and init files from a test fog machine I was messing with. 1.3.0 FOG on there. Copied the to the FOG 1.2.0 server.

The compatibility test comes back with disk and network passing.

Trying to register a host and I get:
Unable to register host: Invalid MAC Address (/bin/fog.man.reg)
Arg Passed:

I think I am making some progress here.

@george1421 Like I mentioned above, the Lenovo ThinkPad 13 works perfectly with the same BIOS setup. No need for the USB solution that the Yoga 260 requires for UEFI/Legacy dual booting. I fully believe the problem is entirely with the firmware on the Yoga.

Both work better now than they did 4 months ago with the BIOS version available then.

@Wayne-Workman Sorry, I will do that in the future. I was able to capture my image after fixing the GPT remnants.

Thank you for all your help!

We have received 3 type of Acer computer this year X2640g, X4640G and N4640G.
Both X are working fine with undionly.kkpxe but N isn’t.
N is only working with ipxe.pxe.

This tells me that the ‘N’ system is a uefi system and the ‘X’ systems are bios (legacy) systems. You must use the right iPXE kernel with the proper firmware or it won’t work.

As for the error above. It appears that the undionly kernel can see the network adapter, but not communicate on the network. I too suspect that this is a spanning tree issue. The problem is that spanning tree takes 27 second to begin forwarding traffic. The 10 second delay kernel is not sufficient to bridge this gap. Its best to enable one of the fast spanning tree protocols on this switch port. OR as a test, place a dumb switch between this target computer and the building switch. This dumb computer will keep the building switch port in the forwarding state while the target computer boots. If inserting the dumb (unmanaged switch) between the building switch and the target computer works, then you do have a spanning tree issue.

@Tom-Elliott Yeah it works fine with this file !
Thanks, topic can be closed 😉

@xerxes2985 just for reference I’ve started documenting this solution here: https://forums.fogproject.org/topic/8971/pxe-booting-surface-pro-3-to-fog-menu

afaik the type cover has its own firmware, just a suggestion… (maybe something to old or even to new) just my 50 cent.

Finally, with all you explanation it’s really my image who’s corrupt. I was able to recreate it with another PC with the fog version 1.2 and now I can deploy it on my HP Prodesk G3.

Thanks for your time

@egregers For a single drive there is no advantage. But I can say with my fleet of computers they are all dells and all are in the raid-on mode with a single drive. Its not clear why you are having this issue. But again I don’t have a T5810 to confirm or deny with. As always do you have the latest firmware installed on that T5810?

@Wayne-Workman The solution from Tom Elliott worked perfectly. However, after installing some software and trying to take a new image, new problems appeared. Will make a separate topic for this.

I’m going to update this thread because the only thing worse than finding no solution to your problem on Google is finding a problem listed without a solution.

These machines can in with 8gb of RAM. Some came in with 4 2gb sticks of memory and some came with 1 4gb and 2 2gb sticks. The machines without the 4gb stick work perfectly. They will image just fine. If I image them and then add the 4gb stick back in, they blue screen. So Tom was correct, it was a RAM issue. The 4gb stick of RAM is causing the issue. Thanks for all the help!

@Quazz Actually on the new Gen 4 there isn’t to many bloatware and “management” tools.

But I will actually look at building a native windows 10 enterprise 1607 iso.

No issues. It just worked.

The Gen1 (Legacy) adapter appears to still be only 100Mb.

@Dave-Misco So your issue is resolved?

I guess lets start with 2 questions.

What version of FOG are you using? On the T3620 are you using the built in RAID controller and have the disks in a RAID array? (I have a T3610 so I’m familiar with the model).

@dustindizzle11 Sorry for my late reply. There is a side way you could go with this now that you know how to modify the init.xz image. Grep yourself a copy of the current script and exchange the one you posted with this new one. See if you can make it work with this. Just an idea for a quick dirty fix.

Try different hdd exit types. Look up the host in Host Management, and on it’s general page you’ll see two drop downs towards the bottom for hdd exit types, one is BIOS the other is UEFI. so the mode that the computer is operating in determines which of these settings will apply. I would first recommend trying Grub, then if that doesn’t work just try one at a time - do a full reboot between each try.