Bug 9076 - applying update to 3.4.30 from 3.4.24 broke the xserver starts and nvidia driver is not loading properly
Summary: applying update to 3.4.30 from 3.4.24 broke the xserver starts and nvidia dri...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2013-02-14 16:20 CET by Paul Dessart
Modified: 2013-11-23 16:14 CET (History)
2 users (show)

See Also:
Source RPM: dkms-nvidia-current
CVE:
Status comment:


Attachments

Description Paul Dessart 2013-02-14 16:20:40 CET
Description of problem:
After applying updates for my Mageia2 X86_64 the system went by default on Kernel 3.4.30 was on 3.4.24 
My Nvidia driver launches perfectly on 3.4.24 but get a black screen on 3.4.30
reading the log it appears to be broken.
restarting and choosing to launch 3.4.24 again the system starts without problem.
hence the issue on latest kernel


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


How reproducible:


Steps to Reproduce:
1. install nvidia latest 
2. apply update to come on 3.4.30 kernel
3.start the computer again from a complete boot [ stop/ halt + start]
Comment 1 Manuel Hiebel 2013-02-16 16:44:54 CET
any dkms log ?

(also maybe this kernel is not yet complete, kmod pkg are not yet rebuilded too)

CC: (none) => tmb
Component: Release (media or process) => RPM Packages
Source RPM: dkms-nvidia-current - NVIDIA kernel module for GeForce 6 and later cardsâ  => dkms-nvidia-current

Comment 2 Thomas Backlund 2013-02-16 16:56:02 CET
Yep, the 3.4.30 was only a testbuild to check a few fixes... there will be a 3.4.32 out probably tomorrow that will get full set for QA to go to updates..
Comment 3 Manuel Hiebel 2013-02-21 08:38:12 CET
so have you tested the new kernel ?

Keywords: (none) => NEEDINFO

Comment 4 Paul Dessart 2013-02-21 10:17:24 CET
I saw you were asking for dkms log but Iḿ not sure how to find it. If you can give me the steps I will try to collect them for you.
Comment 5 Manuel Hiebel 2013-02-21 13:43:04 CET
have you tested the new one which is in testing the 3.4.32 ?
Comment 6 Manuel Hiebel 2013-10-22 12:10:35 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 7 Manuel Hiebel 2013-11-23 16:14:01 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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


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