Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[Solved] Problems with stability...
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
grooveman
Veteran
Veteran


Joined: 24 Feb 2003
Posts: 1166

PostPosted: Wed Jul 06, 2016 6:12 pm    Post subject: [Solved] Problems with stability... Reply with quote

Hi.

I updated to kde 5 plasma desktop probably about 6 weeks ago... perhaps a little while longer (when it became stable in gentoo). I've been having trouble with stability, and I was wondering if anyone else was having these problems.

I have it installed now on 3 different systems, and they all exhibit the same behavior.

I couldn't even login after initially updating. I found that installing the bleeding edge nvidia drivers fixed this. Now I can login , but I do have some stability issues. The worst, however, is when I switch to a VT (CTRL+ALT+F[1-9]). The system locks up hard, and I have to cut the power. Also, I find that at least 1/2 the time I try to reboot my system, it hangs on its way down.

I did follow the recommendations of the wiki when I upgraded,and I have /default/linux/amd64/13.0/desktop/plasma set as my profile.

I really thought that if I just updated daily, that eventually these problems would abate. And on the whole, I'd have to say that the systems are more stable -- but that VT issue has not shown any signs of letting up. It is 100%.

The one thing my systems all have in common is that they all have NVIDIA cards (GTX 750, GTX970 and a 750 mobile). They are all amd64 systems and multi-core.

Anyone else having issues? Did I miss something?

Thanks.

G

Code:
# emerge --info
Portage 2.2.28 (python 3.4.3-final-0, default/linux/amd64/13.0/desktop/plasma, gcc-4.9.3, glibc-2.22-r4, 4.4.6-gentoo x86_64)
=================================================================
System uname: Linux-4.4.6-gentoo-x86_64-Intel-R-_Xeon-R-_CPU_W3670_@_3.20GHz-with-gentoo-2.2
KiB Mem:    24686296 total,    673136 free
KiB Swap:   22906876 total,  22906876 free
Timestamp of repository gentoo: Wed, 06 Jul 2016 13:30:01 +0000
sh bash 4.3_p42-r1
ld GNU ld (Gentoo 2.25.1 p1.1) 2.25.1
app-shells/bash:          4.3_p42-r1::gentoo
dev-java/java-config:     2.2.0-r3::gentoo
dev-lang/perl:            5.20.2::gentoo
dev-lang/python:          2.7.10-r1::gentoo, 3.4.3-r1::gentoo
dev-util/cmake:           3.3.1-r1::gentoo
dev-util/pkgconfig:       0.28-r2::gentoo
sys-apps/baselayout:      2.2::gentoo
sys-apps/openrc:          0.19.1::gentoo
sys-apps/sandbox:         2.10-r1::gentoo
sys-devel/autoconf:       2.13::gentoo, 2.69::gentoo
sys-devel/automake:       1.11.6-r1::gentoo, 1.12.6::gentoo, 1.14.1::gentoo, 1.15::gentoo
sys-devel/binutils:       2.25.1-r1::gentoo
sys-devel/gcc:            4.9.3::gentoo
sys-devel/gcc-config:     1.7.3::gentoo
sys-devel/libtool:        2.4.6::gentoo
sys-devel/make:           4.1-r1::gentoo
sys-kernel/linux-headers: 4.3::gentoo (virtual/os-headers)
sys-libs/glibc:           2.22-r4::gentoo
Repositories:

gentoo
    location: /usr/portage
    sync-type: rsync
    sync-uri: rsync://rsync.gentoo.org/gentoo-portage
    priority: -1000

ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="* @EULA"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=native -mtune=native -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/lib64/libreoffice/program/sofficerc /usr/share/config /usr/share/gnupg/qualified.txt /usr/share/themes/oxygen-gtk/gtk-2.0"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo"
CXXFLAGS="-march=native -mtune=native -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-logs buildpkg config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync news parallel-fetch preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="http://lug.mtu.edu/gentoo/"
LANG="en_US"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
MAKEOPTS="-j 7"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --exclude=/.git"
PORTAGE_TMPDIR="/var/tmp"
USE="X a52 aac acl acpi alsa amd64 av berkdb bindist bluetooth bluray branding bzip2 cairo cdda cdr cli consolekit cracklib crypt cups cxx dbus declarative dri dts dvd dvdr emboss encode exif fam ffmpeg firefox flac fortran gdbm gif glamor gpm iconv java jpeg kde kipi kvm lcms ldap libnotify mad mmx mmxext mng modules mp3 mp4 mpeg ncurses nls nptl ogg opengl openmp pam pango pcre pdf phonon plasma png policykit ppds pulse pulseaudio qml qt3support qt4 qt5 quicktime readline samba sdl seccomp semantic-desktop session sftp spell sse sse2 ssl startup-notification svg tcpd tiff truetype udev udf udisks unicode upower usb vorbis widgets wxwidgets x264 xattr xcb xcomposite xine xinerama xml xscreensaver xv xvid zlib" ABI_X86="64" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump author" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="aes mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ublox ubx" INPUT_DEVICES="evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" LINGUAS="en_US en" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php5-5" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_4" QEMU_SOFTMMU_TARGETS="i386 x86_64" QEMU_USER_TARGETS="i386 x86_64" RUBY_TARGETS="ruby20 ruby21" USERLAND="GNU" VIDEO_CARDS="nvidia vga" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account"
Unset:  CC, CPPFLAGS, CTARGET, CXX, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, USE_PYTHON

_________________
To look without without looking within is like looking without without looking at all.


Last edited by grooveman on Thu Aug 25, 2016 7:02 pm; edited 1 time in total
Back to top
View user's profile Send private message
grooveman
Veteran
Veteran


Joined: 24 Feb 2003
Posts: 1166

