I am attaching another bug with uvesafb that may apear for those switching
to intrepid, just a reference:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/246269
On Fri, Sep 5, 2008 at 3:35 PM, Salva Ferrer <[EMAIL PROTECTED]> wrote:
> Same for me, Intrepid uses the new uvesafb for the same
Same for me, Intrepid uses the new uvesafb for the same function so vesafb
can be blacklisted again. I disabled my vesafb and let uvesafb do the job
and everything went fine.
Just make sure that v86d package is installed, in my case it was not and had
to do it manually.
On Fri, Sep 5, 2008 at 12:3
DF5JT --
> Rebuilding the initramfs with vesafb, fbcon and vga16
My experience has been that I get better results using vesafb OR vga16fb,
but not both. With your hardware setup, my initial guess would be that
vesafb is better for your hardware.
Does dropping vga16fb make a difference in the out
If you will help, really _can_ do it. No programming experience needed.
Best choice to begin is vanilla kernel, but you can do the same with
ubuntu kernel too..
1. download latest kernel and chack if bug still there.
sudo apt-get install git-core
git clone
git://git.kernel.org/pub/scm/linux/ker
The vt / tty switching blank screens problem is a different bug - it is not
this one.
Please read Bug #201591 "atyfb regression - screen blank except for
blinking cursor after fbcon vtswitch"
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug n
On Sun, 23 Mar 2008 07:12:09 -
fishor <[EMAIL PROTECTED]> wrote:
> fb modules are black listed becouse of wired issues on suspend/resume.
> So it should be blacklisted by default. Please do not report this bug
> anymore.
fishor: You appear to think that this bug should just die quietly, with
On Wed, 19 Mar 2008 13:25:26 -
أحمد المحمودي (Ahmed El-Mahmoudy) <[EMAIL PROTECTED]>
wrote:
> I tried setupcon blindly in a tty, and that did restore the tty
> indeed. But I need to do that every time I switch to the tty, even if
> I switch from one tty to the other then back I'll need t
Hello,
I tried setupcon blindly in a tty, and that did restore the tty
indeed. But I need to do that every time I switch to the tty, even if
I switch from one tty to the other then back I'll need to run
'setupcon'.
--
أحمد المحمودي (Ahmed El-Mahmoudy)
Digital design engineer
SySD
Update:
Using a debootstrap installed hardy I am able to run the frame buffer with
vga=788 in VirtualBox.
The console switching problem still exists, but typing
setupcon
blindly in a tty restores it. There appears to be a problem with the
console setup.
--
Blank ttys when using vesafb (vga=xx
On Tue, 18 Mar 2008 17:38:26 -
"mirko.quaglio" <[EMAIL PROTECTED]> wrote:
> Same problem using vesafb.
> I've commented blacklisted-framebuffer #vesafb (and #vga16fb) and loaded
> fbcon and vesafb modules in initramfs. I've tried various vga= options and
> the result was always the same: fra
On Mon, Mar 17, 2008 at 12:33:45PM -, Benson Margulies wrote:
> Just from the blacklist workaround?
>
>
> On Sat, Mar 15, 2008 at 12:03 PM, أحمد المحمودي (Ahmed El-Mahmoudy) <
> [EMAIL PROTECTED]> wrote:
>
> > Hello,
> >
> > I just found out, that I get the blank ttys even if without the vg
Just from the blacklist workaround?
On Sat, Mar 15, 2008 at 12:03 PM, أحمد المحمودي (Ahmed El-Mahmoudy) <
[EMAIL PROTECTED]> wrote:
> Hello,
>
> I just found out, that I get the blank ttys even if without the vga=
> option
>
> --
> Blank ttys when using vesafb (vga=xxx)
> https://bugs.launchpad
Ben,
Thanks for your fixes and comments. I've got just one question. Are all
framebuffer drivers unstable? If so, should bugs be filled upstream about
this functionality?
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because
> * A black screen may be observed on some hardware when switching to the
> console or leaving the X window system when a Vesa framebuffer console driver
> is used. Further details can be found in topic number 737-30687
> Apparently ATI considers this a bug worthy of their attention, although
On Thu, 28 Feb 2008 16:47:28 -
LeGreffi3R <[EMAIL PROTECTED]> wrote:
>
> Le jeudi 28 février 2008 à 14:21 +, PMan a écrit :
> > Come on guys. Please fix this with the fine and automatic upgrade
> > system. It's been way too long.
> >
>
> No. In ubuntu, there are only security upgrade by
Le jeudi 28 février 2008 à 14:21 +, PMan a écrit :
> Come on guys. Please fix this with the fine and automatic upgrade
> system. It's been way too long.
>
No. In ubuntu, there are only security upgrade by default, this problem
(not even a bug to me) is not a critical bug, so no upgrade.
--
On Mon, Feb 25, 2008 at 12:13 PM, Richard Bailey <[EMAIL PROTECTED]> wrote:
> Please keep in mind the Ubuntu Code of Conduct:
> http://www.ubuntu.com/community/conduct
>
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because yo
On Mon, 25 Feb 2008 16:10:53 -
Ben Collins <[EMAIL PROTECTED]> wrote:
> I'm marking this as "Invalid" against the kernel until someone can
> summarize a single bug for us to look at, and directly relate that bug
> to the kernel.
Have you actually tried running a framebuffer in a tty on your o
@ Fabio Marzocca <[EMAIL PROTECTED]>:
> --
> Blank ttys when using vesafb (vga=xxx)
> https://bugs.launchpad.net/bugs/129910
> You received this bug notification because you are a direct subscriber
> of the bug.
I have already written an Ubuntu-specific tutorial concerning this
issue and K/Ubunt
Fabio,
>I believe this is a BUG
I am sensing that I perhaps have inadvertently put you on the
defensive, which was not my intent.
I agree with you wholeheartedly that this is a bug, and I'm not
singling you out. It's just that this is already a long thread, and
more "me too" could actually make i
IF YOU HAVE SOMETHING THAT WILL HELP THE DEVELOPERS FIX THE BUG, THIS
IS THE APPROPRIATE VENUE.
IF YOU NEED HELP TROUBLESHOOTING YOUR PARTICULAR SITUATION, GO TO THE
FORUMS.
That said, Fabio's situation is likely instructive for others, so I'll
write up a general how-to here even though this thre
To my fellow framebuffer-deprived penguins:
I feel your pain, and agree that this needs to be fixed. However,
if you are trying to figure out how to troubleshoot to get your
framebuffer working, it's probably best to submit a question to the
forums. This should venue should really be reserved f
Buzz --
>* GUI is 1440x768 using nvidia-glx, and virtual terminals at 1024x768 when
I specify vga=0x318 as a boot option.
>* GUI is 1024x768 using nv, and virtual terminals are 1440x900 (I think),
when I don't specify vga=xxx as a boot option.
I've found a similar reaction with the radeonfb driver
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
@ 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
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
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
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
>
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
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
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
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
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 updates," because
the console
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
>
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
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
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
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
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
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
47 matches
Mail list logo
