Discuss

discuss@lists.centos.org

8 participants
34745 discussions

Can't boot into GUI: Centos 7 "Server with GUI" option
by Jay Hart 09 Aug '18

09 Aug '18

I'm setting up a new server on Centos 7, running x86_64. Motherboard is a MITAC PD11BICC, running Indian Bay Trail, with a i915 chipset. I installed "Server with GUI", but when it boots I get the "blank screen with a cursor" issue. Decided to see about disabling the i915 driver, by blacklisting it. but I don't think I have the right commands, as when I did that, it appeared on the reboot the i915 driver was still active. vi /etc/modprobe.d/blacklist_i915.conf added the following line to that file blacklist i915 Saved the file. Rebooted. The driver seemed to active upon the reboot. Can someone tell me if this is the correct and full procedure to get rid of this driver. Thanks, Jay

2 1

Okular
by mark 08 Aug '18

08 Aug '18

Does anyone know what Magical configuration file determines whether okular give measurements, in the properties of a .pdf, in millimeters, rather than, say, inches or cm or furlongs? mark -- Measurements will always be given in the least convenient units, such as the speed of light in furlongs per fortnight

2 1

systemd equivalent of xinetd 'only_from' and 'banner_fail' attributes
by James Pearson 08 Aug '18

08 Aug '18

I'm attempting to port an existing xinetd service from CentOS 6 to something equivalent with systemd for CentOS 7 The existing xinetd config uses the attributes 'only_from' to limit connections from a limited set of remote hosts and 'banner_fail' to print a suitable error message when access is denied However, I can't find suitable 'equivalents' with systemd socket/service files on CentOS 7 It appears later versions of systemd supports the option IPAddressAllow= (which is what I think I need ?) Does anyone know how to limit the remote hosts that can connect to a port with CentOS 7's systemd ? Also, how to implement the equivalent of 'banner_fail' ? (not absolutely required, but nice to have) Thanks James Pearson

2 2

SSSD and cache persistence
by Pete Biggs 08 Aug '18

08 Aug '18

I have a large number of CentOS machines (both 6 & 7) getting account information from an LDAP database using SSSD. It all works fine and is fairly reliable. However, I'm having problems with persuading the caching system to forget about users when they are deleted from LDAP. I know about sss_cache with either -E or -U options, but that doesn't delete anything, just invalidates the cache entry. If the cache is invalid SSS will, obviously, go back to the source and return the information there, however, bizarrely, if the original source doesn't have the information (like when a user is deleted) the cached information is still returned. That cached information is retained for ever it seems so my supposedly deleted user accounts still appear to be active on the machines. And it also seems you can't actually turn off caching - even though there are options in sssd.conf to do so. It looks like the "cache_credentials = False" option still caches things, but just acts like the entries are always invalid. I can of course do stop sssd delete the contents of /var/lib/sss/db start sssd and that's what I do when things become an issue. But surely there is a better way of SSSD actually realising that a user has been deleted from LDAP? Pete

4 5

Centos 7.5..and My GDM Greeter/GDM Don't Work Anymore
by Paul E. Virgo 07 Aug '18

07 Aug '18

So, we've updated to 7.5, and for two machines--A Dell Precision M4800, and a Dell Precision 7510..both running Radeon cards--we no longer get the GDM Greeter login box NOR can we switch to virtual text login terminals. It's been driving me nuts. The systems do allow for SSH logins, so that's how we get to them, but I've checked the Xorg.0.log and nothing stands out. Did a systemctl status gdm.service and got this: > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-shell[2023]: g_array_unref: > assertion 'array' failed > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-shell[2023]: g_array_unref: > assertion 'array' failed > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-shell[2023]: g_array_unref: > assertion 'array' failed > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-shell[2023]: g_array_unref: > assertion 'array' failed > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-shell[2023]: g_array_unref: > assertion 'array' failed > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-session-binary[1926]: > WARNING: Could not get session path for session. Check that logind is > properly installed and pam_systemd is getting used at login. > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-shell[2023]: g_array_unref: > assertion 'array' failed > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-session[1926]: > gnome-session-binary[1926]: WARNING: Could not get session path for > session. Check that logind is properly installed and pam_systemd > is...ed at login. > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-shell[2023]: g_array_unref: > assertion 'array' failed > Aug 07 16:23:32 gs6102dsclxpvirgo3 gnome-shell[2023]: JS ERROR: > Exception in callback for signal: reset: Gio.DBusError: > GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: No session available > LoginDialog<._resetGreeterProxy@resource:///org/gnome/shell/gdm/loginDialog.js:837:29 > wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22... Did the upgrade break something? Possibly. Any and all hints/ideas/etc. greatly welcomed. PEV -- Paul E Virgo Sr. System Administrator Code 610.2 SESDA III - DAAC/DISC Goddard Space Flight Ctr/NASA Greenbelt, MD Greenbelt, MD 20771 (301) 614-5751

1 0

Back to Xfce
by Robert Moskowitz 06 Aug '18

06 Aug '18

Now that the basic server is up and running. With Gnome via VNC (yuck), it is time to go back and figure out howto install Xfce without an Xfce group script. So I am asking those with X64 Centos for some pointers. Like where are the group scripts so maybe I can modify them for armhfp. I was reading: https://www.rootusers.com/how-to-install-xfce-gui-in-centos-7-linux/ Where the author talks about doing a minimal install then running: yum groupinstall "Server with GUI" But notes that this installs Gnome (which I don't want) and that instead to yum groupinstall “X Window System” But has concerns if this installs all needed followed up with yum groupinstall "Xfce" Thing is on armhfp, I do not have “X Window System” or "Xfce" I have come to understand that groups are scripts that install all the need rpms for the group. But I have not found where these scripts are so hopefully I can see them, figure out how to modify them for the armhfp rpms, and run them. So I am looking for pointers on where these are in tehx64 repos, and how to work with these scripts. thank you for your help..

