Discuss October 2016

discuss@lists.centos.org

118 participants
100 discussions

VM disk question
by Jerry Geis 21 Oct '16

21 Oct '16

I have VMPlayer 12 running a CentOS 7 disk. Works fine. However I wish to change the disk from UUID booting (fstab) to the old style LABEL. (so I can export it and use on another machine). fdisk -l /dev/sda Disk /dev/sda: 21.5 GB, 21474836480 bytes, 41943040 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk label type: dos Disk identifier: 0x0001c6d3 Device Boot Start End Blocks Id System /dev/sda1 * 2048 20482047 10240000 83 Linux /dev/sda2 20482048 22530047 1024000 82 Linux swap / Solaris /dev/sda3 22530048 41943039 9706496 83 Linux however when I run: e2label /dev/sda1 / e2label: Bad magic number in super-block while trying to open /dev/sda1 Couldn't find valid filesystem superblock. Three questions: 1) Am I doing something wrong? 2) Is there a better way? 3) How do I support VM formats (VBox, VHD and VMWare) easily? Thanks, Jerry

4 3

CentOS-announce Digest, Vol 140, Issue 7
by centos-announce-request＠centos.org 21 Oct '16

21 Oct '16

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. CESA-2016:2079 Critical CentOS 6 java-1.8.0-openjdk Security Update (Johnny Hughes) 2. CESA-2016:2079 Critical CentOS 7 java-1.8.0-openjdk Security Update (Johnny Hughes) 3. CEEA-2016:2053 CentOS 7 qed Enhancement Update (Johnny Hughes) 4. CEEA-2016:2053 CentOS 7 qede Enhancement Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 19 Oct 2016 14:40:38 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:2079 Critical CentOS 6 java-1.8.0-openjdk Security Update Message-ID: <20161019144038.GA1839(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:2079 Critical Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-2079.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 60cf77046bec5d09e30ac37298ae03030f7f12bdf1c85991e895164d43f23df1 java-1.8.0-openjdk-1.8.0.111-0.b15.el6_8.i686.rpm 16bee782dac78dcb28c9b193b93507e7dbcf3e4486fcefb31524c546939a32d8 java-1.8.0-openjdk-debug-1.8.0.111-0.b15.el6_8.i686.rpm 7eef730957fd3bda1f05b693c2d0c8db7b76b79efd55f8dd02a5f748a556ea38 java-1.8.0-openjdk-demo-1.8.0.111-0.b15.el6_8.i686.rpm e523ee91414bf1d2bc968549379ed5236c802b6033d9532f005e703f07d60390 java-1.8.0-openjdk-demo-debug-1.8.0.111-0.b15.el6_8.i686.rpm c2a8ce469379455489ca8244f24f0b746d42b3ecfbb053545daf7a322114ed5f java-1.8.0-openjdk-devel-1.8.0.111-0.b15.el6_8.i686.rpm 03f53cb8d4e9c68801459ee488874072965d2302229f98679ee12c42965f8b59 java-1.8.0-openjdk-devel-debug-1.8.0.111-0.b15.el6_8.i686.rpm 78838b4b92f42d353a1bd2c0b93f1e1680abd8e700cfb6ea87cda478d70a6a0a java-1.8.0-openjdk-headless-1.8.0.111-0.b15.el6_8.i686.rpm a9d5f8ec69fe74b5c2ca61844b708880a12a4c6a9fb02b8e47ab09e036075a3f java-1.8.0-openjdk-headless-debug-1.8.0.111-0.b15.el6_8.i686.rpm 39eb4adf71a189d04374ac6f334a8575e6305bd3f9740b28b4afaa09f0c3dea8 java-1.8.0-openjdk-javadoc-1.8.0.111-0.b15.el6_8.noarch.rpm d95e4b1f0f00548357f68bea0ba618ca57c05c83c6126801e7486f927505ed9d java-1.8.0-openjdk-javadoc-debug-1.8.0.111-0.b15.el6_8.noarch.rpm 75d481665ef258552464259d83abed1b217c156b4b6ff3e5f7dacea0f70643a3 java-1.8.0-openjdk-src-1.8.0.111-0.b15.el6_8.i686.rpm 341c0b2114349353d5ffd7259e203d84639364eadc7dbfac3c5f715ec06baf05 java-1.8.0-openjdk-src-debug-1.8.0.111-0.b15.el6_8.i686.rpm x86_64: f4499b1d6b31f133b89baa832794ff0c37f9ea9e87850172e71e08c1e0c438b6 java-1.8.0-openjdk-1.8.0.111-0.b15.el6_8.x86_64.rpm af76e86cf568bb3274b8ba6c62c48a8a856269264b036350591591575df15772 java-1.8.0-openjdk-debug-1.8.0.111-0.b15.el6_8.x86_64.rpm 1b0945e04fb8ffbadef61357bee914ee494988886eb91b2687601f4f763393e2 java-1.8.0-openjdk-demo-1.8.0.111-0.b15.el6_8.x86_64.rpm d5ec7926cdbb8bbbb3b25403e435082f8cbe14ee88fcb63f4aab01e8c24794cd java-1.8.0-openjdk-demo-debug-1.8.0.111-0.b15.el6_8.x86_64.rpm 33063935b9ff95f54b9d094503eba5f90dcfcc3c8041f3d7bbb9c7e61768ce07 java-1.8.0-openjdk-devel-1.8.0.111-0.b15.el6_8.x86_64.rpm c55e83f7ffff3cdf85dab61c716033b26739ee8c845178cee0aae54423305947 java-1.8.0-openjdk-devel-debug-1.8.0.111-0.b15.el6_8.x86_64.rpm bffd148c22ea1410222cf8542ce5c5ee2288db9510648a0fda8345d2abf9fbe7 java-1.8.0-openjdk-headless-1.8.0.111-0.b15.el6_8.x86_64.rpm 28f12d2c23f0e6f48f40a68f25ca5b8d87399b96139919a32f10a1c709148e16 java-1.8.0-openjdk-headless-debug-1.8.0.111-0.b15.el6_8.x86_64.rpm 39eb4adf71a189d04374ac6f334a8575e6305bd3f9740b28b4afaa09f0c3dea8 java-1.8.0-openjdk-javadoc-1.8.0.111-0.b15.el6_8.noarch.rpm d95e4b1f0f00548357f68bea0ba618ca57c05c83c6126801e7486f927505ed9d java-1.8.0-openjdk-javadoc-debug-1.8.0.111-0.b15.el6_8.noarch.rpm c02bf67c37e94832bcc73b9f5af6eca847ad56e318ffc39a77b2799354130afb java-1.8.0-openjdk-src-1.8.0.111-0.b15.el6_8.x86_64.rpm 393b67b81738b1cd12ca1d1b883759338ea6652264fe34f14afb2b5aa7a7fb5d java-1.8.0-openjdk-src-debug-1.8.0.111-0.b15.el6_8.x86_64.rpm Source: a23a87514ad0c6f825ebd5ff9e2d950521d8de88086d4abfc7a0b6eec29a4e30 java-1.8.0-openjdk-1.8.0.111-0.b15.el6_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Wed, 19 Oct 2016 18:46:08 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:2079 Critical CentOS 7 java-1.8.0-openjdk Security Update Message-ID: <20161019184608.GA10174(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:2079 Critical Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-2079.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 028b7d73cab8947df0f2fe08c028d6349aa7cb6a19ef01ac4ddc78939ab25f61 java-1.8.0-openjdk-1.8.0.111-1.b15.el7_2.x86_64.rpm 83fc734f15cd1891fb0c5fd5e692df9048cd7dc56ec468e7281eb2eaf6654e20 java-1.8.0-openjdk-accessibility-1.8.0.111-1.b15.el7_2.x86_64.rpm 84a58a7dab05f4230d4c30b35e0649de9e0f0acd1ea984428da31ca4d91dab92 java-1.8.0-openjdk-accessibility-debug-1.8.0.111-1.b15.el7_2.x86_64.rpm 02488f4200afbba9b86c6f3cbf6054778afaf24164675fe1a7e3eca113999999 java-1.8.0-openjdk-debug-1.8.0.111-1.b15.el7_2.x86_64.rpm 7c5e7dc04f1286a18c1c5df06fa73dd5640ef9f631c91c2a3cd6c883cb7acf68 java-1.8.0-openjdk-demo-1.8.0.111-1.b15.el7_2.x86_64.rpm 11b2902c6c4d7dfe82b869903c894b05c7b768c337469f36310fc43b5b4611df java-1.8.0-openjdk-demo-debug-1.8.0.111-1.b15.el7_2.x86_64.rpm 03433ad6c3f91643b9744acf870b875d7418593c60c31eb5cfe32f4619112a8f java-1.8.0-openjdk-devel-1.8.0.111-1.b15.el7_2.x86_64.rpm 70c0c17a4dced2896b0f1d4c622615e2e3bfce16042017d0e424496a1386d680 java-1.8.0-openjdk-devel-debug-1.8.0.111-1.b15.el7_2.x86_64.rpm ce6eed8d95c73553e83669594284cfb4d43959761499f1a2d90e040352eb8b1c java-1.8.0-openjdk-headless-1.8.0.111-1.b15.el7_2.x86_64.rpm b9f8e783b3f82a3fe567a6f343a3e7ab5acf3d838fb2bdf6670da3df52bc11bd java-1.8.0-openjdk-headless-debug-1.8.0.111-1.b15.el7_2.x86_64.rpm 5f2d8974a59c970489994bd9f74194122cfccd1d48e3078977e9840cccd4bae4 java-1.8.0-openjdk-javadoc-1.8.0.111-1.b15.el7_2.noarch.rpm 99764694bbfc61c98497d90f482f11b29edeb9a14ed583386e1fcd1f7685a003 java-1.8.0-openjdk-javadoc-debug-1.8.0.111-1.b15.el7_2.noarch.rpm 241163cc6cd5f82476b489dcaa3d02e2e97f71606de63af94178f0538648b9e2 java-1.8.0-openjdk-src-1.8.0.111-1.b15.el7_2.x86_64.rpm 749d9c3495ec107da97f6044016972877c75346e06f358559d8beb1dd0b013ad java-1.8.0-openjdk-src-debug-1.8.0.111-1.b15.el7_2.x86_64.rpm Source: 14dd2d91e721496277c119284a579fe2efd2433e3ee1841053bef94f5fb2f455 java-1.8.0-openjdk-1.8.0.111-1.b15.el7_2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Wed, 19 Oct 2016 18:47:06 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2016:2053 CentOS 7 qed Enhancement Update Message-ID: <20161019184706.GA10243(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2016:2053 Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-2053.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: d377a4d756626c36b06cba43245271483cde612665f7824c2dd4e92ce0a658bd kmod-qed-8.7.1.20-1.el7_2.x86_64.rpm 270416cf1eaa63e45787df70ea96e08b62fa9727617c90c2565db18ae29d06b0 kmod-qed-firmware-8.7.1.20-1.el7_2.x86_64.rpm Source: 9177a9008d81b6e116c7108382229015c9c2794581427d4f712fbab122ea05ad qed-8.7.1.20-1.el7_2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Wed, 19 Oct 2016 18:47:17 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2016:2053 CentOS 7 qede Enhancement Update Message-ID: <20161019184717.GA10299(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2016:2053 Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-2053.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 134fd2c3fe3439169678c5c57518f9231804ee34098e7f169bca57b7179886ae kmod-qede-8.7.1.20-1.el7_2.x86_64.rpm Source: 0f176dc6e202d09ea6e200f17f6ae7f66ea66983c2f5ee5564faf17c99f5782e qede-8.7.1.20-1.el7_2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 140, Issue 7 ***********************************************

2 1

xdgurl
by Mark LaPierre 21 Oct '16

21 Oct '16

Has anyone figured out how to make Firefox 45.4.0 on CentOS 6 use xdgurl to handle xdg:// URLs? Google is full of suggestions that don't work. When I select a an xdg:// link I don't get a dialog asking me what to do like Google says I will. Instead I get a message that says Firefox doesn't have a clue how to handle this URL. Do you want to try again? I tried about:config I added: network.protocol-handler.external.xdg user set string /usr/bin/zdgurl Still no joy. -- _ °v° /(_)\ ^ ^ Mark LaPierre Registered Linux user No #267004 https://linuxcounter.net/ ****

3 4

SSH Weak Ciphers
by Clint Dilks 20 Oct '16

20 Oct '16

Hi, In a recent security review some systems I manage were flagged due to supporting "weak" ciphers, specifically the ones listed below. So first question is are people generally modifying the list of ciphers supported by the ssh client and sshd? On CentOS 6 currently it looks like if I remove all the ciphers they are concerned about then I am left with Ciphers aes128-ctr,aes192-ctr,aes256-ctr for both /etc/ssh/sshd_config and /etc/ssh/ssh_config. Is just using these three ciphers like to cause me any problems? Could having so few ciphers be creating a security concern itself? Thanks The following weak client-to-server encryption algorithms are supported by the remote service: rijndael-cbc(a)lysator.liu.se arcfour256 arcfour128 aes256-cbc 3des-cbc aes192-cbc blowfish-cbc cast128-cbc arcfour aes128-cbc The following weak server-to-client encryption algorithms are supported by the remote service: rijndael-cbc(a)lysator.liu.se arcfour256 arcfour128 aes256-cbc 3des-cbc aes192-cbc blowfish-cbc cast128-cbc arcfour aes128-cbc

9 18

Bacula Restore
by Alessandro Baggi 20 Oct '16

20 Oct '16

Hi list, another question about bacula, but this time about restoring backups. I've a server that I must backup every day. My plan is: from mon to sat incrimental backup and on sunday full backup. When I will perform a restore I must restore from last valid full backup and then all valid incremental backup from last backup to specific date. This server has aweb managed application where user can update data or delete data. Suppose that after a full backup, on monday the user upload a file and incrimental backup is performed. On tuesday the user remove the uploaded file and backup is performed. Suppose that I want perform a restore of these jobs. I restore full, mon-incr and I found on restore path file uploaded on monday. When restoring tuesday incr (where the uploaded file was not present), on restore path I will found the uploaded file or bacula remove it with tuesday incremental backup restore? Sorry but today I can't try this due to time issue. Thanks in advance.

3 4

port running but connection refused
by Jerry Geis 19 Oct '16

19 Oct '16

Hi All, I have a process running on port 5070... I'm using CentOS 7. iptables is running firewalld should be stopped and disabled. When I telnet localhost 5070 I get connection refused. When I stop iptables I still get connection refused. netstat -tnlv | grep 5070 tcp 0 0 192.168.1.8:5070 0.0.0.0:* LISTEN so the process is running and listening. ps ax | grep firewalld returns nothing except the grep command. What else could be blocking this connection? Thanks, Jerry

2 1

glxinfo problem
by Mahmoud A. A. Ibrahim 19 Oct '16

19 Oct '16

Dear Centos Users We are running centos on our HPC. Indeed, we have a problem with running some software using X11 server such as pymol. For your information, we are using cygwin to access to the hpc (using ssh -X -Y username(a)xxx.xxx.xxx.xxx) When we are testing glxinfo on my desktop, it gives us the following error: [username@hpc ~]# glxinfo name of display: localhost:10.0 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 149 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 20 Current serial number in output stream: 23 The weird thing is that when we use another desktop computer running the same cygwin version and accessing with the same username, glxinfo works fine. Indeed, echo $DISPLAY on my desktop computer gives us localhost:10.0 , while it gives localhost:13.0 on the another desktop. If I set DISPLAY on my desktop to localhost:13.0, it doesn't work One more point, if we run glxinfo on the another desktop using my account and logging at the same time from my desktop with the same username and setting DISPLAY to 13:0, glxinfo works on my desktop. Any kind of help will be highly appreciated. Sincerely; M. Ibrahim

2 1

renaming mdadm name
by Phil Manuel 19 Oct '16

19 Oct '16

Hi I have a disk which two of the partitions are part of a RAID1 setup. I'm trying to rename the the second raided partition mdadm -E /dev/sdc4 /dev/sdc4: Magic : a92b4efc Version : 1.2 Feature Map : 0x1 Array UUID : 83d7657b:ebfddcb7:36b0fa14:d29a350c Name : oldname:2 Creation Time : Tue Aug 30 15:25:10 2016 Raid Level : raid1 Raid Devices : 2 Avail Dev Size : 486696960 (232.08 GiB 249.19 GB) Array Size : 243348480 (232.08 GiB 249.19 GB) Data Offset : 262144 sectors Super Offset : 8 sectors Unused Space : before=262056 sectors, after=0 sectors State : clean Device UUID : 97aba979:dd4cf85c:f6dbf4f6:f1e9ccab Internal Bitmap : 8 sectors from superblock Update Time : Fri Sep 23 14:21:00 2016 Bad Block Log : 512 entries available at offset 72 sectors Checksum : 749e26a8 - correct Events : 7319 Device Role : Active device 0 Array State : A. ('A' == active, '.' == missing, 'R' == replacing) For the first partition I stopped the RAID using mdadm --stop /dev/md127 and then reassembeld using mdadm --assemble /dev/md127 --name=newname_boot --update=name /dev/sdc2 The first partition was easy as the system had started the RAID, but the second parition the system does start, and when I try to assemble it, it tells me it's already active:- mdadm --assemble --uuid=83d7657b:ebfddcb7:36b0fa14:d29a350c --name=newname2 --update=name /dev/md2 /dev/sdc4 mdadm: Found some drive for an array that is already active: /dev/md/oldname:2 So any ideas on how i can rename this ? Thanks Phil.

1 0

Lockd: failed to reclaim lock for pid ...
by Dan Hyatt 18 Oct '16

18 Oct '16

My environment is "heterogeneous" my authentication and home server are currently stuck on a 1G shared network, the production servers and storage servers are on a bonded 40G network, all are in the same VLAN. I have about 100 servers on the 40GB bonded network each with 12cores and 128GB of memory. They are running centos 6.6 Except for my storage servers they are all just running large and small research jobs on a grid engine. Two questions: The errors she seems to spawn is lockd: spurious grace period reject?! lockd: failed to reclaim lock for pid 8225 (errno -37, status 4) lockd: spurious grace period reject?! lockd: failed to reclaim lock for pid 8225 (errno -37, status 4) and at some point, we start getting errors that the file locks are stuck.. you can write and read from the lockfile, but programs that depend on the C construct lock file throw filelock errors until we reboot. Why is dmesg, /var/log/dmesg, and /var/log/messages unique from each other? I thought dmesg was a representation of /var/log/messages/ Is there a way to get a date stamp for the dmesg? if a job failed in the last hour and the message is from yesterday...and I don't know that doesn't help. I think what I am troubleshooting is THAT user who REFUSES to follow direction... and is sending thousands of very large jobs which each might immediately spawn another 10-20 jobs to a grid of 100 servers in a matter of seconds overwhelming either the network or the home directory server or the authentication server... because when she strikes, sometimes users cannot get a response from LDAP or the home server within as much as 10 seconds. Thus she breaks the NFS because it gets hammered and I have to restart all the servers on my grid. We have had problems with "out of memory errors" due to her programs in the recent past and had to restart all 100 servers. */var/adm/messages gives this* Oct 18 13:26:08 blade5-2-1 nslcd[2520]: [dd5cc5] ldap_result() failed: Can't contact LDAP server Oct 18 13:26:08 blade5-2-1 nslcd[2520]: [dd5cc5] ldap_abandon() failed to abandon search: Other (e.g., implementation specific) error Oct 18 13:27:14 blade5-2-1 nslcd[2520]: [e01acb] ldap_result() failed: Can't contact LDAP server Oct 18 13:27:30 blade5-2-1 nslcd[2520]: [8c7a8f] ldap_result() failed: Can't contact LDAP server *dmesg gives these* lockd: server home not responding, still trying lockd: server home OK lockd: spurious grace period reject?! lockd: failed to reclaim lock for pid 8225 (errno -37, status 4) lockd: spurious grace period reject?! lockd: failed to reclaim lock for pid 8225 (errno -37, status 4) */var/log/dmesg gives this* pmi_si: probing via SMBIOS ipmi_si: SMBIOS: io 0xca8 regsize 1 spacing 4 irq 10 ipmi_si: Adding SMBIOS-specified kcs state machine ipmi_si: Trying SMBIOS-specified kcs state machine at i/o address 0xca8, slave address 0x20, irq 10 (NULL device *): The BMC does not support setting the recv irq bit, compensating, but the BMC needs to be fixed. IRQ 10/ipmi_si: IRQF_DISABLED is not guaranteed on shared IRQs ipmi_si ipmi_si.0: Using irq 10 ipmi_si ipmi_si.0: Found new BMC (man_id: 0x0002a2, prod_id: 0x0100, dev_id: 0x20) ipmi_si ipmi_si.0: IPMI kcs interface initialized ACPI: No handler for Region [SYSI] (ffff882029e57348) [IPMI] power_meter ACPI000D:00: Found ACPI power meter. ipmi device interface EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: Adding 121724924k swap on /dev/mapper/vg_server-lv_swap. Priority:-1 extents:1 across:121724924

3 2

Disabling sound chip
by Alice Wonder 18 Oct '16

18 Oct '16

01:00.1 Audio device [0403]: NVIDIA Corporation High Definition Audio Controller [10de:0be3] (rev a1) I don't want that seen by the sound software. That's the sound chip on my video card, probably there for the HDMI output. For some reason, that sound device takes preference over my USB headphones and it is really annoying I tried creating /etc/modprobe.d/blacklist with the following : blacklist snd_hda_intel blacklist snd_hda_codec_hdmi That didn't work. Those are not CentOS specific instructions, the only CentOS specific instructions I found are related to nVidia and are rather complex and I don't believe this is that complex - at least it shouldn't be. I'm 99% sure snd_hda_intel is the driver. It shows up as Intel HD Audio in the Mate Sound control panel. I just want it disabled so I don't have to constantly use the control panel. Any hints or suggestions appreciated, not sure why there isn't just a checkbox to disable things like sound devices.

2 2

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss October 2016