Quantcast
Channel: iPXE discussion forum - All Forums
Viewing all 1484 articles
Browse latest View live
↧

IPXE Error (Unsupported NIC/Intel)

October 30, 2014, 4:04 am
$
0
0
Hi, guys.

Currently now using the last ipxe version, I am having this issue where the NIC can't be configured.

Would you know why ?

Sincerely,

Fred
Here is the screenshot :

[Image: i7F4kdWdLbYFV.png]
↧
Search

WimBoot - No Longer Works (2.3.0) - HP DL360p Gen8

November 2, 2014, 5:46 pm
$
0
0
Hi,

It seems the new revisions of HP 360p Gen8 being shipped lately, do not support wimboot anymore.

I've tried all versions and all them have issues, they show a RSOD with win2k8 or a blank screen with win2k12 (after it load the installation files, with the progress bar for both versions).

2K8 [RSOD]
[Image: ib1kBfGUnf0e1y.png]

The images are working 100% fine in other servers of the same family and even the same generation, the problem has started happening in the last units, shipped in the last 60-90 days.

Not sure what is causing that, but it seems to be related with a bios update they've made some months ago.

Sincerely,

Fred
↧
↧

Infoblox and iPXE

November 6, 2014, 3:01 pm
$
0
0
Has anyone experienced DHCP issues using iPXE with Infoblox? I have an Infoblox appliance where DHCP works perfectly for Etherboot and gPXE ROMs, but works only sporadically with iPXE ROMs. When using iPXE the DHCP configuration times out. A packet capture reveals the DHCP server is sending a response. Additionally, using a different DHCP service such as AIX's dhcpsd there are no issues with iPXE+DHCP. I have observed the behavior on Intel Pro 1000 (e1000e) and Intel i210 (igb) NICs. Any insight would be appreciated.

Thanks,
↧

make fails for snponly when CONSOLE_VESAFB

October 30, 2014, 11:31 am
$
0
0
Hi,

[LD] bin-x86_64-efi/snponly.efi.tmp
ld: bin-x86_64-efi/snponly.efi.tmp: hidden symbol `obj_vesafb' isn't defined
make: *** [bin-x86_64-efi/snponly.efi.tmp] Error 1

When I have the following in config/local/console.h
#define CONSOLE_VESAFB /* VESA framebuffer console */

undionly.kpxe and ipxe.lkrn still compile, so must be something related to 64bit.
↧

attach multiple san device

November 2, 2014, 9:43 pm
$
0
0
hi all~~

i'm struggling to attach multiple san device.

is there anybody to attach multiple san device successfully???

details of devices are
- first is device only installed windows 7
- second is device stored additional user data

my ipxe script is
#!ipxe
sanhook --drive 0x81 iscsi:192.168.0.200:tcp:3260:0:iqn.2001-04.com.example:storage.userdata
sleep 5
sanboot iscsi:192.168.0.200:tcp:3260:0:iqn.2001-04.com.example:storage.os

the result is that windows is booted up successfully, but the other device(user data) is not attached.

user data device is not appear in "iSCSI initiator" window.

have a nice day!
↧
↧

Booting Ubuntu 14.04 Live via iPXE on UEFI

November 3, 2014, 7:28 am
$
0
0
Hello,

I am having issues with booting the Ubuntu Live Image via iPXE on UEFI. I've tried two laptops, and they both kernel panic. What is weird, though, is that it boots fine inside VirtualBox, but not on actual UEFI.

Relevant Code (approximation):

kernel nfs://.../vmlinuz.efi
initrd nfs://.../initrd.lz
imgargs vmlinuz.efi initrd=initrd.lz netboot=nfs nfsroot=... boot=casper

I found about the need for initrd=initrd.name from somewhere in the forums, looks like it's a bug in kernels prior to 3.16 or so. Without it, not even VBox works. When removing it in fact, it produces the EXACT same kernel panic in VBox.

It sounds like adding that piece of text should have fixed everything, but it still appears broken when it comes to actual UEFI hardware.

Any ideas?
↧

Need of iPXE boot in VirtualBox using a ROM with HTTP support

November 7, 2014, 7:32 am
$
0
0
Hello.
I want to use iPXE to boot a VirtualBox's virtual machine using a ROM which can use HTTP protocol, but what I finally get is a ROM which can use TFTP and some more protocols, but no HTTP. I write you the steps I've done...I don't know what I'm missing:

1.-After fetching iPXE source code as usual (git clone git://git.ipxe.org/ipxe.git) I've commented the line #undef DOWNLOAD_PROTO_HTTP from ipxe/src/config/vbox/general.h hoping to activate HTTP protocol in my compiled ROM (why is HTTP deactivated by default in vbox specific configuration??!!). I've not seen this step anywhere, but I've done this using "common sense".

2.-Then I've made the compilation with the command: make CONFIG=vbox bin/8086100e.isarom ("8086100e" is the vendor_id of the default net card in VirtualBox, the Intel Pro/1000 MT Desktop)

3.-As seen in https://git.ipxe.org/ipxe.git/blob/HEAD:...ox/README, I've replaced the default rom of VirtualBox with my recently compiled one with the command: vboxmanage setextradata "MyVMName" VBoxInternal/Devices/pcbios/0/Config/LanBootRom /home/myusername/ipxe/src/bin/8086100e.isarom

And that's all: iPXE works but HTTP feature is missing, and I don't know why!! I really need it.

Thanks a lot.
Best regards

PD: I use last VirtualBox (4.3.18) in a Fedora 20 x86_64 host machine
↧

Chainloading iPXE (HTTP), does not work

November 9, 2014, 9:30 am
$
0
0
Hello,

I compiled an embed script as follows in order to chainload my initrd and kernel image:
[undefined=undefined]
#!ipxe

kernel linux bootfile=http://192.168.222.177/n/ fastboot initrd=initrd.gz
initrd initrd.gz
boot[/undefined]


Using binary "undionly.kpxe".

[undefined=undefined]make bin/undionly.kpxe EMBED=myscript.ipxe[/undefined]


Boot process starts (iPXE), but it loops endlessly until I press Ctrl +B.
If I type in manually dhcp followed by chain http://myURL everything WORKING FINE!

Where am I going wrong on this?
Dodgy

P.S. Thanks for such a great piece of software, I've been looking for a long time for such a solution! Smile
↧
Search

iPXE malforms DHCP option 77 UserClass Option

November 9, 2014, 10:17 pm
$
0
0
iPXE malforms DHCP option 77 (UserClass Option)


Hi all,

I'm just started to use the iPXE (really great project) on my UEFI machines (unfortunately without legacy mode) ast the UEFI PXE imlementation is buggy (on all devices I have seen so far - bootserver discovery doens't work). Anyway as I am using my own custom ProxyDHCP, in order to recognize where the Request came from, I'm goigng to use the option 77 as sugested, but it is actually malformed against RFC 3004.

The option is correctly encapsuled,
Code Len Value
+-----+-----+--------------------- . . . --+
| 77 | N | User Class Data ('Len' octets) |
+-----+-----+--------------------- . . . --+
but the content is worng..

UC_Len_i User_Class_Data_i
+--------+------------------------ . . . --+
| L_i | Opaque-Data ('UC_Len_i' octets) |
+--------+------------------------ . . . --+

What I have seen, instead to report the length (once again) it starts with ASCII "iPXE"..

Is there any "switch" or another way to get it comply with the RFC or it is intended not to do so?


Thanks a lot

Miro
↧
↧

UEFI Support

November 11, 2014, 1:10 pm
$
0
0
I'd like to ask regarding this ipxe-devel mailing post from Michael Brown, if there is any chance to get the undionly.efi signed.

I was trying to find something new about that but no luck..

I have unfortunately constrain, not allowing me te disable the stupid secure boot (I really didn't found until now good reason for it unless MS makes some $$ with it.)

Thanks a lot for any info.
↧

attach multiple san device

November 2, 2014, 11:09 pm
$
0
0
hi all~~

i'm struggling to attach multiple san device.

is there anybody to attach multiple san device successfully???

details of devices are
- first is device only installed windows 7
- second is device stored additional user data

my ipxe script is
#!ipxe
sanhook --drive 0x81 iscsi:192.168.0.200:tcp:3260:0:iqn.2001-04.com.example:storage.userdata
sleep 5
sanboot iscsi:192.168.0.200:tcp:3260:0:iqn.2001-04.com.example:storage.os

the result is that windows is booted up successfully, but the other device(user data) is not attached.

user data device is not appear in "iSCSI initiator" window.

have a nice day!
↧

Chainloading iPXE (HTTP), does not work

November 9, 2014, 9:27 am
$
0
0
Hello,

I compiled an embed script as follows in order to chainload my initrd and kernel image:
[undefined=undefined]
#!ipxe

kernel linux bootfile=http://192.168.222.177/n/ fastboot initrd=initrd.gz
initrd initrd.gz
boot[/undefined]


Using binary "undionly.kpxe".

[undefined=undefined]make bin/undionly.kpxe EMBED=myscript.ipxe[/undefined]


Boot process starts (iPXE), but it loops endlessly until I press Ctrl +B.
If I type in manually dhcp followed by chain http://myURL everything WORKING FINE!

Where am I going wrong on this?
Dodgy

P.S. Thanks for such a great piece of software, I've been looking for a long time for such a solution! Smile
↧

iPXE malforms DHCP option 77 (UserClass Option)

November 9, 2014, 9:59 pm
$
0
0
Hi all,

I'm just started to use the iPXE (really great project) on my UEFI machines (unfortunately without legacy mode) ast the UEFI PXE imlementation is buggy (on all devices I have seen so far - bootserver discovery doens't work). Anyway as I am using my own custom ProxyDHCP, in order to recognize where the Request came from, I'm goigng to use the option 77 as sugested, but it is actually malformed against RFC 3004.

The option is correctly encapsuled,
Code Len Value
+-----+-----+--------------------- . . . --+
| 77 | N | User Class Data ('Len' octets) |
+-----+-----+--------------------- . . . --+
but the content is worng..

UC_Len_i User_Class_Data_i
+--------+------------------------ . . . --+
| L_i | Opaque-Data ('UC_Len_i' octets) |
+--------+------------------------ . . . --+

What I have seen, instead to report the length (once again) it starts with ASCII "iPXE"..

Is there any "switch" or another way to get it comply with the RFC or it is intended not to do so?

Thanks a lot

Miro
↧
↧

ipxe failover to USB not working

November 10, 2014, 8:12 am
$
0
0
Hi,
I made a USB stick of Windows 7 Pro. I am using ASUS z87m motherboard. It is OK to boot the USB as the first booting device both SATA or EFI. It is OK to failover to boot the DVD as the second booting device when I boot from IPXE blank iscsi volume. But when I set up the USB as the second booting device and hoping to failover to the USB, I am failed. Some please help me. I need boot from USB instead of DVD.

Thanks!

Mike
↧

Boot multi client

November 12, 2014, 1:35 am
$
0
0
Hi All
I try to build a system boot 20 client's by windows server 2008 r2
but it cannot connect iscsi target (iSCSITarget MCR 3.3)
+ IP server:192.168.2.200
+ iscsi target IQN : iqn.1991-05.com.microsoft:win-u0tje9eaisj-iscsiserver-target
This is my script

#!ipxe
dhcp net0
set initiator-iqn 1
set root-path iscsi:192.168.2.200::::iqn.1991-05.com.microsoft:win-u0tje9eaisj-iscsiserver-target
set keep-san 1

This video client boot
http://youtu.be/JDvEQdOBNvs

i don't what's it please help me
↧
Search

iSCSI digest support (CRC32C)

November 14, 2014, 4:52 pm
$
0
0
Hi!

I'm trying to figure out if iPXE supports iSCSI header and/or data digest (CRC32C)?

Looking at the source code, it doesn't seem like it:

/src/net/tcp/iscsi.c
Code:
634 /**
635  * Build iSCSI login request strings
636  *
637  * @v iscsi             iSCSI session
638  *
639  * These are the initial set of strings sent in the first login
640  * request PDU.  We want the following settings:
641  *
642  *     HeaderDigest=None
643  *     DataDigest=None
644  *     MaxConnections is irrelevant; we make only one connection anyway [4]
645  *     InitialR2T=Yes [1]
646  *     ImmediateData is irrelevant; we never send immediate data [4]
647  *     MaxRecvDataSegmentLength=8192 (default; we don't care) [3]
648  *     MaxBurstLength=262144 (default; we don't care) [3]
649  *     FirstBurstLength=262144 (default; we don't care)
650  *     DefaultTime2Wait=0 [2]
651  *     DefaultTime2Retain=0 [2]
652  *     MaxOutstandingR2T=1
653  *     DataPDUInOrder=Yes
654  *     DataSequenceInOrder=Yes
655  *     ErrorRecoveryLevel=0
.
.
.
723         if ( iscsi->status & ISCSI_STATUS_STRINGS_OPERATIONAL ) {
724                 used += ssnprintf ( data + used, len - used,
725                                     "HeaderDigest=None%c"
726                                     "DataDigest=None%c"

Line 725 and 726 seem to hardcode "None" as the available digest methods, which in turn is the likely cause to generate the following error on my iSCSI box:

Code:
[2414549.983174] Proposer's value list "None" contains no valid values from Acceptor's value list "CRC32C".
[2414549.984696] iSCSI Login negotiation failed.

I see in the SCST mirror that is hosted on the git repository that it implements CRC32C support, though I'm unsure if this has been implemented in iPXE in any way?

Hope someone can shed some light on this. Thanks! =)

EDIT: The iPXE error that was returned after I enabled the digest settings on the iSCSI box: http://ipxe.org/err/410d61
↧

iMAC with BMC57766 tg3 driver issues

October 16, 2014, 2:11 am
$
0
0
Hi,

We have iMACs with Broadcom BCM57766 cards [14e4-1686] unsupported (no entry in tg3.c table). I added a entry in tg3.c table and re-compile ipxe.
Link status tests passed but "dhcp" command reports Error 0x040ee119.
Then I tried to configure iMAC network adapter manually:

ipxe>set net0/ip 10.10.73.125
ipxe>set net0/netmask 255.255.255.0
ipxe>set net0/gateway 10.10.73.1

Ping from DHCP server to iMAC failed.

It seems a issue with de tg3 driver. Are there plans to support this card?

Thanks in advance.
↧
↧

Network unavailable AFTER pxe boot

November 27, 2014, 11:18 pm
$
0
0
Hi,
Since i Switched to UEFI PC, I've no network in any form of ipxe boot (wimboot,sanboot,iso...).
I can boot to ipxe fine using legacy bios, After the system load (winPE for example), network can't initialized. It's just like i don't have a NIC.
Please advice.
Jack
↧

No disks when booting windows 7 setup (x86/x64) from an iSCSI target

November 22, 2014, 1:15 am
$
0
0
I'm trying to run the windows setup from an iSCSI target, the target is a NTFS with all the files from the ISO file just like a bootable usb stick.
Booting the setup works fine (but stays very long at the "Stating Windows" screen) with virtualbox but there are no disks available to install on.

OpenWRT (DHCP) > server.lan (debian, tftp, iscsi) > iPXE (undionly.kpxe) > Windows setup

ietd.conf
Code:
Target iqn.2014-11.lan.server:windows_7_sp1_en_x86
    Lun 0 Path=/srv/iscsi/windows_7_sp1_en_x86.iscsi,Type=fileio,IOMode=ro

Target iqn.2014-11.lan.server:windows_7_sp1_en_x64
    Lun 0 Path=/srv/iscsi/windows_7_sp1_en_x64.iscsi,Type=fileio,IOMode=ro

iPXE
Code:
:w7x86
set netX/gateway ${iscsi-server}
sanhook ${iscsi-url}:iqn.2014-11.lan.server:windows_7_sp1_en_x86 || goto failed
sanboot --no-describe

:w7x64
set netX/gateway ${iscsi-server}
sanhook ${iscsi-url}:iqn.2014-11.lan.server:windows_7_sp1_en_x64 || goto failed
sanboot --no-describe

This is the error I get
http://www.mediafire.com/view/x3owbwk6q7..._disks.png

What is the right way to boot the setup from an iSCSI target?
↧

Attaching more than 1 san target

November 24, 2014, 4:29 am
$
0
0
Hi All

My first post, be gentle ..

Ive successfully installed 3 diskless clients using Win 7 and AoEDsk (which is quite a bit better than the original AoE Driver from a performance perspective). The main disks are hosted on LVM Raid 5 (mdadm) volumesand the PXE environment is tftpd-hpa and isc-dhcp-server on a Debian Wheezy server, which is chainloading iPXE via PXE.

At this point Im presenting a single LVM volume as a single drive to the initiator, which works flawlessly. I have recently got my hands on a rather small (64GB) ssd, which Id like to present as a purely swap volume, to maximize the performance if a machine is swapping. Currently the swap files exist as a regular swap file on the main volume and I have no real performance issues, but you know how it is, if you can make it snappier, you basically do try ..

So this leaves me in a predicament.. I cannot "late bind" the swap to a voluem I can present in the startup scripts in Win 7.. so the most logical solution is to present the swap as a second drive to the OS at iPXE boot level, so that the OS is aware of its existence .. but for some reason this is not working ...

Ive noted a similar (although iScsi) post here http://forum.ipxe.org/showthread.php?tid=7518, but it has had no response .. from what I gather in the iPXE Documentation on the sanhook command, there should be support for multiple targets, but only 1 is allowed to boot from.

From what Im picking up, it appears as though in order to recognize the drive, it requires an iBFT entry, and apparently this functionality only exists for iSCSI multipathing, but any other drives are avialable by int13 (??) ..

Does anyone have any idea, or input around either another workaround for my issues, or a way to attach multiple targets early enough in the boot sequence to allow successfull boots ??

Cheers

Jet
↧
Viewing all 1484 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>