| Summary: | 2_b1: Request that a new kernel build trigger propriety driver rpm build | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Bit Twister <bittwister2> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Normal | CC: | fri |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Bit Twister
2012-03-01 19:13:16 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 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) it's not the case ? (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. 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 yes, users have only to wait (cauldron) and for the 2 there will be never this issue. Status:
NEW =>
RESOLVED |