Date: Mon, 3 Feb 2025 07:29:54 +0000 From: Roderick <hruodr@gmail.com> To: Vitor Sonoki <vitorsonoki.0a04@yahoo.com> Cc: freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: After upgrade to 14.2, I cannot go from X to a virtual console Message-ID: <CABdqxFcQiugDnTs_Ge4T3uSZT-Hxgcc9K1fJv8kXgr1xJ8o1ZQ@mail.gmail.com> In-Reply-To: <20250202213651.15a7d60b@archnux> References: <CABdqxFeFy5tRrH1_y5uDkn4YbEHXMPZD58GEx2vL2JdnQ0Uiqw@mail.gmail.com> <20250202213651.15a7d60b@archnux>
next in thread | previous in thread | raw e-mail | index | archive | help
I wrote in my original posting that X11 is working. The problem is when turning back to the text console, it is a problem with the text consoles, and I want and need the console even if X11 does not work, better said: specially when X11 does not work. I do not see any sense of typing Ctrl-C or Ctrl-D. As I said, in spite of the blank screen the keyboard works, and having a shell may help to solve the problem. It wonders me that it wonders you that I need the +s in Xorg for running it as normal user. Please, I do not need chat, I need to solve the problem ... Rod. Am Mo., 3. Feb. 2025 um 00:37 Uhr schrieb Vitor Sonoki <vitorsonoki.0a04@yahoo.com>: > > Hello, > > I'm assuming from the message that your X session runs without issues. > Drivers, etc, all work, no error log messages, etc. > > > I normally boot in a virtual console and start X after login as > > normal user (Xorg with +s permission). And this was successful. > > I'm a little surprised that you have to set the sticky bit for Xorg to > work. Do you manually set this up in your installation? Doesn't plain > `startx` with vanilla Xorg install as your normal user work without it? > > (I might not remember everything correctly here, but AFAIK you don't > need to explicitly set this up, and one of the biggest reasons to run a > graphical environment directly from console via startx is precisely to > *avoid* running Xorg - a program that by design can "see" a lot of other > processes' stuff - as root.) > > > /var/log/Xorg.0.log indicates that X ends without problem. And typing > > "shutdown -h now" > > on the black screen does shutdown the system. > > Does either Ctrl+C (terminating anything holding back the process) or > Ctrl+D (exiting the shell) work for you here? Since you can type the > command, it might be a problem that the cursor itself isn't returned, > something that happens, for example, when a TUI application exits > uncleanly. Exiting the shell might fix this. > > Another thing: instead of starting Xorg via `startx`, try starting it > with `exec startx`. This will ensure that startx will fork away from > your shell and the shell will exit as soon as Xorg terminates (either > cleanly or through error), in principle dropping you right back to the > console login prompt where you started. > > If the console upon return is broken or jumbled up, it might be a > driver issue (happened to me once that Console broke, but X was fine), > in which case someone more knowledgeable can chip in. > > Best of luck, > > Vitor S > PGP: E931D26D4A97819FA8E7CE20E202415277C50A04 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CABdqxFcQiugDnTs_Ge4T3uSZT-Hxgcc9K1fJv8kXgr1xJ8o1ZQ>