IPXE Boot Issue with Realtek RTL8153

[Tom Elliott]

[url]http://mastacontrola.com/init.gz[/url]

This file is redesigned for what fix I did for the USB NIC’s.

Replace your current init.gz with that of this one here.

[code]sudo mv /tftpboot/fog/images/init.gz /tftpboot/fog/images/init_orig.gz[/code]
sudo wget [url]http://mastacontrola.com/init.gz[/url] -O /tftpboot/fog/images/init.gz[/code]

Words of Caution:

1. I haven’t tested if this will even work, but from what I can tell it will. You’ll likely need one of my kernel’s to ensure support of the drivers needed are already loaded in the kernel: bzImage32
   [code]sudo mv /tftpboot/fog/kernel/bzImage /tftpboot/fog/kernel/bzImage_orig
   sudo wget https://svn.code.sf.net/p/freeghost/code/trunk/packages/web/service/ipxe/bzImage32 -O /tftpboot/fog/kernel/bzImage[/code]

2. if you have customized the files in your init, you will need to port those in.

For your yoga’s, the kernel arguments for the host you’re working with needs has_usb_nic=1. That should do it.

[Sam Wennerlund]

struggling with this a bit, probably party because I’m more used to where things are in fog 0.32, am running a 1.2.0 now on Ubuntu.

Ive tryed different kernels from the FOG management website, official and latest unofficial.

Also have tried adding the host to FOG first and it still is stuck at “iPXE initialising devices”

[Jaymes Driver]

[quote=“Sam Wennerlund, post: 39423, member: 20713”]

Also have tried adding the host to FOG first and it still is stuck at “iPXE initialising devices”[/quote]

Have you tried the undionly.kkpxe
Have you tried the ipxe.kpxe
Have you tried the undionly.kpx.INTEL

I would recommend giving one of these a shot.

[Boyan Biandov]

FYI: undionly.kkpxe worked for me on HP Pro Book 4520s part WH333UT#ABA. I was getting the iPXE initializing stuck message with undionly.kpxe

[Wolfbane8653]

[url]http://fogproject.org/wiki/index.php/WorkingDevices#Computers[/url]: Updated adding HP Probook 4520s as a working device with Fog 1.x.x and the undionly.kkpxe ipxe file.

[Jonathan Hamill]

Hey guys, I’m glad I found this thread. I just wanted to add here that changing the ipxe file to undionly.kkpxe works on HP Mini 2102 netbooks which run this chipset (FOG on CentOS 6.6 and FOG 1.2.0).

[Boyan Biandov]

Good reminder; I also need to report that HP Pro Book 440 G2 requires the boot file changed to undionly.kkpxe

[nweakland]

Hello everyone.
I think I may have the same problem here with the new Lenovo Yogo 12 and the realtek 8153 USB-Ethernet NIC.
I get to
iPXE initialising devices…
and it hags there.
In reading this post, it seems that I need to update my undionly.kpxe to undionly.kkpxe.
My problem is I don’t even know what that means.
I am VERY VERY green to linux command line manipulation.
In fact, I was only able to get this working last year in the first place thanks to the wonderful patience and support from this community and Tom Elliott.
But I have been using this server flawlessly for that entire year.
I was able to update from 1.0.1 to 1.2.0 and then go do subversion to the newest. All of that seemed to go fine.
Can anyone please help with directions on how to change the .kpxe to .kkpxe?
Thanks in advance.

Oh, I have Ubuntu 14.04 LTS 64 bit OS
FOG 1.2
FOG web gui reads 3735

[Wayne Workman]

@nweakland

If Windows Server handles your DHCP, then likely, all you need to do is modify your DHCP IPv4 Scope option 067 to undionly.kkpxe

[nweakland]

Thank you Wayne, but my DHCP is handled by the FOG server.
It’s all one unit.
Would the same theory work?
Modify the local DHCP server? How would I do that?
Thanks

[Wayne Workman]

@nweakland It depends on the distribution. Normally it’s just a conf file you’d change. You’ll see where it says undionly.kpxe and you’d just add the extra k.

[Tom Elliott]

Edit the file /etc/dhcpd.conf and change the next-server to the IP address of your fog server.

Change the filename to the boot file you want loaded.

[nweakland]

Ok, After some more googling, I was able to find how to change to .kkpxe.
I did this:
sudo gedit /etc/dhcp/dhcp.conf
and changed it in there
after that I stopped and started the dhcp service.
That certainly helped becuase now I get past the “initialising devices” hang-up.
However, now it goes just a little farther and reboots.
the last thing in the screen I see is
init.xz…<OK>
then it reboots.
Can anyone point where to go next?
any key words I can google/search?
Thanks