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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
On Friday 11 January 2008 21:23:54 Paul Dufresne wrote: Almost no one have reported this problem on Hardy (I have checked all duplicates, and they are all about Gutsy I'm on Hardy, ever since Alpha 1, and I had this prob the all time up until last week, when I MANUALLY fixed it with the step provided in the bug reports. -- BUGabundo :o) (``-_-´´) http://Ubuntu.BUGabundo.net Linux user #443786GPG key 1024D/A1784EBB My new micro-blog @ http://BUGabundo.net ps. My emails tend to sound authority and aggressive. I'm sorry in advance. I'll try to be more assertive as time goes by... -- 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)
On Sat, Jan 12, 2008 at 08:02:43AM -, Timo Aaltonen wrote : Those who have changed the default configuration and thus cannot use the console. There. *Cough* . You must be joking. This is not $whatever_random_modification that is likely to make the part of your system you are configuring actually not working. It's nothing more than expecting a piece of software that has been working for ages to do its work properly. One sometimes calls that a regression. And a severe one as as the activity on this bug shows, it's 1/ widely used and 2/ affects every single ubuntu user. Please don't try to make it look as if users were doing some evil setup that is perfectly known as harmful. -- 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. -- Albin Tonnerre, aka Lutin - Search a little longer, travel a little further -- 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)
On Fri, 2008-01-11 at 23:24 +, Timo Aaltonen wrote: Andrea, you were right the first time, medium is the right importance: https://wiki.ubuntu.com/Bugs/Importance Lacking a framebuffer console is not an issue that makes your machine explode. Yes, I know but it was going to become a difficult situation :) Thanks for your assistance. -- 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)
@ andrew You have to understand that we normally don't fix bugs in a version that was released. Then why do we claim that we support any release? I really hope that you were speaking off-the-cuff. Deciding not to fix bugs (even with the exception of security fixes) means that we DON'T support the release, and every release is at the end of life the day it's released. The wiki page on Time Based Releases (https://wiki.ubuntu.com/TimeBasedReleases) describes a policy that is, fortunately, somewhat more flexible: What kind of changes are appropriate to make in a released version of Ubuntu? We only update packages for specific types of changes: * Fixes for security vulnerabilities * Other high-impact bug fixes, for example those which cause data loss * Very conservative, unintrusive bug fixes with substantial benefit and very low risk This bug clearly falls into the second category, and I would argue it falls into the third category as well. I can't think of many more high-impact bugs than a broken console. Despite our best efforts to making it more user friendly, Ubuntu and every other GNU/Linux system, needs the command line. This is especially true when dealing with problems with graphics cards and monitors, because the command line is all you have if you can't get X to operate correctly. My users run into this relatively frequently. Example: Example 1: Pancho buys a slick new IYCC Laredo Cuadrado desktop computer with 19 widescreen, preinstalled with Ubuntu and preconfigured for the graphics card and monitor. He gives it to Dario, his 15 year old son, who sets it up in his room. The family decides they want to play an online game in the living room, so Dario disconnects the monitor and carries it by the integrated front panel handle to the living room and hooks it up to the 30 LCD monitor/television in the living room. When he fires it up, everything boots up, but when X starts, the monitor gives and Out of Range error, meaning not even displayconfig-gtk is visible. He wants to use the console to run dpkg-reconfigure xserver-xorg, but alas, the console doesn't show anything, just a black screen staring at him. Example 2: Laredo Trucking Co. buys three Laredo Cuadrado desktops for their offices, again with the 19 screens. The cleaning guy knocks over the monitor one night, leaving it in a dozen pieces on the floor. After cleaning it up, the boss sends his secretary out to Best Buy to buy a monitor. She picks up another LCD monitor, but they were out of 19 wide screens, so she gets a 17 regular 4x3 LCD monitor. They fire it up, but X won't start. The IT guy wants to configure the xserver, but can't because the console doesn't work. Example 3: Ubuntu ships an updated version of a driver, xserver-xorg, displayconfig-gtk, or any of a number of packages needed to make X work. Unfortunately, the update overwrites a configuration file or has some other bug that prevents X from starting. Again, the console is broken, so there's not much he can do. Example 4: The upgrade script from Gutsy to Hardy breaks the computer (like the script for Kubuntu broke many computers upgrading from Feisty to Gutsy). Getting the computer working again merely requires running aptitude update and aptitude full-upgrade from the command line, but the console is invisible, so the user has to first fix the console to be able to fix his system. This bug also meets the second criteria, because a conservative, unobtrusive, low-risk fix is available. From what I've seen here, using the vesafb works very well, even with proprietary graphics drivers. But assuming arguendo that they conflict and further assuming that the community decided to let the proprietary tail wag the open-source dog, it would not be too terribly hard to come up with SOME sort of fix that at the very least allowed the user to work on the console. If the powers that be STILL have a problem with a default boot that allows the user to operate a console when X is running, we could at least make some accomodation by creating an option in GRUB that boots up the system into a command line environment (with networking and other background services loaded as usual), but doesn't start X. Then the user could work on the command line to the user's content and if necessary, execute startx to load X. (BTW, if you really, really don't think the console is worth keeping, then it would make more sense not to load tty 1 through 6 in the first place. Running six tty sessions uses up memory and state, and loading them slows down booting. If the console has no benefit, then there is no reason to pay for it in system resources.) I'm at a loss to understand why the kernel team is so adamently hostile to getting the console working. -- Loye Young Isaac Young Computer Company Laredo, Texas (956) 857-1172 [EMAIL PROTECTED] -- Blank ttys when using vesafb (vga=xxx) https://bugs.launchpad.net/bugs/129910 You received this bug notification because you are
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
On Thu, 2008-01-10 at 20:42 +, Andrew Conkling wrote: I get that. I asked because Andrea Corbellini had mentioned the latest updates while changing the importance of Hardy, so, I'm not sure, I thought he was talking about the latest Hardy updates. If (he could confirm and) you could test it on Hardy, and it works there, then maybe we could see about a possible backport to fix this? I was speaking about latest Hardy updates but it seems the fix was unwilling because this bug still open. I've changed the importance because this bug is not critical 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 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)
On Jan 11, 2008 1:54 PM, klerfayt [EMAIL PROTECTED] wrote: I know this is not the best place to ask question, but - is there a wiki or something that explains all this console/framebuffer/what_ever_is_this_tty_really_called stuff in layman's terms? Yes, there are, though it's a bit more complicated than it appears on the surface. I mentioned a few in an earlier post, but you might also want to look at: http://homer.iycc.biz/cgi-bin/dwww?type=runmanlocation=console/4 http://homer.iycc.biz/cgi-bin/dwww/usr/share/doc/HOWTO/en-html/Keyboard-and-Console-HOWTO.html http://homer.iycc.biz/cgi-bin/dwww/usr/share/doc/HOWTO/en-html/Text-Terminal-HOWTO.html Happy Trails, Loye -- 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)
Andrea, I have to set the importance Did someone die and made you BDFL? critical to bugs which are really critical. It's one thing to mark something as less than critical; it's another to mark it as declined altogether. Loye -- Blank ttys when using vesafb (vga=xxx) https://bugs.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)
On Fri, Jan 11, 2008 at 08:02:33PM -, Andrea Corbellini wrote : @Loye Young: I'm sorry for your company, but I have to set the importance critical to bugs which are really critical. -- Blank ttys when using vesafb (vga=xxx) https://bugs.launchpad.net/bugs/129910 You received this bug notification because you are a direct subscriber of the bug. The very nature of this bug, its activity and the number of duplicates it has clearly show that this is not a trivial bug. It sure deserves a status higher the 'Medium' Please remembert that the kernel team hasn't been able to provide a single answer, even though this bug has gotten the highest priority for SEVERAL months. If you want the bug never to get fixed, just go ahead, and have fun. But it's plain silly -- Albin Tonnerre, aka Lutin - Search a little longer, travel a little further -- 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)
I know this is not the best place to ask question, but - is there a wiki or something that explains all this console/framebuffer/what_ever_is_this_tty_really_called stuff in layman's terms? On Jan 11, 2008 9:39 PM, Loye Young [EMAIL PROTECTED] wrote: To Andrea Corbellini, I've changed the importance because this bug is not critical at all. It may not be important to you, but I am not keen on my company selling computers with a broken console. Remember that you aren't the only fish in this pond, Andrea. You might not care about this bug or the people it affects, but the many people who have commented on it and its many duplicates DO care. Happy Trails, Loye Young -- 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 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 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 Andrea Corbellini, I've changed the importance because this bug is not critical at all. It may not be important to you, but I am not keen on my company selling computers with a broken console. Remember that you aren't the only fish in this pond, Andrea. You might not care about this bug or the people it affects, but the many people who have commented on it and its many duplicates DO care. Happy Trails, Loye Young -- 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
Re: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)
On Jan 11, 2008 4:23 PM, Paul Dufresne [EMAIL PROTECTED] wrote: You have to understand that we normally don't fix bugs in a version that was released. Only in exceptional case this is done, and the conditions for doing so are described at: https://wiki.ubuntu.com/StableReleaseUpdates Bug importance are described at: https://wiki.ubuntu.com/Bugs/Importance One could argue that it should be low because it has many easy workarounds: -don't use vga=xxx -use the terminal in graphics mode rather than real virtual terminals -and the one consisting at modifying initramfs modules to load fbcon and vesa But as it affects many people, well yes, medium seems fair. Agreed. Also, questions about this can be addressed on the bugsquad list: https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad. And let's 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 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)
Andrew Conkling a écrit : And let's keep in mind the Ubuntu Code of Conduct: http://www.ubuntu.com/community/conduct. And let's stop invoking the CoC each time someone doesn't agree, please... Btw, where are the offending words? -- Lionel Le Folgoc - https://launchpad.net/~mrpouit EEBA 555E 0CDE 92BB 3AF4 4AB3 45A0 357B 5179 5910 -- 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)
On Fri, Jan 11, 2008 at 09:23:54PM -, Paul Dufresne wrote : You have to understand that we normally don't fix bugs in a version that was released. You have to understand that I'm part of MOTU and thus do know what a SRU is, thanks. Only in exceptional case this is done, and the conditions for doing so are described at: https://wiki.ubuntu.com/StableReleaseUpdates I see. A non-usable framebuffer for basically evey ubuntu user is actually a very, very common bug. My mistake Among the conditions, the following: An explanation of how the bug has been addressed in the development branch, including the relevant version numbers of packages modified in order to implement the fix; generally, SRUs will not be accepted if the bug has not been fixed in the development branch. Almost no one have reported this problem on Hardy (I have checked all duplicates, and they are all about Gutsy, except mine: bug #162400, which I am not sure is a duplicate, because I have no screen, even without VGA=xxx option, which I seems to be alone in that situation). Bug importance are described at: https://wiki.ubuntu.com/Bugs/Importance One could argue that it should be low because it has many easy workarounds: -don't use vga=xxx This is for people who are too lazy to apply the fix. Until someone tells me why I shouldn't use the framebuffer, which is, let's be honest, quite handy if you want to work properly with your consoles, I see no reason why this would be a proper fix -use the terminal in graphics mode rather than real virtual terminals Btw, it prevents you from seeing usplash. Just use usplash at the lower res then, with svgalib. woot. -and the one consisting at modifying initramfs modules to load fbcon and vesa But as it affects many people, well yes, medium seems fair. Why in hell is that so hard for the kernel team to just comment on the solution, and possibly tell us why this should or should not be done, and eventually fix the thing or definitely mark it as a won't fix ?. Oh, wait. I was dreaming. Nevermind. A new alpha version of Hardy have just come out: Alpha 3. Please consult http://www.ubuntu.com/testing/ , download alpha 3 CD and test how it works for you with it, and report results here. -- 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. -- Albin Tonnerre, aka Lutin - Search a little longer, travel a little further -- 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)
So you tried on Hardy then? -Original Message- From: Loye Young [EMAIL PROTECTED] Date: Thu, 10 Jan 2008 04:25:41 To:[EMAIL PROTECTED] Subject: [Bug 129910] Re: Blank ttys when using vesafb (vga=xxx) I'm not sure what you mean by fixed . . . with latest updates, because the console is still broken unless the user has the inclination and ability to do some hacking. With latest updates the default installation still doesn't allow better than 80x25 on the console, because the framebuffer is blacklisted and nothing takes its place. It is possible to re-engineer the box to get the console working again, but that's not a fix, just a workaround for us in the geek-speak- enlightened club. rant The SVGA standard for 1024 × 768 resolution at 256 colors was released in 1990. Here we are 18 years later running the most advanced, cutting edge kernel on the planet, but we're back to hacking the kernel to get the humble, text-mode tty console working properly. WTF? /rant Bottom line: this bug ain't fixed. 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 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 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)
Le jeudi 10 janvier 2008 à 16:20 +, mozdevil a écrit : Using kernel 2.6.22-14-386 VGA controller: Intel 82945G/GZ rev 02 Solution does not work for me: 1. comment the blacklist vesafb (but leave uncommented every others) line in /etc/modprobe.d/blacklist-framebuffer 2. add fbcon and vesafb in /etc/initramfs-tools/modules 3. add the vga=xxx in your boot list, and i find the font prettier than in the nvidiafb What works though is manually modprobing vesafb and fbcon Did you update your initramfs? sudo update-initramfs -u -k all This should work -- 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)
On Jan 10, 2008 3:21 PM, Loye Young [EMAIL PROTECTED] wrote: @ Andrew So you tried on Hardy then? No. This bug was filed against Gutsy, and it's still a bug against Gutsy. I don't know what would possess anyone to mark it declined for Gutsy. The EOL date for Gutsy isn't until April 2009. Until then, basic functionality of the OS that's broken should be fixed, especially when how to fix the problem is widely known. I get that. I asked because Andrea Corbellini had mentioned the latest updates while changing the importance of Hardy, so, I'm not sure, I thought he was talking about the latest Hardy updates. If (he could confirm and) you could test it on Hardy, and it works there, then maybe we could see about a possible backport to fix this? Also, maybe it was declined because we'd need to release a new kernel package and that wouldn't be possible for this? Again, I'm not sure, just thinking out loud. -- 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)
i update day and day. i fixed in each version. my note book is Thinkpad r50e with intel i810 card Andrea Corbellini 写道: This seems fixed to me with latest updates. Can you confirm this happens also to you? ** Changed in: initramfs-tools (Ubuntu Hardy) Importance: Critical = Medium -- 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)
klerfayt wrote: video= ... boot option will do nothing in ubuntu There's nothing proprietary about Ubuntu's implementation of the kernel or the video stack. video=... is a feature of the vesafb (and similar) framebuffer driver. If the driver is loaded at boot time, as I described, it should work. I've been experimenting with it and found that it does more than nothing. :-) On a slightly different tack, I haven't taken a look at the specifics of how the kernel is compiled to see what effect that has on the framebuffer. If someone knows or has the opportunity to look, it would be helpful. 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 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)
Le jeudi 20 décembre 2007 à 11:49 +, Goodness a écrit : No, it is writen in the settings ## additional options to use with the default boot option, but not with the ## alternatives ## e.g. defoptions=vga=791 resume=/dev/hda5 # defoptions=quiet vga=0x0307 The lines that begin with a # are comments. -- 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)
i also updated to new kernel yesterday. i add vga=792 to new kernel setting. it works, but under new kernel. my sound card does not works, oh. God. i now do not have time to fix it. so i go back to .13 kernel so i want to recommend, backup your older kernels. may be one day you will need it. ;) Goodness 写道: So, today a new kernel-image has installed and dthe same problem again, no output at the booting system. What can i do? -- Blank ttys when using vesafb (vga=xxx) https://bugs.launchpad.net/bugs/129910 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug 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)
-- 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)
Calm down, guys. At least as far as we have our standard 80x24 terminals working. This issue is not an xorg driver issue, as Timo already noted. This issue is caused because the kernel devs have blacklisted all the framebuffer modules. As the modules have been knowingly blacklisted, this can be deemed as a feature, not a bug. Let's see what we gain: $ head -3 /etc/modprobe.d/blacklist-framebuffer # Framebuffer drivers are generally buggy and poorly-supported, and cause # suspend failures, kernel panics and general mayhem. For this reason we # never load them automatically. OK, so all framebuffer modules are blacklisted for a reason. The questions I ask are: 1) Are all the fb modules of such a low quality? 2) Can we afford putting the best supported modules back in, so that some users will still be able to use nice high-res ttys? 3) Is suspend/hibernate working better in gutsy because of the general blacklisting? 4) If one blacklists fb drivers due to suspend/resume woes, should we take the next step and blacklist fglrx because it doesn's support SLUB allocator? Ok, ok, forgive my sarcasm on my last question. Kyle M Weller escribió: Why is this marked invalid? This obviously effects Ubuntu Gutsy so marking it invalid is an invalid decision -- Miguel Martínez Canales Dto. Física de la Materia Condensada UPV/EHU Facultad de Ciencia y Tecnología Apdo. 644 48080 Bilbao (Spain) Fax: +34 94 601 3500 Tlf: +34 94 601 5326 If you have an apple and I have an apple and we exchange these apples then you and I will still each have one apple. But if you have an idea and I have an idea and we exchange these ideas, then each of us will have two ideas. George Bernard Shaw -- 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)
Invalid is an approach or example that is flawed and does not lead to the correct solution of the problem. An invalid approach would be to simplify the expression from left to right, disregarding the order of operations. A valid approach would be to simplify the expression using the order of operations Why is this marked invalid? This obviously effects Ubuntu Gutsy so marking it invalid is an invalid decision On Dec 12, 2007 6:46 PM, Leann Ogasawara [EMAIL PROTECTED] wrote: linux-source-2.6.22 won't be in Hardy, flipping status to Invalid. ** Changed in: linux-source-2.6.22 (Ubuntu Hardy) Status: New = Invalid -- Blank ttys when using vesafb (vga=xxx) https://bugs.launchpad.net/bugs/129910 You received this bug notification because you are a 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 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)
For me it's been enough to remove the vga=xxx option to restore the full functionality of the ttys. I've got an Acer Aspire 5680 laptop, with NVIDIA GeForce Go 7600SE graphics card and Ubuntu Gutsy Desktop x86. BTW, the vga=xxx option is set easily by the StartUp-Manager, who I think was the first to set the vga option. It was not preinstalled by default in Ubuntu, I installed it a little after the installation from the repositories: that's why at the beginning my ttys worked, and then no more. 2007/12/11, Dave Steinberg [EMAIL PROTECTED]: MOM's fix worked for me, too. Thanks! I'm running 7.10 with Linux 2.6.22-14-generic on AMD64, using an Intel 945GM graphics adapter. -- Blank ttys when using vesafb (vga=xxx) https://bugs.launchpad.net/bugs/129910 You received this bug notification because you are a direct subscriber of the bug. -- Elio Killer Behind You Alpha4 -- 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
