Release notes say no support for the RAID card in a box I just picked up...is there no hope for this box running 2.6 kernel?
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/release- notes/as-x86/
The kernel shipped with Red Hat Enterprise Linux 4 includes the new megaraid_mbox driver from LSI Logic, which replaces the megaraid driver. The megaraid_mbox driver has an improved design, is compatible with the 2.6 kernel, and includes support for the latest hardware. However, megaraid_mbox does not support some of the older hardware that was supported by the megaraid driver.
Adapters with the following PCI vendor ID and device ID pairs are not supported by the megaraid_mbox driver:
vendor, device
0x101E, 0x9010 0x101E, 0x9060 0x8086, 0x1960 <--- my card ---<
The lspci -n command can be used to display the IDs for adapters installed in a particular machine. Products with these IDs are known by (but not limited to) the following model names:
* Dell PERC (dual-channel fast/wide SCSI) RAID controller
* Dell PERC2/SC (single-channel Ultra SCSI) RAID controller
* Dell PERC2/DC (dual-channel Ultra SCSI) RAID controller
* Dell CERC (four-channel ATA/100) RAID controller
* MegaRAID 428
* MegaRAID 466
* MegaRAID Express 500
* HP NetRAID 3Si and 1M
Both Dell and LSI Logic have indicated that they no longer support these models in the 2.6 kernel. As a result, these adapters are not supported in Red Hat Enterprise Linux 4.
Craig
Craig White wrote:
Release notes say no support for the RAID card in a box I just picked up...is there no hope for this box running 2.6 kernel?
You are one of many trying to get RHEL4/CentOS4/FC3+ onto machines with this RAID controller breed. I am one of several people attempting to produce a viable driver disk that will enable us to install onto these machines. Unfortunately, this is my first-ever attempt at doing so, and I am met only with challenges and brick-walls.
I am happy to share with you everything I have learned in this effort, although my solution doesn't yet work. I wish I had better news, but it seems that those who know how to make this work aren't interested in sharing a solid, complete, working solution with everyone else on a "for newbies to kernel drivers" level.
When I actually get this to work, I assure you that I will publish the full procedure.
On Sat, 2005-08-13 at 19:51 -0600, William wrote:
Craig White wrote:
Release notes say no support for the RAID card in a box I just picked up...is there no hope for this box running 2.6 kernel?
You are one of many trying to get RHEL4/CentOS4/FC3+ onto machines with this RAID controller breed. I am one of several people attempting to produce a viable driver disk that will enable us to install onto these machines. Unfortunately, this is my first-ever attempt at doing so, and I am met only with challenges and brick-walls.
I am happy to share with you everything I have learned in this effort, although my solution doesn't yet work. I wish I had better news, but it seems that those who know how to make this work aren't interested in sharing a solid, complete, working solution with everyone else on a "for newbies to kernel drivers" level.
When I actually get this to work, I assure you that I will publish the full procedure.
---- I thought I20 driver would do it...
http://i2o.shadowconnect.com/survey_detail.php?id=76
but I get kernel panics when it loads
Did you see this?
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=138590
Craig
Craig White wrote:
I thought I20 driver would do it...
http://i2o.shadowconnect.com/survey_detail.php?id=76
but I get kernel panics when it loads
I've never seen a reference to I20 before, and I'm not sure I'd try it. :)
Did you see this?
Yes. The driver disk I'm trying to build uses the source code for the old LSI megaraid driver -- the one that does work. The machine I have that I'm building this disk for is a Dell PowerEdge 2300 with the PERC 2/SC RAID controller. That machine is currently running CentOS 3 just fine. I'm trying to fully rebuild the box from scratch using CentOS 4; that's why I'm motivated to attempt to make this driver disk.
If you're interested in what I have, here's an archive link to one of my older posts on this very topic: http://lists.centos.org/pipermail/centos/2005-August/009501.html
On Sat, 2005-08-13 at 21:48 -0600, William wrote:
Craig White wrote:
I thought I20 driver would do it...
http://i2o.shadowconnect.com/survey_detail.php?id=76
but I get kernel panics when it loads
I've never seen a reference to I20 before, and I'm not sure I'd try it. :)
Did you see this?
Yes. The driver disk I'm trying to build uses the source code for the old LSI megaraid driver -- the one that does work. The machine I have that I'm building this disk for is a Dell PowerEdge 2300 with the PERC 2/SC RAID controller. That machine is currently running CentOS 3 just fine. I'm trying to fully rebuild the box from scratch using CentOS 4; that's why I'm motivated to attempt to make this driver disk.
If you're interested in what I have, here's an archive link to one of my older posts on this very topic: http://lists.centos.org/pipermail/centos/2005-August/009501.html
---- that sounds simple enough...I've got a CentOS 4 system that I'm updating right now before I download the module source and compile it. Let's see how far I get.
Craig
On Sat, 2005-08-13 at 22:08 -0700, Craig White wrote:
On Sat, 2005-08-13 at 21:48 -0600, William wrote:
If you're interested in what I have, here's an archive link to one of my older posts on this very topic: http://lists.centos.org/pipermail/centos/2005-August/009501.html
that sounds simple enough...I've got a CentOS 4 system that I'm updating right now before I download the module source and compile it. Let's see how far I get.
---- I'm sort of stuck where you are...
anyone to toss a bone here on compiling kernel modules
I'm following the release notes: Note An exploded source tree is not required to build kernel modules against the currently in-use kernel.
For example, to build the foo.ko module, create the following file (named Makefile) in the directory containing the foo.c file:
obj-m := foo.o
KDIR := /lib/modules/$(shell uname -r)/build PWD := $(shell pwd)
default: $(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
so # ls -l total 204 -rw-r--r-- 1 root root 137 Aug 13 23:36 Makefile -rw-r--r-- 1 root root 140 Aug 13 23:33 Makefile~ -rw-r--r-- 1 root root 118447 Jun 24 12:42 megaraid.c -rw-r--r-- 1 root root 29506 Jun 24 12:42 megaraid.h -rw-r--r-- 1 root root 2808 Jun 24 13:04 scsi.h -rw-r--r-- 1 root root 4146 Jun 24 13:05 scsi_obsolete.h -rw-r--r-- 1 root root 215 Jun 24 13:05 scsi_typedefs.h
# cat Makefile obj-m := megaraid.o
KDIR := /lib/modules/2.6.9-11.ELsmp/build PWD := $(shell pwd)
default: $(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
then running the following...I'm shooting blanks...
# make -w make: Entering directory `/usr/src/megaraid' make -C /lib/modules/2.6.9-11.ELsmp/build SUBDIRS=/usr/src/megaraid modules make[1]: Entering directory `/lib/modules/2.6.9-11.ELsmp/build' make[1]: *** No rule to make target `modules'. Stop. make[1]: Leaving directory `/lib/modules/2.6.9-11.ELsmp/build' make: *** [default] Error 2 make: Leaving directory `/usr/src/megaraid'
Anyone care to toss a bone my way?
Craig
On Sat, 2005-08-13 at 23:47 -0700, Craig White wrote:
On Sat, 2005-08-13 at 22:08 -0700, Craig White wrote:
On Sat, 2005-08-13 at 21:48 -0600, William wrote:
If you're interested in what I have, here's an archive link to one of my older posts on this very topic: http://lists.centos.org/pipermail/centos/2005-August/009501.html
that sounds simple enough...I've got a CentOS 4 system that I'm updating right now before I download the module source and compile it. Let's see how far I get.
I'm sort of stuck where you are...
anyone to toss a bone here on compiling kernel modules
I'm following the release notes: Note An exploded source tree is not required to build kernel modules against the currently in-use kernel.
For example, to build the foo.ko module, create the following file (named Makefile) in the directory containing the foo.c file:
obj-m := foo.o
KDIR := /lib/modules/$(shell uname -r)/build PWD := $(shell pwd)
default: $(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
so # ls -l total 204 -rw-r--r-- 1 root root 137 Aug 13 23:36 Makefile -rw-r--r-- 1 root root 140 Aug 13 23:33 Makefile~ -rw-r--r-- 1 root root 118447 Jun 24 12:42 megaraid.c -rw-r--r-- 1 root root 29506 Jun 24 12:42 megaraid.h -rw-r--r-- 1 root root 2808 Jun 24 13:04 scsi.h -rw-r--r-- 1 root root 4146 Jun 24 13:05 scsi_obsolete.h -rw-r--r-- 1 root root 215 Jun 24 13:05 scsi_typedefs.h
# cat Makefile obj-m := megaraid.o
KDIR := /lib/modules/2.6.9-11.ELsmp/build PWD := $(shell pwd)
default: $(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
then running the following...I'm shooting blanks...
# make -w make: Entering directory `/usr/src/megaraid' make -C /lib/modules/2.6.9-11.ELsmp/build SUBDIRS=/usr/src/megaraid modules make[1]: Entering directory `/lib/modules/2.6.9-11.ELsmp/build' make[1]: *** No rule to make target `modules'. Stop. make[1]: Leaving directory `/lib/modules/2.6.9-11.ELsmp/build' make: *** [default] Error 2 make: Leaving directory `/usr/src/megaraid'
Anyone care to toss a bone my way?
---- Solved
yum install kernel-devel didn't work because like a moron, I was in smp kernel and so I needed to yum install kernel-smp-devel which then made it all work but of course the boot cd is a uni-processor so I will have to wait until I can reboot the production machine into a uni-processor mode to compile a suitable module to test
Craig
Craig White wrote:
On Sat, 2005-08-13 at 23:47 -0700, Craig White wrote:
On Sat, 2005-08-13 at 22:08 -0700, Craig White wrote:
On Sat, 2005-08-13 at 21:48 -0600, William wrote:
If you're interested in what I have, here's an archive link to one of my older posts on this very topic: http://lists.centos.org/pipermail/centos/2005-August/009501.html
that sounds simple enough...I've got a CentOS 4 system that I'm updating right now before I download the module source and compile it. Let's see how far I get.
I'm sort of stuck where you are...
anyone to toss a bone here on compiling kernel modules
I'm following the release notes: Note An exploded source tree is not required to build kernel modules against the currently in-use kernel.
For example, to build the foo.ko module, create the following file (named Makefile) in the directory containing the foo.c file:
obj-m := foo.o
KDIR := /lib/modules/$(shell uname -r)/build PWD := $(shell pwd)
default: $(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
so # ls -l total 204 -rw-r--r-- 1 root root 137 Aug 13 23:36 Makefile -rw-r--r-- 1 root root 140 Aug 13 23:33 Makefile~ -rw-r--r-- 1 root root 118447 Jun 24 12:42 megaraid.c -rw-r--r-- 1 root root 29506 Jun 24 12:42 megaraid.h -rw-r--r-- 1 root root 2808 Jun 24 13:04 scsi.h -rw-r--r-- 1 root root 4146 Jun 24 13:05 scsi_obsolete.h -rw-r--r-- 1 root root 215 Jun 24 13:05 scsi_typedefs.h
# cat Makefile obj-m := megaraid.o
KDIR := /lib/modules/2.6.9-11.ELsmp/build PWD := $(shell pwd)
default: $(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
then running the following...I'm shooting blanks...
# make -w make: Entering directory `/usr/src/megaraid' make -C /lib/modules/2.6.9-11.ELsmp/build SUBDIRS=/usr/src/megaraid modules make[1]: Entering directory `/lib/modules/2.6.9-11.ELsmp/build' make[1]: *** No rule to make target `modules'. Stop. make[1]: Leaving directory `/lib/modules/2.6.9-11.ELsmp/build' make: *** [default] Error 2 make: Leaving directory `/usr/src/megaraid'
Anyone care to toss a bone my way?
Solved
yum install kernel-devel didn't work because like a moron, I was in smp kernel and so I needed to yum install kernel-smp-devel which then made it all work but of course the boot cd is a uni-processor so I will have to wait until I can reboot the production machine into a uni-processor mode to compile a suitable module to test
Please keep us posted on your progress. I too am stuck at Centos 3 because of an old Megaraid controller.
Thanks, Ajay
On Tue, 2005-08-16 at 16:33 -0700, Ajay Sharma wrote:
Craig White wrote:
On Sat, 2005-08-13 at 23:47 -0700, Craig White wrote:
On Sat, 2005-08-13 at 22:08 -0700, Craig White wrote:
On Sat, 2005-08-13 at 21:48 -0600, William wrote:
If you're interested in what I have, here's an archive link to one of my older posts on this very topic: http://lists.centos.org/pipermail/centos/2005-August/009501.html
that sounds simple enough...I've got a CentOS 4 system that I'm updating right now before I download the module source and compile it. Let's see how far I get.
I'm sort of stuck where you are...
anyone to toss a bone here on compiling kernel modules
I'm following the release notes: Note An exploded source tree is not required to build kernel modules against the currently in-use kernel.
For example, to build the foo.ko module, create the following file (named Makefile) in the directory containing the foo.c file:
obj-m := foo.o
KDIR := /lib/modules/$(shell uname -r)/build PWD := $(shell pwd)
default: $(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
so # ls -l total 204 -rw-r--r-- 1 root root 137 Aug 13 23:36 Makefile -rw-r--r-- 1 root root 140 Aug 13 23:33 Makefile~ -rw-r--r-- 1 root root 118447 Jun 24 12:42 megaraid.c -rw-r--r-- 1 root root 29506 Jun 24 12:42 megaraid.h -rw-r--r-- 1 root root 2808 Jun 24 13:04 scsi.h -rw-r--r-- 1 root root 4146 Jun 24 13:05 scsi_obsolete.h -rw-r--r-- 1 root root 215 Jun 24 13:05 scsi_typedefs.h
# cat Makefile obj-m := megaraid.o
KDIR := /lib/modules/2.6.9-11.ELsmp/build PWD := $(shell pwd)
default: $(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
then running the following...I'm shooting blanks...
# make -w make: Entering directory `/usr/src/megaraid' make -C /lib/modules/2.6.9-11.ELsmp/build SUBDIRS=/usr/src/megaraid modules make[1]: Entering directory `/lib/modules/2.6.9-11.ELsmp/build' make[1]: *** No rule to make target `modules'. Stop. make[1]: Leaving directory `/lib/modules/2.6.9-11.ELsmp/build' make: *** [default] Error 2 make: Leaving directory `/usr/src/megaraid'
Anyone care to toss a bone my way?
Solved
yum install kernel-devel didn't work because like a moron, I was in smp kernel and so I needed to yum install kernel-smp-devel which then made it all work but of course the boot cd is a uni-processor so I will have to wait until I can reboot the production machine into a uni-processor mode to compile a suitable module to test
Please keep us posted on your progress. I too am stuck at Centos 3 because of an old Megaraid controller.
---- I'm this close ' '
snagged because loading module says I should be compiling for 586 (it's dual Pentium 3 processors - has me befuddled - for the moment)
Ah - there's a 586 devel kernel ;-)
Craig
On Tue, 2005-08-16 at 16:33 -0700, Ajay Sharma wrote:
Solved
yum install kernel-devel didn't work because like a moron, I was in smp kernel and so I needed to yum install kernel-smp-devel which then made it all work but of course the boot cd is a uni-processor so I will have to wait until I can reboot the production machine into a uni-processor mode to compile a suitable module to test
Please keep us posted on your progress. I too am stuck at Centos 3 because of an old Megaraid controller.
---- The Eagle has landed ! ! !
I have installed CentOS 4 on LSI Megaraid 467 (I believe what Dell would call the Perc-2/DC - AND it has booted and is running.
Much thanks to Tom Sightler for his excellent blog. I have included a copy of this in the event it helps him to adjust his blog. For completeness, his blog is here... http://www.tuxyturvy.com/blog/index.php?/archives/4-Installing-RHEL4-on- Systems-with-Legacy-Megaraid-Drivers.html
Adjustments MUST be made to accomplish this on CentOS - the reason is that CentOS permits 586 hardware and thus the installer reduces the lowest common denominator and you have to use the 586 version of the kernel to use anaconda but then you need the 686 version for first boot. The file you copy to your installed base in /lib/modules/2.6.9-11.EL/kernel/drivers/scsi/megaraid should be the 686 version, NOT the 586 version necessary for the anaconda installer.
Thus the way I got it done...
mkdir /usr/src/software cd /usr/src/software wget http://www.tuxyturvy.com/files/megaraid2.tar.bz2 yum install kernel-devel-2.6.9-11.EL.i586 mkdir /usr/src/megaraid cd /usr/src/megaraid tar jxvfp /usr/src/sofware/megaraid2.tar.bz2 make -C /lib/modules/2.6.9-11.EL/build SUBDIRS=/usr/src/megaraid modules
then copied megaraid.ko to a floppy and labeled it megaraid-586
then I cleaned out the kernel-devel...to make way for the 686 version rpm -e kernel-devel yum install kernel-devel
then cd ../ mv megaraid megaraid-586 mkdir megaraid cd megaraid tar jxvfp /usr/src/sofware/megaraid2.tar.bz2 make -C /lib/modules/2.6.9-11.EL/build SUBDIRS=/usr/src/megaraid modules
then copied megaraid.ko to a floppy and labeled it megaraid-686
You could probably repeat for smp kernel if you have multiple processors now...you should be getting the pattern except that you can have kernel- devel and kernel-smp-devel installed at the same time. You cannot have kernel-devel for both 586 and 686 'uni-processor' both installed at the same time.
Anyway, the 586 is used during installs or 'linux rescue' efforts when you screw up ;-)
I found that when I booted into linux rescue, I could switch consoles.. Alt-F2
rmmod megaraid_mbox rmmod megaraid_mm mkdir /mnt/floppy mount /dev/fdo /mnt/floppy insmod /mnt/floppy/megaraid.ko
and be working... this process may be easier than 'noprobe' option passed at boot
Craig
Craig White wrote:
The Eagle has landed ! ! !
I have installed CentOS 4 on LSI Megaraid 467 (I believe what Dell would call the Perc-2/DC - AND it has booted and is running.
and be working... this process may be easier than 'noprobe' option passed at boot
I will attempt this procedure this Saturday on my Dell PowerEdge 2300 (PERC 2/SC) and see if it works for me, as well. Thank you for keeping us posted!
Craig White wrote:
I found that when I booted into linux rescue, I could switch consoles.. Alt-F2
rmmod megaraid_mbox rmmod megaraid_mm mkdir /mnt/floppy mount /dev/fdo /mnt/floppy insmod /mnt/floppy/megaraid.ko
When in rescue mode, I can access the command shell, as you indicated. I could also insert the megaraid-i586 module, as you indicated. However, because I'm in rescue mode -- and after successfully adding the megaraid.ko kernel module -- I am forced back out to the command shell by the installer at the last rescue screen (where it offers to mount your existing file system).
Then, what? How do I actually install CentOS 4 at this point? I never saw anaconda.
The tuxyturvy link reads, "At this point complete switch back to the normal install screen by pressing Alt-F1." This does nothing.
Thanks for your help!
On Sat, 2005-08-20 at 11:42 -0600, William wrote:
Craig White wrote:
I found that when I booted into linux rescue, I could switch consoles.. Alt-F2
rmmod megaraid_mbox rmmod megaraid_mm mkdir /mnt/floppy mount /dev/fdo /mnt/floppy insmod /mnt/floppy/megaraid.ko
When in rescue mode, I can access the command shell, as you indicated. I could also insert the megaraid-i586 module, as you indicated. However, because I'm in rescue mode -- and after successfully adding the megaraid.ko kernel module -- I am forced back out to the command shell by the installer at the last rescue screen (where it offers to mount your existing file system).
Then, what? How do I actually install CentOS 4 at this point? I never saw anaconda.
The tuxyturvy link reads, "At this point complete switch back to the normal install screen by pressing Alt-F1." This does nothing.
Thanks for your help!
---- you don't install in 'linux rescue' mode...that's what you have to do when you install the wrong module and have to fix things.
Follow the instructions on the web page - but see my notes previously in thread. CentOS makes it a bit more difficult because it needs the megaraid.ko built with i586 kernel but when the 'megaraid.ko' you copy into /lib/modules/2.6.9-11.EL[smp]/kernel/drivers/scsi/megaraid has to be built with the 686/smp version and not the 586 version or it won't work.
This of course has nothing to do with linux rescue mode
Craig
Craig White wrote:
you don't install in 'linux rescue' mode...that's what you have to do when you install the wrong module and have to fix things.
Follow the instructions on the web page - but see my notes previously in thread. CentOS makes it a bit more difficult because it needs the megaraid.ko built with i586 kernel but when the 'megaraid.ko' you copy into /lib/modules/2.6.9-11.EL[smp]/kernel/drivers/scsi/megaraid has to be built with the 686/smp version and not the 586 version or it won't work.
This of course has nothing to do with linux rescue mode
When following your instructions very closely, the user is prompted to attempt to install in 'linux rescue' mode in order to have the ability to use Alt+F2 to switch to a shell. :) As I noted early in this discovery, the normal linux installer does not allow this switch. In the time between my query and your reply, I found that 'linux dd' also allows you to switch to a shell with Alt+F2, as well, so I have expanded on your documentation as follows (I am still testing this process, so it should not be considered 'working' until my tests are complete). I included some spelling corrections and some "for dummies" instructions to help a broader user-base:
##### ## HowTo: Install CentOS 4.0 with legacy MegaRAID controllers. ## Authors: ## Tom Sightler ## Craig White ## William Kimball, Jr. #####
##### ## ALERT: Unless you follow tips below, this procedure works only for ## single-CPU machines. #####
##### ## ALERT: You will need two seperate floppy disks that are okay to ## format. Label the first as, "megaraid i586" and the second as, ## "megaraid i686" #####
rpm -e --allmatches kernel-devel yum -y install kernel-devel-2.6.9-11.EL.i586 mkdir /usr/src/software cd /usr/src/software wget http://www.tuxyturvy.com/files/megaraid.tar.bz2 mkdir /usr/src/megaraid cd /usr/src/megaraid tar jxvfp /usr/src/software/megaraid.tar.bz2
##### ## There will be a lot of warnings at this next step. They are ## harmless; ignore them. ##### make -C /lib/modules/2.6.9-11.EL/build SUBDIRS=/usr/src/megaraid modules
##### ## Insert the floppy labeled, "megaraid i586". ##### fdformat -n /dev/fd0u1440 mkfs -t ext2 /dev/fd0u1440 mount /dev/fd0u1440 /media/floppy rm -rf /media/floppy/* cp megaraid.ko /media/floppy/ umount /media/floppy
##### ## Wait for the drive light to turn off, then remove the floppy ## and be sure it is labeled, "megaraid i586" #####
##### ## Uninstall the i586 kernel-devel package and replace it with the i686 ## version. ##### rpm -e --allmatches kernel-devel yum -y install kernel-devel
cd /usr/src/ mv /usr/src/megaraid /usr/src/megaraid-i586 mkdir /usr/src/megaraid cd /usr/src/megaraid tar jxvfp /usr/src/software/megaraid.tar.bz2
##### ## There will be a lot of warnings at this next step. They are ## harmless; ignore them. ##### make -C /lib/modules/2.6.9-11.EL/build SUBDIRS=/usr/src/megaraid modules
##### ## Insert the floppy labeled, "megaraid i686". ##### fdformat -n /dev/fd0u1440 mkfs -t ext2 /dev/fd0u1440 mount /dev/fd0u1440 /media/floppy rm -rf /media/floppy/* cp megaraid.ko /media/floppy/ umount /media/floppy
##### ## Wait for the drive light to turn off, then remove the floppy and be ## sure it is labeled, "megaraid i686" #####
##### ## Quoted from Craig White at: ## http://lists.centos.org/pipermail/centos/2005-August/010021.html ##### " You could probably repeat for smp kernel if you have multiple processors now...you should be getting the pattern except that you can have kernel- devel and kernel-smp-devel installed at the same time. You cannot have kernel-devel for both 586 and 686 'uni-processor' both installed at the same time.
Anyway, the 586 is used during installs or 'linux rescue' efforts when you screw up ;-) "
##### ## Insert disk 1 of the CentOS 4 install set into your machine and ## reboot it. At the CentOS 4 install prompt, insert the "megaraid ## i586" disk into the machine and type: #####
linux dd
##### ## When asked whether you have a driver disk, answer No ## The probe will find the MegaRAID controller and Adaptec SCSI devices, ## but you will get Warning: No hard drives have been found. ## This is normal. Answer Yes, that you'd like to select drivers now. ## Tap Alt+F2 to get to a command prompt, ensure the "megaraid i586" ## disk is loaded and run: ##### rmmod megaraid_mbox rmmod megaraid_mm mkdir /mnt/floppy mount /dev/fd0 /mnt/floppy insmod /mnt/floppy/megaraid.ko lsmod
##### ## Make sure you see megaraid in the lsmod output. ## To confirm that the driver loaded, tap Alt+F4 and look toward the ## bottom for SCSI entries. Tap Alt+F1 to return to the driver ## selection screen. It will still show the wrong driver, but ignore ## this. Click 'Done' to proceed. Anaconda will start up and you are ## free to install whatever packages you deem necessary. #####
##### ## ALERT: DO NOT CLICK [REBOOT] WHEN ALL PACKAGES ARE INSTALLED! ## Instead, remove the last installer CD-ROM and tap Ctrl+Alt+F2 to ## return to the command prompt and run: ##### umount /mnt/floppy
##### ## Insert the "megaraid i686" disk into the machine and type: ##### mount /dev/fd0 /mnt/floppy cp /mnt/floppy/megaraid.ko /lib/modules/2.6.9-11.EL/kernel/drivers/scsi umount /mnt/floppy
##### ## Wait for the drive light to turn off, then remove the floppy and ## proceed by following the remainder of Tom Sightler's instructions, ## starting near the bottom of ## http://www.tuxyturvy.com/blog/index.php?/archives/4-Installing-RHEL4-on-Syst... ## at: ## "3. Type 'chroot /mnt/sysimage' to set your root to your newly ## installed system image" #####
##### ## For convenience, those remaining instructions are: ##### " 3. Type 'chroot /mnt/sysimage' to set your root to your newly installed system image 4. Type 'vi /etc/modules.conf' and make sure that the line with 'alias scsi_hostadapter' says 'alias scsi_hostadapter megaraid'. Save the file 5. Switch to the /boot directory 'cd /boot' 6. Create new initrd file 'mkinitrd initrd-2.6.9-11.EL.img.megaraid 2.6.9-11.EL' 7. Copy the new initrd over old initrd 'cp initrd-2.6.9-11.EL.img.megaraid initrd-2.6.9-EL.img' 8. Exit chroot environment by typing exit 9. Switch back to the GUI installer with Alt-F7 and press Finish
After these steps your system should be able to boot up a UP kernel. If your installing on an SMP section you'll need to boot up the UP system, compile the source driver again for the SMP kernel, install the module, recreate the initrd for the SMP kernel, and reboot again. "
On Sat, 2005-08-20 at 15:02 -0600, William wrote:
Craig White wrote:
you don't install in 'linux rescue' mode...that's what you have to do when you install the wrong module and have to fix things.
Follow the instructions on the web page - but see my notes previously in thread. CentOS makes it a bit more difficult because it needs the megaraid.ko built with i586 kernel but when the 'megaraid.ko' you copy into /lib/modules/2.6.9-11.EL[smp]/kernel/drivers/scsi/megaraid has to be built with the 686/smp version and not the 586 version or it won't work.
This of course has nothing to do with linux rescue mode
When following your instructions very closely, the user is prompted to attempt to install in 'linux rescue' mode in order to have the ability to use Alt+F2 to switch to a shell. :)
---- those aren't my instructions - 'linux resuce' is a mode of anaconda that has nothing to do with installing. ----
As I noted early in this discovery, the normal linux installer does not allow this switch.
---- sure it does - after you complete (or skip) the verify media process, if all you have is the RAID disks, system will stop and report that it was unable to find a suitable disk for installation and ask if you want to install any modules (this is the virtual equivalent of passing a 'linux dd' at boot). At that point, you can switch to a working command prompt (<Alt><F2>) ----
In the time between my query and your reply, I found that 'linux dd' also allows you to switch to a shell with Alt+F2
---- it is unnecessary - do NOT install any of the megaraid modules prsented by the 'Add module' but you can (I think - untested) insert the floppy disk with the proper megaraid.ko at this point (it has to be the one created with the 586 kernel-devel).
I found that it was incredibly simple to boot normally, skip the media test (you MUST have good media) - get to the next screen where it complains about not finding a suitable disk to install upon, to switch to the <Alt><F2> console and... (if you didn't noprobe at boot) rmmod megaraid_mbox rmmod megaraid_mm (whether you booted with noprobe parameter passed at boot or not, continue on) mkdir /mnt/floppy mount /dev/fd0 /mnt/floppy insmod /mnt/floppy/megaraid.ko #this has to be created with 586-kernel- devel then once you have verified that the module is loaded and the disks have been found <Alt><F4> - you can continue on with the install process <Alt><F1> this ain't that hard
the web link at tuxyturvy.com was nearly perfect for RHEL 4 (megaraid.ko should actually be copied to /lib/modules/2.6.9-11EL/kernel/drivers/scsi/megaraid)
the web link at tuxyturvy.com needed additional adjustments for CentOS 4.1:
1 - megaraid.ko at boot time on CD had to be built with kernel- devel-2.6.9-11EL.i586
2 - megaraid.ko copied into /lib/modules/2.6.9-11EL/kernel/drivers/scsi/megaraid had to be built with kernel-devel-2.6.9-11EL.i686
3 - you cannot have both kernel-devel installed on the same computer at the same time. Install one, build the megaraid.ko, copy it to a floppy and then rpm -e kernel-devel and then install the other and build the module, copy it to another floppy. If you have an smp system, you will have to do this a third time (for the smp kernel) but by then, you should have figured out how to get it done.
Again - linux rescue mode parameter passed at boot is only for trying to fix what you did wrong AFTER you have installed CentOS 4.1 and couldn't boot from the RAID array (you will get a kernel panic)
Craig ----
, as well, so I have expanded on your documentation as follows (I am still testing this process, so it should not be considered 'working' until my tests are complete). I included some spelling corrections and some "for dummies" instructions to help a broader user-base:
##### ## HowTo: Install CentOS 4.0 with legacy MegaRAID controllers. ## Authors: ## Tom Sightler ## Craig White ## William Kimball, Jr. #####
##### ## ALERT: Unless you follow tips below, this procedure works only for ## single-CPU machines. #####
##### ## ALERT: You will need two seperate floppy disks that are okay to ## format. Label the first as, "megaraid i586" and the second as, ## "megaraid i686" #####
rpm -e --allmatches kernel-devel yum -y install kernel-devel-2.6.9-11.EL.i586 mkdir /usr/src/software cd /usr/src/software wget http://www.tuxyturvy.com/files/megaraid.tar.bz2 mkdir /usr/src/megaraid cd /usr/src/megaraid tar jxvfp /usr/src/software/megaraid.tar.bz2
##### ## There will be a lot of warnings at this next step. They are ## harmless; ignore them. ##### make -C /lib/modules/2.6.9-11.EL/build SUBDIRS=/usr/src/megaraid modules
##### ## Insert the floppy labeled, "megaraid i586". ##### fdformat -n /dev/fd0u1440 mkfs -t ext2 /dev/fd0u1440 mount /dev/fd0u1440 /media/floppy rm -rf /media/floppy/* cp megaraid.ko /media/floppy/ umount /media/floppy
##### ## Wait for the drive light to turn off, then remove the floppy ## and be sure it is labeled, "megaraid i586" #####
##### ## Uninstall the i586 kernel-devel package and replace it with the i686 ## version. ##### rpm -e --allmatches kernel-devel yum -y install kernel-devel
cd /usr/src/ mv /usr/src/megaraid /usr/src/megaraid-i586 mkdir /usr/src/megaraid cd /usr/src/megaraid tar jxvfp /usr/src/software/megaraid.tar.bz2
##### ## There will be a lot of warnings at this next step. They are ## harmless; ignore them. ##### make -C /lib/modules/2.6.9-11.EL/build SUBDIRS=/usr/src/megaraid modules
##### ## Insert the floppy labeled, "megaraid i686". ##### fdformat -n /dev/fd0u1440 mkfs -t ext2 /dev/fd0u1440 mount /dev/fd0u1440 /media/floppy rm -rf /media/floppy/* cp megaraid.ko /media/floppy/ umount /media/floppy
##### ## Wait for the drive light to turn off, then remove the floppy and be ## sure it is labeled, "megaraid i686" #####
##### ## Quoted from Craig White at: ## http://lists.centos.org/pipermail/centos/2005-August/010021.html ##### " You could probably repeat for smp kernel if you have multiple processors now...you should be getting the pattern except that you can have kernel- devel and kernel-smp-devel installed at the same time. You cannot have kernel-devel for both 586 and 686 'uni-processor' both installed at the same time.
Anyway, the 586 is used during installs or 'linux rescue' efforts when you screw up ;-) "
##### ## Insert disk 1 of the CentOS 4 install set into your machine and ## reboot it. At the CentOS 4 install prompt, insert the "megaraid ## i586" disk into the machine and type: #####
linux dd
##### ## When asked whether you have a driver disk, answer No ## The probe will find the MegaRAID controller and Adaptec SCSI devices, ## but you will get Warning: No hard drives have been found. ## This is normal. Answer Yes, that you'd like to select drivers now. ## Tap Alt+F2 to get to a command prompt, ensure the "megaraid i586" ## disk is loaded and run: ##### rmmod megaraid_mbox rmmod megaraid_mm mkdir /mnt/floppy mount /dev/fd0 /mnt/floppy insmod /mnt/floppy/megaraid.ko lsmod
##### ## Make sure you see megaraid in the lsmod output. ## To confirm that the driver loaded, tap Alt+F4 and look toward the ## bottom for SCSI entries. Tap Alt+F1 to return to the driver ## selection screen. It will still show the wrong driver, but ignore ## this. Click 'Done' to proceed. Anaconda will start up and you are ## free to install whatever packages you deem necessary. #####
##### ## ALERT: DO NOT CLICK [REBOOT] WHEN ALL PACKAGES ARE INSTALLED! ## Instead, remove the last installer CD-ROM and tap Ctrl+Alt+F2 to ## return to the command prompt and run: ##### umount /mnt/floppy
##### ## Insert the "megaraid i686" disk into the machine and type: ##### mount /dev/fd0 /mnt/floppy cp /mnt/floppy/megaraid.ko /lib/modules/2.6.9-11.EL/kernel/drivers/scsi umount /mnt/floppy
##### ## Wait for the drive light to turn off, then remove the floppy and ## proceed by following the remainder of Tom Sightler's instructions, ## starting near the bottom of ## http://www.tuxyturvy.com/blog/index.php?/archives/4-Installing-RHEL4-on-Syst... ## at: ## "3. Type 'chroot /mnt/sysimage' to set your root to your newly ## installed system image" #####
##### ## For convenience, those remaining instructions are: ##### " 3. Type 'chroot /mnt/sysimage' to set your root to your newly installed system image 4. Type 'vi /etc/modules.conf' and make sure that the line with 'alias scsi_hostadapter' says 'alias scsi_hostadapter megaraid'. Save the file 5. Switch to the /boot directory 'cd /boot' 6. Create new initrd file 'mkinitrd initrd-2.6.9-11.EL.img.megaraid 2.6.9-11.EL' 7. Copy the new initrd over old initrd 'cp initrd-2.6.9-11.EL.img.megaraid initrd-2.6.9-EL.img' 8. Exit chroot environment by typing exit 9. Switch back to the GUI installer with Alt-F7 and press Finish
After these steps your system should be able to boot up a UP kernel. If your installing on an SMP section you'll need to boot up the UP system, compile the source driver again for the SMP kernel, install the module, recreate the initrd for the SMP kernel, and reboot again. "
Craig White wrote:
On Sat, 2005-08-20 at 15:02 -0600, William wrote:
As I noted early in this discovery, the normal linux installer does not allow this switch.
sure it does - after you complete (or skip) the verify media process, if all you have is the RAID disks, system will stop and report that it was unable to find a suitable disk for installation and ask if you want to install any modules (this is the virtual equivalent of passing a 'linux dd' at boot). At that point, you can switch to a working command prompt (<Alt><F2>)
To clarify: I'm installing with the original CentOS 4.0 release that has an older 2.6.9-5.0.3.EL kernel. I'm doing my best to balance your instructions (apparently for CentOS 4.1 or perhaps newer CentOS 4.0 install images) against what I actually have on-hand. This is tricky, and one of my hurdles is that the linux installer really does not allow Alt+F2 switching when in modes other than 'dd' or 'rescue'. I found the tuxyturvy page a long time ago and met that frustration very early. Your 'linux rescue' note set me on the right track and things are falling into place, slowly.
In any event, I boffed my first install attempt and I'm running the whole process again. I'll let the list know whether I get this to work with CentOS 4.0.
Thanks, again, for the help! :)
I give. My whole objective was to get this procedure to work on CentOS 4.0 with the oldest kernel, publish the procedure, then publish changes for each successive kernel update. I can't get it to work with 4.0. I can only assume this is either because I have the SC, not DC model, or because I can't seem to get the complete set of correct old kernel sources to compile against.
In any event, it seems that other people are getting this to work with 4.1, so I'll give up my 4.0 ambition and just update with the pack. I'm downloading the 4.1 isos now and I will start over from scratch when I have the new disks burned. (This includes my original objective of producing a working driver disk that will solve this problem with relative ease for everyone else.)
If I can make a working driver disk, I will start a new thread; otherwise, I will just confirm the procedure documented here.
On Sat, 2005-08-20 at 17:12 -0600, William wrote:
I give. My whole objective was to get this procedure to work on CentOS 4.0 with the oldest kernel, publish the procedure, then publish changes for each successive kernel update. I can't get it to work with 4.0. I can only assume this is either because I have the SC, not DC model, or because I can't seem to get the complete set of correct old kernel sources to compile against.
In any event, it seems that other people are getting this to work with 4.1, so I'll give up my 4.0 ambition and just update with the pack. I'm downloading the 4.1 isos now and I will start over from scratch when I have the new disks burned. (This includes my original objective of producing a working driver disk that will solve this problem with relative ease for everyone else.)
If I can make a working driver disk, I will start a new thread; otherwise, I will just confirm the procedure documented here.
----- There's really nothing to it. I seriously doubt that being single channel or dual channel has anything to do with it at all.
If you want megaraid.ko from 2.6.9-11EL-i686, 2.6.9-11EL-i586 and 2.6.9-11ELsmp-i686 I could probably upload them somewhere for you to download but the process is quite simple and you really need to get it down so you don't rely upon others every time the kernel updates.
If you put them on a vfat floppy, they work.
The issue really is, you need an install already functioning to install the matching kernel-devel to build the modules.
Craig
Craig White wrote:
There's really nothing to it. I seriously doubt that being single channel or dual channel has anything to do with it at all.
If you want megaraid.ko from 2.6.9-11EL-i686, 2.6.9-11EL-i586 and 2.6.9-11ELsmp-i686 I could probably upload them somewhere for you to download but the process is quite simple and you really need to get it down so you don't rely upon others every time the kernel updates.
If you put them on a vfat floppy, they work.
The issue really is, you need an install already functioning to install the matching kernel-devel to build the modules.
You underestimate me; perhaps because you're missing the little, but imperative, details in my messages. :)
The CD-ROMs I'm using don't have the 2.6.9.11EL kernel on them; therefore, modules compiled against that kernel do me no good. I know; I've tried. :)
Don't worry, this isn't upsetting. It's just a challenge that I'm going to find a better way to surmount. I was trying to provide a service to others still using the original CentOS 4 (by that, I do mean the very first CentOS 4 that was ever released) and who are still asking for a working megaraid driver disk.
Alas, I'm going to replace my 4.0 CD-ROM set with a new (as of tonight) 4.1 set and probably meet far easier success with it. I'll just recommend everyone else do the same in order to use whatever solution I am able to prove working. No worries. :)
The following text is provided only in an effort to belay any further doubt about my capability on this project. You see, I run an overgrown SOHO at home (8 distinct servers with several additional workstations) where I experiment widely. I write How-Tos, update others that I find useful but inaccurate, contribute to open source projects, and generally tool around with Linux and Windows for curiosity's sake. I'm an engineer elsewhere by trade, and this is my hobby at home. I'm having absolutely no trouble compiling these modules. I'm just using the wrong source and/or I haven't yet found the magic sequence that will pull together a driver disk that will work fully with CentOS 4. I have used the ddiskit utility, which was very educational, but the result was still unsuccessful. Indeed, the installer finally recognizes my disks as driver disks, but it always ignores my megaraid driver claiming that no matching devices were found. I suspect the device ID doesn't match "something" on my dd, but I don't know what. In all honesty, this is my very first driver disk project, but it is far removed from my first major Linux undertaking. Rather than dig deeper into an already antiquated version, I've decided to skip this leg of the project in pursuit of an avenue that seems to have greater, easier success. I'll upgrade my source install set to CentOS 4.1 and see what happens. Then, I'll share the result and, hopefully, provide a fully functional driver disk that will be far easier for the many other people waiting for such a solution. Make no mistake, a lot of other people are looking for this driver disk. The way I see it, good, compassionate assistance can be dreadfully hard to find in the broad Linux community; especially for newbies who face a torrential onslaught of razzing and impatience. I'm just trying to help the lowest common denominator. :)
On Sun, 2005-08-21 at 01:25 -0600, William wrote:
Craig White wrote:
There's really nothing to it. I seriously doubt that being single channel or dual channel has anything to do with it at all.
If you want megaraid.ko from 2.6.9-11EL-i686, 2.6.9-11EL-i586 and 2.6.9-11ELsmp-i686 I could probably upload them somewhere for you to download but the process is quite simple and you really need to get it down so you don't rely upon others every time the kernel updates.
If you put them on a vfat floppy, they work.
The issue really is, you need an install already functioning to install the matching kernel-devel to build the modules.
You underestimate me; perhaps because you're missing the little, but imperative, details in my messages. :)
The CD-ROMs I'm using don't have the 2.6.9.11EL kernel on them; therefore, modules compiled against that kernel do me no good. I know; I've tried. :)
---- It's not that I underestimate you. It's made perfectly clear that the module MUST be compiled on a matching kernel-devel on the tuxyturvy web page...see the first paragraph of getting ready... "On your working RHEL4 system make sure you have the kernel-devel packages installed that match the kernel on your install media"
If you could install the proper kernel-devel rpms on some other system that you have running, you could compile the module on that system.
This is NOT a DC/SC thing, this is not an CentOS 4 or 4.1 thing. ----
Don't worry, this isn't upsetting. It's just a challenge that I'm going to find a better way to surmount. I was trying to provide a service to others still using the original CentOS 4 (by that, I do mean the very first CentOS 4 that was ever released) and who are still asking for a working megaraid driver disk.
---- sounds good but as far as I can tell, the CentOS 4 iso's have been pulled and all that can be downloaded at this point is the 4.1 iso's so I am not sure the value to building them to a now obseleted iso to anyone but yourself. ----
Alas, I'm going to replace my 4.0 CD-ROM set with a new (as of tonight) 4.1 set and probably meet far easier success with it. I'll just recommend everyone else do the same in order to use whatever solution I am able to prove working. No worries. :)
The following text is provided only in an effort to belay any further doubt about my capability on this project. You see, I run an overgrown SOHO at home (8 distinct servers with several additional workstations) where I experiment widely. I write How-Tos, update others that I find useful but inaccurate, contribute to open source projects, and generally tool around with Linux and Windows for curiosity's sake. I'm an engineer elsewhere by trade, and this is my hobby at home. I'm having absolutely no trouble compiling these modules. I'm just using the wrong source and/or I haven't yet found the magic sequence that will pull together a driver disk that will work fully with CentOS 4. I have used the ddiskit utility, which was very educational, but the result was still unsuccessful. Indeed, the installer finally recognizes my disks as driver disks, but it always ignores my megaraid driver claiming that no matching devices were found. I suspect the device ID doesn't match "something" on my dd, but I don't know what. In all honesty, this is my very first driver disk project, but it is far removed from my first major Linux undertaking. Rather than dig deeper into an already antiquated version, I've decided to skip this leg of the project in pursuit of an avenue that seems to have greater, easier success. I'll upgrade my source install set to CentOS 4.1 and see what happens. Then, I'll share the result and, hopefully, provide a fully functional driver disk that will be far easier for the many other people waiting for such a solution. Make no mistake, a lot of other people are looking for this driver disk. The way I see it, good, compassionate assistance can be dreadfully hard to find in the broad Linux community; especially for newbies who face a torrential onslaught of razzing and impatience. I'm just trying to help the lowest common denominator. :)
---- this probably isn't the type of task for a Linux newbie - at least not one that gets discouraged easily.
It does seem that you are completely over thinking the issue of a driver disk. Copy the megaraid.ko to a vfat formatted floppy disk and insert when told to insert driver disk.
The issue is strictly matching the booted kernel on the install CD. On CentOS 4.1, that is known to be 2.6.9-11.EL-i586 - that is different from the instructions on the tuxyturvy web site since that would have to you compile 2.6.9-11.EL-i686.
You will need the 2.6.9-11.EL-i686 compiled module of the megaraid.ko copied into the proper place before you mkinitrd per the instructions on the tuxyturvy site - hence the requirement for compiling for both 586 & 686 when doing this with CentOS
After all that is accomplished - you will have to retain the megaraid source and be prepared to repeat the process for booting any other installed kernels including the SMP kernel (if you use it), and any released updated kernels.
I also note that I installed the 'unsupported' UP & SMP kernels from centosplus and tried to repeat the process and ran into kernel panics when adding the megaraid module built in this fashion.
Craig
Craig White wrote:
this probably isn't the type of task for a Linux newbie - at least not one that gets discouraged easily.
Exactly; that's why I'm building a driver disk. Compiling anything, especially against the kernel, isn't for newbies. That doesn't mean there aren't newbies who need this legacy megaraid in an easy-to-deploy medium. I'm trying to step in to provide that solution.
It does seem that you are completely over thinking the issue of a driver disk. Copy the megaraid.ko to a vfat formatted floppy disk and insert when told to insert driver disk.
I thought you'd know this, but a driver disk is much more than just a .ko file on a floppy (or several). I'm not over thinking this, at all. I'm just challenged by it because this is my first driver disk project and I can't seem to find a full set of detailed requirements for building a successful driver disk (I have provided the rhdd, modinfo, pcitable, modules.cgz, and modules.dep files, but some important detail is still missing). ddiskit filled in some gaps, but I still don't have the specifications for what would cause, "No matching hardware was found on your system."
You're right. I could get my personal server up and running if I followed the steps on the tuxyturvy site, with your additional input, and a 4.1 ISO set. However, that would help only me and others like you and me who are competent with handling these low-level chores. I'm dealing with a bigger picture. I am deliberately trying to build a full-fledged driver disk that will help everyone else. In reality, our process is very complex to a newbie compared to the alternative: download a driver disk image from some web site and use it with the very convenient 'linux dd' install mode. I'm trying to provide that driver disk image; one that I can say works with confidence. That is my only goal. :) I'm not at all desperate to get this particular server running. If I was, I wouldn't be posting on this thread (or the threads that I've started, myself). :)
Part of my problem is that this is my hobby, which I only work on over the weekends. When I started this project, CentOS 4.0 was still available and in wide use. That said, you're right. There is no longer any point in trying to continue with 4.0. I just hope I can make a good driver disk before 4.1 becomes antiquated. :)
After all that, I hope that I have clearly asserted my objective, which isn't quite what you had previously assumed. :) You have helped me clarify some important details in the kernel matching requirements (I had no idea i586 and i686 sources couldn't be on the machine at the same time). Now, if you know where I might find all the specifications and troubleshooting details I need to make a working driver disk (aside from ddiskit), I'm all ears! :)
On Sun, 2005-08-21 at 13:06 -0600, William wrote:
Craig White wrote:
this probably isn't the type of task for a Linux newbie - at least not one that gets discouraged easily.
Exactly; that's why I'm building a driver disk. Compiling anything, especially against the kernel, isn't for newbies. That doesn't mean there aren't newbies who need this legacy megaraid in an easy-to-deploy medium. I'm trying to step in to provide that solution.
It does seem that you are completely over thinking the issue of a driver disk. Copy the megaraid.ko to a vfat formatted floppy disk and insert when told to insert driver disk.
I thought you'd know this, but a driver disk is much more than just a .ko file on a floppy (or several). I'm not over thinking this, at all. I'm just challenged by it because this is my first driver disk project and I can't seem to find a full set of detailed requirements for building a successful driver disk (I have provided the rhdd, modinfo, pcitable, modules.cgz, and modules.dep files, but some important detail is still missing). ddiskit filled in some gaps, but I still don't have the specifications for what would cause, "No matching hardware was found on your system."
You're right. I could get my personal server up and running if I followed the steps on the tuxyturvy site, with your additional input, and a 4.1 ISO set. However, that would help only me and others like you and me who are competent with handling these low-level chores. I'm dealing with a bigger picture. I am deliberately trying to build a full-fledged driver disk that will help everyone else. In reality, our process is very complex to a newbie compared to the alternative: download a driver disk image from some web site and use it with the very convenient 'linux dd' install mode. I'm trying to provide that driver disk image; one that I can say works with confidence. That is my only goal. :) I'm not at all desperate to get this particular server running. If I was, I wouldn't be posting on this thread (or the threads that I've started, myself). :)
Part of my problem is that this is my hobby, which I only work on over the weekends. When I started this project, CentOS 4.0 was still available and in wide use. That said, you're right. There is no longer any point in trying to continue with 4.0. I just hope I can make a good driver disk before 4.1 becomes antiquated. :)
After all that, I hope that I have clearly asserted my objective, which isn't quite what you had previously assumed. :) You have helped me clarify some important details in the kernel matching requirements (I had no idea i586 and i686 sources couldn't be on the machine at the same time). Now, if you know where I might find all the specifications and troubleshooting details I need to make a working driver disk (aside from ddiskit), I'm all ears! :)
----- but a driver disk for this purpose is of little consequence.
1. The driver disk would have to be built with the i586 kernel-devel but when install was completed, it would fail to load the proper module and fail to boot. There is no way a driver disk would fix this problem unless this driver disk had all of the appropriate modules in place and the installer installed each of them to their respective locations and then ran the mkinitrd.
2. All subsequent kernel upgrades would require re-compile of the kernel module and rebuild of initrd after the kernel were installed - thus the driver disk would only further insulate the operator from the information that they would need to know. In fact, this step would probably be necessary almost immediately as I would suspect that a disproportionate amount of users having the LSI hardware raid hba would also be multi-processor and would need to build for smp kernel.
thus your endeavor to simplify isn't really gonna in the end, help all that much.
Craig
Craig White wrote:
thus your endeavor to simplify isn't really gonna in the end, help all that much.
We'll see. Driver disks have been working for years, far preceding CentOS. You just have to do it right. :)
For Centos4.4 I've got the 586 and 686 drivers on 2 floppies so far - recipe follows... Hope this helps someone. I'll try this on my HP and Acer, neither of which will install without intervention. I'll post part 2 of the recipe if it works out.
# recipe part 1 - make the driver disks using #http://www.tuxyturvy.com/blog/index.php?/archives/4-Installing-RHEL4-on-Syst... # modified for Centos4.4 as described in this thread #http://lists.centos.org/pipermail/centos/2005-August/010021.html # # Using Centos4.4Final i386 Disk 1 of 4 # # START # Install Centos4.4 disk 1 of 4 minimal on an old system # with floppy and PCI HD and net access mkdir /usr/src/software cd /usr/src/software wget http://www.tuxyturvy.com/files/megaraid2.tar.bz2 mkdir /usr/src/megaraid cd /usr/src/megaraid tar jxvfp /usr/src/sofware/megaraid2.tar.bz2 yum install gcc yum install kernel-devel-2.6.9-42.EL.i586 make -C /lib/modules/2.6.9-42.EL/build SUBDIRS=/usr/src/megaraid modules # # copy megaraid.ko to a floppy and label it megaraid-586 # mformat a: mount /media/floppy cp /usr/src/megaraid.ko /media/floppy umount /media/floppy # # then clean out the kernel-devel...to make way for the 686 version rpm -e kernel-devel yum install kernel-devel-2.6.9-42.EL.i686 # cd ../usr/src mv megaraid megaraid-586 mkdir megaraid cd megaraid tar jxvfp /usr/src/sofware/megaraid2.tar.bz2 make -C /lib/modules/2.6.9-42.EL/build SUBDIRS=/usr/src/megaraid modules # # then copy megaraid.ko to a floppy and label it megaraid-686 mformat a: mount /media/floppy cp /usr/src/megaraid.ko /media/floppy umount /media/floppy # # Take the floppies to the scsi system and follow recipe part 2 # I'll post that if it works out.
On Sat, 2007-01-20 at 17:37 +1100, David Booth wrote:
For Centos4.4 I've got the 586 and 686 drivers on 2 floppies so far - recipe follows... Hope this helps someone. I'll try this on my HP and Acer, neither of which will install without intervention. I'll post part 2 of the recipe if it works out.
# recipe part 1 - make the driver disks using #http://www.tuxyturvy.com/blog/index.php?/archives/4-Installing-RHEL4-on-Syst... # modified for Centos4.4 as described in this thread #http://lists.centos.org/pipermail/centos/2005-August/010021.html # # Using Centos4.4Final i386 Disk 1 of 4 # # START # Install Centos4.4 disk 1 of 4 minimal on an old system # with floppy and PCI HD and net access mkdir /usr/src/software cd /usr/src/software wget http://www.tuxyturvy.com/files/megaraid2.tar.bz2 mkdir /usr/src/megaraid cd /usr/src/megaraid tar jxvfp /usr/src/sofware/megaraid2.tar.bz2 yum install gcc yum install kernel-devel-2.6.9-42.EL.i586 make -C /lib/modules/2.6.9-42.EL/build SUBDIRS=/usr/src/megaraid modules # # copy megaraid.ko to a floppy and label it megaraid-586 # mformat a: mount /media/floppy cp /usr/src/megaraid.ko /media/floppy umount /media/floppy # # then clean out the kernel-devel...to make way for the 686 version rpm -e kernel-devel yum install kernel-devel-2.6.9-42.EL.i686 # cd ../usr/src mv megaraid megaraid-586 mkdir megaraid cd megaraid tar jxvfp /usr/src/sofware/megaraid2.tar.bz2 make -C /lib/modules/2.6.9-42.EL/build SUBDIRS=/usr/src/megaraid modules # # then copy megaraid.ko to a floppy and label it megaraid-686 mformat a: mount /media/floppy cp /usr/src/megaraid.ko /media/floppy umount /media/floppy # # Take the floppies to the scsi system and follow recipe part 2 # I'll post that if it works out.
---- hmmm...I remember that ;-)
glad my notations are helping
I vaguely recall some discussion that a centos plus kernel module for these old megaraid cards was going to be made available but I haven't seen any discussion about that.
a quick persusal in centos plus shows only a kernel-module for xfs but perhaps it is enabled in the centos plus kernel because if I recall correctly, appletalk is built into centos plus kernels and not separate module.
Craig
Craig White wrote:
hmmm...I remember that ;-)
glad my notations are helping
I hope my acknowledgement was sufficient. I found I needed to write myself a recipe condensing yours and the tuxyturvy one. Have still to execute part 2.
You had also written
"You could probably repeat for smp kernel if you have multiple processors"
I will need to do that but I don't know what you mean - do I need driver disks for that too?
___________ David Booth
On Sun, 2007-01-21 at 08:34 +1100, David Booth wrote:
Craig White wrote:
hmmm...I remember that ;-)
glad my notations are helping
I hope my acknowledgement was sufficient. I found I needed to write myself a recipe condensing yours and the tuxyturvy one. Have still to execute part 2.
You had also written
"You could probably repeat for smp kernel if you have multiple processors"
I will need to do that but I don't know what you mean - do I need driver disks for that too?
You should not need driver disks for install for an smp kernel.
The installer uses the regular kernel and not an smp kernel.
On Sat, Jan 20, 2007 at 04:03:41PM -0600, Johnny Hughes enlightened us:
Craig White wrote:
hmmm...I remember that ;-)
glad my notations are helping
I hope my acknowledgement was sufficient. I found I needed to write myself a recipe condensing yours and the tuxyturvy one. Have still to execute part 2.
You had also written
"You could probably repeat for smp kernel if you have multiple processors"
I will need to do that but I don't know what you mean - do I need driver disks for that too?
You should not need driver disks for install for an smp kernel.
The installer uses the regular kernel and not an smp kernel.
Well, you need them at install time in the sense that if you want the system to boot to the SMP kernel when your done installing, it has to be there.
Matt
Matt Hyclak wrote:
On Sat, Jan 20, 2007 at 04:03:41PM -0600, Johnny Hughes enlightened us:
Craig White had also written
"You could probably repeat for smp kernel if you have multiple processors"
I will need to do that but I don't know what you mean - do I need driver disks for that too?
You should not need driver disks for install for an smp kernel.
The installer uses the regular kernel and not an smp kernel.
Well, you need them at install time in the sense that if you want the system to boot to the SMP kernel when your done installing, it has to be there.
Matt
Thanks, but this doesn't help. I'm installing on an HP with dual processors. (And a dual processor Acer after that.)
Craig mentions "repeat for smp kernel" in the context of compiling the megaraid driver first with kernel-devel-xx.i586 and then again with kernel-devel-xx.686 and loading them at install time in a special sequence.
Is there something similar that needs to be done with kernel-smp-devel-xx.i586/686? Compile what? Load when?
Suppose I can get the megaraid scsi driver working and Centos4.4 installed and running: can I ignore the smp stuff and sort it out later?
On Sun, Jan 21, 2007 at 02:15:59PM +1100, David Booth enlightened us:
Matt Hyclak wrote:
On Sat, Jan 20, 2007 at 04:03:41PM -0600, Johnny Hughes enlightened us:
Craig White had also written
"You could probably repeat for smp kernel if you have multiple processors"
I will need to do that but I don't know what you mean - do I need driver disks for that too?
You should not need driver disks for install for an smp kernel.
The installer uses the regular kernel and not an smp kernel.
Well, you need them at install time in the sense that if you want the system to boot to the SMP kernel when your done installing, it has to be there.
Matt
Thanks, but this doesn't help. I'm installing on an HP with dual processors. (And a dual processor Acer after that.)
Craig mentions "repeat for smp kernel" in the context of compiling the megaraid driver first with kernel-devel-xx.i586 and then again with kernel-devel-xx.686 and loading them at install time in a special sequence.
Is there something similar that needs to be done with kernel-smp-devel-xx.i586/686? Compile what? Load when?
Suppose I can get the megaraid scsi driver working and Centos4.4 installed and running: can I ignore the smp stuff and sort it out later?
Yes, you'll just have to boot the UP kernel until you do. It should just be a matter of repeating the same steps with kernel-smp-devel and putting the resulting .ko files in /lib/modules/xxx.ELsmp
And actually, I don't think the 586 stuff is needed anymore since as of CentOS 4.4, the installer uses the i686 kernel unless you specifically request i586 on the boot line.
Matt
On Sat, 2007-01-20 at 22:21 -0500, Matt Hyclak wrote:
On Sun, Jan 21, 2007 at 02:15:59PM +1100, David Booth enlightened us:
Matt Hyclak wrote:
On Sat, Jan 20, 2007 at 04:03:41PM -0600, Johnny Hughes enlightened us:
Craig White had also written
"You could probably repeat for smp kernel if you have multiple processors"
I will need to do that but I don't know what you mean - do I need driver disks for that too?
You should not need driver disks for install for an smp kernel.
The installer uses the regular kernel and not an smp kernel.
Well, you need them at install time in the sense that if you want the system to boot to the SMP kernel when your done installing, it has to be there.
Matt
Thanks, but this doesn't help. I'm installing on an HP with dual processors. (And a dual processor Acer after that.)
Craig mentions "repeat for smp kernel" in the context of compiling the megaraid driver first with kernel-devel-xx.i586 and then again with kernel-devel-xx.686 and loading them at install time in a special sequence.
Is there something similar that needs to be done with kernel-smp-devel-xx.i586/686? Compile what? Load when?
Suppose I can get the megaraid scsi driver working and Centos4.4 installed and running: can I ignore the smp stuff and sort it out later?
Yes, you'll just have to boot the UP kernel until you do. It should just be a matter of repeating the same steps with kernel-smp-devel and putting the resulting .ko files in /lib/modules/xxx.ELsmp
---- yes - indeed ----
And actually, I don't think the 586 stuff is needed anymore since as of CentOS 4.4, the installer uses the i686 kernel unless you specifically request i586 on the boot line.
---- I didn't realize they had changed the boot disk - that makes the installation significantly easier and thus the tuxyturvy web site instructions are pretty much the ones to follow in that event as my instructions were for dealing with a i586 kernel from the CentOS install disks (substituting kernel versions of course since the kernel has incremented since the original release of RHEL-4).
Craig
Matt Hyclak wrote:
Yes, you'll just have to boot the UP kernel until you do. It should just be a matter of repeating the same steps with kernel-smp-devel and putting the resulting .ko files in /lib/modules/xxx.ELsmp
Don't you mean /lib/modules/`uname -r`/xxx.EXsmp?
Mike Fedyk wrote:
Matt Hyclak wrote:
Yes, you'll just have to boot the UP kernel until you do. It should just be a matter of repeating the same steps with kernel-smp-devel
What happens with the smp verson with insmod /media/floppy/megaraid.ko It was already done with the UP version, same filename.
and putting the resulting .ko files in /lib/modules/xxx.ELsmp
Don't you mean /lib/modules/`uname -r`/xxx.EXsmp?
I don't think so.
uname -r for me is 2.6.9-42.EL
But I have /lib/modules/2.6.9-42.EL and /lib/modules2.6.9-42.ELsmp
From the help so far I am proposing to: # Insert floppy with 686 version of megaraid.ko mount /media/floppy # Copy the 686 megaraid.ko module cp /media/floppy/megaraid.ko /mnt/sysimage/lib/modules/2.6.9-42.EL/kernel/drivers/scsi umount /media/floppy # Insert floppy with 686-smp version of megaraid.ko mount /media/floppy # Copy the smp686 megaraid.ko module cp /media/floppy/megaraid.ko /mnt/sysimage/lib/modules/2.6.9-42.ELsmp/kernel/drivers/scsi
and then
# set root to your newly installed system image chroot /mnt/sysimage vi /etc/modprobe.conf # make the line with 'alias scsi_hostadapter' say alias scsi_hostadapter megaraid # Save the file. :wq #Switch to the /boot directory cd /boot #Create new initrd files mkinitrd initrd-2.6.9-42.EL.img.megaraid 2.6.9-42.EL mkinitrd initrd-2.6.9-42.ELsmp.img.megaraid 2.6.9-42.ELsmp # #Copy the new initrd over old initrd cp initrd-2.6.9-42.EL.img.megaraid initrd-2.6.42-EL.img cp initrd-2.6.9-42.EL.img.megaraid initrd-2.6.42-ELsmp.img # Exit chroot environment exit # Switch back to the GUI installer Alt-F1 press Finish
On Sun, Jan 21, 2007 at 08:41:08PM +1100, David Booth enlightened us:
Mike Fedyk wrote:
Matt Hyclak wrote:
Yes, you'll just have to boot the UP kernel until you do. It should just be a matter of repeating the same steps with kernel-smp-devel
What happens with the smp verson with insmod /media/floppy/megaraid.ko It was already done with the UP version, same filename.
and putting the resulting .ko files in /lib/modules/xxx.ELsmp
Don't you mean /lib/modules/`uname -r`/xxx.EXsmp?
I don't think so.
uname -r for me is 2.6.9-42.EL
But I have /lib/modules/2.6.9-42.EL and /lib/modules2.6.9-42.ELsmp
From the help so far I am proposing to: # Insert floppy with 686 version of megaraid.ko mount /media/floppy # Copy the 686 megaraid.ko module cp /media/floppy/megaraid.ko /mnt/sysimage/lib/modules/2.6.9-42.EL/kernel/drivers/scsi umount /media/floppy # Insert floppy with 686-smp version of megaraid.ko mount /media/floppy # Copy the smp686 megaraid.ko module cp /media/floppy/megaraid.ko /mnt/sysimage/lib/modules/2.6.9-42.ELsmp/kernel/drivers/scsi
and then
# set root to your newly installed system image chroot /mnt/sysimage vi /etc/modprobe.conf # make the line with 'alias scsi_hostadapter' say alias scsi_hostadapter megaraid # Save the file. :wq #Switch to the /boot directory cd /boot #Create new initrd files mkinitrd initrd-2.6.9-42.EL.img.megaraid 2.6.9-42.EL mkinitrd initrd-2.6.9-42.ELsmp.img.megaraid 2.6.9-42.ELsmp # #Copy the new initrd over old initrd cp initrd-2.6.9-42.EL.img.megaraid initrd-2.6.42-EL.img cp initrd-2.6.9-42.EL.img.megaraid initrd-2.6.42-ELsmp.img # Exit chroot environment exit # Switch back to the GUI installer Alt-F1 press Finish
That sounds right to me.
Matt
Here is my recipe, tried and true, to compile and load megaraid.ko for HP Netserver LP 1000r using kernel-devel-2.6.9-42.EL and kernel-smp-devel-2.6.9-42.EL which matches my install disk, Centos4.4Final i386 Disk 1 of 4.
If you update the kernel after this you have to do it all again!
Sources: http://www.tuxyturvy.com/blog/index.php?/archives/4-Installing-RHEL4-on-Syst... http://lists.centos.org/pipermail/centos/2005-August/010021.html
# START # Install Centos4.4 on an old system with floppy, net and PCI HD # mkdir /usr/src/software cd /usr/src/software wget http://www.tuxyturvy.com/files/megaraid2.tar.bz2 mkdir /usr/src/megaraid cd /usr/src/megaraid tar jxvfp /usr/src/sofware/megaraid2.tar.bz2 # yum install kernel-devel-2.6.9-42.EL.i686 yum install kernel-smp-devel-2.6.9-42.EL.i686 # cd /usr/src mkdir megaraid cd megaraid tar jxvfp /usr/src/sofware/megaraid2.tar.bz2 make -C /lib/modules/2.6.9-42.EL/build SUBDIRS=/usr/src/megaraid modules cd /usr/src mv megaraid megaraid-686 mkdir megaraid cd megaraid tar jxvfp /usr/src/sofware/megaraid2.tar.bz2 make -C /lib/modules/2.6.9-42.ELsmp/build SUBDIRS=/usr/src/megaraid modules mv megaraid megaraid-smp-686 # # copy megaraid.ko to a floppies and label # insert new disk mformat a: mount /media/floppy cp /usr/src/megaraid-686/megaraid.ko /media/floppy umount /media/floppy # Label it megaraidUP686 # insert new disk mformat a: mount /media/floppy cp /usr/src/megaraid-smp-686/megaraid.ko /media/floppy umount /media/floppy # Label it megaraidSMP686 # # Now have 2 disks with megaraid.ko # # On the SCSI system, start the install with linux # and get to 'no suitable disk' # Alt-F2 rmmod megaraid_mbox rmmod megaraid_mm # insert the labelled megaraidUP686 mkdir /mnt/floppy mount /dev/fd0 /mnt/floppy insmod /mnt/floppy/megaraid.ko # Verify that the module loaded lsmod # see if megaraid is listed # Verify that your RAID array was found Alt-F4 # look for 'megaraid' in the output from the module load # switch back to the normal install screen Alt-F1 # Since you've manually loaded the driver from the command prompt # ignore the instructions to pick a driver. Continue the install. # After all packages are installed and the system prompts you to reboot: ! DON"T DO IT! # Because the megaraid driver was installed manually the installer will # not build a proper initrd. # Fix this before the reboot right now with the following steps: # # switch from the GUI to a bash prompt Alt-F2 # megaraidUP686 floppy is`still in the floppy drive cp /mnt/floppy/megaraid.ko /mnt/sysimage/lib/modules/2.6.9-42.EL/kernel/drivers/scsi umount /mnt/floppy # Insert floppy labelled megaraidSMP686 mount /dev/fd0 /media/floppy # Copy the smp megaraid.ko module cp /media/floppy/megaraid.ko /mnt/sysimage/lib/modules/2.6.9-42.ELsmp/kernel/drivers/scsi # set root to your newly installed system image chroot /mnt/sysimage vi /etc/modprobe.conf # make the line with 'alias scsi_hostadapter' say alias scsi_hostadapter megaraid # Save the file. :wq #Switch to the /boot directory cd /boot #Create new initrd files /sbin/mkinitrd initrd-2.6.9-42.EL.img.megaraid 2.6.9-42.EL /sbin/mkinitrd initrd-2.6.9-42.ELsmp.img.megaraid 2.6.9-42.ELsmp # #Copy the new initrd over old initrd cp initrd-2.6.9-42.EL.img.megaraid initrd-2.6.42-EL.img cp initrd-2.6.9-42.EL.img.megaraid initrd-2.6.42-ELsmp.img # Exit chroot environment exit # Switch back to the GUI installer Alt-F1 reboot # FINISH ___________ David Booth
On Tue, Jan 23, 2007 at 07:56:32AM +1100, David Booth enlightened us:
Here is my recipe, tried and true, to compile and load megaraid.ko for HP Netserver LP 1000r using kernel-devel-2.6.9-42.EL and kernel-smp-devel-2.6.9-42.EL which matches my install disk, Centos4.4Final i386 Disk 1 of 4.
If you update the kernel after this you have to do it all again!
Sources: http://www.tuxyturvy.com/blog/index.php?/archives/4-Installing-RHEL4-on-Syst... http://lists.centos.org/pipermail/centos/2005-August/010021.html
# START # Install Centos4.4 on an old system with floppy, net and PCI HD # mkdir /usr/src/software cd /usr/src/software wget http://www.tuxyturvy.com/files/megaraid2.tar.bz2 mkdir /usr/src/megaraid cd /usr/src/megaraid tar jxvfp /usr/src/sofware/megaraid2.tar.bz2 # yum install kernel-devel-2.6.9-42.EL.i686 yum install kernel-smp-devel-2.6.9-42.EL.i686 # cd /usr/src mkdir megaraid cd megaraid tar jxvfp /usr/src/sofware/megaraid2.tar.bz2 make -C /lib/modules/2.6.9-42.EL/build SUBDIRS=/usr/src/megaraid modules cd /usr/src mv megaraid megaraid-686 mkdir megaraid cd megaraid tar jxvfp /usr/src/sofware/megaraid2.tar.bz2 make -C /lib/modules/2.6.9-42.ELsmp/build SUBDIRS=/usr/src/megaraid modules mv megaraid megaraid-smp-686 # # copy megaraid.ko to a floppies and label # insert new disk mformat a: mount /media/floppy cp /usr/src/megaraid-686/megaraid.ko /media/floppy umount /media/floppy # Label it megaraidUP686 # insert new disk mformat a: mount /media/floppy cp /usr/src/megaraid-smp-686/megaraid.ko /media/floppy umount /media/floppy # Label it megaraidSMP686 # # Now have 2 disks with megaraid.ko # # On the SCSI system, start the install with linux # and get to 'no suitable disk' # Alt-F2 rmmod megaraid_mbox rmmod megaraid_mm # insert the labelled megaraidUP686 mkdir /mnt/floppy mount /dev/fd0 /mnt/floppy insmod /mnt/floppy/megaraid.ko # Verify that the module loaded lsmod # see if megaraid is listed # Verify that your RAID array was found Alt-F4 # look for 'megaraid' in the output from the module load # switch back to the normal install screen Alt-F1 # Since you've manually loaded the driver from the command prompt # ignore the instructions to pick a driver. Continue the install. # After all packages are installed and the system prompts you to reboot: ! DON"T DO IT! # Because the megaraid driver was installed manually the installer will # not build a proper initrd. # Fix this before the reboot right now with the following steps: # # switch from the GUI to a bash prompt Alt-F2 # megaraidUP686 floppy is`still in the floppy drive cp /mnt/floppy/megaraid.ko /mnt/sysimage/lib/modules/2.6.9-42.EL/kernel/drivers/scsi umount /mnt/floppy # Insert floppy labelled megaraidSMP686 mount /dev/fd0 /media/floppy # Copy the smp megaraid.ko module cp /media/floppy/megaraid.ko /mnt/sysimage/lib/modules/2.6.9-42.ELsmp/kernel/drivers/scsi # set root to your newly installed system image chroot /mnt/sysimage vi /etc/modprobe.conf # make the line with 'alias scsi_hostadapter' say alias scsi_hostadapter megaraid # Save the file. :wq #Switch to the /boot directory cd /boot #Create new initrd files /sbin/mkinitrd initrd-2.6.9-42.EL.img.megaraid 2.6.9-42.EL /sbin/mkinitrd initrd-2.6.9-42.ELsmp.img.megaraid 2.6.9-42.ELsmp # #Copy the new initrd over old initrd cp initrd-2.6.9-42.EL.img.megaraid initrd-2.6.42-EL.img cp initrd-2.6.9-42.EL.img.megaraid initrd-2.6.42-ELsmp.img # Exit chroot environment exit # Switch back to the GUI installer Alt-F1 reboot # FINISH
Looks great to me. Can you get this on the Wiki?
Matt
David Booth wrote:
Here is my recipe, tried and true, to compile and load megaraid.ko for HP Netserver LP 1000r using kernel-devel-2.6.9-42.EL and kernel-smp-devel-2.6.9-42.EL which matches my install disk, Centos4.4Final i386 Disk 1 of 4.
If you update the kernel after this you have to do it all again!
This should go on the Wiki under http://wiki.centos.org/HardwareList, if you are interested to put it there ...
Cheers,
Ralph
Beware of doing business with Alex Bajan at Raqport.
In January 2007 I ordered and paid over US$2000 for a Tyan GS14 server and some installation and migration services. The server proved to be faulty. It would not stay up for more than a few hours. I followed all of Alex's recommendations, including replacing the RAM, the processor and reinstalling the CentOS/Bluequartz operating system but the device would spontaneously attempt to reboot at random intervals of less than a few hours. My guess is a faulty motherboard component.
I returned the device at my expense but months later I have had no satisfaction from Raqport regarding a replacement or refund of the money I sent - not even replies to emails or returned calls.
It is a very poor way to treat a customer. ___________ David Booth
On 9/1/07, David Booth md@goulburn.net.au wrote:
Beware of doing business with Alex Bajan at Raqport.
In January 2007 I ordered and paid over US$2000 for a Tyan GS14 server and some installation and migration services. The server proved to be faulty. It would not stay up for more than a few hours. I followed all of Alex's recommendations, including replacing the RAM, the processor and reinstalling the CentOS/Bluequartz operating system but the device would spontaneously attempt to reboot at random intervals of less than a few hours. My guess is a faulty motherboard component.
I returned the device at my expense but months later I have had no satisfaction from Raqport regarding a replacement or refund of the money I sent - not even replies to emails or returned calls.
It is a very poor way to treat a customer. ___________ David Booth _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
My experience with that company is not good either, they dont keep what they promisse
Here is my proposed recipe Part 2. Not tried. I'll post results. (unless anyone (Craig?) can spot a problem before I try)
# On the SCSI system, boot normally and get to 'no suitable disk' # Alt-F2 rmmod megaraid_mbox rmmod megaraid_mm # insert the floppy with the 586 megamedia.ko mount /media/floppy insmod /media/floppy/megaraid.ko # # from tuxytyrvy: # Verify that the module loaded lsmod # see if megaraid is listed # Verify that your RAID array was found Alt-F4 # see the output from the module load # switch back to the normal install screen Alt-F7 #Since you've manually loaded the driver from the command prompt # ignore the instructions to pick a driver. Continue the install. # After all packages are installed and the system prompts you to reboot: ! DON"T DO IT! # Because the megaraid driver was installed manually the installer will # not build a proper initrd. # Fix this before the reboot right now with the following steps: # # switch from the GUI to a bash prompt Ctrl-Alt-F2 # look for the PATH to sysimage - ???? # may not be '/mnt' as documented by Craig df # Unmount floppy with 586 version of megaraid.ko and # insert and mount the 686 one! umount /media/floppy # Insert floppy with 686 version of megaraid.ko mount /media/floppy # Copy the megaraid.ko module with the command cp /media/floppy/megaraid.ko /PATH/sysimage/lib/modules/2.6.9-42.EL/kernel/drivers/scsi # set your root to your newly installed system image chroot /PATH/sysimage vi /etc/modprobe.conf # make the line with 'alias scsi_hostadapter' say 'alias scsi_hostadapter megaraid' # Save the file. #Switch to the /boot directory cd /boot #Create new initrd file mkinitrd initrd-2.6.9-42.EL.img.megaraid 2.6.9-42.EL #Copy the new initrd over old initrd cp initrd-2.6.9-42.EL.img.megaraid initrd-2.6.42-EL.img #Exit chroot environment exit # Switch back to the GUI installer Alt-F7 and press Finish ___________ David Booth
Yeah, I need to actually figure out how to rebuild an installation CD to use them, or just dump them on a CD-R, because I pretty much can't get any of the old FDD's to work, on any of the ancient machines I see around here.
Peter David Booth wrote:
For Centos4.4 I've got the 586 and 686 drivers on 2 floppies so far - recipe follows... Hope this helps someone. I'll try this on my HP and Acer, neither of which will install without intervention. I'll post part 2 of the recipe if it works out.
# recipe part 1 - make the driver disks using #http://www.tuxyturvy.com/blog/index.php?/archives/4-Installing-RHEL4-on-Syst...
# modified for Centos4.4 as described in this thread #http://lists.centos.org/pipermail/centos/2005-August/010021.html # # Using Centos4.4Final i386 Disk 1 of 4 # # START # Install Centos4.4 disk 1 of 4 minimal on an old system # with floppy and PCI HD and net access mkdir /usr/src/software cd /usr/src/software wget http://www.tuxyturvy.com/files/megaraid2.tar.bz2 mkdir /usr/src/megaraid cd /usr/src/megaraid tar jxvfp /usr/src/sofware/megaraid2.tar.bz2 yum install gcc yum install kernel-devel-2.6.9-42.EL.i586 make -C /lib/modules/2.6.9-42.EL/build SUBDIRS=/usr/src/megaraid modules # # copy megaraid.ko to a floppy and label it megaraid-586 # mformat a: mount /media/floppy cp /usr/src/megaraid.ko /media/floppy umount /media/floppy # # then clean out the kernel-devel...to make way for the 686 version rpm -e kernel-devel yum install kernel-devel-2.6.9-42.EL.i686 # cd ../usr/src mv megaraid megaraid-586 mkdir megaraid cd megaraid tar jxvfp /usr/src/sofware/megaraid2.tar.bz2 make -C /lib/modules/2.6.9-42.EL/build SUBDIRS=/usr/src/megaraid modules # # then copy megaraid.ko to a floppy and label it megaraid-686 mformat a: mount /media/floppy cp /usr/src/megaraid.ko /media/floppy umount /media/floppy # # Take the floppies to the scsi system and follow recipe part 2 # I'll post that if it works out.
-
Ajay Sharma -
Craig White -
David Booth -
Johnny Hughes -
Matt Hyclak -
Mike Fedyk -
Peter Serwe -
Ralph Angenendt -
Tronn Wærdahl -
William