From: Mads Christensen <mfc@krycek.org>
To: Paul Rolland <rol@as2917.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: cannot boot 2.5.67
Date: 17 Apr 2003 20:27:24 +0200 [thread overview]
Message-ID: <1050604044.1136.4.camel@krycek> (raw)
In-Reply-To: <01b401c3050d$7f441d70$6400a8c0@witbe>
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
Common mistake i guess - but dude, never move old .config files to new
kernel dirs - patch the kernel, review the config (make menuconfig) and
recompile!
Regards
On tor, 2003-04-17 at 20:16, Paul Rolland wrote:
> Hello,
>
> > You have to get
> > CONFIG_INPUT=y, CONFIG_VT=y and CONFIG_VT_CONSOLE=y
> > inorder for you to see anything =)
> Yes, I guess I have that, as I'm using the .config from a 2.5.66
> that was booting quite fine...
>
> Anyhow, you are right, maybe that moving .config from a release to
> another one is not 100% safe...
>
> Regards,
> Paul
--
===================================================
| Mads F. Christensen || |
| Email: || mfc@krycek.org |
| Webdesign Development || www.krycek.org |
===================================================
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-04-17 18:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 17:03 cannot boot 2.5.67 Pau Aliagas
2003-04-17 17:16 ` Paul Rolland
2003-04-17 17:46 ` Mads Christensen
2003-04-17 17:54 ` Randy.Dunlap
2003-04-17 18:18 ` Paul Rolland
2003-04-17 17:56 ` Valdis.Kletnieks
2003-04-22 15:28 ` Pau Aliagas
2003-04-22 17:03 ` Valdis.Kletnieks
2003-04-22 18:25 ` Russell King
2003-04-24 20:14 ` Bill Davidsen
2003-04-17 18:16 ` Paul Rolland
2003-04-17 18:27 ` Mads Christensen [this message]
2003-04-18 4:07 ` Felipe Alfaro Solana
2003-04-17 18:36 ` John Bradford
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=1050604044.1136.4.camel@krycek \
--to=mfc@krycek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rol@as2917.net \
/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;
as well as URLs for NNTP newsgroup(s).