similar to: syslinux (pxelinux.0) debug prints

On Thu, Jun 5, 2014 at 8:50 AM, Wissam Shoukair <wissams at mellanox.com> wrote: > Hi Gene, > > More information about this? > > I have found in the syslinux git that this commit id is the last good > commit: > > commit 41c29c26d70fde563d7c255872bbadad87a39dfa (tag: > refs/tags/syslinux-5.02-pre3) > Author: Matt Fleming <matt.fleming at intel.com> >

On May 29, 2014 5:25 AM, "Wissam Shoukair" <wissams at mellanox.com> wrote: > > Hi Gene, > > I was wondering how I can set the ?printf? output to be visible on the screen? (I?m using syslinux-6.03-pre02) printf () or dprintf ()? You need to watch what functions are available at the time you want to print. For example, printf isn't available until ldlinux.c32 is

Op 2014-05-29 om 06:27 schreef Gene Cumm: > On May 29, 2014 5:25 AM, "Wissam Shoukair" <wissams at mellanox.com> wrote: > > > > Hi Gene, > > > > I was wondering how I can set the ???printf??? output to be visible on the > screen? (I???m using syslinux-6.03-pre02) > > printf () or dprintf ()? You need to watch what functions are available at >

Hi Gene, Thanks for the quick response. Im using pxelinux4.07. pxelinux.0 I didn?t find any lpxelinux.0 in this version I will try lpxelinux.0 from Syslinux6.03-pre20. Is there lpxelinux.0 in versions earlier than Syslinux5.10? -----Original Message----- From: Gene Cumm [mailto:gene.cumm at gmail.com] Sent: Monday, 29 September, 2014 18:40 To: Wissam Shoukair; For discussion of Syslinux and

On Mon, Sep 29, 2014 at 11:07 AM, Wissam Shoukair <wissams at mellanox.com> wrote: > Hi Gene, > > Is there a way to compile pxelinux.0 to work with interrupts ? > > I need to check my driver (based on iPXE) which works in interrupt mode (and > not polling) > > > > Thanks for your help. > > Wissam What version? pxelinux.0 or lpxelinux.0? I've never

From: Gene Cumm <gene.cumm at gmail.com> Date: Mon, Mar 17, 2014 at 7:39 PM Subject: Re: [ipxe-devel] iPXE boot from both ports (from diferent subnets) not working To: Wissam Shoukair <wissams at mellanox.com> Cc: "ipxe-devel at lists.ipxe.org" <ipxe-devel at lists.ipxe.org> On Mon, Mar 17, 2014 at 4:43 AM, Wissam Shoukair <wissams at mellanox.com> wrote: >

On Mar 14, 2014 3:37 AM, "Wissam Shoukair" <wissams at mellanox.com> wrote: > > Hi, > > I'm having a similar problem to the one mentioned earlier by "Laborde Louis", but in this case I'm trying to boot in PXE mode and not iSCSI. > > The problem here is this: > > 1 - DHCP from net0 is successful > > 2 - pxelinux.0 is downloaded from

On Fri, Mar 14, 2014 at 7:09 PM, Wissam Shoukair <wissams at mellanox.com> wrote: > Hi Gene , > > I will try to use 4.07 or 4.05 and update. Did you tried it on the VMWare > workstation on which you saw the issue? > > One more question, shouldn't iPXE reassign the correct parameters to the > "new" image its executing? I mean isn't it the responsibility

On Jun 29, 2014 9:37 AM, "Wissam Shoukair" <wissams at mellanox.com> wrote: > > Hi Peter, > > I approached you before on this issue that I?m having with the SYSLINUX 6.03-pre18 when booting with iPXE option ROM. > > The issue was reproduced on different OEMs, and also on 2 different cards (Mellanox and Intel), with latest and 2 years old iPXE code. > > Just

I am experiencing an issue where I ran ipxe (as an option rom) and downloaded the lpxelinux.0 as the bootloader. Next it should download the ldlinux.c32 file using UNDI API. but before that it will close and open the underlying device (which is ipxe), and hooking the device interrupt so it can start getting some packets. What I'm experiencing is that if the underlying device doesn't

On 04-08-15 17:38, Oscar Roozen wrote: > Okay, the code in efi/ uses Print() from gnu_efi, but generic code from > core/ like core/elflink/load_env32.c prints their messages and debugging > stuff using printf(). These messages end up nowhere. This may explain > why I never saw anything beyond a certain point, even with debugging > turned on. I was busy adding some code to dprintf.h

On Fri, Feb 26, 2016 at 01:00:21PM +0000, Wissam Shoukair via Syslinux wrote: > hi > does anyone know if there are some known issues with running lpxelinux.0 > with device that doesn't support Interrupts? > i.e. irq function is null... Take some time to elaborate the question. Cheers Geert Stappers Who thinks that Original Poster doesn't want to hear/read issues.

On 02/26/16 15:10, Wissam Shoukair via Syslinux wrote: > > I am experiencing an issue where I ran ipxe (as an option rom) and > downloaded the lpxelinux.0 as the bootloader. > Next it should download the ldlinux.c32 file using UNDI API. > > but before that it will close and open the underlying device (which > is ipxe), and hooking the device interrupt so it can start getting

On 05-08-15 15:28, Gene Cumm wrote: >>> 0x2f8 is a BIOSism. > >> Is this a problem? The example in the comments said 0x3f8 which is COM1. > > It means that a BIOS IO port for a UART won't work for EFI. No value > for DEBUG_PORT will do anything unless someone's got some translation > "glue" to take the attempts to open the UART and use an EFI handle

On 05-08-15 10:01, Patrick Masotta wrote: >>>> > Okay, the code in efi/ uses Print() from gnu_efi, but generic code from > core/ like core/elflink/load_env32.c prints their messages and debugging > stuff using printf(). These messages end up nowhere. This may explain > why I never saw anything beyond a certain point, even with debugging > turned on. >

[ merging a few sub-threads into one ] > Weird as it sounds I was able to send debug info to COM2 > (redirected to a pipe) on EFI64 VMware workstation clients. Ports 0x3f8 and 0x2f8 are so hardwired into my brain from back in the old BBS-days that I did not expect them NOT to work. Apparently some firmware engineers have this problem too. ;-) >>>> > If there is

>>> > On 05-08-15 12:05, Gene Cumm wrote: >> >>? > I recompiled with this in mk/devel.mk <http://devel.mk>: >>? >? GCCWARN += -DDEBUG_PORT=0x2f8 -DCORE_DEBUG=1 >> >> 0x2f8 is a BIOSism. > Is this a problem? The example in the comments said 0x3f8 which is COM1. It means that a BIOS IO port for a UART won't work for EFI.? No

Hello, I am hoping someone can clarify why I might obtain a quite different value in R & SPSS for a McNemar test I ran. Firstly, here is the R syntax & output R OUTPUT > mctest <- as.table(matrix(c(128,29,331,430), + ncol =2, dimnames = list(group=c("preMHT","postMHT"), + assault=c("yes","no")))) > mctest assault

I was hoping for some advice regarding indexing, From a dataframe there are 27 variables of interest, with the prefix of "pre". [7] "Decision" "MHCDate" "pre01" "pre01111" "pre012" "pre013" [13] "pre02" "pre02111" "pre02114" "pre0211" "pre0212"

>>> Okay, the code in efi/ uses Print() from gnu_efi, but generic code from core/ like core/elflink/load_env32.c prints their messages and debugging stuff using printf(). These messages end up nowhere. This may explain why I never saw anything beyond a certain point, even with debugging turned on. <<< isn't it redirected at all?? >>> I was busy adding some