[WBEL-users] Re: Respin 1 and 3w-9xxx.o
Robert
rbc331@charter.net
Sat, 18 Sep 2004 21:33:56 -0400
This is a multi-part message in MIME format.
------=_NextPart_000_001C_01C49DC7.33A26530
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
----- Original Message -----=20
From: Kurt Haegeman=20
To: rbc331@charter.net=20
Sent: Thursday, September 16, 2004 7:11 AM
Subject: Respin 1 and 3w-9xxx.o
Hi Robert,
I saw your posting on the WhiteBox mailing archive.
I'm having the same problem, trying to install WBEL on a 3Ware =
9500S-12MI controller. I can get the module running if I boot from =
another controller, but had no luck getting it to run from WBEL =
installation. And since the servers normally only have the 3Ware, I'm =
kinda stuck here.
None of the downloadable driver disks from 3Ware work, and a =
self-compiled version gives lots of unresolved symbol errors.
I was wondering if you ever got it working since you posted this =
message. If so, would you be so kind to help me out?
Thanks in advance. Regards,
Kurt Haegeman
IT Manager
Mediargus.be
=
-------------------------------------------------------------------------=
-----------------------
Hi Kurt,
I'm sending this reply to the mailing list in case someone else has =
ideas on this subject. Sorry for the delay in replying but we had a =
hurricane (Ivan) come thru here recently. Also I was experimenting with =
a work-around for the problem and wanted to be able to report some =
degree of success or failure.
/RANT ON/
I'm assuming that it's the x86_64 version of Respin 1 you are =
referring to. IIRC, I was able to compile to compile drivers that worked =
with the i386 version without much problem. If you are talking i386, let =
me know and I can probably fix you up. :)
Like you, I was able to install if I put an IDE drive in and installed =
to that. I could then produce drivers (UP and SMP) that would let me =
access my the SATA drives on my 9500 controller. But I could not boot =
from SATA and I don't want to have to rely on a single-point-of-failure =
IDE drive for booting in the future. So I invested a great deal of time =
and energy trying to produce a driver that would work with the Respin 1 =
Install cds. I thought that using the ia32e config in lieu of the =
i386-BOOT config should do it, but no such luck. It would load without =
error messages but just NOT WORK. Someone smarter than me needs to dig =
into the kernel the cd is booting and tell us what kind of voodoo is =
needed to produce compatible drivers.
So I finally gave up on that. It's been educational, but expensive =
time-wise. :( I'm hoping that the next respin will provide some relief.
/RANT OFF/
In the meanwhile I'm trying a work-around. I discovered during the =
above that the driver disk available at the 3Ware website actually work =
just fine with the RC1 version which is still available on the mirrors. =
So I took the approach of installing to my SATA drives using RC1 and =
then upgrading. When I received your message, I was at the point where I =
had felt my way thru it, but then broke it experimenting with a =
different problem. So I needed to redo it cleanly and decided to =
document the process a bit since it's not entirely straightforward. I'm =
including the procedure I used at the end of this message. If anyone =
else wants to try this approach it will probably save them some time. If =
you want me to send you the drivers rather than build them yourself, let =
me know. They are about 500KB each.
So that's where I currently stand in trying to deal with this. Other =
ideas, anybody?
Robert
For anyone interested, here's the writeup:
Getting WBEL 3.0-x86_64 Respin 1 running with only 3Ware 9500 =
controlled disks (sort of)
WARNING: Produced by a Linux n00b who has learned enough to be =
dangerous. Please point out my misconceptions!
Install RC1 from cd with driver disk available from 3Ware's website.
Copy contents of RedHat/RPMS from all 3 Respin 1 cds into a single =
work directory. 1208 rpm files (1.4G).
Boot into UP mode if not already there.
Go to the directory where you put the rpms. Install the 2.4.21-15.EL =
kernel source (not sure this is necessary, but seemed like a good idea =
to me). Try to install the corresponding x86_64 UP kernel. This will =
fail reporting no module 3w-9xxx found for that kernel. Go into =
/usr/src/linux-2.4.21-4.EL and edit the Makefile changing EXTRAVERSION =
from -4.ELcustom to -15.EL.
(next step not needed if you don't use 3Ware's perl script - see below =
- but the script hangs trying to do 'make oldconfig' on this guy if you =
don't do something to get around it)
Copy the kernel-2.4.21-i386-BOOT.config file from the configs =
directory to .config in the current one. Do make oldconfig accepting the =
defaults. Do it again (it will find stuff it missed the first time). =
Copy .config replacing the kernel-2.4.21-i386-BOOT.config file in the =
configs directory. You will throw away the driver that this config =
produces.
Do a make mrproper to clean things up a bit. Copy the =
kernel-2.4.21-x86_64.config file from the configs directory to .config =
in the current one. Next do 'make dep'. If we were compiling a kernel, =
we would continue with 'make clean', 'make bzImage', etc. But we don't =
need any of that.
(The rest of this assumes you are using 3Ware's script. If you want to =
go under the hood and run your own 'make -f Makefile.rh xxx's, you can =
cut out a few steps here and there.)
Grab the sources from the 3Ware web site. You'll have a perl script =
'Build-3w-driver.pl' and a '3w-9xxx.tgz' file that the script will =
extract the actual sources, Makefile, etc. from. Create a /home/build =
directory (the script expects it to exist). Run the script (perl =
Build-3w-driver.pl -s path/if/needed/3w-9xxx.tgz.
Go into /home/build and grab a copy of the UP driver. There are a =
couple of them lying around. Drop it into =
/lib/modules/2.4.21-15.EL/kernel/drivers/scsi/ naming it 3w-9xxx.o. =
Probably want to turn execute permission on (not sure needed but won't =
hurt).
Go back to where you put the rpms. Do rpm -e kernel-2.4.21-15.EL. This =
will remove the stuff that the failed install above left lying around =
but will leave your new driver in place. Redo the kernel install that =
failed before. Now it should work.
Again go into /usr/src/linux-2.4.21-4.EL and edit the Makefile this =
time changing EXTRAVERSION from to -15.ELsmp. Redo the copy and 'make =
proper' thru 'make dep' steps this time using the SMP config file. Clear =
out /home/build and redo the Build-3w-driver.pl script to get a usable =
SMP driver.
Try to install the SMP kernel. You'll get the same failure. Grab the =
SMP driver out of /home/build and drop it into =
/lib/modules/2.4.21-15.ELsmp/kernel/drivers/scsi/ again naming it =
3w-9xxx.o (execute permission?). Do the same uninstall and reinstall =
procedure for the SMP kernel.
You should now be ready to reboot using a 2.4.21-15 kernel.
Go to where you stored all the rpms and do 'rpm -Fvh *'. It will churn =
for a few minutes, then spit out a list of Failed dependencies. Example: =
jaf is needed by ant-1.5.2-23. I got 19 listed. Basically go thru the =
list one-by-one installing the items needed. Occasionally have to use =
--force (elfutils for instance). In my case, glib-1.2.10-11.1.i386.rpm =
was needed even though glib-1.2.10-11.1.x86_64.rpm was already =
installed. Same deal with libtiff and gtk+. That seemed a little odd, =
but that's what made it work. Some of the libxxxx type entries were a =
little tricky to figure out what rpm provided them, but Google was my =
friend.
Once all those dependencies were pounded into submission, then 'rpm =
-Fvh *' was able to take off and freshen 199 packages. Only took a few =
minutes. Reboot just for the heck of it.
So I'm now running something I hope is pretty close to a Respin 1 =
install equivalent. Think I'll hold off on any up2date stuff for the =
moment, until I've tested this setup a little more. I can tell you from =
my previous attempts at this to beware of the glibc stuff in the updates =
section on the mirrors. That broke my system badly, reproducibly and =
reversibly (forcing the previous ones from the os directory to reinstall =
got things working again).
HTH :)
------=_NextPart_000_001C_01C49DC7.33A26530
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type =
content=3Dtext/html;charset=3DISO-8859-1>
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV><FONT size=3D2></FONT> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A title=3Dkurt.haegeman@mediargus.be=20
href=3D"mailto:kurt.haegeman@mediargus.be">Kurt Haegeman</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Drbc331@charter.net=20
href=3D"mailto:rbc331@charter.net">rbc331@charter.net</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Thursday, September 16, =
2004 7:11=20
AM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Respin 1 and =
3w-9xxx.o</DIV>
<DIV><BR></DIV>
<DIV><FONT size=3D-1><FONT face=3DVerdana>Hi Robert,<BR><BR>I saw your =
posting on=20
the WhiteBox mailing archive.<BR><BR>I'm having the same problem, =
trying to=20
install WBEL on a 3Ware 9500S-12MI controller. I can get the module =
running if=20
I boot from another controller, but had no luck getting it to run from =
WBEL=20
installation. And since the servers normally only have the 3Ware, I'm =
kinda=20
stuck here.<BR><BR>None of the downloadable driver disks from 3Ware =
work, and=20
a self-compiled version gives lots of unresolved symbol =
errors.<BR><BR>I was=20
wondering if you ever got it working since you posted this message. If =
so,=20
would you be so kind to help me out?<BR><BR>Thanks in advance.=20
Regards,<BR><BR>Kurt Haegeman<BR>IT=20
=
Manager<BR>Mediargus.be<BR>----------------------------------------------=
--------------------------------------------------</FONT></FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D-1><FONT face=3DVerdana><FONT=20
face=3DArial></FONT></FONT></FONT> </DIV>
<DIV><FONT size=3D-1><FONT face=3DVerdana><FONT face=3DArial>Hi=20
Kurt,</FONT></FONT></FONT></DIV>
<DIV><FONT size=3D-1><FONT face=3DVerdana><FONT=20
face=3DArial></FONT></FONT></FONT> </DIV>
<DIV><FONT size=3D-1><FONT face=3DVerdana><FONT face=3DArial>I'm =
sending this reply=20
to the mailing list in case someone else has ideas on this subject. =
Sorry for=20
the delay in replying but we had a hurricane (Ivan) come thru here =
recently.=20
Also I was experimenting with a work-around for the problem and wanted =
to be=20
able to report some degree of success or =
failure.</FONT></FONT></FONT></DIV>
<DIV><FONT size=3D-1><FONT face=3DVerdana><FONT=20
face=3DArial></FONT></FONT></FONT> </DIV>
<DIV><FONT size=3D-1><FONT face=3DVerdana><FONT face=3DArial>/RANT=20
ON/</FONT></FONT></FONT></DIV>
<DIV><FONT size=3D-1><FONT face=3DVerdana><FONT face=3DArial>I'm =
assuming that it's=20
the x86_64 version of Respin 1 you are referring to. IIRC, I was =
able to=20
compile to compile drivers that worked with the i386 version without =
much=20
problem. If you are talking i386, let me know and I can probably fix =
you up.=20
:)</FONT></FONT></FONT></DIV>
<DIV><FONT size=3D-1><FONT face=3DVerdana><FONT=20
face=3DArial></FONT></FONT></FONT> </DIV>
<DIV><FONT size=3D-1><FONT face=3DVerdana><FONT face=3DArial>Like you, =
I was able to=20
install if I put an IDE drive in and installed to that. I could then =
produce=20
drivers (UP and SMP) that would let me access my the SATA drives on my =
9500=20
controller. But I could not boot from SATA and I don't want to have to =
rely on=20
a single-point-of-failure IDE drive for booting in the future. So I =
invested a=20
great deal of time and energy trying to produce a driver that would =
work with=20
the Respin 1 Install cds. I thought that using the ia32e config in =
lieu of the=20
i386-BOOT config should do it, but no such luck. It would load without =
error=20
messages but just NOT WORK. Someone smarter than me needs to dig =
into the=20
kernel the cd is booting and tell us what kind of voodoo is needed to =
produce=20
compatible drivers.</FONT></FONT></FONT></DIV>
<DIV><FONT size=3D-1><FONT face=3DVerdana><FONT=20
face=3DArial></FONT></FONT></FONT> </DIV>
<DIV><FONT size=3D-1><FONT face=3DVerdana><FONT face=3DArial>So I =
finally gave up on=20
that. It's been educational, but expensive time-wise. :( I'm =
hoping that=20
the next respin will provide some relief.</FONT></FONT></FONT></DIV>
<DIV><FONT size=3D-1><FONT face=3DVerdana><FONT face=3DArial>/RANT=20
OFF/</FONT></FONT></FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D-1><FONT face=3DVerdana><FONT face=3DArial>In the =
meanwhile I'm=20
trying a work-around. I discovered during the above that the driver =
disk=20
available at the 3Ware website actually work just fine with the RC1 =
version=20
which is still available on the mirrors. So I took the approach of =
installing=20
to my SATA drives using RC1 and then upgrading. When I received your =
message,=20
I was at the point where I had felt my way thru it, but then broke it=20
experimenting with a different problem. So I needed to redo it cleanly =
and=20
decided to document the process a bit since it's not entirely =
straightforward.=20
I'm including the procedure I used at the end of this message. If =
anyone else=20
wants to try this approach it will probably save them some time. If =
you want=20
me to send you the drivers rather than build them yourself, let me =
know. They=20
are about 500KB each.</FONT></FONT></FONT></DIV>
<DIV><FONT size=3D-1><FONT face=3DVerdana><FONT=20
face=3DArial></FONT></FONT></FONT> </DIV>
<DIV><FONT size=3D-1><FONT face=3DVerdana><FONT face=3DArial>So that's =
where I=20
currently stand in trying to deal with this. Other ideas,=20
anybody?</FONT></FONT></FONT></DIV>
<DIV><FONT size=3D-1><FONT face=3DVerdana><FONT=20
face=3DArial></FONT></FONT></FONT> </DIV>
<DIV><FONT size=3D-1><FONT face=3DVerdana><FONT=20
face=3DArial>Robert</FONT></FONT></FONT></DIV>
<DIV><FONT size=3D-1><FONT face=3DVerdana><FONT=20
face=3DArial></FONT></FONT></FONT> </DIV>
<DIV><FONT size=3D-1><FONT face=3DVerdana><FONT face=3DArial>For =
anyone interested,=20
here's the writeup:</FONT></FONT></FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D-1><FONT face=3DVerdana><FONT=20
face=3DArial></FONT></FONT></FONT> </DIV>
<DIV><FONT size=3D-1><FONT size=3D2>
<P><FONT face=3DVerdana>Getting WBEL 3.0-x86_64 Respin 1 running with =
only 3Ware=20
9500 controlled disks (sort of)</FONT></P>
<P><FONT face=3DVerdana>WARNING: Produced by a Linux n00b who has =
learned enough=20
to be dangerous. Please point out my misconceptions!</FONT></P>
<P><FONT face=3DVerdana>Install RC1 from cd with driver disk available =
from=20
3Ware's website.</FONT></P>
<P><FONT face=3DVerdana>Copy contents of RedHat/RPMS from all 3 Respin =
1 cds=20
into a single work directory. 1208 rpm files (1.4G).</FONT></P>
<P><FONT face=3DVerdana>Boot into UP mode if not already =
there.</FONT></P>
<P><FONT face=3DVerdana>Go to the directory where you put the rpms. =
Install the=20
2.4.21-15.EL kernel source (not sure this is necessary, but seemed =
like a good=20
idea to me). Try to install the corresponding x86_64 UP kernel. This =
will fail=20
reporting no module 3w-9xxx found for that kernel. Go into=20
/usr/src/linux-2.4.21-4.EL and edit the Makefile changing EXTRAVERSION =
from=20
-4.ELcustom to -15.EL.</FONT></P>
<P><FONT face=3DVerdana>(next step not needed if you don't use 3Ware's =
perl=20
script - see below - but the script hangs trying to do 'make =
oldconfig' on=20
this guy if you don't do something to get around it)</FONT></P>
<P><FONT face=3DVerdana>Copy the kernel-2.4.21-i386-BOOT.config file =
from the=20
configs directory to .config in the current one. Do make oldconfig =
accepting=20
the defaults. Do it again (it will find stuff it missed the first =
time). Copy=20
.config replacing the kernel-2.4.21-i386-BOOT.config file in the =
configs=20
directory. You will throw away the driver that this config=20
produces.</FONT></P>
<P><FONT face=3DVerdana>Do a make mrproper to clean things up a bit. =
Copy the=20
kernel-2.4.21-x86_64.config file from the configs directory to .config =
in the=20
current one. Next do 'make dep'. If we were compiling a kernel, we =
would=20
continue with 'make clean', 'make bzImage', etc. But we don't need any =
of=20
that.</FONT></P>
<P><FONT face=3DVerdana>(The rest of this assumes you are using =
3Ware's script.=20
If you want to go under the hood and run your own 'make -f Makefile.rh =
xxx's,=20
you can cut out a few steps here and there.)</FONT></P>
<P><FONT face=3DVerdana>Grab the sources from the 3Ware web site. =
You'll have a=20
perl script 'Build-3w-driver.pl' and a '3w-9xxx.tgz' file that the =
script will=20
extract the actual sources, Makefile, etc. from. Create a /home/build=20
directory (the script expects it to exist). Run the script (perl=20
Build-3w-driver.pl -s path/if/needed/3w-9xxx.tgz.</FONT></P>
<P><FONT face=3DVerdana>Go into /home/build and grab a copy of the UP =
driver.=20
There are a couple of them lying around. Drop it into=20
/lib/modules/2.4.21-15.EL/kernel/drivers/scsi/ naming it 3w-9xxx.o. =
Probably=20
want to turn execute permission on (not sure needed but won't=20
hurt).</FONT></P>
<P><FONT face=3DVerdana>Go back to where you put the rpms. Do rpm -e=20
kernel-2.4.21-15.EL. This will remove the stuff that the failed =
install above=20
left lying around but will leave your new driver in place. Redo the =
kernel=20
install that failed before. Now it should work.</FONT></P>
<P><FONT face=3DVerdana>Again go into /usr/src/linux-2.4.21-4.EL and =
edit the=20
Makefile this time changing EXTRAVERSION from to -15.ELsmp. Redo the =
copy and=20
'make proper' thru 'make dep' steps this time using the SMP config =
file. Clear=20
out /home/build and redo the Build-3w-driver.pl script to get a usable =
SMP=20
driver.</FONT></P>
<P><FONT face=3DVerdana>Try to install the SMP kernel. You'll get the =
same=20
failure. Grab the SMP driver out of /home/build and drop it into=20
/lib/modules/2.4.21-15.ELsmp/kernel/drivers/scsi/ again naming it =
3w-9xxx.o=20
(execute permission?). Do the same uninstall and reinstall procedure =
for the=20
SMP kernel.</FONT></P>
<P><FONT face=3DVerdana>You should now be ready to reboot using a =
2.4.21-15=20
kernel.</FONT></P>
<P><FONT face=3DVerdana>Go to where you stored all the rpms and do =
'rpm -Fvh *'.=20
It will churn for a few minutes, then spit out a list of Failed =
dependencies.=20
Example: jaf is needed by ant-1.5.2-23. I got 19 listed. Basically go =
thru the=20
list one-by-one installing the items needed. Occasionally have to use =
--force=20
(elfutils for instance). In my case, glib-1.2.10-11.1.i386.rpm was =
needed even=20
though glib-1.2.10-11.1.x86_64.rpm was already installed. Same deal =
with=20
libtiff and gtk+. That seemed a little odd, but that's what made it =
work. Some=20
of the libxxxx type entries were a little tricky to figure out what =
rpm=20
provided them, but Google was my friend.</FONT></P>
<P><FONT face=3DVerdana>Once all those dependencies were pounded into=20
submission, then 'rpm -Fvh *' was able to take off and freshen 199 =
packages.=20
Only took a few minutes. Reboot just for the heck of it.</FONT></P>
<P><FONT face=3DVerdana>So I'm now running something I hope is pretty =
close to a=20
Respin 1 install equivalent. Think I'll hold off on any up2date stuff =
for the=20
moment, until I've tested this setup a little more. I can tell you =
from my=20
previous attempts at this to beware of the glibc stuff in the updates =
section=20
on the mirrors. That broke my system badly, reproducibly and =
reversibly=20
(forcing the previous ones from the os directory to reinstall got =
things=20
working again).</FONT></P>
<P><FONT face=3DVerdana>HTH :)</FONT></P>
<P><FONT=20
face=3DVerdana></FONT> </P></FONT></DIV></BLOCKQUOTE></FONT></BODY><=
/HTML>
------=_NextPart_000_001C_01C49DC7.33A26530--