Re: [opensuse] How do I turn off frame-buff switch on boot ??
Aaron Kulkis wrote:
boot to runlevel 3 by either...
Thank-you, but I was obviously unclear. Sorry, I'll explain in more detail... I already run in mode 3, but in mode 3, the system is still using a 'frame buffer' rather than an SVGA text mode. The switch to frame buffer seems to happen when grub starts and displays a graphical menu rather than a text menu. From there, it's all downhill -- they system boot using a framebuffer, I don't see the actually boot text coming out to the console reliably or, right now, at all. Normally, whether or not you see boot text or a snazzy boot screen, depends on the setting of the verbose parameter to the kernel in the boot file. But either way, snazzy screen or scrolled text in a framed area -- it's a frame buffer and not actually using the hardware's internal text modes. So when the hardware switch modes into the framebuffer, information is visually lost (though can be perused later in a log if you want to go back and check every time but when looking for problems, I prefer to see the actual text on the screen wizzes by ... though it's getting harder to read these days, usually the hardware scrollingis synced with the screen refresh and scrolls a line at a time, vs. the frame buffer,I think, doing smooth scrolling via bit-shifting (but not sure about that). Anyway...I'd prefer it boot normally and not use the frame buffer during boot. It's not reliable -- due to the lost output -- and, right now, I don't get anyoutput at all -- I just get a blank screen f from the time the boot starts till I get a login prompt -- I don't even see services start. Does this make my question more clear? -linda -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Linda Walsh
Anyway...I'd prefer it boot normally and not use the frame buffer during boot. It's not reliable -- due to the lost output -- and, right now, I don't get anyoutput at all -- I just get a blank screen f from the time the boot starts till I get a login prompt -- I don't even see services start.
Did you try adding/changing the vga= line when booting to vga=normal? You can try it on the grub command line to see if it satisfies you and then edit /boot/grub/menu.lst to make the change permanent. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2009/10/27 18:50 (GMT-0700) Linda Walsh composed:
I already run in mode 3, but in mode 3, the system is still using a 'frame buffer' rather than an SVGA text mode. The switch to frame buffer seems to happen when grub starts and displays a graphical menu rather than a text menu.
AFAIK, there is no such thing as framebuffer prior to kernel taking control from Grub. The graphical mode Grub uses AFAIK is setup by the installer to use either a native video mode or a common VESA mode, typically graphical 1024x768. NAICT, if Grub uses a 1024x768 video mode while the Grub kernel line contains 791 (or its 16 bit hex twin 0x317) or other 1024x768 framebuffer mode there won't be any material "loss" on switching from Grub to kernel video control, unless a graphical boot splash curtain is allowed to alter or hide the messages.
From there, it's all downhill -- they system boot using a framebuffer, I don't see the actually boot text coming out to the console reliably or, right now, at all.
What is your gfxcard chip?
Normally, whether or not you see boot text or a snazzy boot screen, depends on the setting of the verbose parameter to the kernel in the boot file.
AFAICT, all you need to permit all kernel/init messages is to not use quiet on the Grub kernel line. To actually see them needs either a bootsplash that actually works right, or no bootsplash at all.
But either way, snazzy screen or scrolled text in a framed area
The framed area usually is a bootsplash thing. Turn that bling off and you get good framebuffer output speed and no shrunken "output" window.
-- it's a frame buffer and not actually using the hardware's internal text modes. [...] Anyway...I'd prefer it boot normally and not use the frame buffer during boot. It's not reliable -- due to the lost output -- and, right now, I don't get anyoutput at all -- I just get a blank screen f from the time the boot starts till I get a login prompt -- I don't even see services start.
That's broken bootsplash. -- " A patriot without religion . . . is as great a paradox, as an honest man without the fear of God. . . . 2nd U.S. President, John Adams Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 27 October 2009 08:50:47 pm Linda Walsh wrote:
Aaron Kulkis wrote:
boot to runlevel 3 by either...
---- Thank-you, but I was obviously unclear. Sorry, I'll explain in more detail...
I already run in mode 3, but in mode 3, the system is still using a 'frame buffer' rather than an SVGA text mode. The switch to frame buffer seems to happen when grub starts and displays a graphical menu rather than a text menu. From there, it's all downhill -- they system boot using a framebuffer, I don't see the actually boot text coming out to the console reliably or, right now, at all.
Normally, whether or not you see boot text or a snazzy boot screen, depends on the setting of the verbose parameter to the kernel in the boot file. But either way, snazzy screen or scrolled text in a framed area -- it's a frame buffer and not actually using the hardware's internal text modes.
So when the hardware switch modes into the framebuffer, information is visually lost (though can be perused later in a log if you want to go back and check every time but when looking for problems, I prefer to see the actual text on the screen wizzes by ... though it's getting harder to read these days, usually the hardware scrollingis synced with the screen refresh and scrolls a line at a time, vs. the frame buffer,I think, doing smooth scrolling via bit-shifting (but not sure about that).
Anyway...I'd prefer it boot normally and not use the frame buffer during boot. It's not reliable -- due to the lost output -- and, right now, I don't get anyoutput at all -- I just get a blank screen f from the time the boot starts till I get a login prompt -- I don't even see services start.
Does this make my question more clear?
-linda
Yes, /boot/grub/menu.lst Change all splashes to 'splash=0' IIRC That disable all the framebuffers and you will just see the plain text whizzing by on a plain black console. No cute little gray dots all over the place. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 28 Oct 2009 01:50:47 Linda Walsh wrote:
Aaron Kulkis wrote:
boot to runlevel 3 by either...
---- Thank-you, but I was obviously unclear. Sorry, I'll explain in more detail...
I already run in mode 3, but in mode 3, the system is still using a 'frame buffer' rather than an SVGA text mode. The switch to frame buffer seems to happen when grub starts and displays a graphical menu rather than a text menu. From there, it's all downhill -- they system boot using a framebuffer, I don't see the actually boot text coming out to the console reliably or, right now, at all.
Normally, whether or not you see boot text or a snazzy boot screen, depends on the setting of the verbose parameter to the kernel in the boot file. But either way, snazzy screen or scrolled text in a framed area -- it's a frame buffer and not actually using the hardware's internal text modes.
So when the hardware switch modes into the framebuffer, information is visually lost (though can be perused later in a log if you want to go back and check every time but when looking for problems, I prefer to see the actual text on the screen wizzes by ... though it's getting harder to read these days, usually the hardware scrollingis synced with the screen refresh and scrolls a line at a time, vs. the frame buffer,I think, doing smooth scrolling via bit-shifting (but not sure about that).
Anyway...I'd prefer it boot normally and not use the frame buffer during boot. It's not reliable -- due to the lost output -- and, right now, I don't get anyoutput at all -- I just get a blank screen f from the time the boot starts till I get a login prompt -- I don't even see services start.
Does this make my question more clear?
-linda
The real simple one is hit the "Esc" key as the frame buffer screen opens bingo back to text mode , This is the only way i can get 11.2RC1 to boot fully right now init 3 on the grub boot line then Esc as soon as it goes frame buffer all the boot process in all it's glory . Pete . -- Powered by openSUSE 11.2 Milestone 2 (x86_64) Kernel: 2.6.30-rc6-git3-4- default KDE: 4.2.86 (KDE 4.2.86 (KDE 4.3 >= 20090514)) "release 1" 08:23 up 1 day 12:17, 3 users, load average: 0.02, 0.06, 0.01
On Wed, 28 Oct 2009, 09:25:24 +0100, Peter Nikolic wrote:
[...] The real simple one is hit the "Esc" key as the frame buffer screen opens bingo back to text mode , This is the only way i can get 11.2RC1 to boot fully right now init 3 on the grub boot line then Esc as soon as it goes frame buffer all the boot process in all it's glory .
If you don't want GRUB to display a graphical message at all, just comment (or remove) the line gfxmenu (hdx,y)/message in your /boot/grub/menu.lst file.
Pete .
HTH, cheers. l8er manfred -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
David C. Rankin -
Felix Miata -
Linda Walsh -
Manfred Hollstein -
Patrick Shanahan -
Peter Nikolic