PostPosted: Thu Jul 07, 2016 4:22 pm    Post subject: Reply with quote

OK...

At first I thought this was an issue with KDE, but that does not seem to be the case. Too many things upgraded on that last update... major kde upgrade, introduction of sddm, x11, kernel and nvidia drivers... difficult to pinpoint.

The problem seems to be with my graphical environment. If I remove xdm from the default runlevel, and come up to a text-only console, I can switch between VTs without any issues, as many times as I like.

If I so much as run a startx and fire up TWM, the problems arise. I cannot switch between VTs without locking up. I cannot even reboot. I have updated my kernel to 4.6.3, but it didn't help. I cannot upgrade xorg-11, because there is only one version in portage right now. I have updated my nvidia from current/stable to the very latest portage has to offer. The problem still persists.

I have looked through my dmesg and my syslogs.... I don't see any real complaints anywhere.

Thanks again.

G
_________________
To look without without looking within is like looking without without looking at all.
Back to top
View user's profile Send private message
Logicien
Veteran
Veteran


Joined: 16 Sep 2005
Posts: 1360
Location: Montréal

PostPosted: Fri Jul 08, 2016 3:58 pm    Post subject: Reply with quote

Your problem seem's to be between the Linux video driver and the Xorg one. Without X, no problem because only Linux manage the video card. With X, switch between the Xorg driver and the Linux driver create a freeze.

I only use Nouveau with my
Code:
01:00.0 VGA compatible controller: NVIDIA Corporation GK208 [GeForce GT 730] (rev a1)

Nouveau on the Linux side give the nouveaufb framebuffer with KMS witch is use by the Xorg Nouveau driver. The 2 drivers are in synergy and cooperate well giving both the native screen resolution without freeze.

From memory, with the Nvidia Xorg drivers, there is no native Linux video driver to go with, you need to chose Vesafb or Uvesafb at least in Bios mode. The Linux driver can offer only a non native screen resolution compare to the Nvidia Xorg one. The use of 2 independant drivers with different features is not the best.

Witch is your Linux framebuffer when it freeze? Are you sure that Xorg use the Nvidia video drivers? What do say /var/log/Xorg.0.log?
_________________
Paul


Last edited by Logicien on Thu Aug 18, 2016 5:58 pm; edited 1 time in total
Back to top
View user's profile Send private message
grooveman
Veteran
Veteran


Joined: 24 Feb 2003
Posts: 1166

PostPosted: Fri Jul 08, 2016 6:04 pm    Post subject: Reply with quote

Hi Logicien, and thanks for your response.

I am definitely using the nvidia driver, and I have my framebuffer set to uvesafb. It has always worked for me in the past, so I didn't question it. I know I could try nouveau, but I didn't have a lot of luck with that in the past... Is it working well now days? Do you get full graphic accelleration through it? Or does the performance take a hit?

Code:
# eselect opengl list
Available OpenGL implementations:
  [1]   nvidia *
  [2]   xorg-x11


Code:
# cat Xorg.0.log
[    15.917]
X.Org X Server 1.17.4
Release Date: 2015-10-28
[    15.917] X Protocol Version 11, Revision 0
[    15.917] Build Operating System: Linux 4.1.12-gentoo x86_64 Gentoo
[    15.917] Current Operating System: Linux IT-CDITRI-Lin 4.6.3-gentoo #1 SMP Thu Jul 7 11:00:16 EDT 2016 x86_64
[    15.917] Kernel command line: BOOT_IMAGE=/vmlinuz-4.6.3-gentoo root=UUID=86f1df57-3f7e-486c-a962-c246e3086628 ro video=uvesafb:1280x1024-32,mtrr:3,ywrap
[    15.917] Build Date: 05 January 2016  09:54:42AM
[    15.917] 
[    15.917] Current version of pixman: 0.32.8
[    15.917]    Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[    15.917] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    15.917] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Jul  7 11:26:09 2016
[    15.920] (==) Using config file: "/etc/X11/xorg.conf"
[    15.920] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    15.920] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    15.922] (==) ServerLayout "X.org Configured"
[    15.922] (**) |-->Screen "Screen0" (0)
[    15.922] (**) |   |-->Monitor "Monitor0"
[    15.922] (**) |   |-->Device "Device0"
[    15.922] (**) |-->Input Device "Mouse0"
[    15.922] (**) |-->Input Device "Keyboard0"
[    15.922] (**) Option "Xinerama" "0"
[    15.922] (==) Automatically adding devices
[    15.922] (==) Automatically enabling devices
[    15.922] (==) Automatically adding GPU devices
[    15.926] (==) FontPath set to:
        /usr/share/fonts/misc/,
        /usr/share/fonts/TTF/,
        /usr/share/fonts/OTF/,
        /usr/share/fonts/Type1/,
        /usr/share/fonts/100dpi/,
        /usr/share/fonts/75dpi/
[    15.926] (**) ModulePath set to "/usr/lib64/opengl/nvidia,/usr/lib64/xorg/modules"
[    15.926] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[    15.926] (WW) Disabling Mouse0
[    15.926] (WW) Disabling Keyboard0
[    15.926] (II) Loader magic: 0x801c40
[    15.926] (II) Module ABI versions:
[    15.926]    X.Org ANSI C Emulation: 0.4
[    15.926]    X.Org Video Driver: 19.0
[    15.926]    X.Org XInput driver : 21.0
[    15.926]    X.Org Server Extension : 9.0
[    15.926] (II) xfree86: Adding drm device (/dev/dri/card0)
[    15.929] (--) PCI:*(0:2:0:0) 10de:1381:3842:2757 rev 162, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000dc80/128, BIOS @ 0x????????/131072
[    15.929] (II) LoadModule: "glx"
[    15.932] (II) Loading /usr/lib64/opengl/nvidia/extensions/libglx.so
[    16.000] (II) Module glx: vendor="NVIDIA Corporation"
[    16.000]    compiled for 4.0.2, module version = 1.0.0
[    16.000]    Module class: X.Org Server Extension
[    16.001] (II) NVIDIA GLX Module  367.27  Thu Jun  9 18:19:55 PDT 2016
[    16.002] (II) LoadModule: "nvidia"
[    16.005] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
[    16.012] (II) Module nvidia: vendor="NVIDIA Corporation"
[    16.012]    compiled for 4.0.2, module version = 1.0.0
[    16.012]    Module class: X.Org Video Driver
[    16.013] (II) NVIDIA dlloader X Driver  367.27  Thu Jun  9 17:57:30 PDT 2016
[    16.013] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[    16.013] (++) using VT number 7

