Re: [CentOS] Compatible SATA controller needed
On Sun, Mar 27, 2022 at 11:55 AM Pete Geenhuizen wrote: > I'm trying to install Centos 8 on an older PC but it fails because the > SATA controller isn't supported. > Anyone have a source for a PCI/ePCI controller card that is compatible > with Centos 8? > Thanks > Pete > Your controller might be supported by one of the ELRepo's kmod packages. This can be checked if you provide the device ID pairing [:] as reported by 'lspci -nn'. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS Plus 8-stream support?
On Fri, Feb 11, 2022 at 3:02 PM Dan West wrote: > > Are the centos-plus packages for 8-stream no longer supported? I noticed > that all of the repositories have removed the packages, but I have not heard > any announcement that said they were going away. For example: > > The last mention of the centos-plus repos I can find in the mailing list was > from November 18th and was just addressing the final release of CentOS 8: > ``` > Note that older content, obsoleted by newer versions of the same > applications are trim'd off from repos like extras/ and centosplus/ > ``` > While CentOS 8 EOL’d at the end of December, my understanding is that CentOS > 8-Stream will be supported until May 31st 2024. Does that include CentOS > Plus for 8-Stream? > > I really just need CentOS Plus for the kernel-plus package for Wireguard > support. The alternative would be to build it into kernel after each > release myself, but that isn’t easily maintainable with multiple servers. > > Let me know if anyone has any insights. > > Thanks, > Dan West If you need wireguard, then you can use the kmod-wireguard package for CentOS Stream maintained by the CentOS kmods SIG. http://mirror.centos.org/centos-8/8/kmods/x86_64/packages-main/Packages/k/ Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Difference between CentOS Linux and CentOS Stream
On Tue, Jul 20, 2021 at 7:50 AM Ian Pilcher wrote: > > On 7/19/21 1:58 PM, Johnny Hughes wrote: > > If you are not doing anything special with the kernel, then there is > > very little difference between CentOS Stream and CentOS Linux. > > Out of curiosity, do we yet know the frequency of reboot-required > updates (kernel, glibc, systemd, etc.) in CentOS Stream? You may want to go to git.centos.org. For example you can find the kernel commits for CentOS Stream 8 here: https://git.centos.org/rpms/kernel/commits/c8s Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Transition test report going from CentOS8 to Debian 10.
On Thu, Feb 4, 2021 at 10:23 AM Warren Young wrote: > > On Feb 4, 2021, at 8:39 AM, Lamar Owen wrote: > > > > I posted a pretty complete rundown on the scientific linux users mailing > > list, so I won't recap it all here. > > Link? https://listserv.fnal.gov/scripts/wa.exe?A2=ind2102&L=SCIENTIFIC-LINUX-USERS&P=5275 Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Future of CentosPlus?
On Thu, Dec 10, 2020 at 4:12 AM Gerhard Schneider wrote: > > > Is there anything known about the future of CentosPlus after moving to a > Pre-RHEL CentOS Stream? > > It would be of no interest to RedHat.. > > Gerhard Schneider As the maintainer of the plus kernel for the last 10+ years, I'd like to know the answer ... Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] https://blog.centos.org/2020/12/future-is-centos-stream/
On Wed, Dec 9, 2020 at 6:07 PM Lamar Owen wrote: > > On 12/9/20 12:10 PM, Brendan Conoboy wrote: > > While I'm not sure how we'll get there, it seems like the > > mutually satisfying end result would be one where third party binary > > drivers work with CentOS Stream kernels. Let's see what we can do. > > > So, I want to address this part a bit. In MANY cases, it's not a > third-party driver that ELrepo packages; it's an in-kernel driver that > Red Hat has decided to disable. Such as the megaraid_sas driver I need > for my servers. And just to give you some more examples -- ELRepo offers DUD (driver update disk) images for the devices whose support has been dropped in RHEL 8: https://elrepo.org/linux/dud/el8/x86_64/ Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Firefox 78 under CentOS 6 -- no sound?
On Sat, Oct 17, 2020 at 1:38 PM Robert Heller wrote: > I did a yum update on my CentOS 6 laptop and it upgraded Firefox to 78, > and > FF stopped seeing my mic and speakers. Is there some magic I need to do? > As > a short term (?) fix, I downgraded back to Firefox 68. My system is > otherwise > up-to-date. > > -- > Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 > Deepwoods Software-- Custom Software Services > http://www.deepsoft.com/ -- Linux Administration Services This issue? https://bugs.centos.org/view.php?id=17767 Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] JFS for CentOS 7
On Fri, Sep 25, 2020 at 11:51 AM H wrote: > > On 09/15/2020 08:07 PM, Akemi Yagi wrote: > > On Tue, Sep 15, 2020 at 3:54 PM H wrote: > >> I had installed kmod-jfs in an earlier version of CentOS 7, 7.4 if I > >> remember correctly. I now have a machine running the latest version of jfs > >> module but kmod-jfs does not seem to be available. > >> > >> Is anyone running it on the current version of CentOS? > > My suggestion is to use the centosplus kernel (kernel-plus) instead. > > jfs is enabled in this kernel. > > > > Akemi > Would I simply install it by using yum? Are there any downsides to installing > this kernel vs. relying on the standard kernel? To install the kernel-plus: # yum --enablerepo=centosplus install kernel-plus Boot into the just installed kernel-plus and check to see if jfs is working as expected. If all is fine, change the default kernel to kernel-plus: # yum-config-manager --setopt=centosplus.includepkgs=kernel-plus --enablerepo=centosplus --save # sed -e 's/^DEFAULTKERNEL=kernel$/DEFAULTKERNEL=kernel-plus/' -i /etc/sysconfig/kernel I would not say there is any downside, but I'm highly biased. ;) Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 8 LSI SAS2004 Driver
On Sat, Sep 19, 2020 at 8:04 PM William Markuske wrote: > > Hello, > > I've recently been given domain over a number of supermicro storage > servers using Broadcom / LSI SAS2004 PCI-Express Fusion-MPT SAS-2 > [Spitfire] (rev 03) to run a bunch of SSDs. I was attempting to do fresh > installs of CentOS 8 and have come to find out that RedHat deprecated > support for a number of HBAs for 8 including all running the SAS2004 chip. > > Does anyone know if there is a driver available for this chip from a > third party repo? My google searches have led me to believe that EPEL 8 > has a kmod-mpt3sas package but it does not seem to exist though multiple > blogs have stated otherwise. If anyone knows if there is a solution for > CentOS 8 that would be great or if I have to roll back to CentOS 7 for > card support. > > Thanks, > > William It is ELRepo, not EPEL. :) http://elrepoproject.blogspot.com/2019/08/rhel-80-and-support-for-removed-adapters.html Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] JFS for CentOS 7
On Tue, Sep 15, 2020 at 3:54 PM H wrote: > > I had installed kmod-jfs in an earlier version of CentOS 7, 7.4 if I remember > correctly. I now have a machine running the latest version of jfs module but > kmod-jfs does not seem to be available. > > Is anyone running it on the current version of CentOS? My suggestion is to use the centosplus kernel (kernel-plus) instead. jfs is enabled in this kernel. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Viewing changelog for packages to be updated
On Wed, Aug 26, 2020 at 11:18 PM Simon Matter via CentOS wrote: > > > On Wed, Aug 26, 2020 at 2:54 PM Kenneth Porter > > wrote: > >> > >> Is there some way to see the RPM changelog entries for a prospective yum > >> update? Ideally I'd like to see just the entries that are newer than the > >> version of the package I already have. > >> > >> I saw a new kernel in today's yum-cron email and I'd like to know what > >> it's > >> about and how urgent the issue is for me. > > > > You may want to look into git.centos.org. For example, spec file diff > > for the latest C7 kernel update can be seen here: > > > > https://git.centos.org/rpms/kernel/c/c53828b00fb26a7f96b149eef5e220a5ed4cc4e5?branch=c7#_5 > > Hi Akemi, > > Thanks for the hint about git.centos.org. > But, is there some yum/dnf utility which can show the changelog changes? > If not, then I may expand one of my rpm tools to do it. > > Simon yum -q --changelog xxx.rpm will show the changelog. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Viewing changelog for packages to be updated
On Wed, Aug 26, 2020 at 2:54 PM Kenneth Porter wrote: > > Is there some way to see the RPM changelog entries for a prospective yum > update? Ideally I'd like to see just the entries that are newer than the > version of the package I already have. > > I saw a new kernel in today's yum-cron email and I'd like to know what it's > about and how urgent the issue is for me. You may want to look into git.centos.org. For example, spec file diff for the latest C7 kernel update can be seen here: https://git.centos.org/rpms/kernel/c/c53828b00fb26a7f96b149eef5e220a5ed4cc4e5?branch=c7#_5 Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Blog article about the state of CentOS
On Wed, Jun 17, 2020 at 1:53 PM Chris Adams wrote: > Once upon a time, Noam Bernstein said: > > Of course. My only question is whether the observation that the gap > for CentOS 8 is indeed larger than we have come to be used to for CentOS 7. > > So, I took a look... and the answer is "it's not" (with a small sample > set). I took dates from Wikipedia for RHEL and the archived release > notes for CentOS. I didn't bother with the .0 releases (since that's a > lot of new work anyway). Right now, CentOS 8 is far faster than CentOS > 7 and 6 were at this stage. > > release RHEL date CentOS date days > 6.1 2011-05-19 2011-12-12 207 > 6.2 2011-12-06 2012-07-24 231 > 6.3 2012-05-20 2012-09-30 133 > 6.4 2013-02-21 2013-05-21 89 > 6.5 2013-11-21 2014-02-26 97 > 6.6 2014-10-13 2014-11-15 33 > 6.7 2015-07-22 2015-09-05 45 > 6.8 2016-05-10 2016-07-28 79 > 6.9 2017-03-21 2017-04-05 15 > 6.102018-06-19 2018-07-03 14 > > 7.1 2015-03-05 2015-10-11 220 > 7.2 2015-11-19 2016-02-19 92 > 7.3 2016-11-03 2016-12-21 48 > 7.4 2017-08-01 2018-03-21 232 > 7.5 2018-04-10 2018-10-30 203 > 7.6 2018-10-30 2019-01-28 90 > 7.7 2019-08-06 (didn't find release notes) > 7.8 2020-03-31 2020-04-27 27 > > 8.1 2019-11-05 2020-01-15 71 > 8.2 2020-04-28 2020-06-15 48 > 7.7 2019-08-06 2019-09-17 42 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 8 and E1000 intel driver
On Fri, Jan 17, 2020 at 3:16 PM david wrote: > > Folks > > I know that support for the network adaptors supported by the 'e1000' > driver have been removed from the base distribution. However, I have > exactly that controller (Broadcom Gigabit Ethernet PCI, not > PCIe). Is there a way for me to add support for that on Centos > 8.1? Perhaps a driver in an RPM package? > > Thanks > > David The e1000 driver should be in the 8.1 kernel: $ modinfo e1000 filename: /lib/modules/4.18.0-147.3.1.el8_1.x86_64/kernel/drivers/net/ethernet/intel/e1000/e1000.ko.xz version:7.3.21-k8-NAPI license:GPL description:Intel(R) PRO/1000 Network Driver author: Intel Corporation, rhelversion:8.1 Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Raspberri PI 4B 4GB install image
On Wed, Dec 25, 2019 at 7:53 AM Strahil via CentOS wrote: > > Hello Community, > > I'm waiting for my first ARM-based toy - a 4GB Raspberry Pi 4B and I was > looking for a CentOS 8/ CentOS Stream image with no success. > > Do we have an image ? > > Best Regards, > Strahil Nikolov Here we go: https://forums.centos.org/viewtopic.php?f=49&t=71407&p=305437&hilit=pgreco#p305437 Thanks to Pablo Greco. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] State of CentOS 8
On Sun, Dec 22, 2019 at 5:30 PM Bill Maidment wrote: > > > https://wiki.centos.org/About/Building_8.x > > This misses the point of where are the intermediate updates to 8.0 ? or > can we only get point releases with no updates in between? You may want to watch the "CR work" on that wiki page. What is the CR repo? https://wiki.centos.org/AdditionalResources/Repositories/CR Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 Plus Kernel Update Missing?
On Sun, Dec 8, 2019 at 8:34 AM Akemi Yagi wrote: > > On Sun, Dec 8, 2019 at 5:50 AM Albert McCann > wrote: > > > > Along with the recent kernel update (3.10.0-1062.9.1.el7), the CentOS 7 > > plus kernel was likewise updated. The plus kernel though hasn't shown up in > > the mirrors yet, while the plain kernel has. Could someone please push the > > release button for the plus kernel? > > That "someone" is Johnny Hughes. :) The release button pushed today. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 Plus Kernel Update Missing?
On Sun, Dec 8, 2019 at 5:50 AM Albert McCann wrote: > > Along with the recent kernel update (3.10.0-1062.9.1.el7), the CentOS 7 plus > kernel was likewise updated. The plus kernel though hasn't shown up in the > mirrors yet, while the plain kernel has. Could someone please push the > release button for the plus kernel? That "someone" is Johnny Hughes. :) > What I do see in the various random mirrors I've manually checked is the > previous plus kernel (kernel-plus-3.10.0-1062.7.1.el7.centos.plus.rpm) shows > a release date of 12-6 instead of 12-3 it had a few days ago. You can follow the source updates for the plus kernel here: https://git.centos.org/rpms/kernel/commits/c7-sig-centosplus-kernel > Thanks, and thank you for all the work and help you folks do, it's greatly > appreciated by this retired old phart. > > Albert McCann Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] RHEL 8.1
On Tue, Nov 5, 2019 at 10:09 PM Thomas Stephen Lee wrote: > > RHEL 8.1 released to cdn. > > did > > $ dnf upgrade > > and got 8.1 > > No official announcement yet. > > thanks > > --- > Thomas Stephen Lee Press Release [1] and Release Notes [2] are available. (1) https://www.redhat.com/en/about/press-releases/red-hat-ups-iq-intelligent-operating-system-latest-release-red-hat-enterprise-linux-8 (2) https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/8.1_release_notes/index Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] No IrDA Support with CentOS anymore?
On Tue, Oct 29, 2019 at 4:09 AM wrote: > > Hi there, > I've a laptop with CentOS 8 and a PC with CentOS 7. After 3 years of break > I was Scuba Diving last 3 weeks. Back at home I wish to download all dive > logs from my divecomputer connext via IrDA to my PC. > > But no kernel modul for IrDA was found. > > [root@rechner1 ~]# modprobe ircomm > modprobe: FATAL: Module ircomm not found in directory > /lib/modules/4.18.0-147.6.el8.x86_64 > [root@rechner1 ~]# modprobe ircomm_tty > modprobe: FATAL: Module ircomm_tty not found in directory > /lib/modules/4.18.0-147.6.el8.x86_64 > [root@destn40768 ~]# > > > [root@rechner1 ~]# lsusb | grep -i irda > Bus 002 Device 011: ID 9710:7780 MosChip Semiconductor MCS7780 4Mbps Fast > IrDA Adapter > [root@rechner1 ~]# > > Same with CentOS7 > > How do I get IrDA support? > > Mit freundlichen Grüßen / Kind regards > > Andreas Reschke As you found out, there is no support for IrDA in CentOS-7 or -8. The only CentOS kernel I see with the support for device [9710:7780] is the centosplus kernel for CentOS-6. This means that you'd need to install CentOS-6 and then update it with the kernel in the centosplus repository. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 8 and DELL 7540 Intel AX200 WIFI
On Fri, Oct 25, 2019 at 7:33 PM John Pierce wrote: > > On Fri, Oct 25, 2019 at 6:50 PM David Summers > wrote: > > . > > > 70:00.0 Network controller [0280]: Intel Corporation Device [8086:2723] > > (rev 1a) > > > > I believe the Intel AX200 Wifi card is the device 8086:2723 (rev1a) entry. > > > > Is there something I can do to enable it or is this a bug I need to file > > with RedHat? > > > https://www.intel.com/content/www/us/en/support/articles/05511/network-and-i-o/wireless-networking.html > > says that the AX200 is supported with Linux Kernel 5.1+, and the firmware > linked on that page. > -- > -john r pierce Device ID pair [8086:2723] is not in the current CentOS kernel 4.18.0-80.11.2.el8_0. However, it is found in the CentOS Stream kernel 4.18.0-144.el8. So, you may want to give it a try. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 8 Broken Installation
On Wed, Oct 2, 2019 at 4:10 PM Akemi Yagi wrote: > > On Wed, Oct 2, 2019 at 3:35 PM Günther J. Niederwimmer > wrote: > > > > > This Board have 2 Controller!° > > 00:1f.2 RAID bus controller: Intel Corporation C600/X79 series chipset SATA > > RAID Controller (rev 06) > > > > On this controller all drives are found and it is possible to create a > > Raid1! > > > > 07:00.0 Serial Attached SCSI controller: Intel Corporation C602 chipset > > 4-Port > > SATA Storage Control Unit (rev 06) > > > > But on this Contoller NO drives found? > > If you provide the device ID pairing [:] for the one that is > not working, it will become clear. Can you show us the output from: > > lspci -nn > > Is it this one? > > Serial Attached SCSI controller [0107]: Intel Corporation C602 chipset > 4-Port SATA Storage Control Unit [8086:1d6b] > > If so, the above device ID [8086:1d6b] is not supported in RHEL/CentOS > 8, unfortunately. > > Akemi And if that is indeed your device, that was bad news. But you have good news too. Device [8086:1d6b] is supported by the isci kernel module. ELRepo has a DUD for this driver: dd-isci-1.2.0-1.el8.elrepo.iso Ljubomir provided detailed instructions on how to use ELRepo's DUD isos earlier in this thread. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 8 Broken Installation
On Wed, Oct 2, 2019 at 3:35 PM Günther J. Niederwimmer wrote: > > This Board have 2 Controller!° > 00:1f.2 RAID bus controller: Intel Corporation C600/X79 series chipset SATA > RAID Controller (rev 06) > > On this controller all drives are found and it is possible to create a Raid1! > > 07:00.0 Serial Attached SCSI controller: Intel Corporation C602 chipset 4-Port > SATA Storage Control Unit (rev 06) > > But on this Contoller NO drives found? If you provide the device ID pairing [:] for the one that is not working, it will become clear. Can you show us the output from: lspci -nn Is it this one? Serial Attached SCSI controller [0107]: Intel Corporation C602 chipset 4-Port SATA Storage Control Unit [8086:1d6b] If so, the above device ID [8086:1d6b] is not supported in RHEL/CentOS 8, unfortunately. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 8 will be released soon?
On Wed, Sep 4, 2019 at 11:07 AM Jonathan Billings wrote: > > On Wed, Sep 04, 2019 at 12:11:09PM -0500, John R. Dennison wrote: > > > > On Wed, Sep 04, 2019 at 10:04:04AM +0530, Thomas Stephen Lee wrote: > > > I doubt that releasing CentOS 7.7 is a higher priority as many people are > > > using CentOS 7, > > > > ... > > > > I'm not quite sure how to parse that... > > I believe it is supposed to be: > > "I doubt that! Releasing CentOS 7.7 is a higher priority, as many > people are using CentOS 7." > > Punctuation is important. I have yet another theory. He probably meant to say: "I suspect that releasing..." As someone who is not a native English speaker, I know how this happens. "doubt" and "suspect" can be translated into the same word (certainly in Japanese). As a result, these two words are often used incorrectly. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kmod-nvidia-430.40-1.el7_6.elrepo.x86_64 fails to install
On Sat, Aug 24, 2019 at 3:21 PM Ian Mortimer wrote: > > On Sat, 24 Aug 2019, Gregory P. Ennis wrote: > > > On August 2, my desktop unit updated with > > kmod-nvidia-430.40-1.el7_6.elrepo.x86_64 > > which broke yum having a multiple of dependencies not being present. > > The latest from elrepo - kmod-nvidia-430.40-2.el7_7.elrepo.x86_64.rpm - > is built for EL 7.7 and is not compatible with CentOS 7.6. > > kmod-nvidia-430.40-1.el7_6.elrepo.x86_64 is the last that will work > with the latest CentOS 7.6 kernel. > > > --- > Ian This issue can be taken care of by installing yum-plugin-elrepo from ELRepo. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C7 Kernel module compilation
On Wed, Aug 7, 2019 at 11:00 PM Alessandro Baggi wrote: > > Il 07/08/19 20:15, Akemi Yagi ha scritto: > > On Wed, Aug 7, 2019 at 9:00 AM Alessandro Baggi > > wrote: > >> > >> Il 07/08/19 01:02, Phil Perry ha scritto: > >>> On 06/08/2019 14:45, Alessandro Baggi wrote: > > > >>> Please post the actual error message in dmesg or /var/log/messages. > >>> > >>> It's likely that the kernel is just grumbling that the module is not > >>> signed (missing key), but it's just noise unless you're using > >>> SecureBoot. Posting the actual message in full will help determine if > >>> that is the case. > >>> > >>> Thanks > >>> > >>> Phil > >> > >> Hi, thank you for your reply, > >> I solve adding in "General Setup" values of current kernel on > >> localversion option and adding Module.symver from > >> /boot/symver-version.gz to module directory. > >> > >> Now I get another problem compiling the third party module (i2c-nct6775): > >> > >> "CONFIG_RETPOLINE=y but not supported by the compiler. Compiler update > >> recomended. Stop." > >> > >> I tried using scl gcc7 and 8 but get the same issue. > >> > >> I checked that retpoline is related to Spectre but checking on centos with: > >> > >> cat /sys/devices/system/cpu/vulnerabilities/spectre_v2 > >> > >> I get: > >> > >> Mitigation: IBRS (kernel), IBPB > >> > >> and RETPOLINE seems disabled (I'm wrong?). > >> > >> I ridden in a blog post that I can disable this check commenting out > >> some lines starting from N. 166 of arch/Makefile but I don't think this > >> is the best approach. > >> > >> At this point I can't understand what means the previous error and why I > >> get this error when compiling i2c-nct6775. > >> > >> Can someone point me in the right direction? > > > > Please post the output from: > > > > rpm -qa kernel\* | sort > > > > and > > > > uname -r > > > > Akemi > > kernel-3.10.0-957.12.1.el7.x86_64 > kernel-3.10.0-957.12.2.el7.x86_64 > kernel-3.10.0-957.21.3.el7.x86_64 > kernel-3.10.0-957.27.2.el7.x86_64 > kernel-3.10.0-957.el7.x86_64 > kernel-devel-3.10.0-957.21.3.el7.x86_64 > kernel-devel-3.10.0-957.27.2.el7.x86_64 > kernel-headers-3.10.0-957.27.2.el7.x86_64 > kernel-ml-5.1.0-1.el7.elrepo.x86_64 > kernel-ml-devel-5.1.0-1.el7.elrepo.x86_64 > kernel-tools-3.10.0-957.27.2.el7.x86_64 > kernel-tools-libs-3.10.0-957.27.2.el7.x86_64 > kernel-tools-libs-devel-3.10.0-957.27.2.el7.x86_64 > > > 3.10.0-957.27.2.el7.x86_64 So, you tried to build the i2c-nct6775 module against kernel-3.10.0-957.27.2.el7 under the running kernel 3.10.0-957.27.2 and you have a matching version of kernel-devel. Then I don't quite understand why you get the "not supported by the compiler" error... Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C7 Kernel module compilation
On Wed, Aug 7, 2019 at 9:00 AM Alessandro Baggi wrote: > > Il 07/08/19 01:02, Phil Perry ha scritto: > > On 06/08/2019 14:45, Alessandro Baggi wrote: > > Please post the actual error message in dmesg or /var/log/messages. > > > > It's likely that the kernel is just grumbling that the module is not > > signed (missing key), but it's just noise unless you're using > > SecureBoot. Posting the actual message in full will help determine if > > that is the case. > > > > Thanks > > > > Phil > > Hi, thank you for your reply, > I solve adding in "General Setup" values of current kernel on > localversion option and adding Module.symver from > /boot/symver-version.gz to module directory. > > Now I get another problem compiling the third party module (i2c-nct6775): > > "CONFIG_RETPOLINE=y but not supported by the compiler. Compiler update > recomended. Stop." > > I tried using scl gcc7 and 8 but get the same issue. > > I checked that retpoline is related to Spectre but checking on centos with: > > cat /sys/devices/system/cpu/vulnerabilities/spectre_v2 > > I get: > > Mitigation: IBRS (kernel), IBPB > > and RETPOLINE seems disabled (I'm wrong?). > > I ridden in a blog post that I can disable this check commenting out > some lines starting from N. 166 of arch/Makefile but I don't think this > is the best approach. > > At this point I can't understand what means the previous error and why I > get this error when compiling i2c-nct6775. > > Can someone point me in the right direction? Please post the output from: rpm -qa kernel\* | sort and uname -r Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C7 Kernel module compilation
On Mon, Aug 5, 2019 at 9:21 AM Alessandro Baggi wrote: > > Il 05/08/19 18:07, Akemi Yagi ha scritto: > > On Mon, Aug 5, 2019 at 9:01 AM Alessandro Baggi > > wrote: > > Do you have secureboot enabled? Then yes, that requires a proper key. > > > > Akemi > > Yes I have secureboot enabled. If usefull to others in list this could > helps: > > https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Kernel_Administration_Guide/sect-signing-kernel-modules-for-secure-boot.html > > I think also that centos's wiki must be updated because steps are valid > for centos 5 and because key-signing is required for secure boot I think > that a proper section must be inserted. Update not finished yet but the above link has been added near the top of the wiki article. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C7 Kernel module compilation
On Mon, Aug 5, 2019 at 9:01 AM Alessandro Baggi wrote: > > Il 05/08/19 17:49, Akemi Yagi ha scritto: > > On Mon, Aug 5, 2019 at 8:42 AM Alessandro Baggi > > wrote: > >> > >> Il 05/08/19 17:30, Akemi Yagi ha scritto: > >>> On Mon, Aug 5, 2019 at 6:46 AM Alessandro Baggi > >>> wrote: > >>>> > >>>> Hey there, > >>>> I'm trying to compile a single module following this guide: > >>>> > >>>> https://wiki.centos.org/HowTos/BuildingKernelModules#head-d2e4c05886f94c701e4ae74387d41d8c40c25d01 > >>>> > >>>> and > >>>> > >>>> https://wiki.centos.org/HowTos/I_need_the_Kernel_Source > >>>> > >>>> I tried to compile a module for novuton led controller supplied by > >>>> thirdparty and I got several error. > >>>> > >>>> To check if this is the wrong procedure I tried to compile cifs module > >>>> as listed in howto but when loading with modprobe I get "Exec format > >>>> error", and from dmesg "cifs: no symbol version for module_layout > >>>> ", the same errors when compiling novuton module and I don't know why I > >>>> get this error. > >>> > >>> When following the instructions in BuildingKernelModules, which kernel > >>> version did you use? Also, after the "depmod -a" step, what is the > >>> output from: > >>> > >>> $ modinfo cifs | grep filename > >>> > >>>> I noticed that modules in centos are compressed in .xz but after running > >>>> make M=fs/cifs I got only a .ko kernel module and then I run xz to > >>>> compress the new module. > >>> > >>> Compressing modules is optional. Uncompressed form is functionally the > >>> same (of course it saves some disk space). > >>> > >>>> Can someone help me please? > >>>> > >>>> Thanks in advance. > >>> > >>> Akemi > >> > >> Hi Akemi, > >> thank you for your answer. > >> > >> Kernel version used is 3.10.0-957.27.2.el7.x86_64 > >> > >> [root@c7-test SPECS]# modinfo cifs | grep filename > >> filename: /lib/modules/3.10.0-957.27.2.el7.x86_64/extra/cifs.ko > > > > Looking good. I assume your running kernel is 3.10.0-957.27.2.el7 ? > > > > Akemi > Reading from dmesg seems that the module is not accepted by kernel due > to invalid signature. I need to sign the module with a key? Do you have secureboot enabled? Then yes, that requires a proper key. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C7 Kernel module compilation
On Mon, Aug 5, 2019 at 8:42 AM Alessandro Baggi wrote: > > Il 05/08/19 17:30, Akemi Yagi ha scritto: > > On Mon, Aug 5, 2019 at 6:46 AM Alessandro Baggi > > wrote: > >> > >> Hey there, > >> I'm trying to compile a single module following this guide: > >> > >> https://wiki.centos.org/HowTos/BuildingKernelModules#head-d2e4c05886f94c701e4ae74387d41d8c40c25d01 > >> > >> and > >> > >> https://wiki.centos.org/HowTos/I_need_the_Kernel_Source > >> > >> I tried to compile a module for novuton led controller supplied by > >> thirdparty and I got several error. > >> > >> To check if this is the wrong procedure I tried to compile cifs module > >> as listed in howto but when loading with modprobe I get "Exec format > >> error", and from dmesg "cifs: no symbol version for module_layout > >> ", the same errors when compiling novuton module and I don't know why I > >> get this error. > > > > When following the instructions in BuildingKernelModules, which kernel > > version did you use? Also, after the "depmod -a" step, what is the > > output from: > > > > $ modinfo cifs | grep filename > > > >> I noticed that modules in centos are compressed in .xz but after running > >> make M=fs/cifs I got only a .ko kernel module and then I run xz to > >> compress the new module. > > > > Compressing modules is optional. Uncompressed form is functionally the > > same (of course it saves some disk space). > > > >> Can someone help me please? > >> > >> Thanks in advance. > > > > Akemi > > Hi Akemi, > thank you for your answer. > > Kernel version used is 3.10.0-957.27.2.el7.x86_64 > > [root@c7-test SPECS]# modinfo cifs | grep filename > filename: /lib/modules/3.10.0-957.27.2.el7.x86_64/extra/cifs.ko Looking good. I assume your running kernel is 3.10.0-957.27.2.el7 ? Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] C7 Kernel module compilation
On Mon, Aug 5, 2019 at 6:46 AM Alessandro Baggi wrote: > > Hey there, > I'm trying to compile a single module following this guide: > > https://wiki.centos.org/HowTos/BuildingKernelModules#head-d2e4c05886f94c701e4ae74387d41d8c40c25d01 > > and > > https://wiki.centos.org/HowTos/I_need_the_Kernel_Source > > I tried to compile a module for novuton led controller supplied by > thirdparty and I got several error. > > To check if this is the wrong procedure I tried to compile cifs module > as listed in howto but when loading with modprobe I get "Exec format > error", and from dmesg "cifs: no symbol version for module_layout > ", the same errors when compiling novuton module and I don't know why I > get this error. When following the instructions in BuildingKernelModules, which kernel version did you use? Also, after the "depmod -a" step, what is the output from: $ modinfo cifs | grep filename > I noticed that modules in centos are compressed in .xz but after running > make M=fs/cifs I got only a .ko kernel module and then I run xz to > compress the new module. Compressing modules is optional. Uncompressed form is functionally the same (of course it saves some disk space). > Can someone help me please? > > Thanks in advance. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Replacing kernel-headers with custom compiled version (from kernel.org) - safe?
On Wed, Jun 26, 2019 at 5:20 AM Bagas Sanjaya wrote: > > Hello CentOS users, > > Currently I have compiled kernel version 4.19.37, which the source is from > kernel.org. I compiled the kernel by following > steps: > - get the kernel tarball and unpack it > - install prerequisties as described in > https://wiki.centos.org/HowTos/Custom_Kernel (in addition bc and > openssl-devel) > - copy the kernel configuration: >$ cp /boot/config-3.10.0-957.21.3.el7.x86_64 ~/linux-4.19.37/.config > - create configuration: >$ cd ~/linux-4.19.37 >$ make olddefconfig >$ make nconfig > - compile and create RPM package: >$ make vmlinux >$ make modules >$ make rpm-pkg > - install kernel RPM: ># yum install ~/rpmbuild/RPMS/x86_64/kernel-*.rpm > > However, in the last step (installing kernel RPM), I got following notice: > > PackageArch Version > Repository > Size > > Installing: > kernel x86_64 4.19.37_sentinel_custom-1 > /kernel-4.19.37_sentinel_custom-1.x86_64 > 209 M > kernel-devel x86_64 4.19.37_sentinel_custom-1 > /kernel-devel-4.19.37_sentinel_custom-1.x86_64 > 817 M > kernel-headers x86_64 4.19.37_sentinel_custom-1 > /kernel-headers-4.19.37_sentinel_custom-1.x86_64 > 4.6 M > replacing kernel-headers.x86_64 3.10.0-957.21.3.el7 > > Transaction Summary > > Install 3 Packages > > There, the compiled kernel-headers package (4.19.37_sentinel_custom-1) is > about to replace stock version > (3.10.0-957.21.3.el7). Is it safe to continue installing from compiled RPM > package above, or install kernel manually? In general, you want to keep the distro's kernel-headers unless you also plan to play with glibc. You may find the following article useful: https://kernelnewbies.org/KernelHeaders Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] does centos 7.6 support TL-WN725N
On Fri, May 31, 2019 at 8:31 AM qw wrote: > > Does centos 7.6 support TL-WN725N, which is a wireless adaptor? According to this forum thread: https://www.centos.org/forums/viewtopic.php?f=49&t=58006 ELRepo's kmod-8188eu seems to support your device. You may want to check the device IDs by running lsusb. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] youtube-dl No module named 'pkg_resources'
On Tue, May 7, 2019 at 7:55 PM Michael Hennebry wrote: > > youtube-dl doesn't work for me after a recent update. > I do not use it often, so do not know whether the update matters. > It gives the error message: > Traceback (most recent call last): >File "/usr/bin/youtube-dl", line 6, in > from pkg_resources import load_entry_point > ModuleNotFoundError: No module named 'pkg_resources' > > I've tried reinstalling python-setuptools, > installing python34-setuptools and reinstalling youtube-dl . > > I'm aware there is a bugzilla on it. > That and stackoverflow are where I got the ideas above. > > How do I make youtube-dl work on Centos 7? If you are using the EPEL one, you can resolve it by installing: (1) python36-setuptools from epel and (2) youtube-dl from epel-testing Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] detect agfl count corruption and reset agfl
On Mon, Mar 25, 2019 at 8:43 AM Akemi Yagi wrote: > > > On 3/25/19 4:44 AM, Richard Flack wrote: > > > Hi there, > > > > > > My apologies if this is the wrong place to post this, but I was > > > wondering if anyone had any information on whether or not the following > > > patch has or will make its way into the CentOS Kernel? > > > > > > https://patchwork.kernel.org/patch/10283095/ > The patch is commit a27ba2607e60312554cbcd43fc660b2c7f29dc9c upstream > (kernel.org). It was applied to kernel 4.16 and backported to 4.14 ( > https://lkml.org/lkml/2018/6/4/184 ). Therefore both CentOS kernels > 4.14 and 4.19 have that patch. Just checked the current CentOS kernel and confirm that the patch is in there. [fs] xfs: detect agfl count corruption and reset agfl (Brian Foster) [1569471] It was added as of kernel 3.10.0-912.el7. In other words all 7.6.1810 kernels are patched. What is the version of your running kernel? Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] detect agfl count corruption and reset agfl
On Mon, Mar 25, 2019 at 5:04 AM Johnny Hughes wrote: > > On 3/25/19 4:44 AM, Richard Flack wrote: > > Hi there, > > > > My apologies if this is the wrong place to post this, but I was > > wondering if anyone had any information on whether or not the following > > patch has or will make its way into the CentOS Kernel? > > > > https://patchwork.kernel.org/patch/10283095/ > 2. Kernel in the AltArch tree .. We have to use a different kernel for > armhfp, and we also build it for other CentOS arches .. it lives at: > > http://mirror.centos.org/altarch/7/kernel/ > > This kernel is based on a kernel.org LTS kernel (currently 4.14.x) and > if that patch gets rolled into the LTS stream, it will be in our kernels > there. > > 3. Experimential kernel in the AltArch tree .. this is a newer LTS > kernel (which we will use in future armhfp releases .. it is currently > based on 4.19.x LTS kernel.org kernel. This one will replace the 4.14 > kernel in the 7.7.x release whenever that happens. If that patch makes > it into 4.19.x LTS at kernel.org then it will be in this kernel too. > > http://mirror.centos.org/altarch/7/experimental/ The patch is commit a27ba2607e60312554cbcd43fc660b2c7f29dc9c upstream (kernel.org). It was applied to kernel 4.16 and backported to 4.14 ( https://lkml.org/lkml/2018/6/4/184 ). Therefore both CentOS kernels 4.14 and 4.19 have that patch. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOs 7 i386 & PAE Kernel
On Wed, Mar 6, 2019 at 7:23 AM Mike McTernan (wavemobile) wrote: > > On 3/6/19 1:28 PM, Johnny Hughes wrote: > > On 3/6/19 6:26 AM, Mike McTernan (wavemobile) wrote: > > > On 3/5/19 5:48 PM, Johnny Hughes wrote: > > > > > > Last question, if I may - Is there any specific reason why an i686 PAE > > > kernel built from the main RHEL sources isn't in the AltArch i386 os- > > > repo? > > > > > > Notably CentOS 6 provided both non-PAE and PAE 32-bit kernels, and > > > it's that step from CentOS 6 32-bit PAE onto CentOS 7 32-bit which > > > made me stumble, but okay now. > > > > The only reason is .. it is not included in the mainline RHEL 7 kernel > > source > > code. > > Ah - I guess since mainline RHEL 7 is only 64-bit on x86 now, it doesn't have > to worry about PAE vs non-PAE kernels. > > ... > > I have no objections trying to make PAE work with that kernel .. Patches > > accepted :D > > > > https://bugs.centos.org/view.php?id=6828 > > So with what I know now (thank you!) I recon the mainline 4.14 is probably a > better tested path for a 32-bit x86 PAE kernel, rather than starting at RHEL > 7. And since you are already building that kernel it's good news all round > :-) > > Kind Regards, > > Mike Going for the 4.14 kernel is absolutely a better choice. The i686 plus kernel is just lucky to be existing. It would not have been possible to maintain it without great support from people like Pablo and @kabe. We initially got the 32-bit version from Springdale (formerly Puias). Then they stopped building at some point. Building it becomes harder and harder with each release, it seems. So, there is no guarantee that there is another update to the i686 plus kernel. Akemi Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos bug 15570 - Not just a VBOX bug, can also reproduce on direct hardware install
On Thu, Feb 14, 2019 at 2:58 PM Akemi Yagi wrote: > > On Thu, Feb 14, 2019 at 2:32 PM Steve Gomez > wrote: > > > > However, the bug lists seem to refer only to issues with VirtualBox. I > > have experienced the same symptom when installing on a "hardware" system > > (no hypervisor). The same commands above also provide a workaround here, > > but thought the flag should be raised for CentOS and RHEL that it doesn't > > seem to be just VBOX. > > As noted in the CentOS bug report you referenced ( > https://bugs.centos.org/view.php?id=15570 ), I filed a report upstream > ( https://bugzilla.redhat.com/show_bug.cgi?id=1658669, marked > private). In that RHBZ, they were able to reproduce it without > VirtualBox. Therefore they are aware this is not just a VBox problem. > The fix has been added to kernel-3.10.0-984.el7, meaning it will be in > the EL 7.7 kernel. > > Now there is a separate RHBZ for "Z-Stream" for the same issue. This > means that the fix will be ported to the current series (EL 7.6). > Unfortunately I have no access to this BZ, so cannot tell the progress > there. Once it is fixed in RHEL, CentOS will inherit it. > > Akemi I added the following note to bug 15570: "The problem is not unique to VirtualBox. It can be reproduced _without_ VBox." Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos bug 15570 - Not just a VBOX bug, can also reproduce on direct hardware install
On Thu, Feb 14, 2019 at 2:32 PM Steve Gomez wrote: > > Ran into this rather frustrating bug when working with VBOX on a Windows 10 > host. It should come as no surprise that I would hit this bug when > installing CentOS, and also with RHEL 7 Server with GUI (since you get the > same kernel). Based on information from your bug list, I was fortunately > able to workaround the trouble with: > > wget > https://people.centos.org/toracat/kernel/7/plus/bug15570new/kernel-3.10.0-957.1.3.bug15570.plus.el7.x86_64.rpm > wget > https://people.centos.org/toracat/kernel/7/plus/bug15570new/kernel-devel-3.10.0-957.1.3.bug15570.plus.el7.x86_64.rpm > > yum -y localinstall kernel-3.10.0-957.1.3.bug15570.plus.el7.x86_64.rpm > yum -y localinstall kernel-devel-3.10.0-957.1.3.bug15570.plus.el7.x86_64.rpm > > However, the bug lists seem to refer only to issues with VirtualBox. I > have experienced the same symptom when installing on a "hardware" system > (no hypervisor). The same commands above also provide a workaround here, > but thought the flag should be raised for CentOS and RHEL that it doesn't > seem to be just VBOX. > > Perhaps the priority of this issue should be raised further up the pole > since I can't imagine it being a good experience for someone who doesn't > know how to dig through a problem like this. The average bear would > install something else and move on. > > In any case, thank you for the patch information. Look forward to a "real" > fix soon. Other than that I'm really liking CentOS 7. > > SG As noted in the CentOS bug report you referenced ( https://bugs.centos.org/view.php?id=15570 ), I filed a report upstream ( https://bugzilla.redhat.com/show_bug.cgi?id=1658669, marked private). In that RHBZ, they were able to reproduce it without VirtualBox. Therefore they are aware this is not just a VBox problem. The fix has been added to kernel-3.10.0-984.el7, meaning it will be in the EL 7.7 kernel. Now there is a separate RHBZ for "Z-Stream" for the same issue. This means that the fix will be ported to the current series (EL 7.6). Unfortunately I have no access to this BZ, so cannot tell the progress there. Once it is fixed in RHEL, CentOS will inherit it. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Yum refuses to install kmod-8188eu from elrepo
On Tue, Jan 22, 2019 at 10:49 AM Jonathan Billings wrote: > > On Tue, Jan 22, 2019 at 12:03:22PM -0500, Mike Burger wrote: > > Another alternative may be to pull down the SRPM and run it through rpmbuild > > to locally create a binary package compatible with the system as it's > > currently installed/running. > > I encourage this behavior, however, elrepo kmod packages often have > the kernel version hard-coded into it, so you'd need to either edit > the .spec file, or run rpmbuild with a > > --define 'kversion 3.10.0-957.1.3.el7.x86_64' > > to force it to build against the latest el7 kernel. Well, I wouldn't call it "hard-coded', but yes, if the kernel version is not defined from the command line, then whatever the version defined in the spec file is used. :) By the way, the updated package is now in the elrepo testing repository, e.g. https://elrepo.org/linux/testing/el7/x86_64/RPMS/kmod-8188eu-4.1.4_6773.20130222-5.el7_6.elrepo.x86_64.rpm Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Yum refuses to install kmod-8188eu from elrepo
On Tue, Jan 22, 2019 at 8:01 AM Akemi Yagi wrote: > > On Tue, Jan 22, 2019 at 7:54 AM Marko Vojinovic wrote: > > What is the best way to resolve this? Is there some kernel package > > somewhere that matches these properties, or is there some other package > > that provides these features to an existing kernel, or something else? > > That output indicates that that kmod package is built for the EL 7.5 > kernel and is not compatible with the current kernel. I suggest you > file a request to have the kmod-8188eu rebuilt for EL 7.6 at > http://elrepo.org/bugs/ . Users seeing the same issue can now go to: https://elrepo.org/bugs/view.php?id=893 Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Yum refuses to install kmod-8188eu from elrepo
On Tue, Jan 22, 2019 at 7:54 AM Marko Vojinovic wrote: > > > I am having trouble using the realtek wifi chip in my new tp-link > usb wifi dongle. Upon plugging it, the device gets registered by the > kernel (in /var/log/messages), but that's about it, no network device > is being created (iwconfig does not see it, nothing else works). > > A few google searches later I found out that this realtek chip is not > supported by the kernel and requires a driver, and that the driver is > packaged for C7 as kmod-8188eu in elrepo. > > However, yum install kmod-8188eu refuses to install it (full yum > output is here: https://pastebin.com/raw/vvak6FCU ), complaining that > the following dependencies cannot be met: > > --> Processing Dependency: kernel(wireless_send_event) = 0xa02e7e03 for > package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 > --> Processing Dependency: kernel(usb_submit_urb) = 0x74c6ac58 for > package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 > --> Processing Dependency: kernel(usb_reset_device) = 0xddd0084e for > package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 > --> Processing Dependency: kernel(usb_put_dev) = 0xf709107c for > package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 > --> Processing Dependency: kernel(usb_kill_urb) = 0xa55bf715 for > package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 > --> Processing Dependency: kernel(usb_get_dev) = 0x372a41af for > package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 > --> Processing Dependency: kernel(usb_free_urb) = 0x739aecf4 for > package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 > --> Processing Dependency: kernel(usb_control_msg) = 0xd04e3a9e for > package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 > --> Processing Dependency: kernel(usb_alloc_urb) = 0x12a4948e for > package: kmod-8188eu-4.1.4_6773.20130222-4.el7_5.elrepo.x86_64 > > I've never seen such output from yum before --- I'm guessing it is > asking for a kernel with specific "properties", and failing to find > one. > > What is the best way to resolve this? Is there some kernel package > somewhere that matches these properties, or is there some other package > that provides these features to an existing kernel, or something else? That output indicates that that kmod package is built for the EL 7.5 kernel and is not compatible with the current kernel. I suggest you file a request to have the kmod-8188eu rebuilt for EL 7.6 at http://elrepo.org/bugs/ . Akeme ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7.6 1810 vs. VirtualBox : bug with keyboard layout selection
On Fri, Jan 4, 2019 at 5:43 AM Jonathan Billings wrote: > > On Fri, Jan 04, 2019 at 09:42:55AM +0100, Nicolas Kovacs wrote: > > And I'm glad to begin chapter 2 of my Introduction To Linux with > > something like "Well, folks, unfortunately you can't select a custom > > keyboard layout in VirtualBox because the enterprise class Linux we > > talked about in chapter 1 has a bug in the kernel so for now the default > > keyboard layout will have to be sufficient. > > I suppose this shows you how little Red Hat cares about using > VirtualBox (product by their competition). > > If I were running a VM on a linux system, I'd probably use > KVM/qemu/libvirt. I'm sure that was exhaustively tested. You guys are overreacting. :) The bug was in a patch applied to the upstream (kernel.org) kernel version 4.17. Therefore any distribution running this kernel was affected -- including Fedora and SuSE. Red Hat backports upstream patches and this particular one was one of them. By the way, there is a nicely written article about VirtualBox at RH: https://developers.redhat.com/products/rhel/hello-world/#virtualbox along with other VM technologies. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7.6 1810 vs. VirtualBox : bug with keyboard layout selection
On Thu, Jan 3, 2019 at 11:53 PM Nicolas Kovacs wrote: > > Hi, > > I'm currently working on my next Linux book, which will be an elementary > course about CentOS administration. I'm using VirtualBox for all the > installer screenshots. > > Since CentOS has recently been upgraded to version 7.6, I thought I > might as well base all book references on this version. So I downloaded > the 7.6 1810 minimal ISO and started a fresh installation in VirtualBox. > > I'm using a Swiss French keyboard layout (ch-fr or fr_CH-latin1), so one > of the first things I do in the installer is replace the default French > AZERTY keyboard (since I use the french language) by a swiss french > QWERTZ layout. > > Now when I reach this dialog in the installer and try do define my new > layout, the slider in the selection window doesn't appear, and clicking > on any of the first layouts doesn't do anything, so I'm basically stuck > there. > > I'm running OpenSUSE Leap 15.0 KDE on my workstation, so I tried the > same thing with the previous CentOS 7.5 1804 minimal ISO, and the > keyboard selection dialog works perfectly. > > So my intuition would tell me that there's a nasty bug in the CentOS 7.6 > installer. Maybe it went unnoticed, since most folks stick to the > default keyboard layout selected in their language. > > Any suggestions ? > > Cheers, > > Niki There are known issues with VirtualBox and RHEL (therefore CentOS) 7.6. (1) https://forums.virtualbox.org/viewtopic.php?f=3&t=90103 (2) https://forums.virtualbox.org/viewtopic.php?f=3&t=90267 (1) is about the GuestAdditions, so this should not affect the installation. But you were most likely hit by (2). All the details are in that forum thread. In short, this is caused by a bug in the 7.6 kernel (see also https://bugs.centos.org/view.php?id=15570 ). It is possible that the next update to the kernel has the fix but this remains to be seen. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] ZFS fails with C7 957
On Thu, Dec 6, 2018 at 3:23 PM Jonathan Billings wrote: > > On Dec 6, 2018, at 17:45, david wrote: > > > > Folks > > > > I have two USB connected drives, configured as a mirrored-pair in ZFS. > > It's been working fine UNTIL I updated Centos > > from 3.10.0-862.14.4.el7.x86_64 > > to 3.10.0-957.1.3.el7.x86_64 > > > > The import of the pools didn't happen at boot. When I tried executing: > > zpool list > > I got the diagnostic suggesting I do /sbin/modprobe zfs > > And that command claimed the module didn't exist. > > You need to go wherever you got your ZFS kernel module and rebuild it for the > kernel included in CentOS 7.6.1810. I had to rebuild several of my kmods for > the -957 kernels too. If you use a kmod that relies on kernel symbols that > are not on the kabi whitelist, you need to rebuild the kmod for every minor > release, and probably several times mid release. If you get the ZFS from the zfs.repo, they just published the EL7.6 package: https://github.com/zfsonlinux/zfs/wiki/RHEL-and-CentOS Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CR repo update disaster for my desktop.
On Wed, Dec 5, 2018 at 12:38 AM Rob Kampen wrote: > > On 5/12/18 7:21 AM, Phil Perry wrote: > > The only issue I've seen reported that sounds similar or possibly > > related is: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1650634 > Yes, seems this is the laptop issue, will prove tomorrow. > > > > There is a patch in that bug you might like to try. > Not too keen on this, would need to find a detailed howto as I have not > done any rebuilds for a number of years. I presume that RH will at some > point release a fix for this? The submitter of RHBZ 1650634 is a developer of Scientific Linux. The xorg packages in SL 7.6 have been published with the referenced patch applied. If you so wish, you could install their packages. ftp://linux1.fnal.gov/linux/scientific/7.6/x86_64/updates/security/ Note the "sl7" tag instead of "el7". Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [External] Re: CentOS 7 package not present in Red Hat EL 7 - qt-assistant
On Wed, Nov 28, 2018 at 1:00 AM Toralf Lund wrote: > > On 28/11/18 01:24, Akemi Yagi wrote: > > The qt-assistant package is available in RHEL-7: > > > > $ sudo yum list qt-assistant > > > > qt-assistant.x86_64 1:4.8.7-2.el7rhel-7-server-optional-rpms > Right. I notice the word "optional" here - I guess this is where some of > the confusion comes from, as the Red Hat doc mentioned above does not > say anything about optional packages, it just mentions base and > "supplementary" channels. Evidently, optional rpms are not enabled on > the system mentioned earlier... > > Also, this must mean that CentOS "base" is not the same as Red Hat > "base". Right? > > - Toralf Please note that there are multiple Red Hat subscriptions. Workstation is one of them. CentOS builds all the packages made publicly available through git.centos.org. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 package not present in Red Hat EL 7 - qt-assistant
On Tue, Nov 27, 2018 at 5:47 AM Toralf Lund wrote: > > I'm using CentOS 7 for development of software that is sometimes used on > Red Hat Enterprise Linux 7. I conjunction with an update of one of the > applications, I asked some Red Hat users to install the Qt 4 Assistant > application via the qt-assistant package (which is used by a "help" > function in our software.) It seemed like there was no such package in > the Red Hat package set, however, and I also see no mention of it in > "package manifests" like > https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/package_manifest/chap-base-workstation-variant. > Yet I can install the package from the "base" repository on my CentOS > machine. > > Questions: Isn't CentOS base supposed to contain exactly the same > packages as Red Hat Enterprise, except in some special cases that relate > to distribution information, installation sources etc.? Does anyone know > what's going on with the specific package I mention above? > > - Toralf The qt-assistant package is available in RHEL-7: $ sudo yum list qt-assistant qt-assistant.x86_64 1:4.8.7-2.el7rhel-7-server-optional-rpms Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CONFIG_RTC_SYSTOHC not set for CentOS kernels
On Thu, Nov 15, 2018 at 9:31 AM Anand Buddhdev wrote: > > On 15/11/2018 18:09, Phil Perry wrote: > > Hi Phil, > > >> Does anyone know why this option is not enabled for CentOS kernels? > > > > Because it is not enabled on RHEL kernels. > > Heh, okay, that's an easy explanation. > > I'll try to open a bug report in RedHat's bugzilla, and see if they give > me any attention. > > Regards, > Anand In addition to that, you have an option to ask CentOS to have it enabled in the centosplus kernel. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Fresh install C7 nvidia
On Wed, Nov 7, 2018 at 5:36 PM Jerry Geis wrote: > > I am install C7.5 on a nvidia unit and nvidia-detect tells me to use > kmod-nvidia-390xx > so I do the yum install and and after a long time I see this > > -> Processing Dependency: kernel(__drm_atomic_helper_crtc_duplicate_state) > = 0xa5f3a170 for package: kmod-nvidia-390xx-390.87-2.el7_6.elrepo.x86_64 > --> Processing Dependency: kernel(__drm_atomic_helper_crtc_destroy_state) = > 0x00a9c70b for package: kmod-nvidia-390xx-390.87-2.el7_6.elrepo.x86_64 > --> Processing Dependency: kernel(__check_object_size) = 0x88db9f48 for > package: kmod-nvidia-390xx-390.87-2.el7_6.elrepo.x86_64 > --> Processing Dependency: kernel(___ratelimit) = 0x155f4108 for package: > kmod-nvidia-390xx-390.87-2.el7_6.elrepo.x86_64 > --> Processing Dependency: kernel >= 3.10.0-957.el7 for package: > kmod-nvidia-390xx-390.87-2.el7_6.elrepo.x86_64 > ---> Package nvidia-x11-drv-390xx.x86_64 0:390.87-1.el7_5.elrepo will be > installed > > Packages skipped because of dependency problems: > kmod-nvidia-390xx-390.87-2.el7_6.elrepo.x86_64 from elrepo > nvidia-x11-drv-390xx-390.87-1.el7_5.elrepo.x86_64 from elrepo > > I have also tried --skip-broken and get the same result as above. > > have I missed something ? This has always working in the past. > Thanks, > > Jerry I suggest you join the elrepo mailing list. You'll find the following posts, for example: http://lists.elrepo.org/pipermail/elrepo/2018-October/004523.html http://lists.elrepo.org/pipermail/elrepo/2018-November/004529.html http://lists.elrepo.org/pipermail/elrepo/2018-November/004531.html Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Frefox update from firefox-60.2.0-1.el7.centos.x86_64 to 60.2.1-1.el7.centos.x86_64 lost master password
On Wed, Oct 3, 2018 at 9:19 AM Stephen John Smoogen wrote: > It would seem that the problem is with upstream-upstream's (aka > Firefox) cleaning up of items that are not supposed to be there after > Firefox 58 > > https://bugzilla.mozilla.org/show_bug.cgi?id=1475775 > > It looks like it is deleting files it thinks should have been > converted to a newer more secure version.. but don't seem to be for > some reason. I am not sure if those files will just removed again > every time you restore them. That link added to the related RHBZ: https://bugzilla.redhat.com/show_bug.cgi?id=1633932 Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CVE-2018-14634 and kernel-debuginfo ?
On Tue, Sep 25, 2018 at 11:48 AM Zube wrote: > > The current mitigation for CVE-2018-14634 is a systemtap script > mentioned here: > > https://access.redhat.com/security/cve/cve-2018-14634 > > It also mentions that one can build a kernel module to distribute > to other machines, but in any case one needs the corresponding > debuginfo packages to do either. > > After enabling CentOS-Debug.repo, what I get is: > > kernel-debuginfo-2.6.32-754.3.5.el6.centos.plus.x86_64 > > which doesn't match, since I'm not running the centos.plus kernel, > so the systemtap script fails (tested only on CentOS 6 for the moment). > > Is there some way to get kernel-debuginfo-2.6.32-754.3.5.el6.x86_64? > > Thanks for any help. > > Cheers, > Zube You can find it here: http://debuginfo.centos.org/6/x86_64/ Because yum thinks the centos.plus version is newer, you'd need to manually download and install it. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kernel-plus (plus 1?)
On Fri, Aug 24, 2018 at 4:53 AM lejeczek via CentOS wrote: > > On 23/08/18 18:44, Akemi Yagi wrote: > > On Thu, Aug 23, 2018 at 10:42 AM lejeczek via CentOS > > wrote: > >> hi guys > >> > >> did you notice, if you use kernel-plus on 7.5 this > >> > >> CentOS Linux (3.10.0-862.11.6.el7.centos.plus.1.x86_64) 7 (Core) > >> CentOS Linux (3.10.0-862.11.6.el7.centos.plus.x86_64) 7 (Core) > >> > >> is that "plus.1" a new naming convention or just one off? > > It has a bug fix for the IPoIB issue: > > > > https://bugs.centos.org/view.php?id=15193 > > > > Akemi > > I wish guys kept changelog always updated and consistent so when the > rest of us do rpm -q --changelog then we know right away everything and > do not need to bother each other with mundane question like that one of > mine, nor search for answers. 'rpm -q --changelog' shows: * Mon Aug 20 2018 Akemi Yagi [3.10.0-862.11.6.el7.centos.plus.1] - Add omg.patch to fix broken IPoIB, submitted by pgreco [bug#15193] Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kernel-plus (plus 1?)
On Thu, Aug 23, 2018 at 10:42 AM lejeczek via CentOS wrote: > > hi guys > > did you notice, if you use kernel-plus on 7.5 this > > CentOS Linux (3.10.0-862.11.6.el7.centos.plus.1.x86_64) 7 (Core) > CentOS Linux (3.10.0-862.11.6.el7.centos.plus.x86_64) 7 (Core) > > is that "plus.1" a new naming convention or just one off? It has a bug fix for the IPoIB issue: https://bugs.centos.org/view.php?id=15193 Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CVE-2018-0495 Libgcrypt Vulnerability Fix for CentOS 6?
On Tue, Jul 31, 2018 at 10:29 PM, nschehovin--- via CentOS wrote: > Is there a schedule for fixing CVE-2018-0495 Libgcrypt Vulnerability for > CentOS 6? > > I can not find a patch for this CVE. Please point me in the right direction > if I am missing something. > > Thanks, > Ed You can check the status upstream: https://access.redhat.com/security/cve/cve-2018-0495 Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Passwords in plain text
On Fri, Jun 15, 2018 at 3:18 PM, Richard wrote: > >> Date: Friday, June 15, 2018 14:55:21 -0700 >> From: Akemi Yagi >> I also received the "has been disabled" notification. It looks like >> users with gmail addresses are affected. >> >> CentOS admins are looking into this issue (I believe). >> >> Akemi > > I believe this is a DMARC issue. Yahoo, among other places, has set > their dmarc records to p=reject: > > dig +short txt _dmarc.yahoo.com > "v=DMARC1; p=reject; pct=100; rua=mailto:dmarc_y_...@yahoo.com;"; > > So, if your mail hosting provider enforces dmarc,(gmail does) and you > get mail from a list that doesn't rewrite the headers, and people > from places like yahoo post to the list, you'll likely get some form > of warning about being being kicked off the mailing list every now > and then. The frequency depends on how often people from p=reject > places post, and what the settings are for bounce handling of the > mailing list in question. > > I believe that the current version of mailman can be configured to do > the necessary header rewrites. Some lists I'm on only do the rewrites > for headers of posts coming from p=reject sites (much less annoying > than having them all rewritten). I was thinking the same except I do not have enough knowledge in this area. In gmail's header I often see DMARK "Fail" Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Passwords in plain text
On Fri, Jun 15, 2018 at 9:57 AM, Gianluca Cecchi wrote: > > Il Ven 15 Giu 2018, 18:45 Larry Martell ha > scritto: > >> On Fri, Jun 15, 2018 at 12:41 PM rj coleman wrote: >> >> > Am I the only one who just received this email from this group? Which >> > came with my password in the email in plain text? >> > > Your membership in the mailing list CentOS has been disabled due to >> > > excessive bounces The last bounce received from you was dated >> > > 15-Jun-2018. You will not get any more messages from this list until >> > > you re-enable your membership. You will receive 3 more reminders like >> > > this before your membership in the list is deleted. >> > > >> I got it as well. >> > Mee too I also received the "has been disabled" notification. It looks like users with gmail addresses are affected. CentOS admins are looking into this issue (I believe). Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Update announcement request - correction...
On Fri, May 25, 2018 at 9:32 AM, Albert McCann wrote: >> Related to that, a new kernel was released to the Centosplus repo, kernel- >> plus-3.10.0-862.2.3.el7.centos.plus, but perf and python-perf were not >> updated for the new kernel. Is this an oversight? perf doesn't complain >> about mismatched versions though. > > "kernel-plus-3.10.0-862.3.2.el7.centos.plus" not ".2.3.". > > Al McCann I confirm that perf and python-perf for the latest kernel-plus are missing. I suppose Johnny will take care of it soon. Regarding the announcement of the plus kernel, I think there has been no such request so far. But if this is useful/helpful to the plus kernel users, I think it should be implemented. Johnny? Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Samba HOWTO wiki bug: chcon samba_share_t
On Fri, May 4, 2018 at 3:11 PM, Louis Lagendijk wrote: > On Fri, 2018-05-04 at 14:55 -0700, Akemi Yagi wrote: >> On Fri, May 4, 2018 at 2:26 PM, Warren Young >> wrote: >> > On May 4, 2018, at 3:03 PM, Akemi Yagi wrote: >> > > >> > > On Fri, May 4, 2018 at 12:03 PM, Warren Young > > > > wrote: >> > > > >> > > >$ sudo chcon -R -t samba_share_t /path/to/share >> > > >> > > Updated the page as suggested. Thanks. >> > >> > Thanks! >> > >> > I now see another instance of this in section 3. Instead of >> > copying the text verbatim, it should probably be: >> > >> > chcon -R -t samba_share_t /mnt/data >> > >> > …in order to match the text above it. >> >> Warren, >> >> I was just informed that the chcon command your suggested was >> originally there, but it was replaced with the 2 line version >> sometime >> ago. The reason given was "Replace chcon by semanage/restorecon pair >> to survive filesystem relabel". > > The comment is correct: chcon will not survive a relabel. You need to > update the database first (semanage fcontext) and then let a relabel > apply the new context. > > Louis Thanks for the input. Reverted the change. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Samba HOWTO wiki bug: chcon samba_share_t
On Fri, May 4, 2018 at 2:26 PM, Warren Young wrote: > On May 4, 2018, at 3:03 PM, Akemi Yagi wrote: >> >> On Fri, May 4, 2018 at 12:03 PM, Warren Young wrote: >>> >>>$ sudo chcon -R -t samba_share_t /path/to/share >> >> Updated the page as suggested. Thanks. > > Thanks! > > I now see another instance of this in section 3. Instead of copying the text > verbatim, it should probably be: > > chcon -R -t samba_share_t /mnt/data > > …in order to match the text above it. Warren, I was just informed that the chcon command your suggested was originally there, but it was replaced with the 2 line version sometime ago. The reason given was "Replace chcon by semanage/restorecon pair to survive filesystem relabel". What do you think? Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Samba HOWTO wiki bug: chcon samba_share_t
On Fri, May 4, 2018 at 12:03 PM, Warren Young wrote: > In this wiki article: > >https://wiki.centos.org/HowTos/SetUpSamba > > …there is a command down in section 2 that gives an error here on CentOS 7: > > $ sudo semanage fcontext –at samba_share_t /path/to/share > …noise noise noise… > semanage: error: unrecognized arguments: samba_share_t /path/to/share > > That and the following restorecon command can be replaced by a single shorter > command, which also fixes the symptom: > > $ sudo chcon -R -t samba_share_t /path/to/share Updated the page as suggested. Thanks. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problem with Digikam and libgphoto2 after latest update
On Tue, May 1, 2018 at 8:25 AM, Nicolas Kovacs wrote: > > There's a similar problem with gthumb and exiv2. This is a known issue and there is a workaround: https://bugzilla.redhat.com/show_bug.cgi?id=1568618 https://access.redhat.com/discussions/3414821 Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Nvidia-detect error with on HP Z4 (CentOS 6.9)
On Fri, Apr 13, 2018 at 8:21 AM, Danny Smit wrote: > Hi all, > > I'm testing an installation of nvidia drivers on a HP Z4 workstation > (nvidia Quadro P600) with CentOS 6.9. Running nvidia-detect with this > setup gives the following output: > > # nvidia-detect > Error getting device_class > > nvidia-detect also quits with exit-code 255. > Could this be a bug in nvidia-detect? Or is it an unsupported configuration? > > The following hardware is detected, it seems some sort of unknown > Intel device is detected by the OS: > > # lspci | grep VGA > 00:1f.5 Non-VGA unclassified device: Intel Corporation Device a2a4 > 21:00.0 VGA compatible controller: NVIDIA Corporation Device 1cb2 (rev a1) > > # lspci -n | egrep '00:1f.5|21:00.0' > 00:1f.5 : 8086:a2a4 > 21:00.0 0300: 10de:1cb2 (rev a1) > > Tested with the following version (with equal results): > > nvidia-detect-390.25-1.el6.elrepo.x86_64.rpm > nvidia-detect-390.48-1.el6.elrepo.x86_64.rpm > > -- > Regards, > Danny You want to post this to the elrepo mailing list. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 6 i386 - meltdown and spectre
On Mon, Mar 12, 2018 at 1:15 PM, Peter Wood wrote: > Awesome. Thank you. > > Embarrassing but I can't find the Q&A page with this question. Can you > please post a link to it. > > Thanks, > > -- Peter Here it is: https://access.redhat.com/articles/3327321 ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 6 i386 - meltdown and spectre
On Fri, Mar 9, 2018 at 10:46 AM, Peter Wood wrote: > Anyway, I'm stuck with a few 32bit systems exposed to customers and I have > to come up with an answer to their question about meltdown/spectre. At this > point all I can say is that Red Hat hasn't patched 32bit systems but that > is hard to believe so I assumed that I'm wrong and decided to ask the > community. According to a Q&A page about Meltdown and Spectre: Question - Is the patch available for 32 bit RHEL 6.9? Answer - 32-bit patches are pending, being of lower priority than our RHEL 5 work at this time. Apparently, it is not getting a high priority. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] what is the centos/elrepo policy toward LTS kernels?
On Fri, Feb 23, 2018 at 12:30 AM, Robert P. J. Day wrote: > > i'm sure there's a simple answer to this -- i already understand > that newer kernels than the ones shipped with the official release > aren't officially supported but there is the elrepo kernel repository > here: > > http://elrepo.org/linux/kernel/el7/x86_64/RPMS/ > > with a mixture of long-term (lt) and mainline (ml) kernels. i assume > that the mainline kernels pretty closely track the latest kernel > release but that's not the one i'm interested in. > > if i was interested in the additional longevity of the LTS kernels, > i can see that 4.4 is available. but the most recent LTS kernel was > 4.14, was it not? so why is a 4.14 "lt" kernel not available in that > repository? > > i am obviously unclear on the policy used to determine which kernel > versions end up in that repository. > > rday You want to ask elrepo-related questions on the elrepo mailing list. But here's the post that would answer your question: http://lists.elrepo.org/pipermail/elrepo/2018-February/004120.html Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] A question about NBD kernel module...
On Mon, Feb 12, 2018 at 7:59 AM, Raghuram Devarakonda wrote: > Hi, > > I would like to mount a device using NBD protocol on CentOS 7 but it looks > like the module is not available by default in the kernel. Is there a way I > can install it (like from a rpm somewhere)? I found instructions to build > such a module but want to make sure that it is not already available in > some repo before I go ahead with building. > > Any help is greatly appreciated. You can do one (or both) of the following: (1) File a request on http://bugs.centos.org and ask that CONFIG_BLK_DEV_NBD be enabled in the centosplus kernel. (2) File a request on http://elrepo.org/bugs and ask for a driver (kmod package) for that. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kmod c74 broken: howto report it
On Tue, Jan 2, 2018 at 10:10 AM, Akemi Yagi wrote: > > On Thu, Dec 7, 2017 at 6:23 AM, Stijn De Weirdt > wrote: >> latest kmod update 20-15.el7_4.6 is broken on our systems, while >> previous 20-15.el7_4.4 was working fine (and downgrading fixes the issue). >> >> the issue is with modules from mellanox kmod rpms that are symlinked in >> the weak-updates dir. the config files in /etc/depmod.d look ok (and do >> work with previous version): dist.conf has weak-updates after built-in, >> and mellanox kmod rpms ship a config that overrides it for all modules. > A little late in getting back to your post ... > > This issue was reported upstream at RH and is being worked on: > > https://bugzilla.redhat.com/show_bug.cgi?id=1522994 > > Hopefully the fixed version comes out soon. For the record, it was fixed in kmod-20-15.el7_4.7 : https://access.redhat.com/errata/RHBA-2018:0159 Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Update to 3.10.0-693.17.1 breaks ath5k
On Fri, Feb 2, 2018 at 10:57 PM, Stephen Davies wrote: > Where can I find a suitable module or even source code to build here? > > (Centos 7) ELRepo used to provide the kmod-ath5k package. However, the module does not compile under EL7.4 due to the change in the wireless stack. If your device needs ath5k, give ELRepo's kernel-lt a try. The module is enabled in this kernel. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS Linux 7 (1708) AltArch i386 Kernel
On Tue, Jan 9, 2018 at 10:15 AM, Akemi Yagi wrote: > On Tue, Jan 9, 2018 at 10:09 AM, Johnny Hughes wrote: > >> Red Hat no longer maintains the i386 kernel for RHEL 7.4. We have been >> using a modified kernel until this latest meltdown / spectre release >> (*kernel-3.10.0-693.11.6.el7*). >> >> This latest release does not build on i386/i686 and we can't figure out >> how to make it work. >> >> Build try: >> https://buildlogs.centos.org/c7.1708.u.i386/kernel/201801091 >> 71431/3.10.0-693.11.6.el7.centos.plus.i386/ >> >> SRPM: >> http://people.centos.org/hughesjr/kernel-3.10.0-693.11.6. >> el7.centos.plus.src.rpm >> >> We could use some community help in: >> >> 1. Making the 3.10.0-693.11.6.el7.centos.plus.i386 build. >> >> Please post info on this thread in the mailing list >> > > Or you can upload patch(es) to this bug report: > > https://bugs.centos.org/view.php?id=14353 > > Thanks to kabe who offered a patch, a test version of the centos-plus kernel for i686 is available here: https://people.centos.org/toracat/kernel/7/plus/i386/ Feedback welcome. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS Linux 7 (1708) AltArch i386 Kernel
On Tue, Jan 9, 2018 at 10:09 AM, Johnny Hughes wrote: > Red Hat no longer maintains the i386 kernel for RHEL 7.4. We have been > using a modified kernel until this latest meltdown / spectre release > (*kernel-3.10.0-693.11.6.el7*). > > This latest release does not build on i386/i686 and we can't figure out > how to make it work. > > Build try: > https://buildlogs.centos.org/c7.1708.u.i386/kernel/ > 20180109171431/3.10.0-693.11.6.el7.centos.plus.i386/ > > SRPM: > http://people.centos.org/hughesjr/kernel-3.10.0-693.11. > 6.el7.centos.plus.src.rpm > > In the mean time, people running the altarch i386 distribution can the > latest i386 experimental kernel .. use the repo file from here (bottom > of the page, 'CentOS-Experimental.repo' to '/etc/yum.repo.d/' ) to get it: > > https://wiki.centos.org/SpecialInterestGroup/AltArch/i386 > > We could use some community help in: > > 1. Making the 3.10.0-693.11.6.el7.centos.plus.i386 build. > > 2. Testing the 4.9.75.el7.centos.i686 kernel from the experimental repo > on the i386 arch. > > Please post info on this thread in the mailing list. > Or you can upload patch(es) to this bug report: https://bugs.centos.org/view.php?id=14353 Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7.4 fails to boot as Xen PV guest: resurfaces (now also) with centosplus kernel 693.11.6.el7
On Sun, Jan 7, 2018 at 12:07 PM, David Groep wrote: > Dear all, > > Maybe I'm the only one - so before filing it as a bug: it appears that > the latest set of kernel patches in 3.10.0-693.11.6.el7 makes issue > 0013763 "CentOS 7.4 kernel (3.10.0-693*) fails to boot as Xen PV guest" > re-surface *also* with the CentOS PLUS kernel. But maybe in a > different way ... > > Thanks to the (great!) quick work on making the plus kernel available > (in #14330, thanks for that!) I was able to test the following > combinations: > > - 3.10.0-693.11.6.el7.centos.plus works fine on XenServer 7 HVM guests > - 3.10.0-693.11.1.el7.centos.plus works fine on XenServer 7 XenPV guests > - 3.10.0-693.11.6.el7.centos.plus crashes on boot for XS7 XenPV guests > immediately after the boot stage where the PS/2 drivers are loaded > > Crashing does not depend on the amount of VM memory or #cores/sockets. > Also, the tell-tale "mm/vmalloc.c" failure output is no longer present. > The system 'just' crashes (with the kernel log lines as below) around the > time of the i8042 controller probing. > > Obviously the stock upstream 3.10.0-693.11.6.el7 crashes as well for > XS7 XenPV guests, but that was to be expected as per 0013763. > It crashes in the same way, around the time of the i8042 probes. > > Can anyone (maybe bill_mcgonigle?) reproduce the issue? > Did the KPTI patches break the XenPV fixes in CentOS Plus per 13763? > Or is this a new XenPV issue? > You may want to be watching the centos-virt mailing list. Xen-related issues are discussed there. This thread: https://lists.centos.org/pipermail/centos-virt/2018-January/005716.html has a response from Johnny Hughes with a possible solution. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] possible issue with nvidia and new patches?
On Thu, Jan 4, 2018 at 5:29 AM, John Hodrien wrote: > On Thu, 4 Jan 2018, Zube wrote: > > Twitter user stintel, in this thread: >> >> https://twitter.com/stintel/status/948499157282623488 >> >> mentions a possible problem with the new patches and the >> nvidia driver: >> >> "As if the @Intel bug isn't bad enough, #KPTI renders @nvidia driver >> incompatible due to GPL-only symbol 'cpu_tlbstate'. #epicfail" >> > > I've seen no obvious problems with kernel-3.10.0-693.11.6.el7.x86_64 and > nvidia-x11-drv-384.98-2.el7.elrepo.x86_64. > > This includes running under KVM with vfio passthrough. > > jh Apparently CentOS kernels are not affected. I don't see symbol cpu_tlbstate . Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kmod c74 broken: howto report it
On Thu, Dec 7, 2017 at 6:23 AM, Stijn De Weirdt wrote: > hi all, > > latest kmod update 20-15.el7_4.6 is broken on our systems, while > previous 20-15.el7_4.4 was working fine (and downgrading fixes the issue). > > the issue is with modules from mellanox kmod rpms that are symlinked in > the weak-updates dir. the config files in /etc/depmod.d look ok (and do > work with previous version): dist.conf has weak-updates after built-in, > and mellanox kmod rpms ship a config that overrides it for all modules. > > anyhow, before i try to get this upstream, how do i report this with > centos team (to make sure the centos kmod rpm was correctly build). > > (i have already asked here before how to properly report it, but can't > find my previous mail ;) > A little late in getting back to your post ... This issue was reported upstream at RH and is being worked on: https://bugzilla.redhat.com/show_bug.cgi?id=1522994 Hopefully the fixed version comes out soon. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Broadcom BCM4352 on Centos 7
On Thu, Dec 14, 2017 at 6:59 AM, Akemi Yagi wrote: > > Just wanted to add a note that you can use ELRepo's drivers with > SecureBoot enabled if you so wish. > Here's how: > > http://elrepo.org/tiki/SecureBootKey > Yet another comment. Sorry, the above note is a general one. The self-built kmod-wl package does not have the SB key signed by ELRepo. This note has been added to our wiki page. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Broadcom BCM4352 on Centos 7
On Thu, Dec 14, 2017 at 6:59 AM, Akemi Yagi wrote: > On Thu, Dec 14, 2017 at 5:39 AM, Gary Stainburn > wrote: > >> After getting nowhere with the mokutil command I decided to use the other >> option and turn off secure boot in the BIOS settings. >> >> I had been loathed to do this because every time I do anything in the >> BIOS it >> stuffs the boot order and reverts to booting straight into Win8. Guess >> what, >> as soon as I turned off secure boot it did exactly that. Turnng secure >> boot >> back on made no difference. >> >> Thankfully, the mailing list archives for this list still contain the >> instructions on how to fix it. >> >> For those interested, it involved pressing F9 at boot time to select the >> boot >> menu and selecting the Centos option. This then went through GRUB as >> normal >> and booted. I then used 'eftbootmgr -o' to define the correct boot >> sequence. >> >> The upshot is that I now have a laptop that boots correctly, and that >> successfully uses the built in Broadcom WiFi adaptor. >> >> Thanks everyone for your help >> > > Glad to hear things are now working for you. > > Just wanted to add a note that you can use ELRepo's drivers with > SecureBoot enabled if you so wish. > Here's how: > > > http://elrepo.org/tiki/SecureBootKey > > Akemi > > Another [important] note if you are running CentOS 7.4. There is an issue with the current version of shim in CentOS 7.4. The details can be found here: https://bugs.centos.org/view.php?id=14050 Follow the workaround in that bug report. Hope the problem gets fixed soon by CentOS devs. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Broadcom BCM4352 on Centos 7
On Thu, Dec 14, 2017 at 5:39 AM, Gary Stainburn wrote: > After getting nowhere with the mokutil command I decided to use the other > option and turn off secure boot in the BIOS settings. > > I had been loathed to do this because every time I do anything in the BIOS > it > stuffs the boot order and reverts to booting straight into Win8. Guess > what, > as soon as I turned off secure boot it did exactly that. Turnng secure boot > back on made no difference. > > Thankfully, the mailing list archives for this list still contain the > instructions on how to fix it. > > For those interested, it involved pressing F9 at boot time to select the > boot > menu and selecting the Centos option. This then went through GRUB as normal > and booted. I then used 'eftbootmgr -o' to define the correct boot > sequence. > > The upshot is that I now have a laptop that boots correctly, and that > successfully uses the built in Broadcom WiFi adaptor. > > Thanks everyone for your help > Glad to hear things are now working for you. Just wanted to add a note that you can use ELRepo's drivers with SecureBoot enabled if you so wish. Here's how: http://elrepo.org/tiki/SecureBootKey Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Broadcom BCM4352 on Centos 7
On Mon, Dec 11, 2017 at 2:14 AM, Gary Stainburn wrote: > Hi Folks > > I'm trying to get my internal WiFi working and I'm following the > instructions > here: > > https://wiki.centos.org/HowTos/Laptops/Wireless/Broadcom > > My adaptor is: > > [gary@gary ~]$ lspci|grep Broad > 08:00.0 Network controller: Broadcom Limited BCM4352 802.11ac Wireless > Network > Adapter (rev 03) > [gary@gary ~]$ > > However, I've failed at step 2 as I cannot find any Linux / STA / WL > drivers > when I search the support page linked. > > Can anyone suggest how I can fix this, or suggest another web page I can > follow? > As far as I know, the contents on the CentOS wiki are for CentOS 7.3 (or earlier) and a patch is needed to use the driver under 7.4. You may want to go to the ELRepo article that is referenced on that page ( http://elrepo.org/tiki/wl-kmod ). The ELRepo instructions are up to date and should cover EL7.4. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kmod-jfs on Centos 6
On Thu, Oct 26, 2017 at 5:22 PM, H wrote: > On 10/26/2017 08:01 PM, Akemi Yagi wrote: > > On Thu, Oct 26, 2017 at 4:17 PM, H wrote: > > > >> On October 26, 2017 6:31:04 PM EDT, Akemi Yagi > wrote: > >>> On Thu, Oct 26, 2017 at 3:11 PM, H wrote: > >>> > >>> We will update the bug report ( > >>> http://elrepo.org/bugs/view.php?id=728 ) > >>> when the updated version is ready. > >>> > >>> Akemi > >> Where does one see which kernel version the release is intended for? I > >> should add that I installed it from elrepo earlier today on a current > >> computer, not some time ago... No error messages. > >> > > Try the following command on a computer you had kmod-jfs installed: > > > > $ ls -l `find /lib/modules -name jfs.ko` > > > > It will show where the module was installed (in the extra/ directory) and > > may show symbolic links to other kernel versions (if any) that are > > compatible. > > > > In the case of the kmod-jfs package, there was a kABI breakage when going > > from el7.3 to el7.4. As a result, what was built against el7.3 was broken > > in el7.4. It has now been built against the el7.4 kernel. This one is not > > backward compatible with earlier (< 7.4) kernels. > > > > Akemi > > I tried the above and this is the output: > > lrwxrwxrwx. 1 root root 51 Oct 26 17:56 /lib/modules/3.10.0-514.21.2. > el7.x86_64/weak-updates/jfs/jfs.ko -> /lib/modules/3.10.0-514.el7. > x86_64/extra/jfs/jfs.ko > lrwxrwxrwx. 1 root root 51 Oct 26 17:56 /lib/modules/3.10.0-514.26.1. > el7.x86_64/weak-updates/jfs/jfs.ko -> /lib/modules/3.10.0-514.el7. > x86_64/extra/jfs/jfs.ko > lrwxrwxrwx. 1 root root 51 Oct 26 17:56 /lib/modules/3.10.0-514.26.2. > el7.x86_64/weak-updates/jfs/jfs.ko -> /lib/modules/3.10.0-514.el7. > x86_64/extra/jfs/jfs.ko > -rw-r--r--. 1 root root 302480 Apr 16 2017 /lib/modules/3.10.0-514.el7. > x86_64/extra/jfs/jfs.ko > The output shows that the version of the installed kmod-jfs is for kernel-3.10.0-514.el7.x86_64 and is compatible with all -514 kernels (el7.3). I also ran yum update again but it did not pick up kmod-jfs although it was > just updated. How long time does it typically take for an updated package > to become available? > It is syncing to mirrors. It may show up any time between now and several hours later. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kmod-jfs on Centos 6
On Thu, Oct 26, 2017 at 4:17 PM, H wrote: > On October 26, 2017 6:31:04 PM EDT, Akemi Yagi wrote: > >On Thu, Oct 26, 2017 at 3:11 PM, H wrote: > > > >> On 04/18/2017 12:54 PM, H wrote: > >> > A couple of days ago I submitted a request to ElRepo and kmod-jfs > >is > >> now available for CentOS 7 as well. > >> > > >> > >> Did not have a need to mount a JFS disk on my CentOS 7 system until > >today > >> and it does not want to be mounted, instead complaining "unknown > >filesystem > >> type 'jfs'". I do have kmod-jfs installed. > >> > >> The commandline I use is: > >> > >> mount -t "jfs" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdb1" > >/mnt/share > >> > >> I am doing this as root and /mnt/share has been created for the root > >user. > >> > >> What am I doing wrong? Does anyone have JFS volumes mounted under > >CentOS 7? > >> > > > >The kmod-jfs package needs to be rebuilt against the EL7.4 kernel. > > > >We will update the bug report ( > >http://elrepo.org/bugs/view.php?id=728 ) > >when the updated version is ready. > > > >Akemi > > Where does one see which kernel version the release is intended for? I > should add that I installed it from elrepo earlier today on a current > computer, not some time ago... No error messages. > Try the following command on a computer you had kmod-jfs installed: $ ls -l `find /lib/modules -name jfs.ko` It will show where the module was installed (in the extra/ directory) and may show symbolic links to other kernel versions (if any) that are compatible. In the case of the kmod-jfs package, there was a kABI breakage when going from el7.3 to el7.4. As a result, what was built against el7.3 was broken in el7.4. It has now been built against the el7.4 kernel. This one is not backward compatible with earlier (< 7.4) kernels. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kmod-jfs on Centos 6
On Thu, Oct 26, 2017 at 3:11 PM, H wrote: > On 04/18/2017 12:54 PM, H wrote: > > A couple of days ago I submitted a request to ElRepo and kmod-jfs is > now available for CentOS 7 as well. > > > > Did not have a need to mount a JFS disk on my CentOS 7 system until today > and it does not want to be mounted, instead complaining "unknown filesystem > type 'jfs'". I do have kmod-jfs installed. > > The commandline I use is: > > mount -t "jfs" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdb1" /mnt/share > > I am doing this as root and /mnt/share has been created for the root user. > > What am I doing wrong? Does anyone have JFS volumes mounted under CentOS 7? > The kmod-jfs package needs to be rebuilt against the EL7.4 kernel. We will update the bug report ( http://elrepo.org/bugs/view.php?id=728 ) when the updated version is ready. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] workaround using CentOS Plus Kernel? -- for 7.4 does not support PV [Xen]
On Sun, Sep 17, 2017 at 7:54 AM, wrote: > Relates to: https://prgmr.com/blog/2017/09/14/centos-7-pv-unsupported.html > > I'm considering switching to the **CentOS Plus Kernel**. What are the > downsides? > In the link above, will the CentOS Plus Kernel get upgraded or will it be > locked > at a specific kernel? > The CentOSPlus kernel is updated whenever the distro kernel gets updated. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Update to 7.4 using DVD
On Wed, Sep 13, 2017 at 8:21 PM, Lamar Owen wrote: > On 09/13/2017 04:40 PM, Jerry Geis wrote: > >> I am running the propriatry NVIDIA driver 384.69 for GT 720 support. >> > The ELrepo driver works very well for me with CentOS 7.4.1708 on a Dell > Precision M6700. Here's what I have: > ++ > [lowen@localhost ~]$ nvidia-detect -v > Probing for supported NVIDIA devices... > [10de:11be] NVIDIA Corporation GK104GLM [Quadro K3000M] > This device requires the current 384.59 NVIDIA driver kmod-nvidia > [lowen@localhost ~]$ rpm -qa|grep nvidia > nvidia-x11-drv-384.69-2.el7.elrepo.x86_64 > nvidia-detect-384.59-1.el7.elrepo.x86_64 > yum-plugin-nvidia-1.0.2-1.el7.elrepo.noarch > pcp-pmda-nvidia-gpu-3.11.8-7.el7.x86_64 > kmod-nvidia-384.69-1.el7_4.elrepo.x86_64 > [lowen@localhost ~]$ > > (nvidia-detect hasn't yet been updated to .69..) The ELrepo team does > a great job with this driver; unless you have a compelling need to rebuild > it yourself (I hesitate to say 'recompile' as, well, there's very little to > actually compile) you should investigate using the ELrepo.org modules that > make these sorts of updates much easier. Thanks ELrepo for the modules; > thanks CentOS project for the rebuilt OS. > > The ELrepo nvidia driver handles the nouveau disabling as well; it's > seamless, and works. The only caveat is when your card goes to the legacy > driver, at which time you'll have to install the legacy version; ELrepo > builds those too. Right, and one other aspect of ELRepo's kmod package is that it survives kernel updates silently. With Nvidia's script, you need to run it upon every kernel update. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Update to 7.4 using DVD
On Wed, Sep 13, 2017 at 2:00 PM, Johnny Hughes wrote: > On 09/13/2017 03:40 PM, Jerry Geis wrote: > > I am running the propriatry NVIDIA driver 384.69 for GT 720 support. > > If you installed it directly from nvidia, you would need to boot to > runlevel 3 and rerun the NVIDIA*.run script to build against the new > kernel. > > If you are using the one from elrepo, not sure if they have a new one yet. > Just to make a minor note ... ELRepo updated the kmod-nvidia (and related) package s as soon as RHEL 7.4 came out. :-) Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Problem installing glibc-devel.i686 on CentOS 7
On Mon, Aug 28, 2017 at 8:16 AM, Alfred von Campe wrote: > The following transcript should provide all the necessary details: > > # yum install glibc-devel-2.17-157.el7.i686 > Loaded plugins: fastestmirror, langpacks > Loading mirror speeds from cached hostfile > * base: mirrors.gigenet.com > * epel: mirrors.xmission.com > * extras: mirrors.gigenet.com > * updates: ftp.osuosl.org > Resolving Dependencies > --> Running transaction check > ---> Package glibc-devel.i686 0:2.17-157.el7 will be installed > --> Processing Dependency: glibc-headers = 2.17-157.el7 for package: > glibc-devel-2.17-157.el7.i686 > --> Processing Dependency: glibc = 2.17-157.el7 for package: > glibc-devel-2.17-157.el7.i686 > --> Finished Dependency Resolution > > You could try using --skip-broken to work around the problem > You could try running: rpm -Va --nofiles --nodigest > > I tried the two suggesting above to no avail. Has anyone else been able > to install glib-devel.i686 successfully on CentOS 7? > > It is actually glibc-devel-2.17-157.el7_3.5.i686. So you either provide the whole name or just use glibc-devel.i686 for the yum command. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Upstream details at...
On Mon, Jul 3, 2017 at 10:15 AM, Stuart Barkley wrote: > On Fri, 30 Jun 2017 at 08:00 -, centos-announce-requ...@centos.org wrote: > >> Upstream details at : https://rhn.redhat.com/errata/RHBA-2017-1609.html The following page refers to the same RHBA: https://access.redhat.com/errata/RHBA-2017:1609 which will not go away for some time ... Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] installer with centosplus kernel?
On Thu, Jun 22, 2017 at 2:36 PM, Keith Keller wrote: > Hi all, > > Is there any way to get a CentOS 7 ISO with the centosplus kernel? I > have some very old hardware I'd like to keep going if easy, but it has > old NVidia network cards that need the forcedeth driver. Apparently > this driver is now in the centosplus kernel, but if I use the default > ISO I won't be able to get on the network to get the centosplus kernel. > (Of course I can get the kernel to the machine in other ways, but over > the network is by far the most convenient.) > > See https://bugs.centos.org/view.php?id=7359 for more details. I've > done other web searches but found nothing more specific than this link. One other possibility is to ask ELRepo to provide a driver disk for the forcedeth driver. Then you'll be able to do the install using the dd= option. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] [SOLVED] using autofs on C-7
On Fri, Jun 9, 2017 at 12:54 PM, Fred Smith wrote: > On Fri, Jun 09, 2017 at 01:58:25PM -0400, Fred Smith wrote: >> > Your current setup does not agree with the instructions. May I suggest >> > you follow the example in the wiki exactly as it is written? If you >> > confirm that works, you can replace the name etc to fit your >> > situation. >> > >> > Akemi >> >> Akemi: >> >> thanks for the reply! >> >> I was struggling with the instructions because some things are not >> defined, and left to the reader to figure out. Not blaming you, all the >> other instructions I saw have the same issue. but if, for example, there >> was a clear statement of how/where the name of the local mount point >> was defined I might have gotten it right, but as it is I had to guess. >> >> But I'll go do what you suggest and see what happens. >> >> thanks again! >> > > OK, I've got it working, and Akemi's suggestion helped me figure it out. > > This is in /etc/auto.master: > > /mnt /etc/auto.mnt > > and this is in /etc/auto.mnt: > > # > # mounts public and home shares on the NasBox. > # > . syno-public > -fstype=cifs,rw,credentials=/root/.smbcred,defaults,uid=fredex,gid=fredex,noauto,users,exec,vers=3.0 > ://nasbox/public > > syno-fredex > -fstype=cifs,rw,credentials=/root/.smbcred,defaults,uid=fredex,gid=fredex,noauto,users,exec,vers=3.0 > ://nasbox/home > > trying to access /mnt/syno-fredex, then, mounts my home directory on the > Nasbox there, and access of /mnt/syno-public mounts the public share from > the Nasbox there. > > It all makes sense now. > > thanks Akemi! > > PS, would it be worth documenting the systemd automount feature in the > same wiki article? Glad to hear you've got it working. Sure, your contribution to the wiki article is much appreciated. :) Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] using autofs on C-7
On Fri, Jun 9, 2017 at 6:18 AM, Fred Smith wrote: > On Fri, Jun 09, 2017 at 08:25:31AM -0400, Jonathan Billings wrote: >> On Thu, Jun 08, 2017 at 04:02:05PM -0700, Kenneth Porter wrote: >> > Automounting is now done through systemd. >> >> In my use, we continue to use autofs for automounts of CIFS volumes, >> because as best I can tell, systemd doesn't support using the >> request-key infrastructure to use a user's kerberos ticket to set up >> the automount. > > Glad to know it still works. > > Could any of you look back at my first post and give me a hint > what I'm doing wrong? (I can repost if necessary.) Your current setup does not agree with the instructions. May I suggest you follow the example in the wiki exactly as it is written? If you confirm that works, you can replace the name etc to fit your situation. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] SCSI drives and Centos 7
On Sun, Apr 30, 2017 at 1:03 PM, Gregory P. Ennis wrote: > Thanks for your help. I did not want to replace this machine with new > equipment, but it looks like I may need to do just that. > > Here are the results with respect to the lsi raid board for : > > lspci -nn > > > 02:01.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID > [1000:1960] (rev 01) > 02:02.0 SCSI storage controller [0100]: Adaptec AIC-7902B U320 [9005:801d] > (rev 10) > 02:02.1 SCSI storage controller [0100]: Adaptec AIC-7902B U320 [9005:801d] > (rev 10) The driver for your device LSI Logic / Symbios Logic MegaRAID [1000:1960] is disabled in the CentOS kernel (C6 and C7). # CONFIG_MEGARAID_LEGACY is not set You'd need a driver disk with the required driver to install CentOS on your system. My suggestion is that you ask ELRepo to offer such a disk by filing an RFE at http://elrepo.org/bugs . Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kmod-jfs on Centos 6
On Tue, Apr 11, 2017 at 3:58 PM, H wrote: > On 3/13/2017 1:09 PM, Nux! wrote: >> >> yum -y install >> http://mirrors.coreix.net/elrepo/elrepo/el6/x86_64/RPMS/kmod-jfs-0.0-1.el6.elrepo.x86_64.rpm >> >> (that's for 64bit, adjust the url accordingly for 32bit) >> >> it won't hose your system >> Nux! > Thank you, installed it and it worked fine. Now I am looking for the same > for CentOS 7... It did not look like you have that in your repository? You may want to file an RFE (request for enhancement) at http://elrepo.org/bugs . Another option is to use the CentOSPlus kernel (kernel-plus). This kernel has the jfs kernel module enabled. It is available from CentOS (for example, http://mirrors.coreix.net/centos/7/centosplus/ ). Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] New C7 kernel ABI and kmods
On Fri, Mar 3, 2017 at 12:03 PM, Akemi Yagi wrote: > On Fri, Mar 3, 2017 at 9:16 AM, Lamar Owen wrote: >> All, >> >> This is just a heads-up that the new C7 update kernel breaks ABI >> compatibility, at least as far as using the ELrepo nVidia drivers is >> concerned. I have posted more details to the ELrepo list; but since many >> folks use the Elrepo kmods I thought a heads-up would be appropriate. >> >> If you use the ELrepo nvidia kmod you will either need to hold off on the >> kernel update or uninstall the nvidia kmod. > > This is being tracked here: > > https://elrepo.org/bugs/view.php?id=720 The kmod-nvidia packages (legacy packages too) against the latest EL7.3 kernel (3.10.0-514.10.2.el7) have been released to the main repository and are syncing to the mirrors. kmod-nvidia-304xx-304.135-2.el7.elrepo.x86_64.rpm kmod-nvidia-340xx-340.102-2.el7.elrepo.x86_64.rpm kmod-nvidia-375.39-2.el7.elrepo.x86_64.rpm These packages will not be compatible with earlier kernel releases. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] New C7 kernel ABI and kmods
On Fri, Mar 3, 2017 at 9:16 AM, Lamar Owen wrote: > All, > > This is just a heads-up that the new C7 update kernel breaks ABI > compatibility, at least as far as using the ELrepo nVidia drivers is > concerned. I have posted more details to the ELrepo list; but since many > folks use the Elrepo kmods I thought a heads-up would be appropriate. > > If you use the ELrepo nvidia kmod you will either need to hold off on the > kernel update or uninstall the nvidia kmod. This is being tracked here: https://elrepo.org/bugs/view.php?id=720 Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Looking for latest C7 kernel-plus SRPM
On Fri, Dec 16, 2016 at 12:12 PM, Ian Pilcher wrote: > Where can I find the SRPM for the latest C7 kernel-plus package, i.e. > kernel-plus-3.10.0-514.2.2.el7.centos.plus.x86_64? > > http://vault.centos.org/7.3.1611/centosplus/Source/SPackages/ is empty. It is there now. Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kmod-nvidia problems
On Sat, Dec 10, 2016 at 12:21 PM, Rob Kampen wrote: > Hi List, > > I use the kmod-nvidia package on my CentOS workstations. > > Always this has "just worked". > > Doing a yum update this morning I now get this: > > > 09:15:28 : ERROR: Package: kmod-nvidia-367.57-2.el7.elrepo.x86_64 (elrepo) > Requires: kernel(drm_atomic_helper_plane_reset) = 0xabd4c98d > Installed: kernel-3.10.0-327.28.2.el7.x86_64 (@updates) > kernel(drm_atomic_helper_plane_reset) = 0xb23805db > Anyone else get this? any pointers? > TIA > Rob Later versions of kmod-nvidia are for EL7.3 (not backward compatible). You need to update your CentOS system using the CR repo. Or wait until the full release of CentOS 7.3.1611 (next week?). Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] linux-3.10.0-514.el7.tar.xz - process of creation
On Fri, Nov 25, 2016 at 9:13 AM, Alexander Dalloz wrote: > Am 25.11.2016 um 15:03 schrieb Staazul: >> >> I try to create own patch for kernel, and I look in process of >> generation binary rpm file. >> As I can see, for creation binary package, rpmbuild doesn't uses any set >> of patches and doesn't uses file of original (vanilla) version of >> kernel. Instead it, I see some xz archive of compressed tree of kernel >> probably with all changes (linux-3.10.0-514.el7.tar.xz). How and where I >> can find process of creation of this archive and to see separately all >> set of patches? I want to remove some changes and add own. >> >> Many thanks to all, who have such info and can give link on process or >> link on documentations of process of creation of this archive. >> >> best regards, Andrei > > > You cannot easily bisect the kernel tarball provided. Some time ago Red Hat > had dediced to use this way of prividing the sources of their kernel because > well knowns had started an aggressive business to hijack RHEL customers. > > See i.e. > https://linux.slashdot.org/story/11/03/04/1550231/red-hat-stops-shipping-kernel-changes-as-patches > > Alexander That article is not quite accurate. As I noted in my earlier post, the patches are available. As a RHEL subscriber, I can see and search them: https://access.redhat.com/articles/1130403 I would be surprised if no one at Oracle can afford to pay for an entitlement. ;) Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Recent updates for CentOS7?
On Fri, Nov 25, 2016 at 8:55 AM, Albert McCann wrote: >> -Original Message- >> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Johnny Hughes >> Sent: Friday, November 25, 2016 10:13 AM >> To: centos@centos.org >> Subject: Re: [CentOS] Recent updates for CentOS7? > > >> Then we will commence work on the OS tree and ISOs. Historically, this >> takes 10-21 days for the full tree and ISOs .. but except for the >> exceptions listed above, all the packages will be in CR. >> >> Thanks, >> Johnny Hughes > > Johnny, > > Thank you, and all the others, for all the hard work. My family photos > website wouldn't be possible without it. > > I have a question, what about the Plus kernel, when will that get updated? I've submitted the source rpm to Johnny. It is now up to him to find the time to build them. :-) Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] linux-3.10.0-514.el7.tar.xz - process of creation
On Fri, Nov 25, 2016 at 6:03 AM, Staazul wrote: > I try to create own patch for kernel, and I look in process of > generation binary rpm file. > As I can see, for creation binary package, rpmbuild doesn't uses any set > of patches and doesn't uses file of original (vanilla) version of > kernel. Instead it, I see some xz archive of compressed tree of kernel > probably with all changes (linux-3.10.0-514.el7.tar.xz). How and where I > can find process of creation of this archive and to see separately all > set of patches? I want to remove some changes and add own. > > Many thanks to all, who have such info and can give link on process or > link on documentations of process of creation of this archive. The individual kernel patches are available to RHEL subscribers. No public access though. Do you really need to see them to create your patches? Can't you just look at the code and figure out the changes you'd like to make? Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CVE-2016-5195 DirtyCOW : Critical Linux Kernel Flaw
On Tue, Oct 25, 2016 at 10:26 AM, Leon Fauster
wrote:
> Am 25.10.2016 um 15:39 schrieb Peter Kjellström :
>> On Tue, 25 Oct 2016 10:06:12 +0200
>> Christian Anthon wrote:
>>
>>> What is the best approach on centos 6 to mitigate the problem is
>>> officially patched? As far as I can tell Centos 6 is vulnerable to
>>> attacks using ptrace.
>>
>> I can confirm that c6 is vulnerable, we're running a patched kernel
>> (local build) using a rhel6 adaptation of the upstream fix.
>>
>> Ask off-list if you want an src.rpm
>
>
> Hi Peter, can you confirm that its this?
>
> http://pastebin.centos.org/56391/
That is for the EL-7.2 kernel. Peter was offering a patch for CentOS 6.
RH released the patched kernel for EL-6.8 today. I have attached the
diff file between 2.6.32-642.6.1.el6 and 2.6.32-642.6.2.el6. It is
more complex because the 6 kernel is older, so required more mods, I
suppose. Maybe that was the reason why the EL-6 update took longer
than EL-7.
Akemi
diff -uNpr linux-2.6.32-642.6.1.el6/include/linux/mm.h
linux-2.6.32-642.6.2.el6/include/linux/mm.h
--- linux-2.6.32-642.6.1.el6/include/linux/mm.h 2016-08-25 08:07:47.0
-0700
+++ linux-2.6.32-642.6.2.el6/include/linux/mm.h 2016-10-24 06:19:16.0
-0700
@@ -1420,6 +1420,7 @@ struct page *follow_page(struct vm_area_
#define FOLL_HWPOISON 0x100 /* check page is hwpoisoned */
#define FOLL_NUMA 0x200 /* force NUMA hinting page fault */
#define FOLL_MIGRATION 0x400 /* wait for page to replace migration entry */
+#define FOLL_COW 0x4000 /* internal GUP flag */
typedef int (*pte_fn_t)(pte_t *pte, pgtable_t token, unsigned long addr,
void *data);
diff -uNpr linux-2.6.32-642.6.1.el6/mm/memory.c
linux-2.6.32-642.6.2.el6/mm/memory.c
--- linux-2.6.32-642.6.1.el6/mm/memory.c2016-08-25 08:06:57.0
-0700
+++ linux-2.6.32-642.6.2.el6/mm/memory.c2016-10-24 06:19:16.0
-0700
@@ -1177,6 +1177,24 @@ int zap_vma_ptes(struct vm_area_struct *
}
EXPORT_SYMBOL_GPL(zap_vma_ptes);
+static inline bool can_follow_write_pte(pte_t pte, struct page *page,
+ unsigned int flags)
+{
+ if (pte_write(pte))
+ return true;
+
+ /*
+* Make sure that we are really following CoWed page. We do not really
+* have to care about exclusiveness of the page because we only want
+* to ensure that once COWed page hasn't disappeared in the meantime
+* or it hasn't been merged to a KSM page.
+*/
+ if ((flags & FOLL_FORCE) && (flags & FOLL_COW))
+ return page && PageAnon(page) && !PageKsm(page);
+
+ return false;
+}
+
/*
* Do a quick page-table lookup for a single page.
*/
@@ -1266,10 +1284,11 @@ split_fallthrough:
migration_entry_wait(mm, pmd, address);
goto split_fallthrough;
}
- if ((flags & FOLL_WRITE) && !pte_write(pte))
- goto unlock;
-
page = vm_normal_page(vma, address, pte);
+ if ((flags & FOLL_WRITE) && !can_follow_write_pte(pte, page, flags)) {
+ pte_unmap_unlock(ptep, ptl);
+ return NULL;
+ }
if (unlikely(!page)) {
if ((flags & FOLL_DUMP) ||
!is_zero_pfn(pte_pfn(pte)))
@@ -1290,7 +1309,6 @@ split_fallthrough:
*/
mark_page_accessed(page);
}
-unlock:
pte_unmap_unlock(ptep, ptl);
out:
return page;
@@ -1489,17 +1507,13 @@ int __get_user_pages(struct task_struct
* The VM_FAULT_WRITE bit tells us that
* do_wp_page has broken COW when necessary,
* even if maybe_mkwrite decided not to set
-* pte_write. We can thus safely do subsequent
-* page lookups as if they were reads. But only
-* do so when looping for pte_write is futile:
-* in some cases userspace may also be wanting
-* to write to the gotten user page, which a
-* read fault here might prevent (a readonly
-* page might get reCOWed by userspace write).
+* pte_write. We cannot simply drop FOLL_WRITE
+* here because the COWed page might be gone by
+* the time we do the subsequent page lookups.
*/
if ((ret & VM_FAULT_WRITE) &&
!(vma->vm_flags & VM_WRITE))
- foll_flags &= ~FOLL_WRITE;
+ foll_flags |= FOLL_COW;
cond_resched();
}
_
Re: [CentOS] C6 Firefox 45.1 segmentation faults
On Wed, May 4, 2016 at 9:57 AM, Nux! wrote: > That's because it's not in the testing repo, it's in the main one. :-) > > Make sure the main repo is enabled and perhaps run yum with --noplugins to > make rule out other stuff. My bad. Since the main repo is enabled by default, I thought it was ON. I apparently must have disabled it at some point. All is well now. The "crash" site no longer crashes. Will continue testing. Thanks a bunch! Akemi ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
