Bug 42280 - NVc0 generation card (0x0c1000a1) not working
Summary: NVc0 generation card (0x0c1000a1) not working
Status: RESOLVED WORKSFORME
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/nouveau (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-26 06:48 UTC by Bruno Antunes
Modified: 2011-10-31 04:23 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg output (60.44 KB, text/plain)
2011-10-26 06:48 UTC, Bruno Antunes
Details
lspci output (4.74 KB, text/plain)
2011-10-26 06:51 UTC, Bruno Antunes
Details
X.org log (69.05 KB, text/x-log)
2011-10-27 02:11 UTC, Bruno Antunes
Details

Description Bruno Antunes 2011-10-26 06:48:12 UTC
Created attachment 52795 [details]
dmesg output

Hello.

I have an eVGA GT440 PCI-e card, and nouveau does not work. The card in question has 1024MB of DDR3 memory.

Attached are the lspci and dmesg logs.

My Linux info:
Comment 1 Bruno Antunes 2011-10-26 06:50:35 UTC
Hello.

I have an eVGA GT440 PCI-e card, and nouveau does not work. The card in question has 1024MB of DDR3 memory.

Attached is the dmesg log.

Arch Linux
uname -a output:

Linux beast 3.1.0-mainline #1 SMP PREEMPT Mon Oct 24 12:18:09 UTC 2011 x86_64 Intel(R) Core(TM) i7 CPU 960 @ 3.20GHz GenuineIntel GNU/Linux

I tried passing noaccel=0 on the kernel args, but Gnome 3.2 still boots up in fallback mode saying my driver is llvmpipe Gallium 0.4.

Please help, really wanna know how I can make this work!


Thanks,


Bruno Antunes
Comment 2 Bruno Antunes 2011-10-26 06:51:11 UTC
Created attachment 52796 [details]
lspci output
Comment 3 Robert Hancock 2011-10-26 21:07:50 UTC
What do you mean by "does not work"? There does not seem to be anything obviously abnormal in dmesg. If you're referring to GNOME Shell not working in normal mode, then the Xorg.0.log file would be useful.
Comment 4 Bruno Antunes 2011-10-27 02:11:05 UTC
By "does not work" I mean I have no 3D accel :)

I'll attach the X log, but the relevant part of it appears to be:


[    15.599] (EE) NOUVEAU(0): Error creating GPU channel: -19
[    15.599] (EE) NOUVEAU(0): Error initialising acceleration.  Falling back to NoAccel
[    15.602] (==) NOUVEAU(0): Backing store disabled
[    15.602] (==) NOUVEAU(0): Silken mouse enabled
[    15.602] (==) NOUVEAU(0): DPMS enabled
[    15.602] (II) NOUVEAU(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[    15.603] (--) RandR disabled
Comment 5 Bruno Antunes 2011-10-27 02:11:34 UTC
Created attachment 52817 [details]
X.org log
Comment 6 Marcin Slusarz 2011-10-27 09:29:12 UTC
Isn't it "nouveau.noaccel=0" instead of "noaccel=0"?
Comment 7 Bruno Antunes 2011-10-27 10:23:18 UTC
will that make the '-19' error go away?
Comment 8 Bruno Antunes 2011-10-31 03:04:02 UTC
Thanks for the help, Marcin! I was just adding "noaccel=0" without "nouveau."!

This whole process is really not straight-forward. The reporting should be simpler and the docs are hard to grasp.

Enjoying default Gnome Shell now, thanks to you man! :D

Thanks a bunch
Comment 9 Ben Skeggs 2011-10-31 03:40:54 UTC
(In reply to comment #8)
> Thanks for the help, Marcin! I was just adding "noaccel=0" without "nouveau."!
> 
> This whole process is really not straight-forward. The reporting should be
> simpler and the docs are hard to grasp.
I presume you updated in the mean time, in which case, you don't need the option anymore anyway.  If you'd tried this without the updates as of yesterday, you would not be enjoying how gnome shell looked, which is the entire reason it was disabled by default.  It wasn't *mean't* to be used.

> 
> Enjoying default Gnome Shell now, thanks to you man! :D
> 
> Thanks a bunch
Glad it's working for you though, thanks for letting us know.
Comment 10 Bruno Antunes 2011-10-31 04:23:32 UTC
I'm using the 3.1 kernel from last Wednesday... it only works with "nouveau.noaccel=0"


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.