Re: [gentoo-user] Removing Packages with Portage
On Mon, 4 May 2009 13:11:02 +0100 Matt Causey wrote: --snip-- > > Along the same lines, how does the ebuild know what to remove on > --unmerge? For example I'm wandering around and looking at ebuilds: > > prometheus ethtool # pwd > /usr/portage/sys-apps/ethtool > prometheus ethtool # ls > ChangeLog Manifest ethtool-6.ebuild metadata.xml > prometheus ethtool # > > I see nothing in that ebuild which describes the files that ethtool > put on the system. Yet an --unmerge removes the binaries and > sourceinteresting. > > So I found a CONTENTS file: > > prometheus ethtool-6 # pwd > /var/db/pkg/sys-apps/ethtool-6 > prometheus ethtool-6 # cat CONTENTS > dir /usr > dir /usr/sbin --snip-- Another way to check which files are installed by a given package and to which package a given file belongs. emerge app-portage/portage-utils (if you haven't already) Example: ~ $ qlist ethtool /usr/share/man/man8/ethtool.8.bz2 /usr/share/doc/ethtool-6/AUTHORS.bz2 /usr/share/doc/ethtool-6/ChangeLog.bz2 /usr/share/doc/ethtool-6/NEWS.bz2 /usr/share/doc/ethtool-6/README.bz2 /usr/sbin/ethtool ~ $ ~ $ qfile ethtool sys-apps/ethtool (/usr/sbin/ethtool) ~ $ ~ $ qlist nvidia-drivers | grep /lib/modules /lib/modules/2.6.28-core2/video/nvidia.ko ~ $ HTH -- Best regards, Daniel
Re: [gentoo-user] Removing Packages with Portage
> Out of tree kernel modules are a maintenance pain in the ass, and cause > severely non-obvious problems like this. Every time you upgrade your kernel, > you must rebuild the out-of-tree modules, and you do that by re-running > "emerge madwifi-ng". This builds a new modules that matches the currently > configured kernel (/usr/src/linux/) and puts the module in > /lib/modules/ > > Upgrade your kernel a few times and you have various versions of modules > floating around. Portage remembers the modules installed by the most recent > emerge, but AFAIK forgets all the previous ones. This is expected of course - > when you upgrade firefox-2 to firefox-3 you would not expect the system to > remember the firefox-2 files (as they are supposed to not be there anymore) Your explanation is extremely helpful here. Thanks! As long as I know the expectation, I can plan for it when troubleshooting. I can certainly see the 'pain in the ass' factor there. :-) I was originally chasing a panic caused by ath_pci - but now that I've looked more closely at the issue that you describe here, I see that I did manage to get 2 incompatible interdependent modules installed in the system...grrr. I'll be doing some more-than-casual tinkering with ath_pci vs ath5k in the coming weeks, so I'll probably just plan not to use that ebuild for the present moment. :-) Althoughwould it be non-trivial for me to try and extend the ebuild to make it clean up after itself on unmerge? Along the same lines, how does the ebuild know what to remove on --unmerge? For example I'm wandering around and looking at ebuilds: prometheus ethtool # pwd /usr/portage/sys-apps/ethtool prometheus ethtool # ls ChangeLog Manifest ethtool-6.ebuild metadata.xml prometheus ethtool # I see nothing in that ebuild which describes the files that ethtool put on the system. Yet an --unmerge removes the binaries and sourceinteresting. So I found a CONTENTS file: prometheus ethtool-6 # pwd /var/db/pkg/sys-apps/ethtool-6 prometheus ethtool-6 # cat CONTENTS dir /usr dir /usr/sbin obj /usr/sbin/ethtool e830749ff2f81cc25b6629b19e93e3e7 1241002052 dir /usr/share dir /usr/share/doc dir /usr/share/doc/ethtool-6 obj /usr/share/doc/ethtool-6/NEWS.bz2 8757829b0fb19bb74c968c203fc76b68 1241002049 obj /usr/share/doc/ethtool-6/AUTHORS.bz2 11b48a9d12c1cebcb2ae6bb29e80d1e1 1241002049 obj /usr/share/doc/ethtool-6/ChangeLog.bz2 08b981d7a1afb29bbac1636ae81026c2 1241002049 obj /usr/share/doc/ethtool-6/README.bz2 3188a9ad571f7e4e4d0c1df4479db6d4 1241002049 dir /usr/share/man dir /usr/share/man/man8 obj /usr/share/man/man8/ethtool.8.bz2 71a609e8a269cc9dcc0e813e77675ab6 1241002049 prometheus ethtool-6 # Based on this, it looks like portage internally records the files which get installed.and then can retrieve this information later (qfile might want this information, --unmerge might want it...etc.). Is this the correct way to understand how portage maintains sanity? Thanks! -- Matt
[gentoo-user] Removing Packages with Portage
Hello all! I am a Gentoo n00b. I have question about what the 'expected behaviour' is/should be when removing packages under Gentoo package management. So I read this document: http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?style=printable&full=1#book_part2 And it says, to remove software, use 'emerge --unmerge'. Cool, yeah that seems to do what I expect... So, I have a package madwifi-ng, which contains some kernel modules. I want to emerge --unmerge that package, because I want to make those drivers go away. That seems to go well, as when I search for it in portage it show all non-installed and stuff: prometheus ~ # emerge --search madwifi-ng Searching... [ Results for search key : madwifi-ng ] [ Applications found : 2 ] * net-wireless/madwifi-ng Latest version available: 0.9.4 Latest version installed: [ Not Installed ] Size of files: 3,403 kB Homepage: http://www.madwifi-project.org/ Description: Next Generation driver for Atheros based IEEE 802.11a/b/g wireless LAN cards License: atheros-hal || ( BSD GPL-2 ) Buuut, there are still kernel modules there, which are owned by that package: prometheus ~ # ls -lah /lib/modules/2.6.28-gentoo-r5/net/ath_pci.ko -rw-r--r-- 1 root root 77K May 3 20:43 /lib/modules/2.6.28-gentoo-r5/net/ath_pci.ko prometheus ~ # and of course they still load. Sooo, my question. What is the expected behaviour here? Are the ebuilds intended to maintain knowledge of the files they put on a system, so they can remove the binaries when --unmerge'd? Are kernel modules handled differently because of the possibility of damaging a working system? Thanks! -- Matt
Re: [gentoo-user] Removing Packages with Portage
On Monday 04 May 2009 11:45:00 Matt Causey wrote: > Hello all! > > I am a Gentoo n00b. I have question about what the 'expected > behaviour' is/should be when removing packages under Gentoo package > management. So I read this document: > > http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?style=printable&full >=1#book_part2 > > And it says, to remove software, use 'emerge --unmerge'. Cool, yeah > that seems to do what I expect... So, I have a package madwifi-ng, > which contains some kernel modules. I want to emerge --unmerge that > package, because I want to make those drivers go away. That seems to > go well, as when I search for it in portage it show all non-installed > and stuff: > > prometheus ~ # emerge --search madwifi-ng > Searching... > [ Results for search key : madwifi-ng ] > [ Applications found : 2 ] > > * net-wireless/madwifi-ng > Latest version available: 0.9.4 > Latest version installed: [ Not Installed ] > Size of files: 3,403 kB > Homepage: http://www.madwifi-project.org/ > Description: Next Generation driver for Atheros based IEEE > 802.11a/b/g wireless LAN cards > License: atheros-hal || ( BSD GPL-2 ) > > Buuut, there are still kernel modules there, which are owned by that > package: > > prometheus ~ # ls -lah /lib/modules/2.6.28-gentoo-r5/net/ath_pci.ko > -rw-r--r-- 1 root root 77K May 3 20:43 > /lib/modules/2.6.28-gentoo-r5/net/ath_pci.ko > prometheus ~ # > > and of course they still load. > > Sooo, my question. What is the expected behaviour here? Are the > ebuilds intended to maintain knowledge of the files they put on a > system, so they can remove the binaries when --unmerge'd? That's the general idea. Except for *this* case :-) > Are kernel > modules handled differently because of the possibility of damaging a > working system? Out of tree kernel modules are a maintenance pain in the ass, and cause severely non-obvious problems like this. Every time you upgrade your kernel, you must rebuild the out-of-tree modules, and you do that by re-running "emerge madwifi-ng". This builds a new modules that matches the currently configured kernel (/usr/src/linux/) and puts the module in /lib/modules/ Upgrade your kernel a few times and you have various versions of modules floating around. Portage remembers the modules installed by the most recent emerge, but AFAIK forgets all the previous ones. This is expected of course - when you upgrade firefox-2 to firefox-3 you would not expect the system to remember the firefox-2 files (as they are supposed to not be there anymore) -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] kde-misc/synaptiks crashes immediately
On Sat, 22 Mar 2014 16:47:23 +0100 Alexander Puchmayr wrote: > Symptom: > Start synaptiks configuration module, get immedeately DrKonqi crash > report (trace attached, likely not much useful since I disabled debug > flags) Start either from kde systemsettings or konsole; the latter > gives > > alex@prometheus /datadisk/home/alex $ synaptiks > Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: > reading configurations from ~/.fonts.conf is deprecated. > KCrash: Application 'synaptiks' crashing... > KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from > kdeinit sock_file=/homedisk/alex/.kde4/socket-prometheus/kdeinit4__0 > unnamed app(17763): Communication problem with "synaptiks" , it > probably crashed. > Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message > did not receive a reply (timeout by message bus)" " > > Any ideas what could go wrong? The crash would reveal what is wrong; therefore, I suggest you to recompile the libraries of those packages with debug flags. See http://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces Besides that, you might be able to use strace and/or ltrace (with -f parameter; if needed, increase the -s parameter) to see what happens under the hood. I'm suspecting you'll find the cause by inspecting both; because as the trace mixes in evaluation of a Python script, you might need to use strace and/or ltrace to discover which Python script this is. A next step could be to use a debugger on that Python script if the trace, strace and/or ltrace are insufficient to reveal the cause. When you have found the cause, can you file the details in a bug at https://bugs.gentoo.org such that the maintainers are aware of this? Thank you very much in advance. -- With kind regards, Tom Wijsman (TomWij) Gentoo Developer E-mail address : tom...@gentoo.org GPG Public Key : 6D34E57D GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
Re: [gentoo-user] kdevelop broken (llvm slot issue)
Am Sonntag, 19. August 2018, 17:57:55 CEST schrieb Andrew Udvare: > > I am not having issues with KDevelop with Clang support and I have > everything on the latest version: > > LLVM 6.0.1-r1 libffi ncurses > Clang 6.0.1 +static-analyzer LLVM_TARGETS="AMDGPU BPF NVPTX X86" > KDevelop 5.2.3 gdbui hex plasma qmake welcomepage > kDevelop-php 5.2.3 > kdevelop-python 5.2.3 > Mesa 18.* classic dri3 egl gallium gbm gles2 llvm wayland > Thanks for the quick response. Upgrading to mesa 18 solves the problem. Regards Alex
Re: [gentoo-user] Removing Packages with Portage
On Monday 04 May 2009 14:11:02 Matt Causey wrote: > > Out of tree kernel modules are a maintenance pain in the ass, and cause > > severely non-obvious problems like this. Every time you upgrade your > > kernel, you must rebuild the out-of-tree modules, and you do that by > > re-running "emerge madwifi-ng". This builds a new modules that matches > > the currently configured kernel (/usr/src/linux/) and puts the module in > > /lib/modules/ > > > > Upgrade your kernel a few times and you have various versions of modules > > floating around. Portage remembers the modules installed by the most > > recent emerge, but AFAIK forgets all the previous ones. This is expected > > of course - when you upgrade firefox-2 to firefox-3 you would not expect > > the system to remember the firefox-2 files (as they are supposed to not > > be there anymore) > > Your explanation is extremely helpful here. Thanks! As long as I > know the expectation, I can plan for it when troubleshooting. I can > certainly see the 'pain in the ass' factor there. :-) I was > originally chasing a panic caused by ath_pci - but now that I've > looked more closely at the issue that you describe here, I see that I > did manage to get 2 incompatible interdependent modules installed in > the system...grrr. Love gotta love gentoo - break it, you get to keep both pieces :-) > I'll be doing some more-than-casual tinkering with > ath_pci vs ath5k in the coming weeks, so I'll probably just plan not > to use that ebuild for the present moment. :-) Althoughwould it > be non-trivial for me to try and extend the ebuild to make it clean up > after itself on unmerge? " Portage keeps it's house-keeping in /var/db/pkg with subdirectories in the form /-. There's interesting stuff in there, like a file called CONTENTS. It has the files installed by the ebuild, plus their md5sums, and that's how portage knows what to rm when you unmerge. "man ebuild" lists the functions you can override in ebuilds, including unmerge. It calls pkg_postrm (a simple bash function) so you could in theory insert a call to "find /lib/modules" to find all the modules in question and delete them. You'd have to think this through carefully though as the potential for destruction is vast... > Along the same lines, how does the ebuild know what to remove on > --unmerge? For example I'm wandering around and looking at ebuilds: > > prometheus ethtool # pwd > /usr/portage/sys-apps/ethtool > prometheus ethtool # ls > ChangeLog Manifest ethtool-6.ebuild metadata.xml > prometheus ethtool # > > I see nothing in that ebuild which describes the files that ethtool > put on the system. Yet an --unmerge removes the binaries and > sourceinteresting. Portage runs the ebuild in a restricted directory - /var/tmp/portage and all the built files end up there, in a directory structure that mirrors the root filesystem layout. "man ebuild" has all the gory details. Try this: run "ebuild /usr/portage/sys-apps/ethtool-6.ebuild install" and examine /var/tmp/portage/sys-apps/ethtool/work. Note that you emerge a *package name* but ebuild an ebuild *file* (much the same way yum install and rpm -ivh do it). That command will run all the ebuild steps up to and including install, but the files are not yet on the lie filesystem. "ebuild merge" does that, skipping all steps already completed. It then locates every file in the tmp directory and moves them onto the live filesystem, recording what it finds. This list is what goes in CONTENTS. Simple, hey? Virtually every tool out there which gives you information on installed packages (except eix, that also uses huge chunks of voodoo), looks in /var/db/pkg/, which explains why it's so slow - 1462 directories and 35847 files on this box is a lot of stuff to stat and read -- alan dot mckinnon at gmail dot com
[gentoo-user] kdevelop broken (llvm slot issue)
Hi there, After recent upgrades of mesa, llvm, clang etc kdevelop does not work anymore. It crashes immediately after start with errors : CommandLine Error: Option 'help-list' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options This issue is covered by bug https://bugs.gentoo.org/651658, which is open since March 2018 and no progress since also March 2018. It seems as if multiple slots of llvm cause the problems. mesa pulls in llvm: 5, while other programs pull in llvm:6 (via clang:6) Does anyone have an idea how to get a working kdevelop again? Regards Alex
Re: [gentoo-user] Re: nvidia-drivers segfault when starting X
On Friday 02 August 2013 02:38:37 Nikos Chantziaras wrote: > On 01/08/13 23:02, Alexander Puchmayr wrote: > > Hi there, > > > > When I start X (or start kdm), I get a segmentation fault and no X. > > > >[...] > > > > Kernel 3.8.18, nvidia-drivers 304.88 (Last to support the GeForce7600, > > newer drivers do not support it any more). > > > > Any ideas? > > Try manually rolling your own ebuild for 307.83. This is the latest > version for your card, but unfortunately it's not in portage. 304.88 > are a year old. > Thanks for the suggestion, but do you have a link for downloading the *.run file from nvidia? I can't find one on ftp://download.nvidia.com :-( Alex
Re: [gentoo-user] [SOLVED] Re: nvidia-drivers segfault when starting X
On Friday 02 August 2013 02:38:37 Nikos Chantziaras wrote: > On 01/08/13 23:02, Alexander Puchmayr wrote: > > Hi there, > > > > When I start X (or start kdm), I get a segmentation fault and no X. > > > >[...] > > > > Kernel 3.8.18, nvidia-drivers 304.88 (Last to support the GeForce7600, > > newer drivers do not support it any more). > > > > Any ideas? > > Try manually rolling your own ebuild for 307.83. This is the latest > version for your card, but unfortunately it's not in portage. 304.88 > are a year old. > A BIOS upgrade for my Asus F2A55-M MoBo to version 6402 solved the problem. Thanks to all who spent a thought on it Alex
Re: [gentoo-user] why you've chosen your desktop environment? (no war !)
> Thanks for the reminder ! -- I do indeed have Mupdf installed, > but had forgotten all about it : yes, it's quick & easy for simple browsing. > Evince has extra features, eg a side menu, but mb Mupdf is sufficient. If you're looking for a more feature-complete solution, check out llpp[1], which is based on mupdf. As a long time zathura user that switched to to mupdf because zathura's newest version now depends on >=x11-libs/gtk+-3.2:3, I found that mupdf had a few limitations and annoyances. I'm quite happy with llpp now and wouldn't want to go back. [1] - http://repo.or.cz/w/llpp.git -- Wolfgang Mueller / vehk.de / 0xc543cfce9465f573 That gum you like is going to come back in style. signature.asc Description: Digital signature
[gentoo-user] kstars and indilib
Hi there, I tried to compile kstars with useflag indi, but the provided version in portage is too old: [build.log from kstars] -- Checking for module 'libindi' -- Found libindi, version 1.6.0 -- INDI version 1.5.0 found in /usr/include/libindi, but at least version 1.7.1 is required -- INDI version 1.5.0 found in /usr/include/libindi, but at least version 1.7.1 is required -- Found INDI: /usr/lib/libindiclient.a, /usr/include/libindi I have no idea why it pretends to find indi-1.5.0, when 1.6 is installed :-( Version 1.6 is currently the only version in portage, which renders the useflag "indi" for kstars useless, as the resulting kstars binary does not support indi. https://indilib.org/download/gentoo.html shows a way to add an overlay, but the repo proposed does not exist anymore. Where do I find a ebuild for installing at least indilib-1.7.1? Regards Alex
[gentoo-user] sddm no longer working
Hi there, After last update, on one machine sddm-0.17.0-r1 no longer does not anything anymore. Systemd starts the service, and systemctl status shows that the sddm is running, and also ps jax shows a running sddm. apollo ~ # systemctl status sddm ● sddm.service - Simple Desktop Display Manager Loaded: loaded (/lib/systemd/system/sddm.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2018-04-04 16:41:28 CEST; 2s ago Docs: man:sddm(1) man:sddm.conf(5) Main PID: 8350 (sddm) CGroup: /system.slice/sddm.service └─8350 /usr/bin/sddm Apr 04 16:41:28 apollo systemd[1]: Started Simple Desktop Display Manager. Apr 04 16:41:28 apollo sddm[8350]: Initializing... Apr 04 16:41:28 apollo sddm[8350]: Logind interface found Apr 04 16:41:28 apollo sddm[8350]: Starting... But thats all. It does not create a log file (/var/log/sddm.log not touched, no entry), it does not start X (no process). It seems like sddm is starting and waiting for something I don't know. Any ideas? Thanks, Alex
[gentoo-user] kde-misc/synaptiks crashes immediately
Hi there, since the last world upgrade last week synaptiks no longer works on my laptop. x11-drivers/xf86-input-synaptics-1.7.1 kde-misc/synaptiks-0.8.1-r2 kde-base/kde-meta-4.11.5 dev-lang/python-2.7.5-r3 dev-lang/python-3.3.3 Symptom: Start synaptiks configuration module, get immedeately DrKonqi crash report (trace attached, likely not much useful since I disabled debug flags) Start either from kde systemsettings or konsole; the latter gives alex@prometheus /datadisk/home/alex $ synaptiks Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated. KCrash: Application 'synaptiks' crashing... KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit sock_file=/homedisk/alex/.kde4/socket-prometheus/kdeinit4__0 unnamed app(17763): Communication problem with "synaptiks" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " Any ideas what could go wrong? Thanks, Alex Application: synaptiks (synaptiks), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #5 0x7fca426060fb in ?? () from /usr/lib64/qt4/libQtCore.so.4 #6 0x7fca4260bb53 in QObject::connect(QObject const*, char const*, QObject const*, char const*, Qt::ConnectionType) () from /usr/lib64/qt4/libQtCore.so.4 #7 0x7fca3a8c3f44 in KActionCollection::addAction(QString const&, QAction*) () from /usr/lib64/libkdeui.so.5 #8 0x7fca3b208855 in ?? () from /usr/lib64/python2.7/site-packages/PyKDE4/kdeui.so #9 0x7fca46533dae in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0 #10 0x7fca46535535 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.7.so.1.0 #11 0x7fca46533af1 in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0 #12 0x7fca46535535 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.7.so.1.0 #13 0x7fca464c107c in ?? () from /usr/lib64/libpython2.7.so.1.0 #14 0x7fca4649b363 in PyObject_Call () from /usr/lib64/libpython2.7.so.1.0 #15 0x7fca464aa11f in ?? () from /usr/lib64/libpython2.7.so.1.0 #16 0x7fca4649b363 in PyObject_Call () from /usr/lib64/libpython2.7.so.1.0 #17 0x7fca464f1aa6 in ?? () from /usr/lib64/libpython2.7.so.1.0 #18 0x7fca464f1708 in ?? () from /usr/lib64/libpython2.7.so.1.0 #19 0x7fca4649b363 in PyObject_Call () from /usr/lib64/libpython2.7.so.1.0 #20 0x7fca4653282a in PyEval_EvalFrameEx () from /usr/lib64/libpython2.7.so.1.0 #21 0x7fca46535535 in PyEval_EvalCodeEx () from /usr/lib64/libpython2.7.so.1.0 #22 0x7fca464c107c in ?? () from /usr/lib64/libpython2.7.so.1.0 #23 0x7fca4649b363 in PyObject_Call () from /usr/lib64/libpython2.7.so.1.0 #24 0x7fca464aa11f in ?? () from /usr/lib64/libpython2.7.so.1.0 #25 0x7fca4649b363 in PyObject_Call () from /usr/lib64/libpython2.7.so.1.0 #26 0x7fca4652e517 in PyEval_CallObjectWithKeywords () from /usr/lib64/libpython2.7.so.1.0 #27 0x7fca401fee82 in ?? () from /usr/lib64/python2.7/site-packages/sip.so #28 0x7fca3fdfbfdd in ?? () from /usr/lib64/python2.7/site-packages/PyQt4/QtCore.so #29 0x7fca3b060aa6 in sipKUniqueApplication::newInstance() () from /usr/lib64/python2.7/site-packages/PyKDE4/kdeui.so #30 0x7fca3a9d4712 in ?? () from /usr/lib64/libkdeui.so.5 #31 0x7fca3a9d4788 in ?? () from /usr/lib64/libkdeui.so.5 #32 0x7fca3a9d48c9 in ?? () from /usr/lib64/libkdeui.so.5 #33 0x7fca41edda41 in ?? () from /usr/lib64/qt4/libQtDBus.so.4 #34 0x7fca41ede47f in ?? () from /usr/lib64/qt4/libQtDBus.so.4 #35 0x7fca41edee03 in ?? () from /usr/lib64/qt4/libQtDBus.so.4 #36 0x7fca41edeefb in ?? () from /usr/lib64/qt4/libQtDBus.so.4 #37 0x7fca4260fd6e in QObject::event(QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #38 0x7fca3e545864 in QApplication::event(QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #39 0x7fca3b06b3a3 in sipKUniqueApplication::event(QEvent*) () from /usr/lib64/python2.7/site-packages/PyKDE4/kdeui.so #40 0x7fca3e53bccc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #41 0x7fca3e53fa91 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #42 0x7fca3a9d12c6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #43 0x7fca3b06b44e in sipKUniqueApplication::notify(QObject*, QEvent*) () from /usr/lib64/python2.7/site-packages/PyKDE4/kdeui.so #44 0x7fca425f2a6e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #45 0x7fca425f5e11 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/qt4/libQtCore.so.4 #46 0x7fca42626c23 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #47 0x7fca408f43f5 in g_main_context_dispatch () f
Re: [gentoo-user] kde-misc/synaptiks crashes immediately [SOLVED]
Thanks for the reply.
strace showed very detailed the last syscalls before the SIGSEV:
[pid 21801] sendmsg(9, {msg_name(0)=NULL,
msg_iov(2)=[{"l\4\1\1\0\0\0\0\3\0\0\0X\0\0\0\1\1o\0\23\0\0\0/StatusNotifierItem\0\0\0\0\0\2\1s\0\32\0\0\0org.kde.StatusNotifierItem\0\0\0
\0\0\0\3\1s\0\7\0\0\0NewIcon\0", 104}, {"", 0}], msg_controllen=0,
msg_flags=0}, MSG_NOSIGNAL) = 104
[pid 21801] --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x8}
---
and file descriptor 9 was connected to dbus. Well, but this did not show WHERE
it crashed.
Next try was ltrace, but ltrace cannot be applied on python scripts (no ELF).
Finally, I checked the dependencies, and starting with pykde4 seemed to be a
good idea. Recompiled it with "USE=debug" and "CXXFLAGS=-O2 -g", and voila,
synaptiks worked without a problem. Hmmm.
So, recompiled pykde with the normal options, and it still worked.
Very strange, since I ran revdep-rebuild and pyhton-updater after the world
upgrade ...
Note@self: Maybe updating/re-emerging PyQt4 and pykde4 is worth the time, even
if its not neccessary.
However, it seems to work now.
Best regards
Alex
Am Samstag, 22. März 2014, 17:19:14 schrieb Tom Wijsman:
> On Sat, 22 Mar 2014 16:47:23 +0100
>
> Alexander Puchmayr wrote:
> > Symptom:
> > Start synaptiks configuration module, get immedeately DrKonqi crash
> > report (trace attached, likely not much useful since I disabled debug
> > flags) Start either from kde systemsettings or konsole; the latter
> > gives
> >
> > alex@prometheus /datadisk/home/alex $ synaptiks
> > Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14:
> > reading configurations from ~/.fonts.conf is deprecated.
> > KCrash: Application 'synaptiks' crashing...
> > KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from
> > kdeinit sock_file=/homedisk/alex/.kde4/socket-prometheus/kdeinit4__0
> > unnamed app(17763): Communication problem with "synaptiks" , it
> > probably crashed.
> > Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message
> > did not receive a reply (timeout by message bus)" "
> >
> > Any ideas what could go wrong?
>
> The crash would reveal what is wrong; therefore, I suggest you to
> recompile the libraries of those packages with debug flags.
>
> See http://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces
>
> Besides that, you might be able to use strace and/or ltrace (with -f
> parameter; if needed, increase the -s parameter) to see what happens
> under the hood.
>
> I'm suspecting you'll find the cause by inspecting both; because as
> the trace mixes in evaluation of a Python script, you might need to use
> strace and/or ltrace to discover which Python script this is.
>
> A next step could be to use a debugger on that Python script if the
> trace, strace and/or ltrace are insufficient to reveal the cause.
>
> When you have found the cause, can you file the details in a bug at
> https://bugs.gentoo.org such that the maintainers are aware of this?
>
> Thank you very much in advance.
--
Dipl. Ing. Alexander Puchmayr
Grundbachstraße 36
4060 Leonding, Österreich
Re: [gentoo-user] sddm no longer working
Am Mittwoch, 4. April 2018, 17:20:17 CEST schrieb Jack: > On 2018.04.04 11:14, Alexander Puchmayr wrote: > > Hi there, > > > > After last update, on one machine sddm-0.17.0-r1 no longer does not > > anything anymore. Systemd starts the service, and systemctl status > > shows that the sddm is running, and also ps jax shows a running sddm. > > > > apollo ~ # systemctl status sddm > > ● sddm.service - Simple Desktop Display Manager > > > >Loaded: loaded (/lib/systemd/system/sddm.service; enabled; vendor > > > > preset: disabled) > > > >Active: active (running) since Wed 2018-04-04 16:41:28 CEST; 2s ago > > > > Docs: man:sddm(1) > > > >man:sddm.conf(5) > > > > Main PID: 8350 (sddm) > > > >CGroup: /system.slice/sddm.service > > > >└─8350 /usr/bin/sddm > > > > Apr 04 16:41:28 apollo systemd[1]: Started Simple Desktop Display > > Manager. > > Apr 04 16:41:28 apollo sddm[8350]: Initializing... > > Apr 04 16:41:28 apollo sddm[8350]: Logind interface found > > Apr 04 16:41:28 apollo sddm[8350]: Starting... > > > > But thats all. It does not create a log file (/var/log/sddm.log not > > touched, no entry), it does not start X (no process). It seems like > > sddm is starting and waiting for something I don't know. > > > > Any ideas? > > > > Thanks, > > > > Alex > > Can you start X manually? Is there anything relevant in > /var/log/Xorg.0.log? Yes, I can start X manually, and it seems to work. But sddm does not even start X. > Are all sddm config files OK? I think so. They look the same as before the update (where it worked fine) Alex
Re: [gentoo-user] virtualbox: no x-server after kernel upgrade to 4.12.12-gentoo [SOLVED]
Am Freitag, 15. September 2017, 20:35:03 schrieb Alexander Kapshuk: > On Fri, Sep 15, 2017 at 5:47 PM, Alexander Puchmayr wrote: > [list with log dumps cutted] > > Obviously, something is going terribly wrong here, and I'm getting stuck > > as I > > do not have any Idea where to start. The only thing that changed is a > > kernel > > upgrade and a rebuild of the virtual box modules. > > > > Any ideas? > > > > Thanks in advance, > > > > Alex > > The Gentoo wiki article referenced below emphasizes the fact that certain > kernel config options need enabling in order to have proper hardware > emulation. So you want to make sure you have those enabled in your kernel > config. Then take it from there. > > https://wiki.gentoo.org/wiki/VirtualBox > Thanks for your hint, the kernel config was as it should be (except that I used modules wherever possible). My assumption was that the kernel frame buffer device and X driver conflict and the X server does not load because the kernel frame buffer driver was active. So, I removed the kernel driver by blacklisting vboxvideo $ cat /etc/modprobe.d/blacklist.conf blacklist vboxvideo $ genkernel initramfs [...] $ reboot After reboot: sddm showed a login screen, X was working (with VboxVideo driver), I could log in successfully. Problem solved :-) Thanks to all who spent a thought on this! Regards Alex PS: The question, why a framebuffer device for virtualbox is automatically created just to cause a conflict with X later on, still remains. Do other installations have the same problem?
[gentoo-user] libepoxy fails to compile on arm
Hi there, I'm trying to compile a system for my raspberry 2, and during compiling media-libs/libexpoxy-1.2, I encountered a problem: > libtool: compile: armv7a-hardfloat-linux-gnueabi-gcc -std=gnu99 > -DHAVE_CONFIG_H -I. > -I/var/tmp/portage/media-libs/libepoxy-1.2/work/libepoxy-1.2/src -I.. > -I/var/tmp/portage/media-libs/libepoxy-1.2/work/libepoxy-1.2/include > -I../include -Wall -Wpointer-arith -Wmissing-declarations -Wformat=2 > -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs > -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement > -Wunused -Wuninitialized -Wshadow -Wmissing-noreturn > -Wmissing-format-attribute -Wredundant-decls -Wlogical-op -Werror=implicit > -Werror=nonnull -Werror=init-self -Werror=main -Werror=missing-braces > -Werror=sequence-point -Werror=return-type -Werror=trigraphs > -Werror=array-bounds -Werror=write-strings -Werror=address > -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast > -fno-strict-aliasing -Wno-int-conversion -fvisibility=hidden -O2 -pipe > -march=armv7-a -mfpu=neon -mfloat-abi=hard -c > /var/tmp/portage/media-libs/libepoxy-1.2/work/libepoxy-1.2/src/dispatch_com > mon.c -fPIC -DPIC -o .libs/dispatch_common.o In file included from > ../include/epoxy/egl_generated.h:10:0, > > from > /var/tmp/portage/media-libs/libepoxy-1.2/work/libepoxy-1.2 > /include/epoxy/egl.h:46, from > /var/tmp/portage/media-libs/libepoxy-1.2/work/libepoxy-1.2 > /src/dispatch_common.h:48,> > from /var/tmp/portage/media- libs/libepoxy-1.2/work/libepoxy-1.2/src/dispatch_glx.c:28: > /usr/include/EGL/eglplatform.h:110:45: fatal error: > interface/vmcs_host/vc_dispmanx.h: No such file or directory> > #include "interface/vmcs_host/vc_dispmanx.h" > > ^ > > compilation terminated. > Makefile:614: recipe for target 'dispatch_glx.lo' failed > make[3]: *** [dispatch_glx.lo] Error 1 > make[3]: *** Waiting for unfinished jobs Obviously, a file interface/vmcs_host/vc_dispmanx.h cannot be found; Searching for it reveals that it is part of media-libs/raspberrypi-userland-0_pre20140117 and installed in /opt/vc/include/interface/vmcs_host/vc_dispmanx.h It seems like it is just a INCLUDEPATH problem, but I have no idea how to add a path to the build process. Thanks for suggestions Alex --
Re: [gentoo-user] virtualbox: no x-server after kernel upgrade to 4.12.12-gentoo
Am Freitag, 15. September 2017, 10:43:52 schrieb R0b0t1: > On Fri, Sep 15, 2017 at 9:47 AM, Alexander Puchmayr > > wrote: > > Hi there, > > > > I'm using a gentoo-guest inside a virtual box on a Win10 host. The last > > somewhat working combination was kernel 4.4.39/virtualbox-5.1.24. > > > > When I update to kernel 4.12.12, the X-Server does not work anymore (I've > > also tried with 4.9.xx, same result -- no X) > > > > I used genkernel to compile the kernel, copied the previous 4.4.39-config > > from /proc/config.gz to /usr/src/linux-4.12.12-gentoo via zcat, and did > > no further changes; so nothing relevant should be changed, at least to my > > knowledge. > > > > After compilation of the kernel, required packages have been re-emerged: > > - app-emulation/virtualbox-guest-additions > > - x11-drivers/xf86-video-virtualbox > > > > Booting with 4.12.12: > > - sddm crashes with segfaults > > - Starting X from the command line: X complains missing EGL_MESA_drm > > EGL_MESA_drm_image required. > > > > : CommandLine Error: Option 'asan-instrument-assembly' registered more > > : than > > > > once! > > LLVM ERROR: inconsistency in registered CommandLine options > > [??? No idea where this comes from :-( ] > > > > > > cat /var/log/Xorg.0.log > > [ 793.159] (II) LoadModule: "vboxvideo" > > [ 793.159] (II) Loading /usr/lib64/xorg/modules/drivers/vboxvideo_drv.so > > [ 793.159] (II) Module vboxvideo: vendor="Oracle Corporation" > > [ 793.159]compiled for 1.19.3, module version = 1.0.1 > > [ 793.159]Module class: X.Org Video Driver > > [ 793.159]ABI class: X.Org Video Driver, version 23.0 > > [ 793.159] (**) Load address of symbol "VBOXVIDEO" is 0x7f3840a24380 > > [ 793.160] (II) VBoxVideo: guest driver for VirtualBox: vbox > > [ 793.160] (II) modesetting: Driver for Modesetting Kernel Drivers: kms > > [ 793.160] (II) FBDEV: driver for framebuffer: fbdev > > [ 793.160] (II) VESA: driver for VESA chipsets: vesa > > [ 793.160] (II) vboxvideo: kernel driver found, not loading. > > <-- !! [ 793.160] (II) vboxvideo: kernel driver found, not loading. > > [ 793.160] (II) modeset(0): using drv /dev/dri/card0 > > [ 793.160] (II) Loading sub module "glamoregl" > > [ 793.160] (II) LoadModule: "glamoregl" > > [ 793.160] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so > > [ 793.163] (II) Module glamoregl: vendor="X.Org Foundation" > > [ 793.163]compiled for 1.19.3, module version = 1.0.0 > > [ 793.163]ABI class: X.Org ANSI C Emulation, version 0.4 > > [ 793.163] (II) glamor: OpenGL accelerated X.org driver based. > > [ 793.217] (II) glamor: EGL version 1.4 (DRI2): > > [ 793.217] EGL_MESA_drm_image required. > > [ 793.218] (EE) modeset(0): glamor initialization failed > > > > dmesg shows: > > 5.269630] VBoxService 5.1.24 r117012 (verbosity: 0) linux.amd64 (Sep 15 > > 2017 16:09:26) release log > > > > 00:00:00.46 main Log opened > > > > 2017-09-15T15:23:25.22099Z > > [5.269691] 00:00:00.000133 main OS Product: Linux > > [5.269717] 00:00:00.000165 main OS Release: 4.12.12-gentoo > > [5.269740] 00:00:00.000191 main OS Version: #1 SMP Fri Sep 15 > > 15:33:45 CEST 2017 > > [5.269772] 00:00:00.000213 main Executable: /usr/sbin/vboxguest- > > service > > > >00:00:00.000214 main Process ID: 4275 > >00:00:00.000215 main Package type: LINUX_64BITS_GENERIC > > > > (OSE) > > [5.272160] 00:00:00.002532 main 5.1.24 r117012 started. Verbose > > level = 0 > > [7.780006] vboxvideo :00:02.0: fb0: vboxdrmfb frame buffer device > > > > Booting old 4.4.39 kernel[Just select old kernel in grub] > > - sddm shows login screen > > - /var/log/Xorg.0.log shows lots of lines regarding VBoxVideo driver. > > - dmesg does not show the vboxvideo line from above > > > > Obviously, something is going terribly wrong here, and I'm getting stuck > > as I do not have any Idea where to start. The only thing that changed is > > a kernel upgrade and a rebuild of the virtual box modules. > > > > Any ideas? > > Details on this are sparse but you need to run @x11-modules-rebuild > after a kernel upgrade. You may also want to run @module-rebuild > depending on how you rebuilt your kernel. > > https://wiki.gentoo.org/wiki/X_server/upgrade > https://forums.gentoo.org/viewtopic-p-6633091.html > Thanks for the answer! I re-emerged both @x11-modules-rebuild and @module-rebuild, but it did not help a bit. Still the same problem. I assume that the key is the vboxvideo line from dmesg. It registers a framebuffer device fb0, which may cause the Xorg-driver to fail. But I do not know how to disable this, since it comes from the vbox driver module itself. Regards Alex
[gentoo-user] nvidia-drivers segfault when starting X
Hi there, When I start X (or start kdm), I get a segmentation fault and no X. The Xorg-log says: [ 8675.702] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32 [ 8675.702] (==) NVIDIA(0): RGB weight 888 [ 8675.702] (==) NVIDIA(0): Default visual is TrueColor [ 8675.702] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0) [ 8675.702] (**) NVIDIA(0): Option "TwinViewOrientation" "LeftOf" [ 8675.703] (**) NVIDIA(0): Option "AddARGBGLXVisuals" [ 8675.703] (**) NVIDIA(0): Option "UseEvents" "false" [ 8675.703] (**) NVIDIA(0): Enabling 2D acceleration [ 8676.186] (II) NVIDIA(GPU-0): Display (Samsung SyncMaster (DFP-0)) does not support NVIDIA [ 8676.186] (II) NVIDIA(GPU-0): 3D Vision stereo. [ 8676.253] (II) NVIDIA(GPU-0): Display (Eizo L565 (DFP-1)) does not support NVIDIA 3D Vision [ 8676.253] (II) NVIDIA(GPU-0): stereo. [ 8676.255] (II) NVIDIA(0): NVIDIA GPU GeForce 7600 GT (G73) at PCI:1:0:0 (GPU-0) [ 8676.255] (--) NVIDIA(0): Memory: 262144 kBytes [ 8676.255] (--) NVIDIA(0): VideoBIOS: 05.73.22.18.00 [ 8676.255] (II) NVIDIA(0): Detected PCI Express Link width: 16X [ 8676.255] (--) NVIDIA(0): Interlaced video modes are supported on this GPU [ 8676.255] (--) NVIDIA(0): Valid display device(s) on GeForce 7600 GT at PCI:1:0:0 [ 8676.255] (--) NVIDIA(0): CRT-0 [ 8676.255] (--) NVIDIA(0): CRT-1 [ 8676.255] (--) NVIDIA(0): TV-0 [ 8676.255] (--) NVIDIA(0): Samsung SyncMaster (DFP-0) (connected) [ 8676.255] (--) NVIDIA(0): Eizo L565 (DFP-1) (connected) [ 8676.255] (--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock [ 8676.255] (--) NVIDIA(0): CRT-1: 400.0 MHz maximum pixel clock [ 8676.255] (--) NVIDIA(0): TV-0: 400.0 MHz maximum pixel clock [ 8676.255] (--) NVIDIA(0): TV encoder: Unknown [ 8676.255] (--) NVIDIA(0): Samsung SyncMaster (DFP-0): 330.0 MHz maximum pixel clock [ 8676.255] (--) NVIDIA(0): Samsung SyncMaster (DFP-0): Internal Dual Link TMDS [ 8676.255] (--) NVIDIA(0): Eizo L565 (DFP-1): 165.0 MHz maximum pixel clock [ 8676.255] (--) NVIDIA(0): Eizo L565 (DFP-1): Internal Single Link TMDS [ 8676.255] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display [ 8676.255] (**) NVIDIA(0): device Samsung SyncMaster (DFP-0) (Using EDID frequencies [ 8676.255] (**) NVIDIA(0): has been enabled on all display devices.) [ 8676.255] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display [ 8676.255] (**) NVIDIA(0): device Eizo L565 (DFP-1) (Using EDID frequencies has been [ 8676.255] (**) NVIDIA(0): enabled on all display devices.) [ 8676.255] (II) NVIDIA(0): Validated MetaModes: [ 8676.255] (II) NVIDIA(0): "DFP-0:nvidia-auto-select,DFP-1:nvidia-auto- select" [ 8676.255] (II) NVIDIA(0): Virtual screen size determined to be 3200 x 1200 [ 8676.256] (WW) NVIDIA(0): Unable to support custom viewPortOut 1920 x 1080 +0 +60 [ 8676.256] (WW) NVIDIA(0): Unable to support custom viewPortOut 1920 x 1080 +0 +60 [ 8676.256] (--) NVIDIA(0): DPI set to (93, 95); computed from "UseEdidDpi" X config [ 8676.256] (--) NVIDIA(0): option [ 8676.256] (**) NVIDIA(0): Enabling 32-bit ARGB GLX visuals. [ 8676.256] (--) Depth 24 pixmap format is 32 bpp [ 8676.262] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto- select,DFP-1:nvidia-auto-select" [ 8676.286] (EE) [ 8676.286] (EE) Backtrace: [ 8676.286] (EE) 0: X (xorg_backtrace+0x34) [0x5cd634] [ 8676.286] (EE) 1: X (0x40+0x1d1ca9) [0x5d1ca9] [ 8676.286] (EE) 2: /lib64/libpthread.so.0 (0x7fe689cb+0x10810) [0x7fe689cc0810] [ 8676.286] (EE) 3: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fe6840d8000+0x11643b) [0x7fe6841ee43b] [ 8676.286] (EE) 4: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fe6840d8000+0x72773) [0x7fe68414a773] [ 8676.286] (EE) 5: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fe6840d8000+0xeaa01) [0x7fe6841c2a01] [ 8676.286] (EE) 6: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fe6840d8000+0xe30e4) [0x7fe6841bb0e4] [ 8676.286] (EE) 7: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fe6840d8000+0xe3820) [0x7fe6841bb820] [ 8676.286] (EE) 8: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fe6840d8000+0x9447b) [0x7fe68416c47b] [ 8676.286] (EE) 9: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fe6840d8000+0x8fedb) [0x7fe684167edb] [ 8676.286] (EE) 10: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fe6840d8000+0xde8f6) [0x7fe6841b68f6] [ 8676.286] (EE) 11: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fe6840d8000+0x56f6bb) [0x7fe6846476bb] [ 8676.286] (EE) 12: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7fe6840d8000+0x5609f1) [0x7fe6846389f1] [ 8676.286] (EE) 13: X (AddScreen+0x75) [0x43ddb5] [ 8676.286] (EE) 14: X (InitOutput+0x3ec) [0x48b20c] [ 8676.286] (EE) 15: X (0x40+0x29910) [0x429910] [ 8676.286] (EE) 16: /lib64/libc.so.6 (__libc_start_main+0xec) [0x7fe68890a4cc] [ 8676.286] (EE) 17: X (0x40+0x2a22d) [0x42a22d] [ 8676.286] (EE) [ 8676.28
RE: [gentoo-user] New PC hangs/lacks ?
Well, I think you should be able to set up some real-time monitoring that keeps collecting system status in the background and make some plot to observe if something's going wrong during the Blender workload. An easy setup would be to fire up a Prometheus and Grafana docker app, and to run some node_exporters to collect metrics on your machine in question. You may miss chances to reproduce the issue when you're looking out for them, but the monitoring system would catch it when you're not watching and things do go wrong. Also wanted to say that sys-apps/dstat seems to be a good quick glance over what's happening in the system on different aspects in a single place. It does this nice printing to the terminal once a second: 2 1 97 0 0| 0 8192B| 292B 16k| 0 0 | 684 1662 2 2 96 0 0| 0 0 | 346B 17k| 0 0 | 690 1641 --total-cpu-usage-- -dsk/total- -net/total- ---paging-- ---system-- usr sys idl wai stl| read writ| recv send| in out | int csw 2 1 97 0 0| 0 0 | 560B 17k| 0 0 | 696 1630 4 3 93 0 0| 0 0 |1060B 34k| 0 0 |1368 3231 2 1 97 0 0| 0 0 |1112B 18k| 0 0 | 699 1675 It's easy to overlook things when you're juggling with multiple monitoring apps like htop/iotop/... while having to manage the real workload simultaneously. Maybe try it out when you're dealing with system activity problems next time. Regards, -- Pengcheng Xu https://jsteward.moe > -Original Message- > From: tu...@posteo.de > Sent: Wednesday, May 6, 2020 11:10 PM > To: gentoo-user@lists.gentoo.org > Subject: Re: [gentoo-user] New PC hangs/lacks ? > > On 05/06 04:19, tu...@posteo.de wrote: > > On 05/06 07:07, Mark Knecht wrote: > > > On Wed, May 6, 2020 at 3:21 AM wrote: > > > > > > > > > > > > Hi, > > > > > > > > while rendering with Blender the system performance (especially > > > > graphic related stuff) lacks. That's not nice but it seems that > > > > this is the way it is designed. > > > > > > > > What makes me a little nervous are freezes of several seconds. It > > > > not onlu freezes but the whole graphical interface of everything > > > > locks down (I couldn't find a corona computer virus, though). > > > > > > > > In the Xorg log I found this: > > > > > > > > [ 2808.761] (WW) NVIDIA: Wait for channel idle timed out. > > > > > > > > which possibly match such a moment of a freeze. > > > > > > > > My setup: > > > > Blender 2.90a (alpha) and Blender 2.83 (beta) and Blender 2.82a > > > > (stable). > > > > All Blender versions show the same problem. > > > > > > > > X11/Openbox > > > > > > > > NVidia 484.82 as delivered by NVidia, since the Gentoo package > > > > does not install all files of the driver which are needed for > > > > Blender (for example to support Optix). > > > > > > > > No other application, which heavily uses the GPU was running at > > > > that time. > > > > > > > > MSI RTX 2060 SUPER > > > > Ryzen 5 3600 > > > > 32GB RAM > > > > MSI Tomahawk MAX > > > > > > > > Does everyone has the same problems probably already solved or any > > > > idea how I can those freezes? > > > > > > > > Any help or idea what causes this freezes is very appreciated! :) > > > > > > > > Cheers! > > > > Meino > > > > > > > > > > > > > > > > > > Meino, > > >Generically, you need to set up some sort of real-time monitoring > > > and watch to see what is using CPU and/or I/O when the machine > > > 'appears' to hang. I say 'appears' because the machine is probably > > > running correctly but doing something other than Blender work. > > > > > >NOTE: You didn't say that there is or isn't any disk activity > > > when this happens. > > > > > >When I look at this sort of problem I set up a second machine, > > > ssh in with a bunch of terminals and start with 'top' and 'iotop' to > > > watch for what process might be using resources. top watches CPU, > > > iotop watches disk. Conceptually networking can lock up the machine > > > but it's never happened to me. > > > > > >You can also look to see if some piece of hardware is generating > > > too
