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

Intel pxe -> iPXE = dhcp fail

May 25, 2016, 2:22 pm
$
0
0
I've been trying to chainload iPXE from pxelinux.0, initially I had lots off random issues with ESXi virutal machines but after setting up dhcp reservations my problems went away.

Now trying to install Debian on my laptop, over http by chain loading iPXE over TFTP and then booting the Debian iPXE script. My onboard Intel PXE rom loads pxelinux.0 and chainloads iPXE.lkrn. But when iPXE starts up I'm unnable to automatically obtain a DHCP lease. And the MAC address is set up with a reserved address which sorted all my troubles with virtual machines.

Below is the DHCP trafic as captured on the virtual OpenWRT router running dnsmasq 2.55. (pcap file is available here)

Intel PXE
Code:
1   0.000000    0.0.0.0     255.255.255.255  DHCP  590  DHCP Discover - Transaction ID 0x54a05c60
2   0.000529    10.10.0.1   255.255.255.255  DHCP  365  DHCP Offer    - Transaction ID 0x54a05c60
3   4.000158    0.0.0.0     255.255.255.255  DHCP  590  DHCP Request  - Transaction ID 0x54a05c60
4   4.001254    10.10.0.1   255.255.255.255  DHCP  365  DHCP ACK      - Transaction ID 0x54a05c60
iPXE
Code:
5   108.443783  0.0.0.0     255.255.255.255  DHCP  441  DHCP Discover - Transaction ID 0xff8a5477
6   108.444831  10.10.0.1   10.10.0.220      DHCP  365  DHCP Offer    - Transaction ID 0xff8a5477
7   109.402196  0.0.0.0     255.255.255.255  DHCP  441  DHCP Discover - Transaction ID 0xff8a5477
8   109.402664  10.10.0.1   10.10.0.220      DHCP  365  DHCP Offer    - Transaction ID 0xff8a5477
9   111.379510  0.0.0.0     255.255.255.255  DHCP  453  DHCP Request  - Transaction ID 0xff8a5477
10  111.380543  10.10.0.1   10.10.0.220      DHCP  365  DHCP ACK      - Transaction ID 0xff8a5477
Manual ifopen + dhcp
Code:
11  181.486911  0.0.0.0     255.255.255.255  DHCP  352  DHCP Request  - Transaction ID 0x8c3a7101
12  181.488076  10.10.0.1   255.255.255.255  DHCP  359  DHCP ACK      - Transaction ID 0x8c3a7101
13  184.926221  10.10.0.220 255.255.255.255  DHCP  342  DHCP Inform   - Transaction ID 0x64026297
14  184.926700  10.10.0.1   10.10.0.220      DHCP  342  DHCP ACK      - Transaction ID 0x64026297

iPXE output:
Code:
Loading ipxe.krn...ready
iPXE initialising devices...ok


iPCE 1.0.0+ (a588) -- Open Source Network Boot Firmware -- http://ipxe.org
Features: DNS HTTP iSCSI TFTP SRP AoE ELF MBOOT PXE bzImage Menu PXEXT
Waiting for link up on net0 ................ Down (http://ipxe.org/38086101
iPXE>

To me it seems like iPXE is getting the DHCP offers, and actually ACK'ing it before giving up, and retrying manually afterwards works fine; yet it fails every time when selecting the menu entry from pxelinux.0

menu entry;
Code:
label iPXE-deblive
        menu label iPXE ^deb live
        kernel ipxe.krn dhcp && chain http://10.10.0.100:8001/boot/jessie-live.ipxe || shell

Suggestions on what to try where? Which debug flags to build iPXE with?
↧
Search

how to do host lookups

June 1, 2016, 6:50 am
$
0
0
Hi,

I am using a particular open source virtualisation platform, which has ipxe as the PXE implementation. In our kickstart menu (which is php), we need to do a hostname lookup to choose the appropriate local server as there are different boot servers in different global locations. Currently, on our other closed-source virtualisation platforms it is done via 'nslookup' when pxebooting. The nslookup command has not been compiled into ipxe on the open source virtualisation platform. I have requested that they add it. I could replace their ipxe rom with my own, but I thought I'd explore a different way of doing this. I've tried:

<?php $ip = gethostbyname('wds'); ?>
set wds <?php echo $ip; ?>
set net0/next-server ${wds}

However, this does not work. The lookup is successful when I use the 'show' command to print it, but it doesn't seem to get read into the variable properly. Any ideas? Or is there another way of getting this functionality?

Thanks,

Cam
↧
↧

I'm new to iPXE in general - How to get started with a Thinkpad T61?

May 29, 2016, 3:09 pm
$
0
0
Hello :-)

I'm a javascript developer who knows nodejs too and I never ventured into PXE or anything similar yet.

The only time I wish I'd get in touch with the topic is aprox. once a year, when I get a new laptop or I want to install everything from scratch on my current laptop for various reasons, because to install an operating system and set everything up the way I want, including:
OS installation guided by the usual wizard, deinstall some pre-installed programs, install other programs that i need, copy over configuration files, adapt some configuration manually, and finally copy over my data. This process usually takes me a weekend to tweak everything so that it suite me.

I'd love to automate the procedure completely.

After a long time of research I figured, that iPXE could help me to automate all of this.
I read a Thinkpad T61 doesnt support PXE Boot, but I also read it's not needed for iPXE.

MY QUESTIONS:
  • What should I read?
  • Are there some good text or video tutorials?
  • Do I need a FOG Server?
  • Can I write my own server? (I found nodejs packages that help with creating chcp/tftp/etc.. servers)
  • What are the websites "netboot.xyz" and "networkboot.org" about?
  • Do I need to buy and create a special USB Stick that I can stick into my Thinkpad T61 to be able to iPXE boot it? (and if so, what would be a good one to buy and where - link appreciated)
↧

imgfetch stuck mid-download

May 30, 2016, 2:11 am
$
0
0
Hi,

I'm a netboot rookie and I'm using iPXE version "aa4b0", in BIOS mode generally ipxe.pxe (more on that later).
First, I've wanted two things to work: Memtest86 and WinPE(10) with EFI and BIOS mode.
EFI mode is working OK, both stuff. (Memtest86 version is Memtest86 7.0.0 Beta 1 -- I cannot get it to use supplied mt86.cfg, but I think it's a Memtest86 bug).

Now the BIOS mode.
I want to use Memtest86 4.3.7 (NOT Memtest86+ 5.0.1).
If I just chainload it from iPXE, it fails with known error 460381.
Going the longer way (iPXE -> pxelinux 6.03 -> memtest) it's working:

set filename lpxelinux.0
set next-server 192.168.x.y # same server
set root-path http://<local http server address>/
chain ${root-path}${filename}

Done. Going for WinPE by the book (latest wimboot), so there are a couple of imgfetch calls.
Sometimes it works, but more often it gets stuck in the middle of a download (sometimes it happens in the middle of a font file, other times it's the .wim file). It's not frozen, it's just not advancing.
(I could try a timeout loop per file, but it's a working LAN environment, it should work hassle-free.)

I've switched back to undionly.kpxe. It boots 3 out of 3 times successfully, no hiccups.
Unfortunately, now the previously working memtest part fails:
Booting kernel failed: Invalid argument

The BIOS PC is equipped with a onboard rtl8168 (LAN ROM 2.59).

So, I would go with ipxe.pxe instead of undionly.kpxe, but than I don't know why imgfetch is not working ALL the time.

Any ideas? What other info would help?
↧

iPXE handoff issues

May 31, 2016, 4:01 pm
$
0
0
So to start, I love iPXE, but can't use it.

I started off using gPXE a few months ago to install windows 7 to iSCSI drives on a NAS.

I used a regular windows 7 install disk to install the OS after attempting a sanboot that failed because the iSCSI drive was blank. Then the BIOS did as it should and reverted to the next in the Boot Order which was CD.

Since I used keep-san = 1 then the iSCSI drive stayed mounted and showed up as a local hard drive to the windows 7 installer CD.

I cannot reproduce this ability with iPXE.
I can still boot to windows 7 with gPXE and install on blank iSCSI drives with gPXE.
With iPXE I cannot boot from or install to iSCSI.

There are a lot of features of iPXE that I really want to use, like the built in menu system and the advanced command line and scripting options like using the sanhook command which is new compared to gPXE.

In my experience iPXE has had some issues handing off control of the NIC to other programs.

Example: I can boot gPXE, run dhcp then chain iPXE fine
BUT
If I run iPXE, get dhcp then chain gPXE, gPXE cannot obtain dhcp

Example2: I can boot Windows Deployment services fine by itself and install to local drives, but if I chain wdsnbp.com from iPXE (with all the right gateway hacks) I can ping the iSCSI target and I see the static route to it with the gateway the same as the target. But Windows PE gives the error: "Windows cannot be installed to this disk. This computer's hardware may not support booting to this disk..."

Example3: If I sanhook my iSCSI target, then exit iPXE to drop to CD install, windows PE does not see any NIC interfaces at all.

Example4: I can boot from an iSCSI disk by using sanboot on gPXE, but when I use the same command from iPXE the boot fails to "A disk read error occurred"

It seems like iPXE is not releasing the NIC to the next thing in each of these situations. I know that after a sanhook certain tunnels need to stay open so you don't lose connection to the target, but how come this worked in the past with the last version of gPXE but not anymore?

I really would like to use the new features in iPXE, but if I can't get the basics that are already working in gPXE to work in iPXE then there is no point to move further. I read that windows installation media needs to be modified to allow it to install to an iSCSI disk. Why? It works with gPXE just fine.

Can someone help me?

I am chainloading undionly.kpxe from builtin PXE rom for both gPXE and iPXE. I got these files from the rom-o-matic sites from the tops of the latest builds. I have tried these examples above across various network cards and computer types with consistent results.

Surely the compatibility that gPXE had with regular things like windows install discs shouldn't be lost to introduce new features right? Surely things can't actually be HARDER in iPXE to accomplish than in gPXE right?

If I can't get iPXE to work, I will have to stick with gPXE because that is working, but boy would I like to be able to use the new command line options from iPXE.
↧
↧

DHCP issues with unicast

June 1, 2016, 5:26 am
$
0
0
So I started discussing this issue on IRC last week, here's a recap for other people. If you don't want to know the background story and get right to my final point/suggestion, scroll down to the last paragraph (tl;dr> On our network, dhcp requests with broadcast flag not set are unreliable).

I could not get the dhcp client to work when booting ipxe.usb from a USB key. A packet sniffer installed before the client showed that no DHCP offers ever reached the client. Patching ipxe to set the broadcast flag in the DHCP requests fixed the issue, as the reply was delivered as a broadcast and everything worked fine. Seeing that the two physical machines I had here had the onboard classic PXE also send their DHCP requests with the broadcast flag set, I assumed this would be the proper way to do it (but I was wrong Wink).
Next I tried to boot Ubuntu from a USB key, and lo and behold, its DHCP client did *not* set the broadcast flag, and yet it worked.

The network here is somewhat complex, the dhcp server is for on another subnet, so there are relay agents running on the routers. We have several dozen subnets spread across the city, vlans, private and public ip ranges, and probably a hand full of hardware manufacturers/models for all the routers and switches in use.

So I could finally get one of the network guys to take half a day to debug this issue with me, as the problem seemed interesting enough to him. Smile
And things were quite crazy. If the machine was booted up successfully and you quickly switched to the ipxe stick, it would boot just fine, which makes you assume that some mac or arp table somewhere along the way was still filled, and behaved weird otherwise. But other than that, we couldn't find anything overly suspicious, and the fact that every other client that does request unicast replies succeeds doesn't help too much either. At some point I was desperate enough to hack up ipxe so much that its dhcp discover looks exactly like the one ubuntu sends, but still no luck. We did realize however that the problem only occurs on some network ports, while on others it works, even if they both lead to the same switch, with both ports configured on the same vlan.
And best of all, today I could not reproduce the problem at all anymore, so I asked if they changed anything or have an idea what happened, but they don't.

So finally what I'm trying to get to:
We're building a USB key that will boot a system from our servers. We want to hand it out as some kind of demo, so we want it to work anywhere someone has a DHCP server running and access to the internet. But I have no clue how common this problem would be in the wild. Maybe we're a one-in-a-million case. Maybe this is why classic PXE also sets the broadcast flag.
So we could maintain a private patch that always sets the broadcast flag, but it'd be nice if that could just be in mainline ipxe. It could easily be made a setting in config/dhcp.h (isc client has that too), a more sophisticated approach would be to set the flag automatically if the first one or two requests timed out.
Any thoughts on that? I'd be willing to create a patch for whatever solution sounds reasonable, if desired.
↧

iPXE boot for BIOS images

June 2, 2016, 12:25 pm
$
0
0
Hi all,

I'm trying to get iPXE booting to work for a BIOS image. The image itself works just fine, if I dd to a USB drive it will boot up correctly, but when I PXE boot, I get:

Registered SAN device 0x80
Booting from SAN device 0x80
Lenovo Group Limited

Invalid System Disk
Replace the disk, and then press any key

We used to use memdisk for BIOS image booting but some problems arose a year or so ago and we migrated towards sanbooting, I just added another image recently and it stopped working:

My iPXE configs:

bios-sanboot:

#!ipxe

isset ${target_kernel} || goto missing_targetkernel

set base_url http://bios-url/

chain ${base_url}${target_kernel}

bios-model-name:

#!ipxe

set target_kernel bios/laptop-bios.img

chain bios-sanboot.ipxe

Is there something wrong with my IPXE configs? When I sanboot manually with:

sanboot http://bios-url/laptop-bios.img it gives me the same error.

Specs:
Lenovo Carbon X1 Laptop
Ubuntu OS
Boot Mode Selection: UEFI and Legacy with Legacy First
AFAIK we are using a pretty recent version of IPXE

Any help would be greatly appreciated!
↧

How to set the DHCPv6 in win2012r2 to boot ipxe.efi

June 2, 2016, 8:49 pm
$
0
0
As title, I would like to use the IPv6 iPXE.

Environment----
1. 2012R2 , WDS, DHCPv4 + V6
2. Boot to ipxe.efi with DHCPv4 UEFI is successful.(set DHCP option 67 = boot\x64\ipxe.efi)

My question is ----
How can I use the DHCP IPv6 service under 2012r2 to "set the boot file" as same as IPv4?

for example:
[Image: Step_10.png]
↧
Search

ASUS AT5IONT-I: iPXE hangs on "iPXE Inicjalcizing devices..."

June 3, 2016, 12:27 am
$
0
0
Hi!

I'm trying to iPXE boot of ASUS AT5IONT-I board with current iPXE master.
MoBo has most recent BIOS.
Unfortunatelly iPXE hangs on "iPXE Inicjalcizing devices..."
It hangs on undionly.kpxe and iPXE.pxe
May somebody hint me how to gather debug info and where report it to move forward?
↧
↧

boot to grub2

June 3, 2016, 1:32 am
$
0
0
Hi,
I'm familiar with the option to boot from grub4dos,
Is there a way to boot to GRUB2?
↧

Building iPXE

June 6, 2016, 3:45 pm
$
0
0
Ok, so I think I have all the dependencies to build iPXE,

Quote:You will need to have at least the following packages installed in order to build iPXE:

◾ gcc (version 3 or later)
◾ binutils (version 2.18 or later)
◾ make
◾ perl
◾ syslinux (for isolinux, only needed for building .iso images)
◾ liblzma or xz header files

The computer I am trying to build on is not connected to the internet, so that creates some complexity. I downloaded what I think is the libzma header files and added them to
Code:
/usr/local/include

then I do
Code:
cd src
make
and it starts building but halts on
Code:
[AR] bin/blib.a
ar: creating bin/blib.a
[HOSTCC] util.zbin
util.zbin.c: In function 'process_zinfo_pack':
util/zbin.c:272:2 error: unknown type name 'lzma_options_lzma'
So does that mean I have the wrong lzma.h ?

I am using Ubuntu, I ported over the lzma files myself, but am not sure they got configured correctly. I don't have a package installer on the Ubuntu box I don't think.

Any ideas?
↧

iPxe wimboot win 7

June 6, 2016, 2:43 pm
$
0
0
I tried posting in another related thread but it doesnt show up. so my appologies if I am duplicating efforts.

I am wondering if there is any more info about booting and installing windows with wimboot or any other pxeboot method.

I keep getting the "Select driver to be installed" message/error. I've read through many forums bbut the dont give much info on how to resolve this. I have tried injecting the NIC driver on one PC into the boot.wim. Map a drive back to my server and re-run setup .exe. But I still get the needs driver messages. On anohter that I dont have the driver injected I can use a USB to install the NIC driver using drvload and get the network working but its still the same problems. How do we get past the needs driver screens? What is missing? Is it a driver? Is it missing install files? How do we get this to work?

The same files from a usb drive work as expected. The hard drive is seen when browsing so its not missing or un-readable. I am at a loss.

I have used wimboot 2.5.? the current latest as of 6/6//2016
I have also used 2.4.? with same results.

iPxe is installed/configured from using Fog 1.2.0 running ubuntu/linuxmint 17.3

While I am not new to linux I don't use it often. So it's possible I am missing a config. rather that be in pxe/linux/or fog. I quit using undi*.*pxe as I couldnt get them to work. Found how to use pxelinux.cfg/default and boot to fog boot.php

Just trying to give as much troubleshooting that could be relavent.

Any assistance in this would be appreciated.

Thanks,

Jason
↧

ISO booting over the Internet

June 11, 2016, 8:08 am
$
0
0
I'm working on ISO booting over the internet and building the boot menu.
Anyone have any handy configs for Caine 7, Sysrecue, or Hiren's?

Bastardo
↧
↧

StartSSL - HTTPS failure - permission denied

June 16, 2016, 6:47 am
$
0
0
Starting ~ Jun 15, https began failing with a "permission denied" 0216e93c error. The certificate in use is valid and from StartSSL (granted not a tier 1 provider).

a) This permission denied language is a poor choice for this condition. This leads someone to believe there are permission problems at the file level and not a failed cert check. If the request is denied because of the certificate and not file permissions then I suggest the language indicate same in some manner. The ambiguity of "permission denied" is too vague.

b) It might be necessary for ipxe.org to update / have a look at their CA repo. StartSSL and LetsEncrypt should probably be added in a more persistent manner.

Many thanks,
Mark
↧

iSCSI disconnect problem with ipxe but not with gpxe

June 21, 2016, 2:41 am
$
0
0
I've been trying to install Windows using pxe chainloading (undionly.kpxe) with an embedded script to sanboot with a fallback to a local cdrom drive.

ipxe from master (dated 20160616) can connect to the iscsi target and falls back to cdrom (as the image is empty). Trying to use the iscsi target from the installer is excruciatingly slow. Looking in the logs for the target (a synology/Linux/LIO scsi target) I see many login/closes happening. After a few hours the partitions have been set up. After that I aborted it. Another iSCSI target (istgt from nas4free) shows the same problem. The interval between login/close is 20 secs. which matches the NOPIN interval.

When I use the ancient gPXE in the same way it does not show this behaviour. Seems like a regression happened somewhere the last 5 years.... Does anybody have an idea what could have caused the regression? I can retest easily enough, but going through 5 years of commits seems like a lot of work.
↧
Search

The first point to check when debugging boot to HTTP issues

June 23, 2016, 9:47 am
$
0
0
Hi guys. I have not slept whole night due a problem and it turned out so simple I wanted to leave a note on other people who might run into similar problem.

I wanted to test booting to a WinPE image that resides on a web server using iPXE. I followed the instructions to the point, copied and pasted scripts, burnt ipxe.iso file to a USB stick and was ready to go.

Here are the things I learnt first:

- if you copy and paste the script given on http://ipxe.org/howto/winpe to boot.ipxe file, it does not work. You have to remove the spaces so that each line starts at first position of the line ( at least the first #!ipxe command ). It would be great if site maintainers either change the script box on that page and remove the leading spaces on each line.
- Setting up winPE section was not valid for Windows 10 AIK, or the way I installed it. there was no "Deployment and Imaging Tools Environment" on my installation, so I had to execute copype command manually which lead to a few more hours to sort out. Thanks to helpful people's posts and google, I made it.
- I uploaded the files to my webserver using FileZilla but FileZilla experienced lots of disconnections during the process and it took a lot of time.

I started a VM to boot into WinPE image by booting from ipxe.iso. After some more modifications, I was able to download files.

Then the actual problem came. I was able to download everything including the boot.wim, but instead of booting into WinPE image, the VM was restarting itself. I tried it with an actual laptop and saw it was restarting itself too.

I copied the web folder into another place and started tinkering with it by replacing the boot.wim image with different images. I tried for hours without any progress and googled everything in the process.

Then I came to this page using a Google search: http://ipxe.org/wimboot I was surprised that ı did not seen it when I browsed the ipxe.org pages. Anyway, as it showed a different way to booting into WinPE by using files from Windows Installer ISO's, I wanted to try it too. I copied contents of Windows 10 ISO just as decribed in this page and was able to boot into WinPE.

At that point, I decided somehow the wim images I was building were faulty. I spent the whole night building wim images, uploading them and watching them fail to boot one by one; I had two VMs running at the same time.

Around noon, I was devastated. So I did what every engineer would do: I started mixing the files from booting Windows 10 installer image with my own built images one by one.

It took me two more hours, but one the last file to try was wimboot, I recognized that the file size was 41.5 KB on the booting Windows 10 folder, but was 41.36 KB on other non-booting folders. the moment I replaced the 41.36 KB files with 41.5 KB files, my images started to boot. It took me a couple of hours more to sort everything out and get it running as I wanted, but in the end worked.

[undefined=undefined]The moral of the story: Even with proven tools like FileZilla and decades old ftp protocol, it is possible that a file can not copied correctly and no error or warning message be thrown.

In the hindsight, considering that the only file to be copied to web folder is wimboot, I should have make sure it was copied correctly. [/undefined]

I think the first step of any debugging process needs to be checking whether iPXE related files are OK or not.

Best Regards,

Eyup
↧

ipxe boot ccboot

June 26, 2016, 7:20 pm
$
0
0
hi,
how to boot ccboot 2016
sanboot iscsi, get blue screen Huh
chain ccboot gpxe.pxe, get an error Huh
↧
↧

A couple of issues with Flexboot

June 27, 2016, 2:24 pm
$
0
0
I have compiled the source code off of Mellanox is website, but it seems it not compiling intelx driver with it. It shows it does compile it, but when ipxe boot, it says no driver found for 8086:1528. I was wondering if anyone might know what is going on or what can I possibly look at. I am using the FlexBoot-3.4.521 source code off there site.

Also, when I try to compile the code from the flexboot.git, it errors out on mlx_port.c.

If anyone has any thoughts on what might be going on and what I can try, please let me know, thanks.

Code:
# make -j `getconf _NPROCESSORS_ONLN` bin/ConnectX-3.mrom EMBED=./script.ipxe EXTRA_CFLAGS='-DMLX_BUILD -D__MLX_0001_MAJOR_VER_=0x00100003 -D__MLX_MIN_SUB_MIN_VER_=0x000402cf -D__MLX_DEV_ID_00ff=0x100300ff -D__BUILD_VERSION__=\"3.4.719\" -DFLASH_CONFIGURATION  -Idrivers/infiniband/mlx_utils_flexboot/include/  -Idrivers/infiniband/mlx_utils/include/  -Idrivers/infiniband/mlx_utils/include/public/  -Idrivers/infiniband/mlx_utils/include/private/  -Idrivers/infiniband/mlx_nodnic/include/  -Idrivers/infiniband/mlx_nodnic/include/public/  -Idrivers/infiniband/mlx_nodnic/include/private/  -Idrivers/infiniband/mlx_utils_flexboot/tests/include/  -Idrivers/infiniband/mlx_utils/mlx_lib/mlx_reg_access/  -Idrivers/infiniband/mlx_utils/mlx_lib/mlx_nvconfig/  -Idrivers/infiniband/mlx_utils/mlx_lib/mlx_vmac/  -DDEVICE_CX3'
  [BUILD] bin/mlx_port.o
  [BUILD] bin/efi_hii.o
  [BUILD] bin/efi_init.o
  [BUILD] bin/efi_pci.o
  [BUILD] bin/efi_pxe.o
  [BUILD] bin/efi_reboot.o
  [BUILD] bin/efi_smbios.o
  [BUILD] bin/efi_snp.o
  [BUILD] bin/efi_snp_hii.o
  [BUILD] bin/efi_strings.o
  [BUILD] bin/efi_time.o
  [BUILD] bin/efi_timer.o
  [BUILD] bin/efi_uaccess.o
  [BUILD] bin/efi_umalloc.o
  [BUILD] bin/efi_usb.o
cc1: warnings being treated as errors
drivers/infiniband/mlx_nodnic/src/mlx_port.c: In function ‘nodnic_port_add_mac_filter’:
drivers/infiniband/mlx_nodnic/src/mlx_port.c:725: error: dereferencing pointer ‘mac.116’ does break strict-aliasing rules
drivers/infiniband/mlx_nodnic/src/mlx_port.c:725: note: initialized from here
  [BUILD] bin/efi_utils.o
  [BUILD] bin/efi_watchdog.o
make: *** [bin/mlx_port.o] Error 1
make: *** Waiting for unfinished jobs....
↧

ipxe boot thinstation ?

June 29, 2016, 3:02 am
$
0
0
when use script
kernel ${base-url}/boot/vmlinuz
initrd ${base-url}/boot/initrd
imgargs vmlinuz splash=silent,theme:default load_ramdisk=1 ramdisk_blocksize=4096 root=/dev/ram0 ramdisk_size=786432 console=tty1 vt.global_cursor_default=0 quiet loglevel=3 LM=3
boot || goto failed

Get error

kernel panic - not syncing :VFS: Unable to mount root fs on unknown-block(1,0)
kernel Offset: disabled
---[ end Kernel panic - not syncing: VFS: Unable to mout root fs on unknown-block(1,0)

what's wrong?
↧

Wimboot issue Wyse Terminal 5020

June 29, 2016, 7:22 am
$
0
0
Hey Guys

So I have a couple Wyse Terminals, model 5020, that I have in my office. I was play around with them booting iPXE and seeing if I could get a Windows install to load. I setup a simple menu which the following option:

:cdrom
clear net0/ip
set net0/ip [clientip]
sanunhook
chain http://[serverip]/clone.php?mac=${net0/mac:hexhyp}&serverip=[serverip] || exit
exit

:installwin8x
clear net0/ip
set net0/ip [clientip]
chain http://[serverip]/clone.php?mac=${net0/mac:hexhyp}&serverip=169.254.10.26
imgfree
kernel http://[serverip]/live/wimboot
initrd http://[serverip]/live/win81/bcd BCD
initrd http://[serverip]/live/win81/boot.sdi boot.sdi
initrd http://[serverip]/live/win81/boot.wim boot.wim
imgstat
boot

If we select the CDROM option, the machine reboots and the boot process starts over. If we select the Install Windows 8x option WIMBOOT goes to a black screen and I get:

Using bootmgr.exe va 0x2b9c8 len 0x9cb58
...extracted bootmgr.ext
Emlating drive 0x01

and if we just boot to a normal DVD Drive, they work fine and load the installer. We're currently using the UNDIONLY bin format. Has anyone seen this or been able to get the Wyse Terminals to work?
↧
Viewing all 1484 articles
Browse latest View live
Search