From: Thomas Capricelli <capricel@enst.fr>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: long-term 7600-booting patch
Date: Tue, 2 Nov 1999 13:33:04 +0100 [thread overview]
Message-ID: <9911021333290B.13454@uranium> (raw)
>> As my 2.1.125 kernel from linuxppc R4 was always fine but I need to
>> boot new kernels, I've made this patch. Not that I understand a lot of what
>> i've done, mainly backporting the mesh code from 2.1.125.
>>
>> At least, my mac now always BOOT. Before applying this patch, I had to
>> try between 6 and 16 times to boot my computer. You DON'T know how tiring this
>> is
>
>Can you please try a 2.3.x kernel? I suffered from a similar problem and it was
>solved in 2.3.x.
My macintosh still won't boot with 2.3.24 until my pacth is applied.
This problem is here since march, 1999. on all >2.2.0 kernel.
Also, the stock-linux-2.3.24 is really a pain to compile. The kernel won't link
until pmu is added (pmu is powerbook-related stuff), and some other minor
problems.
Also, I don't dare to compile anything as module anymore, cause most of
them won't link when insmod'ed. (unresolved symbols such as memcpy...)
Those two last problems are here since at least 2.3.18, probably much
more longer.
Thomas
--
Thomas Capricelli
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-11-02 12:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-02 12:33 Thomas Capricelli [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-10-27 14:45 long-term 7600-booting patch Thomas Capricelli
1999-10-27 16:33 ` Geert Uytterhoeven
1999-10-27 16:41 ` Thomas Capricelli
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=9911021333290B.13454@uranium \
--to=capricel@enst.fr \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).