Re: [opensuse] Re: systemd learning curve ease (was Re: Configuring service runlevels)
Per Jessen wrote:
This is a boot option - used to be called "splash", it might have changed, but I generally remove it.
--- No splash is the graphics... nosplash gives me the blank screen, or recently with newest kernels (3.7 and later) it will give me a half a screen of scrolled output in the upper half of the screen. Um.. you call that splash? I call it messed up output... you say half dozen, I say 6? ;-) It tries to load a frame buffer on my crap, on-board, video card which, with VGA compatibility, doesn't do so well and can, at best do 1280x1024 in 32 bit (on a 16:9 display that came with it! ;-)); To run in 1920x1080 it needs to drop down to 16bit color). It wasn't meant to do graphics. It's outfitted to be run as a server. Same CPU does go in my desktop but there it has graphics (but not much disk space). Only in 12.3 and later have I gotten the half screen -- but that's partly because my card now has a kernel adapter that matches it -- I don't know what mode the half-screen is...maybe it's trying 1920x1080 in 32 bit to match the monitor? Just a guess.. I try not to boot in a graphics or framebuffer mode, usually. It eats memory for a console that isn't going to be used very often. That's what you get when I boot from initrd or if I let it set my console font: a frame buffer that runs slowly with no HW acceleration. Vs. Running in VGA text mode, and it uses HW scrolling @ about 10X the speed (not that either is readable in any detail, but the frame buffer scroll creates a motion blur as a it scrolls up on my screen, whereas the HW scroll does not , though it goes by too fast for anything other than catching anomalies or errors. It doesn't have to switch mode so the graphics monitor never loses sync -- so no missed output during a mode switch. Scrolling is offloaded to the video controller. If it stayed in VGA mode, it wouldn't need to waste memory allocating a frame buffer nor waste cpu resources doing the software scrolling that a frame buffer requires (not that it's alot of memory or cpu, but it's still wasted).
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Linda Walsh wrote:
It tries to load a frame buffer on my crap, on-board, video card which, with VGA compatibility, doesn't do so well and can, at best do 1280x1024 in 32 bit (on a 16:9 display that came with it! ;-)); To run in 1920x1080 it needs to drop down to 16bit color). It wasn't meant to do graphics. It's outfitted to be run as a server. Same CPU does go in my desktop but there it has graphics (but not much disk space).
You can probably avoid all of this by using vga=normal or one of those. A monitor that will fit in a 19" rack rarely does more than 1280x1024 anyway. -- Per Jessen, Zürich (8.2°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
You can probably avoid all of this by using vga=normal or one of those. A monitor that will fit in a 19" rack rarely does more than 1280x1024 anyway.
It came w/the system... not a rack system -- deskside. I use vga=0x30A... Oops.. my comments in lilo.conf says thats 132x43 not 132x50... # modes 0x30A 132x43 # 0x31b - 1280x1024x32 # 0x31c, 0x31d - 1600x1200x16 ---- So have that in the boot config, but it's when it first comes up and hits ...kbd (fbset_params = null, in fbset, so it exits). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Linda Walsh
-
Per Jessen