I'm also getting the FATAL: error inserting vesafb, but it's not doing
any harm other than slowing my boot time by several seconds.
12.10 on AMD 32 bit kernel 3.5.0-21.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: iso-testing
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
On Mon, 2009-02-02 at 20:32 +, Ivan Ivanoff wrote:
When I made kernel recompiling with PAE (for 64 Gb RAM), I lose the
ability to use my uvesafb. Is it possible to enable uvesafb with PAE at
the same time?
I don't know, but this certainly isn't related to the bug. Perhaps you
should haed
When I made kernel recompiling with PAE (for 64 Gb RAM), I lose the
ability to use my uvesafb. Is it possible to enable uvesafb with PAE at
the same time?
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug
I have made workaround mentioned above at first post. And it works with
1200x1600 resolution! At my Intel G45 with intel 2.4.1 driver on my
Ubuntu Linux 8.10 box.
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug
According to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/246269/comments/71 a fix
was released.
1. I am however not sure, if it is fixed for 8.10 final only? RC of Kubuntu
Live CD (kubuntu-8.10-rc-desktop-i386.iso) shows still shows the bug. The boot
stalls for half a minute, but then
Tested on a system with Intel 82G33, running 64-bit. Boots fine with
vga=792. The bootsplash appears, but is a bit large and down to the
right.
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification
For completeness, kernel 2.6.27-7.11 enabled and made default the vesafb
module, which is what we used in the past. To get the benefit, uninstall
v86d.
Dean If usplash doesn't work without quiet, that's a usplash bug.
Please file a report there.
--
Switched from vesafb to uvesafb, but uvesafb
Thank you Ben--noted acted upon.
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Fixed with last kernel upload.
** Changed in: linux (Ubuntu Intrepid)
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) = Ben Collins
(ben-collins)
Status: Triaged = Fix Released
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
I reversed all the mods suggested above uninstalled v86d---my system
now boots with a quiet splash as it should. I next tried to boot with
splash instead of quiet splash to see the text below usplash. Boot-
up with this mode is text-only, not usplash + text below--Shut-
down/reboot works as
Ben says we don't need the initramfs-tools task on this bug; it'll be
fixed in the kernel.
** Changed in: initramfs-tools (Ubuntu Intrepid)
Status: New = Invalid
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received
I just wanted to add the following-
I get the bug also
I didn't see anything wrong until I added my nvidia card into the system.
Is that normal?
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification
I am assuming this is not fixed in beta release
attempting to try ubuntu not intstall
I got the v86dhelper not installed or missing
then the machine yells alot beepbeepbeepbeep and I shut it down to stop the
noises
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
I noticed that someone mentioned the need for using 915resolution on Intel
GPUs. However, I managed to get the solution working without 915resolution,
using the Intel GMA965 GPU on a Lenovo Y410. What I did was this:
1. Install v86d
2. Add /etc/modprobe.d/uvesafb containing this line:
options
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/246269/comments/47
Works for me with 1440x900 also. I am running the solution on a HP
dv9500t. Thank you.
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug
I am afraid that captn's solution did not fully work for me:
The situation is not as bad as before (computer now boots without
beeping and stripes, and I can use the X desktop now without problems),
but:
-) The text on the console window is displaced about 1/2 of the screen width to
the right
Thank you captn!!
for this:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/246269/comments/47
It works on Asus M50VM-AS010C with resolution set to 1440*900.
No beep, and stripes, and such poor things...
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
** Changed in: linux (Ubuntu Intrepid)
Target: None = ubuntu-8.10
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
when I chose a resolution of 1024x768-32 or even 1024x768 in
/etc/modprobe.d/uvesafb
if got the -22 error
However after checking /sys/class/graphics/fb0/modes
notice this is NOT /sys/devices/platform/uvesafb.0/vbe_modes
I specified 1024x768p-60 which was in the list
Thank you chris_c That has FINALLY allowed me to partly fix a bug
I've been fighting quite a while nowsee:
https://bugs.launchpad.net/ubuntu/+source/usplash/+bug/235662
I now can see my usplash for more that one time in a row--only problem
is that splash is still broken (text below
Bug confirmed and the workaround fixed the problem. Thanks
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
denisius.sion in #58 (probably 3 messages up, but I cannot tell until
after I post) seems to have an MTRR problem.
This message means that the kernel is refusing to change the type of an MTRR as
the driver is telling it to do:
[ 16.285745] mtrr: type mismatch for fb00,80 old: write-back
I got the uvesafb working by the descriptions above.
Although it gets loaded too late for usplash to function.
Seeing in dmesg it's only after 34 seconds the module is loaded.
How can I make it load earlier?
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
Still doesn't work:
[ 16.040648] uvesafb: NVIDIA Corporation, G86 Board - e416h01 , Chip Rev ,
OEM: NVIDIA, VBE v3.0
[ 16.284005] uvesafb: VBIOS/hardware doesn't support DDC transfers
[ 16.284074] uvesafb: no monitor limits have been set, default refresh rate
will be used
[ 16.285459]
Arrr ;-) Unfortunately the intel xorg driver doesn't seems to like it.
It causes sometimes overlay and opengl lockups. Generally the coexistence with
any frame-buffer makes the opengl system more
unstable. Still in deep water here. (No wonder why without an intel network
card you feel lucky
Hello. Somehow motoplux's instructions did not work for me, but captn's
on comment #47 above
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/246269/comments/47)
did. Thank you captn!
dmesg shows me the following lines:
[ 23.179171] uvesafb: Intel Corporation, Intel(r)GM965/PM965/GL960
Hello. Sorry for extra comment (should have included in previous), but I
note that the framebuffer comes into effect only later, i.e. after first
few kernel messages (as you can see, for first 23 seconds) pass. It is
unlike the previous vga=792 functionality where right from the start,
the
Aye, captn! I already filed a bug on that :) bug #274442
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
@Bogdan: Than someone should resurrect that package? I suppose ubuntu has to
ride
the dead horse here about a 1/2 - 1 year (until the kernel mode setting driver
arrives).
https://launchpad.net/ubuntu/hardy/+source/915resolution
--
Switched from vesafb to uvesafb, but uvesafb can't work
** Changed in: linux (Ubuntu)
Importance: Medium = High
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Thank You for changing the importance to High--is there any information
you need that has not been supplied?
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because you are a member of Ubuntu
Bugs,
@captn: Thanks for reminding me; I actually put in an
/etc/modprobe/uvesafb install scriptlet, so it's run automatically
whenever uvesafb is loaded.
@everyone else:
On my machine (Dell Latitude D620 with intel 945GM video) I couldn't get
uvesafb to start during the boot. The module got loaded,
( this workaround is similar as in comment #42 )
1) install v86d
2) create /etc/modprobe.d/uvesafb
options uvesafb mode_option=1280x800-32 mtrr=3 scroll=ywrap
4) append
blacklist uvesafb
to /etc/modprobe.d/blacklist-framebuffer
3) append
uvesafb
to /etc/modules
** Description changed:
Binary package hint: linux-image-2.6.26-3-generic
After grub selection there is no any output to screen till gdm start.
This happens if VESA mode selected in grub command (vga=792 for example). VGA
modes work well.
This problem exists only in 2.6.26-3
@captn: Strange: I tried the exact same parameters you gave, and I
receive this error:
[ 14.298314] uvesafb: Unknown parameter `mttr'
Any idea why that'd be missing? I don't think I ever saw a help file
that mentioned it mightn't exist.
I tried removing that parameter and modprobeing the
OK, ignore the part about mttr, I noticed the typo. (It should have been
mtrr.)
Any idea how I can get a better resolution?
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because you are a member
Until somebody decides to fix the Intel fb driver ;-) you have to patch the VGA
BIOS
( Read http://dev.gentoo.org/~spock/projects/uvesafb/faq.php )
e.g .for 1280x800:
* wget
'https://launchpad.net/ubuntu/hardy/+source/915resolution/0.5.3-1ubuntu1/+files/915resolution_0.5.3.orig.tar.gz'
Following
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/246269/comments/41
and changing mode to mode_option= does not work here, too.
[1.982693] v86d[1080]: segfault at 0 ip 00402069 sp
7fffba7333a0 error 4 in v86d[40+1a000]
[6.804010] uvesafb: Getting VBE info
@Christian Roessner I'm on 32
and this is my dmsg:
[1.487817] uvesafb: ATI Technologies Inc., C24 , 01.00, OEM: ATI MOBILITY
RADEON X600 , VBE v2.0
[1.585195] uvesafb: protected mode interface info at c000:5b20
[1.585198] uvesafb: pmi: set display start = c00c5b8e, set palette =
I experience this bug when trying to use the Alpha 6 Live CD:
Sep 21 13:23:41 ubuntu kernel: [1.712833] uvesafb: failed to execute
/sbin/v86d
Sep 21 13:23:41 ubuntu kernel: [1.712875] uvesafb: make sure that the v86d
helper is installed and executable
Sep 21 13:23:41 ubuntu kernel: [
I tried what motoplux rockpiper had work for them--I get a different
response:
[ 11.295996] v86d[1086]: segfault at 0 ip 08049cd1 sp bf87b600 error 4 in
v86d[8048000+17000]
[ 16.132008] uvesafb: Getting VBE info block failed (eax=0x4f00, err=1)
[ 16.132061] uvesafb: vbe_init() failed with
Finally I'm able to run uvesafb.
This is what I did:
-- installed v86d from intrepid repo
-- added the module uvesafb in /etc/initramfs-tools/modules
-- removed all the old parameter in /boot/grub/menu.lst, like video=...
-- created /etc/modprobe.d/uvesafb containing the parameters for uvesafb. In
make that “mode_option” instead of “mode” and it works for me, too!
thanks.
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: regression-potential
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I am having this issue on my machine while using Intrepid alpha 6 64bit.
I didnt have this issue while using 8.0.4.1 64bit live cd.
My machine is:
MSI P7N SLI-FI 750i SLI Chipset LGA775
NVIDIA GeForce 8500 GT 512MB 16X PCI Express
Core 2 Quad Q6600 @ 2.4GHz 1066FSB 8MB L2 Cache 64-bit
4gb PC6400
*Clarification on my last post... I am not able to boot into the alpha 6
live cd, I end up at a Busybox prompt as a result of the errors.
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because you
i used this howto
http://otamay.wordpress.com/2008/01/12/howto-uvesafb-on-debian-in-my-case-sid-d/
for intrepid with 2.6.27 and works very well.
u have to compile kernel and v86d your self
here is a german howto i made one month ago for ubuntu
Did no one look at the Gentoo bug report?
http://bugs.gentoo.org/196848
I think Harvey is right, v86d must be built against klibc. Having said
that, while I get the -22 error when trying to manually load uvesafb
from the initramfs (by adding break=modules to the kernel command line),
if I then
This bug affects Hardy when the 2.6.27 kernel is installed from
http://kernel.ubuntu.com/pub/next/2.6.27-rc3/{all,hardy}
I installed this because of the response to 236937.
Is there any .deb containing v86d made available for Hardy?
--
Switched from vesafb to uvesafb, but uvesafb can't work
** Tags added: linux-2.6.27
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Still the Same with new Kernel
[EMAIL PROTECTED]:~# lsb_release -rd
Description:Ubuntu intrepid (development branch)
Release:8.10
[EMAIL PROTECTED]:~# uname -a
Linux merlin 2.6.27-2-generic #1 SMP Thu Aug 28 17:20:02 UTC 2008 i686 GNU/Linux
[EMAIL PROTECTED]:~# dmesg | grep uvesa
[
Who is working on this?
What is the status?
When will it be fixed?
Will it be fixed in time for Intrepid?
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because you are a member of Ubuntu
Bugs,
on an Acer Travelmate TM8106wlmi
~# lsb_release -rd
Description:Ubuntu intrepid (development branch)
Release:8.10
~# uname -a
Linux bored 2.6.27-2-generic #1 SMP Thu Aug 28 17:20:02 UTC 2008 i686 GNU/Linux
~# lsmod | grep uvesafb
uvesafb34788 0
cn
Regarding my previous comment above:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/246269/comments/11
When I made the comment above, I was working within a system I had
personally built by hand. I manually built the kernel, klibc, and v86d.
It of course worked perfectly in that
Updated from .27-1 to .27-2, I only have now :
[EMAIL PROTECTED]:~$ dmesg | grep uvesa
[1.937205] uvesafb: Unknown parameter `mode'
I no longer have the error -22.
Thanks to Harvey Muller for the following news:
Uvesafb will not work in Ubuntu until Debian/Ubuntu begin shipping v86d
built
apparently the name changed from mode to mode_option in uvesafb (modinfo
uvesafb)
modprobe mode_option=1440x900 mtrr=3 scroll=ywrap works, but the short form
of video=vesafb:1440x900,mtrr:3,ywrap on the kernel line is not working
(gives the complaint about unknown mode parameter.)
--
Switched
Yep, seems like it worked even better on my work PC:
before:
[3.668437] uvesafb: Getting VBE info block failed (eax=0x4f00, err=-3)
[3.668437] uvesafb: vbe_init() failed with -22
[3.668437] uvesafb: probe of uvesafb.0 failed with error -22
after:
[3.780626] uvesafb: Intel
Installing v86d shows uvesafb setup messages, but causes X to fail to
start, saying it cannot work in framebuffer mode. This is on an intel
965 with no xorg.conf
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug
Ok, I'm back home (i.e. the Intel 915 system), and mistakenly decided to
update the kernel once more to 2.6.27.2 from 27.1. :(
I'm guessing I'll just have to wait till 8.10 formally comes out before
I'll try again. Or I could try reverting back to 27.1
[EMAIL PROTECTED]:~$ uname -a
Linux
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
Thanks Leann! Took your suggestion and installed the latest kernel (and
re-installed usplash and the corresponding ubuntu theme package; I think
I already had v86d installed manually before)
As the system went down, got the usual red screen with white bars I saw
when I had usplash installed. In
Hi Leann,
Thanks for this post. After updating to kernel 2.6.27-1,After bootup,
I'm having the following problems :
[EMAIL PROTECTED]:~$ dmesg | grep uvesa
[0.00] Kernel command line:
root=UUID=c48d6261-5fb3-45fd-9cec-ade1e3816556 ro
video=uvesafb:800x600-16,mtrr:3,ywrap
[
Leann to clarify, on .27 VESA modes still cannot be achieved. Also the
usual boot time messages about the -22 error still occurs. Thanks.
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because you
nothing changed with 2.7.1 about uvesafb:
$ dmesg | grep uvesa
[2.712002] uvesafb: Getting VBE info block failed (eax=0x4f00, err=-3)
[2.712002] uvesafb: vbe_init() failed with -22
[2.712002] uvesafb: probe of uvesafb.0 failed with error -22
--
Switched from vesafb to uvesafb, but
Leann Ogasawara,
I'd like to inform about positive changes with 2.7.1, but this is not
about uvesafb. I can't find any contact info\mechanism for it. Point me,
please.
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received
Oddly enough, on a cold boot I was actually surprised to see the almost-
forgotten Ubuntu startup splash bar rendered properly. I'm still seeing
a different uvesafb error, but not the -22 error as some are still
apparently seeing.
[EMAIL PROTECTED]:~$ dmesg | grep vesa
[ 3.170630] uvesafb: Intel
Not that I'm being pushy in any way, but was wondering if there was a
planned fix (and rough timeframe) for this. I've gotten by for the most
part by removing usplash (prior to this I was getting a completely blank
screen, so I ssh'ed, apt-get removed, and rebooted, and voila I can see
the gdm
I am no longer getting kernel panic (blank screen flashing lights) and
the bahavior of this bug is identical to what has been reported above.
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because
The linux task is the appropriate one for this bug, linux-meta is
usually for bugs that affect multiple kernel releases.
** Changed in: linux-meta (Ubuntu)
Status: New = Invalid
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
Actually on my system I typically get kernel panic that can only be
terminated by REISUB. (TTY is not available - I checked.) This occurs
immediately after vbe_init fails.
Very occasionally the boot continues to GDM:
[1.678748] uvesafb: failed to execute /sbin/v86d
[1.678748] uvesafb:
After returning two junk desktops by Gateway and HP, I built a new rig to run
Linux...Ubuntu as my primary choice. Anyway, I tried installing Hardy and the
desktop CD for Ibex Alpha 4. Hardy froze up with a busybox error while Ibex
gave me this one:
[ 2.422795] uvesafb: Getting VBE info block
reh4c the bug system is not for user support. You have various support
avenues, such as IRC, community documentation or the Ubuntu forums.
Intrepid has not been released to production and given it's Alpha status
bugs are to be expected.
While this error prevents high resolution modes in virtual
Bug is confirmed here with Intrepid Ipex on my Sony Vaio with Nvidia and
linux kernel 2.6.26-5-generic. The following messages are displayed
during boot:
[2.152084] uvesafb: Getting VBE info block failed (eax=0x4f00, err=-3)
[2.152140] uvesafb: vbe_init() failed with -22
[2.152193]
Andre,
Your problem is most likely due to using incorrect modes on the kernel
parameter line, and not a confirmation of the bug. The documentation in
the kernel describes the correct method (Documentation/fb/uvesafb.txt):
video=uvesafb:1024x768-32,mtrr:3,ywrap
The specific mode that you
~$ dmesg | grep vesa
[2.776166] uvesafb: Getting VBE info block failed (eax=0x4f00, err=-3)
[2.776166] uvesafb: vbe_init() failed with -22
[2.776166] uvesafb: probe of uvesafb.0 failed with error -22
on nvidia 8400gs
$ lsmod | grep vesa
uvesafb34660 0
cn
one more experiment:
after clean boot I see uvesafb as loaded module (lsmod), but it doesn't
work: I have no /sys/bus/platform/drivers/uvesafb/uvesafb.0 and
/sys/class/graphics/fb0, and all terminals have usual text mode (40x25
or like that)
I can reload uvesafb:
$ sudo modprobe -r uvesafb
$
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: Confirmed = Triaged
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because you are
I am also experiencing this problem -- multiple beeps upon reboot (sometimes)
followed by either:
1. A black screen until kdm loads
2. Blue/Red background with white vertical bands instead of boot kernel messages
3. Normal boot with kernel messages but no usplash whatsoever.
It seems the beeps
** Also affects: linux-meta (Ubuntu)
Importance: Undecided
Status: New
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
ok. it should be installed automatically - this is first bug.
I've installed it by hands (apt-get) and it doesn't work for me. this is second
bug.
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification
This bug was correctly filed against linux, which installs this module
in /lib/modules/`uname -r`/initrd, which causes it to be loaded in the
initramfs. Please leave it there.
** Changed in: linux (Ubuntu)
Sourcepackagename: initramfs-tools = linux
--
Switched from vesafb to uvesafb, but
Matt Zimmerman : Thanks for your correction
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
One more bug with connections to non-working uvesafb
https://bugs.launchpad.net/ubuntu/+source/usplash/+bug/249037
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because you are a member of Ubuntu
I confirm that current uvesafb is broken due to missing v86d.
This might be another bug, but uvesafb even starts without VGA=
arguments in /boot/grub/menu.lst in my case, causing corrupted splash
screens on a brand new intrepid installation.
** Changed in: linux (Ubuntu)
Importance: Undecided
** Changed in: initramfs-tools (Ubuntu)
Sourcepackagename: linux = initramfs-tools
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
currently there is v86d, but still it doesn't work
i think that this bug and https://bugs.launchpad.net/ubuntu/+source
/linux-meta/+bug/189621 is the same on current stage (missing v86d was
fixed)
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
Answer for post https://bugs.launchpad.net/ubuntu/+source/linux-
meta/+bug/189621/comments/16 about this bug:
I've tried move uvesafb options from /etc/initramfs-tools/modules to
/etc/modules - same black blank terminal with errors:
~$ dmesg | grep vesa
[2.412814] uvesafb: Getting VBE info
Michael Sotnikov : v86d has been added to repositories, however it is
not a part of the default intrepid installation, at least it is not with
alpha 3 which was released yesterday. I had to install it manually
through synaptic to get uvesafb working.
--
Switched from vesafb to uvesafb, but
** Summary changed:
- frame buffer doesn't work during boot (interpid)
+ Switched from vesafb to uvesafb, but uvesafb can't work without v86d
--
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because
90 matches
Mail list logo
