Re: Cannot Cleanly Exit FVWM / X Windows System
On 02/05/2016 03:41 AM, Dahlberg, David wrote: Am Donnerstag, den 04.02.2016, 16:40 -0500 schrieb Samir Parikh: If you investigate more closely, you will probably find out, that the system still works, just the graphics is fscked up: Try logging in via ssh, or shutting down the system by blindly typing into ttyC0. I know this is a stupid question but should I try logging into ttyC0 via CRTL-ALT-F1 while FVWM/X.org is still running or when I am in the original shell at login? When xenocara hangs, you may press e.g. Ctrl-Alt-F2 and enter blindly: | | | shutdown -p now In the other posting you were saying that pressing the power button shortly wouldn't work. At least on my 2015 Lenovo you need to press the power button for aprox. 2 seconds to send an ACPI powerdown. Any ideas or suggestions? 1) Use modesetting(4) in xorg.conf and wait for 5.9 Does not work on 5.8 yet -> See Jonathan Grey's comment. He is one of the devs, who ported the Broadwell support. So basically you have two options: If you want to stay on -stable: You have to work around the but. E.g. by starting the X server with startx and killing it from the console instead of regularly logging out. If you use XDM put the following into /etc/X11/xdm/xdm-config: | DisplayManager.*.resetSignal: 9 This still destroys the graphics on your consoles, but at least you get a shiny new X server login after exiting. In that situation, most graphical Desktop environments won't work, but the more simplistic ones do. The following setup worked okay'ish for me: xfce4, with xfce4-power-manager, no xscreensaver installed (xfce4-power-manager + xscreensaver triggers the bug) 3) Update to a recent snapshot. Ok. Thank you for the ideas. Perhaps I'll look into a recent snapshot if not other methods work The `problem' with a snapshot is that from then on you will be following current and keep on updating. It was bad luck for you to buy the wrong machine at the wrong time. I did the same though, knowing quite well that a lot of the OpenBSD developers use the same Laptop as me and thus will feel the same pain ;-) Regarding Broadwell Graphics support: Matthew Dillon and wrote it first for DragonflyBSD. The OpenBSD people could not directly import it, as the graphics stacks seem to differ significantly between Open and Dragonfly. After Matt Dillon also ported his Broadwell support to Linux, jsg@ and kettenis@ started to implement it in OpenBSD. This was shortly after the 5.8 release. Be assured that the Ubuntus and RedHats have not been faster either and AFAIK FreeBSD/PC-BSD is still working on Haswell support ;-) maybe OpenBSD is not the right OS for my skills and laptop. I hope that is not the case though!) Don't be afraid. Your problem is that you have bought the latest and greatest of models and open source support takes usually a few month. If you install 5.9 (to be released 1st of May), it will probably work fine for you. And about the simplicity: If it works, it is IMHO easier to master than most of the Linux distros that I know of. And definitively better documented :-) Cheers, David David, Jonathan -- Thanks for your help and tips. As you say, perhaps I've got the right laptop and the wrong time. Unfortunately, I don't have the technical skills to keep up with all of the updates with a snapshot or -RELEASE at this point. I was able to successfully run Fedora 23 and Ubuntu MATE 15.10 with no problems, including wireless and the screen brightness keys so I think I'll stay with that for now and look at putting on OpenBSD or FreeBSD on this older T61. I promise I'll be back with more questions as I really would like to make BSD work for me! Samir
Re: Cannot Cleanly Exit FVWM / X Windows System
Hi Marcus -- Thank you for the quick reply. I'll try to provide some additional details and answers to your questions below: On 02/04/16 03:12, Marcus MERIGHI wrote: Hello Samir, spytho...@gmail.com (Samir Parikh), 2016.02.03 (Wed) 21:29 (CET): Hi Everyone! This is my first post to the mailing list as I am new to OpenBSD. I am running version 5.8 (amd64) on a Lenovo Thinkpad T450s with a fairly default installation. I have a few issues to sort out but my first concern is that I cannot exit out of FVWM. I launch it via the command startx while logged in as root. https://en.wikipedia.org/wiki/Principle_of_least_privilege TL;DR: don't run as root. Use doas(1). Point noted. Right now, my main goal is to get OpenBSD working on this laptop as quickly as possible. Once I do, I will create additional users for day-to-day use but do understand your advice. When I go to exit (left mouse click on the desktop > Exit), the system just hangs which requires me to forcefully power down the laptop. Did you try 'ctrl+alt+backspace'? This should end X. Yes, that was another method I had used which I should have pointed out. Unfortunately, I got the same result in that FVWM just froze. Did you try a short power button press followed by some waiting for a clean shutdown? Yes. I waited for about 10 seconds, quickly pressed the laptop power button, and then waited for another 10 seconds but the system was still hung. Did you try to switch the tty back to ttyC0 (ctrl+alt+F1) when X/fvwm are making you wait? Yes. I tried pressing CTRL-ALT-F1 as well but with the same results, unfortunately. I am not using a login or display manager such as xdm(1) so I do not have an ~/.xinitrc or /etc/rc.conf.local file. During installation, I answered Yes to "Do you expect to run the X Window System?" and No to "Do you want the X Window System to be started by xdm(1)?" When you have restarted, the /var/log/Xorg.0.log file should still be there. Maybe that gives some clues. Please see my Xorg.0.log file below at the end of the email. And, from http://www.openbsd.org/mail.html: Include important information Don't waste everyone's time with a hopelessly incomplete question. No one other than you has the information needed to resolve your problem, it is better to provide more information than needed than not enough detail. Maybe someone already knew what you problem is if he/she only saw your dmesg? Bye, Marcus I will include that in the future. Thanks for keeping me honest! Here is the output of my Xorg.log. (The output of dmesg follows immediately after.) If the standard practice on this list is to use something like pastebin instead of email, please let me know as well. [40.874] (--) checkDevMem: using aperture driver /dev/xf86 [40.880] (--) Using wscons driver on /dev/ttyC4 in pcvt compatibility mode (version 3.32) [40.894] X.Org X Server 1.16.4 Release Date: 2014-12-20 [40.894] X Protocol Version 11, Revision 0 [40.894] Build Operating System: OpenBSD 5.8 amd64 [40.894] Current Operating System: OpenBSD t450s.home 5.8 GENERIC.MP#1236 amd64 [40.894] Build Date: 16 August 2015 03:14:12AM [40.894] [40.894] Current version of pixman: 0.32.6 [40.894]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [40.894] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [40.894] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Feb 4 16:09:46 2016 [40.896] (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d" [40.896] (==) No Layout section. Using the first Screen section. [40.897] (==) No screen section available. Using defaults. [40.897] (**) |-->Screen "Default Screen Section" (0) [40.897] (**) | |-->Monitor "" [40.897] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [40.897] (==) Disabling SIGIO handlers for input devices [40.897] (==) Automatically adding devices [40.897] (==) Automatically enabling devices [40.897] (==) Not automatically adding GPU devices [40.902] (==) FontPath set to: /usr/X11R6/lib/X11/fonts/misc/, /usr/X11R6/lib/X11/fonts/TTF/, /usr/X11R6/lib/X11/fonts/OTF/, /usr/X11R6/lib/X11/fonts/Type1/, /usr/X11R6/lib/X11/fonts/100dpi/, /usr/X11R6/lib/X11/fonts/75dpi/ [40.902] (==) ModulePath set to "/usr/X11R6/lib/modules" [40.902] (II) The server relies on wscons to provide the list of input devices. If no devices become available, reconfigure wscons or disable AutoAddDevices. [40.902] (II) Loader magic: 0x1964859356a0 [40.902] (II) Module ABI versions: [40.902]X.Org ANSI C Emulation: 0.4 [40.902]X.Org Video
Re: Cannot Cleanly Exit FVWM / X Windows System
Hi David -- Thanks for your reply! On 02/04/16 03:39, David Dahlberg wrote: Am Mittwoch, den 03.02.2016, 15:29 -0500 schrieb Samir Parikh: I am running version 5.8 (amd64) on a Lenovo Thinkpad T450s with a fairly default installation. The T405s is a Broadwell. I have a few issues to sort out but my first concern is that I cannot exit out of FVWM. I launch it via the command startx while logged in as root. When I go to exit (left mouse click on the desktop > Exit), the system just hangs which requires me to forcefully power down the laptop. If you investigate more closely, you will probably find out, that the system still works, just the graphics is fscked up: Try logging in via ssh, or shutting down the system by blindly typing into ttyC0. I know this is a stupid question but should I try logging into ttyC0 via CRTL-ALT-F1 while FVWM/X.org is still running or when I am in the original shell at login? Broadwell graphics support was added a while ago. IIRC 5.8 should have some basic support, but still a few bugs. By now (-current) it is petty stable though. Any ideas or suggestions? 1) Use modesetting(4) in xorg.conf and wait for 5.9 2) Avoid the vulnerable code paths (e.g. "shutdown" in wm) and wait for 5.9 3) Update to a recent snapshot. Ok. Thank you for the ideas. Perhaps I'll look into a recent snapshot if not other methods work (I also have to get my wireless working so maybe OpenBSD is not the right OS for my skills and laptop. I hope that is not the case though!)
Re: Cannot Cleanly Exit FVWM / X Windows System
On Thu, Feb 04, 2016 at 08:39:43AM +, David Dahlberg wrote: > Am Mittwoch, den 03.02.2016, 15:29 -0500 schrieb Samir Parikh: > > I am running version 5.8 (amd64) on a Lenovo Thinkpad T450s > > with a fairly default installation. > > The T405s is a Broadwell. > > > I have a few issues to sort out but my first concern is that I cannot > > exit out of FVWM. I launch it via the command startx while logged in > > as > > root. When I go to exit (left mouse click on the desktop > Exit), > > the > > system just hangs which requires me to forcefully power down the > > laptop. > > If you investigate more closely, you will probably find out, that the > system still works, just the graphics is fscked up: Try logging in via > ssh, or shutting down the system by blindly typing into ttyC0. > > Broadwell graphics support was added a while ago. IIRC 5.8 should have > some basic support, but still a few bugs. By now (-current) it is petty > stable though. > > > Any ideas or suggestions? > > 1) Use modesetting(4) in xorg.conf and wait for 5.9 The update that added Broadwell related parts to inteldrm went in after 5.8. The modesetting driver requires kms support. So yes, use snapshots. > 2) Avoid the vulnerable code paths (e.g. "shutdown" in wm) > and wait for 5.9 > 3) Update to a recent snapshot.
Re: Cannot Cleanly Exit FVWM / X Windows System
Hello Samir, spytho...@gmail.com (Samir Parikh), 2016.02.03 (Wed) 21:29 (CET): > Hi Everyone! This is my first post to the mailing list as I am new to > OpenBSD. > I am running version 5.8 (amd64) on a Lenovo Thinkpad T450s with a > fairly default installation. > I have a few issues to sort out but my first concern is that I cannot exit > out of FVWM. I launch it via the command startx while logged in as root. https://en.wikipedia.org/wiki/Principle_of_least_privilege TL;DR: don't run as root. Use doas(1). > When I go to exit (left mouse click on the desktop > Exit), the system just > hangs which requires me to forcefully power down the laptop. Did you try 'ctrl+alt+backspace'? This should end X. Did you try a short power button press followed by some waiting for a clean shutdown? Did you try to switch the tty back to ttyC0 (ctrl+alt+F1) when X/fvwm are making you wait? > I am not using > a login or display manager such as xdm(1) so I do not have an ~/.xinitrc or > /etc/rc.conf.local file. During installation, I answered Yes to "Do you > expect to run the X Window System?" and No to "Do you want the X Window > System to be started by xdm(1)?" When you have restarted, the /var/log/Xorg.0.log file should still be there. Maybe that gives some clues. And, from http://www.openbsd.org/mail.html: Include important information Don't waste everyone's time with a hopelessly incomplete question. No one other than you has the information needed to resolve your problem, it is better to provide more information than needed than not enough detail. Maybe someone already knew what you problem is if he/she only saw your dmesg? Bye, Marcus > !DSPAM:56b26471126511186110957!
Re: Cannot Cleanly Exit FVWM / X Windows System
Am Mittwoch, den 03.02.2016, 15:29 -0500 schrieb Samir Parikh: > I am running version 5.8 (amd64) on a Lenovo Thinkpad T450s > with a fairly default installation. The T405s is a Broadwell. > I have a few issues to sort out but my first concern is that I cannot > exit out of FVWM. I launch it via the command startx while logged in > as > root. When I go to exit (left mouse click on the desktop > Exit), > the > system just hangs which requires me to forcefully power down the > laptop. If you investigate more closely, you will probably find out, that the system still works, just the graphics is fscked up: Try logging in via ssh, or shutting down the system by blindly typing into ttyC0. Broadwell graphics support was added a while ago. IIRC 5.8 should have some basic support, but still a few bugs. By now (-current) it is petty stable though. > Any ideas or suggestions? 1) Use modesetting(4) in xorg.conf and wait for 5.9 2) Avoid the vulnerable code paths (e.g. "shutdown" in wm) and wait for 5.9 3) Update to a recent snapshot.
Cannot Cleanly Exit FVWM / X Windows System
Hi Everyone! This is my first post to the mailing list as I am new to OpenBSD. I am running version 5.8 (amd64) on a Lenovo Thinkpad T450s with a fairly default installation. I have a few issues to sort out but my first concern is that I cannot exit out of FVWM. I launch it via the command startx while logged in as root. When I go to exit (left mouse click on the desktop > Exit), the system just hangs which requires me to forcefully power down the laptop. I am not using a login or display manager such as xdm(1) so I do not have an ~/.xinitrc or /etc/rc.conf.local file. During installation, I answered Yes to "Do you expect to run the X Window System?" and No to "Do you want the X Window System to be started by xdm(1)?" Any ideas or suggestions? Thanks in advance. Samir Parikh
