Re: l4ka::pistachio boot problem

I tried booting it on qemu. However, it doesn't move ahead of the
point where it tries mounting the root file system (VFS root mount)
coz I can't figure out the correct "root=" option in the kernel
command line. my root file system is mounted on /dev/hda2. However,
when i try passing "root=/dev/hda2" in the kernel command line, then
mounting fails with error message "incorrect root option". somehow it
doesn't recognize /dev/hda2. any ideas what can be done now.

On Fri, Feb 15, 2008 at 5:34 AM, Jan Stoess <[email protected]> wrote:
> > -----Original Message-----
>  > From: Ashish Bijlani [mailto:[email protected]]
>  > Sent: Thursday, February 14, 2008 02:38
>  > To: Jan Stoess
>  > Cc: [email protected]
>  > Subject: Re: l4ka::pistachio boot problem
>  >
>  > Hi Jan,
>  >
>  > This is exactly what I did to build l4ka-pistachio and marzipan with
>  > afterburner. I downloaded afterburner and tried building it. It
>  > internally downloaded everything into a single build dir (including
>  > linux-2.6.9 and xen).
>
>  It seems my comment was a bit misleading: it's not only that we don't use
>  the CVS anymore, the source code base in the CVS is also older (and
>  different) compared to the code base in the now-referenced HG repo.
>
>
>  > I used the default configs (make menuconfig in
>  > the build dir) except I'm using VGA as opposed to serial in the
>  > default configs. Did I miss anything important? Any thoughts about the
>  > above problem?
>
>  OK. I don't know of anybody in our group using anything else than serial
>  ports
>  for console I/O for development, so the VGA could very well be the problem.
>  The repo currently works with VGA and qemu on my box, though. So you could
>  try
>  building for the qemu emulator yourself, and start from there. Just check
>  out
>  the HG repo, build the everything using the default config, and then run
>  "make
>  run-qemu". That should bring up the afterburner qemu.
>
>  If you then still get problems on a real box, you'll have to find the
>  culprit
>  for the null pointer dereference. I'd suggest to inspect wedge and linux
>  stack
>  contents to get a feeling where the problem stems from.
>
>
>
>  Regards,
>  -Jan
>
>
>  --
>  Jan Stoess
>  System Architecture Group
>  University of Karlsruhe
>  Phone: +49 (721) 608-4056
>  Fax: +49 (721) 608-7664
>  eMail: [email protected]
>