Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
01-17-2015, 05:30 PM
|
#1
|
Member
Registered: Aug 2010
Location: USA
Distribution: Slackware 14.1, LFS (someday)
Posts: 40
Rep:
|
Fvwm2 slow to switch windows; shows grey screen inbetween.
I just upgraded from Slackware 13.1 to 14.1.
Now when I change windows in fvwm2
the screen turns gray before the 2nd window appears.
The system isnt overloaded - there's only 2 windows & I checked 'top'.
Also when there's no windows and a window is created -
at first it is gray for an annoying split second
(this didnt happen in sw13.1).
I'm using fvwm2.4 (from slackware 13.1)
instead of fvwm2.6 (from slackware 14.1)
because fvwm2.6 required 5 more extra packages that I didnt want:
librsvg,
libgdx,
libffi,
libcroco,
libxml2.
Please, please dont just tell me to use number 2.6.
Fvwm2.6 starts up using 'dbus-launch'
so i made fvwm2.4 do the same
(thru /etc/X11/xinit/xinitrc and /usr/bin/startfvwm2).
(Probably a red herring?)
I'm still using the stock huge-smp kernel.
Could it be the framebuffer or double-buffering?
I dont even know how to check/enable those.
I'm using an old computer:
Pentium 4
512 MB RAM
nVidia GeForce FX5200 GPU
I'm not using the "nouveau" driver (but the package is installed).
I'm using the "nv" driver.
The "nouveau-blacklist" package is also installed (to get kbd & mouse to work).
Attached are /etc/X11/xorg.conf & /var/log/Xorg.0.log.
/etc/X11/xorg.conf.d/ is empty.
Much thanks for all your time.
|
|
|
01-18-2015, 07:06 PM
|
#2
|
Member
Registered: Nov 2008
Location: US
Distribution: slackware
Posts: 821
|
Quote:
Originally Posted by rivercat
I'm using fvwm2.4 (from slackware 13.1)
|
Are you using the actual package from 13.1 or did you rebuild it ? If you are using the package I would suggest you rebuild from source.
Quote:
Originally Posted by rivercat
Please, please dont just tell me to use number 2.6.
|
The above is all I could suggest, I have been using 2.6 and 2.5 before that for many years so I do not have any other suggestions for 2.4
John
|
|
1 members found this post helpful.
|
01-18-2015, 11:29 PM
|
#3
|
Member
Registered: Aug 2010
Location: USA
Distribution: Slackware 14.1, LFS (someday)
Posts: 40
Original Poster
Rep:
|
I was hoping some one out there must have seen these annoying intermediate grey screens.
|
|
|
01-19-2015, 08:42 AM
|
#4
|
Member
Registered: Nov 2008
Location: US
Distribution: slackware
Posts: 821
|
I thought you were asking about a fvwm2 specific issue. What happens under other window managers ? twm or fluxbox ?
I wonder if nvidia is the issue. What happens with nouveau ? Are you using the correct driver ? Seems there are 5 different drivers, see:
nvidia. I need to use version 304.125
|
|
1 members found this post helpful.
|
01-19-2015, 11:12 PM
|
#5
|
Member
Registered: Aug 2010
Location: USA
Distribution: Slackware 14.1, LFS (someday)
Posts: 40
Original Poster
Rep:
|
I uninstalled fvwm 2.4, and installed 2.6 with the nescecary library packages.
Still the grey screens.
I guess I'll try fluxbox next.
Last edited by rivercat; 01-19-2015 at 11:17 PM.
Reason: to edit
|
|
|
01-20-2015, 02:18 PM
|
#6
|
Member
Registered: Aug 2010
Location: USA
Distribution: Slackware 14.1, LFS (someday)
Posts: 40
Original Poster
Rep:
|
I tried the "nvidia" driver but it says I need to recompile my kernel for a module.
I've done that, but for me it takes a few days.
I also tried the "fbdev" and "vesa" X drivers, but they had the same problem.
That seems important.
If the grey screens persisted with them, then I suppose its not an X driver problem,
and the "nvidia" route is a dead end.
Does anyone know any "xorg.conf" options that could be missing?
|
|
|
01-21-2015, 06:57 PM
|
#7
|
Member
Registered: Nov 2008
Location: US
Distribution: slackware
Posts: 821
|
Quote:
Originally Posted by rivercat
I tried the "nvidia" driver but it says I need to recompile my kernel for a module.
|
How did you install it ? I have never received that message using stock slackware kernels (in various releases). Are you using the stock slackware kernel ?
Quote:
Originally Posted by rivercat
Does anyone know any "xorg.conf" options that could be missing?
|
nivida asks you if you want to generate a xorg.conf, I have said yes and it seems to work form me. Somewhere in here LQ Slackware there is a thread about xorg.conf and nvidia
|
|
1 members found this post helpful.
|
01-22-2015, 02:52 AM
|
#8
|
Member
Registered: Aug 2010
Location: USA
Distribution: Slackware 14.1, LFS (someday)
Posts: 40
Original Poster
Rep:
|
I'm using the stock kernel "huge-smp-3.10.17".
Its headers and source packages are installed too.
I wont go with the "generic" kernels as I dont like initrd's, but I will recompile soon.
The actual error message I get from the nvidia driver installer is:
"Unable to determine the NVIDIA kernel module filename."
How can it be on my system if its not compiled yet?
sh-4.2$ find / -iname '*nvidia*'
/lib/modules/3.10.17-smp/kernel/drivers/char/agp/nvidia-agp.ko
/lib/modules/3.10.17-smp/kernel/drivers/video/nvidia/nvidiafb.ko
/usr/src/linux-3.10.17/drivers/char/agp/nvidia-agp.c
/usr/src/linux-3.10.17/drivers/video/nvidia/nvidia.c
/usr/src/linux-3.10.17/include/config/fb/nvidia
/usr/src/linux-3.10.17/include/config/fb/nvidia.h
/usr/src/linux-3.10.17/include/config/agp/nvidia.h
/usr/src/linux-3.10.17/include/config/net/vendor/nvidia.h
The following is taken from the driver's README:
A kernel module,
(/lib/modules/`uname -r`/video/nvidia.o or
/lib/modules/`uname -r`/kernel/drivers/video/nvidia.o),
provides low-level access to your NVIDIA hardware.
It is generally loaded into the kernel when the X server is started, and is used by the X driver and OpenGL.
nvidia.o consists of two pieces: the binary-only core, and a kernel interface that must be compiled specifically for your kernel version.
Note that the Linux kernel does not have a consistent binary interface like the X server,
so it is important that this kernel interface be matched with the version of the kernel that you are using.
This can either be accomplished by compiling yourself,
or using precompiled binaries provided for the kernels shipped with some of the more common Linux distributions.
|
|
|
01-22-2015, 03:05 AM
|
#9
|
Member
Registered: Aug 2010
Location: USA
Distribution: Slackware 14.1, LFS (someday)
Posts: 40
Original Poster
Rep:
|
Slackware 14.1 (with the 13.10.17 kernel) was released 2013-11-07. (slackware.com/index.html)
Nvidia driver 173.14.39 was released 2013-12-07. (devtalk.nvidia.com/default/topic/655258)
Maybe Nvidia didnt have time to build-in precompiled compatability into their legacy driver package?
|
|
|
01-24-2015, 09:27 AM
|
#10
|
Member
Registered: Nov 2008
Location: US
Distribution: slackware
Posts: 821
|
Everything I see points it should work. The only other suggestion I have is to try
Code:
/usr/bin/nvidia-settings
maybe that would help out, that is installed for me when I installed the 304 driver.
|
|
1 members found this post helpful.
|
All times are GMT -5. The time now is 08:03 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|