From: Martin Costabel <costabel@wanadoo.fr>
To: ramp@oddjob.uchicago.edu
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: devel kernels 2.3.41
Date: Mon, 31 Jan 2000 08:20:50 +0100 [thread overview]
Message-ID: <389537D2.D4642F0A@wanadoo.fr> (raw)
In-Reply-To: Pine.LNX.4.10.10001302151040.3009-100000@xpol.uchicago.edu
The 2.3.41 final kernel is broken on most non-intel architectures (dma
code changed completely). I would think (and hope) the PPC kernel
developers are too busy fixing this right now to answer your question.
And many people, even on intel hardware, are seeing file system
corruption with 2.3.x kernels. Plus, the new USB code probably doesn't
work yet.
So for non-kernel-developers this means to be patient for a while.
ramp@oddjob.uchicago.edu wrote:
>
> Hi everyone,
>
> I hope I'm not the only one having problems getting a working
> 2.3.41 kernel. I downloaded the stock 2.3.41 from kernel.org.
> This one didn't even compile. There were some problems with
> pci.h. I then decided to go back to 2.3.40 and apply the
> pre-patches [1..4] where 4 is the final 2.3.41. I was able
> to successfully compile a 2.3.41pre3. However on boot I was
> unable to use my keyboard/mouse. The boot messages seemed to
> indicate that the keyboard and mouse were recognized. Any ideas
> and fixes? 2.3.41pre2 also compiled successfully. On boot this
> led to disk errors and I was asked to fsck. This was a total loss
> since I could not type anything with the keyboard and mouse not
> even recognized. I'm now back to my 2.2.14 and things seem OK.
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-01-31 7:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B4B7C54D.602%pajama1@mindspring.com>
2000-01-30 3:56 ` HFS+ format Brad Boyer
2000-01-30 13:58 ` Olaf Hering
2000-01-31 4:04 ` devel kernels 2.3.41 ramp
2000-01-31 7:20 ` Martin Costabel [this message]
2000-01-31 21:23 ` Kevin M. Myer
2000-01-31 22:22 ` Martin Costabel
2000-02-01 17:18 ` Ani Joshi
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=389537D2.D4642F0A@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=ramp@oddjob.uchicago.edu \
/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).