From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Simon Piette <simonp@Sat.QC.CA>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Video acceleration on IMSTT with bk (and Ben's) 2.4.7-pre6 kernel
Date: Thu, 19 Jul 2001 23:52:31 +0100 [thread overview]
Message-ID: <20010719225238.8EC81DBB59@atlas.valhalla.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
> I just compiled 2.4.7pre6 from Ben's tree, and another one from bk, with
> the same results. It compiled without any problems, but I can't have
> accelerated video. I use "video=imsttfb:vmode:17,cmode:16 video=ofonly"
> as kernel args to have a working unaccelerated video. Without ofonly, I
> get some blue dots forming a very distortioned screen of what should be
> there (linux logo and kernel verbosity). Without the imsttfb part, it
> won't work after the initial boot screen: it stops after
[snip]
BK 2.4.7-pre6:
OK. It comes up for me 9600/233 with video acceleration and runs "single".
However, it won't start the X-server the error is something like:
_X11TransConnectUNIX??? errno = 111
Other symptom is that the splash screen #cpus penguin is missing it's
background.
exactly the same config boots 2.4.3 OK and starts the X-server OK.
dmesg attached - I think Ben already has the lspci stuff from this machine -
but I can send it again if needed.
ciao,
Iain.
[-- Attachment #2: dmesg-2.4.7p6 --]
[-- Type: audio/x-mpeg, Size: 4569 bytes --]
next reply other threads:[~2001-07-19 22:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 22:52 Iain Sandoe [this message]
2001-07-20 7:14 ` ISDN cards Giuliano Pochini
2001-07-20 8:10 ` Olaf Hering
2001-07-23 9:02 ` Albrecht Dreß
-- strict thread matches above, loose matches on Subject: below --
2001-07-20 15:09 Video acceleration on IMSTT with bk (and Ben's) 2.4.7-pre6 kernel Iain Sandoe
2001-07-20 10:49 Iain Sandoe
2001-07-20 20:14 ` Ani Joshi
2001-07-19 1:45 Simon Piette
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=20010719225238.8EC81DBB59@atlas.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=simonp@Sat.QC.CA \
/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).