Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
nvidia-drivers-410.57 breaks openrc (I think)
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
Utsuho Reiuji
Apprentice
Apprentice


Joined: 03 Apr 2013
Posts: 157

PostPosted: Sun Sep 23, 2018 2:47 am    Post subject: nvidia-drivers-410.57 breaks openrc (I think) Reply with quote

Hi, I'm having some serious trouble. If I start my gentoo system. Even worse, I have no idea what is causing this, but I suppose it has to do with the 186 package update I just finished (without errors):

So when I start, the boot process hangs a bit at setting the system time and then prints an error (both didn't happen before). Apparently, the system has to recover a journal on one of my raid drives (Which I think is due to shutdown service not working after an update, so I had to reboot in shell). Then, the system should start networking and sddm, but all I get is a black screen. This is what rc.log says:
Code:
rc boot logging started at Sun Sep 23 06:26:53 2018

 * Setting system clock using the hardware clock [Local Time] ...
hwclock: select() to /dev/rtc0 to wait for clock tick timed out
 * Failed to set the system clock
 [ !! ]
 * Starting up RAID devices ...
 *
 [ !! ]
 * Checking local filesystems  ...
/dev/sda3: Superblock last mount time is in the future.
(by less than a day, probably due to the hardware clock being incorrectly set)
/dev/sda3: clean, 1447559/6668288 files, 11623284/26649344 blocks
/dev/sda2 was not cleanly unmounted, check forced.
/dev/sda2: |==                                                      |  4.4%   /dev/sda2: |========================================================| 100.0%                                                                                  /dev/sda2: 333/32768 files (2.7% non-contiguous), 51098/131072 blocks
warehouse: recovering journal
warehouse: clean, 205753/183148544 files, 482664465/732566272 blocks
/dev/md127: recovering journal
/dev/md127: clean, 460528/61038592 files, 135796917/244126720 blocks
 * Filesystems repaired
 [ !! ]
 * Remounting root filesystem read/write ...
 [ ok ]
 * Remounting filesystems ...
 [ ok ]
 * Updating /etc/mtab ...
 * Creating mtab symbolic link
 [ ok ]
 * Activating swap devices ...
 [ ok ]
 * Mounting local filesystems ...
 [ ok ]
 * Configuring kernel parameters ...
 [ ok ]
 * Creating user login records ...
 [ ok ]
 * Restoring Mixer Levels ...
 [ ok ]
 * Mounting misc binary format filesystem ...
 [ ok ]
 * Loading custom binary format handlers ...
 [ ok ]
 * Setting hostname to phoenix  ...
 [ ok ]
 * Setting terminal encoding [UTF-8] ...
 [ ok ]
 * Setting keyboard mode [UTF-8] ...
 [ ok ]
 * Loading key mappings [en] ...
cannot open file en
 [ ok ]
 * Bringing up network interface lo ...
 [ ok ]
 * Setting up tmpfiles.d entries ...
 [ ok ]
 * Initializing random number generator ...
 [ ok ]

rc boot logging stopped at Sun Sep 23 04:27:05 2018

Nothing works from this point on, I cannot open another tty or interact otherwise with the system. I have to soft reset.
I can get into the system via the recovery kernel. If I then give myself write permission, manually start the networkmanager and xdm, I can use the desktop normally (which is however not ideal of course)

Can somebody help me out, please?


Last edited by Utsuho Reiuji on Tue Sep 25, 2018 9:19 pm; edited 1 time in total
Back to top
View user's profile Send private message
Keruskerfuerst
Advocate
Advocate


Joined: 01 Feb 2006
Posts: 2288
Location: near Augsburg, Germany

PostPosted: Sun Sep 23, 2018 5:22 am    Post subject: Reply with quote

Can you try to access the logs with a live cd (Systemrescuecd or similar) ?
Back to top
View user's profile Send private message
Utsuho Reiuji
Apprentice
Apprentice


Joined: 03 Apr 2013
Posts: 157

PostPosted: Sun Sep 23, 2018 4:44 pm    Post subject: Reply with quote

Keruskerfuerst wrote:
Can you try to access the logs with a live cd (Systemrescuecd or similar) ?


Yes. Strangely, my liveusb starts into a black screen, but booting into my normal recovery kernel gives me the maintenance access and from there, I can access my desktop normally and of course the log files.
It took me a while but I managed to get a list of all packages I emerged before my system broke:
Code:
sys-devel/llvm-common-7.0.0
sys-kernel/linux-firmware-20180913
dev-libs/gobject-introspection-common-1.56.1
media-libs/libpng-1.6.35-r1
sys-apps/busybox-1.29.3

sys-apps/less-538
app-text/qpdf-8.2.1
sys-devel/bc-1.07.1-r2
dev-libs/protobuf-3.6.1
dev-libs/icu-62.1

dev-libs/libpcre2-10.32
sys-power/acpid-2.0.30
media-libs/libsndfile-1.0.28-r3
dev-libs/boost-1.65.0
dev-tex/bibtexu-3.71_p20170524

sys-devel/binutils-2.31.1-r1
sys-libs/binutils-libs-2.31.1-r1
app-editors/nano-3.1
sys-kernel/gentoo-sources-4.18.9
dev-qt/qtcore-5.11.1-r1

x11-libs/libdrm-2.4.94
sys-fs/fuse-common-3.2.6
dev-libs/gobject-introspection-1.56.1
sys-fs/fuse-2.9.8
media-libs/gstreamer-1.14.3

dev-util/gtk-update-icon-cache-3.24.0
sys-fs/eudev-3.2.6
sys-apps/hwids-20180917
dev-libs/libinput-1.12.0
dev-libs/libxml2-2.9.8

dev-lang/spidermonkey-52.9.1_pre1
app-arch/libarchive-3.3.3
dev-util/cmake-3.12.2
sys-devel/llvm-7.0.0
kde-frameworks/extra-cmake-modules-5.50.0

media-gfx/exiv2-0.26_p20180811-r3
dev-libs/libical-3.0.3
net-libs/libssh-0.8.3
dev-cpp/gtest-1.8.1
kde-frameworks/breeze-icons-5.50.0

sys-libs/libcxxabi-7.0.0
dev-libs/json-glib-1.4.4
kde-frameworks/kcoreaddons-5.50.0
kde-frameworks/ki18n-5.50.0
kde-frameworks/kconfig-5.50.0

kde-frameworks/kwidgetsaddons-5.50.0
kde-frameworks/kwindowsystem-5.50.0
kde-frameworks/kdbusaddons-5.50.0
kde-frameworks/karchive-5.50.0
kde-frameworks/kitemviews-5.50.0

kde-frameworks/kcodecs-5.50.0
kde-frameworks/kguiaddons-5.50.0
kde-frameworks/kidletime-5.50.0
kde-frameworks/kitemmodels-5.50.0
kde-frameworks/sonnet-5.50.0

kde-frameworks/kirigami-5.50.0
kde-frameworks/threadweaver-5.50.0
kde-frameworks/kholidays-5.50.0
kde-frameworks/attica-5.50.0
kde-frameworks/bluez-qt-5.50.0

kde-frameworks/syntax-highlighting-5.50.0
kde-frameworks/kplotting-5.50.0
kde-apps/libkexiv2-18.08.1
kde-frameworks/kdnssd-5.50.0
sys-libs/libcxx-7.0.0

kde-frameworks/kcrash-5.50.0
kde-frameworks/kdoctools-5.50.0
kde-frameworks/kcompletion-5.50.0
kde-frameworks/kjobwidgets-5.50.0
kde-frameworks/kpackage-5.50.0

kde-frameworks/kpty-5.50.0
kde-frameworks/kunitconversion-5.50.0
kde-frameworks/kimageformats-5.50.0
kde-frameworks/kservice-5.50.0
kde-frameworks/kglobalaccel-5.50.0

kde-frameworks/kjs-5.50.0
kde-frameworks/kdesignerplugin-5.50.0
media-libs/mesa-18.2.0-r1
kde-frameworks/knotifications-5.50.0
kde-frameworks/kdesu-5.50.0

kde-frameworks/kemoticons-5.50.0
kde-frameworks/kjsembed-5.50.0
kde-frameworks/kpeople-5.50.0
kde-frameworks/kwayland-5.50.0
media-libs/openal-1.19.0

dev-python/certifi-2018.8.24
kde-frameworks/solid-5.50.0
net-misc/openssh-7.8_p1
net-mail/mailutils-3.4-r3
kde-frameworks/kauth-5.50.0

gnome-base/gvfs-1.34.2.1-r1
kde-frameworks/kconfigwidgets-5.50.0
kde-frameworks/kiconthemes-5.50.0
kde-frameworks/ktextwidgets-5.50.0
kde-frameworks/qqc2-desktop-style-5.50.0

media-fonts/encodings-1.0.4-r3
media-libs/fontconfig-2.13.1-r2
kde-frameworks/kwallet-5.50.0
kde-frameworks/kxmlgui-5.50.0
x11-libs/cairo-1.14.12

kde-frameworks/kbookmarks-5.50.0
kde-apps/libkipi-18.08.1
app-text/ghostscript-gpl-9.25
kde-frameworks/kio-5.50.0
app-emulation/wine-staging-3.16

media-libs/gd-2.2.5-r1
app-emulation/wine-vanilla-3.16
media-libs/harfbuzz-1.9.0
kde-frameworks/kinit-5.50.0
kde-frameworks/kfilemetadata-5.50.0

dev-python/pygobject-3.28.3
dev-vcs/git-2.19.0
media-libs/gst-plugins-base-1.14.3-r1
net-misc/networkmanager-1.14.0
dev-qt/qtwebengine-5.11.1

x11-libs/gtk+-3.24.1
media-libs/gst-plugins-good-1.14.3
media-libs/gst-plugins-ugly-1.14.3
media-libs/gst-plugins-bad-1.14.3
kde-frameworks/networkmanager-qt-5.50.0

media-plugins/gst-plugins-cdparanoia-1.14.3
net-misc/networkmanager-pptp-1.2.6
  *** exiting unsuccessfully with status '1'.

Compiling networkmanager failed due to missing header file. I used this break to try fixing another problem I had with dxx-rebirth by downgrading physfs, but that was unsuccessful:
Code:
Started emerge on: Sep 22, 2018 22:08:28
dev-games/physfs-2.0.3-r2
games-action/dxx-rebirth-0.59.100
  *** exiting unsuccessfully with status '1'.

Then I continued the update process...
Code:
Started emerge on: Sep 22, 2018 22:21:33
media-plugins/gst-plugins-taglib-1.14.3
media-plugins/gst-plugins-a52dec-1.14.3
media-plugins/gst-plugins-faad-1.14.3
media-plugins/gst-plugins-dts-1.14.3
media-plugins/gst-plugins-dvdread-1.14.3

media-plugins/gst-plugins-mpeg2dec-1.14.3
media-plugins/gst-plugins-resindvd-1.14.3
media-plugins/gst-plugins-flac-1.14.3
media-plugins/gst-plugins-mpg123-1.14.3
media-plugins/gst-plugins-x264-1.14.3

dev-games/physfs-3.0.1-r1
media-plugins/gst-plugins-soup-1.14.3
dev-qt/qtwebkit-5.212.0_pre20180120
x11-libs/gtk+-2.24.32-r1
www-client/google-chrome-69.0.3497.100
media-plugins/gst-plugins-meta-1.14.3
  *** terminating.

But forgot something and aborted and continued shortly after:
Code:
Started emerge on: Sep 22, 2018 22:31:17
dev-qt/qtwebkit-5.212.0_pre20180120
x11-libs/gtk+-2.24.32-r1
media-sound/clementine-1.3.1_p20180523
x11-drivers/nvidia-drivers-410.57
www-plugins/adobe-flash-31.0.0.108

media-video/aegisub-3.2.2_p20160518-r2
kde-frameworks/kded-5.50.0
kde-frameworks/kparts-5.50.0
kde-frameworks/kdeclarative-5.50.0
kde-frameworks/knewstuff-5.50.0

kde-frameworks/baloo-5.50.0
kde-frameworks/knotifyconfig-5.50.0
kde-apps/kdialog-18.08.1
kde-frameworks/kxmlrpcclient-5.50.0
kde-apps/ksystemlog-18.08.1

kde-apps/kcron-18.08.1
kde-apps/filelight-18.08.1
kde-frameworks/kactivities-5.50.0
kde-frameworks/kcmutils-5.50.0
kde-frameworks/kdelibs4support-5.50.0

kde-frameworks/ktexteditor-5.50.0
kde-frameworks/khtml-5.50.0
kde-frameworks/frameworkintegration-5.50.0
kde-apps/konsole-18.08.1
kde-frameworks/kross-5.50.0

kde-apps/keditbookmarks-18.08.1
kde-apps/baloo-widgets-18.08.1
kde-apps/kdeadmin-meta-18.08.1
kde-apps/ark-18.08.1
kde-apps/spectacle-18.08.1

kde-frameworks/plasma-5.50.0
kde-apps/kio-extras-18.08.1
kde-frameworks/kactivities-stats-5.50.0
kde-apps/kfind-18.08.1
kde-apps/kwrite-18.08.1

kde-apps/kwalletmanager-18.08.1
kde-apps/gwenview-18.08.1
kde-apps/kalzium-18.08.1
kde-apps/kmplot-18.08.1
kde-apps/okular-18.08.1

kde-frameworks/krunner-5.50.0
kde-apps/dolphin-18.08.1
kde-apps/kate-18.08.1
kde-plasma/kwin-5.13.5
kde-plasma/plasma-workspace-5.13.5-r1

kde-plasma/oxygen-5.13.5-r1
kde-apps/khelpcenter-18.08.1
kde-apps/kmix-18.08.1
kde-apps/kdecore-meta-18.08.1
kde-plasma/plasma-desktop-5.13.5-r1

kde-apps/kdebase-meta-18.08.1

With the help of the forums, I was able to emerge networkmanager afterwards (note, I did not restart the system yet):
Code:
Started emerge on: Sep 23, 2018 02:33:50
net-misc/networkmanager-pptp-1.2.6
  *** exiting unsuccessfully with status '1'.

Started emerge on: Sep 23, 2018 02:37:18
net-misc/mobile-broadband-provider-info-20170310
sys-libs/libcap-ng-0.7.9
virtual/freedesktop-icon-theme-0-r3
app-crypt/libsecret-0.18.6-r1
app-crypt/gcr-3.20.0
gnome-base/gnome-keyring-3.20.1
app-crypt/pinentry-1.1.0-r2
gnome-extra/nm-applet-1.8.18
net-misc/networkmanager-pptp-1.2.6

And finally, another unsuccessful attempt to patch physfs to get dxx-rebirth running:
Code:
Started emerge on: Sep 23, 2018 02:48:49
dev-games/physfs-3.0.1-r1
  *** exiting unsuccessfully with status '1'.

One update left some libs so I had to emerge @preserved-rebuild:
Code:
Started emerge on: Sep 23, 2018 02:55:55
app-text/texlive-core-2017-r4

There were no config files I needed to update. I rebooted the system, but got the black screen afterwards.
Back to top
View user's profile Send private message
Utsuho Reiuji
Apprentice
Apprentice


Joined: 03 Apr 2013
Posts: 157

PostPosted: Sun Sep 23, 2018 5:58 pm    Post subject: Reply with quote

There're a few things I noticed whenever I manually start xdm from recovery (unsure if the problem is related).
1st, the groups per user appear twice now:
Code:
# groups $USER
wheel audio video usb users plugdev sddm storage music videos games wheel audio video usb users plugdev sddm storage music videos games $USER

2nd, the system cannot set the system time via the hardware clock:
Code:
rc boot logging started at Sun Sep 23 21:43:13 2018

 * Setting system clock using the hardware clock [Local Time] ...
hwclock: select() to /dev/rtc0 to wait for clock tick timed out
 * Failed to set the system clock
 [ !! ]

And 3rd, in the subsequent steps, the system seems unable to load keymaps (in my case en_UK):
Code:
 * Starting up RAID devices ...
 *
 [ !! ]
 * Checking local filesystems  ...
/dev/sda3: clean, 1447559/6668288 files, 11623320/26649344 blocks
/dev/sda2: clean, 333/32768 files, 51098/131072 blocks
warehouse: clean, 205771/183148544 files, 485100793/732566272 blocks
/dev/md127: clean, 462039/61038592 files, 133341714/244126720 blocks
 [ ok ]
 * Remounting root filesystem read/write ...
 [ ok ]
 * Remounting filesystems ...
 [ ok ]
 * Updating /etc/mtab ...
 * Creating mtab symbolic link
 [ ok ]
 * Activating swap devices ...
 [ ok ]
 * Mounting local filesystems ...
 [ ok ]
 * Configuring kernel parameters ...
 [ ok ]
 * Creating user login records ...
 [ ok ]
 * Restoring Mixer Levels ...
 [ ok ]
 * Mounting misc binary format filesystem ...
 [ ok ]
 * Loading custom binary format handlers ...
 [ ok ]
 * Setting hostname to phoenix  ...
 [ ok ]
 * Setting terminal encoding [UTF-8] ...
 [ ok ]
 * Setting keyboard mode [UTF-8] ...
 [ ok ]
 * Loading key mappings [en] ...
cannot open file en
 [ ok ]
 * Bringing up network interface lo ...
 [ ok ]
 * Setting up tmpfiles.d entries ...
 [ ok ]
 * Initializing random number generator ...
 [ ok ]

rc boot logging stopped at Sun Sep 23 19:43:25 2018


This part "cannot open file en" doesn't make sense...
From the packages I emerged (one of them must have caused this since everything worked fine before), I can't think which one is responsible..
Back to top
View user's profile Send private message
Utsuho Reiuji
Apprentice
Apprentice


Joined: 03 Apr 2013
Posts: 157

PostPosted: Sun Sep 23, 2018 9:18 pm    Post subject: Reply with quote

I also noticed that the system does not start the swap partition. I have to manually start this..

Maybe something is broken with openrc, this is what it is supposed to do:
Code:
eselect rc list
Available init scripts
  acpid
  agetty
  alsasound                 boot
  binfmt                    boot
  bluetooth
  bootmisc                  boot
  busybox-ntpd
  busybox-watchdog
  cgroups                   sysinit
  ckb-daemon                default
  consolefont
  consolekit                default
  cronie
  cups-browsed
  cupsd
  dbus                      default
  devfs                     sysinit
  device-mapper
  dhcpcd
  dhcpd
  dhcrelay
  dhcrelay6
  dmcrypt
  dmesg                     sysinit
  dmeventd
  fsck                      boot
  fuse
  git-daemon
  gpm
  hostname                  boot
  hwclock                   boot
  ip6tables
  iptables
  keymaps                   boot
  killprocs                 shutdown
  kmod-static-nodes         sysinit
  local                     default
  localmount                boot
  loopback                  boot
  lvm
  lvmetad
  lvm-monitoring
  mdadm
  mdraid                    boot
  modules                   boot
  mount-ro                  shutdown
  mtab                      boot
  net.enp2s0
  net.lo
  netmount                  default
  net-online
  NetworkManager            default
  nullmailer
  numlock
  nvidia-persistenced
  nvidia-smi
  opentmpfiles-dev          sysinit
  opentmpfiles-setup        boot
  osclock
  pciparm
  procfs                    boot
  pydoc-2.7
  pydoc-3.3
  pydoc-3.4
  pydoc-3.5
  pydoc-3.6
  pydoc-3.7
  root                      boot
  rsyncd
  runsvdir
  s6-svscan
  savecache                 shutdown
  smartd
  sshd
  swap                      boot
  swclock
  sysctl                    boot
  sysfs                     sysinit
  syslog-ng                 default
  termencoding              boot
  timidity
  transmission-daemon
  udev                      sysinit
  udev-settle
  udev-trigger              sysinit
  urandom                   boot
  wpa_supplicant
  xdm                       default
  xdm-setup
Back to top
View user's profile Send private message
Utsuho Reiuji
Apprentice
Apprentice


Joined: 03 Apr 2013
Posts: 157

PostPosted: Tue Sep 25, 2018 9:18 pm    Post subject: Reply with quote

ok, I figured it out, the nvidia-drivers-410.57 break something.
This is probably the same issue as in the following thread:
https://forums.gentoo.org/viewtopic-t-1086860.html

Here's what I observed:
With 410.57 installed, the system seems to be unable to sync to hwclock.
In addition, there seems to be an issue with other drivers, e.g. ckb-daemon (not exactly a driver) and systempower.
Once xdm is started, system goes into black screen. No tty's are started either. Rc-logger does not log anything beyond this point.

Downgrading fixes this issue.

(requesting moderator to merge this thread with the one linked above)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum