Bug 4764 - 2_b1: Request that a new kernel build trigger propriety driver rpm build
Summary: 2_b1: Request that a new kernel build trigger propriety driver rpm build
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-01 19:13 CET by Bit Twister
Modified: 2012-05-24 19:11 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bit Twister 2012-03-01 19:13:16 CET 
Description of problem:

I would like to request that a new kernel build trigger a propriety driver rpm build. Example: 

A kernel-3.2.9-desktop would build a fglrx-kernel-3.2.9-desktop

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 Manuel Hiebel 2012-03-01 19:38:31 CET 
We have kmod-fglrx but the build faild:
http://pkgsubmit.mageia.org/
Manuel Hiebel 2012-03-06 22:37:59 CET

Keywords: (none) => NEEDINFO

Comment 2 Bit Twister 2012-03-06 23:08:42 CET 
No idea about what NEEDINFO you wanted. I just thought it would be nice for any new kernel and intel video packages to be generated for the proprietary video drivers.

Keywords: NEEDINFO => (none)

Comment 3 Manuel Hiebel 2012-03-06 23:17:57 CET 
it's not the case ?
Comment 4 Bit Twister 2012-03-07 14:33:59 CET 
(In reply to comment #3)
> it's not the case ?

Looks like it to me. You might recall two bug reports opened about ati/nvidia drivers which would not compile or run with updated 2.9.x kernel just after I made this request.

Reason I made this request was because my radeon/fglrx rpm was not available with the updated kernel. I was lucky because my fglrx would still run on updated kernel. Some were not so lucky.

Seemed like it was 2 or 3 days later when the driver rpms showed up.
Comment 5 Morgan Leijström 2012-05-23 03:00:54 CEST 
I just watched a new kernel getting installed, which then triggered nvidia module rebuild (And also virtualbox module)

So that seem to work.

( ...and later in same update session it retrieved a newer nvidia driver and rebuilt the nvidia driver again... Hmmm -> Bug 6030 )

CC: (none) => fri

Comment 6 Manuel Hiebel 2012-05-24 19:11:17 CEST 
yes, users have only to wait (cauldron) and for the 2 there will be never this issue.

Status: NEW => RESOLVED
Resolution: (none) => INVALID
Note You need to log in before you can comment on or make changes to this bug.