From: Fabrice Eudes <fabrice@oberon.ambre.fr>
To: linux-kernel@vger.kernel.org
Cc: "Club LinuX" <clx@gaia.anet.fr>,
"Utilisateurs Debian Français"
<debian-user-french@lists.debian.org>
Subject: [Re: Can't boot 2.4.17 or 2.5.1 kernel] problem solved ?!
Date: Thu, 7 Feb 2002 02:55:23 +0100 [thread overview]
Message-ID: <20020207015523.GA1267@oberon.ambre.fr> (raw)
[anglophobes, ne lisez pas la suite :-)]
Hi !
Le Mon, Feb 04, 2002 at 08:51:19PM +0100, Jose Luis Domingo Lopez a
écrit:
> One day I tried again to boot those "problematic" kernels from the
> same
> PC, now upgraded to Woody, and the problems appeared in the same
> places.
> One thing that I noticed is that Alan's 2.4.x-acY kernels had no
> problems booting where plain 2.4.x kernels failed.
thanks a lot for the tip !
I compiled a kernel from the "plain" 2.4.13 sources with the ac-8 patch
and it works fine.
haaa... my radeon works and I can play tuxracer; great !
more seriously, thanks to all the people making the ac kernel-variants.
Just one more -silly?- question: it seems -for me at least- that some
of the ac patches should be integrated in the kernel, why aren't they ?
(I repeat that ANY 2.4.17 variant I compiled won't even boot ! I'm not
talking about kernel panic here)
is my hardware so exotic ??
thanks again.
PS: it worked also with a 2.4.13-ac5 :-)
PPS: I don't mind to buils a few more kernel to identify which part(s)
of the ac patches is(are) responsible of this non-non-booting ;-)
situation but I need someone to guide me.
PPPS: I'll have some time in a week; tomorrow I go skiing 8-)
--
Stéphanie, Fabrice et Fiona -o)
stephanie.dupuis@free.fr /\\
fabrice.eudes@free.fr _\_V
next reply other threads:[~2002-02-07 1:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 1:55 Fabrice Eudes [this message]
2002-02-07 2:09 ` Alan Cox
2002-02-07 4:55 ` William Lee Irwin III
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=20020207015523.GA1267@oberon.ambre.fr \
--to=fabrice@oberon.ambre.fr \
--cc=clx@gaia.anet.fr \
--cc=debian-user-french@lists.debian.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®