Posts made by RipAU

I’ve found I have the same issue when installing as a FOG Storage Node onto Fedora 22.

Last message in the error log is “package dhcp is not installed”

Cheers,

I for the life of me cannot get the kkpxe or kpxe working at all. Chainloading the ipxe.krn also doesn’t help because as you said I don’t think the drivers are working for my particular Lenovo dongles.
I’m currently going to test clonezilla. Kind of frustrating as pxelinux.0 works perfect
At this stage I haven’t even thought about how to add a serial cable to debug it as I need to roll these devices out very shortly and I am dreading using SCCM as it is so slow.

Thanks again.

Just to let you know what I’ve found is that after building another ipxe.kkpxe and building in the console break command e.g.
[CODE]prompt --key 0x02 --timeout 1000 Press Ctrl-B for the iPXE command line… && shell ||
[/CODE] I’m finding that the driver doesn’t even seem to be loading at all which would obviously cause an issue
I’ll keep poking around.

Just got a little further thanks. Now switched my bench over to booting ipxe with default fog settings. And this works on our Dells. I’m using the [url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/tftp/ipxe.kkpxe[/url].
Works fine on my dell laptops loading the fog menu perfectly.

I’ll have a read through those again. As it seems to just be fairly complex supporting USB Ethernet devices.
Just wondering what the difference between my Yoga/ethernet device is and others that seem to have it working?
If I figure it out I’ll let you know

Thanks again.

This is where it freezes now by the way:
[IMG]https://i.imgur.com/troml9O.jpg[/IMG]

Same thing, just did a build with debug on xHCI and it spews out alot of red text but doesn’t seem to report anything.
iPXE is reporting the network is unreachable when doing a debug with dhcp,tftp,http
it doesn’t report anything else but again the screen goes instantly blank after it reports network unreachable.

So this is what leads me to think the driver isn’t loading correctly for the lenovo USB3 Ethernet adapter.

I was using the latest version of iPXE that I built on my fog server previously as well as ones from Rom-o-matic
I’m not sure it even has anything to do with FOG yet as it seems to go blank before it even loads a DHCP address.

I’ve tried chainloading from pxelinux which works for all of our other laptops but this leaves me with the same blank screen.
I’ve also used the ipxe.krn from [url]https://mastacontrola.com/ipxe/latest/[/url]

I’ll try building with debug and testing.

Hi, everyone.

I’ve read through a few other posts and thought I should create a new thread. ([url]http://fogproject.org/forum/threads/ipxe-boot-issue-with-realtek-rtl8153.10507/[/url])

I’m having issues getting iPXE to load only on the Yoga 12.5 with the USB dongles that Lenovo supplied (USB RTL8153) I’m finding that iPXE displays a blank screen as soon as iPXE loads and says iPXE initializing devices and the screen goes blank. All the other laptops are working fine, just this Yoga.

Some background: I no longer have DNSMasq working due to our over arching education switching over to the new version of Windows Deployment services and using Proxy DHCP no longer lets network boot on our main network. So I have resorted to using a USB key with iPXE when using the normal network.

Our Imaging station in the office has a second network setup for PXE booting but even trying with this displays a blank screen as soon as iPXE displays iPXE initializing devices .

I even tried booting iPXE with USB with no USB network adapter plugged in and I am getting the same blank screen.

I’m just wondering if anyone else has had this happen? or might know any bios settings I will need to change.

SecureBoot is disabled
and legacy boot is enabled.

Cheers,

After testing this for about an hour and downloading every file but the default.ipxe I worked out it was the client.
I tried this on several machines with the same error tested it with a different client and it works fine.

I thought I was on to something but I’m still getting the original error 0x3d126001 (Error: Inappropriate I/O control operation)

Hi guys,

Ok, I find this an odd issue that I cannot work out.
This has been going on since I installed fog but I did get a work around going using pxelinux (temp fix)

What seems to be happening is that the tftp-server does not want to allow downloading of the default.ipxe file.
SELinux and iptables are disabled so that isn’t the issue.

When trying to download the default.ipxe file I am seeing the error (/var/log/messages)

[CODE]in.tftpd[18556]: tftpd: read(ack): Connection refused[/CODE]

What is odd is if I move the /tftpboot/default.ipxe file to /tftpboot/default or /tftpboot/default.txt or /tftpboot/default.ipxe.0 I can download the file at the new location. if I create a new file called default.ipxe I cannot download this new file, if I move it to another location I can download it fine. Permissions are all correct as far as I can tell.

Not sure if this is a bug with tftpserver or some other issue I cannot work out.

I’d rather get this fixed so when doing fog upgrades I can update without having to move my fixes back into place.

Cheers,

I figured it would go into a loop trying to boot iPXE as DNS masq was turned on which was configured to pxeboot iPXE.
Autoboot seems to ignore iPXE and boot WDS even with dnsmasq turned on.

it works.
I didn’t think it would be as simple as that. Thanks

Also as a follow up, when going into the iPXE shell and running Autoboot for the WDS it works correctly.
Just when trying to run the commands imgfetch, imgload or imgexec.
So I’m not sure where I’m going wrong?

I’m wondering if it has got to do with mixed mode? I honestly don’t know enough about Windows DHCP servers as I have never had to manage them before.

I found this that might be related?
[url]http://social.technet.microsoft.com/Forums/windows/en-US/ff41bfb9-799e-40ea-b5ef-4cdd319dba71/wds-mixed-mode-problems?forum=itprovistadeployment[/url]

I have been finding that I can attempt to download the files manually from a tftpclient on my computer but reports that it couldn’t write the file and reports a random port number from the windows server.
I have tested downloading from my Linux TFTP server with no problems at all.

Yep tried all of them, same issue it just sits there with a blinking dos style dash and hangs.

@Tom Elliott - Firewall on the server? I don’t think that is an issue as I can boot to the WDS correctly when not using dnsmasq/ipxe

@Junkhacker - I’ve read that but from what I understand that is just installing winpe onto my own server and not chain loading an existing one? I don’t have access to any of the Windows files on the existing WDS server or the default Windows Images that it creates.

Cheers,

Hi Everyone,

Just wondering if anyone has tried chainbooting Windows WDS?
Would be nice to get FOG and WDS sitting next to each other with iPXE lording over the netboot process.

I’ve tried to boot the Windows file from the Windows TFTP server tftp://10.0.0.100/boot/x64/pxeboot.com
but it just reports with the default iPXE message cannot boot.

Would this be possible at all?

Thanks again,

Hi guys,

I’m wondering if anyone has had trouble or used the Intel Rapid Restore Technology built into the Bios of some Dell Laptops (I’m sure it is in others but I haven’t used them).

I’m finding when using the Exit to Hard Drive Type in FOG (SAN, Grub, etc.) - The computer hangs when trying to exit the network menu to the Hard drive when the Intel Raid On (Intel Rapid Restore Technology) is switched on.
When switching modes to AHCI or ATA it works as expected.
Normally I would switch it but the entire fleet was preloaded with this configuration.

Also when testing with grub it cannot find any hard drives at all when this is switched on.

Cheers,

I was thinking about this the other day,
Would this be something that could be done with PHP and iPXE using the ${product} field from iPXE?

e.g.

if the ${product} = OptiPlex 755
That way if we have problem PC’s that have a known product ID we can manually issue them a kernel over the default one.

Cheers,

Hi Guys,

After successfully updating to Fog 1.1.2 I am finding the Progress bar in Active Tasks isn’t showing data.
It worked previously in Fog 1.1.1, I have checked the Http error logs and can’t see any errors.

Would there be a better place to look for errors?

Cheers,

Ahhh yep, fixing up the root password and localhost fixed the issue.
I was confused as it seemed to work perfect the way it was on previous installations.

Thank you very much. I’ll start the upgrade on my storage nodes now as well.

I’m not sure what you mean by fix?

I tested the following and am still getting the error:

[CODE]ipaddress=“10.0.0.254”;
interface=“eth0”;
routeraddress=“”;
plainrouter=“”;
dnsaddress=“”;
dnsbootimage=“”;
password=“password”;
osid=“1”;
osname=“Redhat”;
dodhcp=“n”;
bldhcp=“0”;
installtype=“N”;
snmysqluser=“”
snmysqlpass=“password”;
snmysqlhost=“”;
installlang=“0”;
donate=“0”;
fogupdateloaded=“1”
[/CODE]

So I am guessing that isn’t correct?

Cheers,