Date: Sat, 3 Jan 2004 12:46:49 +0100
To: linux-kernel@vger.kernel.org
Subject: switching to 2.6 on SATA system
Message-ID: <20040103114649.GA31181@margo.student.utwente.nl>
Mail-Followup-To: simon, linux-kernel@vger.kernel.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
From: Simon Oosthoek <simon@margo.student.utwente.nl>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1412
Lines: 34

Hi all

I'm having a lot of trouble getting a 2.6 kernel up and running on my pc[1].
I have a working 2.4 based install (mandrake 9.2) and I installed a cooker
snapshot with the 2.6 kernel on it as well. the snapshot also uses a 2.4
kernel to boot from.

One problem is that I get a kernel panic ("Bad EIP Value"), but I can solve
that by giving the option "pnpbios=off" to the kernel, so that is not
critical anymore.

The biggest problem is that apparently 2.4 kernels don't see SATA drives as
SCSI and 2.6 kernels do. I believe that lilo on 2.4 puts a root-partition
address in a different format than 2.6 expects, causing it to fail when it
is looking for the init script.

The failure (from memory) comes down to "please specify init= option to the
kernel", but all I could find in the documentation was something about a
linuxrc, which I could not find anywhere on the disk.

I'm wondering if this could be solved by compiling libata in the 2.4 kernel
and thus have 2.4 use the same addressing of the disks? Wouldn't this give
the same bootstrap problem I have with 2.4 and 2.6?

Cheers

Simon  

[1] intel bonanza i875pbz (bios vP18) + P4 + 2xSATA maxtor disks
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/