Discuss

discuss@lists.centos.org

2 participants
34758 discussions

Re: [CentOS] Semi-OT: hardware: NVidia proprietary driver, C7.4
by Kretschmer, Jens 20 Nov '17

20 Nov '17

Hi Mark, did you manage to sort out messages from Dracut and /sbin/weak-modules you received while installing kmod-nvidia? We get the same messages while installing kmod-nvidia-384.98-1.el7_4.elrepo.x86_64 on RHEL 7.4 with the kernel 3.10.0-693.5.2.el7.x86_64. Kr, Jens

3 2

gnome boot problem
by dominic adair-jones 20 Nov '17

20 Nov '17

greetings all. running centos 7. i recently performed an upgrade and the server rebooted later in the night. now everytime i start my server its sits at the grey gnome background. i can hit ctl+atl+f2 to get to another console and the error message states "a start job is running for wait for plymouth boot screen to quit". i can ssh into the server but i dont see any obvious issues. this is the brain of my network and houses all my vms and documents. any help would be greatly appreciated.

6 15

Intel Bluetooth problems - "Invalid request code (56)" - on CentOS 6.9
by Toralf Lund 20 Nov '17

20 Nov '17

Hi, I have Lenovo laptop with an Intel wireless and Bluetooth adapter, running CentOS 6.9. The wireless works just fine, but I can't seem to get Bluetooth to work. When I try to force it up from the command line I get # hciconfig hci0 up Can't init device hci0: Invalid request code (56) There is also a similar message message in /var/log/messages from start-up on boot. The device info from "hciconfig" also seems a bit suspicious to me - notice how the address has all 0s: # hciconfig -a hci0: Type: BR/EDR Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:48 acl:0 sco:0 events:8 errors:0 TX bytes:24 acl:0 sco:0 commands:12 errors:4 /var/log/messages indicates that firmware is loaded correctly # egrep "iwlwifi.*firmware" /var/log/messages Nov 20 09:24:16 osl-97214 kernel: iwlwifi 0000:04:00.0: firmware: requesting iwlwifi-8000C-17.ucode Nov 20 09:24:16 osl-97214 kernel: iwlwifi 0000:04:00.0: firmware: requesting iwlwifi-8000C-16.ucode Nov 20 09:24:16 osl-97214 kernel: iwlwifi 0000:04:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm and I think the following shows that the device is actually there # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 17ef:1010 Lenovo Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 005: ID 5986:0706 Acer, Inc Bus 002 Device 002: ID 17ef:1010 Lenovo Bus 001 Device 006: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 007: ID 17ef:100f Lenovo Bus 002 Device 003: ID 2109:8110 VIA Labs, Inc. Hub Bus 001 Device 008: ID 05e3:0610 Genesys Logic, Inc. 4-port hub # lsusb -s 001:004 -v | grep bInterface bInterfaceNumber 0 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth bInterfaceNumber 1 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth bInterfaceNumber 1 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth bInterfaceNumber 1 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth bInterfaceNumber 1 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth bInterfaceNumber 1 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth bInterfaceNumber 1 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth The bluetooth kernel modules should be loaded, too (but perhaps I need some extra driver or whatever?) # lsmod | grep bluetooth bluetooth 97799 6 sco,bnep,l2cap,btusb rfkill 19255 5 cfg80211,bluetooth,thinkpad_acpi Does anyone have any idea what's wrong here? Is there any way at all I can enable Bluetooth on this system? Thanks, - Toralf

2 1

Possible to have EthX acting like the ipaddress of the attached device (aka bridge) having no ipaddress?
by Jobst Schmalenbach 20 Nov '17

20 Nov '17

Hi I have a Centos 6.X router/firewall/gateway for a /29 network all connected to one ETHX that has a switch behind it. This setup works very well but does NOT allow me to QOS one of the devices (a VOIP phone, many lines) as for "tc" to work I need a device, not ipaddress. I thought to connect the VOIP phone directly to the router, but in doing so I need that interface to ACT like the IPADDRESS of the VOIP box, meaning the ethernet interface has no ipaddress acting like a bridge: Internet | --------------------------- | router ip | | BRIDGE base of /29 --------------------------- | | | ------------- | | | | _____________ | | | | | | ---------------- | phone system | ---------------- That way I can use "tc" to prioritize the traffic for the phone system If there are other ways to do this, please suggest. thanks Jobst -- Sometimes, the sharpest sword is not enough, but usually...it is. | |0| | Jobst Schmalenbach | | |0| +61 3 9533 0000, POBox 277, Caulfield South, 3162, Australia |0|0|0|

1 0

CentOS 7: unable to mount
by wwp 18 Nov '17

18 Nov '17