[    16.016] (II) Loading sub module "fb"
[    16.016] (II) LoadModule: "fb"
[    16.016] (II) Loading /usr/lib64/xorg/modules/libfb.so
[    16.017] (II) Module fb: vendor="X.Org Foundation"
[    16.017]    compiled for 1.17.4, module version = 1.0.0
[    16.017]    ABI class: X.Org ANSI C Emulation, version 0.4
[    16.017] (II) Loading sub module "wfb"
[    16.017] (II) LoadModule: "wfb"
[    16.017] (II) Loading /usr/lib64/xorg/modules/libwfb.so
[    16.019] (II) Module wfb: vendor="X.Org Foundation"
[    16.019]    compiled for 1.17.4, module version = 1.0.0
[    16.019]    ABI class: X.Org ANSI C Emulation, version 0.4
[    16.019] (II) Loading sub module "ramdac"
[    16.019] (II) LoadModule: "ramdac"
[    16.019] (II) Module "ramdac" already built-in
[    16.021] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[    16.021] (==) NVIDIA(0): RGB weight 888
[    16.021] (==) NVIDIA(0): Default visual is TrueColor
[    16.021] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[    16.021] (**) NVIDIA(0): Option "Stereo" "0"
[    16.021] (**) NVIDIA(0): Option "nvidiaXineramaInfoOrder" "DFP-0"
[    16.021] (**) NVIDIA(0): Option "SLI" "Off"
[    16.021] (**) NVIDIA(0): Option "MultiGPU" "Off"
[    16.022] (**) NVIDIA(0): Option "BaseMosaic" "off"
[    16.022] (**) NVIDIA(0): Stereo disabled by request
[    16.022] (**) NVIDIA(0): NVIDIA SLI disabled.
[    16.022] (**) NVIDIA(0): NVIDIA Multi-GPU disabled.
[    16.022] (**) NVIDIA(0): Option "MetaModes" "DVI-I-1: nvidia-auto-select +1280+0, DP-1: nvidia-auto-select +0+0"
[    16.022] (**) NVIDIA(0): Enabling 2D acceleration
[    16.663] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:2:0:0
[    16.663] (--) NVIDIA(0):     CRT-0
[    16.663] (--) NVIDIA(0):     DFP-0 (boot)
[    16.663] (--) NVIDIA(0):     DFP-1
[    16.663] (--) NVIDIA(0):     DFP-2
[    16.663] (--) NVIDIA(0):     DFP-3
[    16.675] (--) NVIDIA(0): CRT-0: disconnected
[    16.675] (--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock
[    16.675] (--) NVIDIA(0):
[    16.700] (--) NVIDIA(0): Samsung SME2420L (DFP-0): connected
[    16.700] (--) NVIDIA(0): Samsung SME2420L (DFP-0): Internal TMDS
[    16.700] (--) NVIDIA(0): Samsung SME2420L (DFP-0): 330.0 MHz maximum pixel clock
[    16.700] (--) NVIDIA(0):
[    16.713] (--) NVIDIA(0): DELL 1704FPT (DFP-1): connected
[    16.713] (--) NVIDIA(0): DELL 1704FPT (DFP-1): Internal TMDS
[    16.713] (--) NVIDIA(0): DELL 1704FPT (DFP-1): 165.0 MHz maximum pixel clock
[    16.713] (--) NVIDIA(0):
[    16.713] (--) NVIDIA(0): DFP-2: disconnected
[    16.713] (--) NVIDIA(0): DFP-2: Internal TMDS
[    16.713] (--) NVIDIA(0): DFP-2: 165.0 MHz maximum pixel clock
[    16.713] (--) NVIDIA(0):
[    16.713] (--) NVIDIA(0): DFP-3: disconnected
[    16.713] (--) NVIDIA(0): DFP-3: Internal DisplayPort
[    16.713] (--) NVIDIA(0): DFP-3: 960.0 MHz maximum pixel clock
[    16.713] (--) NVIDIA(0):
[    16.714] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 750 (GM107-A) at PCI:2:0:0 (GPU-0)
[    16.714] (--) NVIDIA(0): Memory: 1048576 kBytes
[    16.714] (--) NVIDIA(0): VideoBIOS: 82.07.32.00.54
[    16.714] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[    16.714] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[    16.714] (**) NVIDIA(0):     device Samsung SME2420L (DFP-0) (Using EDID frequencies
[    16.714] (**) NVIDIA(0):     has been enabled on all display devices.)
[    16.716] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[    16.716] (**) NVIDIA(0):     device DELL 1704FPT (DFP-1) (Using EDID frequencies has
[    16.717] (**) NVIDIA(0):     been enabled on all display devices.)
[    16.718] (II) NVIDIA(0): Validated MetaModes:
[    16.718] (II) NVIDIA(0):   
[    16.718] (II) NVIDIA(0):     "DVI-I-1:nvidia-auto-select+1280+0,DP-1:nvidia-auto-select+0+0"
[    16.718] (II) NVIDIA(0): Virtual screen size determined to be 3200 x 1080
[    16.731] (--) NVIDIA(0): DPI set to (93, 94); computed from "UseEdidDpi" X config
[    16.731] (--) NVIDIA(0):     option
[    16.731] (--) Depth 24 pixmap format is 32 bpp
[    16.732] (II) NVIDIA: Using 12288.00 MB of virtual memory for indirect memory
[    16.732] (II) NVIDIA:     access.
[    16.739] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[    16.739] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[    16.739] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[    16.739] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[    16.739] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[    16.739] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[    16.739] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[    16.739] (II) NVIDIA(0):     Config Options in the README.
[    16.763] (II) NVIDIA(0): Setting mode "DVI-I-1:nvidia-auto-select+1280+0,DP-1:nvidia-auto-select+0+0"
[    16.820] (==) NVIDIA(0): Disabling shared memory pixmaps
[    16.820] (==) NVIDIA(0): Backing store enabled
[    16.820] (==) NVIDIA(0): Silken mouse enabled
[    16.821] (==) NVIDIA(0): DPMS enabled
[    16.821] (II) Loading sub module "dri2"
[    16.821] (II) LoadModule: "dri2"
[    16.821] (II) Module "dri2" already built-in
[    16.821] (II) NVIDIA(0): [DRI2] Setup complete
[    16.821] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[    16.822] (--) RandR disabled
[    16.822] (II) Initializing extension GLX
[    16.822] (II) Indirect GLX disabled.
[    16.929] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[    16.929] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[    16.929] (II) LoadModule: "evdev"
[    16.930] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
[    16.932] (II) Module evdev: vendor="X.Org Foundation"
[    16.932]    compiled for 1.17.4, module version = 2.9.2
[    16.932]    Module class: X.Org XInput Driver
[    16.932]    ABI class: X.Org XInput driver, version 21.0
[    16.932] (II) Using input driver 'evdev' for 'Power Button'
[    16.932] (**) Power Button: always reports core events
[    16.932] (**) evdev: Power Button: Device: "/dev/input/event1"
[    16.932] (--) evdev: Power Button: Vendor 0 Product 0x1
[    16.932] (--) evdev: Power Button: Found keys
[    16.932] (II) evdev: Power Button: Configuring as keyboard
[    16.932] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[    16.932] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[    16.932] (**) Option "xkb_rules" "evdev"
[    16.932] (**) Option "xkb_model" "pc104"
[    16.932] (**) Option "xkb_layout" "us"
[    16.947] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[    16.947] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[    16.947] (II) Using input driver 'evdev' for 'Power Button'
[    16.947] (**) Power Button: always reports core events
[    16.947] (**) evdev: Power Button: Device: "/dev/input/event0"
[    16.947] (--) evdev: Power Button: Vendor 0 Product 0x1
[    16.947] (--) evdev: Power Button: Found keys
[    16.947] (II) evdev: Power Button: Configuring as keyboard
[    16.947] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0/event0"
[    16.947] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[    16.947] (**) Option "xkb_rules" "evdev"
[    16.947] (**) Option "xkb_model" "pc104"
[    16.947] (**) Option "xkb_layout" "us"
[    16.948] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event4)
[    16.948] (II) No input driver specified, ignoring this device.
[    16.948] (II) This device may have been added with another device file.
[    16.948] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event5)
[    16.948] (II) No input driver specified, ignoring this device.
[    16.948] (II) This device may have been added with another device file.
[    16.948] (II) config/udev: Adding input device HDA NVidia HDMI/DP (/dev/input/event6)
[    16.948] (II) No input driver specified, ignoring this device.
[    16.948] (II) This device may have been added with another device file.
[    16.949] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event7)
[    16.949] (II) No input driver specified, ignoring this device.
[    16.949] (II) This device may have been added with another device file.
[    16.949] (II) config/udev: Adding input device HDA Intel Mic (/dev/input/event8)
[    16.949] (II) No input driver specified, ignoring this device.
[    16.949] (II) This device may have been added with another device file.
[    16.949] (II) config/udev: Adding input device HDA Intel Line (/dev/input/event9)
[    16.949] (II) No input driver specified, ignoring this device.
[    16.949] (II) This device may have been added with another device file.
[    16.949] (II) config/udev: Adding input device HDA Intel Line Out (/dev/input/event10)
[    16.949] (II) No input driver specified, ignoring this device.
[    16.949] (II) This device may have been added with another device file.
[    16.950] (II) config/udev: Adding input device HDA Intel Front Headphone (/dev/input/event11)
[    16.950] (II) No input driver specified, ignoring this device.
[    16.950] (II) This device may have been added with another device file.
[    16.950] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event2)
[    16.950] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[    16.950] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[    16.950] (**) Logitech USB Receiver: always reports core events
[    16.950] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event2"
[    16.950] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc52b
[    16.950] (--) evdev: Logitech USB Receiver: Found keys
[    16.950] (II) evdev: Logitech USB Receiver: Configuring as keyboard
[    16.950] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.0/0003:046D:C52B.0001/input/input5/event2"
[    16.950] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 8)
[    16.950] (**) Option "xkb_rules" "evdev"
[    16.950] (**) Option "xkb_model" "pc104"
[    16.950] (**) Option "xkb_layout" "us"
[    16.951] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event3)
[    16.951] (**) Logitech USB Receiver: Applying InputClass "evdev pointer catchall"
[    16.951] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[    16.951] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[    16.951] (**) Logitech USB Receiver: always reports core events
[    16.951] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event3"
[    16.951] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc52b
[    16.951] (--) evdev: Logitech USB Receiver: Found 20 mouse buttons
[    16.951] (--) evdev: Logitech USB Receiver: Found scroll wheel(s)
[    16.951] (--) evdev: Logitech USB Receiver: Found relative axes
[    16.951] (--) evdev: Logitech USB Receiver: Found x and y relative axes
[    16.951] (--) evdev: Logitech USB Receiver: Found absolute axes
[    16.951] (II) evdev: Logitech USB Receiver: Forcing absolute x/y axes to exist.
[    16.951] (--) evdev: Logitech USB Receiver: Found keys
[    16.951] (II) evdev: Logitech USB Receiver: Configuring as mouse
[    16.951] (II) evdev: Logitech USB Receiver: Configuring as keyboard
[    16.951] (II) evdev: Logitech USB Receiver: Adding scrollwheel support
[    16.951] (**) evdev: Logitech USB Receiver: YAxisMapping: buttons 4 and 5
[    16.951] (**) evdev: Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[    16.951] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.1/0003:046D:C52B.0002/input/input6/event3"
[    16.951] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 9)
[    16.951] (**) Option "xkb_rules" "evdev"
[    16.951] (**) Option "xkb_model" "pc104"
[    16.951] (**) Option "xkb_layout" "us"
[    16.951] (II) evdev: Logitech USB Receiver: initialized for relative axes.
[    16.951] (WW) evdev: Logitech USB Receiver: ignoring absolute axes.
[    16.951] (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
[    16.951] (**) Logitech USB Receiver: (accel) acceleration profile 0
[    16.951] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[    16.951] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[    16.952] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/mouse0)
[    16.952] (II) No input driver specified, ignoring this device.
[    16.952] (II) This device may have been added with another device file.
[    40.992] (--) NVIDIA(GPU-0): CRT-0: disconnected
[    40.992] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[    40.993] (--) NVIDIA(GPU-0):
[    41.017] (--) NVIDIA(GPU-0): Samsung SME2420L (DFP-0): connected
[    41.017] (--) NVIDIA(GPU-0): Samsung SME2420L (DFP-0): Internal TMDS
[    41.017] (--) NVIDIA(GPU-0): Samsung SME2420L (DFP-0): 330.0 MHz maximum pixel clock
[    41.017] (--) NVIDIA(GPU-0):
[    41.031] (--) NVIDIA(GPU-0): DELL 1704FPT (DFP-1): connected
[    41.031] (--) NVIDIA(GPU-0): DELL 1704FPT (DFP-1): Internal TMDS
[    41.031] (--) NVIDIA(GPU-0): DELL 1704FPT (DFP-1): 165.0 MHz maximum pixel clock
[    41.031] (--) NVIDIA(GPU-0):
[    41.031] (--) NVIDIA(GPU-0): DFP-2: disconnected
[    41.031] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
[    41.031] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[    41.031] (--) NVIDIA(GPU-0):
[    41.032] (--) NVIDIA(GPU-0): DFP-3: disconnected
[    41.032] (--) NVIDIA(GPU-0): DFP-3: Internal DisplayPort
[    41.032] (--) NVIDIA(GPU-0): DFP-3: 960.0 MHz maximum pixel clock
[    41.032] (--) NVIDIA(GPU-0):
[    41.157] (II) NVIDIA(0): Setting mode "DVI-I-1: nvidia-auto-select @1920x1080 +1280+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, DP-0: nvidia-auto-select @1280x1024 +0+0 {ViewPortIn=1280x1024, ViewPortOut=1280x1024+0+0}"
[    41.561] (--) NVIDIA(GPU-0): CRT-0: disconnected
[    41.561] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[    41.561] (--) NVIDIA(GPU-0):
[    41.586] (--) NVIDIA(GPU-0): Samsung SME2420L (DFP-0): connected
[    41.586] (--) NVIDIA(GPU-0): Samsung SME2420L (DFP-0): Internal TMDS
[    41.586] (--) NVIDIA(GPU-0): Samsung SME2420L (DFP-0): 330.0 MHz maximum pixel clock
[    41.586] (--) NVIDIA(GPU-0):
[    41.599] (--) NVIDIA(GPU-0): DELL 1704FPT (DFP-1): connected
[    41.599] (--) NVIDIA(GPU-0): DELL 1704FPT (DFP-1): Internal TMDS
[    41.599] (--) NVIDIA(GPU-0): DELL 1704FPT (DFP-1): 165.0 MHz maximum pixel clock
[    41.599] (--) NVIDIA(GPU-0):
[    41.599] (--) NVIDIA(GPU-0): DFP-2: disconnected
[    41.599] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
[    41.599] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[    41.599] (--) NVIDIA(GPU-0):
[    41.600] (--) NVIDIA(GPU-0): DFP-3: disconnected
[    41.600] (--) NVIDIA(GPU-0): DFP-3: Internal DisplayPort
[    41.600] (--) NVIDIA(GPU-0): DFP-3: 960.0 MHz maximum pixel clock
[    41.600] (--) NVIDIA(GPU-0):
[    44.612] (--) NVIDIA(GPU-0): CRT-0: disconnected
[    44.612] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[    44.612] (--) NVIDIA(GPU-0):
[    44.636] (--) NVIDIA(GPU-0): Samsung SME2420L (DFP-0): connected
[    44.636] (--) NVIDIA(GPU-0): Samsung SME2420L (DFP-0): Internal TMDS
[    44.636] (--) NVIDIA(GPU-0): Samsung SME2420L (DFP-0): 330.0 MHz maximum pixel clock
[    44.636] (--) NVIDIA(GPU-0):
[    44.650] (--) NVIDIA(GPU-0): DELL 1704FPT (DFP-1): connected
[    44.650] (--) NVIDIA(GPU-0): DELL 1704FPT (DFP-1): Internal TMDS
[    44.650] (--) NVIDIA(GPU-0): DELL 1704FPT (DFP-1): 165.0 MHz maximum pixel clock
[    44.650] (--) NVIDIA(GPU-0):
[    44.650] (--) NVIDIA(GPU-0): DFP-2: disconnected
[    44.650] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
[    44.650] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[    44.650] (--) NVIDIA(GPU-0):
[    44.651] (--) NVIDIA(GPU-0): DFP-3: disconnected
[    44.651] (--) NVIDIA(GPU-0): DFP-3: Internal DisplayPort
[    44.651] (--) NVIDIA(GPU-0): DFP-3: 960.0 MHz maximum pixel clock
[    44.651] (--) NVIDIA(GPU-0):
[    44.663] (--) NVIDIA(GPU-0): CRT-0: disconnected
[    44.663] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
[    44.663] (--) NVIDIA(GPU-0):
[    44.687] (--) NVIDIA(GPU-0): Samsung SME2420L (DFP-0): connected
[    44.687] (--) NVIDIA(GPU-0): Samsung SME2420L (DFP-0): Internal TMDS
[    44.687] (--) NVIDIA(GPU-0): Samsung SME2420L (DFP-0): 330.0 MHz maximum pixel clock
[    44.687] (--) NVIDIA(GPU-0):
[    44.701] (--) NVIDIA(GPU-0): DELL 1704FPT (DFP-1): connected
[    44.701] (--) NVIDIA(GPU-0): DELL 1704FPT (DFP-1): Internal TMDS
[    44.701] (--) NVIDIA(GPU-0): DELL 1704FPT (DFP-1): 165.0 MHz maximum pixel clock
[    44.701] (--) NVIDIA(GPU-0):
[    44.701] (--) NVIDIA(GPU-0): DFP-2: disconnected
[    44.701] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
[    44.701] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[    44.701] (--) NVIDIA(GPU-0):
[    44.701] (--) NVIDIA(GPU-0): DFP-3: disconnected
[    44.701] (--) NVIDIA(GPU-0): DFP-3: Internal DisplayPort
[    44.701] (--) NVIDIA(GPU-0): DFP-3: 960.0 MHz maximum pixel clock
[    44.701] (--) NVIDIA(GPU-0):

