similar to: How to blacklist a device driver (sysemd)

On 11/15/2017 07:50 PM, Gordon Messmer wrote: > On 11/15/2017 10:35 AM, Frank Thommen wrote: >> >> I tried with the files >> /etc/modprobe.d/blacklist >> /etc/modprobe.d/blacklist.conf >> and with entries >> blacklist mlx5_core >> blacklist mlx5_ib > > The "blacklist" entries prevent a module being loaded by its alias >

Frank Thommen wrote: > ** WARNING: This mail is from an external source ** > > > Hi, > > how can a specific device driver in CentOS 7 be blacklisted, so that it > doesn't load at boot time?? We have Infiniband adapters which are not > completely supported by CentOS and we want to silence the error messages > for the time being. > > I tried with the files

On 11/15/2017 10:35 AM, Frank Thommen wrote: > > I tried with the files > ? /etc/modprobe.d/blacklist > ? /etc/modprobe.d/blacklist.conf > and with entries > ? blacklist mlx5_core > ? blacklist mlx5_ib The "blacklist" entries prevent a module being loaded by its alias (typically a PCI ID), but not from being loaded if something explicitly loads it by module

From: Leon Romanovsky <leonro at nvidia.com> Changelog: v1: * Renamed _mlx5_rescan_driver to be mlx5_rescan_driver_locked like in other parts of the mlx5 driver. * Renamed MLX5_INTERFACE_PROTOCOL_VDPA to tbe MLX5_INTERFACE_PROTOCOL_VNET as a preparation to coming series from Eli C. * Some small naming renames in mlx5_vdpa. * Refactored adev index code to make Parav's SF series

Hi, Sometimes, I found one of my Mellanox NIC renamed to rename6, instead of eth1. The right names of NICs in my system should be: eth0 Mellanox NIC eth1 Mellanox NIC eth2 Intel NIC eth3 Intel NIC eth4 Intel NIC eth5 Intel NIC eth0 and eth1 will combined as bond1 with mode 4. However, the current names are: eth0 Mellanox

Hi, On Mon, May 15, 2017 at 03:04:03PM +0200, Frank Thommen wrote: > This problem still bites us. I've tried to play around with DHCP > settings (rd.net.timeout.dhcp, rd.net.dhcp.retry) to no avail. > > I'm happy about /any/ hint. 1) ip route seems ok, but what does your /etc/resolv.conf looks like? 2) could you try with 7.3.1611, 7.2.1511 is no longer supported. Tru >

Hi, kickstarting fails due to problems with host resolution, even though the network seems to be properly configured through DHCP. eno1 and eno2 are both attached to the network, but only eno1 gets an IP via DHCP. Still `curl` cannot resolve the mirror host and the kickstart host during dracut-initqueue: rdsosreport.txt ------------------------------------------------ [...] [ 14.780428]

Folks, Is there a limit on the quantity of IP''s you can ban in the blacklist file? Thanks, -MikeD

On 9/24/20 3:24 AM, Eli Cohen wrote: > On Thu, Sep 24, 2020 at 05:30:55AM -0400, Michael S. Tsirkin wrote: >>>> --- linux-next-20200917.orig/drivers/vdpa/Kconfig >>>> +++ linux-next-20200917/drivers/vdpa/Kconfig >>>> @@ -31,7 +31,7 @@ config IFCVF >>>> >>>> config MLX5_VDPA >>>> bool "MLX5 VDPA support library for

On 9/24/20 3:24 AM, Eli Cohen wrote: > On Thu, Sep 24, 2020 at 05:30:55AM -0400, Michael S. Tsirkin wrote: >>>> --- linux-next-20200917.orig/drivers/vdpa/Kconfig >>>> +++ linux-next-20200917/drivers/vdpa/Kconfig >>>> @@ -31,7 +31,7 @@ config IFCVF >>>> >>>> config MLX5_VDPA >>>> bool "MLX5 VDPA support library for

I'm setting up a new server on Centos 7, running x86_64. Motherboard is a MITAC PD11BICC, running Indian Bay Trail, with a i915 chipset. I installed "Server with GUI", but when it boots I get the "blank screen with a cursor" issue. Decided to see about disabling the i915 driver, by blacklisting it. but I don't think I have the right commands, as when I did that, it

Samba organizers might want to look into this: [ns1:~] dig 150.73.70.66.relays.osirusoft.com ; <<>> DiG 9.2.2 <<>> 150.73.70.66.relays.osirusoft.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28005 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 13 ;; QUESTION SECTION:

hey, I'm seeing an Oops when nouveau loads (see below). I've verified that this is because both device->chip and device->name are NULL prior to the strncpy()s at the end of nvkm_udevice_info(). Bisect shows that this started happening after: commit 24d5ff40a732633dceab68c6559ba723784f4a68 Author: Karol Herbst <kherbst at redhat.com> Date: Tue Apr 28 18:54:02 2020 +0200

Hi, Given the recent increase in SIP brute force attacks, I've had a little idea. The standard scripts that block after X attempts work well to prevent you actually being compromised, but once you've been 'found' then the attempts seem to keep coming for quite some time. Older versions of sipvicious don't appear to stop once you start sending un-reachables (or straight

I have NOUVEAU driver disabled however its "showing" in my X log file. [ 140.086] (II) NVIDIA dlloader X Driver 390.59 Wed May 9 21:30:06 PDT 2018 [ 140.086] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs [ 140.086] (II) NOUVEAU driver [ 140.087] (II) NOUVEAU driver for NVIDIA chipset families : [ 140.087] RIVA TNT (NV04) [ 140.087] RIVA TNT2

From: Randy Dunlap <rdunlap at infradead.org> drivers/vdpa/mlx5/ uses vhost_iotlb*() interfaces, so add a dependency on VHOST to eliminate build errors. ld: drivers/vdpa/mlx5/core/mr.o: in function `add_direct_chain': mr.c:(.text+0x106): undefined reference to `vhost_iotlb_itree_first' ld: mr.c:(.text+0x1cf): undefined reference to `vhost_iotlb_itree_next' ld:

From: Yonatan Maman <Ymaman at Nvidia.com> This patch series aims to enable Peer-to-Peer (P2P) DMA access in GPU-centric applications that utilize RDMA and private device pages. This enhancement is crucial for minimizing data transfer overhead by allowing the GPU to directly expose device private page data to devices such as NICs, eliminating the need to traverse system RAM, which is the

Hi, while kickstarting our virtual machines with PXE we often run into kickstart/anaconda failing with [...] [...] dracut-mount[xxx]: Warning: Can't mount root filesystem [...] dracut-mount[xxx]: Warning: /dev/root does not exist [...] dracut-mount[xxx]:/lib/dracut-lib.sh: line 1030: echo write error: No space left on device Starting Dracut Emergency Shell... Warning: /dev/root

In my blacklist I have: database show ... /blacklist/Manitoba : advertising ... [incoming] ; First, lets take care of telemarketers exten => 4,1,GotoIf(${BLACKLIST()}?blacklisted,s,1) exten => 4,n,Set(goaway=${CALLERID(number):0:2}) exten => 4,n,GotoIf($["${goaway}" = "V4" ]?blacklisted,s,1) exten => 4,n,GotoIf($["${goaway}" = "V3"

Hello All, I was wondering where does Asterisk stores the blacklist numbers? I looked into the dialplan and it shows that it *"Set(DB(blacklist/${blacknr})=1)"* the number... Does it save in MySQL DB? hyperion*CLI> show dialplan app-blacklist-add [ Context 'app-blacklist-add' created by 'pbx_config' ] '1' => 1.