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