Discuss

discuss@lists.centos.org

5 participants
34752 discussions

Setting GDM resolution without knowing the monitor specs
by Warren Young 01 Mar '19

01 Mar '19

We had a complaint recently from a customer that received a server we shipped out that their monitor just showed a black screen. It turns out that they’d hooked it up to an ancient POS with 800x600 as its best resolution, and gdm in CentOS 7 apparently assumes at least 1024x768. It was apparently a major hassle for them to hunt down a reasonable monitor for us. Since we almost never use the GUI on these things, we thought we’d solve that problem going forward by shipping these boxes out to use a fixed 800x600, so they’ll work on any monitor the user plugs in. The first problem you run into is that the Settings > Devices > Display GUI only affects the login you do it under. GDM doesn’t pay attention to this, not even to the configuration set as root! Then you go web searching and find solutions involving xrandr and advice to just put it in /etc/gdm/Init/Default, but that doesn’t seem to work. I then got soooo close when I found the advice to set the monitor configuration in the GUI, then copy ~/.config/monitors.xml to /var/lib/gdm/.config. That works…until you plug in a different monitor, because that file has a hard tie to the monitor brand, model and *serial number*! The monitors.xml file looks like this: <monitors version="2"> <configuration> <migrated/> <logicalmonitor> <x>0</x> <y>0</y> <primary>yes</primary> <monitor> <monitorspec> <connector>VGA-1</connector> <vendor>SAM</vendor> <product>SyncMaster</product> <serial>H1AK500000</serial> </monitorspec> <mode> <width>800</width> <height>600</height> <rate>60</rate> </mode> </monitor> </logicalmonitor> </configuration> </monitors> I have tried: 1. Removing the <monitorspec> section entirely. gdm then gives me a black screen on “systemctl restart gdm” from a text console. 2. Filling out all fields except <connector> with values like “default”, “generic”, “any”, “*”, etc. GDM decides you couldn’t possibly mean for this configuration to apply to that monitor, since it differs, so it ignores you and does whatever it likes instead. 3. Lots and lots of web searching for documentation on the file format to see if I can find out if there is a different way of specifying “any monitor, I don’t care”. I was about to go reading the source code, but I thought I’d ask here first. Keep in mind that we ship these systems out without knowing what monitor they’ll plug in, and once the systems are out in the field, it’s often difficult to get remote access to them. That means we can’t just log in with SSH, probe it with xrandr, and fix it remotely; we’re probably having the customer log in via the GUI to fix the problem that prevents us from SSHing in in the first place! It’s fine in our case to pin the configuration to “VGA-1”, because we know what connectors are on the server itself. We just don’t know what the customer will plug into it. I assume there’s a minimum screen resolution for CentOS 7, probably 1024x768, but we’re installing these systems with a reasonable screen. We only need this low resolution post-install, and then only so the customer can pull up a terminal and maybe run the Network settings tool. For that, 800x600 is fine. You do have to drag the Settings app around a bit to see everything, but it works. Our current fallback is Ctrl-Alt-F2 and nano, which is tolerable for some things — “Okay, type ‘ifconfig’…now find the line that has ‘inet’ in it, and read that back to me…’ — but remotely talking someone through changing ifcfg-noisenoise via nano is a minor nightmare, especially now that Confusing Network Device Naming is the default.

5 11

CentOS-announce Digest, Vol 169, Issue 1
by centos-announce-request＠centos.org 01 Mar '19

01 Mar '19

1 0

Performing post-installation setup tasks - for 75 minutes
by Gary Stainburn 01 Mar '19

01 Mar '19

I'm doing a new install, and everything seems to have gone fine apart from the incredible amount of time it's taken. It does have 6 x 4TB drives in RAID6 and I am installing from a USB DVD drive as I had no SATA ports left, but this is getting rediculous. I chose a simple install (the one above file and print server) and added Postgresql but that was about it. It took over 5 hours to do the install and at 16:50 it changed to Performing post-installation setup tasks. That was 85 minutes ago. The HDD light keeps flashing, but other than that (and the circle swirling) there doesn't seem to be any activity. Is this normal and can I check to see if it is actually doing something?

4 6

CentOS-announce Digest, Vol 168, Issue 6
by centos-announce-request＠centos.org 27 Feb '19

27 Feb '19

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CEBA-2019:0412 CentOS 6 unbound BugFix Update (Johnny Hughes) 2. CEBA-2019:0413 CentOS 6 binutils BugFix Update (Johnny Hughes) 3. CEBA-2019:0414 CentOS 6 sos BugFix Update (Johnny Hughes) 4. CESA-2019:0416 Moderate CentOS 6 java-1.8.0-openjdk Security Update (Johnny Hughes) 5. CESA-2019:0415 Important CentOS 6 kernel Security Update (Johnny Hughes) 6. CESA-2019:0420 Important CentOS 6 polkit Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 26 Feb 2019 18:06:03 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2019:0412 CentOS 6 unbound BugFix Update Message-ID: <20190226180603.GA5030(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2019:0412 Upstream details at : https://access.redhat.com/errata/RHBA-2019:0412 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 25abb1bca48f050f3b83404860f6f104f6b5385ce36bcd543af505178429a754 unbound-1.4.20-26.el6_10.1.i686.rpm e29e6025d9e17e771fcbbfe57503eed1fb57a63a6592edced0a56d8f7e73d99f unbound-devel-1.4.20-26.el6_10.1.i686.rpm 1b74dbd489e6264f2370aa165937d1c7efd030eed777ebd1b1c141f139170a76 unbound-libs-1.4.20-26.el6_10.1.i686.rpm 54e595a60edc0a827e2f3296a99f3c5dee304d3ef68d8656d2a6baef6092579a unbound-python-1.4.20-26.el6_10.1.i686.rpm x86_64: a71e9763d4fa50c7de4e24d525059e4c139fa941b1bcfc457187a7213b7a84d5 unbound-1.4.20-26.el6_10.1.x86_64.rpm e29e6025d9e17e771fcbbfe57503eed1fb57a63a6592edced0a56d8f7e73d99f unbound-devel-1.4.20-26.el6_10.1.i686.rpm 292d0074c4ade9040169c7a78768ad24bc6f3ed27bfb19f54a4710c0fff03dd7 unbound-devel-1.4.20-26.el6_10.1.x86_64.rpm 1b74dbd489e6264f2370aa165937d1c7efd030eed777ebd1b1c141f139170a76 unbound-libs-1.4.20-26.el6_10.1.i686.rpm d575aa8890a443896ea9317b1e28f2d288a8cca60ddbed22e186fecdc2385057 unbound-libs-1.4.20-26.el6_10.1.x86_64.rpm 54e595a60edc0a827e2f3296a99f3c5dee304d3ef68d8656d2a6baef6092579a unbound-python-1.4.20-26.el6_10.1.i686.rpm 72a797b73fdc1a86e2409258afd11a8bf9a2dfc922b90a62ff294386c90f9f50 unbound-python-1.4.20-26.el6_10.1.x86_64.rpm Source: bc0eae8f0e4bf3594382485a04ab0470e950f133446011978a91903e9ffa2150 unbound-1.4.20-26.el6_10.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Tue, 26 Feb 2019 18:09:32 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2019:0413 CentOS 6 binutils BugFix Update Message-ID: <20190226180932.GA5239(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2019:0413 Upstream details at : https://access.redhat.com/errata/RHBA-2019:0413 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: afa661d760a4ac97a7959ca7949a626b96f4a406b3bbfedc60eba4d767c635cf binutils-2.20.51.0.2-5.48.el6_10.1.i686.rpm f8d8d58e471267f6247ee3bd3a54fd742a78af3dba468fa131c13b2f0e4a7ada binutils-devel-2.20.51.0.2-5.48.el6_10.1.i686.rpm x86_64: fcffe62534bf900ab84700da19b51f98ab5bc0227f5f3b862df16d4d8d8d1b2d binutils-2.20.51.0.2-5.48.el6_10.1.x86_64.rpm f8d8d58e471267f6247ee3bd3a54fd742a78af3dba468fa131c13b2f0e4a7ada binutils-devel-2.20.51.0.2-5.48.el6_10.1.i686.rpm 1e6aad2dbc7a54ee34792b13980842ad833cd92000129334bf462b3593b3e1ad binutils-devel-2.20.51.0.2-5.48.el6_10.1.x86_64.rpm Source: e0ad428636abc38068b7fc3d8f2dc82e4b6fbabd1933d258e27b1da4f2ac5085 binutils-2.20.51.0.2-5.48.el6_10.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Tue, 26 Feb 2019 18:09:44 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2019:0414 CentOS 6 sos BugFix Update Message-ID: <20190226180944.GA5373(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2019:0414 Upstream details at : https://access.redhat.com/errata/RHBA-2019:0414 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 1848905af31854cbc95f65fcb1513089fcc7ed55351878594f40e16e2bd41617 sos-3.2-63.el6.centos.3.noarch.rpm x86_64: 1848905af31854cbc95f65fcb1513089fcc7ed55351878594f40e16e2bd41617 sos-3.2-63.el6.centos.3.noarch.rpm Source: fd0212eb15901efb1dc961708305457b9b8faf50ff34d79ab44b51387afa27a5 sos-3.2-63.el6.centos.3.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Tue, 26 Feb 2019 18:10:55 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:0416 Moderate CentOS 6 java-1.8.0-openjdk Security Update Message-ID: <20190226181054.GA5713(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:0416 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2019:0416 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 9a5c6248ec8c2d24d502d29906edda94c7cf1f13f3a13ca7eaac99f29b45b212 java-1.8.0-openjdk-1.8.0.201.b09-1.el6_10.i686.rpm 3162bbbd55c494b9137ae575b8442dbb0b44007fbb5d47e52da547aa24b4d5e3 java-1.8.0-openjdk-debug-1.8.0.201.b09-1.el6_10.i686.rpm e07a828253b45576ebb920a0b14ef307501f1351d792ccb235609aeb87470b02 java-1.8.0-openjdk-demo-1.8.0.201.b09-1.el6_10.i686.rpm 93ea1dcb90c2c53988a1bc76e18d7dcbfca57f790ea182d0ac147da4aa67560d java-1.8.0-openjdk-demo-debug-1.8.0.201.b09-1.el6_10.i686.rpm d291487e190c345e22918a6a9a84b0a262d607521cb71a4655ae6f20ea214c5f java-1.8.0-openjdk-devel-1.8.0.201.b09-1.el6_10.i686.rpm 05fc3390147d7fc7caf2f7998e667b5fa04fa886d778ecc192f0c95f71895267 java-1.8.0-openjdk-devel-debug-1.8.0.201.b09-1.el6_10.i686.rpm 95d8305328fb282adcac162ca8e0d26f1acc9a123fb0da0a02732f22d9d8a31b java-1.8.0-openjdk-headless-1.8.0.201.b09-1.el6_10.i686.rpm c156e41e34f8fb42d134989f3f8581ac01576acded90c074e2e0336b3685ab46 java-1.8.0-openjdk-headless-debug-1.8.0.201.b09-1.el6_10.i686.rpm 2f944432293be44bf3a434d85b5774d79823cde1c0fd32e4eb2f6b5551960041 java-1.8.0-openjdk-javadoc-1.8.0.201.b09-1.el6_10.noarch.rpm 0133f75781615bbdd57bf5c494daa34a678d1ac1bb84e2a3ddfeb1a8108c7e3b java-1.8.0-openjdk-javadoc-debug-1.8.0.201.b09-1.el6_10.noarch.rpm 22c2333ab44d8f66a3a103b37d0c0fa2fd86e511149d4be73dc49b1905b19902 java-1.8.0-openjdk-src-1.8.0.201.b09-1.el6_10.i686.rpm a032d80ce2d876a0eadc171a2b341e50cdb08c60d5fa38c07cae18a97cd4039d java-1.8.0-openjdk-src-debug-1.8.0.201.b09-1.el6_10.i686.rpm x86_64: cd75f219a8ec0f89656445a191740bc5104e7c2a751cd48db1ea339d21443182 java-1.8.0-openjdk-1.8.0.201.b09-1.el6_10.x86_64.rpm 03b3d60ce144c11a1d786427158cb599b9ba9cc80f992af83f44d507248c16df java-1.8.0-openjdk-debug-1.8.0.201.b09-1.el6_10.x86_64.rpm ea2cf54aeed2d8b4acd3b2e81852380cea9b99a823ba737d575fe8aeaa9d7d58 java-1.8.0-openjdk-demo-1.8.0.201.b09-1.el6_10.x86_64.rpm 2568fb7a798ab0f4bb7ed2168e693dbdded247832d3fdb1766d4ffb1088ea751 java-1.8.0-openjdk-demo-debug-1.8.0.201.b09-1.el6_10.x86_64.rpm 5069d9f24f9a94af8029fa40e705851ac98fedee5bbed42d1e248672a18d4eb9 java-1.8.0-openjdk-devel-1.8.0.201.b09-1.el6_10.x86_64.rpm f0ea67a65a096c2bea4615579bef63745793051a79057e06be84cbc81acd6064 java-1.8.0-openjdk-devel-debug-1.8.0.201.b09-1.el6_10.x86_64.rpm 234239956d70d66bae388baec9ef9b84c651b431c487df76d9a07cf7439ab9ec java-1.8.0-openjdk-headless-1.8.0.201.b09-1.el6_10.x86_64.rpm 3b9d8b29c2af67debbd33c7d8e167a6fc165302567024d4aca26c0b7f5fc433e java-1.8.0-openjdk-headless-debug-1.8.0.201.b09-1.el6_10.x86_64.rpm 2f944432293be44bf3a434d85b5774d79823cde1c0fd32e4eb2f6b5551960041 java-1.8.0-openjdk-javadoc-1.8.0.201.b09-1.el6_10.noarch.rpm 0133f75781615bbdd57bf5c494daa34a678d1ac1bb84e2a3ddfeb1a8108c7e3b java-1.8.0-openjdk-javadoc-debug-1.8.0.201.b09-1.el6_10.noarch.rpm c7ffa8544d3a7d7fb1c274eb615b1324b72da5f8020b0cf259c1d40635f084d9 java-1.8.0-openjdk-src-1.8.0.201.b09-1.el6_10.x86_64.rpm caf7e8d93759e980efb4fccb3ddf796298d64d5c80371b8c31aa2c5d7a20a0a7 java-1.8.0-openjdk-src-debug-1.8.0.201.b09-1.el6_10.x86_64.rpm Source: 3506b54b993c106636e1f050e6f31234912662efbeb265581c30328f8d96df59 java-1.8.0-openjdk-1.8.0.201.b09-1.el6_10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 5 Date: Tue, 26 Feb 2019 18:11:53 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:0415 Important CentOS 6 kernel Security Update Message-ID: <20190226181153.GA5996(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:0415 Important Upstream details at : https://access.redhat.com/errata/RHSA-2019:0415 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: fb1f9cac888b731536cfe9b39b98bb28434ffd2baa9f5dfa3d2dcfaba5006147 kernel-2.6.32-754.11.1.el6.i686.rpm 32670dd2d7ee24ea3abe21ae02973e5d21496cce1c702506dbefe4fa58be2336 kernel-abi-whitelists-2.6.32-754.11.1.el6.noarch.rpm 382d6f2284f7e522c17d840440f16fe906dae1397ecf7d34e215387189340154 kernel-debug-2.6.32-754.11.1.el6.i686.rpm 91386e06f79ba911da59dbda4454eb7802602aa6140f9309cee50f0a6c50184b kernel-debug-devel-2.6.32-754.11.1.el6.i686.rpm 69f65648a4104132c72f3fae917d824ae250fb513b319c17a345c1586cd9858d kernel-devel-2.6.32-754.11.1.el6.i686.rpm df694bb232274ff0db728718550104246fdfda65fbb19251675264f6538c6c74 kernel-doc-2.6.32-754.11.1.el6.noarch.rpm a827e78f40c43d43d8063f97edc540a13e058d6215abedd3bd0c2a9d3b134e08 kernel-firmware-2.6.32-754.11.1.el6.noarch.rpm 36f5eec7cb6795c2bb1c33e5aba518d61ce0a8e2ba5123a784ac354612612e0f kernel-headers-2.6.32-754.11.1.el6.i686.rpm d2736041398601ba5c299b16cf1bf7919d3de249a6288248f841a70850069aab perf-2.6.32-754.11.1.el6.i686.rpm 4a32381065be5d771329e0b039b8bc46bc9038b317db2221efc63b6159da09b8 python-perf-2.6.32-754.11.1.el6.i686.rpm x86_64: 32481d32a7aff15635edcb556b51c3d081a631f142e254cbee589dacd3c0fc29 kernel-2.6.32-754.11.1.el6.x86_64.rpm 32670dd2d7ee24ea3abe21ae02973e5d21496cce1c702506dbefe4fa58be2336 kernel-abi-whitelists-2.6.32-754.11.1.el6.noarch.rpm 8d1548af08530ed99e550ad39bb5fdfae04971061cca9fed4185539b501cb9ed kernel-debug-2.6.32-754.11.1.el6.x86_64.rpm 91386e06f79ba911da59dbda4454eb7802602aa6140f9309cee50f0a6c50184b kernel-debug-devel-2.6.32-754.11.1.el6.i686.rpm 7745d7eea5bbf348d4fa1167c62f5cccd1ac0d4de62fc783c672d24b5e0749ae kernel-debug-devel-2.6.32-754.11.1.el6.x86_64.rpm 3ee8e75367dbfde010163fb33633829b7622fcef96ace23997e65bef19d92faf kernel-devel-2.6.32-754.11.1.el6.x86_64.rpm df694bb232274ff0db728718550104246fdfda65fbb19251675264f6538c6c74 kernel-doc-2.6.32-754.11.1.el6.noarch.rpm a827e78f40c43d43d8063f97edc540a13e058d6215abedd3bd0c2a9d3b134e08 kernel-firmware-2.6.32-754.11.1.el6.noarch.rpm 321e1d56bd3a956ca016f4e5c773fe8c6ace618b40291520a5d58450726e5fef kernel-headers-2.6.32-754.11.1.el6.x86_64.rpm 9f564c205cf0af4a3e7b047a9d7ff9644fa1098851dfe1dafa3428763da01a17 perf-2.6.32-754.11.1.el6.x86_64.rpm 32eae3bafda6fc72841ec3a3384e27f1012e68cabd931c37259c7296d57cd1a2 python-perf-2.6.32-754.11.1.el6.x86_64.rpm Source: ac0d88f133a1846dea569044bdeaed8cd29f2326df5e5e67dac66ac57d49be13 kernel-2.6.32-754.11.1.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 6 Date: Tue, 26 Feb 2019 20:22:22 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2019:0420 Important CentOS 6 polkit Security Update Message-ID: <20190226202222.GA9535(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2019:0420 Important Upstream details at : https://access.redhat.com/errata/RHSA-2019:0420 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 9c7ffb83260b20f047405646b42d5f84f45a8971a6dab2fdfb48bcb782552e49 polkit-0.96-11.el6_10.1.i686.rpm b71aa41dd3114244ae3bf12e665158522203d82d4705148931a4981c87b406d1 polkit-desktop-policy-0.96-11.el6_10.1.noarch.rpm 9b710b4ea155f2b4a7225a93a9c6bb0d0a4e42b172dc9e0e4d0f9c36460f36e4 polkit-devel-0.96-11.el6_10.1.i686.rpm 5b55e623669bdb12a1d516d1d5e073e084fb5ade8a0b461219dfa013231811da polkit-docs-0.96-11.el6_10.1.i686.rpm x86_64: 9c7ffb83260b20f047405646b42d5f84f45a8971a6dab2fdfb48bcb782552e49 polkit-0.96-11.el6_10.1.i686.rpm e8f98075594018cd33fcbd6b2ab926486b9524b10f8170f0011c9c4fdd598d5c polkit-0.96-11.el6_10.1.x86_64.rpm b71aa41dd3114244ae3bf12e665158522203d82d4705148931a4981c87b406d1 polkit-desktop-policy-0.96-11.el6_10.1.noarch.rpm 9b710b4ea155f2b4a7225a93a9c6bb0d0a4e42b172dc9e0e4d0f9c36460f36e4 polkit-devel-0.96-11.el6_10.1.i686.rpm d713d91610f9e4508ef648c69f6aee7bd673ac400d9530f3dcfd44a1314f71db polkit-devel-0.96-11.el6_10.1.x86_64.rpm 6bdeb9a0a1324b6dafbeecbef4fae23ee5a762d00d2c31bbb5ff9dccad3b9c3a polkit-docs-0.96-11.el6_10.1.x86_64.rpm Source: 736c0b5e52f5ea48aa75ae28a18a0451e8c525b88e32028d3dca76d550421ade polkit-0.96-11.el6_10.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 168, Issue 6 ***********************************************

1 0

how to use 2 Nvidia Cards in one system
by Ralf Prengel 27 Feb '19

27 Feb '19

Hallo, is there a way to use 2 different Nvidia Graphiccards in one system? The first one is working fine with 3 displays but I want to use 2 more displays with the second card. Do I need two card of the same series (4 or 7) or is there a way to mix different series? Thanks for hints. Ralf [root@pcprengellx ~]# lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07) 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31) 00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31) 00:16.3 Serial controller: Intel Corporation 100 Series/C230 Series Chipset Family KT Redirection (rev 31) 00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] (rev 31) 00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Q170 Chipset LPC/eSPI Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31) 00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31) 00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-LM (rev 31) 01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 745] (rev a2) 01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 405] (rev a2) 02:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1)

1 0

Problem with mdadm, raid1 and automatically adds any disk to raid
by Jobst Schmalenbach 27 Feb '19

27 Feb '19

Hi. CENTOS 7.6.1810, fresh install - use this as a base to create/upgrade new/old machines. I was trying to setup two disks as a RAID1 array, using these lines mdadm --create --verbose /dev/md0 --level=0 --raid-devices=2 /dev/sdb1 /dev/sdc1 mdadm --create --verbose /dev/md1 --level=0 --raid-devices=2 /dev/sdb2 /dev/sdc2 mdadm --create --verbose /dev/md2 --level=0 --raid-devices=2 /dev/sdb3 /dev/sdc3 then I did a lsblk and realized that I used --level=0 instead of --level=1 (spelling mistake) The SIZE was reported double as I created a striped set by mistake, yet I wanted the mirrored. Here starts my problem, I cannot get rid of the /dev/mdX no matter what I do (try to do). I tried to delete the MDX, I removed the disks by failing them, then removing each array md0, md1 and md2. I also did dd if=/dev/zero of=/dev/sdX bs=512 seek=$(($(blockdev --getsz /dev/sdX)-1024)) count=1024 dd if=/dev/zero of=/dev/sdX bs=512 count=1024 mdadm --zero-superblock /dev/sdX Then I wiped each partition of the drives using fdisk. Now every time I start fdisk to setup a new set of partitions I see in /var/log/messages as soon as I hit "W" in fdisk: Feb 25 15:38:32 webber systemd: Started Timer to wait for more drives before activating degraded array md2.. Feb 25 15:38:32 webber systemd: Started Timer to wait for more drives before activating degraded array md1.. Feb 25 15:38:32 webber systemd: Started Timer to wait for more drives before activating degraded array md0.. Feb 25 15:38:32 webber kernel: md/raid1:md0: active with 1 out of 2 mirrors Feb 25 15:38:32 webber kernel: md0: detected capacity change from 0 to 5363466240 Feb 25 15:39:02 webber systemd: Created slice system-mdadm\x2dlast\x2dresort.slice. Feb 25 15:39:02 webber systemd: Starting Activate md array md1 even though degraded... Feb 25 15:39:02 webber systemd: Starting Activate md array md2 even though degraded... Feb 25 15:39:02 webber kernel: md/raid1:md1: active with 0 out of 2 mirrors Feb 25 15:39:02 webber kernel: md1: failed to create bitmap (-5) Feb 25 15:39:02 webber mdadm: mdadm: failed to start array /dev/md/1: Input/output error Feb 25 15:39:02 webber systemd: mdadm-last-resort(a)md1.service: main process exited, code=exited, status=1/FAILURE I check /proc/mdstat and sure enough, there it is trying to assemble an Array I DID NOT TOLD IT TO DO. I do NOT WANT this to happen, it creates the same "SHIT" (the incorrect array) over and over again (systemd frustration). So I tried to delete them again, wiped them again, killed processes, wiped disks. No matter what I do as soon as I hit the "w" in fdisk systemd tries to assemble the array again without letting me to decide what to do. Help! Jobst -- windoze 98: <n.> useless extension to a minor patch release for 32-bit extensions and a graphical shell for a 16-bit patch to an 8-bit operating system originally coded for a 4-bit microprocessor, written by a 2-bit company that can't stand for 1 bit of competition! | |0| | Jobst Schmalenbach, General Manager | | |0| Barrett & Sales Essentials |0|0|0| +61 3 9533 0000, POBox 277, Caulfield South, 3162, Australia

5 11

hplips
by mark 26 Feb '19

26 Feb '19

Yeah, about that... Back in '12, we got a nice HP poster printer. They don't support Linux, but a co-worker got the .ppd out of the Mac support file. I tried it, then I looked at the file in vi... and found it *only* supported the 24" printer, *not* the 44" printer that we had. Well, we just bought a replacement, since the old printer was EOL'd. This time, I went to hplips, d/l and built the current one, and sure enough, there's a .ppd for the DesignJet Z9. Any bets on what I found? No? There was *NO* support for the 44" printer. I saw *one* setting for something 30x42 (the 100' roll of paper is 42" wide). I joined and tried asking about that on the hplips site. That was last week. Not a single response. HP no longer does software support for their printers (I got that from the engineer - we do have contract support). Had a friend d/l and install the Mac ps driver... no .ppd. Anyone know someone who's involved with hplips? Otherwise, I'm going to have to spend half a day or a day hacking the damn .ppd. Btw, the server it's attached to is C6. One of these days I'll upgrade it to C7, but the *only* think it's used for now are these poster printers. mark

