fusion-MPT

Tue May 17 08:17:56 MDT 2005

Peter,

(1) you are welcome
(2) you should cite the bug number for the benefit of others who may
encounter this thread.

-Joseph

======================================================================
On Tue, 2005-05-17 at 14:38 +0100, peter.g.harper at magnox.co.uk wrote:
> Joseph,
> 
> There is already one there. I should have looked there before.
> 
> I've learnt a lot in the last few weeks.
> 
> Thanks for all your help.
> 
> Peter
> 
> 
> 
> 
> 
> "Joseph E. Sacco, Ph.D." <joseph_sacco at comcast.net> on 17/05/2005 14:08:20
> 
> Please respond to Yellow Dog Linux General Discussion List
>        <yellowdog-general at lists.terrasoftsolutions.com>
> 
> 
> 
> To:         Yellow Dog Linux General Discussion List
>             <yellowdog-general at lists.terrasoftsolutions.com>
> cc:          (bcc: Peter G Harper/Magnox/Berkeley/BNFL)
> Fax to:
> Subject:    Re: fusion-MPT
> 
> 
> 
> Looks like a regression bug. You should file a bug report at
> 
>         http://bugzilla.kernel.org/
> 
> -Joseph
> ==============================================================================
> 
> 
> On Tue, 2005-05-17 at 09:15 +0100, peter.g.harper at magnox.co.uk wrote:
> > Joseph,
> >
> > I did all of that, although I used mkinitrd rather than
> > /sbin/new-kernel-pkg.
> >  I've had to rebuild the kernel several times, first to apply the patch
> to
> > stop the fans from running at full speed, and then to enable Fibre
> Channel
> > and LVM
> > support, I'm getting quite comfortable with the process now. That all
> > worked perfectly for 2.6.8.
> >
> > I can build a kernel for 2.6.10 which works too, but when I add support
> for
> > the Fibre Channel
> > it just won't boot. It gets to the point in the boot process where it
> would
> > detect the Fibre Channel
> > disks and just stops. The same thing happened when I tried 2.6.9.
> >
> > I seem to have solved my particular problem now however. I took the
> 2.6.8.1
> > source from
> > www.kernel.org and patched in the tree below fs/ as well as
> > include/linux/fs.h into the YDL
> > 2.6.8 and that built quite happily. The problem I had with NFS seems to
> > have gone.
> >
> > There just seem to be something in 2.6.9 and 2.6.10 that stops the kernel
> > from finding
> > the Fibre Channel disks.
> >
> >
> > Peter
> >
> >
> >
> >
> >
> >
> > "Joseph E. Sacco, Ph.D." <joseph_sacco at comcast.net> on 16/05/2005
> 18:16:41
> >
> >
> > To:         Peter G Harper/Magnox/Berkeley/BNFL at BNFL
> > cc:
> > Fax to:
> > Subject:    fusion-MPT
> >
> >
> >
> > When you rebuilt the kernel, what did you do to install the new kernel?
> > maybe there's an issue there.
> >
> > When I rebuild a kernel, it has a new name, for example
> >
> >       vmlinux-2.6.10-2
> >
> > Take a look at
> >
> >       path-to-kernel-source/include/linux/version.h
> >
> > to determine the name of your new kernel.
> >
> > * install kernel and system map
> >
> >       vmlinux -> /boot/vmlinux-2.6.10-2
> >         System.map -> /boot/System.map-2.6.10-2
> >
> > * install modules
> >
> >       make modules_install
> >
> > * generate a new /boot/initrd file
> >
> >       /sbin/new-kernel-pkg --rminitrd --rmmoddep --remove 2.6.10-2
> >       /sbin/new-kernel-pkg --mkinitrd --depmod --install 2.6.10-2
> >
> > * edit /etc/yaboot.conf
> > Add an entry for the new kernel:
> >
> >       image=/boot/vmlinux-2.6.10-2
> >         label=linux
> >         read-only
> >         initrd=/boot/initrd-2.6.10-2.img
> >         root=/dev/sdb4
> >         append="rhgb quiet"
> >
> > * install the yaboot boot loader to the bootstrap partition:
> > RUN:
> >        /sbin/ybin -v         [-v to see what it's doing]
> >
> > -Joseph
> >
> >
> > --
> > joseph_sacco [at] comcast [dot] net
> >
> >
> >
> >
> >
> >
> >
> > The information contained in this email may be commercially sensitive
> and/or legally privileged. It is intended solely for the person(s) to whom
> it is addressed. If you are not a named recipient, you are on notice of its
> status. Please notify the sender immediately by reply e-mail and then
> delete this message from your system. You must not disclose it to any other
> person, copy or distribute it or use it for any purpose.
> >
> > _______________________________________________
> > yellowdog-general mailing list
> > yellowdog-general at lists.terrasoftsolutions.com
> > http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
> > HINT: to Google archives, try  '<keywords> site:terrasoftsolutions.com'
> --
> joseph_sacco [at] comcast [dot] net
> 
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general at lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
> HINT: to Google archives, try  '<keywords> site:terrasoftsolutions.com'
> 
> 
> 
> 
> 
> 
> The information contained in this email may be commercially sensitive and/or legally privileged. It is intended solely for the person(s) to whom it is addressed. If you are not a named recipient, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. You must not disclose it to any other person, copy or distribute it or use it for any purpose.
> 
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general at lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
> HINT: to Google archives, try  '<keywords> site:terrasoftsolutions.com'
-- 
joseph_sacco [at] comcast [dot] net