There are a lot of different USB to Ethernet adapters out there. But I am pretty sure that not all of them will work.

There is a thing called ECM (Ethernet Control Model) which is one of several different protocols used by those adapters (see here for more information: [url]http://en.wikipedia.org/wiki/Ethernet_over_USB[/url]).

Check out this post: [url]http://www.johnwillis.com/2014/03/pxe-booting-using-usb-to-ethernet-dongle.html[/url]

Are we talking about this ASUS brand adapter?? [url]https://www.asus.com/Tablet_Mobile_Accessories/USB_Ethernet_Cable/[/url]
I found it very hard to find information about this!! Not sure if I’d buy it. I still don’t know which ethernet chip is used and if linux in gernal is happy with it… And it’s not gigabit ethernet, right? I highly recommend looking for other adapters.

We’ve had several people here in the forums. Some got their USB thingys working. Maybe it’s time to add those to this list here too: [url]http://fogproject.org/wiki/index.php/WorkingDevices[/url]

EDIT: There is a long (still reading) and interesting thread about USB ethernet adapters in the ipxe forums. Seems a lot more complicated then I thought at first. As far as I could find out the chip used in the ASUS adapter is ASIX (maybe AX88772B). Start reading here: [url]http://forum.ipxe.org/showthread.php?tid=6151&pid=10612#pid10612[/url]

Do I get this right? You were never ever able to boot FOG (upload or download) on this Latitude 3540? Could you please download ubuntu live cd (or any other live cd really) and try booting this. Just to make sure.

Others made it work in the past:
[url]http://fogproject.org/forum/threads/dell-latitude-3540-fails-with-kernel-3-8-8.10224/[/url]
But there is another thread talking about issues on this model:
[url]http://fogproject.org/forum/threads/pxe-menu-not-loading-on-latitude-3540.12519/[/url]

Hope we can get this to work at some point.

Any news on this?? Please make sure TFTP is running and listening on the server:
[CODE]sudo netstat -antup | grep “:69”[/CODE]

Thanks for reporting back although I am not happy that at least two people had an issue with this but we are unable to find out why! I have phpmyadmin installed on all my FOG servers so I suspect it to not be the problem. And I’d really wonder if webmin plays a role in this either. But could you still install webmin just to make sure??

Sorry if my last comment wasn’t clear. With “you’d still need to chainload iPXE” I meant that using SmscUsbNetUtility.efi doesn’t help at all as you need iPXE to use FOG (version 1.2.0 and newer)!

I didn’t have much time today so I had no chance to really find out where this “Boot Succeeded - Ethernet IPV4” is coming from. It’s definitely not iPXE. I guess it’s the manufacturer binary that’s burned into the NIC ROM. So it seams like iPXE hands back to the NIC at some point…?!?

Maybe it’s time to get into compiling your own iPXE binary with debugging ON!

[CODE]make … DEBUG=efi_init,efi_snp[/CODE]

[quote=“Wayne Workman, post: 44019, member: 28155”]I bet the manufacturer’s driver will work.[/quote]
Sure it will! I saw that on their website too. But what will it do?? To get FOG running you’d still need to chainload iPXE…

So far I haven’t found anyone on the web having the same message: “Boot Succeeded - Ethernet IPV4”. Are you sure that’s what it says?? I will grep through the ipxe code when I get back…

Well, that’s a whole new story but would you be interested to get rid of this dependency from your ISP? I don’t say that you should change your ISP but you could do DHCP yourself (using the exact same addresses) and ignore the external DHCP traffic completely. Feel free to start a conversation on this with me and we should be able to set this up for you…

You’d probably best use DHCP user classes. There is one example for this in the wiki in Macintosh: [url]http://fogproject.org/wiki/index.php/FOG_on_a_MAC[/url]

Something similar can be done not just for Mac but for other platforms. The tricky bit will be to find a check that will reliably distinguish between those with EFI and those without…

Interesting… looking for a full dhcpd.conf on the web I found this: [url]http://fogproject.org/wiki/index.php/Using_your_FOG_server_to_backup_and_restore_Macintosh_computers[/url]

Does anyone know who wrote this?

@Junkhacker: Thanks for the link! I’ll read through it and add it to the wiki!

Let me explain: Your network card requests an IP via DHCP and loads the boot image over the network, first step done. Now iPXE has to detect your network card to be able to talk on the network and request things via TFTP and HTTP. This is where things go wrong I suppose. iPXE can either use native drivers (someone has to write a driver for each and every piece of hardware) or UNDI (see here for more information about this: [url]http://fogproject.org/wiki/index.php/IPXE[/url]). As far as I could find out this piece of hardware should actually be able to talk UNDI. The only native driver I could find in iPXE source code is smc9000 which seems to only support LAN91xx devices and it’s kind of old anyway.

And then there is another thing. BIOS vs. (U)EFI. As you already saw undionly.kpxe is not working for you. That’s only made for BIOS type PCs. You need to use .efi files OR you need to switch your elitepad to legacy BIOS mode (not 100% sure if this can be done, a quick search on the web mentioned something like this). iPXE support on BIOS is definitely a lot better than with EFI (see here: [url]http://ipxe.org/efi/vision[/url])! As you see there are a lot of combinations and it’s up to you to fiddle with those till you get it right. Although there is no garantee that it’ll work (see below) there is a high chance that you will learn a lot about all those things and hopefully will get it working too!!

With some of our EFI Macintoshs I had to compile my own patched version of iPXE to get it working. See here on how to build your own iPXE files: [url]http://fogproject.org/forum/threads/build-ipxe-from-source.10152/[/url]

Please follow this: [url]http://fogproject.org/wiki/index.php/FOG_on_a_MAC[/url]

I’ve got Mac OS X imaging up and running at our university! No USB sticks or CDROMs! I am working on the wiki as I find time to squeeze that in…

Any comments are highly appreciated!

Which Linux did you choose. And please let us know about the version too (e.g. Ubuntu 14.04).

Have you ever tried registering that (test) client by hand in the web interface? What happens then when you boot that client? Do you see “registered host” in the headline of the boot menu?? What if you schedule an upload task for this host then? Does it upload?

See here: [url]http://www.fogproject.org/wiki/index.php/SVN[/url]

I’d suggest setting up a test server first to see if this works for you before upgrading your production server…

As far as I can see on that video you are pretty close to get things working!! After bootup you see iPXE which loads, gets an IP address via DHCP and also loads the menu! Then it loads the linux kernel and initrd. Kind of weird that you don’t see any error messages but the menu again.
Could you please try downloading any kind of linux live CD (e.g. ubuntu) and try booting it, just to see how linux in general is running on your X200M. I found an article about someone installing linux on his X200M. Try following this to see if you can boot (not install!) ubuntu: [url]http://sajan.io/blog/asus-x200m-perfect-linux-ubuntu-xubunu-utility-laptop[/url]

[quote=“mkstreet, post: 43838, member: 24215”]At first, when I booted, the clients would find DHCP and load iPXE. However, after that load was done, there was about a 50-50 chance that it will go to the Fog PXE menu or an error message would flash by and it boots from the clients local disk.[/quote]
Would you be able to record this with a camera and re-play it in slow motion (or pause/play through) to get to see the error message?

It’s very interesting that with internet connection being hooked up still all clients seam to load iPXE because the DHCP server had to be involved to make this work already! Maybe it’s because the local FOG DHCP server is faster in that very first step…

To give you a little more insight on how this works (and what might be different in FOG 1.2.0):
[LIST]
[]PC boots up
[]BIOS is configured to boot from network so it sends a DHCP request (broadcast)
[]DHCP request is answered (including options for ‘next-server’ and ‘filename’)
[]PC loads boot image from tftp://<next-server>/<filename> (e.g. tftp://192.168.1.1/undionly.ipxe)
[]iPXE boot image is loaded and executed on the PC
[]iPXE sends another DHCP request to get an IP address (before being able to load things via HTTP, TFTP or other protocols)
[*]…
[/LIST]
I guess this is where things go wrong from time to time… In FOG 0.32 pxelinux was used instead of iPXE. As far as I could find out pxelinux does not request an IP from the DHCP server (because it is less capable of loading things).

Not sure if this helps!?

Before we can get any closer I guess we need to know which ethernet connector you use. Searching the web I found people using docking stations (e.g. C0M84AA) or ElitePad Ethernet Adapter or even USB hubs like LAN951x to add ethernet to their elite pad…

Please let us know about your ethernet adapter! Maybe even let us know about the PCI IDs found in windows device manager…

[quote=“Chadd, post: 43760, member: 28977”]Any updates on this? I’ve also been unable to get this going with Yoga S1’s and the same usb adapter, I’ve tried with a bunch of different kernels and no go. I’ve tried with the flag enabled which hasn’t made a difference I’ve attached a screenshot of the issue I’m having. If I just wait it ends up saying that there’s no network connection…[ATTACH]1781[/ATTACH][/quote]
From what I can see on that picture I’d say that iPXE is not an issue. Comes up and loads kernel and initrd. The kernel does not recognize the usb adapter I suppose. Which kernels have you tried?

Do you see any error messages in your apache server logs??

Well, that’s an interesting piece of hardware I reckon!! Reading the specs I found this:
[QUOTE]HW RAID functionality not supported by Linux. Use SW RAID functionality provided in the Red Hat Operating system instead.[/QUOTE]
Just guessing here but I think you installed linux using software RAID on those two disks! What do you see if you bootup that client (the one you uploaded the image from) and run the following command:
[CODE]sudo cat /proc/mdstat[/CODE]

I guess you’ll see RAID related information… software RAID. If PING was able to capture a backup from a software RAID FOG should be able to. AFAIK the kernel used is not compiled with RAID support included so you need to compile your own kernel to make this work! On top of that you might have to modify FOG a little bit to make it detect your RAID array when it comes up…

Start here: [url]http://fogproject.org/wiki/index.php?title=Building_a_Custom_Kernel[/url]

As far as I remember we changed a couple of things with extended partitions in SVN a few weeks ago. Switching between SVN an older versions could cause trouble I suppose…

Please run a debug session on the client you use to upload the image from, run the following command and copy paste all the output (including warnings and errors) you see:
[CODE]sfdisk -d[/CODE]