This is a sort of update.
In my /etc/initramfs-tools/modules
fbcon
vesafb
nvidiafb
And in /etc/modprobe.d/blacklist-framebuffer
# blacklist nvidiafb
# blacklist vesafb
Now this is interesting. If my boot line DOES NOT include vga=XXX, I
get virtual terms which are very crisp c
Hello, running a Gateway C-140x convertible tablet that includes an "ATI
Mobility™ Radeon® X2300 HD" card. I initially had problems with the usplash
not displaying on boot as well as the no terminal problem.
I changed around the display settings in /etc/usplash.conf to be:
xres=1024
yres=768
The
Hallo,
I tried the workaround for this bug too, but always ended with a console screen
containing some spread green squares, partly blinking.
I have an older Toshiba notebook with a NVidia GeForce4 620Go. Because I need
the Xinerama function (for beamer presentations), I use the restricted nvidi
I did not realize this was a bug. I always had my virtual consoles at
VGA quality, not realizing that higher resolutions were possible, until
I experimented with different distros. When I started messing with
vga=XXX I got the blank screens.
The process below, similar to others, gets 1024x768 in
My desktops have Nvidia 5700LE and 5200, my notebook has a 6150go, and I
followed the same procedure in all of them, didn't work in the notebook.
My point is this bug, caused by a decision from a brainy boffin, shouldn't be
there at all. That rare intelligence thought it would be mean to blank ev
I did what Kai (message 92 above:
https://bugs.launchpad.net/ubuntu/+source/initramfs-
tools/+bug/129910/comments/92 ) explained:
sudo mcedit /etc/initramfs-tools/modules
fbcon
radeonfb
sudo update-initramfs -u -k all -v
sudo mcedit /etc/modprobe.d/blacklist-framebuffer
#blacklist radeonfb
Well, this bug drives me crazy, not because it's hard to fix (it isn't or it
shouldn't), but because no kernel dev seems to be interested in fixing it.
I was able to fix it in my desktops, but not in my notebook, no matter what I
did. Installed openSUSE 10.3 on it and now the nb runs fine.
I'm ge
thanks to Stefan Ollinger,
your bugfix describtion finally worked for me.
just wanted to say thank you :)
running [EMAIL PROTECTED]
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which i
It seems to me that this bug (or regression of a long-existing feature,
which ever way you want to look at it) was introduced in order to fix
issues with suspend-to-RAM or hibernate features on computers with frame
buffer LCDs (as pointed out to us by Miguel Martinez on Dec 13). It also
seems that
Hi,
i am running ubuntu 7.10. last week i did a kernel update to 2.6.22-4-generic.
after that i lost my system's framebuffer capability.
i did following to re-enable it:
content of /etc/initramfs-tools/modules:
fbcon
vesafb
-( eof )-
change the end of /usr/share/initramfs-
On Sunday 13 January 2008 00:27:28 Jonas Bygdén wrote:
> I would be more inclined to understand that if this bug had been reported
> AFTER Gutsy was released. But this bug was reported on August 2nd, and as
> far as I know Gutsy is also known as 7.10, which indicates that it was
> released in Octob
On Friday 11 January 2008 21:23:54 Paul Dufresne wrote:
> Almost no one have reported this problem on Hardy (I have checked all
> duplicates, and they are all about Gutsy
I'm on Hardy, ever since Alpha 1, and I had this prob the all time up
until last week, when I MANUALLY fixed it with the step
Hello everybody,
I've got a little question regarding this bug. When I'm on tty[1-6] before
modprobing radeonfb and fbcon, my 80x25 tty works without any kind of
colour. Well, I have different shades of grey, but nothing else. No blue
folders, no green exes, no red tarballs nor purple images. A
I upgraded from Gutsy to Hardy and observed no improvement. Then I added
vesafb to /etc/modules. This proved a partial solution. I no longer need
to manually modprobe vesafb, but there's a much too long 25 second delay
between Grub menu selection and observing anything but black on the
screen again
On 11/01/2008, Paul Dufresne <[EMAIL PROTECTED]> wrote:
>
> You have to understand that we normally don't fix bugs in a version that
> was released.
> Only in exceptional case this is done, and the conditions for doing so are
> described at:
> https://wiki.ubuntu.com/StableReleaseUpdates
I would b
@ andrew
> You have to understand that we normally don't fix bugs in a version that
> was released.
Then why do we claim that we "support" any release? I really hope that
you were speaking off-the-cuff. Deciding not to fix bugs (even with
the exception of security fixes) means that we DON'T suppor
Just tested in Hardy Alpha 3: Bug is still present there :(
Graphics Card: Nvidia Geforce 2MX
Kernel: 2.6.24-3-generic
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug con
On Fri, 2008-01-11 at 23:24 +, Timo Aaltonen wrote:
> Andrea, you were right the first time, medium is the right importance:
>
> https://wiki.ubuntu.com/Bugs/Importance
>
> Lacking a framebuffer console is not an issue that makes your machine
> explode.
Yes, I know but it was going to become
> Please don't try to make it look as if users were doing some evil setup that
> is
> perfectly known as harmful.
But I am. Framebuffer consoles can break lots of things, like power
management. The ultimate solution is coming though; kernel modesetting.
Hardy+1 material, hopefully.
If you haven'
On Sat, Jan 12, 2008 at 08:02:43AM -, Timo Aaltonen wrote :
> "Those who have changed the default configuration and thus cannot use
> the console". There.
>
*Cough* . You must be joking. This is not $whatever_random_modification that is
likely to make the part of your system you are configuri
"Those who have changed the default configuration and thus cannot use
the console". There.
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-
Andrea, you were right the first time, medium is the right importance:
https://wiki.ubuntu.com/Bugs/Importance
Lacking a framebuffer console is not an issue that makes your machine
explode.
** Changed in: initramfs-tools (Ubuntu Hardy)
Importance: Critical => Medium
** Changed in: linux (Ubu
Andrew Conkling a écrit :
>
> And let's keep in mind the Ubuntu Code of Conduct:
> http://www.ubuntu.com/community/conduct.
>
And let's stop invoking the CoC each time someone doesn't agree, please...
Btw, where are the offending words?
--
Lionel Le Folgoc - https://launchpad.net/~mrpouit
EEBA
On Fri, Jan 11, 2008 at 09:23:54PM -, Paul Dufresne wrote :
> You have to understand that we normally don't fix bugs in a version that was
> released.
You have to understand that I'm part of MOTU and thus do know what a SRU is,
thanks.
> Only in exceptional case this is done, and the conditi
On Jan 11, 2008 4:23 PM, Paul Dufresne <[EMAIL PROTECTED]> wrote:
> You have to understand that we normally don't fix bugs in a version that
> was released.
> Only in exceptional case this is done, and the conditions for doing so are
> described at:
> https://wiki.ubuntu.com/StableReleaseUpdates
>
You have to understand that we normally don't fix bugs in a version that was
released.
Only in exceptional case this is done, and the conditions for doing so are
described at:
https://wiki.ubuntu.com/StableReleaseUpdates
Among the conditions, the following:
An explanation of how the bug has been
I set the importance "critical" also for linux so. Sorry for the
mistake.
** Changed in: initramfs-tools (Ubuntu Hardy)
Importance: Medium => Critical
** Changed in: linux (Ubuntu Hardy)
Importance: Medium => Critical
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bu
On Fri, Jan 11, 2008 at 08:02:33PM -, Andrea Corbellini wrote :
> @Loye Young: I'm sorry for your company, but I have to set the
> importance "critical" to bugs which are really critical.
>
> --
> Blank ttys when using vesafb (vga=xxx)
> https://bugs.launchpad.net/bugs/129910
> You received t
On Jan 11, 2008 1:54 PM, klerfayt <[EMAIL PROTECTED]> wrote:
> I know this is not the best place to ask question, but - is there a wiki or
> something that explains all this
> "console/framebuffer/what_ever_is_this_tty_really_called" stuff in layman's
> terms?
Yes, there are, though it's a bit mor
Andrea,
>I have to set the importance
Did someone die and made you BDFL?
>"critical" to bugs which are really critical.
It's one thing to mark something as less than critical; it's another
to mark it as declined altogether.
Loye
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpa
@Loye Young: I'm sorry for your company, but I have to set the
importance "critical" to bugs which are really critical.
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug con
I know this is not the best place to ask question, but - is there a wiki or
something that explains all this
"console/framebuffer/what_ever_is_this_tty_really_called" stuff in layman's
terms?
On Jan 11, 2008 9:39 PM, Loye Young <[EMAIL PROTECTED]> wrote:
> To Andrea Corbellini,
> > I've changed t
To Andrea Corbellini,
> I've changed the importance because this bug is not critical at all.
It may not be important to you, but I am not keen on my company
selling computers with a broken console.
Remember that you aren't the only fish in this pond, Andrea. You might
not care about this bug or t
On Thu, 2008-01-10 at 20:42 +, Andrew Conkling wrote:
> I get that. I asked because Andrea Corbellini had mentioned the latest
> updates while changing the importance of Hardy, so, I'm not sure, I thought
> he was talking about the latest Hardy updates. If (he could confirm and) you
> could tes
Another try after a fresh install of Feisty.
1. comment the "blacklist vesafb" (but leave uncommented every others) line in
/etc/modprobe.d/blacklist-framebuffer
2. add "fbcon" and "vesafb" in /etc/initramfs-tools/modules
3. add the vga=xxx in your boot list
4. update-initramfs -v -u -k $(uname -
Adding the modules to /etc/initramfs-tools/modules and executing update-
initramfs -u did not work for me.
What helped me a bit was this comment:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/129910/comments/236
After adding the modules to the start of /etc/modules it worked fine
On Thursday 10 January 2008 12:26:42 Andrew Conkling wrote:
> So you tried on Hardy then?
Been using Hardy ever since Alpha 1, and I still have this prob, with may
onboard Intel i855.
actually, it even worse now, because hibernation also cause the screen to get
all those "nice" color squares, an
On Jan 10, 2008 3:21 PM, Loye Young <[EMAIL PROTECTED]> wrote:
> @ Andrew
> >So you tried on Hardy then?
>
> No. This bug was filed against Gutsy, and it's still a bug against
> Gutsy. I don't know what would possess anyone to mark it "declined for
> Gutsy". The EOL date for Gutsy isn't until Apri
@ Andrew
>So you tried on Hardy then?
No. This bug was filed against Gutsy, and it's still a bug against
Gutsy. I don't know what would possess anyone to mark it "declined for
Gutsy". The EOL date for Gutsy isn't until April 2009. Until then, basic
functionality of the OS that's broken should be f
Yes i did:
update-initramfs -u
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
Le jeudi 10 janvier 2008 à 16:20 +, mozdevil a écrit :
> Using kernel 2.6.22-14-386
> VGA controller: Intel 82945G/GZ rev 02
>
> Solution does not work for me:
> 1. comment the "blacklist vesafb" (but leave uncommented every others) line
> in /etc/modprobe.d/blacklist-framebuffer
> 2. add "f
Using kernel 2.6.22-14-386
VGA controller: Intel 82945G/GZ rev 02
Solution does not work for me:
1. comment the "blacklist vesafb" (but leave uncommented every others) line in
/etc/modprobe.d/blacklist-framebuffer
2. add "fbcon" and "vesafb" in /etc/initramfs-tools/modules
3. add the vga=xxx in y
So you tried on Hardy then?
-Original Message-
From: Loye Young <[EMAIL PROTECTED]>
Date: Thu, 10 Jan 2008 04:25:41
To:[EMAIL PROTECTED]
Subject: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
I'm not sure what you mean by "fixed . . . with latest updat
I'm not sure what you mean by "fixed . . . with latest updates," because
the console is still broken unless the user has the inclination and
ability to do some hacking.
With latest updates the default installation still doesn't allow better
than 80x25 on the console, because the framebuffer is bla
i update day and day.
i fixed in each version.
my note book is Thinkpad r50e with intel i810 card
Andrea Corbellini 写道:
> This seems fixed to me with latest updates. Can you confirm this happens
> also to you?
>
> ** Changed in: initramfs-tools (Ubuntu Hardy)
>Importance: Critical => Medium
>
This seems fixed to me with latest updates. Can you confirm this happens
also to you?
** Changed in: initramfs-tools (Ubuntu Hardy)
Importance: Critical => Medium
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you ar
@Loye Young
I have already written an Ubuntu-specific tutorial concerning this issue
and K/Ubuntu usplash as well, using only "hwinfo" program and
traditional "vga=" instead of "video=" parameter. I haven't posted here
earlier, because this bug already has had lots of comments. But since
you've m
klerfayt wrote:
>"video= ... " boot option will do nothing in ubuntu
There's nothing proprietary about Ubuntu's implementation of the
kernel or the video stack. "video=..." is a feature of the vesafb (and
similar) framebuffer driver. If the driver is loaded at boot time, as
I described, it should
in response to Loye Young "the keyboard and the chair problem":
"video= ... " boot option will do nothing in ubuntu - I believe this is
vesafb-tng/gentoo specific ... sigh ...
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification bec
The following isn't a cut-and-paste "how to" solution. Rather, in an
effort to get resolution (the pun was too good to pass up) on this bug,
my comments are intended as a starting place for how to get the
framebuffer working. If this were a real "how to", I'd make it more
friendly for newbies, but
The statement in /etc/modprobe.d/blacklist-framebuffers to the effect that all
framebuffer drivers suck is extremely bizarre, because GFXBOOT that the install
CD uses loads the framebuffer to install the system and does it damn near
flawlessly.
As a sanity check, when I boot from the install
Upgrading to the latest kernel didn't help my mga system at all. My
/etc/modprobe.d/blacklist-framebuffer file has no content. No matter
what combination of modules I do or don't include in /etc/initramfs-
tools/modules before doing 'update-initramfs -u -k all', I get entirely
black screen between
i also updated to new kernel yesterday. i add vga=792 to new kernel
setting.
it works,
but under new kernel. my sound card does not works, oh. God.
i now do not have time to fix it. so i go back to .13 kernel
so i want to recommend, backup your older kernels. may be one day you
will need it
Yes, but update-grub interpret them and use them to update the kernels
boot options.
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs m
Le jeudi 20 décembre 2007 à 11:49 +, Goodness a écrit :
> No, it is writen in the settings
>
> ## additional options to use with the default boot option, but not with the
> ## alternatives
> ## e.g. defoptions=vga=791 resume=/dev/hda5
> # defoptions=quiet vga=0x0307
The lines that begin with
No, it is writen in the settings
## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet vga=0x0307
I have the Boot-Information back, i modified the Skript from Interbird
with a hold command before
Your menu.lst has been updated, put vga=xxx on the line of your kernel
should get things back working.
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
So, today a new kernel-image has installed and dthe same problem again,
no output at the booting system.
What can i do?
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug co
** Tags added: qa-hardy-list
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.u
"4) If one blacklists fb drivers due to suspend/resume woes, should we take
the next step and blacklist fglrx because it doesn's support SLUB allocator?"
That's exactly what I did! I get massive artifacts and no suspend/resume
at all w/ fglrx.
--
Blank ttys when using vesafb (vga=xxx)
https://bu
Calm down, guys. At least as far as we have our standard 80x24 terminals
working.
This issue is not an xorg driver issue, as Timo already noted. This issue
is caused because the kernel devs have blacklisted all the framebuffer modules.
As the modules have been knowingly blacklisted, this can be
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/u
@Jonas Bygdén
> What's probably most frustrating is the complete and utter silence from the
> responsible teams.
I completely agree with that (and not only for this bug, but for others
as well).
@Felix Miata
> or install some gfxcard other than Intel.
If you do, don't install an nVidia card. I
FWIW, this bug does not apply to OpenSUSE 10.3, Mandriva 2008, or
Feisty, and I highly doubt it applies to Fedora 8 or any other recent
distro. Apparently the devs think those who rightly expect their fb
consoles to work correctly should use something other than Gutsy or
Hardy, or write their own s
Not a driver issue.
** Changed in: xserver-xorg-video-ati (Ubuntu Hardy)
Status: Confirmed => Invalid
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for U
Invalid is an approach or example that is flawed and does not lead to the
correct solution of the problem. An invalid approach would be to simplify
the expression from left to right, disregarding the order of operations. A
valid approach would be to simplify the expression using the order of
operat
What is this?
Is this the way to solve problems now?
First the responsible teams just ignores the bug long enough, then the
QA team says that since Gutsy is now released it's too late to fix it
and sends it to the next release which will not include the same source
(which I'm pretty sure was know
linux-source-2.6.22 won't be in Hardy, flipping status to Invalid.
** Changed in: linux-source-2.6.22 (Ubuntu Hardy)
Status: New => Invalid
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubunt
2007/12/11, Alpha4:
>
> For me it's been enough to remove the vga=xxx option to restore the
> full functionality of the ttys.
That doesn't work for me because of bug 175475. The framebuffer goes
into an ugly, low-res graphics mode (instead of staying in text mode)
and for some reason X won't run
For me it's been enough to remove the vga=xxx option to restore the full
functionality of the ttys.
I've got an Acer Aspire 5680 laptop, with NVIDIA GeForce Go 7600SE graphics
card and Ubuntu Gutsy Desktop x86.
BTW, the vga=xxx option is set easily by the StartUp-Manager, who I think
was the firs
MOM's fix worked for me, too. Thanks!
I'm running 7.10 with Linux 2.6.22-14-generic on AMD64, using an Intel
945GM graphics adapter.
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which
Just tried LeGreffi3R's fix for Gutsy, and it works fine for me with
NVidia GeForce 2 MX200, except that the tty displays are offset a little
from the position of the X display - this problem first appeared in the
later Feisty kernels.
I must say I'm a bit miffed at being expected to wait 6 months
just updated hardy kernel to 2.6.24.1.1 and using vga=0x0360 still
leaves me with a blank screen
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
u
The causes of this bug have been cristal-clear for a long time. The only
reason it's still open if that the kernel team just doesn't care (or if
it does, it apparently enjoys not telling us)
Cheers
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this
This bug was nominated for Gutsy but does currently not qualify for a
7.10 stable release update (SRU) and the nomination is therefore
declined. According the the SRU policy, the fix should already be
deployed and tested in the current development version before an update
to the stable releases wil
using hardy with all updates, and I still dont have TTYs if i set vga=0x0360
both regular and recovery modes fail. I have to edit the grub parameter to see
anything.
Using intel 855 GPU
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notifi
I think it's not good to mix the framebuffer drivers, my tty work great
in gutsy, and it's not related to nvidia (should work with any CGU)
1. comment the "blacklist vesafb" (but leave uncommented every others) line in
/etc/modprobe.d/blacklist-framebuffer
2. add "fbcon" and "vesafb" in /etc/init
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team)
Status: Incomplete => Triaged
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Dropping -intel as subscriber as it looks like Paul determined the
-intel issue is separate (bug 162400), so will focus there.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Invalid
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You recei
Confirmed: still getting the blank ttys with 2.6.24-1 kernel.
However, I also couldn't start X, and do not seem to have any evidence
of my attempt in system or X logs to bring some light to the problem,
sorry.
System started up fine without the vga=794 in my boot options (selected
2.6.24-1 in Rec
** Tags removed: hardy-kernel-candidate
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
I believe this issue still exists in the recently released Hardy kernel,
but if someone else can confrim that would be great. Unfortunately, the
Hardy Heron Alpha1 LiveCD was released with the older 2.6.22 kernel.
You'll have to manually install the newer Hardy Heron kernel in order to
test. This
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing li
** Changed in: xserver-xorg-video-ati (Debian)
Status: Unknown => Fix Released
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
I am removing my bug #162400 as a duplicate of this one, because I don't use
vga=xxx and I am affected by almost identical symptoms, except that modprobe of
the different proposed modules did not help me.
If you don't use vga=xxx in your /boot/grub/menu.lst on the kernel lines, then
maybe you sh
** Summary changed:
- tty[1-6] are active but display nothing in Gutsy
+ Blank ttys when using vesafb (vga=xxx)
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact fo
101 - 186 of 186 matches
Mail list logo
