> I believe I have a working scratch install of S10u2 on my new server > box, but when I boot it, after relatively few seconds I get a message > on the screen that X login screen is coming and I should wait for it. > Then the screen blanks, and I cannot talk to the system through the > keyboard again. I don't currently have it on a LAN so I have no > *other* way to talk to it (but I notice that the default tools > installed don't include sshd anyway). > > During the install, it went into graphics mode fine, and seemed to > find the name of the video card and be happy with it.
It was using the "Xsun" X11 server at install time. When the system is installed to HDD, it defaults to the "Xorg" X11 server. > So, short-term I want to turn off X login and just work through the > console. I might be able to type fast enough to do that before the > login screen comes up, if I knew the commands. > It'd be an svcadmin disable <something> type of command? For some value > of <something>? Try to boot into single user mode, by editing the boot command line on the initial grub boot screen; add a "-s" option at the end of the "kernel .. multiboot" line. Login with the root password in single user mode, and try to fix the X11 server setup. What probably works is switching back from "Xorg" to the "Xsun" server. This can be done by running the command "kdmconfig". Follow the instructions on the first screen. You can also change various "Xsun" settings from within "kdmconfig". Or you have to find out why "Xorg" fails, and fix the Xorg X11 server setup. You have to look at the /var/log/Xorg.0.log and /var/dt/Xerrors file for possible errors, and maybe construct a custom /etc/X11/xorg.conf file in case the Xorg autoconfiguration has failed. An initial xorg.conf file template can be constructed by running /usr/X11/bin/xorgconfig or /usr/X11/bin/Xorg -configure > Anybody have any idea what? I think of "XDM" as the thing that > provides X login screens at consoles. Is there a way to disable it by > editing files in failsafe mode instead of trying to race with the X > login screen? > > Long-term I guess I want to get X really working, but that can wait > until I can see my system and install software and so forth. > > I'm just starting to review the SMF section in the administrator's > guide, we'll see if that clues me. > > The "failsafe" environment is really icky. No command-line editing or > command recall or filename completion, Yep, the failsafe miniroot starts a standard /bin/sh bourne shell, so no command line editing. I think you can exec a "ksh" or "csh", both should be available in the failsafe environment. These shells could be configured to support command line editing or command recall or filename completion, but... > and more doesn't even work; > it seems to exit at the end of the first screen. I'm hoping not to spend > much time there. A known bug, this was broken the day newboot appeared in Solaris x86. I filed bug 6342722: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6342722 The fix is quite simple, but noone seems to care... The "exec </dev/console >/dev/console 2>&1" in the /sbin/sulogin script in the miniroot archive needs to be fixed;stdin/stdout/stderr should all be opened in read/write mode. I think the source for the /sbin/sulogin shell script isn't part of "OpenSolaris". Workaround is to run the following command before trying to use "more" in the failsafe environment: exec 2<>/dev/console Of cause "$TERM" isn't set in the failsafe environment either, so you also have to run TERM=sun export TERM to make "more" (or "vi") happy. This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list [email protected]
