From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: problem with v86d
Date: Wed, 11 Jun 2014 14:34:29 +0000 (UTC) [thread overview]
Message-ID: <loom.20140611T162313-397@post.gmane.org> (raw)
In-Reply-To: 5805.1402463655@ccs.covici.com
<covici <at> ccs.covici.com> writes:
> Hi. Does anyone have a clue as to why v86d should suddenly start being
> very cpu intensive on my computer? When I first boot its fine (using
> either systemd or openrc), but after a while -- maybe a day or two it
> starts using up lots of cpu and definitely increases the load average
> and slows down things. I notice this has not changed in several years,
> so I am wondering if it is not working as it used to?
> Thanks in advance for any ideas.
Ok so the first thing I noticed:
http://dev.gentoo.org/~spock/projects/uvesafb/
You don't have permission to access /~spock/projects/uvesafb/ on this server.
So you need to drop the (gentoo-dev) a line about where to look at his
sources....
Now looking at the flags {debug x86emu} I see:
sys-apps/v86d: Use x86emu for Video BIOS calls
If you've been reading the gentoo user list, you can see
much has changed with frame buffers and video drivers recently
in the kernel. The best place to start reading is posting on
25/may/2014 by Greg Turner.
My best guess is changes in the kernel affect your emulation,
and you'll have much digging to do, if the gentoo -dev that
develops/maintains that code does not "drop a hint" onto your
questions as to "waz sup" with x86emu.
Are there any notes when you compile it? News? Read the comments
in the ebuild as to new problems?
good hunting.
hth,
James
next prev parent reply other threads:[~2014-06-11 14:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 5:14 [gentoo-user] problem with v86d covici
2014-06-11 14:33 ` [gentoo-user] " Nikos Chantziaras
2014-06-11 14:34 ` James [this message]
2014-06-11 14:49 ` covici
2014-06-11 15:22 ` Nikos Chantziaras
2014-06-11 20:10 ` James
2014-06-11 20:38 ` covici
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=loom.20140611T162313-397@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@lists.gentoo.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