Quantcast
Viewing all 1484 articles
Browse latest View live
↧

Invalid image file (Burning iPXE to Intel NIC)

July 26, 2013, 3:33 pm
$
0
0
Hi!

After relocating my server, I got the brilliant idea that while it's down, I should update my iPXE flash on the Intel NIC, since the one I'm currently running is from 2011. Also, I wanted to replace the embedded script with a dynamic one loaded from a webserver.

Anyway, after 3 days of bashing my head against the wall, not being able to flash (burn) the latest iPXE to the NIC, I'm hoping someone here might have a few tips.

The issue I'm running into is that when I run BootUtil.exe with the following parameters:

bootutil -nic 1 -restoreimage -file 808610c9.rom

I get this error:

"Invalid image file 808610C9.ROM"

Now I've googled myself half to death, and did come over this thread. The thing about the size of the image file did ring a bell, and so I built a new one with less features, so that it's now at 61,440 bytes, which should be well below the 64KB limit. So I tried again, bit no luck. Still get the same error.

Then I tried using the older utility as suggested in the same thread, but that utility/version doesn't recognize my NIC (8086:10c9 - Intel 82576).

So I'm pretty much stuck now.

It's obviously possible to flash the 82576 with iPXE, as that's exactly what I have been using for the past couple of years, but I can't for the life of me remember how I did it, so again, any help or tips will be greatly appreciated!
↧
Search

When do I use .pxe, .kpxe, and .kkpxe?

July 27, 2013, 8:27 am
$
0
0
Hi!

When do I use .pxe, .kpxe, and .kkpxe?
↧
↧

Need Suggestions

July 27, 2013, 11:12 pm
$
0
0
Please suggest cheap/commodity($50-$75) motherboards with socket 1155 that has LAN on Motherboard that works with iPXE perfectly Out-of-Box.

We will be using Windows 8 or Windows Server 2012.

ASRock, Gigabyte, MSI, Intel, ECS, etc... Any brand would do, I just need this to work smoothly.

I have tried:
ASRock H61M-VG4 with Realtek RTL8111/8168
Failed. MAC becomes 00:00:00:00:00:00. Long loading time followed by blue screen then reboot.

Intel DH61BF with Realtek RTL8111/8168
Failed. MAC becomes 00:00:00:00:00:00. Long loading time followed by blue screen then reboot.

Intel DH61WW with Intel 82579V
Failed. Bus-id becomes 82579LM. Long loading time followed by blue screen then reboot.

Compaq CQ40 with Realtek LAN on MoBo
Failed. Long loading time followed by blue screen then reboot.

Tried chainloading undionly.kpxe; ipxe.pxe, ipxe.kpxe, ipxe.kkpxe with specific drivers for each LAN on Motherboard. Also tried bootable .iso.

All boards install perfectly using wimboot/WinPE method but fails to boot(sometimes they boot, most times they don't).

Using Windows Server 2012, MS DHCP, MS iSCSI Target, IIS8, and Solarwinds TFTP for server.

Code:
#!ipxe

:retry
dhcp || goto retry
set initiator-iqn iqn.2010-04.org.ipxe:computenode
set keep-san 1
set netX/gateway 0.0.0.0
sanboot iscsi:192.168.1.2::::iqn.1991-05.com.microsoft:server11-${ip}-target ||
module amd64/media/bootmgr                     bootmgr        ||
module amd64/media/Boot/BCD                    BCD        ||
module amd64/media/Boot/Fonts/segmono_boot.ttf segmono_boot.ttf    ||
module amd64/media/Boot/Fonts/segoe_slboot.ttf segoe_slboot.ttf    ||
module amd64/media/Boot/Fonts/wgl4_boot.ttf    wgl4_boot.ttf    ||
module amd64/media/Boot/boot.sdi               boot.sdi        ||
module amd64/media/sources/boot.wim            boot.wim        ||
chain wimboot || reboot

Thanks.
↧

Odd behavior running under Parallels

July 29, 2013, 6:56 am
$
0
0
All,

I'm seeing some general weirdness trying to use iPXE between VMs for testing. I could use some troubleshooting tips, particularly around what's happening under the hood during file download.

What I'm seeing:
With ipxe.iso, the initrd image will start to load, then hang. The point isn't consistent, but ranges from 65k to 150k into the file.
With pxelinux.0, the full 370k image will load and boot, but fail for other reasons.
With undionly.kpxe, the process never gets as far as starting the initrd step - it hangs while loading

What I'm wondering:
When the initrd command runs, does it download the whole file first, or does part of the downloaded image start executing partway through the download process? i.e., do I have a simple issue here with a download failing, or is it possible that code inside the image is causing the failure?


I'm running CentOS6.4 on MacOS 10.8.3 using Parallels 8.0.18494, and trying to replicate this boot scheme as a start:
http://blog.braastad.org/?p=332
The goal is to iPXE and run these commands:
dhcp
initrd http://example.com/initrd0.img
kernel http://example.com/vmlinuz0 initrd=/initrd0.img root=/centos64-pxe.iso rootfstype=auto rw liveimg toram size=4096
boot

What I've tried:
Booting from the ipxe.iso demo file, Ctrl-B, and manually entering the commands, trying both HTTP and TFTP as sources
Booting an ipxe.iso file from rom-o-matic with the above script embedded
Chain loading the above in undionly.kpxe form
Booting the image via pxelinux.0
Running tcpdump during the above, and analyzing with Wireshark


I'm suspecting some issue here between iPXE and the Parallels virtual NIC. Among the symptoms, when loading fails (e.g., TFTP timeout) the NIC goes dead - subsequent tries show no packets in tcpdump, and ifopen or dhcp won't work until the interface is ifclose'd first.

I've hit a wall trying to debug this. Any pointers would be appreciated.

Thanks,
Richard
↧

Intel Active Management

July 29, 2013, 8:53 am
↧
↧

Translating configs from pxelinux to iPXE

July 31, 2013, 2:22 am
$
0
0
I'm trying to translate a simple config from pxelinux into the proper iPXE syntax. At the moment, the test config isn't working with either one, so I'm not sure if I've translated things correctly.

Relative to my prior posts, I'm now dabbling with PXE booting CentOS 6.4 with an NFS-based root filesystem. Redhat offers a doc here with the relevant steps using pxelinux:
https://access.redhat.com/site/documenta...onfig.html

Here's the original tftpboot/pxelinux.cfg/default config, based on the URL above:
Code:
default foo

label foo
  kernel vmlinuz-2.6.33-358.14.1.el6.x86_64
  append initrd=initramfs-2.6.33-358.14.1.el6.x86_64.img root=nfs:169.254.1.100:/image rw
And this is the iPXE statement I translated it into:
Code:
kernel vmlinuz-2.6.33-358.14.1.el6.x86_64 initrd=initramfs-2.6.33-358.14.1.el6.x86_64.img root=nfs:169.254.1.100:/image rw
boot

Question is... is simply munging the two lines together the proper way to do this translation? Based on my other work here, this looks right.

Secondly, if anyone's done this before (booted Linux with an NFS-based root filesystem), can you critique the root= statement here? Either it's not being passed successfully, or I've formatted something wrong, because that seems to be my current hangup.

Thanks,
Richard
↧

Please help me. What do I need and how ipxe amount on a NAS DS212J?

July 31, 2013, 7:34 pm
$
0
0
I'm new to this and which do not understand almost nothing, so I turn to you to help me to implement a nas iPXE DS212J with DSM 4.2-3211.
I have read and seen several topics on the forum to try to understand but the truth is that I so dizzy info.

The intention of this is to make any network installations. Iso of the OS XP, 7.8, and images Distro linux OS installed with the ATIH 2012.

I tried to PXE, but did not know how to compile the default file pxeconfig.0.

I see iPXE is better, faster and without much roll.

Thank you.
↧

booting ipxe from pxelinux

August 1, 2013, 3:44 am
$
0
0
using pxelinux.0 (Version 4.04) I could boot ipxe in this way:

LABEL IPXE_shell
KERNEL /ipxe/IPXE.KRN ipxe command (eg. Shell)

using pxelinux (Version 6.01) this works no more
getting: "invalid argument" error.

same error occurs if I try

LABEL IPXE_shell
KERNEL /ipxe/IPXE.KRN
INITRD myscript.ipxe

Is there a workaround?
How to transfer a commandline to ipxe?
I perfer solutions without creating different configurations of ipxe because administration of versions is cumbersome.
pxelinux (v 5.x) I have never used
↧
Search

booting ipxe from pxelinux

August 1, 2013, 1:43 pm
$
0
0
booting ipxe from pxelinux (V4.04) worked fine in both variants

LABEL IPXE_command
KERNEL IPXE.LKRN ipxe_command

LABEL IPXE_initrd
KERNEL IPXE.LKRN
INITRD IPXE_initrd_file.ipxe

booting pxelinux (V6.01) both variants terminate with an error (invalid argument)

is there a workaround? How can I boot ipxe.lkrn and supply parameters without engaging dhcp or embed them in ipxe.
I try to avoid embedding commands in ipxe.lkrn because of additional administration efforts.
↧
↧

Computer hanging at iPXE initialising devices...

August 7, 2013, 7:45 am
$
0
0
On HP dc5000 computers iPXE hangs at "iPXE initialising devices..." whenever a build a non-standard PXE bootstrap loader image from rom-o-matic.eu

By "non-standard", I mean when I select the advanced mode on the rom-o-matic.eu website, select any PXE bootstrap loader image target (.pxe, .kpxe, .kkpxe, .kkkpxe) but leave all the other options at their default setting. If I select the undionly.kpxe standard build, the computer boots fine.

However, I need a .kkpxe image because I'm chainloading from PXELINUX and passing the boot script name with the cached DHCP response.

If I boot directly to ipxe.kkpxe (bypassing PXELINUX), the computer hangs the same way.
↧

Menu: password on an item

August 7, 2013, 8:21 am
$
0
0
Is there a way to put a password on an item in the menu?

If not, it would be a great feature to add!
↧

Suggested correction to ipxe forum faq

August 14, 2013, 12:35 pm
$
0
0
In robinsmidsrod's forum FAQ posting we see:

"How do I boot the Windows ISO from HTTP and install to an iSCSI volume?

Use wimboot to boot the files extracted from the Windows ISO."


This is certainly not the case for Vista x64 using sanhook to install via iscsi.

Even when:

1) the iscsi server is on a different subnet than, well, everything else except the router.
2) the sanhook reports 'ok' using chap with login username and password.
3) boot.ipxe is as described on the faq with all the content on an http server
4) for neither the pure x64 vista sp1 download nor the msdn disribution disc giving the choice of x32 or x64 sp1 and release version.
5) Latest ipxe (ipxe.dsk booted from a floppy by a vm with 2 cores and 2 processors, 1gb mem), latest wimboot.

