similar to: making new initrd, how to do it?

All, I've posted here earlier regarding a kernel crash we were seeing on kernel 2.4.13, on our embedded hardware... We have recently upgraded to 2.4.16, and are still seeing crash issues. We are running Vanilla 2.4.16 (including some of our own device driver modules) on a PowerPC 7410, with the root partition being EXT3. We have a test which creates a EXT3 partition, coppeis /usr/bin to

Hi, I get a warning in the domU kernels when I pass-through the ehcu/uhci devices. The usb-ports seem to work. I can use usb-sticks and a sundtek DVB-C stick. A microsoft usb-mouse is not recognized. Can I ignore the warning or do I have some serious issue/misconfiguration? Dom0: xm info: host : luna release : 3.1.0-rc5+ version : #6 SMP Sat Sep

Hello, I noticed the default megaraid_sas driver version in upstream Linux 2.6.32.25 is pretty old, version 4.01, and it seems to be very buggy. It fails to bring up disks and boot fails. Many people have reported this issue on various hardware using LSI RAID adapters, and on various Dell servers (R310/R410/R510/R710) using Dell PERC H700 RAID adapters (which are rebranded LSI adapters).

Hello, I noticed the default megaraid_sas driver version in upstream Linux 2.6.32.25 is pretty old, version 4.01, and it seems to be very buggy. It fails to bring up disks and boot fails. Many people have reported this issue on various hardware using LSI RAID adapters, and on various Dell servers (R310/R410/R510/R710) using Dell PERC H700 RAID adapters (which are rebranded LSI adapters).

Hi List, I''ve testet a bunch of kernel- and module versions with megaraid_sas and xen for months now. With 2.6.18.8 kernel and v00.00.03.01 megaraid_sas module there seem to be sometimes strange and unreproduceable segmentation faults up to kernel panics under heave i/o load. With 2.6.24-19-xen kernel from Ubuntu and v00.00.03.10 megaraid_sas it seemed stable. But I was able to

CentOS Errata and Enhancement Advisory 2014:0893 Upstream details at : https://rhn.redhat.com/errata/RHEA-2014-0893.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: ba8d66aa82c1aabaf23f0635284306d4715a9580baea9ceded32ba4887cb882e kmod-megaraid_sas-06.803.01.00_rh1-1.el6_5.i686.rpm x86_64:

Hi all, this patchset implements an emulation for the megaraid_sas HBA. It provides emulates an LSI MegaRAID SAS 8708EM2 HBA, ie presenting to the guest a virtual SCSI adapter. Internally it is using aio for read/write requests and either SG_IO or SCSI command emulation for everything else. The reason for choosing the megaraid_sas HBA and not, say, implementing a virtio scsi interface is

Hi all, this patchset implements an emulation for the megaraid_sas HBA. It provides emulates an LSI MegaRAID SAS 8708EM2 HBA, ie presenting to the guest a virtual SCSI adapter. Internally it is using aio for read/write requests and either SG_IO or SCSI command emulation for everything else. The reason for choosing the megaraid_sas HBA and not, say, implementing a virtio scsi interface is

CentOS Errata and Enhancement Advisory 2016:1780 Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-1780.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 3f942683663a5acf3ec76fbc4da33363451ff5778ea1da2dec382806510af15f kmod-megaraid_sas-06.811.02.00-1.el7_2.x86_64.rpm Source:

CentOS Errata and Enhancement Advisory 2017:0518 Upstream details at : https://rhn.redhat.com/errata/RHEA-2017-0518.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: ed979c3e0264765971802dcf126c98649e278f5c5fddd224d72e80b461826169 kmod-redhat-megaraid_sas-07.700.00.00-rh1.el7_3.x86_64.rpm Source:

CentOS Errata and Enhancement Advisory 2018:1670 Upstream details at : https://access.redhat.com/errata/RHEA-2018:1670 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: a795c66044e67414a963d7531c1ce960850b788b1cb1fe63db95ed1159f18a9c kmod-redhat-megaraid_sas-07.702.06.00_rh2_dup7.5-1.el7_5.x86_64.rpm Source:

Hi to all I have a supermicro server with LSI 3108 with - 2x300GB SAS spin drive in raid1 (virtual drive 0) - 2x300GB SAS spin drive in raid1 (virtual drive 1) - 2x200GB Intel SSD DC S3710 drives configured as JBOD in LSI bios In the IPMI storage health status eveything looks fine until I boot into Centos 7.1 (unfortunatelly I didn't try other OS, but also I'm not interested in other)

CentOS Errata and Enhancement Advisory 2018:1670 Upstream details at : https://access.redhat.com/errata/RHEA-2018:1670 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) Source: b243c283592e002f31d604f12edbbfdd26a188f335f2751b92ad129045e79172 kmod-redhat-megaraid_sas-07.702.06.00_rh2_dup7.5-1.el7_5.src.rpm -- Johnny Hughes

Hi all, I try to install CentOS 4.3 for X64_64 on a new Dell PowerEdge 2950. I have two problems: 1. After booting from CD I pressed 'return' to start installation (BIOS-support for USB-keyboard works). After probing the hardware my USB-Keyboard is not working anymore. Dell removed ALL PS/2-Interfaces so I have to use USB. When I start installation with 'linux noprobe' the

I use xen 4.0(dom0 is suse11.sp1,2.6.32 x86_64) on Dell R710 with PERC H700 RAID adapter. --Intel(R) Xeon(R) CPU E5620 @ 2.40GHz --8 CPU cores. --Memory 64G --RAID5 4.5T When I dedicated (pin) a CPU core only for dom0 use. (I specify "dom0_max_vcpus=1 dom0_vcpus_pin" options for Xen) I got dom0 kernel panic error(pin-1-5.30.bmp) When I pin 2 core to dom0, the dom0 system can boot up,

ok - I tried this too. But CentOS tries to find the floppy as /dev/hda which is not the device for the USB-Floppy. Dell ships one with the server because no one is integrated. So when I try to include the driver disk the installer is not able to find it. -----Urspr?ngliche Nachricht----- Von: centos-bounces at centos.org [mailto:centos-bounces at centos.org] Im Auftrag von Jim Perrin Gesendet:

Hi list, I had a problem with the dahdi XPP driver. After this error in syslog, the Xorcom disconnect from the server: Jun 3 15:03:29 kernel: [361010.637858] *NOTICE-xpp_usb: xusb-0 (usb-0000:00:1d.7-3) [X1047686]: Sluggish USB. Dropping next PCM frame (p** **ending_writes=5)* Jun 3 15:03:52 kernel: [361033.890575]* ERR-xpp: XBUS-00: Failed to send from command_queue (ret=-19)* Jun 3

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

We have DELL R900 server with PERC6/i and PERC 6/E in it. O.S. is CENTOS 5.3. I download latest PERC 6 driver from DELL site and tried to installed it. I have error messages said : Module version 00.00.03.21 for megaraid_sas.ko is not newer than what is already found in kernel 2.6.18-128.1.10.el5 (00.00.04.01-RH1). Does CENTOS 5.3 come with PERC6 driver? I knew in CENTOS 4.X PERC 5 or PERC6