_________________
To look without without looking within is like looking without without looking at all.
Back to top
View user's profile Send private message
Logicien
Veteran
Veteran


Joined: 16 Sep 2005
Posts: 1360
Location: Montréal

PostPosted: Fri Jul 08, 2016 7:57 pm    Post subject: Reply with quote

Hi,
at the beginning I was using Nvidia drivers. Than I switch to Nouveau. Nouveau give me 3000 FPS according with Glxgears. Nvidia give more. It's like Radeon versus Fglrx, Fglrx is more performant than Radeon. Both Nouveau and Radeon have been enough good for me. I never came back to Nvidia and Fglrx.

I prefer free softwares, so I give a chance to them even if proprietary ones can be better. I can contribute to ameliorate them, as a user I test them at the same time. Because free drivers are often written without full hardware specifications available, developpers do reverse engineering to write the code. It's a kind of miracle for me that this code work.

Linus Torvalds ever denounce the few collaboration of Nvidia with GNU/Linux.
_________________
Paul
Back to top
View user's profile Send private message
tomtom69
Apprentice
Apprentice


Joined: 09 Nov 2010
Posts: 193
Location: Bavaria

PostPosted: Mon Jul 11, 2016 5:04 pm    Post subject: Reply with quote

I had to set eselect opengl xorg-x11 (instead of "nvidia") in order to get plasma to start and work. Additionally I switched off all effects because they sometimes freezed the system.
However this is an older board (MCP61) with nvidia-drivers
Back to top
View user's profile Send private message
parramata
n00b
n00b


