linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Robert E Brose II <bob@kunk.jriver.com>
To: mlan@cpu.lu
Cc: linuxppc-devel@lists.linuxppc.org
Subject: Re: controlfb and X (fixed)
Date: Sun, 19 Nov 2000 22:39:44 -0600 (CST)	[thread overview]
Message-ID: <20001120050245.2300.qmail@kunk.jriver.com> (raw)
In-Reply-To: <200011191036.LAA00685@piglet.grunz.lu> "from Michel Lanners at Nov 19, 2000 11:36:30 am"


User Michel Lanners says:
>
> > Which 2.4.0 kernel source are YOU using?
>
> I'm running BenH's 2.5 kernel, that's the only one I was able to boot on
> my 7600. Paulus' 2.4 kernels lock my machine 90% of the time at boot. I
> haven't found what's wrong with them, though...
>
> BenH's kernel is at:
>
> rsync -arvz penguinppc.org::linux-benh-devel .
>
> Happy compiling ;-)

FINALLY got the 2.4.0-test10 benh kernel going.
I had to turn off a bunch of stuff to get it to run (i.e. to avoid
the black screen of death on boot) and I'm not sure the
PPP async driver works yet, had to compile it as a module.

The controlfb driver now senses the 4m video memory properly
on the 7500.

XFree4.01 runs (though the keyboard is messed up. I have to investigate
the new input layer)

The stock XFree86 (XFree86-3.3.6-11.2) also works in 24/32 bits now!!!
HOORAY!! Hopefully the changes will eventually make it to the stock
trees.

Thanks Michel!

Bob
--
Robert E. Brose II    N0QBJ
http://www.jriver.com/~bob/
bob@kunk.jriver.com


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

       reply	other threads:[~2000-11-20  4:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200011191036.LAA00685@piglet.grunz.lu>
2000-11-20  4:39 ` Robert E Brose II [this message]
2000-11-07 21:22 controlfb and X bob
2000-11-18 18:31 ` controlfb and X (fixed) Michel Lanners

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=20001120050245.2300.qmail@kunk.jriver.com \
    --to=bob@kunk.jriver.com \
    --cc=linuxppc-devel@lists.linuxppc.org \
    --cc=mlan@cpu.lu \
    /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).