[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

AW: kernel compile on RS6000 7043-260

Hi Pat,

thanks for Your fast reply, but that isn't it.
I did exactly what You wrote before, so the sym53c8xx
and scsi disk IS in config flagged with "Y".
When I compare the top of the logs, there's already
something different. The original kernel loads ramdisk first
and later finds the cramfs and mounts it.
The new kernel does a chrp-boot...
Must really have to do with initrd/cramfs/ramdisk.

BTW I just want to build my own kernel to get rid of
the IDE support in the original kernel, since the "noprobe"
kernel argument doesn't work and this adds about 2 minutes
boot time for probing something, that isn't really there.
Maybe noprobe is fixed in a newer kernel, but as far as I know,
2.6.11 is the last 32bit-smp-kernel. And although I'm on a 64-bit
machine, I'd like to use the 32-bit environment for compatibility
reasons to an older ppc-machine here.


> -----Urspruengliche Nachricht-----
> Von: Patrick Finnegan [mailto:pat@computer-refuge.org]
> Gesendet: Freitag, 26. August 2005 17:24
> An: rsps@netterchef.de
> Cc: debian-powerpc@lists.debian.org
> Betreff: Re: kernel compile on RS6000 7043-260
> On Friday 26 August 2005 08:44, Ralph wrote:
> > Hi !
> >
> > As I finally do have my 7043-260 up and running with
> > kernel 2.6.11 power3 smp, I went to try to build my
> > own kernel. Needless to say: not very successfull.
> > Although I did (as one can read in lots of howtos) configure
> > all the important modules to drive my disk as mandatory, the
> > new created kernel does always the same when it should do
> > something different, as the log of my good old kernel shows.
> > Must be something with initrd/cramfs/ramdisk, when i interpret
> > the logfiles in the right way...
> > (see logs below)
> >
> > What am I doing wrong ?
> It looks like you're not including the correct SCSI driver:
> Make sure that "SYM53C8XX" under "SCSI low-level drivers" is turned on, 
> as well as "SCSI disk support".  I'd compile those into the kernel 
> ("Y") instead of as modules, just to be safe.
> Pat
> -- 
> Purdue University ITAP/RCS        ---  http://www.itap.purdue.edu/rcs/
> The Computer Refuge               ---  http://computer-refuge.org

Reply to: