search for: pushad

Hi All, I have encountered a problem when reading PXELinux's source code. In syslinux/core/pxelinux.asm, function *pxenv* is as below: pxenv: pushfd pushad ; We may be removing ourselves from memory cmp bx,PXENV_RESTART_TFTP ...... push es push di push bx .jump: call 0:0 add sp,6 mov [cs:PXEStatus],ax ...... ret "Around" .jump, we store ES:DI and BX on PXE stack, which points to PXE parameter block and PXE opcode correspondi...

In pxelinux.asm the xchg instruction in xchg ax,ax . data_on_top: should be xchg ax,dx, I think At the end of pxe_get_cached_info routine,there is and ax,ax jnz .err It is supposed to test for AX status, but since pxenv does pushad and popad, AX doesn't contain status. In fact the other routines calling pxenv don't have this bug. pxe_unload seems to be never called; if so, also RealBaseMem is unused. According to the specification, pxe_unload_stack_pkt.reserved are 10 bytes, not 10 words

...di ; Command line write pointer push di mov byte [di],0 ; Null-terminate command line mov si,command_line call cwritestr ; Write command line so far pop di jmp short get_char_2 auto_boot: mov si,default_cmd mov di,command_line @@ -3377,21 +3435,24 @@ pushad .top: lodsb and al,al jz .end call writechr jmp short .top .end: popad popfd ret -%ifdef debug +; BEGIN DTM ------------------------------------------------ +;%ifdef debug +%ifdef debug or writehex +; END DTM ------------------------...

Tim Legge has passed the following message on to me: hpa wrote: > Quinn wrote: > > Now it seems I have found a bug in PXELINUX with regards to etherboot. > > Up until 2.07 pxelinux was responsive to the keyboard. From 2.08 and > > up the keyboard is locked at the boot prompt when pxelinux is loaded > > via etherboot 5.3.14. > > That would not be a PXELINUX bug,

...DD SP,0004 > > 9300:0316 RET > > 9300:0317 PUSHF > > 9300:0318 PUSH CS > > 9300:0319 PUSH 031F > > 9300:031C PUSH EAX > > 9300:031E RETF > > 9300:031F RET > > 9300:0320 CALL FAR WORD PTR SS:[139C] > > 9300:0325 RET > > 9300:0326 PUSHAD > > 9300:0328 PUSH DS > > 9300:0329 PUSH ES > > 9300:032A PUSH FS Thanks for the details. I wonder if this might be related to some troubles I've had recently with gpxelinux.0 where my VM on VMware Workstation has a CPU fault in a similar version range, starting around 5.0...

...9;ia64' (assuming that if PXE + ; runs on IA-64, then it runs in IA-32 mode). For further details see + ; http://www.sandpile.org/ia32/cpuid.htm. Finally, '-smp' suffix is + ; appended on Intel MP 1.x compliant machines. + ; + check_cpuid: + push dword [di-4] + push dword [di-8] + pushad + + mov dword [di-8],'i386' + mov dword [di-4],0 + + ; check if we can change EFLAGS.ID + pushfd + pop eax + mov edx,eax + xor eax,1<<21 ; EFLAGS.ID + push eax + popfd + pushfd + pop eax + xor eax,edx + and eax,1<<21 + jnz .do_cpuid + .done_cpuid: +...

This set of patches add some support for sector size >512. Currently it fixes extlinux, MBR for GPT and ext partitions. Other code is unaffected. This set of patches has been tested on a read Dell machine running a beta firmware.

Hi, These patches contain support for some features that are already in Syslinux 4 but weren't working properly on the elflink branch. It's another step closer to feature parity with Syslinux 4. Having to jump through the comboot API for localboot support is less than ideal and I'll eventually fix that, probably when we move a big chunk of code from asm to C. Also, there's a

Sensei H. Peter Anvin, I have successfully modified/enhanced memdisk so that one can chainload a local operating system after running diskless FreeDOS. I would like your advice regarding the appropriate interface for invoking this functionality. In addition, I would like to know what steps to take so that you feel comfortable considering including this in the standard syslinux distribution.