Hi, Is there a variable I can check from the loader prompt to check the value of OsConsole?
On Thu, Aug 28, 2025 at 7:06 AM Peter Tribble <[email protected]> wrote: > On Thu, Aug 28, 2025 at 4:56 AM Atiq Rahman <[email protected]> wrote: > >> *Even though subject is: OmniOS CE (bloody-20250709) usb image hangs, >> please note that stable release r151054 is also broken, repros same result* >> >> Hi Dan, >> Thanks for all the help. >> >> > I assume you did see “Booting..” text, then it cleared the screen and >> thats it. >> Yep, I did see that (a few lines including booting) before it showed the >> cursor only screen. (photo: p1) >> > > That looks exactly like what happens when the system decides that the > console ought > to go somewhere else, such as a serial port. (I've had reports of this > happening with > OmniOS on some cloud providers.) > > So, what does loader think OsConsole is set to? > > >> > ok framebuffer get >> output on photo (p2) >> >> ok show efi-version >> 2.90 >> >> > BIOS mode (CSM) if the system does support it. >> It doesn't support CSM. >> >> > ok set boot_resolution=“800x600” >> > ok set prom_debug=true >> > ok set kbm_debug=true >> > ok boot -kv >> same result (big cursor on top left). Native screen resolution is 4K >> (3840x2400). I also tried other 16:10 resolutions, for example, 1920x1200 >> neither of which led to a successful installer screen. >> >> > see if there is more visible output after boot command. >> Nope >> >> Unfortunately, I am getting busier. I will probably stop experimenting >> with >> OmniOS for now and stick to the OI text installer. I thought, for me, >> OmniOS, >> OI don't make any difference; I have no GUI anyways! So I thought would >> try >> OmniOS but this installer image is a blocker. I might give it a shot on >> the next >> OmniOS release. >> >> >> Sincerely, >> >> Atiq >> >> >> >> On Wed, Aug 27, 2025 at 12:51 AM Toomas Soome via illumos-developer < >> [email protected]> wrote: >> >>> >>> >>> On 27. Aug 2025, at 04:40, Atiq Rahman <[email protected]> wrote: >>> >>> (changing subject because this time I only tried bloody image; >>> motivation: more up to date image in case it fixes things) >>> >>> Hi, >>> Thanks for the replies on this boot image issue. >>> >>> So I booted omnios-bloody-20250709. Answers below, >>> >>> > 1. do you get boot loader operational - that is, get menu on screen, >>> press esc to get to ok prompt, are commands like ls, lsdev working? >>> yep (photo 1 attached) >>> >>> >>> btw: lsdev -v will show pool details as well (including bootfs dataset >>> name). >>> >>> > 2. from loader ok prompt, enter: start — this will load kernel and >>> modules, use lsmod -s to check list of loaded modules and their checksums. >>> yep, this is working as well (photo 2 attached) >>> >>> >>> >>> btw: checksums are sha1 (and boot_archive hash does match with one from >>> boot_archive.hash). >>> >>> >>> > 3. enter: boot -kv -B prom_debug=true,kbm_debug=true — this should >>> spam a console a lot, but if we get the hung system, we will have some idea >>> where this is happening. (photo 3 attached) >>> >>> >>> ok, this is not good. I assume you did see “Booting..” text, then it >>> cleared the screen and thats it. >>> >>> No spamming on the screen. Like before it immediately brings up that >>> blank screen with a big cursor on top of the left of the screen. >>> >>> Also, fonts (bootloader menu) are zoomed out looking bigger on the >>> screen on the initial screen. The OI Hipster bootloader menu appears more >>> natural than this. (photo 4) >>> >>> >>> omnios devs did decide to use fixed size screens (not defaulting on what >>> hardware has): >>> >>> /boot/defaults/loader.conf: >>> >>> >>> loader_resolution="800x600" # The resolution of the loader menu >>> screen >>> >>> loader_font="10x18" # The font used for the loader menu >>> screen >>> >>> boot_resolution="1024x768" # The resolution set before booting the >>> system >>> >>> boot_font="10x18" # The font selected before booting the >>> system >>> >>> >>> To try to diagnose it a bit more, lets try to tell it to not change the >>> resolution: >>> ... >>> As you are running UEFI mode, try booting with BIOS mode (CSM) if the >>> system does support it. >>> >>> The problem with such issue is about to get the information out of the >>> system. You have no serial ports, so the only option right now is to get >>> the output on screen. >>> >>> rgds, >>> toomas >>> >>
_______________________________________________ oi-dev mailing list [email protected] https://openindiana.org/mailman/listinfo/oi-dev
