Console font turned cyan
in [Debian]
|
From: Phil Requirements on 11 Apr 2010 03:20 > I don't know when it happened but it must have been during some > "aptitude upgrade" run lately: My console font turned from white to > cyan. At first I thought that the red VGA signal had a bad contact, I was recently experimenting with framebuffer settings, and when I tried certain settings, I got something very similar to what you are describing. Specifically, I got the pale green text when I chose a framebuffer setting of a certain bit depth, and it had the multi-color smeary looking distortion. I wanted my framebuffer to be nice because I use some console apps and I don't always like to run X. I was experimenting with lots of settings. When I tried 1024x768x24, it looks nice. 1024x768x32 is also nice. But when I tried 1024x768x16 or 1024x768x8, the colors were all wrong, and the main console font was a sickly green color. Not quite cyan, but similar. Your framebuffer could have gone on the fritz with your recent update if you changed from grub-legacy to grub-pc (the new grub). The new grub has a different way of setting up framebuffers, you can't use vga=795 any more. If you want to try to chase down a new-grub framebuffer problem, try looking at these: /etc/grub/default GRUB_GFXMODE=1024x768x32 (or whatever you choose) GRUB_TERMINAL update-grub gfxpayload These are just some ideas that I thought might be helpful. Phil -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/20100411070120.GA6472(a)kasploosh.net
From: Tom H on 11 Apr 2010 09:40 On Sun, Apr 11, 2010 at 3:01 AM, Phil Requirements <simultaneous(a)comcast.net> wrote: >> I don't know when it happened but it must have been during some >> "aptitude upgrade" run lately: My console font turned from white to >> cyan. At first I thought that the red VGA signal had a bad contact, > > I was recently experimenting with framebuffer settings, and when I tried certain > settings, I got something very similar to what you are describing. Specifically, > I got the pale green text when I chose a framebuffer setting of a certain bit > depth, and it had the multi-color smeary looking distortion. > > I wanted my framebuffer to be nice because I use some console apps and I > don't always like to run X. I was experimenting with lots of settings. When I > tried 1024x768x24, it looks nice. 1024x768x32 is also nice. > > But when I tried 1024x768x16 or 1024x768x8, the colors were all wrong, and the > main console font was a sickly green color. Not quite cyan, but similar. > > Your framebuffer could have gone on the fritz with your recent update if you > changed from grub-legacy to grub-pc (the new grub). The new grub has a different > way of setting up framebuffers, you can't use vga=795 any more. > > If you want to try to chase down a new-grub framebuffer problem, try looking > at these: > > /etc/grub/default > GRUB_GFXMODE=1024x768x32 (or whatever you choose) > GRUB_TERMINAL > update-grub > gfxpayload Just in case you are running grub2, the /etc/grub/default variables for framebuffer are GRUB_TERMINAL=gfxterm GRUB_GFXMODE=<resolution> GRUB_GFXPAYLOAD_LINUX=[<resolution|keep>] There used to be a warning about using "vga=<resolution>" as a GRUB_CMDLINE_LINUX_DEFAULT or GRUB_CMDLINE_LINUX option (it seems to have been removed or my eyes are too slow to see it) and advice to use GRUB_GFXPAYLOAD, but the latter has now been superceded by the above payload variable. Do you still have this font-color problem if you comment out GRUB_GFXMODE and GRUB_GFXPAYLOAD_LINUX and set "GRUB_TERMINAL=console" (and reboot after running "update-grub")? -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/j2q6d4219cc1004110635o40c8d5baxc3a4003b3ddf2661(a)mail.gmail.com
From: Tom H on 20 Apr 2010 15:30 On Mon, Apr 19, 2010 at 2:37 PM, Robert Latest <boblatest(a)googlemail.com> wrote: > On Sun, Apr 11, 2010 at 3:35 PM, Tom H <tomh0665(a)gmail.com> wrote: >> On Sun, Apr 11, 2010 at 3:01 AM, Phil Requirements >> <simultaneous(a)comcast.net> wrote: > >> Just in case you are running grub2, the /etc/grub/default variables >> for framebuffer are > > I needed that hint, too. Between muckings around with GRUB's config I > keep forgetting that the settings are not in menu.lst, nor in > /etc/grub.d but in /etc/grub/defaults. IMO the whole new GRUB system > is suffering from incredible bloat, but maybe I'm just not seeing the > benefits. > BTW, if "vga=" doesn't cut it any more, how is stuff passed to the > kernel nowadays? You only need to edit /etc/default/grub and run update-grub in order to modify /boot/grub/grub.cfg (theoretically; unfortunately, you have to edit /etc/grub.d/10_linux or /etc/grub.d/30_os-prober to change the default generation of the menu entry names or prevent os-prober from picking up a windows recovery partition), The squeeze and sid kernels set the graphic mode through Kernel-based Mode Setting (KMS). I only use headless and Xless boxes so I have not looked into whether the kernel uses grub2's GRUB_GFXMODE OR GRUB_GFXPAYLOAD_LINUX variables to set the video mode. KMS can be turned off in grub.cfg with either "nomodeset" (possibly superceded) or "<video>.modeset=0" where video=i915|i945|nouveau|radeon... but I have only gleaned this from reading Fedora and Ubuntu stuff. -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/k2n6d4219cc1004201220i27c29909x78a487a0d4374441(a)mail.gmail.com
|
Pages: 1 Prev: Debian Lenny + Grub2 + kernel message log capturing Next: Boot / LVM best practices |