Posts made by mandrade

@Sebastian-Roth ,

I have tried the rom-omatic.eu guide to create a USB stick. When it boots it fails with "“could not connect to net0: input/output error”

I

@Wayne-Workman ,

So I found out that the OneLink+ mini dock required a Firmware update. I now get straight through to the boot menu but when I try an inventory it’goes to the bzImage and hangs at 0%.

I have take another dump and forwarded it to Sabastian hopefully now we will see what’s causing the problem.

@Wayne-Workman ,

So no dice either way. Tried manually registering the machine and also booting from the bootable USB following the wiki how to https://wiki.fogproject.org/wiki/index.php?title=USB_Bootable_Media. If I boot from the usb it just returns back to the boot menu. If I add the has_usb_nic=1 parameter it boots through to start imaging but hangs at loading the bzImage.

I tried another laptop different hardware of course, one that has an onboard NIC. This worked no problems booted straight and created images seamlessly. So more and more I think the problem here is how FOG handles the Onelink+ mini doc.

@Wayne-Workman ,

Right but in this case I would have to capture the Host manualy first right? Because, I cannot inventory the computer.

@Tom-Elliott ,

same result as when I run Intel.pxe

@Tom-Elliott ,

DHCP fails and I’m requested to pres ‘S’ to exit to iPXE shell. Probably worth the mention the machine is seeing the interface as a Realteck RTL8153 USB Ethernet Controller (xHCI) v2.00

USB, would FOG handle USB NIC’s differently perhaps?

@Wayne-Workman ,

Yep tried all the things Sebastian has posted. I was requested to send new tcpdump which I sent to the previously supplied e-mail address.

At this stage I am able to image all my workstations with exception of my Lenovo Thinkpad x1 Carbon machines which connect to the network via a OneLink+ mini docking station as they do not have an onboard NIC.

@Tom-Elliott ,

this is what happens if I boot from ipxe.pxe:

It just sits there and eventually reboots

@Tom-Elliott ,

I am indeed using a trunked version of FOG. There is no firewall, VLAN separation between the host and FOG. It does get an IP otherwise I would not be able to get to the menu to select an option am I right?

When I select inventory from the menu list it starts to attempt to load the bzImage but fails with connection timed out. All just very strange! I then run the same thing only this time on another host that has an onboard NIC and BOOM it works fine. So my take is that it’s something to do with the mini DOCK. Perhaps drivers? I dunno pure speculation from my part.

@Tom-Elliott ,

Thanks for the response Tom. Other workstations work fine, I am able to image them without issue. I did mention earlier that this setup is slightly different from the others in that this laptop doesn’t have an onboard NIC. It uses a OneLink+ mini dock. The thing is I can see it gets an IP from the DHCP server before it starts to the boot process. Somewhere along the line it loses it’s config somehow and then Fog server is no longer reachable.

@Sebastian-Roth ,

Hi, I had already sent a second TCPDUMP to the supplied e-mail. Let me know if you didn’t get it I’ll re-send if need be.

@Tom-Elliott ,

I meant the undionly.kkpxe boots past the ipxe boot screens and into the menus where I can inventory etc. The problem then comes when I make select a menu item like inventory for instance. The result you can see in the image below. I cannot inventory or take an image of this host using either undionly.kpxe or undionly.kkpxe only that the undionly.kkpxe gets further in the process.

@Sebastian-Roth said in Make new bzImage...:

ither generate a debugging enabled iPXE binar

I am able to type commands I type ‘S’ to be taken to the iPXE shell. So I ran ifstat, nstat and also tried to load the kernel. This was the result:

woops forgot to resize:

I tried renaming the bg.png file and it went further, only now it hangs here:


oh and for the record, for this machine ipxe will only boot up with undionly.kkpxe. If I use undionly.kpxe it hangs.

ok so removing line flush(); from /var/www/html/fog/service/ipxe/boot.php means now it no longer hangs at the bootp.php but now hangs at:

http://X.X.X.X/fog/service/ipxe/bg.png

@Tom-Elliott ,

Sure can try another machine but I think you may be right I think this may be an ipxe driver issue. I have also tried updating the BIOS version on the machine and that has made no difference. I’ve attempted to play around with the Network boot option also with no change.

I have the tcpdump here with me who could I send it to? e-mail address?

@Sebastian-Roth said in Make new bzImage...:

sudo tcpdump -i eth0 -w hang.pcap host

I have that tcdump for you, let me know where you would like me to send it to.

@Wayne-Workman ,

Tried both ipxe.kpxe and ipxe.kkpxe. Both times it hangs at:

“iPXE initializing devices”