LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   nouveau/nvidia problems - adapter 6150SE, kernel=3.10.14 (http://www.linuxquestions.org/questions/slackware-14/nouveau-nvidia-problems-adapter-6150se-kernel%3D3-10-14-a-4175480738/)

perbh 10-14-2013 10:30 AM

nouveau/nvidia problems - adapter 6150SE, kernel=3.10.14
 
the Geforce-6150SE adapter seem to give me nothing but grief.
'nouveau' (which normally is extremely stable, which why I never had to use the proprietary driver before - no gaming!) will freeze up tighter than a nun's posterior - leaving me only with the BRS (Big Red Switch) - also corrupting the screen.

the nvidia driver (304.60, 304.64) refuses to compile because it cannot find 'version.h' in the kernel source

FYI - using slackware-14.0 with kernel=3.2.29 - the nouveau driver has no problems whatsoever.

cynwulf 10-14-2013 11:05 AM

304.108 is patched for 3.10.x kernel source.

No idea as regards the nouveau problem. Did you search to see if anyone else was having problems with the nouveau module from that kernel on that hardware?

perbh 10-14-2013 11:59 AM

not really - my best place for replies is usually here - there must be _someone_ who has come across this problem before ...
I presume though, that later nouveau-drivers are primarily for the more recent nvidia adapters and they may have lost something at some stage ...

but thank you - I'll try the 108-version!

colorpurple21859 10-14-2013 12:52 PM

It wouldn't happen to happen when trying to use firefox? I have same card and firefox or something related to it was causing same problem.

perbh 10-14-2013 01:39 PM

Indeed it was - but also chrome caused the same freeze. After trying some more times - firefox was the worst of the culprits. I also tried chrome (which crashed it all) when firefox was running ok ... so it might still have been firefox - never tried chrome on its own.

However, be that as it may - the nvidia-304.108 driver is working fine.

Skaperen 10-15-2013 01:16 AM

How much RAM do you have? Are you running 32-bit? I have found that the 32-bit version of nouveau has issue if I have more than 2GB of RAM. The 64-bit version is stable. This is on a GTX-560. I have a machine with a 6150SE that works with nouveau, but it's a version of Slackware-current more than a month back. I could upgrade that box this weekend and see if I have the same issue.

perbh 10-15-2013 12:52 PM

4 gigs of ram, triple core amd (64-bit able), 32-bit (the triple-core is a wing-shot quad-core, one of the first quads).
I do believe its a GT560 I have.

As I pointed out initially - the 3.2.29-kernel with its nouveau works fine using 32-bit.

I tend to use 32-bit where possible, with PAE I can throw as much memory at it as I need (albeit at a slight performance penalty, but I'm not stressing the rigs any)

Looks like I have to try 64-bit - got a couple of spare partitions - let yall know if it works out with nouveau.

brewmaster1234 10-19-2013 08:29 PM

try the 304 legacy drivers
 
Hi
I'm new to Linux and Slackware and noticed that kde was sluggish, that means driver issue, i have a 6150se on a Compaq x86_64

and i have to say it was quite the ordeal to update the driver!! but it is done and kde works great, haven't tried any shooters but

menus snap open like they should, also a nvidia app is in the menu.

the problem now is the command line stays at 320 instead of switching to 800 or 1024 (dont know which) kind of annoying cause i do

most of my work on command line. i figure an init script got clobbered but don't know which one. I'd be greatfull for any help!

regards

don

TobiSGD 10-19-2013 09:42 PM

Quote:

Originally Posted by brewmaster1234 (Post 5048822)
Hi
I'm new to Linux and Slackware and noticed that kde was sluggish, that means driver issue, i have a 6150se on a Compaq x86_64

and i have to say it was quite the ordeal to update the driver!! but it is done and kde works great, haven't tried any shooters but

menus snap open like they should, also a nvidia app is in the menu.

the problem now is the command line stays at 320 instead of switching to 800 or 1024 (dont know which) kind of annoying cause i do

most of my work on command line. i figure an init script got clobbered but don't know which one. I'd be greatfull for any help!

regards

don

Nothing to do with init scripts. That behavior is caused by the fact that the Nvidia driver does not support kernel mode setting (KMS), but the nouveau driver does. So you can either use the framebuffer console with boot options like vga=791 (1024x768) or go back to the nouveau drivers if you want higher resolutions on the console.

brewmaster1234 10-20-2013 02:41 PM

Thanks
do you mean the lilo.conf settings?
i tried changing the settings but nothing happens

TobiSGD 10-20-2013 11:55 PM

You have to rerun lilo after changing the settings.

brewmaster1234 10-21-2013 06:15 AM

oops i forgot about that lol
it all works perfect now
thanks very much for your help


All times are GMT -5. The time now is 08:42 PM.