| 1 |
<covici <at> ccs.covici.com> writes: |
| 2 |
|
| 3 |
|
| 4 |
> Hi. Does anyone have a clue as to why v86d should suddenly start being |
| 5 |
> very cpu intensive on my computer? When I first boot its fine (using |
| 6 |
> either systemd or openrc), but after a while -- maybe a day or two it |
| 7 |
> starts using up lots of cpu and definitely increases the load average |
| 8 |
> and slows down things. I notice this has not changed in several years, |
| 9 |
> so I am wondering if it is not working as it used to? |
| 10 |
> Thanks in advance for any ideas. |
| 11 |
|
| 12 |
|
| 13 |
Ok so the first thing I noticed: |
| 14 |
|
| 15 |
|
| 16 |
http://dev.gentoo.org/~spock/projects/uvesafb/ |
| 17 |
You don't have permission to access /~spock/projects/uvesafb/ on this server. |
| 18 |
|
| 19 |
So you need to drop the (gentoo-dev) a line about where to look at his |
| 20 |
sources.... |
| 21 |
|
| 22 |
Now looking at the flags {debug x86emu} I see: |
| 23 |
|
| 24 |
|
| 25 |
sys-apps/v86d: Use x86emu for Video BIOS calls |
| 26 |
|
| 27 |
If you've been reading the gentoo user list, you can see |
| 28 |
much has changed with frame buffers and video drivers recently |
| 29 |
in the kernel. The best place to start reading is posting on |
| 30 |
25/may/2014 by Greg Turner. |
| 31 |
|
| 32 |
|
| 33 |
My best guess is changes in the kernel affect your emulation, |
| 34 |
and you'll have much digging to do, if the gentoo -dev that |
| 35 |
develops/maintains that code does not "drop a hint" onto your |
| 36 |
questions as to "waz sup" with x86emu. |
| 37 |
|
| 38 |
Are there any notes when you compile it? News? Read the comments |
| 39 |
in the ebuild as to new problems? |
| 40 |
|
| 41 |
good hunting. |
| 42 |
|
| 43 |
|
| 44 |
hth, |
| 45 |
James |
Archives