LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-25-2011, 12:55 AM   #16
andyt22
LQ Newbie
 
Registered: Sep 2005
Location: North London, England
Distribution: Slackware,OpenSuSE,Debian
Posts: 8

Rep: Reputation: 0

I too had the same frustrating problems after I upgraded from Slackware 13.1 to 13.37 - nouveau is very unstable and my system would hang or crash frequently. Also, 1 used the Twin View feature of the nvidia driver in my 13.1 installation to drive 2 CRT monitors side by side and nouveau doesn't support that, although I have to say nouveau did correctly set the resolution to 1600 x 1200 with no need for an xorg.conf

While looking at glx/video problems on a Ubuntu 11.04 machine at work (which also used nouveau by default) I found out that if you download and install the latest nVidia driver, the installer will offer to disable nouveau for you. So I tried this on Slack 13.37 and it works fine and I've now got my stable 2 screen set-up back.

I'm surprised at Slackware (and Ubuntu) rushing headlong into the nouveau camp and making this the default as nouveau is nowhere near 'production-ready'. Can someone remind me why we need to merge X servers into the kernel in the first place? And (slightly off-topic) does anyone make high-grade CRT monitors any more?

Andy
 
Old 06-25-2011, 07:33 AM   #17
adamk75
Senior Member
 
Registered: May 2006
Posts: 3,091

Rep: Reputation: 399Reputation: 399Reputation: 399Reputation: 399
Quote:
Originally Posted by andyt22 View Post
I'm surprised at Slackware (and Ubuntu) rushing headlong into the nouveau camp and making this the default as nouveau is nowhere near 'production-ready'.
Just because it doesn't work for you doesn't make it non 'production-ready'.

Quote:
Can someone remind me why we need to merge X servers into the kernel in the first place?
Because it's impossible to effectively manage high amounts of video RAM without a memory manager. In order to be fast and secure, the GPUs memory manager needs to be in kernel space. The proprietary nvidia and fglrx drivers also include nearly all the same functionality in their kernel modules, the only difference being that they don't hook into the kernel framebuffer driver.

Adam
 
Old 06-26-2011, 01:02 AM   #18
andyt22
LQ Newbie
 
Registered: Sep 2005
Location: North London, England
Distribution: Slackware,OpenSuSE,Debian
Posts: 8

Rep: Reputation: 0
Quote:
Originally Posted by adamk75 View Post
Just because it doesn't work for you doesn't make it non 'production-ready'.
Judging from comments in various forums, quite a few people are having problems with it and switching to commercial drivers so this suggests there is a problem with it at the moment. When you rely on your computer for your livelihood, you want a reliable and dependable system with most of the software issues sorted and unlike my previous Slackware upgrades, my update from 13.1 to 13.37 was retrograde step, at least until I disabled nouveau.

Quote:
Because it's impossible to effectively manage high amounts of video RAM without a memory manager. In order to be fast and secure, the GPUs memory manager needs to be in kernel space. The proprietary nvidia and fglrx drivers also include nearly all the same functionality in their kernel modules, the only difference being that they don't hook into the kernel framebuffer driver.
Thanks for the explanation. I'm not sure that using nouveau to run the basic framebuffer itself is such a good idea though - my Linux systems boot into run level 3 and I start X manually with 'startx' so if there are any problems with X, at least I can regain control of the system. But with the nouveau driver, when X crashed or hung, I couldn't kill it with the usual key sequence nor could I access any VT. I had to log in through another system and either kill X or more often, reboot the machine. This reduced level of control over the system is what you'd expect from Windows, not Linux!

Andy
 
Old 06-26-2011, 01:36 AM   #19
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 4,602

Rep: Reputation: 1509Reputation: 1509Reputation: 1509Reputation: 1509Reputation: 1509Reputation: 1509Reputation: 1509Reputation: 1509Reputation: 1509Reputation: 1509Reputation: 1509
Actually, you are wrong to blame the nouveau driver for your woes. The cause of your problem is an interaction between the capabilities of your hardware as advertised by OpenGL (saying that certain facilities are available when in fact they are not or have limited capability) and your X desktop (likely KDE) trying to use the advertised capabilities.
Control over your system does require that you do your homework.
From CHANGES_AND_HINTS.TXT
Quote:
Regardless of your chipset (though it seems more common with intel), if KDE
crashes on startup, try disabling the Composite extension (which will also
disable all of the fancy desktop effects). Place the following content in
a file at /etc/X11/xorg.conf.d/disable-composite.conf:
Section "Extensions"
Option "Composite" "Disable"
EndSection
I am happily running the nouveau driver to support KDE on two different nVidia chipsets. Just do not expect the fancy KDE desktop effects to be available.
 
