[opensuse] How to reset vga to nomal on boot?
I've started to get the hang of the booting my next kernel with kexec...as long as I don't really need to look at my boot screen, it seems just fine.. For some reason, the 'vga' setting I have in lilo doesn't work to reset video on the command line, so I end up with a bunch of garbage on the console. I've tried vga=0x942 & 0x30a..both of which work in in lilo, but no reset on the cmd line.... Any special magic (any special console parameters) to get the console into a readable state when booting into a new kernel? Right now have: kexec -l '/boot/vmlinuz-3.6.0-Isht-Van' root=/dev/sdc1 vga=0x942 --append='root=/dev/sdc1 showopts console=ttyS0,115200n8 console=tty0 elevator=cfq pcie_aspm=force pcie_ports=native' Thanks, -linda -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012-10-07 16:30 (GMT-0700) Linda Walsh composed:
Any special magic (any special console parameters) to get the console into a readable state when booting into a new kernel?
You might want to look at https://bugzilla.novell.com/show_bug.cgi?id=675793 as a guide to what you're probably up against. I can't say for sure because I don't intentionally let Lilo (or Grub2) onto any of my systems. When given a choice between no bootloader, Lilo and Grub2 and not Grub Legacy, I choose no bootloader and use some already installed Grub Legacy, or install Grub Legacy using Knoppix, to get me booted. With Grub Legacy I manage between the combination of non-installation of plymouth, splashy & bootsplash, and a video= on cmdline to override KMS automagic on the ttys. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/7/2012 7:43 PM, Felix Miata wrote:
On 2012-10-07 16:30 (GMT-0700) Linda Walsh composed:
Any special magic (any special console parameters) to get the console into a readable state when booting into a new kernel?
You might want to look at https://bugzilla.novell.com/show_bug.cgi?id=675793 as a guide to what you're probably up against. I can't say for sure because I don't intentionally let Lilo (or Grub2) onto any of my systems. When given a choice between no bootloader, Lilo and Grub2 and not Grub Legacy, I choose no bootloader and use some already installed Grub Legacy, or install Grub Legacy using Knoppix, to get me booted.
With Grub Legacy I manage between the combination of non-installation of plymouth, splashy & bootsplash, and a video= on cmdline to override KMS automagic on the ttys.
Crazy you have to go through such hoops. I have to do the same thing. A dead serial console on a remote server is no fun. Especially when you know that, you don't want some new special feature, all you want is what already worked fine until other people worked quite hard to make gfxboot and plymouth and kms do their things and break it. We're supposed to thank them for this progress. We're supposed to thank them for having to replace dirt-cheap, ultra efficient, already-installed, already learned and documented and employees trained, equipment in several remote sites, with new, FAR more expensive, FAR less efficient, not already installed, not even researched let alone purchased let alone tested let alone installed let alone employees trained, ip-kvm equipment to replace all the telnet/ssh serial console servers? And since that's actually outlandishly extravagantly impractical, all I really do is fight against the default system the same way you just described from now to forever. That's all, no big. Why would anyone have a problem with that? -- bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 20 Oct 2012 14:35:10 -0400
"Brian K. White"
Crazy you have to go through such hoops. I have to do the same thing.
A dead serial console on a remote server is no fun.
Console that lynn mentioned is what you get after start booting, not serial console, and which has strange selection of colors in default configuration making it barely readable.
Especially when you know that, you don't want some new special feature, all you want is what already worked fine until other people worked quite hard to make gfxboot and plymouth and kms do their things and break it.
Problem is that number of people reported that upgrade from older system with grub legacy to one with grub2 just used old grub. So it would be interesting to know how can happen to get grub2. I would guess the same way I got mine, installing new installation in separate partition to have old system as fallback solution. In this case system is acting in a usual way, replacing old booting system with a new one. That is how it works since ever.
We're supposed to thank them for this progress. We're supposed to thank them for having to replace dirt-cheap, ultra efficient, ...
'We' has a limited application in this context. Your use case is obviously special case with elaborate remote booting that needs some thoughts before starting any new installation, or upgrade. You are skilled at that, but if you find that you need extra help with your dead cheap solution, I bet you can get some from SUSE, or number of companies that make money from support. I don't think that they will decline to make few bucks. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012-10-20 15:59 (GMT-0500) Rajko composed:
Problem is that number of people reported that upgrade from older system with grub legacy to one with grub2 just used old grub.
That's very rarely a problem. If it's an upgrade, odds are extremely high Grub Legacy worked fine on that system. Whenever that's the case, there's no good reason to switch to the buggy and incompletely-supported-by-openSUSE-configuration-tools Grub2. Grub 2 is v1 software (in spite of its claim to v2.x), as it's a complete rewrite of with minimal similarity to Grub Legacy.
So it would be interesting to know how can happen to get grub2.
It can be selected during installation, same as any other software in the available installation source. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Brian K. White -
Felix Miata -
Linda Walsh -
Rajko