Posts made by yochaigal

@sebastian-roth I worked around the issue using an iPXE boot ISO.

@george1421

If I understand you correctly, this would be exactly what I’m looking for. Would the end result simply require a custom grub.cfg that calls the image process?

@george1421

Ooooh, I see. The primary use here is to setup deploy tasks (typically updated Windows images). Would I need to add the USB NIC’s MAC each time?

Running Version 1.3.0-RC-29
SVN Revision: 6031

First, I built a BIOS bootable client:
After ensuring the BIOS is in Legacy mode, I try booting the USB stick. It gets to iPXE initializing devices… and then quickly flashes some text, only to return to the boot devices screen.

Second, I built a UEFI bootable client:
Switching to UEFI mode in the BIOS, the USB is completely ignored.

I built the FOS client but I get an error after the menu: fatal error unknown request type null

Finally I created a debug USB, I can boot to the debug console but am unsure where to go from there.

@george1421
The BIOS must also support it, yes?

@x23piracy

I’m going to order one of these adapters, thanks! Am I to understand that OEMs require specific USB chipsets (in this case, Lenovo) in order to PXE boot over USB?

Hello. I run a small computer repair shop that sees dozens of different machines from various OEMs each day. Many are a few years old or more. I setup FOG earlier this year, and it is absolutely amazing - however, I have not been able to consistently use FOG on machines without a built-in ethernet jack; namely Ultrabook PCs. Some do not support it at all, others seem to require that the iPXE builds I’m creating use specific USB-to-NIC adapters.

For instance, today I was working on a 1st-generation Lenovo X1 Carbon; there is no way to get this thing to PXE boot on a USB NIC! Thus I have to install Windows the old fashioned way (and wait 20 hours for the updates to finish).

Anyways, what I’d like to do (as a workaround) is figure out the proper way to boot systems like this into a compatible environment - for instance, in the CloneZilla days I could just boot Parted Magic and load CZ from there. Is there a similar approach in FOG? Is this the right direction to go?

Thank you for your time.

PS The FOG server is running on Ubuntu 16.04 64bit.

@Sebastian-Roth

Apologies, I’ll explain:

On ~10 different machines (XPS 15, Precision 5510, X1 Carbon 3rd gen, Thinkpad T500, Thinkpad X220, HP Elitebook, etc) I have the same result: it’s as if nothing is plugged into the ethernet port. I get a “Waiting for link-up on net0 . . . . . . . . . . . . . . . . Down” no matter what. I’ve tried using an iPXE bootable ISO as well as simply connecting to the FOG server via BIOS/UEFI PXE. I can successfully boot to the FOG menu (and image) using actual ethernet, but never using this adapter (or the other two I’ve tried). Further, I’ve made 100% certain that the BIOS/UEFI is configured for ethernet PXE booting (the X1 Carbon for instance has a menu entry for this exact purpose). I always switch to Legacy/CSM with secureboot disabled.

I’d found John Willis blog previously - that’s what led me here, actually :).

@Wayne-Workman

Tom Elliot’s seem to work, see https://forums.fogproject.org/topic/2118/looking-for-usb-nic-that-is-known-to-work-with-pxe-fog/5
And that’s what I’m using (via FOG). I’ve tried booting from various iPXE builds as well but with no luck.

I’ve set the kernel arguments system-wide, as well after host registration - I still can’t get anything to boot using USB NIC! Not sure what I’m missing.

Thanks, found it under FOG System Settings.

Thanks.
Forgive my ignorance here, but where can I set system-wide kernel arguments?
Thanks

Hello!

Currently have FOG Version 1.3.0-RC-9/ SVN Revision: 5952 running on an Ubuntu 16.04 server; works great!
I’m able to boot almost any PC, and image sysprepped Windows images to the device without registration. This is great for me, because I run a small repair shop that gets tons of different PCs every single day.

Anyways, recently I bought a StarTech USB21000S2 (recommended from these forums) in the hopes of booting the newer Dells, HPs and Lenovos that don’t come with a built-in ethernet adapter. However, I have so far been unsuccessful - booting directly with PXE as well as using an iPXE bootable ISO. I’ve also tried adding the host manually via MAC address (kind of a pain for my techs, honestly) with the appropriate kernel arguments. I’ve made sure the BIOS had the appropriate settings (no secure boot, USB/PXE boot enabled where available, etc).

I’ve seen some mention of symlinking a different bootable kernel, but haven’t found anything “solid” pointing me to where I’m going wrong.

FWIW, I’m a Linux and Windows sysadmin, so don’t hold back! Any advice appreciated.

Thanks

@Junkhacker Yeah, this totally worked! That’s really all I need; I doubt I’ll see another of these machines for some time.
Thanks so much you guys! Consider this thread solved. I really appreciate how quickly people here responded; I’ll try to help others in turn (at least, as much as I can!).

Here’s a more general question:

I’ve setup FOG for my computer repair business; we install Win/Mac/Linux on a daily basis on all sorts of different hardware scenarios; we were originally looking into MDT until I found this amazing FOSS solution, that so far works great!

However, In instances where I’m dealing with different hardware on a regular basis, what is the best “fallback” scenario? Is there an alternative PXE booting utility I could use in these cases? I’ve already tried PLOP but had the same issue.

Thanks

@Wayne-Workman I already did - it is using the “latest” release (late 2011).

http://support.lenovo.com/us/en/products/Laptops-and-netbooks/Lenovo-V-Series-laptops/Lenovo-V570-Notebook/1066/A9U/downloads/DS027341

@Junkhacker Done. Same problem:
0_1463154351281_undionly.0.pcap

@Junkhacker Oh right, that makes sense!

Well, I changed the name to undionly.pxe (8.3) - same issue. Uploaded new pcap file.
0_1463151170763_too_long.pxe.pcap

I’ve attached the tcpdump file - wireshark tells me that you’re right on the money, though:

0_1463149698271_too_long.pcap

I also tried changing the undionly.kpxe file to just u.kpxe (and updated my dhcp server) but had the same result; is there something else I need to do when changing the name?

Thanks