public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Herman <fherman@inferential.com>
To: linux-msdos@vger.kernel.org
Subject: RPM Binary for FC11 x86_64 (AMD)?
Date: Mon, 26 Apr 2010 20:17:17 -0600	[thread overview]
Message-ID: <4BD6492D.3030405@inferential.com> (raw)

I am once again trying to get dosemu to work on the titles machine.  I 
have been able to get it to load using a couple of versions not 
specific to my processor, but it segfaults when I try to run a 
moderately sized application.

If there is a rpm binary that works with x86_64/AMD on fc11, I'd 
appreciate a pointer to it.

Thanks

Fred

===end of boot.log---athelon rpm, not x86_64-------------------

DOSEMU-1.4.0.0 is coming up on Linux version 2.6.30.5-43.fc11.x86_64
WARN: vm86plus service not available in your kernel
WARN: using CPU emulation for vm86()
CONF: reserving 640Kb at 0x00000 for 'd' (Base DOS memory (first 640K))
CONF: reserving 48Kb at 0xF4000 for 'r' (Dosemu reserved area)
CPU: Stack bottom 0xffbc3000, top 0xffbd8000, esp=0xffbc5f10
CONF: reserving 128Kb at 0xA0000 for 'v' (Video memory)
CONF: reserving 8256Kb at 0x100000 for 'x' (Extended memory (HMA+XMS))
Registering HWRAM, type=e base=0xff9000 size=0x400000
CONF: reserving 4096Kb at 0xFF9000 for 'e' (VGAEMU LFB)
CONF: reserving 12Kb at 0xC0000 for 'V' (VGAEMU Video BIOS)
SERIAL $Id: ser_init.c 1769 2007-05-04 05:59:48Z bartoldeman $
CONF: detected layout is "auto"
CONF: detected alternate layout: (null)
CONF: reserving 64Kb at 0xE4000 for 'E' (EMS page frame)
CONF: reserving 132Kb at 0xC3000 for 'U' (Upper Memory Block (UMB, XMS 
3.0))
TIME: using 9154 usec for updating ALRM timer
======================= ENTER CPU-EMU ===============

not emulated EE 3d8
leavedos(0|0x0) called - shutting down
======================= LEAVE CPU-EMU ===============
Total cpuemu time           887870 us (incl.trace)
Total codgen time            66791 us
Total linker time            64274 us
Total exec   time           375280 us (incl.faults)
Total insert time            55758 us
Total search time            23966 us
Total clean  time            30384 us
Max tree nodes                2599
Max node size                  354
Max tree depth                  13
Nodes parsed                 65711
Find misses                  74161
Nodes executed              390161
Find hits                   115795 (29%)
Find last hits              274366 (70%)
Page faults                  20453
Signals received               118
Tree cleanups                   11

             reply	other threads:[~2010-04-27  2:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-27  2:17 Frederic Herman [this message]
2010-04-27 17:24 ` RPM Binary for FC11 x86_64 (AMD)? solarflow99
     [not found]   ` <4BD74E71.3030401@inferential.com>
2010-04-27 20:57     ` solarflow99
     [not found]       ` <4BD75359.7060401@inferential.com>
2010-04-27 21:24         ` solarflow99
     [not found]           ` <4BD770E8.4060702@inferential.com>
     [not found]             ` <p2i7020fd001004280927sade2eddvf8be7a3df1b7c127@mail.gmail.com>
     [not found]               ` <4BD8781A.1030101@inferential.com>
     [not found]                 ` <r2s7020fd001004281146s84360c02zda49ffb51992aa7c@mail.gmail.com>
2010-04-28 18:46                   ` solarflow99

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BD6492D.3030405@inferential.com \
    --to=fherman@inferential.com \
    --cc=linux-msdos@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox