linux-alpha.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bob Tracy <rct@gherkin.frus.com>
To: linux-alpha@vger.kernel.org
Cc: debian-alpha@lists.debian.org
Subject: X11 on Alpha running Debian "sid"
Date: Mon, 8 Oct 2018 13:49:27 -0500	[thread overview]
Message-ID: <20181008184927.GA7997@gherkin.frus.com> (raw)

It had been an *extremely* long time since I dared try to run a graphical
console on my PWS 433au, so I screwed-up my courage and gave it a try...

"sddm" is extremely slow to initialize, and even slower to respond to
both keyboard and mouse input.  Usually, this means something screwy
going on with acceleration, which historically has barely worked on this
platform anyway.  AIGLX is something new showing up in the "Xorg.log.0"
file that wasn't there the last time I had X11 working (which should
tell you something about how long it has been), so that's a prime suspect.

On the system configuration side of things, the video card is a Radeon 7500
(RV200), which is pretty much as good as it gets on the Alpha.  Modern Xorg
releases do a respectable job of figuring things out on their own as far as
not needing to override anything (or at least not much) in a "xorg.conf"
file, so I moved that out of the way as part of the debugging effort.
That didn't make any difference as best I can tell, i.e., the display
still initializes properly, and while Xorg.0.log has a lot more
information related to "figuring things out" in it, there's nothing
there to raise an eyebrow.

KDE and GNOME are both elephantine on a 1.5 GB machine in 2018, so I'm
attempting to run with AfterStep.  It seems to mostly work, or *will*
when I replace all the "x-terminal-emulator" in-/re-direction going on
in the Wharf configuration.  Out of the box, the configuration seems
predisposed to use the gnome terminal, whereas AfterStep should default
to aterm --> urxvt.

So, if someone can provide a hint or three as to how to make "sddm" more
responsive, that would be much appreciated.  Alternatively, if I need to
be using a different display manager, suggestions would be appreciated
as long as they're window-manager-agnostic.  In particular, substantial
dependencies on KDE infrastructure should probably be avoided :-(.

--Bob


                 reply	other threads:[~2018-10-08 18:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20181008184927.GA7997@gherkin.frus.com \
    --to=rct@gherkin.frus.com \
    --cc=debian-alpha@lists.debian.org \
    --cc=linux-alpha@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;
as well as URLs for NNTP newsgroup(s).