SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I recently installed Slackware in dual boot beside Arch.
I am sure there might be dozen of things to consider or look at but I am not clear as to how to proceed with the folowing.
I installed rxvt-unicode from Slackbuild.org and it seems not to respond as fast as it does when used in Arch. There is that fraction of a second where it seems to hang when typing.
Out of curiosity, I modified the slackbuild script to reflect the PKGBUILD in Arch, reinstalled rxvt and yet no improvement.
IIRC a possible culprit *could* be the nouveau version included in Slackware 13.37, as I observed that with it but not with a more recent one nor with the blob that I am right now using.
But I usually run xterm, not rxvt-unicode. Did you try with an xterm and does that make any difference?
I will switch to nouveau later today and will tell you if I still observe this behavior.
Meanwhile, what are your GPU kernel driver + X module used for video? If it's Intel or ATI my assumption can be safely moved to /dev/null "lspci -k| grep -A3 VGA" is usually enough to answer that.
OTOH, would it be right you just would have to wait a few days till Slackware 14 be released (if, indeed, you are not already running Slackware-current).
Last edited by Didier Spaier; 09-19-2012 at 02:32 AM.
My Arch installation uses the nvidia driver. If I find time and boot Arch, I should probably try to install the nouveau driver for comparison purposes.
I am running Slackware 13.37 at the moment.
I briefly tried xterm. Hard to tell. I will see if I can customize it a bit i.e. no border, black background and see how it goes.
@fl0. No I don't use antialiasing In fact, this is my configuration
Quote:
URxvt.termName:rxvt
URxvt.transparent: true
URxvt.inheritPixmap: false
URxvt.scrollBar: false
URxvt.savelines: 1000
URxvt.urlLauncher: firefox
URxvt.cursorBlink: true
URxvt.geometry: 93x26
URxvt.fading: 25%
urxvt.font: xft:Bitstream Vera Sans Monoixelsize=11
urxvt.boldfont: xft:Bitstream Vera Sans Mono:boldixelsize=11
urxvt.depth: 32
urxvt.background: rgba:0000/0000/0000/dddd
!URxvt.foreground: grey80
URxvt.tintColor: #262626
URxvt.borderLess: true
URxvt.borderColor: #888888
I can't try now (it's late in Paris) but tomorrow I will switch ton nouveau in both Slackware 13.37 and Slackware current. If I see a difference I will try a more recent version of nouveau in Slackware 13.37 and tell you the results, both with xterm and urxvt.
Nothing really obvious here using nouveau. I have an awk script started from an xterm and spitting one line of text every 4 seconds. Sometime the first horizontal half of a line line is displayed first, then the second half. But the script is very CPU hungry so that may not be significant.
You could check that the nouveau driver *could* be involved with "cp /etc/X11/xorg.conf.vesa /etc/X11/xorg.conf" and restart X to see if there is any change using the vesa driver instead of nouveau.
Last edited by Didier Spaier; 09-20-2012 at 07:18 AM.
Nothing really obvious here using nouveau. I have an awk script started from an xterm and spitting one line of text every 4 seconds. Sometime the first horizontal half of a line line is displayed first, then the second half. But the script is very CPU hungry so that may not be significant.
You could check that the nouveau driver *could* be involved with "cp /etc/X11/xorg.conf.vesa /etc/X11/xorg.conf" and restart X to see if there is any change using the vesa driver instead of nouveau.
You mean an awk script on rxvt I presume... . The thing is it's really when I type text as opposed to when displaying say a long ls command which seem fine. Now looks like xterm behaves better. I will look at terminator too for comparison purposes.
You could check that the nouveau driver *could* be involved with "cp /etc/X11/xorg.conf.vesa /etc/X11/xorg.conf" and restart X to see if there is any change using the vesa driver instead of nouveau.
nouveau is a kernel mode setting driver, so that likely won't work unless the OP also blacklists it (and reboots).
nouveau is a kernel mode setting driver, so that likely won't work unless the OP also blacklists it (and reboots).
Good point. I just tried, and though Xorg.0.log show nothing weird, the nouveau kernel module becomes angry that his buddy the nouveau X module be discarded. To avenge this affront it spits so many[*] lines like this one in the logs
Code:
Sep 21 14:19:05 machine kernel: [ 118.325211] [drm] nouveau 0000:01:00.0: PFIFO_BAR_FAULT - VM: Trapped write at 0001075c78 status 00001a26 channel 0 (0x00000040)
that the system becomes *really* unresponsive
[*] 645 lines accounting for 106258 characters in one second.
Last edited by Didier Spaier; 09-21-2012 at 07:56 AM.
Reason: Tell how big is many
Well, I try rebooting with an xorg.conf but the screen resolution kind of suck. I set up terminator to my liking and will go with that. It has been a learning experience .
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.