[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 me to choose from, and an option to scan. I selected scan and the result did not offer any modes in the 1440x900 resolution. I ended up selecting the best 1024x768 mode available. I did not need to mess with modules vga16fb and vesafb in any manner. I am wondering if during the installation of Intrepid, the system was unable to properly detect my resolution and so excluded the vga line from the menu.lst file? Just a guess...probably wrong though. Based off of what I observed today, I can't help but think that this bug has a hook into the default display resolution and the ATI fglrx driver. For the moment my TTYs are 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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) 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 linux-restricted-modules-2.6.27-2-generic_2.6.27-2.2_i386.deb linux-restricted-modules-common_2.6.27-2.2_all.deb linux-restricted-modules-generic_2.6.27.2.2_i386.deb and I am not getting my tty-s when using vesafb. Is there a regression and should this bug be reopened? -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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:39 PM, Shriramana Sharma [EMAIL PROTECTED]wrote: 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 linux-restricted-modules-2.6.27-2-generic_2.6.27-2.2_i386.deb linux-restricted-modules-common_2.6.27-2.2_all.deb linux-restricted-modules-generic_2.6.27.2.2_i386.deb and I am not getting my tty-s when using vesafb. Is there a regression and should this bug be reopened? -- 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. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 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:39 PM, Shriramana Sharma [EMAIL PROTECTED]wrote: 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 linux-restricted-modules-2.6.27-2-generic_2.6.27-2.2_i386.deb linux-restricted-modules-common_2.6.27-2.2_all.deb linux-restricted-modules-generic_2.6.27.2.2_i386.deb and I am not getting my tty-s when using vesafb. Is there a regression and should this bug be reopened? -- 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. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 sound is imo a showstopper, so please don't consider this bug closed yet. Thanks for the ongoing effort on this yet-to-be-fixed bug. ;) -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 installed, this is not a bug. Alsa is the linux sound system, but this system won't use your sound card if the linux kernel does not have any drivers (modules) for it. Also, problem with sound cards is not a part of this bug which is about blank tty, this bug is closed. It would make more sense that you wait for the ubuntu-modules and restricted-modules to come for your kernel before opening a bug for this if the problem really persist. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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) 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 have problems, it is appropriate to look at this deeper. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 High Definition Audio recognized. I'd like to thank all people involved in fixing this bug and 201591. Seeing things being sorted out is wonderful, and I hope the final fix without regression cases will appear soon. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 can be reached by Ctrl-Alt-F7 and Ctrl-Alt-F9. Almost in 90% percent of the cases switching back from F9 to F7 results in a blank screen with the mouse pointer present and I can see its shape change when hovering over the KDE-Menu, Also, Input is possible by Alt-F2. Since I have another distribution (Mandriva) sitting on a different partition, it simply works there, so this is definitely an /K)Ubuntu problem. Also, in Mandriva I can use a console with hi-res framebuffer and switch back and forth without problem. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 outcome in your case? -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 at the desired resolution. Switching between ttys leaves one with a blank console again, setupcon brings it back. I belive this is bug #201591 which is fixed and patches should go soon to repos. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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/kernel/git/torvalds/linux-2.6.git for vanilla kernel or git clone git://kernel.ubuntu.com/ubuntu/ubuntu-hardy.git for ubuntu hardy. 2. install packages to build kernel sudo apt-get build-dep linux sudo apt-get install libncurses5-dev libncursesw5-dev 3. go to kernel, configure, compile and install it. ( you do not need to make kernel with initrd ) cd linux-2.6 make menuconfig ( to configure kernel ) make -j2 all sudo make isnatll sudo make modules_install ( -j2 option for dual core users ) 4. edit grub to boot latest kernel sudo vi ( or ) nano /boot/grub/menu.lst --- and change this parts: timeout 5 #hiddenmenu title Linux root(hd0,0) kernel /vmlinuz root=/dev/sda2 acpi_sleep=s3_bios,s3_mode libata.noacpi=1 ro -- normally you will have other kernel parameters 5. (MOST important part) If bug still exist and this is regression to some kernel version: man git-bisect git bisect start( will make extra branch for testing ) git bisect bad ( current version is bad ) git bisect good v2.6.23( version 2.6.23 is bad ) make menuconfig make -j2 all sudo make isnatll sudo make modules_install reboot test kernel if it's good, go to you git repository: cd linux-2.6 git bisect goodmake -j2 all sudo make isnatll sudo make modules_install #if it's bad git bisect bad -- This testing will need some time bud you will find exact patch braced your system. And believe me, such bug report will really accelerate bug fixing and make you as part of solution and not part of noise. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 cursor on an otherwise blank screen. A root login is possible and setupcon reveals a functional console at the desired resolution. Switching between ttys leaves one with a blank console again, setupcon brings it back. 2.6.24-11: Rebuilding the initramfs with vesafb, fbcon and vga16 results in an 80x25 textconsole with working ttys, but vesafb is not initialized: [ 14.919875] vga16fb: initializing [ 14.919879] vga16fb: mapped to 0xc00a [ 15.023979] fb0: VGA16 VGA frame buffer device I found that 2.6.24-12 puts vesafb into /lib/modules/2.6.24-12-generic/initrd/ while 2.6.24-11 does not do that. Manually copying the module into /lib/modules/2.6.24-11-generic/initrd/ and rebuilding intramfs doesn't make a difference. Go figure. Hardware: Thinkpad T60, Intel 945, SXGA+ with broken Video BIOS (No 1400x1050) -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 boots, X session is opened, but when I switch to console no text is displayed. I tried to log in and start mc and strange thing: background colors are more or less properly displayed, but not the text. Running setupcon makes the fonts visible, but after switching to another VT and back makes issue come again. This appears to be somehow related to kernel 2.6.24-12. While I am booting to 2.6.24-11 virtual consoles are working just fine, the same is with usplash. I first encountered the issue the same day 2.6.24-12 kernel was first released. Since then i updated system frequently So I see two issues there somehow related to 2.6.24-12 kernel: 1) Usplash hanging boot process. 2) No text displayed on virtual terminals using vesafb driver. Maybe some vesafb bug was addressed in 2.6.24-12-21; but obviously another issue came out of it... some kind of regression... The most recent issue was observed after 2.6.24-12 kernel upgrade. The solution can be found by answering the question: WHAT HAS CHANGED BETWEEN 2.6.24-11 and 2.6.24-12? -- Hardy/x86; Nvidia 8600GT (fb:vesafb X:nvidia-glx-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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 situations just because of suspend/resume problem. Since there are so many people they do not need suspend/resume function, but fb function is required. Please, something did changed from 2.6.24-11 to 2.6.24-12, fix it, please. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 2 ttys, it's blank. See ? This is in ubuntu server release, same problem. I did not put any vga=xxx as boot parameter. Just boot it, and got this problem. Please, test it and you will see this is not a normal vesafb problem. I think I'd better to report this as another new bug report. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 die quietly, without being fixed. You also appear not to have read Ben Collins' comments, and the fact that frame buffer modules *supposedly* can be loaded with vga=xxx in the most recent hardy kernel. I have reported a bug against console-setup, in the hope that the bug is no longer kernel-related. See Bug #205484 People will continue to comment on this bug *until it is properly fixed* . So far, it isn't fixed. If the developers do not like the noise, I suggest that they try booting with vga=791 for example, then attempt to switch to tty2-6 . Until the behaviour is rectified to work as it has done without issues in every Linux since way back in kernel 2.2 or so, it isn't fixed. This bug is making a lot of people unhappy (see subscriber numbers), and has been unfixed for over six months. A lot of sysadmins will stop using a distribution that only gives them 80x25 without X, for example. Have fun trying to use mc, jed, or any number of slang and ncurses console apps without decent fb resolution and functionality... /consciously noisy rant -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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) 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 129910] Re: 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 (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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 SySDSoft, Inc. GPG KeyID: 0x9DCA0B27 (@ subkeys.pgp.net) GPG Fingerprint: 087D 3767 8CAC 65B1 8F6C 156E D325 C3C8 9DCA 0B27 -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 run 'setupcon'. Correct. It is still broken, as I have said previously. -- INX Is Not X Live CD based on Ubuntu 7.04 : http://inx.maincontent.net Screenshots slideshow: http://inx.maincontent.net/album/1.png.html -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 modules fbcon vesafb into /etc/initramfs-tools/modules any ideas? -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 becomes black except the blinking cursor. Kernel version: 2.6.24-3 videocard: ati radeon HD2400 -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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: framebuffer seems to work but when I switch between ttys (ALT+right, ALT+left) all becomes black except the blinking cursor. This is exactly what happens here with the most recent kernel. The frame buffer appears to work for example on tty1, but switching to another tty results in a blank screen. This is not recoverable. In addition, even to get this much functionality the initramfs and modules hacks are still required. This bug is *still not fixed*, and should be so marked. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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.net/bugs/129910 You received this bug notification because you are a direct subscriber of the bug. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 ---end quoted text--- I don't understand your question. -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer SySDSoft, Inc. GPG KeyID: 0x9DCA0B27 (@ subkeys.pgp.net) GPG Fingerprint: 087D 3767 8CAC 65B1 8F6C 156E D325 C3C8 9DCA 0B27 -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
** 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
** 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 running update-initramfs. This workaround was working in Gutsy and Hardy, but when I upgraded to kernel 2.6.24-12, it stopped working. ** Attachment added: lspci -vvnn output (I boot with noapic due to another bug) http://launchpadlibrarian.net/12624689/lspci-vvnn_noapic.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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
** 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 asix portion of xen patch, breaks driver - LP: #199296 [Colin Ian King] * SAUCE: fix Udma not fully available in Acer 1694 Wlmi - LP: #187121 * SAUCE: Update toshiba_acpi.c to version 0.19a - LP: #77026 [Stefan Bader] * x86: Clear DF before calling signal handler * Enable FN key on Apple aluminum bluetooth keyboard - LP: #162083 -- Ben Collins [EMAIL PROTECTED] Tue, 11 Mar 2008 13:20:49 -0400 ** Changed in: linux (Ubuntu Hardy) Status: Fix Committed = 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 without have always been very brief, days or at most two weeks. Six months of a choice between being stuck with the exclusively Ubuntu only 80x25 possible on the ttys, or using any of the many major distros not suffering this ridiculous bug instead is inexcusable. Fedora 8 doesn't have this. Etch doesn't have this. SUSE 10.3 doesn't have this. Mandriva 2008 doesn't have this. Knoppix doesn't have this. OTOH, every release of Ubuntu since my first exposure to it over 3 years ago has given me consoles that are different from what just works elsewhere. Whatever it is that Ubuntu does differently with framebuffer from what other distros do is simply broken, and should be changed to conform to what seems to be bulletproof everywhere else. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 lists or ubuntu brainstorm http://brainstorm.ubuntu.com/ Thanks for your participation and for your understanding. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 Hardy) Status: Invalid = Confirmed -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 user) LP: #129910 -- Ben Collins [EMAIL PROTECTED] Tue, 11 Mar 2008 11:46:08 -0400 ** Changed in: initramfs-tools (Ubuntu Hardy) Status: Invalid = 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
** 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
** 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 people were running into this bug. That's a plausible explanation, but it's not what I'm seeing with my customers. I like the F4 feature very much because it's much easier to see what you're doing when setting up several machines a day. However, my sense is that few people ever use the F4. I have taught around 50 people how to install Ubuntu, and I tell them about F4 when I do. However, when they actually do the install themselves, they ignore it. The reason people use the console is because it is useful for so many tasks, especially when fixing problems with video in X. They are accustomed to modern video resolutions, even in text mode, so they naturally expect the CLI to work with a decent resolution. Uploaded an initramfs-tools . . . . Bug is only partially fixed right now. I think the solution Ben is driving towards is a reasonable compromise. It will get the framebuffer working for those who need or want it, but works around the suspend/remove problem in the X video driver. I think I can speak for many on this thread: THANKS!! Happy Trails, Loye Young -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 finds itself booting with a vga= and all framebuffer modules blacklisted, which default configuration, the system should produce a meaningful error message and gracefully ignore the vga=... option, rather than the current behavior which is to display a black screen without offering any explanation to the user as to what's going on. Maybe that's not practical to implement, but the current system is not intuitive. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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, vesafb and fbcon with default /boot/grub/menu.lst, i get virtual terminals and xserver is on tty7. but if i use the boot-up manager to change the dafault to show bootloader, show boot splash, and show text during boot (note:all the three), then i get no virtual terminal and gdm moves to tty9! is this a different bug? honestly, i do not see this as a major problem, but however wondered if there is a solution to this. i appreciate your response in advance. thanks. marhahs -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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, vesafb and fbcon with default /boot/grub/menu.lst, i get virtual terminals and xserver is on tty7. but if i use the boot-up manager to change the dafault to show bootloader, show boot splash, and show text during boot (note:all the three), then i get no virtual terminal and gdm moves to tty9! is this a different bug? honestly, i do not see this as a major problem, but however wondered if there is a solution to this. i appreciate your response in advance. thanks. shahram. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
* 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, although from what I know the issue is not an exclusively ATI issue. The problem with ATI's driver is distinct from the bug described in this thread, and the two should not be confused. The bug described in this thread is really a misconfiguration of the kernel and of the boot-up routine in Ubuntu, to wit: Use of the console framebuffer is blacklisted altogether by default in Ubuntu Gutsy et seq. The ATI driver has a separate problem of corruption of video when moving between the framebuffer and X. The solution by the Ubuntu kernel team was to blacklist the framebuffer, effectively making the console unusable, instead of fixing the problem with ATI's X video driver. The kernel team's current position towards the console is akin to throwing away all four tires when the car gets a flat. You have to drive the car on the rims, but at least you don't have to fix flats anymore. Besides, the rims are prettier than the tires, so who cares? Happy Trails, Loye Young Isaac Young Computer Company Laredo, Texas http://www.iycc.biz -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 the second head in dual head mode. Further details can be found in topic number 737-26985 * Desktop corruption may be noticed when dragging the overlay/video when using dual-display mode. Further details can be found in topic number 737-29578 * 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 * Video Playback may display wrong colors and additional shadow images when cropping or expanding a video file using a video player that utilizes the XVideo extension Apparently ATI considers this a bug worthy of their attention, although from what I know the issue is not an exclusively ATI issue. Larry -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 modules fbcon and all of vesafb nvidiafb vga16fb by themselves and sometimes with each other. None have ever produced anything other than a blank tty screen. My Kit: GeForce3 Ti 200 with latest restricted drivers LCD DVI flat panel 1280x1024 -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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) 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: 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) 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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) 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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, this problem (not even a bug to me) is not a critical bug, so no upgrade. The fact that it isn't a bug for *you* does not mean that it is not a bug. Among other things, it breaks apps that use the frame buffer without X - for example, the fbi and fbgs programs, links2 -g called from a tty and probably a number of others. In addition, it is still present in Hardy (the development version of Ubuntu), so your argument regarding security only falls flat on its face. The frame buffer has worked on every version of Linux that I have used since I started in 2002. This is a regression, whether you like it or not. I notice that Ben Collins is committing a change with vesafb, so perhaps this absurd situation will be rectified after all. We live in hope. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 process, has been enough to encourage me to return to openSUSE, despite Novell's ties with Microsoft. At least the SUSE guys are good engineers. c u. Was fun while it lasted. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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. Thanks ** Changed in: linux (Ubuntu Hardy) Status: Triaged = 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 these comments. Let's bring it to perspective: if there are so many comments on this bug it's because this bug bites a lot of people. If you close this bug with such a lame half-baked excuse you pass the idea you don't give a [EMAIL PROTECTED] to all these people, and you and (*)Ubuntu don't care to look beyond your own noses. Very good example of how bad Ubuntu us becoming. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 hardware ? Have you perhaps noticed that most of the comments relate to this? Did you happen to notice that this bug has been around since at least August last year? Do you care? -- INX Is Not X Live CD based on Ubuntu 7.04 : http://inx.maincontent.net Screenshots slideshow: http://inx.maincontent.net/album/1.png.html -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 bug is, imo, a completely natural reaction. Closing a bug as invalid doesn't magically fix the problem. Closing a bug as invalid in such circumstances makes people question the seriousness, commitment and capability of the maintainer and his employer. Complaining != being disrespectful. Following Ubuntu's Code of Conduct doesn't make everything pink, happy, right and good. The CoC is a guideline, not the 10 Commandments. The CoC shouldn't be used as a cloaking device to avoid criticism. The CoC's link (http://www.ubuntu.com/community/conduct) has a beautiful word in it: community. If we can't give opinions, question people or express ourselves, including our dismal about other community members, it may well not be a community worth of taking part. 'Humanity towards others', Ubuntu's motto, expresses fully this concept of interaction between humans (sharing ideas, feelings) for a greater good. I believe nobody here complained or suggested fixes to this bug just to piss off the Ubuntu's kernel team, but because fixing it was seen by all these people as being an improvement to Ubuntu and another step in direction to a greater good. Before another Law's Guardian comes up here to trump the CoC card again, let's take a look at it: Be considerate. Your work will be used by other people, and you in turn will depend on the work of others. Any decision you take will affect users and colleagues, and we expect you to take those consequences into account when making decisions. For example, when we are in a feature freeze, please don't upload dramatically new versions of critical system software, as other people will be testing the frozen system and not be expecting big changes. When the unknown-to-me Kernel maintainer added this regression in august 2007, almost 7 months ago, before gutsy's stable release, he/she disregarded the very CoC, as this bug affects a lot of people, and framebuffer consoles are used mostly by developers, sysadmins and other knowledgeable people who have a good deal of influence, either as local gurus or IT professionals. Be respectful. The Ubuntu community and its members treat one another with respect. Everyone can make a valuable contribution to Ubuntu. We may not always agree, but disagreement is no excuse for poor behaviour and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It's important to remember that a community where people feel uncomfortable or threatened is not a productive one. We expect members of the Ubuntu community to be respectful when dealing with other contributors as well as with people outside the Ubuntu project, and with users of Ubuntu. Ignoring so many people for 7 months _is_ disrespectful. Asking if the maintainer cares is mostly a rethorical question, as his actions speak for him. 7 months is a way too large span for now and then. Being less productive than he has being (at least as long as this bug is concerned) is impossible, be it because of our complaints or not. As of expecting this or that, we're expecting for months to no avail. Be collaborative. Ubuntu and Free Software are about collaboration and working together. Collaboration reduces redundancy of work done in the Free Software world, and improves the quality of the software produced. You should aim to collaborate with other Ubuntu maintainers, as well as with the upstream community that is interested in the work you do. Your work should be done transparently and patches from Ubuntu should be given back to the community when they are made, not just when the distribution releases. If you wish to work on new code for existing upstream projects, at least keep those projects informed of your ideas and progress. It may not be possible to get consensus from upstream or even from your colleagues about the correct implementation of an idea, so don't feel obliged to have that agreement before you begin, but at least keep the outside world informed of your work, and publish your work in a way that allows outsiders to test, discuss and contribute to your efforts. Lots of people collaborated with reports, confirmations and fixes to this very bug. By the sheer volume of comments here, there's a huge upstream community that is interested. The transparency was so great we saw through it as if is was nothing. When you disagree, consult others. Disagreements, both political and technical, happen all the time and the Ubuntu community is no exception. The important goal is not to avoid disagreements or differing views but to resolve them constructively. You should turn to the community
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 bug is, imo, a completely natural reaction. Closing a bug as invalid doesn't magically fix the problem. Closing a bug as invalid in such circumstances makes people question the seriousness, commitment and capability of the maintainer and his employer. Complaining != being disrespectful. Following Ubuntu's Code of Conduct doesn't make everything pink, happy, right and good. The CoC is a guideline, not the 10 Commandments. The CoC shouldn't be used as a cloaking device to avoid criticism. The CoC's link (http://www.ubuntu.com/community/conduct) has a beautiful word in it: community. If we can't give opinions, question people or express ourselves, including our dismal about other community members, it may well not be a community worth of taking part. 'Humanity towards others', Ubuntu's motto, expresses fully this concept of interaction between humans (sharing ideas, feelings) for a greater good. I believe nobody here complained or suggested fixes to this bug just to piss off the Ubuntu's kernel team, but because fixing it was seen by all these people as being an improvement to Ubuntu and another step in direction to a greater good. Before another Law's Guardian comes up here to trump the CoC card again, let's take a look at it: Be considerate. Your work will be used by other people, and you in turn will depend on the work of others. Any decision you take will affect users and colleagues, and we expect you to take those consequences into account when making decisions. For example, when we are in a feature freeze, please don't upload dramatically new versions of critical system software, as other people will be testing the frozen system and not be expecting big changes. When the unknown-to-me Kernel maintainer added this regression in august 2007, almost 7 months ago, before gutsy's stable release, he/she disregarded the very CoC, as this bug affects a lot of people, and framebuffer consoles are used mostly by developers, sysadmins and other knowledgeable people who have a good deal of influence, either as local gurus or IT professionals. Be respectful. The Ubuntu community and its members treat one another with respect. Everyone can make a valuable contribution to Ubuntu. We may not always agree, but disagreement is no excuse for poor behaviour and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It's important to remember that a community where people feel uncomfortable or threatened is not a productive one. We expect members of the Ubuntu community to be respectful when dealing with other contributors as well as with people outside the Ubuntu project, and with users of Ubuntu. Ignoring so many people for 7 months _is_ disrespectful. Asking if the maintainer cares is mostly a rethorical question, as his actions speak for him. 7 months is a way too large span for now and then. Being less productive than he has being (at least as long as this bug is concerned) is impossible, be it because of our complaints or not. As of expecting this or that, we're expecting for months to no avail. Be collaborative. Ubuntu and Free Software are about collaboration and working together. Collaboration reduces redundancy of work done in the Free Software world, and improves the quality of the software produced. You should aim to collaborate with other Ubuntu maintainers, as well as with the upstream community that is interested in the work you do. Your work should be done transparently and patches from Ubuntu should be given back to the community when they are made, not just when the distribution releases. If you wish to work on new code for existing upstream projects, at least keep those projects informed of your ideas and progress. It may not be possible to get consensus from upstream or even from your colleagues about the correct implementation of an idea, so don't feel obliged to have that agreement before you begin, but at least keep the outside world informed of your work, and publish your work in a way that allows outsiders to test, discuss and contribute to your efforts. Lots of people collaborated with reports, confirmations and fixes to this very bug. By the sheer volume of comments here, there's a huge upstream community that is interested. The transparency was so great we saw through it as if is was nothing. When you disagree, consult others. Disagreements, both political and technical, happen all the time and the Ubuntu community is no exception. The important goal is not to avoid disagreements or differing views but to resolve them constructively. You should turn to the community
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 bug is, imo, a completely natural reaction. Closing a bug as invalid doesn't magically fix the problem. Closing a bug as invalid in such circumstances makes people question the seriousness, commitment and capability of the maintainer and his employer. Complaining != being disrespectful. Following Ubuntu's Code of Conduct doesn't make everything pink, happy, right and good. The CoC is a guideline, not the 10 Commandments. The CoC shouldn't be used as a cloaking device to avoid criticism. The CoC's link (http://www.ubuntu.com/community/conduct) has a beautiful word in it: community. If we can't give opinions, question people or express ourselves, including our dismal about other community members, it may well not be a community worth of taking part. 'Humanity towards others', Ubuntu's motto, expresses fully this concept of interaction between humans (sharing ideas, feelings) for a greater good. I believe nobody here complained or suggested fixes to this bug just to piss off the Ubuntu's kernel team, but because fixing it was seen by all these people as being an improvement to Ubuntu and another step in direction to a greater good. Before another Law's Guardian comes up here to trump the CoC card again, let's take a look at it: Be considerate. Your work will be used by other people, and you in turn will depend on the work of others. Any decision you take will affect users and colleagues, and we expect you to take those consequences into account when making decisions. For example, when we are in a feature freeze, please don't upload dramatically new versions of critical system software, as other people will be testing the frozen system and not be expecting big changes. When the unknown-to-me Kernel maintainer added this regression in august 2007, almost 7 months ago, before gutsy's stable release, he/she disregarded the very CoC, as this bug affects a lot of people, and framebuffer consoles are used mostly by developers, sysadmins and other knowledgeable people who have a good deal of influence, either as local gurus or IT professionals. Be respectful. The Ubuntu community and its members treat one another with respect. Everyone can make a valuable contribution to Ubuntu. We may not always agree, but disagreement is no excuse for poor behaviour and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It's important to remember that a community where people feel uncomfortable or threatened is not a productive one. We expect members of the Ubuntu community to be respectful when dealing with other contributors as well as with people outside the Ubuntu project, and with users of Ubuntu. Ignoring so many people for 7 months _is_ disrespectful. Asking if the maintainer cares is mostly a rethorical question, as his actions speak for him. 7 months is a way too large span for now and then. Being less productive than he has being (at least as long as this bug is concerned) is impossible, be it because of our complaints or not. As of expecting this or that, we're expecting for months to no avail. Be collaborative. Ubuntu and Free Software are about collaboration and working together. Collaboration reduces redundancy of work done in the Free Software world, and improves the quality of the software produced. You should aim to collaborate with other Ubuntu maintainers, as well as with the upstream community that is interested in the work you do. Your work should be done transparently and patches from Ubuntu should be given back to the community when they are made, not just when the distribution releases. If you wish to work on new code for existing upstream projects, at least keep those projects informed of your ideas and progress. It may not be possible to get consensus from upstream or even from your colleagues about the correct implementation of an idea, so don't feel obliged to have that agreement before you begin, but at least keep the outside world informed of your work, and publish your work in a way that allows outsiders to test, discuss and contribute to your efforts. Lots of people collaborated with reports, confirmations and fixes to this very bug. By the sheer volume of comments here, there's a huge upstream community that is interested. The transparency was so great we saw through it as if is was nothing. When you disagree, consult others. Disagreements, both political and technical, happen all the time and the Ubuntu community is no exception. The important goal is not to avoid disagreements or differing views but to resolve them constructively. You should turn to the community
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
@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 have the effects, but no more the ttys... :-( Is this the world we created? -- 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/ubuntu-bugs
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
@ 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 usplash as well. It works great for me and it has been reported by several folks that it works for them too :) To can find my post in the forums: * GeForce 1440x900 resolution, virtual terminals and wide usplash-theme-ubuntu http://ubuntuforums.org/showthread.php?t=622018 Though personally I would rather prefer things to work out of the box, so my howto would not be needed at all. If you have more questions, feel free to comment on the aforementioned thread. Friendly, Wiktor -- Registered Linux user #390131 (http://counter.li.org) -- 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/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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. If I try to go back to tty-7, the computer freezes and I have to hard reset. Concerning your suggestion to go to the forums, I will do it for sure (as I always did in the past), but I believe this is a BUG and not a misuse of the OS. Since warty I always had my ttys and I was used to use them very often (before Gutsy...). -- 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/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 your post: of, I am not paying any support and I know what I am getting. This is a community-driven service and sometimes you can find in the community people much more professional than those on the paid support. -- 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/ubuntu-bugs
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 harder on the developers to figure out how to solve the problem. In your particular situation, it comes down to a judgment call whether to post here or the forums. If you believe you have something to contribute that will help the developers fix this bug, you are in the right place. If you're merely troubleshooting your own issues, the forum is the right place. As is true in the rest of life, wisdom is a better guide than knowledge. 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. If I try to go back to tty-7, the computer freezes and I have to hard reset. Here are a few suggestions to isolate the problem. Work them sequentially. Between each, review your log files to see if you get a clue about what's going on. * I've seen behavior you are describing when the BIOS was buggy (sometimes the video card BIOS, sometimes the system BIOS). (Yet another reason to pressure Intel and AMD to open up the BIOS.) Try turning off all power management in X and in your BIOS and see if you get the same results. You might also check with the manufacturer of your computer and see if later BIOS upgrades refer to any issues with suspend to RAM, hibernation, or other power management issues. Leave the power management off while you troubleshoot. * The nvidia-glx driver may be the culprit. Back up /etc/X11/xorg.conf. Disable the proprietary video driver using the Restricted Driver Manager. Reboot to see if the results are the same. * Boot into recovery mode, and run dpkg-reconfigure xserver-xorg, specifying the nv driver instead (the open source driver for nvidia cards). Then reboot as normal to see if the results are the same. Continue to use the nv driver while you troubleshoot. * Perhaps your console configuration is out of whack. Run, as root, dpkg-reconfigure console-setup. Reboot. * [Advanced troubleshooting technique; do only if you are comfortable doing it.] Rename the appropriate files to prevent gdm, xdm, or kdm (as the case may be) from starting. The instructions are in /etc/rc2.d/README. Reboot. * Boot into recovery mode. Run lsmod | grep fb to see what framebuffer drivers you are running. If vesafb and fbcon are not loaded, use modprobe to load them. Use the instructions for fbset to see if you can get a working framebuffer. If you can, something about the modules and drivers loaded with runlevel 2 are interfering with the framebuffer. If you are able to get your framebuffer loaded, undo (one at a time) each of the prior steps to get your machine to where it should be. Report back on results. Loye Young -- 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/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 72 tileblit3584 1 fbcon font9344 1 fbcon bitblit 6912 1 fbcon 3. [EMAIL PROTECTED]:~ $ lsmod | grep agp agpgart35016 1 nvidia 4. I switch to tty-1 with Ctrl-Alt-1. Only on that tty I see the line Loading. Please wait On other tty's there is a blank screen If I go to single-mode user (with telinit 1) the tty screen is good. 5. kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=ead6c453-7721-49c0-ad26-1287c8486460 ro quiet splash vga=791 quiet splash 6. /etc/modules: psmouse mousedev lp /etc/initramfs-tools/modules fbcon vesafb vga16fb 7. Relevant log messages: vesafb: framebuffer at 0xe000, mapped to 0xf888, using 3072k, total 131072k [ 24.264190] vesafb: mode is 1024x768x16, linelength=2048, pages=1 [ 24.264193] vesafb: protected mode interface ino at c000:d5a0 [ 24.264196] vesafb: pmi: set display start = c00cd5d6, set palette = c00cd640 [ 24.264198] vesafb: pmi: ports = 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc 3ce 3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da [ 24.264214] vesafb: scrolling: redraw [ 24.264217] vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0 [ 24.264339] Console: switching to colour frame buffer device 128x48 [ 24.293986] fb0: VESA VGA frame buffer device [ 25.452768] vga16fb: initializing [ 25.452773] vga16fb: mapped to 0xc00a [ 25.452832] fb1: VGA16 VGA frame buffer device 8. I blacklisted vesafb and vga16fb 9. [EMAIL PROTECTED]:~ $ lsmod | grep nv nvidia 4716468 32 agpgart35016 1 nvidia i2c_core 26112 2 nvidia,i2c_nforce2 sata_nv20612 1 libata125168 3 ata_generic,sata_nv,ahci Thank you. Fabio -- 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/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 . When I boot with ubuntu-splash enabled, I get on tty1..6 black screens with randomly spread green squares. Just before the splash appears I can see for a very short time the kernel-output on the screen, so I think the console works before the splash comes up. When I disable the splash I get a blank screen for the first, hm. say 15 seconds, until the kernel loads the vesafb module. It's output is the first appearing on the screen. But then the console works in 1024x768 (which is the native resolution of my LCD). Best regards, Thomas. -- 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/ubuntu-bugs
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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 thread should be about the bug and not about troubleshooting. Fabio has four video drivers loaded: -- vesafb -- vga16fb -- fbcon -- nvidia The correct number is at most THREE. You should not use vga16fb and vesafb at the same time. In Fabio's case, vesafb will probably be the best choice. 1. Go back to /etc/modprobe.d/blacklist-framebuffer and remove the # before the vga16fb line. 2. Remove vga16fb from /etc/initramfs-tools/modules. 3. Add vesafb and fbcon to /etc/modules. The framebuffer mode is probably incorrect on your boot kernel command in /boot/grub/menu.lst. 4. Remove splash vga=791 everywhere it appears in /boot/grub/menu.lst. 5. Run depmod. 6. Run update-initramfs -u 7. Reboot. You should now have your consoles back, but in 640x480 mode. (Sometimes, the graphics card figures out the right thing to do and just works. If it does, don't fix what ain't broke.) Now you want to figure out which framebuffers are best for your card/monitor combination. Run the rest of the commands below from a console, NOT a terminal in X. The following two commands will give you a great deal of information: 8. Run get-edid | parse-edid to get the possible modes for your monitor. 9. Run hwinfo --vbe | less and find the stanzas for the framebuffer and monitor. (For me, they are at the end of the file, so I just press the END key.) ALTERNATIVE 1 -- hwinfo should give you the list of framebuffer modes to put in your boot kernel command and the native resolution of your monitor. Note that not all monitors do such a good job of reporting, so you might have to pull out the documentation and read it to find the best resolution. Usually, a digital LCD should run at 60 Htz (long story that's not worth telling now). Pick the best framebuffer mode for your monitor. If you have a digital LCD, use a resolution that equals the native resolution of your monitor. 10. Edit /boot/grub/menu.lst and insert your chosen vga mode. (You may have to do some trial and error to figure out which is best.) 11. Reboot and see how it comes out. ALTERNATIVE 2 -- get-edid | parse-edid should give you the possible modes for your monitor, if your monitor has a decent implementation of EDID. (My LG 19 Flatron does not work with this, but my Acer 19 widescreen does. YMMV) 10. Run less /etc/fb.modes. Study it and find which stanzas match your monitor as reported by the EDID command. 11. From the console, run fbset [EMAIL PROTECTED], substituting the correct arguments that match fb.modes. Trial and error may be necessary. If your console blanks out and you can't see anything, use Alt-Right or Alt-Left (i.e., the Alt key and the appropriate arrow key pressed simultaneously) to go to another console and try again. If you almost always use the console, Alternative 1 is probably more convenient. If you only occasionally use the console, Alternative 2 is probably for you. Of course, if one works and the other doesn't, use the one that works. Further troubleshooting help requests should be directed to the Ubuntu community help forums, one of the Ubuntu community IRC help channels, or to one of the growing number of companies who provide paid (and usually very reasonably priced) support for Ubuntu. Feel free to plagarize this posting, but remember, you didn't pay for this advice, so if following these instructions turns out badly for you or your machine, it's TFB. Happy Trails, Loye Young Isaac Young Computer Company Laredo, Texas http://www.iycc.biz -- 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/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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) 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/ubuntu-bugs
Re: [Bug 129910] Re: 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 for reporting or helping to fix bugs. To Fabio, You'll need to provide more information for the community to be able to help. Some relevant information would be: 1. Which video driver are you running under X, and which version? 2. Which framebuffer drivers are you running on the console? Open up a virtual terminal (while running X), and type: [code] $ lsmod | grep fb [/code] 3. Are you loading the agpgart module? [code] $ lsmod | grep agp [/code] 4. When you switch to tty, how are you switching? (It turns out that there are several ways to do it, and they have different effects on switching back and forth.) Is the result the same on each of tty1 through tty6? 5. What does your boot command say? (The line towards the end of /boot/grub/menu.lst that starts with kernel for your default boot option) 6. What do the files /etc/modules and /etc/initramfs-tools/modules say? 7. What does your log file say? (Don't send the whole thing, just look for any relevant messages.) 8. Which of the blacklist items did you blacklist? 9. Are you running more than one nvidia video driver? [code] $ lsmod | grep nv [/code] Happy Trails, Loye Young Isaac Young Computer Company Laredo, Texas http://www.iycc.biz -- 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/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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. -- 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/ubuntu-bugs
[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
** 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
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. Have you tried running dpkg-reconfigure xserver-xorg from a terminal when vga=xxx is not specified? 2. I haven't had good luck when running a vesafb AND the card-specific fb driver. Have you tried using only the nvidiafb without vesafb and vice versa? -- Loye Young Isaac Young Computer Company Laredo, Texas http://www.iycc.biz -- 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/ubuntu-bugs
