Re: [CentOS] libreoffice 5 slow after 7.3 update
On 12/13/2016 11:44 PM, José María Terry Jiménez wrote: I had this problem in Fedora 22/23? and the solution was install LibreOffice 5.1 from the LibreOffice site. Thank you, I have installed the latest version from libreoffice site and everything is OK now. But I am wondering it is something with my setup or it's a bug in CentOS, does anybody encountered the same problem in CentOS 7.3? Best regards, Alexandru ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] libreoffice 5 slow after 7.3 update
Hello all, After the update to 7.3 libreoffice (5.0.6.2-3.el7.x86_64) became unusable slow. For an excel file with 250 rows even a simple scroll takes a few seconds, during that time the Xorg server is 100% working and the GPU utilization is at about 77% (from NVIDIA server settings). I have tried disabling the hardware acceleration (options->view) and OpenCL (options) but the problem and the high usage for Xorg and GPU persisted. I have seen the the same bug (probably) was present in Fedora 23 (libreoffice version 5.0.5.2-1.fc23.x86_64 https://bugzilla.redhat.com/show_bug.cgi?id=1308700) Does anyone had the same problem and if yes what was the fix? Does RedHat 7.3 has the same problem? I have searched the bugzilla database and found only the Fedora bug. System info: Intel I3-6098P, 8GB ram, NVIDIA GT 240 with all the packages updated. libreoffice-ure-5.0.6.2-3.el7.x86_64 libreoffice-opensymbol-fonts-5.0.6.2-3.el7.noarch libreoffice-core-5.0.6.2-3.el7.x86_64 libreoffice-pyuno-5.0.6.2-3.el7.x86_64 libreoffice-calc-5.0.6.2-3.el7.x86_64 libreoffice-writer-5.0.6.2-3.el7.x86_64 libreoffice-emailmerge-5.0.6.2-3.el7.x86_64 libreoffice-base-5.0.6.2-3.el7.x86_64 libreoffice-math-5.0.6.2-3.el7.x86_64 libreoffice-impress-5.0.6.2-3.el7.x86_64 libreoffice-graphicfilter-5.0.6.2-3.el7.x86_64 libreoffice-pdfimport-5.0.6.2-3.el7.x86_64 libreoffice-draw-5.0.6.2-3.el7.x86_64 libreoffice-5.0.6.2-3.el7.x86_64 libreoffice-langpack-ro-5.0.6.2-3.el7.x86_64 libreoffice-langpack-en-5.0.6.2-3.el7.x86_64 nvidia-x11-drv-340xx-32bit-340.98-1.el7.elrepo.x86_64 nvidia-x11-drv-340xx-340.98-1.el7.elrepo.x86_64 kmod-nvidia-340xx-340.98-1.el7.elrepo.x86_64 OpenGL version string: 3.3.0 NVIDIA 340.98 server glx version string: 1.4 Best regards, Alexandru Chiscan ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] test please ignore
test please ignore ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ssh -X versus -Y
I stand corrected. Regards, Lec On 06/26/2015 07:22 PM, Stuart Barkley wrote: On Fri, 26 Jun 2015 at 03:16 -, Alexandru Chiscan wrote: On 06/25/2015 11:51 PM, Stuart Barkley wrote: Then from your desktop (assuming Linux already running X) in a local xterm do something like: ssh -Y remote-system Do not use that because any user logged on the server can connect to your X server display and snoop what you are doing, open windows etc. -Y disables all the X server authentication mechanisms (http://www.x.org/wiki/Development/Documentation/Security/) I believe this is incorrect. The authentication protocols are still used (thus the need for the xorg-x11-xauth package on CentOS). This is not the same as 'xhost +' which should never be used. Both -X and -Y require read access to the ~/.Xauthority file on the remote system in order to connect back to the X server. You can see this by using the 'xauth remove' command to remove the authentication token for the display and clients can no longer connect. Note about -X versus -Y with ssh: -X enables basic X forwarding, It disables some X functionality making it safer to allow. -X also stops working after about 20 minutes (this is by design but not well documented). I only recently learned why it would stop working after pulling out the last of my hair. I have been using ssh X forwarding for current work use (local betwork) for more than 15 years and never got into this kind of problem from RH 7 to Centos 7, AIX and Solaris. Likewise, I've used ssh/X for 20+ years on a variety of systems. In most cases -X is sufficient, but some applications seem to require -Y and I have not dug into all of the reasons. Maybe it is some other issue that is closing your ssh connection (maybe you should use the KeepAlive options on the ssh server/client); just guessing. On Debian and FreeBSD 'man ssh_config' now shows: ForwardX11Timeout Specify a timeout for untrusted X11 forwarding using the format described in the TIME FORMATS section of sshd_config(5). X11 connections received by ssh(1) after this time will be refused. The default is to disable untrusted X11 forwarding after twenty minutes has elapsed. This option seems to have appeared in OpenSSH 6.0 [See more at the end of this email]. -Y allows the full X protocol which might be a security risk. Some applications will only work with -Y. With this, remote X applications can grab keyboard interactions, grab passwords, put windows on top of other windows (obscuring security messages), etc. For my own choice I use -Y (although I only enable it occasionally to specific systems). This is a recent behaviour change on my part with limited use to system I trust. Now that I know about the timeout I can probably just live with -X and will consider moving back to -X for my occasional use, The documentation of the practical differences between -X and -Y is pretty obscure (mostly defering to the X Security extension documentation). I would like to see better clarification of the differences. ...some additional research looking at the source code and revision history... The ForwardX11Timeout change was 5 years ago in OpenSSH 6.0. CentOS 6 still has OpenSSH 5.3 without this change (or if a patch was applied the documentation was not also patched). CentOS 7 has OpenSSH 6.6 which includes this change. http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/clientloop.c.diff?r1=1.220r2=1.221 Prior to that there was an intended hard coded 20 minute timeout since at least 2005: http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/clientloop.c.diff?r1=1.137r2=1.138 Based upon the comments in the June 2010 revision it appears that the timeout was not working correctly and perhaps was falling back to trusted authentication after 20 minutes: Add X11ForwardTimeout option to specify timeout for untrusted X11 authentication cookies to avoid fallback in X11 code to fully-trusted implicit authentication using SO_PEERCRED described at: http://lists.x.org/archives/xorg-devel/2010-May/008636.html After the X11ForwardTimeout has expired the client will now refuse incoming X11 channel opens. I will need to see it this is an unpatched security issue on CentOS/RedHat 6. If so, I claim credit for observing it as a possibility. Stuart ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] An odd X question
Hello Stuart, On 06/25/2015 11:51 PM, Stuart Barkley wrote: For (ssh based) X forwarding no X server needs to run on the server. I usually install the xorg-x11-xauth (necessary) and xterm (optional) rpms on all my servers in case X forwarding becomes necessary. Then from your desktop (assuming Linux already running X) in a local xterm do something like: ssh -Y remote-system Do not use that because any user logged on the server can connect to your X server display and snoop what you are doing, open windows etc. -Y disables all the X server authentication mechanisms (http://www.x.org/wiki/Development/Documentation/Security/) Note about -X versus -Y with ssh: -X enables basic X forwarding, It disables some X functionality making it safer to allow. -X also stops working after about 20 minutes (this is by design but not well documented). I only recently learned why it would stop working after pulling out the last of my hair. I have been using ssh X forwarding for current work use (local betwork) for more than 15 years and never got into this kind of problem from RH 7 to Centos 7, AIX and Solaris. Maybe it is some other issue that is closing your ssh connection (maybe you should use the KeepAlive options on the ssh server/client); just guessing. -Y allows the full X protocol which might be a security risk. Some applications will only work with -Y. With this, remote X applications can grab keyboard interactions, grab passwords, put windows on top of other windows (obscuring security messages), etc. For my own choice I use -Y (although I only enable it occasionally to specific systems). It is a security risk as I said above any user logged on the server can connect to your display X server without you knowing. Lec ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] rsyncing directories - sanity check
Hello Tim, On 06/24/2015 07:42 PM, Tim Dunphy wrote: rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32) rsync: write failed on /opt/var/log/lastlog: No space left on device (28) lastlog is a VERY large SPARSE file and when you rsync it it looses the sparsity and tries to copy all the data to /opt ls -al -h /var/log/lastlog -rw-r--r--. 1 root root *94G* Jun 25 09:10 /var/log/lastlog Real space on disk du -h /var/log/lastlog *60K* /var/log/lastlog Lec ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Folding At Home OT
Hello all,
On 04/28/2015 01:51 AM, Mark LaPierre wrote:
On 04/22/15 21:05, Mark LaPierre wrote:
Can someone recommend a good video card to use with CentOS 6.6 that has
a GPU, or two, or more, that will work with the Folding At Home project.
I built a killer machine primarily for contributing to the FAH effort
but the video card, NVIDIA Corporation G94 [GeForce 9600 GT], I had on
hand is not getting any assignments. I'm using the proprietary NVIDIA
driver. I've got a pcie 16X socket to plug it into.
I tried also to run a GPU queue with FAH and it seems that the client program needs a
newer libc library than available in C6.
The logs were not helpfull:
09:33:52:WU00:FS01:Running FahCore: /usr/bin/FAHCoreWrapper
/var/lib/fahclient/cores/web.stanford.edu/~pande/Linux/AMD64
/NVIDIA/Fermi/Core_17.fah/FahCore_17 -dir 00 -suffix 01 -version 704 -lifeline 13249
-checkpoint 15 -gpu 0 -gpu-vendor nvidia
09:33:52:WU00:FS01:Started FahCore on PID 13558
09:33:52:WU00:FS01:Core PID:13562
09:33:52:WU00:FS01:FahCore 0x17 started
09:33:53:WARNING:WU00:FS01:FahCore returned: FAILED_2 (1 = 0x1)
I have discovered the real error only after manually running the command listed in logs
with strace:
[pid 13645] writev(2, [{/var/lib/fahclient/cores/web.sta..., 96}, {: , 2},
{/lib64/libm.so.6, 16}, {: , 2}, {version `GLIBC_2.15' not found (..., 141}, {\n,
1}], 6) = 258
[pid 13645] writev(2, [{/var/lib/fahclient/cores/web.sta..., 96}, {: , 2},
{/usr/lib64/libstdc++.so.6, 25}, {: , 2}, {version `GLIBCXX_3.4.15' not fou...,
145}, {\n, 1}], 6) = 271
[pid 13645] writev(2, [{/var/lib/fahclient/cores/web.sta..., 96}, {: , 2},
{/lib64/libc.so.6, 16}, {: , 2}, {version `GLIBC_2.15' not found (..., 141}, {\n,
1}], 6) = 258
[pid 13645] writev(2, [{/var/lib/fahclient/cores/web.sta..., 96}, {: , 2},
{/lib64/libc.so.6, 16}, {: , 2}, {version `GLIBC_2.14' not found (..., 141}, {\n,
1}], 6) = 258
I have to investigate if there is a alternate fahclient (older version maybe) which works
in C6
Lec
PS: I have seen that the FAH executable for cpu queue is statically linked:
file
/var/lib/fahclient/cores/web.stanford.edu/~pande/Linux/AMD64/Core_a4.fah/FahCore_a4
/var/lib/fahclient/cores/web.stanford.edu/~pande/Linux/AMD64/Core_a4.fah/FahCore_a4: ELF
64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, for GNU/Linux 2.6.15,
stripped
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] OT: Bittorrent clients
ktorrent Lec ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] OT: Bittorrent clients
Isn't that a KDE-specific program? Yes, it's from kde. Works with Gnome as well? All kde programs work in all desktop managers provided that you install the required libraries. The same is true for gnome programs. LEC - Reply message - From: Sorin Srbu sorin.s...@orgfarm.uu.se To: Centos centos@centos.org Subject: [CentOS] OT: Bittorrent clients Date: Sun, Dec 28, 2014 13:14 Isn't that a KDE-specific program? Works with Gnome as well? //Sorin Sent from my tablet, please excuse the brevity. Alexandru Chiscan l...@easterng.ro wrote: ktorrent Lec ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] OT: Bittorrent clients
Hey, ktorrent looks pretty good! Thanks for the hint! Maybe it's time to give KDE a second look :) LEC ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] KDE on C6.5: start a program from command line on a specific screen
In KDE you can force the position, size, fullscreen etc based on the window properties: class title, etc. you can access the options by clicking right mouse button on the window title and selecting Advanced-Special Window Settings... you can memorize the positioning for your windows one in screen 0 and the other in screen 1 and after that start the virt-viewer with the -f option to force full screen - each window will go fullscreen in it's screen Lec On 04/30/2014 01:00 PM, Patrick Bervoets wrote: I'd like to start from konsole a virt-viewer to vm1 on screen vga1 and another virt-viewer to vm2 on screen lvds1. Anyone knows if this is possible with KDE on a CentOS 6.5? Thanks Patrick ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos -- Lec ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] write barrier support in CentOS 6
On 04/03/2014 06:25 AM, Tom Robinson wrote: On 02/04/14 20:17, Alexandru Chiscan wrote: On 04/02/2014 01:00 AM, Tom Robinson wrote: On 01/04/14 17:49, Alexandru Chiscan wrote: On 04/01/2014 06:27 AM, Keith Keller wrote: On 2014-04-01, Tom Robinson tom.robin...@motec.com.au wrote: Now, I understand that Red Hat (and therefore CentOS) backport many upstr= eam features into the stock kernel so how can I be sure that kernel 2.6.32-431.11.2.el6 has write bar= rier support? from the kernel changelog (https://access.redhat.com/knowledge/sources/source_rpms/kernel-2.6.32-431.11.2.el6/changelog) the barrier support for filesystems, lvm (dm) and md is active from 2.6.32-82-el6 Thanks Alexandru, I did look at the changelog but, for my untrained eye, I saw no specific reference to LVM there (and indeed still don't in your list above). Are you saying that because dm is patched, LVM is now implementing barriers correctly? As what I know the LVM system is implemented on top of dm (device mapper) (see http://en.wikipedia.org/wiki/Logical_Volume_Manager_%28Linux%29) so it should handle the barrier requests if dm does it. quote In the 2.6-series of the Linux Kernel, the *LVM is implemented in terms of the **device mapper http://en.wikipedia.org/wiki/Device_mapper*, a simple block-level scheme for creating virtual block devices and mapping their contents onto other block devices. This minimizes the amount of relatively hard-to-debug kernel code needed to implement the LVM. It also allows its I/O redirection services to be shared with other volume managers (such as EVMS http://en.wikipedia.org/wiki/Enterprise_Volume_Management_System). *Any LVM-specific code is pushed out into its user-space tools, which merely manipulate these mappings and reconstruct their state from on-disk metadata upon each invocation.* /quote Regards, Lec Kind regards, Tom ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos -- Lec ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] write barrier support in CentOS 6
On 04/02/2014 01:00 AM, Tom Robinson wrote: On 01/04/14 17:49, Alexandru Chiscan wrote: On 04/01/2014 06:27 AM, Keith Keller wrote: On 2014-04-01, Tom Robinson tom.robin...@motec.com.au wrote: Now, I understand that Red Hat (and therefore CentOS) backport many upstr= eam features into the stock kernel so how can I be sure that kernel 2.6.32-431.11.2.el6 has write bar= rier support? Take a look here: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/writebarrieronoff.html Regards, Lec Thanks Lec, I did read this already. It does address filesystems but not LVM. Are write barriers enabled for LVM? Write barriers need to be implemented through the entire stack for them to work. If you have ext4 on LVM on MD not having them on LVM would break the chain. N'est-ce pas? from the kernel changelog (https://access.redhat.com/knowledge/sources/source_rpms/kernel-2.6.32-431.11.2.el6/changelog) the barrier support for filesystems, lvm (dm) and md is active from 2.6.32-82-el6 -[fs]jbd2: replace barriers with explicit flush and FUA usage https://access.redhat.com/knowledge/sources/source_rpms/kernel-2.6.32-431.11.2.el6/patches/fs-jbd2-replace-barriers-with-explicit-flush-and-FUA-usage.patch (Mike Snitzer) [635199 https://bugzilla.redhat.com/show_bug.cgi?id=635199] -[fs]jbd2: Modify ASYNC_COMMIT code to not rely on queue draining on barrier https://access.redhat.com/knowledge/sources/source_rpms/kernel-2.6.32-431.11.2.el6/patches/fs-jbd2-Modify-ASYNC_COMMIT-code-to-not-rely-on-queue-draining-on-barrier.patch (Mike Snitzer) [635199 https://bugzilla.redhat.com/show_bug.cgi?id=635199] -[fs]jbd: replace barriers with explicit flush and FUA usage https://access.redhat.com/knowledge/sources/source_rpms/kernel-2.6.32-431.11.2.el6/patches/fs-jbd-replace-barriers-with-explicit-flush-and-FUA-usage.patch (Mike Snitzer) [635199 https://bugzilla.redhat.com/show_bug.cgi?id=635199] -[fs]gfs2: replace barriers with explicit flush and FUA usage https://access.redhat.com/knowledge/sources/source_rpms/kernel-2.6.32-431.11.2.el6/patches/fs-gfs2-replace-barriers-with-explicit-flush-and-FUA-usage.patch (Mike Snitzer) [635199 https://bugzilla.redhat.com/show_bug.cgi?id=635199] -[fs]btrfs: replace barriers with explicit flush and FUA usage https://access.redhat.com/knowledge/sources/source_rpms/kernel-2.6.32-431.11.2.el6/patches/fs-btrfs-replace-barriers-with-explicit-flush-and-FUA-usage.patch (Mike Snitzer) [635199 https://bugzilla.redhat.com/show_bug.cgi?id=635199] -[fs]xfs: replace barriers with explicit flush and FUA usage https://access.redhat.com/knowledge/sources/source_rpms/kernel-2.6.32-431.11.2.el6/patches/fs-xfs-replace-barriers-with-explicit-flush-and-FUA-usage.patch (Mike Snitzer) [635199 https://bugzilla.redhat.com/show_bug.cgi?id=635199] -[block]pass gfp_mask and flags to sb_issue_discard https://access.redhat.com/knowledge/sources/source_rpms/kernel-2.6.32-431.11.2.el6/patches/block-pass-gfp_mask-and-flags-to-sb_issue_discard.patch (Mike Snitzer) [635199 https://bugzilla.redhat.com/show_bug.cgi?id=635199] -[block]disallow FS recursion from sb_issue_discard allocation https://access.redhat.com/knowledge/sources/source_rpms/kernel-2.6.32-431.11.2.el6/patches/block-disallow-FS-recursion-from-sb_issue_discard-allocation.patch (Mike Snitzer) [635199 https://bugzilla.redhat.com/show_bug.cgi?id=635199] -[dm]convey that all flushes are processed as empty https://access.redhat.com/knowledge/sources/source_rpms/kernel-2.6.32-431.11.2.el6/patches/dm-convey-that-all-flushes-are-processed-as-empty.patch (Mike Snitzer) [635199 https://bugzilla.redhat.com/show_bug.cgi?id=635199] -[dm]fix locking context in queue_io() https://access.redhat.com/knowledge/sources/source_rpms/kernel-2.6.32-431.11.2.el6/patches/dm-fix-locking-context-in-queue_io.patch (Mike Snitzer) [635199 https://bugzilla.redhat.com/show_bug.cgi?id=635199] -[dm]relax ordering of bio-based flush implementation https://access.redhat.com/knowledge/sources/source_rpms/kernel-2.6.32-431.11.2.el6/patches/dm-relax-ordering-of-bio-based-flush-implementation.patch (Mike Snitzer) [635199 https://bugzilla.redhat.com/show_bug.cgi?id=635199] -[dm]implement REQ_FLUSH/FUA support for request-based dm https://access.redhat.com/knowledge/sources/source_rpms/kernel-2.6.32-431.11.2.el6/patches/dm-implement-REQ_FLUSH-FUA-support-for-request-based-dm.patch (Mike Snitzer) [635199 https://bugzilla.redhat.com/show_bug.cgi?id=635199] -[dm]implement REQ_FLUSH/FUA support for bio-based dm https://access.redhat.com/knowledge/sources/source_rpms/kernel-2.6.32-431.11.2.el6/patches/dm-implement-REQ_FLUSH-FUA-support-for-bio-based-dm.patch (Mike Snitzer) [635199 https://bugzilla.redhat.com/show_bug.cgi?id=635199] -[block]make __blk_rq_prep_clone() copy most command flags https://access.redhat.com/knowledge/sources/source_rpms/kernel-2.6.32-431.11.2.el6
Re: [CentOS] write barrier support in CentOS 6
On 04/01/2014 06:27 AM, Keith Keller wrote: On 2014-04-01, Tom Robinson tom.robin...@motec.com.au wrote: Now, I understand that Red Hat (and therefore CentOS) backport many upstr= eam features into the stock kernel so how can I be sure that kernel 2.6.32-431.11.2.el6 has write bar= rier support? Take a look here: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/writebarrieronoff.html Regards, Lec I believe you can look through the RHEL tech notes. Here they are for 6.5: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html-single/6.5_Technical_Notes/index.html If you require barriers, you can always use the mainline kernel from elrepo. You can read about the mainline and long-term packages here: http://elrepo.org/tiki/kernel-lt You probably want the kernel-ml packages, but that page doesn't mention the -lt packages. Lots of CentOS admins use these kernels (including me) and are happy with them. --keith -- Lec ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NVidia, again
On 03/26/2014 03:40 PM, m.r...@5-cent.us wrote: Johnny Hughes wrote: On 03/26/2014 08:14 AM, m.r...@5-cent.us wrote: Johnny Hughes wrote: On 03/26/2014 07:01 AM, mark wrote: On 03/26/14 03:01, Johnny Hughes wrote: On 03/25/2014 04:36 PM, m.r...@5-cent.us wrote: Got a HBS (y'know, Honkin' Big Server, one o' them technical terms), a Dell 720 with two Tesla GPUs. I updated the o/s, 6.5, and I cannot get the GPUs recognized. As a last resort, I d/l NVidia's proprietary driver/installer, 325, and it builds fine... I've yum removed the kmod-nvidia I had on the system, nouveau is blacklisted, and when I reboot, lsmod shows me nvidia loaded, which modinfo tells me looks like the one I built but enum_gpu, which is from a CUDA group, builds... but can't enumerate the GPUs (how we wake them up for the users). I see the /dev/nvidia*, and they're a+r, a+w Oh, and selinux is permissive. Anyone got a clue? If I can't get this working, I'm going to have to downgrade the system several kernels. Do you have an /etc/X11/xorg.conf file or something in /etc/X11/xorg.conf.d/ that actually name nvidia and not nv as the driver? Nope - nothing there. When you run the ./NVIDIAversion command to build the driver, one of the last steps is to have it automatically update your configuration file .. select yes for that and it should create an xorg.conf file that will use the nvidia driver. a) I didn't have that before - did kmod-nvidia handle loading the correct one *without* an xorg.conf? b) Do you think it'll do the right thing - this *is* a headless server. And a general question: what *does* kmod-nvidia do - is it different than, say, setting up a flag, or a script to notice that you're booting a new kernel, and run the proprietary installer -a -s? Are you connecting to the server to do X related things remotely ... and therefore need NVIDIA drivers for that? I think you missed that part of my original post: no X. This box has two Tesla GPUs, and my users are using them for heavy duty scientific computing And my problem is that neither their programs, nor the utility I use (I *think* it that it seems to be part of the CUDA toolkit - I didn't set that part up) can enumerate them... meaning that they can't see or use the GPUs. Try to install CUDA Toolkit (https://developer.nvidia.com/cuda-downloads), see from their FAQ: *Q: *Will the installer replace the driver currently installed on my system? *A: *The installer will provide an option to install the included driver, and if selected, it will replace the driver currently on your system. Lec I'll let one of the elrepo guys explain their RPM. Fair 'nough. I just threw that out as a general question, not expecting that was yours to answer. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos -- Lec ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] NVidia, again
On 03/26/2014 03:40 PM, m.r...@5-cent.us wrote: I think you missed that part of my original post: no X. This box has two Tesla GPUs, and my users are using them for heavy duty scientific computing And my problem is that neither their programs, nor the utility I use (I *think* it that it seems to be part of the CUDA toolkit - I didn't set that part up) can enumerate them... meaning that they can't see or use the GPUs. what is the error? For example if I run CUDA Device Query (example from cuda toolkit) I get the following error if the kernel module is not the version needed for the compiled version of cuda program (cuda toolkit 5.5 and nvidia kernel module 310.19 - installed from nvidia.com) #./deviceQuery ./deviceQuery Starting... CUDA Device Query (Runtime API) version (CUDART static linking) cudaGetDeviceCount returned 35 - CUDA driver version is insufficient for CUDA runtime version Result = FAIL -- Lec ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] libvirt hooks for startup and shutdown
On 07/15/2013 02:45 PM, AJH wrote: Hello list, could anyone tell me where are the hooks for libvirt/qemu/kvm? Read there: http://www.libvirt.org/hooks.html did you actually read it? quote The libvirt hook scripts are located in the directory |$SYSCONFDIR/libvirt/hooks/|. * *In Linux distributions such as Fedora and RHEL, this is **|/etc/libvirt/hooks/|*. Other Linux distributions may do this differently. * If your installation of libvirt has instead been compiled from source, it is likely to be |/usr/local/etc/libvirt/hooks/|. To use hook scripts, you will need to create this |hooks| directory manually, place the desired hook scripts inside, then make them executable. Script names At present, there are three hook scripts that can be called: * |/etc/libvirt/hooks/daemon| Executed when the libvirt daemon is started, stopped, or reloads its configuration * |/etc/libvirt/hooks/qemu| Executed when a QEMU guest is started, stopped, or migrated * |/etc/libvirt/hooks/lxc| Executed when an LXC guest is started or stopped /quote Lec I need the hooks for startup and stop at the Centos architecture. My version of libvirt: 0.9.10 -- thanks + bye ajh ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos -- Lec ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Repair grub GPT/UEFI?
On 06/13/2013 01:41 AM, Les Mikesell wrote: device (hd0) HD(1,800,64000,0557c1a7-7538-4ba1-b81e-74c4328b8b8d) Just an ideea: check this line to see if 0557c1a7-7538-4ba1-b81e-74c4328b8b8d is not related to the boot disk. you said you cloned it so probably you must put there the UUID of the cloned disk. -- Lec ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Google Earth on EL6.x x86_64
On 03/06/2013 05:54 AM, Fred Smith wrote: http://lists.centos.org/mailman/listinfo/centos Yes, I did the modifications given earlier by Earl and one other poster and now google earth starts up. but it complains there's no usable graphics card, and only displays the menus/borders/etc, with the main view window being empty/black. I do have a supported graphics card (Nvidia GeForce 9800GT), and have the nvidia drivers installed. can anyone advise how to make GE recognize it? I'm guessing it's failing because Google seems to be distributing 32-bit binaries instead of 64-bit binaries, but I've no clue how to fix this. Clues will be appreciated! try to install the nvidia 32bit compatibility libraries. if installed using the nvidia installer it asks you, if installed from elrepo use nvidia-x11-drv-32bit package Lec thanks in advance. Fred -- Lec ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Dual Monitor setup on CentOS 6?
On 03/30/2012 10:55 AM, Toralf Lund wrote: Hi. Is anyone here running CentOS 6 with dual monitors configured as a single X Screen? I'm trying such a setup on version 5 (again), using NVIDIA TwinView, and it works in many ways, but there are a number of problems that means it's not too usable - the most important one being that there appears to be no way to control which of the displays new applications/windows will appear on. I mean, I don't necessarily need to be able to configure this or anything, but I would at least expect programs to open on the monitor that displaying the menu item or icon or terminal or whatever used for startup, but often they end up on the other one. It's the window's manager job to do that using the XINERAMA X extension. see http://en.wikipedia.org/wiki/Xinerama For example in centos 6 KDE the window manager redirects the new windows in the display that have the mouse in, so if I start an application and quickly enough move the mouse to the desired screen, the application window displays in that screen. Lec So I guess my question is, would upgrading to version 6 help? - Toralf This e-mail, including any attachments and response string, may contain proprietary information which is confidential and may be legally privileged. It is for the intended recipient only. If you are not the intended recipient or transmission error has misdirected this e-mail, please notify the author by return e-mail and delete this message and any attachment immediately. If you are not the intended recipient you must not use, disclose, distribute, forward, copy, print or rely on this e-mail in any way except as permitted by the author. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos -- Lec ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] gtar compression achieved
On 02/01/2012 04:18 PM, Alan McKay wrote: Hey folks, I looked at the man page and don't see any way to do this - maybe it is a function of the compression program used I dunno. Is there any way to get gtar to report on the compression it achieved? I can't just check file sizes because I'm writing data to tape. The basic problem is that I know how much data is there to begin with but I don't know how much room it took up on the tape so I have no idea how much room is left on the tape. You could ask tar to automatically request tape change when reaching end of tape: -M, --multi-volume create/list/extract multi-volume archive Lec ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 6.1 Update request
Hello all I had the same problems with centos 6.0 and a SandyBridge laptop (Dell Latitude E5420 i5 2410M) On 09/19/2011 12:24 PM, John Hodrien wrote: On Sun, 18 Sep 2011, Timo Neuvonen wrote: I simply installed CentOS 6.0, downloaded kernel from SL6.1 repo, and installed it. Basically this is what was needed to make Intel graphics work, I think there were 1-2 other rpms I needed to upgrade too to fix dependencies, but this was easy to notice during the kernel install. If you don't mind passing on some details for me, as I've got a related problem. you have to install the following from SL 6.1: - latest kernel (kernel-2.6.32-131.12.1.el6) - kernel-firmware-2.6.32-131.12.1.el6 - latest xorg-x11-drv-intel (xorg-x11-drv-intel-2.14.0-1) with dependencies (xorg-x11-drivers) - latest mesa packages: mesa-dri-drivers, mesa-libGL, mesa-libGLU (version 7.10-1 at the moment) - latest libdrm (libdrm-2.4.23-1) Which intel chipset have you got? Does OpenGL work, and if so, what's you glxinfo output? openGL and DRI now work. (for my laptop also screen brightness and suspend to RAM work ok) Lec lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Sandy Bridge DRAM Controller [8086:0104] (rev 09) 00:02.0 VGA compatible controller [0300]: Intel Corporation Sandy Bridge Integrated Graphics Controller [8086:0116] (rev 09) 00:16.0 Communication controller [0780]: Intel Corporation Cougar Point HECI Controller #1 [8086:1c3a] (rev 04) 00:1a.0 USB Controller [0c03]: Intel Corporation Cougar Point USB Enhanced Host Controller #2 [8086:1c2d] (rev 04) 00:1b.0 Audio device [0403]: Intel Corporation Cougar Point High Definition Audio Controller [8086:1c20] (rev 04) 00:1c.0 PCI bridge [0604]: Intel Corporation Cougar Point PCI Express Root Port 1 [8086:1c10] (rev b4) 00:1c.1 PCI bridge [0604]: Intel Corporation Cougar Point PCI Express Root Port 2 [8086:1c12] (rev b4) 00:1c.5 PCI bridge [0604]: Intel Corporation Cougar Point PCI Express Root Port 6 [8086:1c1a] (rev b4) 00:1c.6 PCI bridge [0604]: Intel Corporation Cougar Point PCI Express Root Port 7 [8086:1c1c] (rev b4) 00:1d.0 USB Controller [0c03]: Intel Corporation Cougar Point USB Enhanced Host Controller #1 [8086:1c26] (rev 04) 00:1f.0 ISA bridge [0601]: Intel Corporation Cougar Point LPC Controller [8086:1c49] (rev 04) 00:1f.2 SATA controller [0106]: Intel Corporation Cougar Point 6 port SATA AHCI Controller [8086:1c03] (rev 04) 00:1f.3 SMBus [0c05]: Intel Corporation Cougar Point SMBus Controller [8086:1c22] (rev 04) 02:00.0 Network controller [0280]: Intel Corporation 6000 Series Gen2 [8086:0082] (rev 34) 03:00.0 SD Host controller [0805]: O2 Micro, Inc. Device [1217:8321] (rev 05) 03:00.1 Mass storage controller [0180]: O2 Micro, Inc. Device [1217:8331] (rev 05) 04:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5761 Gigabit Ethernet PCIe [14e4:1681] (rev 10) glxinfo name of display: :0.0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap, GLX_INTEL_swap_event GLX version: 1.4 GLX extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap OpenGL vendor string: Tungsten Graphics, Inc OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile GEM 20100330 DEVELOPMENT OpenGL version string: 2.1 Mesa 7.10 OpenGL shading language version string: 1.20 OpenGL extensions: GL_ARB_copy_buffer, GL_ARB_depth_clamp, GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_draw_elements_base_vertex, GL_ARB_explicit_attrib_location, GL_ARB_fragment_coord_conventions, GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, GL_ARB_fragment_shader, GL_ARB_framebuffer_object, GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, GL_ARB_map_buffer_range, GL_ARB_multisample,
Re: [CentOS] SCSI bad block table display
Hugh E Cruickshank wrote: Hi All: Is there a utility available that will allow for the dump/display of the bad track table of a SCSI drive. We had this capability on SCO OSR5 but I have not been able to locate anything similar for Linux. The closest I have found is the badblocks utility that is part of the e2fsprogs package but this appears to only test for bad blocks not display the current bad block table contents. I have done quite a bit of searching with Google but either it does not exist or (more than likely) I am using the wrong search parameters. TIA Regards, Hugh Hello, If you are looking for the table which badblocks builds then you should use dumpe2fs (for ext2/3 filesystem). man dumpe2fs DUMPE2FS(8) DUMPE2FS(8) NAME dumpe2fs - dump ext2/ext3 filesystem information SYNOPSIS dumpe2fs [ -bfhixV ] [ -ob superblock ] [ -oB blocksize ] device DESCRIPTION dumpe2fs prints the super block and blocks group information for the filesystem present on device. dumpe2fs is similar to Berkeley’s dumpfs program for the BSD Fast File System. OPTIONS -b print the blocks which are reserved as bad in the filesystem. Regards, Lec ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
