Hi,
I was able to reproduce this error on one of my machines. It seems it
*does* find v86d, as the error would have to more lines if it wouldn't:
uvesafb: failed to execute /sbin/v86d
uvesafb: make sure that the v86d helper is installed and executable
uvesafb: Getting VBE info block failed (eax=0
Hi,
On Fri, 18 Jul 2008 18:17:14 - Michael Sotnikov wrote:
> $ apt-cache policy v86d
> v86d:
> Установлен: 0.1.5-1ubuntu2
> Кандидат: 0.1.5-1ubuntu2
> Таблица версий:
> *** 0.1.5-1ubuntu2 0
> 500 http://archive.ubuntu.com intrepid/main Packages
> 100 /var/lib/dpkg/statu
hi,
On Fri, 18 Jul 2008 13:26:24 - Michael Sotnikov wrote:
> I use default kernel (iterpid):
> $ uname -a
> Linux astar-laptop 2.6.26-4-generic #1 SMP Mon Jul 14 18:39:53 UTC 2008 i686
> GNU/Linux
>
> my config:
> $ cat /boot/config-2.6.26-4-generic | grep VESA
> CONFIG_FB_UVESA=m
> # CONFI
Hi,
On Fri, 18 Jul 2008 07:58:52 - Michael Sotnikov wrote:
> 1. with current interpid kernel (2.6.26-4) vesafb isn't possible - it's
> absent. It was replaced with uvesafb, which use another command (according to
> documents)
> In addition. After system load we can see that uvesafb was load
Hi,
On Fri, 18 Jul 2008 02:14:53 - nullack wrote:
> Problem 1:
>
> From within Intrepid if I unload and reload the module like so:
>
> sudo modprobe -r uvesafb
> sudo modprobe uvesafb mode=1280x1024-32
>
> It results in tty alignment being wrong (like its centre aligned not
> left)
Why do
Hi,
On Mon, 07 Jul 2008 11:57:05 - Colin Watson wrote:
> I've synced v86d into Ubuntu. We still need to review it for main and
> probably get it into the minimal seed, or have the new kernel depend on
> it, or both.
It failed to build because your linux-libc-dev does not have
a /usr/include/
