similar to: rpmbuild how to know we are building kernel module package

Displaying 20 results from an estimated 400 matches similar to: "rpmbuild how to know we are building kernel module package"

2018 Jun 03
0
encoding argument of source() in 3.5.0
Looks like this actually comes from readLines(), nothing to do with source() as such: In current R-devel (still): > f <- file("http://home.versanet.de/~s-berman/source2.R", encoding="UTF-8") > readLines(f) character(0) > close(f) > f <- file("http://home.versanet.de/~s-berman/source2.R") > readLines(f) [1] "source.test2 <- function()
2016 Nov 05
3
Avago (LSI) SAS-3 controller, poor performance on CentOS 7
I have a handful of new systems where I've seen unexpectedly low disk performance on an Avago SAS controller, when using CentOS 7. It looked like a regression, so I installed CentOS 6 on one of them and reloaded CentOS 7 on the other. Immediately after install, a difference is apparent in the RAID rebuild speed. The CentOS 6 system is initializing its software RAID5 array at somewhere
2019 Apr 12
0
rpmbuild how to know we are building kernel module package
On 4/12/19 7:04 AM, wuzhouhui wrote: > So my question is rpmbuild how to know he is building kernel module package? > Based on which condition? I believe the %kernel_module_package macro defined in /usr/lib/rpm/redhat/macros is used to invoke /usr/lib/rpm/redhat/kmodtool, which provides some overrides.
2018 Jun 04
3
encoding argument of source() in 3.5.0
>>>>> peter dalgaard >>>>> on Sun, 3 Jun 2018 23:51:24 +0200 writes: > Looks like this actually comes from readLines(), nothing > to do with source() as such: In current R-devel (still): >> f <- file("http://home.versanet.de/~s-berman/source2.R", encoding="UTF-8") >> readLines(f) > character(0)
2017 May 17
0
4.9 kernel fails to boot because it didn't have the mpt3sas module
On 05/16/2017 09:04 PM, Jerry wrote: <snip> > > Turns out dracut was unable to mount the root file system. So I went back > into the 3.10 kernel again to see if the mpt2sas or mpt3sas driver was in > its initramfs file... and it wasn't: > > > $ sudo lsinitrd -k 4.9.25-27.el7.x86_64 | grep mpt > -rw-r--r-- 1 root root 0 May 16 12:39
2017 May 17
2
4.9 kernel fails to boot because it didn't have the mpt3sas module
On Wed, May 17, 2017 at 10:07 AM, Sarah Newman <srn at prgmr.com> wrote: > On 05/16/2017 09:04 PM, Jerry wrote: > <snip> > > > > Turns out dracut was unable to mount the root file system. So I went > back > > into the 3.10 kernel again to see if the mpt2sas or mpt3sas driver was in > > its initramfs file... and it wasn't: > > > > >
2002 Jan 04
2
Strange problem from "identical" hosts
Long post.. sorry. Ok.. I've got three systems, all running openssh-3.0.2p1. As a matter of fact, they were installed from the same built tree, so I know they are the same. Here's the deal. I've got three systems, call them source1, source2 and target. All are HP-UX 11.0 systems installed from the same tree. Source1 and source2 both have thier root rsa pub keys in target's
2018 Jun 05
0
encoding argument of source() in 3.5.0
Thanks for the report, fixed in R-devel (74848). Best Tomas On 06/04/2018 02:41 PM, NELSON, Michael wrote: > > On R 3.5.0 (Mac) > > The issue appears when using the default (libcurl) method and specifying the encoding > > Note that using method='internal' causes a segfault if used in conjunction with encoding. (and works when encoding is not set) > > urlR <-
2018 Jun 04
0
encoding argument of source() in 3.5.0
On Mon, 4 Jun 2018 10:44:11 +0200 Martin Maechler <maechler at stat.math.ethz.ch> wrote: >>>>>> peter dalgaard >>>>>> on Sun, 3 Jun 2018 23:51:24 +0200 writes: > > > Looks like this actually comes from readLines(), nothing > > to do with source() as such: In current R-devel (still): > > >> f <-
2018 Jun 04
2
encoding argument of source() in 3.5.0
On R 3.5.0 (Mac) The issue appears when using the default (libcurl) method and specifying the encoding Note that using method='internal' causes a segfault if used in conjunction with encoding. (and works when encoding is not set) urlR <- "http://home.versanet.de/~s-berman/source2.R" # works url_default <- url(urlR) scan(url_default, "") # Read 7 items # [1]
2019 Jan 15
2
Request for edit permission on HowTos/BuildingKernelModules
Hi CentOS Docs team, I am writing to request for updating the wiki page HowTos/BuildingKernelModules[1] Basically, the page need some love for more recent CentOS releases - in CentOS 7 if people use the in-distro /usr/lib/rpm/redhat/kmodtool the following command won't work rpmbuild -bb --target=`uname -m` --define 'kversion 3.10.0-862.el7' testkmod.spec Instead, people should use
2017 May 17
2
4.9 kernel fails to boot because it didn't have the mpt3sas module
Howdy, I hit a snag trying to install Xen4CentOS on a Supermicro based system (X9DRD-7LN4F with the Broadcom/LSI 2308 chipset). I spent a few hours on this today, I'm posting this here in case it helps anyone else and saves them the frustration I dealt with. On this system I did a fresh install of CentOS 7, updated it, rebooted it, then installed Xen. The system was booting fine using the
2018 Jun 02
2
encoding argument of source() in 3.5.0
In R 3.5.0 using the `encoding' argument of source() prevents loading files from the internet; without the `encoding' argument files can be loaded from the internet, but if they contain non-ascii characters, these are not correctly displayed under MS-Windows (but they are correctly displayed under GNU/Linux). With R 3.4.{2,3,4} there is no such problem: using `encoding' the files are
2014 Jul 30
0
[PATCH libdrm] configure: Support symbol visibility when available
From: Thierry Reding <treding at nvidia.com> Checks whether or not the compiler supports the -fvisibility option. If so it sets the VISIBILITY_CFLAGS variable which can be added to the per directory AM_CFLAGS where appropriate. By default all symbols will be hidden via the VISIBILITY_CFLAGS. The drm_public macro can be used to mark symbols that should be exported. Signed-off-by: Thierry
2014 Jul 30
0
[PATCH libdrm] configure: Support symbol visibility when available
On 30/07/14 15:31, Rob Clark wrote: > On Wed, Jul 30, 2014 at 9:48 AM, Thierry Reding > <thierry.reding at gmail.com> wrote: >> From: Thierry Reding <treding at nvidia.com> >> >> Checks whether or not the compiler supports the -fvisibility option. If >> so it sets the VISIBILITY_CFLAGS variable which can be added to the per >> directory AM_CFLAGS
2014 Jul 30
2
[PATCH libdrm] configure: Support symbol visibility when available
On Wed, Jul 30, 2014 at 9:48 AM, Thierry Reding <thierry.reding at gmail.com> wrote: > From: Thierry Reding <treding at nvidia.com> > > Checks whether or not the compiler supports the -fvisibility option. If > so it sets the VISIBILITY_CFLAGS variable which can be added to the per > directory AM_CFLAGS where appropriate. > > By default all symbols will be hidden
2016 Sep 28
0
CEEA-2016:1930 CentOS 7 mpt3sas Enhancement Update
CentOS Errata and Enhancement Advisory 2016:1930 Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-1930.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: d14458a2bca348a99df8dcdf0b1ecceec16e7c5a85e3cd87fe2aa7b5b1df3a44 kmod-mpt3sas-13.100.00.00-1.el7_2.x86_64.rpm Source:
2017 Mar 08
0
CEEA-2017:0458 CentOS 7 kmod-redhat-mpt3sas Enhancement Update
CentOS Errata and Enhancement Advisory 2017:0458 Upstream details at : https://rhn.redhat.com/errata/RHEA-2017-0458.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 5d5fd5d8ca7d36045da7cf51014ef923cf0e7ff482f99fa745d5b81babd54d86 kmod-redhat-mpt3sas-14.101.00.00-1.el7_3.x86_64.rpm Source:
2020 Sep 20
1
CentOS 8 LSI SAS2004 Driver
On 20/09/2020 04:16, Akemi Yagi wrote: > On Sat, Sep 19, 2020 at 8:04 PM William Markuske <wmarkuske at gmail.com> 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
2019 Oct 02
2
CentOS 8 Broken Installation
On 10/2/19 9:47 PM, Jonathan Billings wrote: > On Oct 2, 2019, at 3:39 PM, Ljubomir Ljubojevic <centos at plnet.rs> wrote: >> Richard on CentOS-devel mailing list has similar problem but suggests it >> might be issue only with CentOS, he says he had to add the kernel line >> to make it work. >> Name of the tread is: >> [CentOS-devel] Booting CentOS 8 in a VM