similar to: kernel parm question: MPS? pcie_bus_safe

Phil Wyett wrote: > On Wed, 2016-03-23 at 09:20 -0400, m.roth at 5-cent.us wrote: >> Now, this is one we have an issue with: it's got a bttv card, and motion >> running on it. It's a Dell PE R720. For some reason, it has never liked >> the card: 20 min after reboot, it says fatal bus error... but nothing's >> wrong, and it runs just fine. Well, expect that we

On Wed, 2016-03-23 at 10:26 -0400, m.roth at 5-cent.us wrote: > Phil Wyett wrote: > > On Wed, 2016-03-23 at 09:20 -0400, m.roth at 5-cent.us wrote: > >> Now, this is one we have an issue with: it's got a bttv card, and motion > >> running on it. It's a Dell PE R720. For some reason, it has never liked > >> the card: 20 min after reboot, it says fatal bus

Got an older server running 6.5. I've been fighting it - I have two webcams for surveillance of the room; one works with motion, but it resizes the picture down Adjusting resolution from 640x480 to 360x296 and the video's dark and bad contrast. So I went back to the camer I'd been using before that worked fine... on CentOS 5.x, and then I remembered why I'd gone to the other camera

Now, this is one we have an issue with: it's got a bttv card, and motion running on it. It's a Dell PE R720. For some reason, it has never liked the card: 20 min after reboot, it says fatal bus error... but nothing's wrong, and it runs just fine. Well, expect that we need to keep it on the 2.6.32-431.20.3 kernel, because *everything* later, it randomly starts rebooting, several times a

Did nobody ever verify this for Ken? > On Mon, Oct 01, 2012 at 23:38:33 +0530, Desai, Kashyap wrote: > > > > > > > -----Original Message----- > > > From: owner-freebsd-stable at freebsd.org [mailto:owner-freebsd- > > > stable at freebsd.org] On Behalf Of Kenneth D. Merry > > > Sent: Monday, October 01, 2012 8:58 PM > > > To: John

John R Pierce wrote: > On 3/16/2017 11:12 AM, m.roth at 5-cent.us wrote: >> I'm still trying to find a video capture card that won't crash Dell >> servers, and ran across a Blackmagic BDLKDUO2 DeckLink Duo 2. It claims >> to support Linux. I'm also seeing, in the few non-Blabkmagic or sales >> pages I can find, that they like "binary blobs". I

We've got several secure rooms, with video surveillance 24x7. A few years ago, we got a couple of cards based on BT878 chips, which we use with the motion package. I've posted here about hardware issues... After a fair bit of testing, the cards just don't seem to be compatible with Dell rackmount server firmware. They work fine... on older Penguins, which are Supermicro. It's

I am trying to get a bt878 capture card working in Ubuntu 7.04 for a video surveillance application running on LAMP stack. It is based on Xen 3.0.3. Got all xm stuff working and apache/mysql/python working in domU. Now need access to /dev/Video0 I first tried pciback, where I get the following failure (from dom0 dmesg). (I blacklisted the bttv and related drivers). [ 0.198929] Kernel command

On Wed, 2016-03-23 at 09:20 -0400, m.roth at 5-cent.us wrote: > Now, this is one we have an issue with: it's got a bttv card, and motion > running on it. It's a Dell PE R720. For some reason, it has never liked > the card: 20 min after reboot, it says fatal bus error... but nothing's > wrong, and it runs just fine. Well, expect that we need to keep it on the >

I have 2 video devices LML33 and PV155 $ lspci 06:00.0 Multimedia video controller: Zoran Corporation ZR36057PQC Video cutting chipset (rev 02) 07:08.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11) 07:08.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11) 07:09.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture

Hi. I'm running the 9.1-RC1 release. At the end of the boot sequence, I see: mps0: mpssas_scsiio_timeout checking sc 0xffffff8000759000 cm 0xffffff8000784380 (probe19:mps0:0:19:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 length 0 SMID 240 command timeout cm 0xffffff8000784380 ccb 0xfffffe0006918000 mps0: mpssas_alloc_tm freezing simq mps0: timedout cm 0xffffff8000784380 allocated tm

While other aspects of the system configuration may still be controlled by the outcome of the table scan, if apic= was given on the command line its effect should not be overridden here. Signed-off-by: Jan Beulich <jbeulich@novell.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, folks, I'm still trying to find a video capture card that won't crash Dell servers, and ran across a Blackmagic BDLKDUO2 DeckLink Duo 2. It claims to support Linux. I'm also seeing, in the few non-Blabkmagic or sales pages I can find, that they like "binary blobs". I also haven't been able to find anything about o/s or library requirements. Has anyone run

---------------------------- Original Message ---------------------------- Subject: ipmitool and CentOS 7 From: m.roth at 5-cent.us Date: Mon, May 16, 2016 16:57 To: "CentOS" <centos at centos.org> -------------------------------------------------------------------------- On Dells running CentOS 6, we could use this command ipmitool delloem lcd set mode userdefined

Hallo *! I have a board SE7501HG2. - On 2.6.18 ipmitool works succefull. On Xen-3.1 (2.6.18) ipmitool say: # ipmitool sensor WARNING: Unknown SDR repository version 0x00 SDR record id 0x0000: invalid length 0 (see thread [ipmitool-devel] Unknown SDR version) - On page [4] as written: ipmitool -> BMC ---> i2c/smbus ''-> SDR - On Thread [9] was written:

Hi, I have updated the firmware for perc raid controller card, network card, IDRAC firmware and the BIOS version on Dell R720 server. I have installed CentOS 6.4 and updated with all the latest packages using yum -y update. # cat /var/log/messages | grep -i error Sep 23 14:09:35 x24 kernel: ERST: Error Record Serialization Table (ERST) support is initialized. Sep 23 14:09:35 x24 kernel: ACPI

Changing the vapply() behavior makes sense in principle. I analyzed the CRAN code base using the R parser and found 143 instances of calling vapply with USE.NAMES=FALSE. These would need to be inspected to understand the consequences of the change. For reference: /AzureML/R/datasets.R:226 /BBmisc/R/toRangeStr.R:33 /DBI/R/DBDriver.R:205 /Kmisc/R/str_rev.R:37 /Matrix/R/diagMatrix.R:98

Introduce and use a new inspect_mount_root function to mount all the mountpoints of a root in the guest, replacing the same code doing that in different tools. inspect_mount_root_ro is inspect_mount_root with readonly mount option. --- builder/builder.ml | 10 +--------- customize/customize_main.ml | 9 +-------- get-kernel/get_kernel.ml | 9 +--------

On Thu, Jul 12, 2018 at 07:27:58PM -0500, Chris Adams wrote: > > Default Gateway IP : 192.168.0.100 > > Default Gateway MAC : 00:25:90:0a:42:87 > > No, that does not look right. You have configured the gateway of the > IPMI to be the host OS side of the NIC. You can't do that... in a lot > of systems I've seen, the IPMI side of the NIC can't even

Dear R Community, I would like to announce the package "surveillance", which provides methods for the surveillance of count data time series originating from the routine collection of public health data. The package addresses epidemiologists and statisticians working with routine surveillance, but it also offers an infrastructure for developers of new detection algorithms. Implemented