3 8

rsync versioning problem
by Robert Moskowitz 06 Aug '18

06 Aug '18

I seem to have an rsync versioning problem. The sender is an old ClearOS6 server with rsynv 3.0.6 The receiver is a brand new Centos7-armv7 server with rsync 3.1.2 I am running rsync over ssh Got the error: rsync error: error in rsync protocol data stream (code 12) at io.c(600) [sender=3.0.6] And researching this it comes down to a versioning issue. But all I have found was to upgrade the 3.0.6 system! That will happen when I migrate to ClearOS7! Is there some option to specify to get this to work? rsync -ah --stats --delete -e "ssh" /var/flexshare/shares x.htt-consult.com:/media/backup/homebase/var/flexshare/shares/

2 6

Installing GCC 5.3.0 in CentOS 6 in Docker.
by Mohan Ganesalingam 06 Aug '18

06 Aug '18

I need to compile some C++ 11 with GCC 5.3.0 on CentOS 6. All of this is happening inside docker in CI using the centos:6 base image. (NB. It can't be GCC 6 or 7, because I have to send binaries to clients who won't install newer vs of libstdc++.so.) Until recently, I was installing devtoolset-4-gcc-c++ via yum, and then using RUN scl enable devtoolset-4 gcc to build the code. Unfortunately, devtoolset-4 is no longer supported, so this has stopped working. I've been trying to compile GCC from scratch, but it's been running for hours and hours – even if I get it working, I'll have to replicate the whole process inside Docker and I suspect it will be very brittle. Is there any easy way of downloading a precompiled version? E.g. -- Is there something that I can do to go back to the old v. of Software Collections? Or -- Is there somewhere I might find a precompiled gcc 5 package? Thanks very much, Mohan

1 0

Lenovo Ideapad 320 touchpad not recognized
by Frank Cox 04 Aug '18

04 Aug '18

I'm setting up a new Lenovo Ideapad 320 and everything shows up and works fine except for the touchpad. I did have to get into the bios and set Legacy for boot device and boot mode to get Centos 7 to finish installing. The default bios settings would load the Centos 7 Gnome Live image from a usb flash drive and work (except for the touchpad) but when I tried to install to the hard drive it would get to the end of the process and kernel panic when it was writing the bootloader. Setting Legacy Boot in the bios solved that problem. I have run yum update so everything is up to date. But the touchpad doesn't show up at all. [frankcox@localhost ~]$ cat list.txt ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ - Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ - Logitech USB Receiver id=8 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] - Virtual core XTEST keyboard id=5 [slave keyboard (3)] - Video Bus id=6 [slave keyboard (3)] - Power Button id=7 [slave keyboard (3)] - EasyCamera id=9 [slave keyboard (3)] - AT Translated Set 2 keyboard id=10 [slave keyboard (3)] - Ideapad extra buttons id=11 [slave keyboard (3)] The Logitech USB Receiver listed here is the wireless mouse that I'm using on it right now since the touchpad doesn't work. I've been reading everything I can find about this problem, tried a few different grub parameters that didn't help, and the most advanced solution that I've tried was this: https://superuser.com/questions/1156057/touchpad-not-working-on-centos-7-2 1. Add i8042.nopnp to grub command line in /etc/default/grub: # change this: GRUB_CMDLINE_LINUX_DEFAULT="... quiet splash" # to: GRUB_CMDLINE_LINUX_DEFAULT="... quiet splash i8042.nopnp" 2. Update your grub config (as root): # If you're using UEFI boot grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg # or legacy grub2-mkconfig -o /boot/grub2/grub.cfg 3. Blacklist module i2c_hid (as root): echo "blacklist i2c_hid" > /etc/modprobe.d/i2c-hid.conf 4. Regenerate your initramfs (as root): cp -v /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak dracut -f 5. Reboot! Unfortunately, that didn't change anything; xinput --list still doesn't show the touchpad. I have found references to some deb packages and fedora rpms that don't appear to exist for Centos 7: xorg-x11-drv-synaptics-legacy.x86_64 elantech-0608-dkms_0.2_all.deb I've pretty much run out of ideas. I checked the bios and don't see anything that appears to be related to the touchpad (not that I was really expecting to). -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

1 0

How to set macaddr with nmcli
by Robert Moskowitz 03 Aug '18

03 Aug '18

I see my problem. I mis-read what nmcli con mod eth0 mac "02:67:15:00:81:0B" does. It sets HWADDR; which interface to link to, not MACADDR, what MAC address you want for your interface. So I have read the nmcli pages and googled a bit. I cannot find a way to set MACADDR. I suppose I can set HWADDR then use sed to change it to MACADDR, but this seems a real hack. ARM boards do not have assigned MAC addresses. Uboot uses various information to generate a local MAC address. I want finer control of my MAC address for my servers. In the past, I just edited ifcfg-eth0. I am trying now to do it all with nmcli. I thought I had it, but I misread the manual. Any pointers? thanks BTW, I remember setting MAC addresses on 3COM 3C501C boards because the old board died and we had software licensed to specific MAC addresses. So you had to specify your MAC address in the config file. The DEC admin had to do a similar thing if he had to swap out his LAN card (related: read up on why Dr. Comer set ARP timeout to 10min). Then there was that counterfeit 3C503C from Malaysia, all with the same MAC address. Caused havoc on the networks. EVERYONE had to specify their MAC address with those. 3COM did find the plant making these clones and shut them down. But the damage was done to a lot of us.

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss