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.
For me Kde 4.5.1 starts with desktop effects switched off. But If I press Alt+Shift+F12 two times (one to switch effects off besides the fact that it is already switched off, and second time to switch it on), Effects starts to work. On each reboot I have to repeat the procedure.
I think KDE for some reasons switches off the effects, while wrongly detects that hardware has no support for it. But manually it is still possible to switch it on.
Click here to see the post LQ members have rated as the most helpful post in this thread.
For me Kde 4.5.1 starts with desktop effects switched off. But If I press Alt+Shift+F12 two times (one to switch effects off besides the fact that it is already switched off, and second time to switch it on), Effects starts to work.
Other than xf86-video-radeonhd, all of the obsolete stuff was only present in the sources -- there were no packages. As such, the "upgradepkg --install-new *.t?z" in the appropriate arch directory is fine, and then do "removepkg xf86-video-radeonhd"
nouveau crashes flashplayer plugin in chrome in full screen
Well I finally got around to testing out the new X packages and nouveau, and everything seems fine, except that my flashplayer plugin crashes chrome when I go full screen. I blacklisted nouveau, changed to my regular nvidia xorg.conf and rebooted to test the proprietary driver and everything worked fine. This is with the 2.6.35.4 kernel built with the generic config posted here except for filesystem inclusion and CPU specific options selected instead of the generic selections because that's how I build all of my kernels anyway.
I didn't try it in any other browser since I very rarely use any other browser for watching flash videos.
In a nice side note, the NVIDIA installer now detects if you are using nouveau and will blacklist it for you if you choose to allow it.
Finally got around to playing with this today myself too.
Slackware64/current.
NVIDIA GT140 graphics card.
2.6.35.4 + nouveau built as module.
Installed all of robby's packages, rebooted to runlevel 3 and did a startx with no existing xorg.conf file.
Resulted in garbled/hung screen and had to do a SYSRQ-REISUB to get out of it. Looking at the xorg.log.0 file it seems that even when the nouveau module is loaded, it prefers to use the vesa module in it's default state and this reacted badly with nouveau.
I added
/etc/X11/xorg.conf.d/94-drivers.conf:
Code:
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
Section "Device"
Identifier "nouveau"
Driver "nouveau"
EndSection
/etc/X11/xorg.conf.d/95-screens.conf:
Code:
# **********************************************************************
# Screen sections
# **********************************************************************
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "nouveau"
# Monitor "My Monitor"
DefaultDepth 24
Subsection "Display"
Depth 24
Modes "1280x1024"
EndSubsection
EndSection
... and everything is working like a charm.
Other than the above, the only other thing I had to change was to set 90-keyboard to 'gb'.
glxgears, and some of the xscreensavers GL hacks work nicely, as does xcompmgr which I've been using on top of WindowMaker. mplayer and xine videos seem to be fine too. Not tried it with KDE4 as I don't have that installed any more (gave up on it).
On the whole pretty impressed. Thanks Robby. I'll look forward to seeing this stuff hit current. You just need to be careful with this vesa/nv/nouveau incompatibility as it might be a little daunting for some of the newer users.
With no xorg.conf and Compositing Type set to OpenGL in KDE 4.4.5 I have all desktop effects including the cube.
I have added a /etc/X11/xorg.conf.d/50-synaptics.conf file containing:
This enables circular scrolling, horizontal two finger scroll and my preferences for tap buttons on my touchpad.
All is working well for me, but I have not done any of the September updates to -current as yet.
I have performed the -current updates for September to date i.e KDE 4.5.1
On my desktop, with the nVidia GeForce 7300 LE running the nouveau driver,in KDE Compositing Type OpenGL is unavailable and desktop effects using compositing are unavailable.
On my netbook, with the Intel 945GME running the intel driver, in KDE Compositing Type OpenGL is unavailable.
On both systems, with the Xrender Compositing Type, desktop effects using compositing are unavailable.
I did not have to disable compositing to get KDE to start.
In short, KDE4.5.1 is broken with these X updates, probably in the checks for OpenGL functionality.
Just found something interesting. Under nouveau driver "xboard -fcp gnuchess" takes over 6 seconds to draw the board on startup. Happens instantly with nvidia prop driver. Not quite sure what's going on here, but something isn't quite right.
It's not exactly the most demanding of graphic guis.
Hi,
My cursor's icon became invisible. I am using Fujitsu-Siemens laptop with Intel 82..GM graphic adapter. Usually laptop works in dual monitor configuration: the laptop's display and external LCD display connected via VGA connector. When I disconnected the external monitor mouse icons became invisible - I mean the mouse is working but you don't see a cursor on a display. I first noticed this with KDE - but the same happens with Xfce. So I guess this it is rather a X server related issue. I tried both runlevels 3 and 4. No difference. I have an impression that X server somehow 'remebers' previous dual monitor configuration and tries to display a cursor on the external 'virtual' monitor. These are cuts from Xorg.0.log
Code:
(II) config/udev: Adding input device 2.4GHz 2way RF receiver (/dev/input/mouse2)
.
.
(EE) ioctl EVIOCGNAME failed: Inappropriate ioctl for device
(II) UnloadModule: "evdev"
(EE) PreInit returned NULL for "2.4GHz 2way RF Receiver"
Edited:
When I booted the system with the 2.6.34 kernel a mouse pinter is displayed properly. So it may be also a kernel issue. WHne I am using the new kernel 2.6.35 then tho mouse's pointer is not displayed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.