public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Wise, Jeremey" <jeremey.wise@agilysys.com>
To: "David B. Stevens" <dsteven3@maine.rr.com>,
	linux-kernel@vger.kernel.org,
	"Marcos D. Marado Torres" <marado@student.dei.uc.pt>
Subject: Re: Kernel or Grub bug.
Date: Wed, 01 Sep 2004 08:20:27 -0400	[thread overview]
Message-ID: <1094041227.4635.7.camel@wizej.agilysys.com> (raw)
In-Reply-To: <200408312358.08153.dsteven3@maine.rr.com>

[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]

On Tue, 2004-08-31 at 23:58 -0400, David B. Stevens wrote:
> Jeremey,
> 
> It might help if you had attached the failing kernel config file and a copy of 
> your /etc/fstab  it appears that whatever file system you have root on is not 
> recognized by the kernel.  
> 
> Cheers,
>   Dave
> 
Thanks for all the replies. I will have to second all that Marcos D.
Marado Torres <marado@student.dei.uc.pt> has said. I did notice that my
post of grub.conf config in the original email lacked the
"root=/dev/hda3" as I had made so many attempts to get it to boot with
other people's suggestions (fat finger:>) Just to ensure full testing I
redid all test inputs "root=/dev/hda3" and also "root=0303" and also
tried a Fedora Core box with the same kernel and initrd with the above
and also a "root=LABEL-/" with the same error. 


Here are both the config file (copied from /proc/config.gz) and the one
I am attempting to get to work (using the same kind of option selection
I know works with my 2.4.x tree.



-- 
Thanks,

Jeremey Wise
jeremey.wise@agilysys.com

All opinions or information expressed here are personal in nature and do
not reflect the official position of Agilysys Inc.

[-- Attachment #2: config-2.6.5-7.104-default.gz --]
[-- Type: application/x-gzip, Size: 15089 bytes --]

[-- Attachment #3: config-2.6.8.1.gz --]
[-- Type: application/x-gzip, Size: 10358 bytes --]

  parent reply	other threads:[~2004-09-01 12:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-01  3:12 Kernel or Grub bug Wise, Jeremey
2004-09-01  4:28 ` Prasad
2004-09-01  5:20   ` Marcos D. Marado Torres
2004-09-01  6:16     ` prasad
2004-09-01  6:55       ` Marcos D. Marado Torres
2004-09-01 13:40   ` Horst von Brand
2004-09-01  5:24 ` Obelix
     [not found] ` <200408312358.08153.dsteven3@maine.rr.com>
2004-09-01 12:20   ` Wise, Jeremey [this message]
     [not found]     ` <200409011135.36537.dsteven3@maine.rr.com>
2004-09-01 16:26       ` Wise, Jeremey
     [not found]         ` <4699bb7b04090109415f64fea1@mail.gmail.com>
2004-09-01 19:40           ` Wise, Jeremey
2004-09-02 21:33             ` Valdis.Kletnieks
2004-09-03 14:29               ` Marcos D. Marado Torres
2004-09-01 19:46           ` Wise, Jeremey
2004-09-02 21:02         ` Horst von Brand
2004-09-02 22:53           ` David B. Stevens
2004-09-02 23:25           ` David B. Stevens
2004-09-03  0:31             ` David Lloyd
2004-09-03  2:15               ` David B. Stevens
2004-09-03  0:37           ` Johann Koenig
2004-09-19 10:03           ` Yury Umanets
2004-09-20 14:27             ` Tonnerre

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1094041227.4635.7.camel@wizej.agilysys.com \
    --to=jeremey.wise@agilysys.com \
    --cc=dsteven3@maine.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marado@student.dei.uc.pt \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox