Bug 596 - nvidia173 driver problem
Summary: nvidia173 driver problem
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-31 00:30 CEST by Barry Jackson
Modified: 2011-04-20 18:59 CEST (History)
0 users

See Also:
Source RPM: nvidia173
CVE:
Status comment:


Attachments
/var/log/messages (134.46 KB, text/plain)
2011-04-20 02:36 CEST, Barry Jackson
Details
xorg.0.log (8.07 KB, text/plain)
2011-04-20 02:37 CEST, Barry Jackson
Details

Description Barry Jackson 2011-03-31 00:30:54 CEST
Description of problem:
Selecting the nvidia173 driver (FX5600U) stops X from running
Xorg.0.log is here:-
http://pastebin.com/raw.php?i=JMR8jL2E
Since I can't see any way to attach a file.

The nvidia driver was working fine until updates today.

Version-Release number of selected component (if applicable):
Sorry not in that system now - but it's a fully updated cauldron system.

How reproducibleworks fine:
Always - Works with vesa but segfaults with nvidia.

Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Ahmad Samir 2011-04-01 20:32:22 CEST
current nvidia173 driver doesn't work with X server 1.10, there was an ABI requirement in the spec file, but I think I wrongly dropped it when importing nvidia173 in Cauldron... I'll fix it now.

For the time being, either revert to x server 1.9 packages, or use the open source driver(s).
Comment 2 Ahmad Samir 2011-04-01 20:35:27 CEST
Looking further into this, Anssi had committed some changes to nvidia173 in SVN, but since the changes weren't submitted they didn't exist in the src.rpm I imported, I'll add merge those committs now.
Comment 3 Ahmad Samir 2011-04-01 21:12:33 CEST
Submitted new nvidia173 package(s) should properly conflict with current X server; even though the message displayed by urpmi isn't too descriptive (c.f. bug 444), it'll stop the user from installing X 1.10 with current nvidia173 driver.
Comment 4 Barry Jackson 2011-04-01 22:21:34 CEST
Thanks Ahmad, 
I caught Anssi on IRC last night - however moving to nouveau has thrown up another issue (bug 610) which makes it unusable (drives me mad !) :-(

Barry
Comment 5 Ahmad Samir 2011-04-02 01:08:32 CEST
(nouveau doesn't work well with my GTX 260, the mouse pointer hangs every half a minute...).

I hope you have better luck with nv (or you have older X server RPMs cached :)).

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 6 Ahmad Samir 2011-04-02 05:20:36 CEST
On second thought, we should keep this report open until upstream release a new driver supporting 1.10...

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 7 Ahmad Samir 2011-04-20 00:52:46 CEST
Please test nvidia173 173.14.30, which should hit the mirrors soon.

Source RPM: (none) => nvidia173

Comment 8 Barry Jackson 2011-04-20 02:36:32 CEST
Created attachment 253 [details]
/var/log/messages
Comment 9 Barry Jackson 2011-04-20 02:37:18 CEST
Created attachment 254 [details]
xorg.0.log
Comment 10 Barry Jackson 2011-04-20 02:39:40 CEST
(In reply to comment #7)
I just did a full auto-update at RL3 because of 
https://bugs.mageia.org/show_bug.cgi?id=893
the update included the new nvidia stuff and went perfectly.
I then went straight into drakx11 and set it up and was offered the proprietary driver - again all perfect and was even told to re-boot which I notice is now correct.
However on re-boot bug 893 broke everything. Loads of drm nouveau messages in /var/log/messages and xorg can't use nvidia because of nouveau being loaded.

messages and xorg.0.log attached
Comment 11 Barry Jackson 2011-04-20 12:00:12 CEST
OK now all - sorted,
Nvidia 173 working OK again, now that bug 893 issue resolved.

Marking as resolved/fixed.

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED

Comment 12 Ahmad Samir 2011-04-20 18:59:20 CEST
(I would have reopened, but since the improvements regarding the nokmsboot  Anssi is working on are already tracked in bug 893, no need :)).

Note You need to log in before you can comment on or make changes to this bug.