2 1

Policy issue: C7 and motion
by mark 25 Feb '19

25 Feb '19

Not sure who's package let an error slip in, but I don't believe I've had this issue before: SELinux is preventing /usr/bin/motion from map access on the chr_file /dev/video1 Yes, that should be allowed by default. mark

1 0

Geany 1.34
by H 25 Feb '19

25 Feb '19

Does anyone know if Geany 1.34 is headed to one of the repositories? I am running version 1.31 and interested in the 1.33+ since the markdown plugin has apparently been updated.

4 9

Nvme m.2 disk problem
by Alessandro Baggi 24 Feb '19

24 Feb '19

Hi list, I'm running Centos 7.6 on an Corsair Force MP500 120 GB. Root fs is ext4 and this drive is ~1 year old. System works very well except on boot. During boot process I got always a file system check on nvme drive. Running smartctl on this drive I got this: === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02, NSID 0x1) Critical Warning: 0x00 Temperature: 41 Celsius Available Spare: 100% Available Spare Threshold: 1% Percentage Used: 1% Data Units Read: 5,355,595 [2,74 TB] Data Units Written: 5,826,517 [2,98 TB] Host Read Commands: 67,978,550 Host Write Commands: 75,422,898 Controller Busy Time: 32,863 Power Cycles: 811 Power On Hours: 2,813 Unsafe Shutdowns: 317 Media and Data Integrity Errors: 0 Error Information Log Entries: 177 Warning Comp. Temperature Time: 0 Critical Comp. Temperature Time: 0 Temperature Sensor 2: 77 Celsius Error Information (NVMe Log 0x01, max 64 entries) Num ErrCount SQId CmdId Status PELoc LBA NSID VS 0 177 0 0x0014 0x4004 - 8796109799680 1 - 1 176 0 0x0019 0x4004 - 8796109799680 1 - 2 175 0 0x001a 0x4004 - 8796109799680 1 - 3 174 0 0x0005 0x4004 - 8796109799680 1 - 4 173 0 0x000c 0x4004 - 8796109799680 1 - 5 172 0 0x0019 0x4004 - 8796109799680 1 - 6 171 0 0x001d 0x4004 - 8796109799680 1 - 7 170 0 0x0014 0x4004 - 8796109799680 1 - 8 169 0 0x0011 0x4004 - 8796109799680 1 - 9 168 0 0x000f 0x4004 - 8796109799680 1 - 10 167 0 0x0000 0x4004 - 8796109799680 1 - 11 166 0 0x0006 0x4004 - 8796109799680 1 - 12 165 0 0x0008 0x4004 - 8796109799680 1 - 13 164 0 0x000e 0x4004 - 8796109799680 1 - 14 163 0 0x0008 0x4004 - 8796109799680 1 - 15 162 0 0x0006 0x4004 - 8796109799680 1 - ... (48 entries not shown) I noticed that Unsafe shutdowns increased rapidly and I don't know why there is an unsafe shutdown. Every 3/4 boot this value is increased by 1 and I don't know why. I can't find any errors on system logs. Can someone point me in the right direction? Thanks in advance. Alessandro.

1 0

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