TIP: Click on subject to list as thread! ANSI
echo: linux
to: ALEXEY VISSARIONOV
from: MAURICE KINAL
date: 2015-01-11 21:41:00
subject: nasm/syslinux on 32-bit a

-={ dimanche, janvier 11 2015, 13:41:05 -0800 }=-

Hey Alexey!

Just to make sure it isn't a x86_64 issue I repeated the nasm/syslinux on the
below processor;

-={ output of 'lscpu' starts }=-

Architecture:          i686
CPU op-mode(s):        32-bit
Byte Order:            Little Endian
CPU(s):                1
On-line CPU(s) list:   0
Thread(s) per core:    1
Core(s) per socket:    1
Socket(s):             1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 13
Model name:            Intel(R) Celeron(R) M processor          900MHz
Stepping:              6
CPU MHz:               630.104
BogoMIPS:              1260.20

-={ output of 'lscpu' ends }=-

Exactly the same problem as before using nasm-2.11.06 and syslinux-6.03 which
are both the latest versions.  From what I've read and seen it looks to be an
issue with Intel processors and nano-2.11.06 although syslinux-6.03 could still
have some bugs in it.  Mind you that doesn't completely jive with what I saw
when using the latest nasm snapshot so there it is more likely that the fault
lies with nasm.

Aside:  Using vim to do Fidonet messaging is definetly kickass.  :-)

Life is good,
Maurice

... Don't cry for me I have vi.
--- GNU bash, version 4.3.30(1)-release (x86_64-atom-linux-gnu)
* Origin: Pointy Stick Society - Ladysmith BC, Canada (1:153/7001.0)

SOURCE: echomail via QWK@docsplace.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.