*** This bug is a duplicate of bug 246269 ***
https://bugs.launchpad.net/bugs/246269
** This bug has been marked a duplicate of bug 246269
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
--
v86d missing, needed for uvesafb
https://bugs.launchpad.net/bugs/189621
You
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
my answers are there: https://bugs.launchpad.net/ubuntu/+source
/initramfs-tools/+bug/246269 ,cause this bug (missing v86d) is already
fixed.
--
v86d missing, needed for uvesafb
https://bugs.launchpad.net/bugs/189621
You received this bug notification because you are a member of Ubuntu
Bugs,
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/status
I've tried same line in /etc/initramfs-tools/modules - the same as it was.
I didn't do anything special about uvesafb. This stuff is coming through
updates. I've tried to figure out what's the problem, but you see...
$ cat /etc/initramfs-tools/modules | grep -v #
uvesafb mode=1024x768
$ ls -a
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 you do
I can reply in return for him.
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 loaded (lsmod | grep
uvesafb), but it
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 loaded
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
# CONFIG_FB_VESA is not set
after clean start without any vga= or video=:
$ dmesg |grep
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
#
$ 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/status
with unpacked initrd:
$ find . | grep vesa
As Michael notes, there is still problems. Having installed v86d from
the new package Matt created I still cant access high res vesa modes.
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
v86d is available in Intrepid:
Package: v86d
Priority: optional
Section: utils
Installed-Size: 180
Maintainer: Ubuntu Core Developers [EMAIL PROTECTED]
Original-Maintainer: Evgeni Golov [EMAIL PROTECTED]
Architecture: i386
Version: 0.1.5-1ubuntu2
Depends: libc6 (= 2.7)
Filename:
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.
--
v86d missing, needed for uvesafb
https://bugs.launchpad.net/bugs/189621
You received this bug notification because you are a member of
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
There is problem with uvesafb, which used in 2.6.26-3 kernel.
Check bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/246269
Maybe this is the same bug.
--
v86d missing, needed for uvesafb
https://bugs.launchpad.net/bugs/189621
You received this bug notification because you are a member
I've just filled http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473176:
ITP: v86d -- execute x86 BIOS code in a controlled environment
Will try to get this into Debian asap, should follow to Ubuntu then ;)
--
v86d missing, needed for uvesafb
https://bugs.launchpad.net/bugs/189621
You received
Agreed, it should be somewhere in the repositories.
** Changed in: linux-meta (Ubuntu)
Status: New = Confirmed
--
v86d missing, needed for uvesafb
https://bugs.launchpad.net/bugs/189621
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
18 matches
Mail list logo