Hello, when I plug an external disk (USB3) of mine, I get this 'Unable to mount /mnt/storage10' alert: Error mounting system-managed device /dev/sda1: Command-line `mount "/mnt/storage10"' exited with non-zero exit status 32: mount: /dev/sda1 is already mounted or /mnt/storage10 busy /dev/sda1 is already mounted on /mnt/storage10 And it's right, /mnt/storage10 has just been mounted (by root): # mount /dev/sda1 on /mnt/storage10 type ext4 (rw,nosuid,nodev,relatime,seclabel,data=ordered) as it's defined in /etc/fstab: /dev/disk/by-id/usb-TOSHIBA_External_USB_3.0_20140807009490F-0:0-part1 /mnt/storage10 auto nosuid,nodev,nofail,x-gvfs-show 0 0 Question is: why are there 2 concurrent mount attempts? The user one fails. I will need the root password to unmount. I'd prefer the user mount to proceed, BTW. Other USB disks behave the same here. For every single USB disk I need, once I've mounted it the first time, I've edited the mount options in the gnome-disk-utility and set it to be automatically mounted and "Mount at startup" and "Show in user interface" to true. Any hint, there? Regards, -- wwp

1 0

semi-OT:apcupsd
by m.roth＠5-cent.us 18 Nov '17

18 Nov '17

I can't seem to find apcupsd for C 6. Just went to epel's website, and not visible. Anyone have a clue? mark

9 14

Re: [CentOS] semi-OT:apcupsd
by Miguel Medalha 18 Nov '17

18 Nov '17

>> I can't seem to find apcupsd for C 6. Just went to epel's website, >> and not visible. Anyone have a clue? I am running apcupsd on CentOS 6.9, monitoring through the network a common UPS that is physically connected to another server via USB. Just download the latest source code and compile it yourself. It's as easy as ./configure make make install No problems whatsoever.

1 0

CentOS-announce Digest, Vol 153, Issue 4
by centos-announce-request＠centos.org 18 Nov '17

18 Nov '17

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-2017:3247 Critical CentOS 6 firefox Security Update (Johnny Hughes) 2. CESA-2017:3247 Critical CentOS 7 firefox Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 17 Nov 2017 16:50:04 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:3247 Critical CentOS 6 firefox Security Update Message-ID: <20171117165004.GA21777(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:3247 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2017:3247 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: d7077384cc2593c8bc462d76e5167ba9e8fd9bcc517c8ce01dc110ad259b7d6b firefox-52.5.0-1.el6.centos.i686.rpm x86_64: d7077384cc2593c8bc462d76e5167ba9e8fd9bcc517c8ce01dc110ad259b7d6b firefox-52.5.0-1.el6.centos.i686.rpm 61d760be7c4fc39ea73792b64bf1c795f2e69cb3da13897e2b3b0e60506f7648 firefox-52.5.0-1.el6.centos.x86_64.rpm Source: e1f638e27bac1f4aec6cbbec91a0bfda495c77f6f1089771cb7e45df32f1a616 firefox-52.5.0-1.el6.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Fri, 17 Nov 2017 16:54:29 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:3247 Critical CentOS 7 firefox Security Update Message-ID: <20171117165429.GA21965(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:3247 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2017:3247 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 69d18c12d8754992222e09d20142293882e45d27e6998df7ea6a4134da97e11d firefox-52.5.0-1.el7.centos.i686.rpm 3fea84e873702db7febafaf1677c89d7038127c3280921b6e8498911618eb4a7 firefox-52.5.0-1.el7.centos.x86_64.rpm Source: 25633241b2c7d527db4cb389b1fb9a57e8b82cebc8c3794043eb0ddb074438d8 firefox-52.5.0-1.el7.centos.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 153, Issue 4 ***********************************************

1 0

CentOS Linux 6 to CentOS Linux 7 upgrade tool
by Johnny Hughes 17 Nov '17

17 Nov '17

We have asked several times on this list (and other places) for someone from the Community to maintain the Upgrade Tool for c6 to c7 upgrades. It was maintained for a very short period of time, and now that version no longer works. Info about the tool is here: https://wiki.centos.org/TipsAndTricks/CentOSUpgradeTool If we can not get someone to maintain the tool, we are going to have to remove it from downloads as it no longer works. Will someone from the Community please step up and maintain it? Thanks, Johnny Hughes

1 0

USB Serial Ports
by Chris Olson 17 Nov '17

17 Nov '17

We have several CentOS 6 systems that are used in various configurations of test equipment. One of the primary functions of these systems is the connectivity to serial ports of some operational systems that have serial port control requirements. Lack of interface bus slots led us to the use of USB connected serial ports on these CentOS 6 systems. We first used these USB connected serial ports in our RHEL 5 test equipment systems. With RHEL 5, shut down and boot up of the systems would often cause the serial ports to have a different driver name, even though we had not changed the ports where the USB devices were plugged in. This caused software access problems until we discovered what could be done using the udev rules to lock in the driver names. This problem seems to have gone away in our newer systems with CentOS 6, and we would like to make sure that it does not return. We are deploying some of the systems and do not want to have software access issues in the field where fixes are more difficult. We would like to know if there is some underlying factor that has solved this problem for us. Any ideas on what to check would be greatly appreciated.

3 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss