2005-09-08 21:18:54

by Mike Miller

[permalink] [raw]
Subject: can't boot 2.6.13

I am not able to boot the 2.6.13 version of the kernel. I've tried different systems, tried downloading again, still nothing. Here's the last thing I see from the serial port:

md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
input: AT Translated Set 2 keyboard on isa0060/serio0
VFS: Mounted root (ext2 filesystem).
logips2pp: Detected unknown logitech mouse model 1
input: PS/2 Logitech Mouse on isa0060/serio1
SCSI subsystem initialized
Fusion MPT base driver 3.03.02
Copyright (c) 1999-2005 LSI Logic Corporation

The console shows the reiserfs module loaded and then the message

waiting for /dev/sda2 to appear

It then dumps a list of devices and sda is not one of them. I've attached the entire boot log if any one is interested.

I've tried statically linking cciss on another system and the same basic results. Apparently, MPT cannot be statically linked unless I missed something.

What do I have to do to get 2.6.13 to boot up?

Thanks,
mikem


Attachments:
(No filename) (0.99 kB)
2613boot.txt (31.18 kB)
Download all attachments

2005-09-08 22:52:32

by Eric Moore

[permalink] [raw]
Subject: RE: can't boot 2.6.13

On Thursday, September 08, 2005 3:19 PM, Mike Miller(HP) wrote:
> I am not able to boot the 2.6.13 version of the kernel. I've
> tried different systems, tried downloading again, still
> nothing. Here's the last thing I see from the serial port:
>
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> RAMDISK: Compressed image found at block 0
> input: AT Translated Set 2 keyboard on isa0060/serio0
> VFS: Mounted root (ext2 filesystem).
> logips2pp: Detected unknown logitech mouse model 1
> input: PS/2 Logitech Mouse on isa0060/serio1
> SCSI subsystem initialized
> Fusion MPT base driver 3.03.02
> Copyright (c) 1999-2005 LSI Logic Corporation
>

We introduced split drivers for 2.6.13. There are new layer drivers
that sit ontop of mptscsih.ko. These drivers are split along bus
protocal, so there is mptspi.ko, mptfc.ko, and mptsas.ko. This is
to tie into the scsi transport layers that are split the same.

For 1030(a SPI controller)
If your using RedHat, you need to change mptscish to mptspi in
/etc/modprobe.conf.
If your using SuSE, you need to change mptscish to mptspi in
/etc/sysconfig/kernel

2005-09-08 23:24:05

by Mike Miller

[permalink] [raw]
Subject: RE: can't boot 2.6.13

Thanks, Eric.
Anyone have any ideas why my cciss based system won't boot?

mikem

> -----Original Message-----
> From: Moore, Eric Dean [mailto:[email protected]]
> Sent: Thursday, September 08, 2005 5:52 PM
> To: Miller, Mike (OS Dev); [email protected];
> [email protected]
> Cc: [email protected]; [email protected]
> Subject: RE: can't boot 2.6.13
>
> On Thursday, September 08, 2005 3:19 PM, Mike Miller(HP) wrote:
> > I am not able to boot the 2.6.13 version of the kernel. I've tried
> > different systems, tried downloading again, still nothing.
> Here's the
> > last thing I see from the serial port:
> >
> > md: Autodetecting RAID arrays.
> > md: autorun ...
> > md: ... autorun DONE.
> > RAMDISK: Compressed image found at block 0
> > input: AT Translated Set 2 keyboard on isa0060/serio0
> > VFS: Mounted root (ext2 filesystem).
> > logips2pp: Detected unknown logitech mouse model 1
> > input: PS/2 Logitech Mouse on isa0060/serio1 SCSI subsystem
> > initialized Fusion MPT base driver 3.03.02 Copyright (c)
> 1999-2005 LSI
> > Logic Corporation
> >
>
> We introduced split drivers for 2.6.13. There are new layer
> drivers that sit ontop of mptscsih.ko. These drivers are
> split along bus protocal, so there is mptspi.ko, mptfc.ko,
> and mptsas.ko. This is to tie into the scsi transport layers
> that are split the same.
>
> For 1030(a SPI controller)
> If your using RedHat, you need to change mptscish to mptspi
> in /etc/modprobe.conf.
> If your using SuSE, you need to change mptscish to mptspi in
> /etc/sysconfig/kernel
>
>

2005-09-09 06:46:30

by Jens Axboe

[permalink] [raw]
Subject: Re: can't boot 2.6.13

On Thu, Sep 08 2005, Miller, Mike (OS Dev) wrote:
> Thanks, Eric.
> Anyone have any ideas why my cciss based system won't boot?

Hmm I thought Eric's suggestion was quite good, it bit me on a tiger as
well (you have to set _SPI or _FCI variant of the driver now). I see no
CISS detection at all, if your system has both perhaps the driver got
left out?

A boot log from a working system would help a lot.

--
Jens Axboe