1 members found this post helpful.
Old 06-26-2011, 07:51 AM   #20
adamk75
Senior Member
 
Registered: May 2006
Posts: 3,091

Rep: Reputation: 399Reputation: 399Reputation: 399Reputation: 399
Quote:
Originally Posted by andyt22 View Post
Judging from comments in various forums, quite a few people are having problems with it and switching to commercial drivers so this suggests there is a problem with it at the moment.
Based on that logic, you could look at all the complaint posts on the nvnews linux forum and say that the nvidia drivers are not production ready. Or you could look at all the problem posts on linuxquestions and say that linux is not production ready.

Besides, I don't think anyone said there are no problems with nouveau.

Adam
 
Old 06-26-2011, 08:23 AM   #21
tommcd
Senior Member
 
Registered: Jun 2006
Location: Philadelphia PA USA
Distribution: Lubuntu, Slackware
Posts: 2,230

Rep: Reputation: 291Reputation: 291Reputation: 291
Quote:
Originally Posted by andyt22 View Post
I'm surprised at Slackware (and Ubuntu) rushing headlong into the nouveau camp and making this the default as nouveau is nowhere near 'production-ready'.
According to the Package Additions sections of the Changes and Hints.txt for Slackware 13.1 and 13.37, nouveau was blacklisted by default on 13.1, as 13.1 included x/xf86-video-nouveau-blacklist by default. Slackware 13.37 includes x/xf86-video-nouveau; and nouveau is not blacklisted by default on 13.37.
So Pat V did not really rush into using nouveau. As always, he apparently waited until he felt it was ready.

By way of comparison, Ubuntu started using nouveau as early as February 2010 according to this mailing list post: https://lists.ubuntu.com/archives/ub...ry/000766.html
And nouveau was enabled by default in Ubuntu Karmic 9.10.

As far as I know the open source "nv" driver is no longer being developed. The "nv" driver had it's own limitations anyway. So going forward it will be either nouveau or the binary blob from nvidia.
The nouveau people have been doing a fine job with developing an open source driver for nvidia cards, especially since they get no help whatsoever from the good folks at nvidia.

Last edited by tommcd; 06-26-2011 at 08:31 AM.
 
Old 06-26-2011, 11:02 AM   #22
afreitascs
Member
 
Registered: Aug 2004
Location: Brasil
Distribution: Slackware_Cur-64_mult
Posts: 433

Rep: Reputation: 30
guess ...

Install a previous version of Slackware, which you can use xorgsetup (eg slackware 12.0). Note which is horizontal & vertical refresh rates.

Slackware13:37 install the proprietary drivers from nvidia.com. At the end of the installation it creates an xorg.conf file.
Using horizontal & vertical refresh rates., noted earlier, vi xorg.conf, and "Section" Monitor " type...

Code:
Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "your monitor"
    HorizSync       rate noted <-----------
    VertRefresh     rate noted <-----------
    Option         "DPMS"
EndSection
In xorg.config adjust to the proper resolution

I hope you understand what I write. My English is bad .

good luck :-)
 
1 members found this post helpful.
Old 12-20-2011, 10:13 PM   #23
dchmelik
Member
 
Registered: Nov 2008
Location: Washington state, USA
Distribution: NetBSD, FreeBSD, OpenBSD, OpenSolaris, Slackware, FreeSlack, Android
Posts: 256

Original Poster
Rep: Reputation: 23
Smile

Quote:
Originally Posted by allend View Post
Actually, you are wrong to blame the nouveau driver for your woes. The cause of your problem is an interaction between the capabilities of your hardware as advertised by OpenGL (saying that certain facilities are available when in fact they are not or have limited capability) and your X desktop (likely KDE) trying to use the advertised capabilities.
Control over your system does require that you do your homework.
From CHANGES_AND_HINTS.TXT

I am happily running the nouveau driver to support KDE on two different nVidia chipsets. Just do not expect the fancy KDE desktop effects to be available.
This solved it.

Last edited by dchmelik; 12-20-2011 at 10:19 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Wine 32 bit on Slackware 13 64 bit problems: configure can't find some libraries ozanbaba Slackware 28 11-26-2010 02:42 PM
Slackware 13 64-bit + php 5.3.0 + lighttpd 1.4.23 -> fastcgi problems lordbone Linux - Software 2 10-14-2009 11:00 AM
Slamd64 (64 Bit slackware) and ATI driver problems ljones0 Slackware 3 04-07-2009 10:03 AM
Monitor problems with dual boot slackware and winxp Kelean Slackware 6 10-06-2007 06:42 PM
Problems with XF86, chip VIA KM400, Monitor Samsung 551v, Slackware 8.0 olarteo Linux - Newbie 1 01-20-2004 01:36 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:57 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration