From: Alex <alex@meerkatsoft.com>
To: Christian Kivalo <valo@valo.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Cannot boot after new Kernel Build
Date: Sun, 11 Jan 2004 01:19:44 +0900 [thread overview]
Message-ID: <40002620.2060205@meerkatsoft.com> (raw)
In-Reply-To: <NMEHJKFGFEGJPIPOLFFEIEBEDEAA.valo@valo.at>
Hi,
yes I already tried /dev/hda3 but still get the same errors when booting.
Alex
Christian Kivalo wrote:
>>Hi,
>>I tried changing the fstab, removing the LABLE from the grub.conf,
>>removing initrd from it and also tried to boot with
>>/dev/hda3. Nothing
>>works, still the same problem.
>>
>>
>
>hi!
>
>you don't have to change your fstab, there should everything ok with you
>fstab.
>
>you should change the root= entry in your grub configuration to your
>actual root partition. if you don't know what partition your root is on,
>do a 'df' and look where '/' is mounted on.
>
>the second line of df output should read somewhat similar to:
>/dev/sda2 4806936 1611232 2951516 36% /
>
>that's my fileserver where /dev/sda2 is mounted as '/'.
>
>your root= in grub config should read somewhat like this:
>root=/dev/hda1)
>
>hth
>christian
>
>
>
>>Alex
>>
>>
>>
>
>-
>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/
>
>
>
>
next prev parent reply other threads:[~2004-01-10 16:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 8:21 Cannot boot after new Kernel Build Alex
2004-01-10 9:37 ` Bongani Hlope
2004-01-10 15:08 ` Christian Kivalo
2004-01-10 15:43 ` Alex
2004-01-10 16:10 ` Christian Kivalo
2004-01-10 16:19 ` Alex [this message]
2004-01-11 5:34 ` Joseph Fannin
2004-01-11 6:04 ` Kernel 2.4.20 RH Cannot set DMA Alex
-- strict thread matches above, loose matches on Subject: below --
2004-01-11 3:33 Cannot boot after new Kernel Build Zhu, Yi
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=40002620.2060205@meerkatsoft.com \
--to=alex@meerkatsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=valo@valo.at \
/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