On 11/06/14 08:14, cov...@ccs.covici.com wrote:
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
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
James wirel...@tampabay.rr.com wrote:
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
On 11/06/14 17:49, cov...@ccs.covici.com wrote:
Thanks. I have a fairly old kernel for other reasons and I installed
v86d in 2011 and it has not changed since. I use udesafb because I
want a frame buffer so I can get a lot more than 80x25 in a virtual
console. Iget 64x160. I also need
Nikos Chantziaras realnc at gmail.com writes:
like that driver. I can't remember what it complained about, but it
means no X at all.
If you're not booting in EFI mode, then you can use vesafb instead. This
doesn't require v86d and doesn't even require an initrd.
uvesafb is mostly
James wirel...@tampabay.rr.com wrote:
Nikos Chantziaras realnc at gmail.com writes:
like that driver. I can't remember what it complained about, but it
means no X at all.
If you're not booting in EFI mode, then you can use vesafb instead. This
doesn't require v86d and doesn't
6 matches
Mail list logo