Joined: 25 Jul 2004
Posts: 18

PostPosted: Mon Jul 11, 2016 6:41 pm    Post subject: Reply with quote

tomtom69 wrote:
I had to set eselect opengl xorg-x11 (instead of "nvidia") in order to get plasma to start and work. Additionally I switched off all effects because they sometimes freezed the system.
However this is an older board (MCP61) with nvidia-drivers


I've some issues after the upgrade to KDE Plasma5. I've found this along the way to get my
box working, with one Intel graphic card, openrrc : https://bugs.kde.org/show_bug.cgi?id=338999
Back to top
View user's profile Send private message
grooveman
Veteran
Veteran


Joined: 24 Feb 2003
Posts: 1166

PostPosted: Mon Jul 11, 2016 7:30 pm    Post subject: Reply with quote

So it sounds like the only thing to do is try to work around it.

I find it interesting that every time I have a problem that vexes me for this long it always traces itself back to one of the very, very few closed-source components of my system. Nvidia is usually pretty good, but I seem to recall something like this before several years back... they eventually sorted it out. I think most of the Ubuntu-style users never use VTs, so they probably don't even notice, so it probably isn't a priority to NVidia. They will get it eventually, I think. But I don't know how much longer I can hold out.

I think I will try nouveau on one of my systems, and see how it goes.

Thanks.

G
_________________
To look without without looking within is like looking without without looking at all.
Back to top
View user's profile Send private message
tomtom69
Apprentice
Apprentice


Joined: 09 Nov 2010
Posts: 193
Location: Bavaria

PostPosted: Tue Jul 12, 2016 8:13 am    Post subject: Reply with quote

Nouveau may be the better choice if it works with your chipset (and it works with most chipsets).
I would also use it, but I am stuck at nvidia drivers because nouveau has severe problems with my old board (https://bugzilla.kernel.org/show_bug.cgi?id=50091)
Back to top
View user's profile Send private message
Roman_Gruber
Advocate
Advocate


Joined: 03 Oct 2006
Posts: 3806
Location: Austro Bavaria

PostPosted: Tue Jul 12, 2016 10:00 am    Post subject: Reply with quote

Please choose a better title

Problems with stability with kde5

I assume your issues are with kde5, so I leave this topic as is.
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6825
Location: Austria

PostPosted: Tue Jul 12, 2016 11:05 am    Post subject: Reply with quote

There is no kde5.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
gerard27
Advocate
Advocate


Joined: 04 Jan 2004
Posts: 2377
Location: Netherlands

PostPosted: Tue Jul 12, 2016 12:14 pm    Post subject: Reply with quote

@genstorm
Quote:
There is no kde5.

Then what's the correct name for the new kde crap?
Gerard.
_________________
To install Gentoo I use sysrescuecd.Based on Gentoo,has firefox to browse Gentoo docs and mc to browse (and edit) files.
The same disk can be used for 32 and 64 bit installs.
You can follow the Handbook verbatim.
http://www.sysresccd.org/Download
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6825
Location: Austria

PostPosted: Tue Jul 12, 2016 12:36 pm    Post subject: Reply with quote

gerard82 wrote:
Then what's the correct name for the new kde crap?

You are offtopic here.
grooveman wrote:
If I so much as run a startx and fire up TWM, the problems arise.

_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
grooveman
Veteran
Veteran


Joined: 24 Feb 2003
Posts: 1166

PostPosted: Tue Jul 12, 2016 12:37 pm    Post subject: Reply with quote

Quote:
Then what's the correct name for the new kde crap?


I assume he means it is referred to as Plasma Desktop.


I did try nouveau, and there is not yet any 3D acceleration for my card, so I'm going to have to wait... hopefully it won't be too long... I suppose I could kill my framebuffer and see if that helps...
_________________
To look without without looking within is like looking without without looking at all.
Back to top
View user's profile Send private message
grooveman
Veteran
Veteran


Joined: 24 Feb 2003
Posts: 1166

PostPosted: Tue Jul 12, 2016 12:39 pm    Post subject: Reply with quote

Quote:
You are offtopic here.
grooveman wrote:
If I so much as run a startx and fire up TWM, the problems arise.


I don't see how. It is a relevant trouble-shooting step for the problems I'm experiencing.
_________________
To look without without looking within is like looking without without looking at all.
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6825
Location: Austria

PostPosted: Tue Jul 12, 2016 12:47 pm    Post subject: Reply with quote

grooveman wrote:
I don't see how. It is a relevant trouble-shooting step for the problems I'm experiencing.

Yes of course, it is your thread - it was directed at gerard. And anyone else who might have missed that step - looking at tw04l124 there.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
Roman_Gruber
Advocate
Advocate


Joined: 03 Oct 2006
Posts: 3806
Location: Austro Bavaria

PostPosted: Tue Jul 12, 2016 1:09 pm    Post subject: Reply with quote

grooveman wrote:
Quote:
You are offtopic here.
grooveman wrote:
If I so much as run a startx and fire up TWM, the problems arise.


I don't see how. It is a relevant trouble-shooting step for the problems I'm experiencing.


Yes it is, as you have issues with kde and not generic issues. Choosing a proper title is the first step to get things solved faster and to not waste valueable times of your forum members.

Generic, I do not read topics of software which i do not use.

issues with kde crap => clear the user uses kde desctop environment

so PLEASE AGAIN, change the topic title, thank you.

Your title suggests you have generic issues, but you have a specific issue with kde crap, which was already discussed pages over pages over months. I suggest a forum search for kde plasma. And it always the same stuff, it is not proper designed / coded / not supported by the gpu drivers.


---

just quick reading your text wall, considering of your nvidia card works or not ... no one asked for this so far

?? do you have direct rendering?

Code:
roman@ASUS-G75VW ~ $ glxinfo |grep Yes
direct rendering: Yes


When you get that, than your nvidia-drivers works

Check also full output of glxinfo,

e.g.

Code:
glxinfo |grep 4.50\ NVIDIA
OpenGL core profile shading language version string: 4.50 NVIDIA
OpenGL shading language version string: 4.50 NVIDIA


only newest mesa now supports 4.5 opengl. before it was afaik 4.2 opengl standard.

--

When you want to rule out things, you need to install another desctop environment. No idea waht to recommend. xfce?

--

i am not sure if you need it or not, but jsut for reference. Becaue your first few posts may state, or i understood it that way, that you are unable to use the X server with the binary drivers. (at least i understood it that way quick reading it)


nvidia-drivers here, amd64 unstable, 4.6.3 kernel 660m gtx nvidia notebook

Code:
ASUS-G75VW etc # cat /etc/X11/xorg.conf.d/20opengl.conf
Section "Files"
   ModulePath "/usr/lib32/xorg/modules"
   ModulePath "/usr/lib64/opengl/nvidia"
   ModulePath "/usr/lib64/xorg/modules"
EndSection
ASUS-G75VW etc # cat /etc/X11/xorg.conf.d/nvidia.conf
Section "Device"
         Identifier  "nvidia"
         Driver      "nvidia"
         Option "Coolbits" "28"
         Option "NoLogo" "True"
EndSection

# This is a trailing line, it is needed so that End Section is not the last line


and no /etc/xorg.conf or what it was called years back.
these are all to get my box running without setting up my external monitor with nvidia-settigs every time i use it.
Back to top
View user's profile Send private message
grooveman
Veteran
Veteran


Joined: 24 Feb 2003
Posts: 1166

PostPosted: Tue Jul 12, 2016 1:29 pm    Post subject: Reply with quote

tw04l124 wrote:

Yes it is, as you have issues with kde and not generic issues. Choosing a proper title is the first step to get things solved faster and to not waste valueable times of your forum members.


Running twm from a startx shows that the problem is not with KDE and not with sddm. There was no KDE involved, and the problem persisted, so I removed it from the topic title.
_________________
To look without without looking within is like looking without without looking at all.
Back to top
View user's profile Send private message
Chiitoo
Administrator
Administrator


Joined: 28 Feb 2010
Posts: 1687
Location: Here and Away Again

PostPosted: Thu Aug 18, 2016 2:07 pm    Post subject: Reply with quote

gerard82,

I sometimes call it 'KDEFP5' or 'KDEPF5', more or less as a joke, but in case you haven't bumped to it before, here's something that should clear up at least some things about the official naming they went with: There’s no such thing as KDE 5, and its status on Gentoo

grooveman,

Did you try disabling 'uvesafb' (and any other in-kernel framebuffer drivers)?

You might (probably should) see something like this in your 'dmesg' output:

Code:
NVRM: Your system is not currently configured to drive a VGA console
NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
NVRM: requires the use of a text-mode VGA console. Use of other console
NVRM: drivers including, but not limited to, vesafb, may result in
NVRM: corruption and stability problems, and is not supported.

Indeed, I've had quite a few different kinds of issues with 'x11-drivers/nvidia-drivers' while using 'vesafb', and quite recently I did experience something very similar, if not identical to what you describe here. I can't remember which version of nvidia-drivers that was with, however, but I do see I still have 'x11-drivers/nvidia-drivers-367.18' masked.

That said, it may or may not have been this issue that I do still have, where 'kwin' (from 'kde-base/kwin-4.11.22') sometimes starts using a core's worth of CPU, and everything seems frozen (most commonly happens when switching away from an x-session to the text console). I can switch to a virtual terminal, kill 'kwin', then switch back to the x-session, and with some luck, I can start 'kwin' anew via a terminal emulator I usually have open, and recover. This has been happening a lot more recently, but I do believe that it's a different issue, possibly this bug, though it's pretty old and I only really noticed it recently myself (and from the looks of it, it probably won't be fixed in the version of 'kwin' I use).

I'm almost sure that hasn't happened with compositing disabled, but I can't remember if the more serious issue did.

Aside from that, things seem to be working okay here, with 'x11-drivers/nvidia-drivers-367.35-r1' and 'sys-kernel/ck-sources-4.7.0', even while using 'vesafb' to get a nice high-resolution console.
_________________
Kind Regards,
~ The Noob Unlimited ~

Sore wa sore, kore wa kore.
Back to top
View user's profile Send private message
grooveman
Veteran
Veteran


Joined: 24 Feb 2003
Posts: 1166

PostPosted: Mon Aug 22, 2016 1:56 pm    Post subject: Reply with quote

[quote="Chiitoo"]gerard82,

Code:
NVRM: Your system is not currently configured to drive a VGA console
NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
NVRM: requires the use of a text-mode VGA console. Use of other console
NVRM: drivers including, but not limited to, vesafb, may result in
NVRM: corruption and stability problems, and is not supported.

Thank you, but unfortunately, this is not my problem... even though the symptoms sound similar. There is nothing like this in my dmesg. I suspect that my is related to my framebuffer and the latest nvidia drivers... but a VT without framebuffer nowdays is is nigh-useless. So, I'm really hoping that this will be fixed with a subsequent release of nvidia drivers, or kernel...

I've exhausted so much time on this, I'm afraid I can afford no more right now. I will sit tight, and hope that this works itself out with time. But I wish to reiterate: my problems do not appear to be KDE related. The same thing happens in TWM, in the most stripped-down environment possible. At first I thought it was KDE, but it has subsequently been proven to not be the case. Likewise, the problems do not seem to occur on systems that do not have nvidia cards in them, or that use Optimus. My systems with an nvidia card as primary all seem to exhibit this issue (under gentoo anyway).

I appreciate the input though.

G
_________________
To look without without looking within is like looking without without looking at all.
Back to top
View user's profile Send private message
Chiitoo
Administrator
Administrator


Joined: 28 Feb 2010
Posts: 1687
Location: Here and Away Again

PostPosted: Mon Aug 22, 2016 6:01 pm    Post subject: Reply with quote

I probably need to make my post a bit more clear-like. Sorry about that! :]

I agree that your issue is not KDE-specific. I added the KDE (kwin/nvidia-drivers) issue I have had as a side-note, as it was related to my experience, and indeed similar, but the main focus was supposed to be that the proprietary 'x11-drivers/nvidia-drivers' and in-kernel framebuffer drivers /really/ isn't a supported combination, and that I have experienced similar, if not identical issues (not KDE-specific) before with said combo.

So whenever you have the time and energy to look into this again, I would suggest disabling 'uvesafb' (do you actually use that for anything else than a high(er) resolution console? I tried it years ago, but I didn't make use of its special features so I went with the more simple 'vesafb').

Also worth trying with 'x11-drivers/nvidia-drivers-367.35-r1', if possible.
_________________
Kind Regards,
~ The Noob Unlimited ~

Sore wa sore, kore wa kore.
Back to top
View user's profile Send private message
grooveman
Veteran
Veteran


Joined: 24 Feb 2003
Posts: 1166

PostPosted: Thu Aug 25, 2016 7:01 pm    Post subject: Reply with quote

OK. I decided to bite the bullet on this one, and go back to VESAFB.

That did the trick! My system behaves as it should. They changed how vesafb works a little bit since I last used it. I used to use vga=0x792. Now it likes vga=0x31B ... just in case anyone else tries this. Otherwise, you get a 640x480 fb display, which isn't really very useful.

I feel like I have a system again. Thanks for the help.

G
_________________
To look without without looking within is like looking without without looking at all.
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