My solution under Intrepid:
modified /boot/grub/menu.lst
added vga=0x0323 to defoptions
modified /etc/usplash.conf:
xres=1024 was: 1440
yres=768was: 900
Note: vga=0x0365 did not work even though my default display is
1440x900. During reboot this produced a screen of vga mode options for
ardchoille
I sympathize with your frustrations. I did a clean install to Intrepid
after release date. This issue has returned to my laptop. I will be
working for net couple hours to see what hack must be done to resolve
it.
--
Blank ttys when using vesafb (vga=xxx)
One year later and this problem still isn't fixed.
http://ardchoille.nfshost.com/Blog/20081029
--
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 subscribed to Ubuntu.
--
In Interpid I've installed v86d and blacklisted vesafb, but still see
blank consoles. They worked fine in hardy with vesafb.
--
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
Trying the latest Intrepid kernel with the following packages:
linux_2.6.27.2.2_i386.deb
linux-generic_2.6.27.2.2_i386.deb
linux-image_2.6.27.2.2_i386.deb
linux-image-2.6.27-2-generic_2.6.27-2.3_i386.deb
linux-image-generic_2.6.27.2.2_i386.deb
linux-restricted-modules_2.6.27.2.2_i386.deb
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
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
Why is that bug still open in xserver-xorg-video-ati? Does the
framebuffer problem persist with ATI cards with latest ubuntu kernel? If
not, we should close that bug and open new bugs if new issues appears.
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You
As far as I can tell, this fixes my problem with an NVidia Geforce Go
7300. If there is a seperate ATI issue, it should be broken into a
seperate bug imo.
Cheers...
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you
Setting back to fix released. This bug is fixed and similar issues
should be posted as different bugs. Thanks.
** Changed in: xserver-xorg-video-ati (Ubuntu Hardy)
Status: Confirmed = Fix Released
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You
search for screen in the repositories, install it, boom, you have vt's.
--
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 subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I believe both my sound cards not being recognized is not related at all to the
-restricted modules, as ALSA is free and included by default in Kernel.
The released fix introduced a grave regression. It manifests with
linux-2.6.24-13.23 (amd64) ,but not with 2.6.24-12.
Not being able to play
Taupter : restricted modules and ubuntu modules are two packages which
add drivers and modules to ubuntu. Most of laptops won't have sound
working without these packages for your kernel, opening a new bug report
for this is really not appropriate because you don't have necessary
packages
Issue is result of perceived conflict between framebuffer kernel driver
and X video driver. See extended discussion in the thread
** Changed in: xserver-xorg-video-ati (Ubuntu Hardy)
Status: Invalid = Confirmed
--
Blank ttys when using vesafb (vga=xxx)
Bug #201591 is now fixed.
--
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 subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Saïvann, are you on x86? I'm still having the problem on amd64, where
2.6.24-12.23 doesn't seem to be available yet...
--
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 subscribed
ski : The 2.6.24-13 kernel is available for AMD64 too, I just looked,
but the restricted-modules are not yet. It's normal that you still have
the problem if you did not install the update. Just wait for update-
manager to install the packages once they will be all ready. After this,
if you still
The 2.6.24-13.23 kernel seems to fix the framebuffer issue, but my
Creative Audigy soundcard doesn't work with this kernel. As the
following linux-restricted-drivers package was not put in the repos,
closed-source NVIDIA video driver doesn't work either. Another machine
here doesn't get its MCP51
When will this fix really appear in repositories? (if there's a fix at
all).
--
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 subscribed to Ubuntu.
--
ubuntu-bugs mailing list
An additional, maybe related culprit, which I am asking other users to
verify; maybe it helps to track down what's really going on:
Two Different X-Sessions, the first one created by logging into KDM,
second one created by Switch User with a different user from the KDE-
Menu. The two sessions
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
This is unrelated:
Rebuilding the initramfs with vesafb, fbcon and vga16 results in a working
framebuffer setup when started with video=vesafb vga=0X31A. However, one is
left with a blinking cursor on an otherwise blank screen.
A root login is possible and setupcon reveals a functional console
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
There seems to be a fundamental difference in handling vesafb between
2.6.24-12 and the previous 2.6.24-11.
2.6.24-12:
Rebuilding the initramfs with vesafb, fbcon and vga16 results in a
working framebuffer setup when started with video=vesafb vga=0X31A.
However, one is left with a blinking
I'm having this problem too with Hardy BETA/amd64/nvidia-glx-new.
vga=791 is fine, but vga=792 is blank.
--
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 subscribed to Ubuntu.
--
I have been using un-blacklist-workaround for some time now (both in
Gutsy and Hardy) but after 2.6.24-12 kernel was installed, the
workaround stopped working.
While booting to 2.6.24-12, system hangs just after usplash has been
shown and power-cycling is required. When using nosplash, the system
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
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.
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a member of
When kernel 2.6.24-11-generic was in Hardy development branch, no such problem.
This is a bug definitely.
When I am running an ubuntu server, fb is the one I need, while suspend/resume
is not.
fb has been existed in the kernel for a long time, you can not just set it as
blacklist for all the
Here tested it again with
http://releases.ubuntu.com/releases/8.04/ubuntu-8.04-beta-server-i386.iso
This is a release for server, I did not touch anything, no vga=xxx in boot
parameter, just booted it, when I saw the language to choose, I used
ctrl-alt-fx to switch them. If I switched more than
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.
consciously noisy rant
fishor: You appear to think that this bug should just
The chvt / blank tty on ALT+F[1-6] behaviour is apparently Bug #201591
(Thanks, Matthew Garrett)
--
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 subscribed to Ubuntu.
--
This bug was confirmed here. I used Ubuntu 8.04 Beta (downloaded from
http://releases.ubuntu.com/releases/8.04/ubuntu-8.04-beta-
desktop-i386.iso), booted with vga=788, and used ctrl-alt-F* to switch
the consoles, blank ttys.
--
Blank ttys when using vesafb (vga=xxx)
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
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
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 to
Im running Ubuntu hardy on a Dell m1330.
Textmode boot works with vga=865 in grub.
However, after i login with gdm and Ctrl-Alt-F1-6 to a tty they only
have a blinking cursor and nothing else.
I have commented the blacklisted vesafb in
/etc/modprobe.d/blacklist-framebuffer and added the
Same problem.
In update from kernel 2.6.24-11 to 2.6.24-12 tty is missing.
I have fbcon and vesafb in initrams modules and commented in
blacklist-framebuffer.
IBM Thinkpad X41.
intel driver.
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug
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: framebuffer seems to work but when I switch between ttys
(ALT+right, ALT+left) all
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:
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)
Since my last update, the problem returned, except that the background
color I set in .bashrc is not ignored.
--
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 subscribed to
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 vga=
option
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.net/bugs/129910
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: uname-a.log
http://launchpadlibrarian.net/12624691/uname-a.log
--
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 subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: dmesg.log
http://launchpadlibrarian.net/12624690/dmesg.log
--
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 subscribed to Ubuntu.
--
ubuntu-bugs mailing
Hello,
Since I upgraded the kernel to 2.6.24-12, the tty is blank, I use vga=0x318.
I have been using this workaround:
Commented those lines in /etc/modprobe.d/blacklist-framebuffer :
#blacklist nvidiafb
#blacklist vesafb
Added those lines to /etc/initramfs-tools/modules:
fbcon
vesafb
Then
** Attachment added: version.log
http://launchpadlibrarian.net/12624693/version.log
--
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 subscribed to Ubuntu.
--
ubuntu-bugs
I'm another sufferer. This evening I tried to add vga=865 to my menu.lst
to get full resolution, and, splam, blank virtual ttys. Nvidia card,
proprietary driver.
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a
Just a quick comment, my solution is not a compromise, it restores the
original functionality that we've always had. Framebuffer drivers for
the console should never be loaded by default, and we've never done this
to my knowledge. It's way to unstable, even ignoring the suspend/resume
issues.
--
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
This bug was fixed in the package linux - 2.6.24-12.21
---
linux (2.6.24-12.21) hardy; urgency=low
[Ben Collins]
* build: Fix vesafb module inclusion into initrd subdir
- LP: #129910
* net/bluetooth: POWERBOOK = APPLE, fix for apple keyboard patch
* custom/xen: Remove
Ben Collins wrote It's way to [sic] unstable,
That's utter nonsense. In all the years I've been using Linux since
sometime last century, my kernel lines have not had vga= parameters only
briefly when necessary to overcome brokenness such as this. With the
exception of this bug, such periods
As said earlier, please don't use launchpad for argumentation or it
become very difficult to work on these bug reports. This bug was close
to stay unfixed because it has too much comments.
If you still disagree and when to ask for this idea, please debate of
the idea with developers in mailing
Bug still exists in Hardy Alpha 6.
--
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 subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Setting back to confirmed because it makes no sense that a so high
volume bug in invalid everywhere. However, please don't post additional
comments here unless a developers is asking for some information. Thank
you for your contribution and for your understanding.
** Changed in: linux (Ubuntu
Uploaded an initramfs-tools that doesn't call modprobe with -b (which
honors blacklists, when it shouldn't). Need to fix the kernel build so
that vesafb.ko gets copied to /lib/modules/`uname -r`/initrd/ in order
for it to be included in the initramfs. Bug is only partially fixed
right now.
--
This bug was fixed in the package initramfs-tools - 0.85eubuntu29
---
initramfs-tools (0.85eubuntu29) hardy; urgency=low
* Do not honor blacklists for vga=/video= parsing. We should always load the
fb drivers in this case (since this is a manual operation on the part of
the
** Changed in: linux (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 subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Loye: the reason we don't use vesafb by default is that it breaks
suspend/resume.
--
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 subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Changed in: linux (Ubuntu Hardy)
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) = Ben Collins
(ben-collins)
Status: Invalid = Fix Committed
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You received this bug notification because you are a
FWIW, the CD boot menu in Hardy no longer incites people to use vga=
(that F4 menu has been removed and replaced with something different),
which was probably why quite so many people were running into this bug.
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You
Colin:
it breaks suspend/resume
The suspend/remove issue is a bug in the proprietary X video drivers,
not in vesafb. I'm sure that blacklisting the framebuffer seemed like
the thing to do at the time.
CD boot menu in Hardy no longer incites people . . . , which was
probably why quite so many
The default behavior using the vga=... parameter on Gusty is to break
the virtual consoles while producing no error message to the user.
I understand that it makes sense to start the booting process with the
lowest common denominator driver for reliability reasons,
however I think if the system
Hello,
I have had a similar problem. I use ati radeon x1300 pro, dell
2007wfp with [EMAIL PROTECTED] I installed the ati driver by amd (the free
driver does not work for me). I have compiz installed and works almost
fine (except the image quality in cube is not good enough).
using radeonfb,
Hello,
I have had a similar problem. I use ati radeon x1300 pro, dell
2007wfp with [EMAIL PROTECTED] I installed the ati driver by amd (the free
driver does not work for me). I have compiz installed and works almost
fine (except the image quality in cube is not good enough).
using radeonfb,
* 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
snip
Apparently ATI considers this a bug worthy of their attention,
Here is an excerpt from the latest ATI Catalyst driver released today,
note point 3.
The following section provides a brief description of known issues
associated with the latest version of ATI Catalyst™ Linux software
suite. These issues include:
* There is no support for video playback on
I have totally blank consoles (tty 1-6). My boot screen works OK. I do
need the consoles in cases of rare crashes. I have tried all the
possible solutions here with no success.
I have tried editing in /etc/modules and /etc/initramfs-tools/modules
and /etc/modprobe.d/blacklist-framebuffer the
Hi,
I have the same problem as Stevie, with the same card. The only
difference is that I see 2 modes at 1440x1050, but only at 8 or 16 bits.
It is still lower than my native 1680x1050 resolution and I see no wide
resolution in the list…
--
Blank ttys when using vesafb (vga=xxx)
Caravel's solution sort of worked for me - I can get the ttys to show up
at 1024x768, but I have the same problem as Stevie, where hwinfo
--framebuffer doesn't show anything higher than 1024x786.
Gusty, nVidia 7600 GT.
--
Blank ttys when using vesafb (vga=xxx)
yep ! i got a geforce 7600 go!
--
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 subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Would just like to say that Caravel's solution worked for me, followed exactly,
with no side effects as of yet.
Gutsy
Dell Inspiron 1720
Nvidia GT8600M
*New to Ubuntu and Linux, so if I can add any other useful info please let me
know.
--
Blank ttys when using vesafb (vga=xxx)
what if my hwinfo --framebuffer doesnt show me my native resolution of 1440*900?
im lost then or is there still a solution?
--
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
Come on guys. Please fix this with the fine and automatic upgrade
system. It's been way too long.
--
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 subscribed to Ubuntu.
--
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 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 default,
one wonders whether the people closing this bug as invalid are the
same arrogant individuals who caused it in the first place, wrt the
comment in the blacklist file...
In any case, this bug, and especially the opportunity to witness how
this ubuntu developer community includes all in their
This bug report is so convoluted, it can not be made sense of. Over 300
comments, various me too's and more tangents than a geometry lesson.
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.
Ben Collins,
It's a really poor excuse for closing this bug.
The problem exists, people complained, people even posted fixes in this bug
report, and here comes you to say this bug is invalid.
Be honest and say you're closing this bug because you don't want to fix it or
are too lazy to parse
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 you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
FYI, committing a change that will get vesafb.ko back into the
initramfs, which should resolve the generic problems of vga=
** Changed in: initramfs-tools (Ubuntu Hardy)
Status: Triaged = Invalid
--
Blank ttys when using vesafb (vga=xxx)
https://bugs.launchpad.net/bugs/129910
You
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 own
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 you
About Ubuntu's Code of Conduct,
Disregarding so many people for so much time is, imo, a disrespectful act.
Getting upset with the aforementioned lack of consideration to its users and to
all the people who cared about reporting, confirming, investigating and posting
workarounds/fixes to this
About Ubuntu's Code of Conduct,
Disregarding so many people for so much time is, imo, a disrespectful act.
Getting upset with the aforementioned lack of consideration to its users and to
all the people who cared about reporting, confirming, investigating and posting
workarounds/fixes to this
About Ubuntu's Code of Conduct,
Disregarding so many people for so much time is, imo, a disrespectful act.
Getting upset with the aforementioned lack of consideration to its users and to
all the people who cared about reporting, confirming, investigating and posting
workarounds/fixes to this
@developers: maybe this can help in fixing the bug.
I have found the cause of my bug: nvidia-glx driver. By removing this
driver and using the free nv driver, I have back my tty's (with the
workaround suggested by Loye). But in such a case, I havo no compiz
effects. If I reinstall nvidia-glx, I
@ 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/Ubuntu
Loye,
this is my feedback report.
I have run points 1 to 7. Now, when I switch to tty-1 (Ctrl-Alt-F1), I
got a 640x480 screen on which is displayed the boot sequence until
running local boot scripts.., then the cursor is blinking and I cannot
enter anything . The other ttys are completely blank.
Thanks Loye,
I had both vesafb and vga16fb because I have read a post here saying to
put them both, and them I forgot to remove. Anyway I will try your
suggestions, even thou I remember I have tried in the past the same
configuration you are correctly describing.
Concerning the last comment on
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 it
You're right, Loye, I should have provided more informations.
Here they are:
1. nvidia-glx 1:1.0.9639+2.6.22.4-14.10
2. [EMAIL PROTECTED]:~ $ lsmod | grep fb
vga16fb15500 0
vgastate 11008 1 vga16fb
vesafb 9092 1
fbcon 41760
Hello,
@Fabio:
1. try to use only one framebuffer driver.
2. Maybe if helps to disable the Ubuntu-splash during boot (Remove
splash quiet from the kernel command line in /boot/grub/menu.lst)
I have an older nvidia graphic in my notebook (GeForce4 420 Go) and use the
nvidia-glx (9639) too .
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
I've tried all tricks with adding/commenting vesafb, vga16fb and fbcon
modules with no success. however, Wiktor Wandachowicz's hint worked. my
machine is thinkpad r60, intel graphics card. i use 1024x768/32 with no
problem now!
--
Blank ttys when using vesafb (vga=xxx)
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
I tried everything in this thread, with no success.
I am running Gutsy and nVidia GeForce 7300LE.
If I switch to tty, I only have one line stating: Loading, please
wait Then when I come back to tty-7 I have a black screen and
nothing working. Computer freezes and I have to hard switch off.
** Tags added: qa-hardy-kernel
** Tags removed: 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
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.
1 - 100 of 185 matches
Mail list logo