The sypmtom is: No error messages for any of the ipxe process. Windows installer pops right up, asking for language and then giving the choice to 'install now'. After 'install now' 'please wait' appears for a few minutes, then it asks to browse for a missing driver. It gives no hint as to what driver it is that it is looking to find. The availble disks to browse are the blank ntfs partition via iscsi that was to be the install target (cImage may be NSFW.
Clik here to view. Smile, the floppy (AImage may be NSFW.
Clik here to view. Smile, and (XImage may be NSFW.
Clik here to view. Smile which is basically the whole of the tftp install directory. I tried a few directories hoping it would find the drivers it was looking for, but none ever appeared.

So, I'm suggesting the advice given on the FAQ "Use wimboot to boot the files extracted from the Windows ISO" is not accurate. Indeed it has cost me many hours of frustration.

I'm now going to try the "win pe" method, which I was hoping to avoid as Windows at present has no future beyond the legacy things given all the open source out there, as such I had no reason to go to the bother of installing all the extra machinery of Win PE.

Hope this post saves someone else my frustration. Harry
↧

IPXE Version

August 19, 2013, 1:51 pm
$
0
0
Hi,

I'm need to detect also the version of iPXE with 'avoid loop'. If the version is to old, call undionly.kpxe as another pxe rom.

if exists user-class and option user-class = "iPXE" {
filename "http://my.web.server/real_boot_script.php";
} else {
filename "undionly.kpxe";
}

Thanks for helps,
Regards,
Yannick
↧
↧

Boot winpe with ipxe

August 22, 2013, 1:36 pm
$
0
0
Hi.

I try to set up a ipxe to boot winpe with http. I have followed the "How to boot windows pe with http" guide, but I still cant get it to work.

I start ipxe by tftp server and it works fine. Then I break break the dhcp loop with ctrl-b. I get an ip-address by typing dhcp. But then the problem start.

My boot script is on my web server and I try to type:
chain http://bootserver/boot.ipxe or
boot http://bootserver/boot.ipxe

But all i get is:
http://bootserver/boot.ipxe... ok

And then nothing happens. I have tested in a web browser that I can open my bootscript. I have also tried to type in every command in my bootscript manually in ipxe and then it works.

I hope someone can help me. Thanks.
↧

Does WIMBOOT work with the current 'preview' editions of Windows PE?

August 27, 2013, 9:03 am
$
0
0
Just asking because I'm getting 'no embedded bootmgr.exe found' failures when using source files built from the Windows 8.1 Preview ADK.

If there's a way to add a new bootmgr.exe signature to look for, it would make me a very happy camper.

Of course, I could just be being a big bozo and missing something dumb, but this appears to be the problem.

I've uploaded the latest 'bootmgr' file _temporarily_ to my office dropbox so you can grab it and peek (or you could install the latest ADK, which is free for the taking from Microsoft).

https://dropbox.brown.edu/download.php?hash=94f70088
I just verified that the error goes away when I bump back down to Server 2012 sources (instead of 2012 R2 Preview). If you want to skip the 'preview' release, that's fine with me.
↧
Search

chain menu.c32

August 30, 2013, 10:23 am
$
0
0
Hi,

chain menu.c32 menu.cfg works with syslinux 3.x but not with higher versions.

Is the comboot compatibility broken between syslinux and ipxe ?

Regards,
Erwan
↧

iSCSI URI Bug?

August 25, 2013, 9:08 pm
$
0
0
Is there a LUN limitation on sanhook? Or is this a bug? I can hook any LUN between 0-9 but nothing higher than that.

Works: sanhook --drive 0x81 iscsi:192.168.77.23:::9:iqn.2013-08.chaos.olympia.local:hyperion-boot

Error: sanhook --drive 0x81 iscsi:192.168.77.23:::10:iqn.2013-08.chaos.olympia.local:hyperion-boot

Image may be NSFW.
Clik here to view. [Image: ipxe_error1.jpg]

On what could be a related note. I'm having trouble installing XenServer 6.2 using the --use_ibft switch.
The installer seems to detect the iBFT entry properly
Image may be NSFW.
Clik here to view. [Image: xen1.jpg]

But it seems to always want to add a 0 to the LUN when trying to mount.
Image may be NSFW.
Clik here to view. [Image: xen2.jpg]

Any help would be appreciated. Spent a whole day trying to figure this out with no progress.

Cheers,

Tom
↧
↧

SCCM WinPE task sequence failure

August 26, 2013, 12:58 am
$
0
0
Hi

I have followed this guide:
http://ipxe.org/howto/sccm

When it boots up the WinPE image it runs the sciprt and says enabled DNS service.
I can also choose a task sequence that I want to load.
No matter which task sequence I load it comes with an error:
Launch mode is not defined TSMBootstrap 23-08-2013 15:00:33 1568 (0x0620)

ThreadToResolveAndExecuteTaskSequence failed. Code(0x80004005)TSMBootstrap 23-08-2013 15:00:33 1568 (0x0620)

I would like to upload the whole sccm log file, but I cant attach .log or .txt files, what file types can I upload?
↧

Flashing RTL8111B/RTL8111C

September 2, 2013, 4:08 am
$
0
0
Hey.

Im trying to flash iPXE into a PCIe RTL8111B/RTL8111C. VEN DEV id is 10ec:8168. (integrated into a ASUS P6T SE Motherboard)

Have tried with numerious flash tools, RTFLASH.EXE, flashrom.exe etc.
None of them can see the card.

The RTFLASH.EXE one is pretty old, 2000 something. Anyone know where I can get a newer one?

Or does anyone know a way to flash the ROM?
↧

iPXE + WinPE + iscsi How-to

September 4, 2013, 8:19 am
$
0
0
Hello I want subscribe my short notes about installation Win7 to iscsi disk.

1.st Step - DHCP

I am using gentoo so I dont't have isc-dhcp-server like debian based users. I am using net-misc/dhcp-4.2.4_p2-r1. At first time I was scared about support iPxe in this DHCP but it works perfect with this configuration.

Code:
if exists user-class and option user-class = "iPXE" {
      filename "http://10.0.0.53/winpe/boot.ipxe";
  } else {
      filename "undionly.kpxe";
  }

2.nd Step - Tftp

Only one thing what I have to set after instal tftphpa was path so simply edit tftp config. (in gentoo /etc/conf.d/in.tftpd)

I will be using winpe so I had running apache.
Simply I add this line into tftp conifg and start it.

Code:
INTFTPD_PATH="/var/www/localhost/htdocs/winpe/"

3.rd Step - dnsmasq

after install I only add 1 line to dnsmasq.conf

Code:
dhcp-boot=undionly.kpxe,hostname,10.0.0.100

4.rd Step - Lvm + iscsi

I had to create some lv to install and add it to iscsi server.

Code:
lvcreate -L100G -n iscsiwinD_lv md1000-01VG

/etc/ietd.conf
Target iqn.2001-04.org.gentoo:win
        Lun 2 Path=/dev/md1000-01VG/iscsiwinD_lv,Type=fileio
/etc/initiators.allow
iqn.2001-04.org.gentoo:win ALL
restart ietd and this part is done.

5.th - Step Create winpe

on Pc where I had installed Windows 7 I download and install Windows AIK

In Deployment Tools Command Prompt I generate basic windowsPE.

Code:
mkdir C:\temp\winpe
  copype x86 C:\temp\winpe\x86
  copype amd64 C:\temp\winpe\amd64

If you need add drivers for ehernet check this manual

6.th Step - boot.ipxe

I use config from ipxe.org with one important thing.

Code:
#!ipxe
cpuid --ext 29 && set arch amd64 || set arch x86
set netX/gateway 10.0.0.100
[b]sanhook iscsi:10.0.0.100:::2:iqn.2001-04.org.gentoo:win[/b]
kernel wimboot
initrd ${arch}/ISO/bootmgr       bootmgr
initrd ${arch}/ISO/boot/bcd      BCD
initrd ${arch}/ISO/boot/boot.sdi boot.sdi
initrd ${arch}/winpe.wim         boot.wim
boot

set netX/gateway is only needed if your router is a bit messed up (doesn't route back to local network, or has slow network interfaces)

Most inportant thing in this fille is sanhook. You dont have to add some iscsi initiator to winpe like google whispers.

Now I am ready to boot WinPe.

After what is WinPe loaded I see command line so simply start setup.exe from samba sharing.

Code:
net use \\10.0.0.140\win7
  \\10.0.0.140\win7\setup.exe
(10.0.0.140 is my samba server)

And now I see 100G disk for install.

After was win7 installed I add this lines to dhcpd.conf

Code:
if exists user-class and option user-class = "iPXE" {
     filename "";
      option root-path "iscsi:10.0.0.100:::2:iqn.2001-04.org.gentoo:win";
  } else {
      filename "undionly.kpxe";
  }

And now I am able to boot win7 from network with Iscsi Image may be NSFW.
Clik here to view. Smile

Image may be NSFW.
Clik here to view. [Image: TBEp878.png?1]

If someone will need some hints just IRC freenode /msg |Nuclear|
↧
Viewing all 1484 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>