Bug 4886 - nvidia173 module build (failed) slowing boot
Summary: nvidia173 module build (failed) slowing boot
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: Anssi Hannula
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-11 21:30 CET by Barry Jackson
Modified: 2012-08-20 20:54 CEST (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Barry Jackson 2012-03-11 21:30:18 CET
Description of problem:
There is currently no working nvidia173 upstream driver that supports the current Cauldron X11 version, so the system correctly has defaulted to nouveau.
However on each boot the nvidia module attempts to build and fails, which delays the boot.
Assigning to Anssi as requested on IRC.

[baz@jackodesktop ~]$ rpm -qa | grep nvidia
x11-driver-video-nvidia173-173.14.31-1.mga2.nonfree
dkms-nvidia173-173.14.31-1.mga2.nonfree
nvidia173-doc-html-173.14.31-1.mga2.nonfree
[baz@jackodesktop ~]$

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 Manuel Hiebel 2012-03-11 21:44:12 CET
duplicate of https://bugs.mageia.org/show_bug.cgi?id=4842 I think
Comment 2 Marja Van Waes 2012-05-26 13:06:06 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 3 Barry Jackson 2012-06-14 22:09:26 CEST
I suspect that this was resolved by Anssi - for me it was solved by removing a package after a chat on irc.

Keywords: NEEDINFO => (none)

Comment 4 Barry Jackson 2012-08-20 20:54:31 CEST
(In reply to comment #1)
> duplicate of https://bugs.mageia.org/show_bug.cgi?id=4842 I think

Closing as fixed since duplicate is fixed and I can no longer verify as the hardware involved died.

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


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