Re: [Nix-dev] Disappearing X session on some systems
The issue on the ThinkPad E465 seems to have been fixed. No longer have I experienced a locked X session. The problem may have been related to GDM. It was some error messages received during nixos-rebuild switch which led me down this path. The fix was achieved after applying a workaround supplied by digs: https://github.com/NixOS/nixpkgs/issues/24172# issuecomment-304540789 Unfortunately I was not able to test the fix on the SuperMicro Intel with Nvidia card. Before I could test, I was receiving garbled images on my monitor from boot. I assumed the 10-year old Nvidia 8800 GT had given up the ghost, so swapped it with a spare Radeon 7750. I verified with the Radeon 7750 that GDM-related error messages were no longer being produced by running nixos-rebuild switch - the intended fix of the Issue 24172 workaround. The latest issue is the SuperMicro Intel machine cannot keep an X session running - even when I'm actively using a session. Sessions freeze up within 1 - 5 minutes after starting. The mouse cursor still works, but nothing on the screen responds to it. I have used journalctl to review a few logs of what happens when X freezes. Around the time stuck to the clock in the X session, these things happen: Up to one minute before, org.freedesktop.PackageKit and org.bluez both fail. I'm not sure if this is related or not. .gnome-shell-wr[1699]: JS LOG: Error calling StartServiceByName for org.freedesktop.PackageKit: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.PackageKit': timed out ... dbus[1378]: [system] Failed to activate service 'org.bluez': timed out ... At the exact moment when X gets stuck, these kernel messages are logged: kernel: DMAR: DRHD: handling fault status reg 2 kernel: DMAR: [INTR-REMAP] Request device [00:00.0] fault index 13 [fault reason 38] Blocked an interrupt request due to source-id verification failure ... After the above kervel messages, these gdm and gnome messages follow: /nix/store/cslvy4s12r9y0ixi33x79m3906zbsimb-gdm-3.22.0/libexec/gdm-x-session[2088]: (II) AIGLX: Suspending AIGLX clients for VT switch xsession[2030]: gnome-session-binary[2055]: DEBUG(+): emitting SessionIsActive gnome-session-binary[2055]: DEBUG(+): emitting SessionIsActive ... After the above messages, gdm-related "systemd-logind: got pause" messages appear: /nix/store/cslvy4s12r9y0ixi33x79m3906zbsimb-gdm-3.22.0/libexec/gdm-x-session[2016]: (II) systemd-logind: got pause for 13:70 /nix/store/cslvy4s12r9y0ixi33x79m3906zbsimb-gdm-3.22.0/libexec/gdm-x-session[2016]: (II) systemd-logind: got pause for 13:65 /nix/store/cslvy4s12r9y0ixi33x79m3906zbsimb-gdm-3.22.0/libexec/gdm-x-session[2016]: (II) systemd-logind: got pause for 226:0 /nix/store/cslvy4s12r9y0ixi33x79m3906zbsimb-gdm-3.22.0/libexec/gdm-x-session[2016]: (II) systemd-logind: got pause for 13:64 /nix/store/cslvy4s12r9y0ixi33x79m3906zbsimb-gdm-3.22.0/libexec/gdm-x-session[2016]: (II) systemd-logind: got pause for 13:68 /nix/store/cslvy4s12r9y0ixi33x79m3906zbsimb-gdm-3.22.0/libexec/gdm-x-session[2016]: (II) systemd-logind: got pause for 13:69 ... After the above messages, there is then a repeat of these 'GSD_IS_WACOM_DEVICE (device)' failed & invalid pointer messages: gnome-settings-[2177]: gsd_wacom_device_get_device_type: assertion 'GSD_IS_WACOM_DEVICE (device)' failed gnome-settings-[2177]: gsd_wacom_device_get_settings: assertion 'GSD_IS_WACOM_DEVICE (device)' failed gnome-settings-[2248]: invalid (NULL) pointer instance ... Except for the org.freedesktop.PackageKit and org.bluez messages, all of the messages here are invariably displayed in this order, within the span of a minute, every time X freezes on this machine. The exact meaning of this I'm unsure of. I am considering opening up a separate issue on GitHub. On Sun, May 28, 2017 at 1:31 PM, Evan Rowley <rowley.e...@gmail.com> wrote: > Upon further inspection, it appears bug 24172, bug 22470, and pull request > 25621 may be related to the X session problem I mentioned. > > Gdm on nvidia > https://github.com/NixOS/nixpkgs/pull/25621 > > nixos-rebuild switch fails in X terminal > https://github.com/NixOS/nixpkgs/issues/22470 > > systemd-vconsole-setup.service seems to get started after every switch > https://github.com/NixOS/nixpkgs/issues/23118 > > > On Sat, May 27, 2017 at 11:57 AM, Evan Rowley <rowley.e...@gmail.com> > wrote: > >> Has anyone left their NixOS machine running for awhile, come back to it, >> and saw a console on tty7 where X used to be running? I experience this >> when I leave two of my NixOS systems alone for awhile. Both are using Gnome >> 3. It affects my ThinkPad E465 which is running an AMD A10-8700P & Radeon >> R6 M340DX. It also affects my SuperMicro SYS-7038A-i with Intel Xeon CPUs >> and Nvidia 8800 GT graphics. It never happens while I'm using these, just >> only when I've left them alone f
Re: [Nix-dev] Disappearing X session on some systems
Upon further inspection, it appears bug 24172, bug 22470, and pull request 25621 may be related to the X session problem I mentioned. Gdm on nvidia https://github.com/NixOS/nixpkgs/pull/25621 nixos-rebuild switch fails in X terminal https://github.com/NixOS/nixpkgs/issues/22470 systemd-vconsole-setup.service seems to get started after every switch https://github.com/NixOS/nixpkgs/issues/23118 On Sat, May 27, 2017 at 11:57 AM, Evan Rowley <rowley.e...@gmail.com> wrote: > Has anyone left their NixOS machine running for awhile, come back to it, > and saw a console on tty7 where X used to be running? I experience this > when I leave two of my NixOS systems alone for awhile. Both are using Gnome > 3. It affects my ThinkPad E465 which is running an AMD A10-8700P & Radeon > R6 M340DX. It also affects my SuperMicro SYS-7038A-i with Intel Xeon CPUs > and Nvidia 8800 GT graphics. It never happens while I'm using these, just > only when I've left them alone for a while - like overnight, for example. I > have not seen this behavior on my NixOS ThinkPad T420 with Intel i5-2520M > and integrated graphics. I realize that the T420 is relatively mature in > Linux support & things working well is somewhat expected - but a crashing X > session seems to be abnormal, even for hardware that's less tested. One > major difference between the T420 and the other systems is the T420 is > using integrated graphics while the other systems are using dedicated > graphics cards - which is why I listed out the cards here. If anyone knows > of ongoing issues with NixOS/X/graphics which could be related, how it > further investigate the issue, ideas on a fix, or is experiencing the same > kind of issue - please reply. :) > > -- > - EJR > -- - EJR ___ nix-dev mailing list nix-dev@lists.science.uu.nl https://mailman.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] Disappearing X session on some systems
Has anyone left their NixOS machine running for awhile, come back to it, and saw a console on tty7 where X used to be running? I experience this when I leave two of my NixOS systems alone for awhile. Both are using Gnome 3. It affects my ThinkPad E465 which is running an AMD A10-8700P & Radeon R6 M340DX. It also affects my SuperMicro SYS-7038A-i with Intel Xeon CPUs and Nvidia 8800 GT graphics. It never happens while I'm using these, just only when I've left them alone for a while - like overnight, for example. I have not seen this behavior on my NixOS ThinkPad T420 with Intel i5-2520M and integrated graphics. I realize that the T420 is relatively mature in Linux support & things working well is somewhat expected - but a crashing X session seems to be abnormal, even for hardware that's less tested. One major difference between the T420 and the other systems is the T420 is using integrated graphics while the other systems are using dedicated graphics cards - which is why I listed out the cards here. If anyone knows of ongoing issues with NixOS/X/graphics which could be related, how it further investigate the issue, ideas on a fix, or is experiencing the same kind of issue - please reply. :) -- - EJR ___ nix-dev mailing list nix-dev@lists.science.uu.nl https://mailman.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] ZFS configuration for 17.03
I have seen some guides from 2014 and 2015 but these are pre-17.03. Are there any recent configurations guides, configuration.nix, or basic pointers for setting this up for a new system? -- - EJR ___ nix-dev mailing list nix-dev@lists.science.uu.nl https://mailman.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] [drm:radeon_acpi_init [radeon]] *ERROR* Cannot find a backlight controller
I received this on a Lenovo ThinkPad E465. It's hardware should be similar to any E565, E455, or E555. Has anyone seen a message like this? Any ideas on how to fix it so that the backlight controller is detected? -- - EJR ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
Re: [Nix-dev] Where to start when nixos-rebuild switch --upgrade goes wrong
A simple "nixos-rebuild switch --rollback" took the machine back to 16.03.836.aff03ae. Afterwards, a "nixos-rebuild switch --upgrade" brought it to 16.03.909.f199be0. Machine is working now. Thanks to all the nix devs who made rollback functionality work so well. -- - EJR ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] Where to start when nixos-rebuild switch --upgrade goes wrong
Hi Everyone,
I performed a nixos-rebuild switch --upgrade and after rebooting, was
not able to see my usual KDE session. There was no X session. I
selected a previous generation in gummiboot and was able to have my
KDE session back. What can I do about the upgraded components which
did not work? I could issue a nixos-rebuild switch --rollback, but
would the development community benefit from finding out what went
wrong? This is a very rudimentary and unsophisticated NixOS
installation. Aside from the failed upgrade, nothing out of the
ordinairy has been done to it.
configuration.nix:
{ config, pkgs, ... }:
{
imports =
[ # Include the results of the hardware scan.
./hardware-configuration.nix
];
# Use the gummiboot efi boot loader.
boot.loader.gummiboot.enable = true;
boot.loader.efi.canTouchEfiVariables = true;
networking.hostName = "ejr-e465"; # Define your hostname.
networking.wireless.enable = true; # Enables wireless support via
wpa_supplicant.
# Select internationalisation properties.
i18n = {
consoleFont = "Lat2-Terminus16";
consoleKeyMap = "us";
defaultLocale = "en_US.UTF-8";
};
# Set your time zone.
time.timeZone = "America/New_York";
# List packages installed in system profile. To search by name, run:
# $ nix-env -qaP | grep wget
environment.systemPackages = with pkgs; [
wget
vim
pkgs.kde4.kdemultimedia
pkgs.kde4.kdegraphics
pkgs.kde4.kdeutils
pkgs.kde4.applications
pkgs.kde4.kdebindings
pkgs.kde4.kdeaccessibility
pkgs.kde4.kde_baseapps
pkgs.kde4.kactivities
pkgs.kde4.kdeadmin
pkgs.kde4.kdeartwork
pkgs.kde4.kde_base_artwork
pkgs.kde4.kdenetwork
pkgs.kde4.kdepim
pkgs.kde4.kdepimlibs
pkgs.kde4.kdeplasma_addons
pkgs.kde4.kdesdk
pkgs.kde4.kdetoys
pkgs.kde4.kdewebdev
pkgs.kde4.oxygen_icons
pkgs.kde4.kdebase_workspace
pkgs.kde4.kdelibs
pkgs.kde4.kdevelop
pkgs.kde4.kdevplatform
];
# List services that you want to enable:
# Enable the OpenSSH daemon.
# services.openssh.enable = true;
# Enable CUPS to print documents.
# services.printing.enable = true;
# Enable the X11 windowing system.
services.xserver.enable = true;
services.xserver.layout = "us";
#services.xserver.xkbOptions = "eurosign:e";
# Enable the KDE Desktop Environment.
services.xserver.displayManager.kdm.enable = true;
services.xserver.desktopManager.kde4.enable = true;
fonts = {
enableFontDir = true;
enableGhostscriptFonts = true;
fonts = with pkgs; [
corefonts # Micrsoft free fonts
inconsolata # monospaced
];
};
users.extraUsers.ejr = {
name = "ejr";
group = "users";
uid = 1001;
createHome = true;
home = "/home/ejr";
useDefaultShell = true;
description = "Evan Johannes Rowley";
password = "password";
extraGroups = [
"wheel"
"libvirtd"
"audio"
"kvm"
"cdrom"
"docker"
];
};
# release to be compatible with for stateful data such as databases.
system.stateVersion = "16.03";
system.autoUpgrade.enable = true;
system.autoUpgrade.channel = https://nixos.org/channels/nixos-16.03;
}
--
- EJR
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] Synchronizing a the binary cache
Hello, I am wondering if it is possible to somehow synchronize a machine with the nix binary cache, so that on a separate network, it may service NixOS client requests to download binaries. I'm interested in any other tips / guides on using NixOS on networks with limited or no connectivity to the internet. I don't use NixOS at the moment, but if this were possible, then it would bring me one step closer towards using it. My home internet connectivity is extremely unreliable due to it's remote location, so am looking for a way to cache packages and other necessary things locally. The OS I use the most now is FreeBSD and it is simple to cache packages and binary sets used to perform installations. -- - EJR ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-dev] Install Nix Manuals
Hello Basic question: How can I get the Nix manuals and other Nix documentation loaded on a basic graphical NixOS install? I have recently installed NixOS using the directions shown in Example 2.1 on the Version 15.09.688.ef7a813 NixOS manual: https://nixos.org/nixos/manual/ The NixOS Manual that was available on the Live DVD isn't visible on the KDE desktop after I followed the installation. If the manual is on the new installation, then it isn't obvious to me where I can find it. I also wasn't sure if I should have installed it as a Nix package. -- - EJR ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
