Realtek 8111\8168 & undionly.kpxe -> hangs on Initialising Devices...

[Andy Abplanalp]

This dirty hack in my default.ipxe file seemed to do the trick:

#!ipxe
cpuid --ext 29 && set arch x86_64 || set arch i386
isset ${net1/mac} && chain [url]http://10.0.0.50/fog/service/ipxe/boot.php?mac=${net1/mac}[/url] ||
params
param mac ${net0/mac}
param arch ${arch}
chain [url]http://10.0.0.50/fog/service/ipxe/boot.php##params[/url]

[Tom Elliott]

Why are you sending net1 instead of net0, are you booting from another nic, or is ipxe booting from another nic?

[Andy Abplanalp]

ipxe.kpxe (and undionly.kpxe for that matter) is identifying the wireless NIC as net0. I had to get to net1 somehow.

[Junkhacker]

fyi, you can associate more then one MAC address with a host.
add additional MACs to a host on the host management page for that host.

[Andy Abplanalp]

Thanks. All these years using FOG and I’d completely forgotten about that feature.

[Baite]

[quote=“tamatech, post: 26861, member: 24111”]Tom,

I recompiled a new undionly.kpxe using this site: rom-o-matic.eu and with help from these forums on chainloading default.ipxe, I was able to upload an image into FOG 1.0.0.

Is there a way to remove (or reduce) the 60 second wait time on the “i2c-parport-light adapter type unspecified” message before the kernel is finally loaded?

Embedded script:#!ipxe
dhcp
chain default.ipxe

Thanks again,

Andy[/quote]
Tamatech:

Could you please be gentle enough to show how you did it (or share your working undionly.pxe)?

[Andy Abplanalp]

Baite:

Here’s my ipxe.kpxe.

Andy

[url=“/_imported_xf_attachments/0/843_ipxe.zip?:”]ipxe.zip[/url]

[Tom Elliott]

[quote=“Baite, post: 28277, member: 24308”]Tamatech:

Could you please be gentle enough to show how you did it (or share your working undionly.pxe)?[/quote]

You can also use any of the ipxe.*pxe files in trunk and this should work for you as well as it’s basically the same.

[Baite]

[quote=“tamatech, post: 28445, member: 24111”]Baite:

Here’s my ipxe.kpxe.

Andy[/quote]
Thank you, Tamatech

[Baite]

[quote=“Tom Elliott, post: 28446, member: 7271”]You can also use any of the ipxe.*pxe files in trunk and this should work for you as well as it’s basically the same.[/quote]
Thank you, Tom.

[Baite]

[quote=“Tom Elliott, post: 28446, member: 7271”]You can also use any of the ipxe.*pxe files in trunk and this should work for you as well as it’s basically the same.[/quote]
For me to use any of those files, I just need to replace the undionly.kpxe file with that one, right?

[Tom Elliott]

Yes, and replace it AS the undionly.kpxe

[andjjru]

After much trial and error, this one is working well for me.
[url]http://mastacontrola.com/ipxe/f3d42-QUOTA_20-GOOD/undionly.kkpxe[/url]

[Jaymes Driver]

[quote=“andjjru, post: 28706, member: 575”]After much trial and error, this one is working well for me.
[url]http://mastacontrola.com/ipxe/f3d42-QUOTA_20-GOOD/undionly.kkpxe[/url][/quote]

Ohh yes that does seem to be a good file, my machines like that and so do my virtual machines as long as the exit method is set to “exit” and not sanboot.

[andjjru]

I’m in the unfortunate situation of having a lot of important computers out there that require sanboot to continue to boot to hard drive, as well as a lot of important Dell laptops with IRRT enabled that need the opposite.

Rock, hard place, etc.

[andjjru]

This post is deleted!

[Tom Elliott]

[quote=“andjjru, post: 28728, member: 575”]I’m in the unfortunate situation of having a lot of important computers out there that require sanboot to continue to boot to hard drive, as well as a lot of important Dell laptops with IRRT enabled that need the opposite.

Rock, hard place, etc.[/quote]

If I had a solid knowledge of exactly which systems like (and/or) dislike a specific type, I could programmatically make this a non-issue. In your particular case, is there a specific model that requires certain types?

Maybe we can get a listing of Systems and their preferred method of exiting to the hard drive?

[andjjru]

[quote=“Tom Elliott, post: 28793, member: 7271”]If I had a solid knowledge of exactly which systems like (and/or) dislike a specific type, I could programmatically make this a non-issue. In your particular case, is there a specific model that requires certain types?

Maybe we can get a listing of Systems and their preferred method of exiting to the hard drive?[/quote]

I know for sure that the Dell Optiplex 390 prefers sanboot, and a bunch of Dell Latitudes (E5540, E5520, E6510, probably more) that have IRRT turned on by default prefer exit-style. Those Latitude models are fine with sanboot if their SATA type had been switched to AHCI or ATA prior to imaging, but not all of our techs had been doing that.

[Junkhacker]

last night, tom added a new feature to the development release of fog. if you install the svn version of fog, you will find a new option of “grub” for exit type. that will load the grub4dos boot-loader, which is known to exit cleanly on a wide variety of systems, and boot to hard disk.

[andjjru]

Thanks guys! I’ll check into that on Monday.