Bugzilla – Bug 4645
after sys-unconfig, cannot see questions due to graphical boot
Last modified: 2009-04-11 23:17:51 UTC
You need to log in before you can comment on or make changes to this bug.
This is found in osol b101a rc1b image. After installing the system, I ran sys-unconfig and reboot the system. After the system reboot, I cannot see any of the sysid questions because happy face is enabled by default. As a workaround, I edit the grub menu as follow to disable happy face: The workaround is to remove the the following line: splashimage /boot/solaris.xpm - need to use d foreground d25f00 - need to use d background 115d93" lines - need to use d and ",console=graphics" in kernel$ line from the GRUB menu - need to use e Then select b and it works.
Could sys-unconfig make a transient grub entry to boot the next time with the text console settings, like reboot -r does?
Recategorizing.
*** Bug 4743 has been marked as a duplicate of this bug. ***
*** Bug 4747 has been marked as a duplicate of this bug. ***
*** Bug 4773 has been marked as a duplicate of this bug. ***
*** Bug 4775 has been marked as a duplicate of this bug. ***
I saw essentially this same problem but on an initial install of my Toshiba R500 laptop. I didn't see a smiley face, but basically got the OSOL 2008.11 background with a "busy" line moving back & forth and nothing more. The workaround from this bug, though, seemed to fix it. Let me know if you want me to test new bits or if you want to see my system.
*** Bug 4895 has been marked as a duplicate of this bug. ***
Adding as a release blocker and raising to P1. This seems really toxic, since sys-unconfig is the only rational way to get the system to participate in a larger network in a lot of environments (such as on Sun's internal network, where participation in NIS is really helpful).
The management decision is to not fix this bug, but instead to implement the workaround of adding a text mode boot prompt (see bug 4673) and release note the sys-unconfig issue. Removing from blocker list.
I will send out the release note.
We've a few CP3020 AMD based blades. After installing osol_0906-106a (or b107 or b108) the system doesn't appear to boot. It does install correctly however this blade, even though its x86, does not have any graphics card. None, zip, nada. Output from scanpci -v will be attached. So on boot the box (blade016 as its named) doesn't appear to boot. Since theres no graphics device we can't simply attach a monitor. Solution was to boot it again over the network, remove all graphics related entries from the grub menu. This allowed us to boot it correctly. - seems to boot correctly with no issues after just 'cleaning' the grub menu - no other work was necessary.
The fix for 6810939 should address the text mode console interaction issue. It does not do anything about the continued existence of sysidconfig.