Bug 43487 – Adjust installer to Kernel 4.9

Bug 43487 - Adjust installer to Kernel 4.9


Summary:	Adjust installer to Kernel 4.9

Status:	RESOLVED DUPLICATE of bug 42048

Product:	UCS
Classification:	Unclassified
Component:	UCS Installer
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Installer maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-02-02 16:31 CET by Stefan Gohmann
Modified:	2018-04-14 14:02 CEST (History)
CC List:	0 users

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

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

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

Description Stefan Gohmann

2017-02-02 16:31:19 CET

I've build a new kernel via Bug #42048. It seems the following modules are no longer available:

E: Unable to locate package acpi-modules-4.9.0-ucs101-amd64-di
E: Unable to locate package cdrom-core-modules-4.9.0-ucs101-amd64-di
E: Unable to locate package fat-modules-4.9.0-ucs101-amd64-di
E: Unable to locate package fb-modules-4.9.0-ucs101-amd64-di
E: Unable to locate package firewire-core-modules-4.9.0-ucs101-amd64-di
E: Unable to locate package hyperv-modules-4.9.0-ucs101-amd64-di
E: Unable to locate package input-modules-4.9.0-ucs101-amd64-di
E: Unable to locate package mouse-modules-4.9.0-ucs101-amd64-di
E: Unable to locate package pata-modules-4.9.0-ucs101-amd64-di
E: Unable to locate package pcmcia-modules-4.9.0-ucs101-amd64-di

Comment 1 Stefan Gohmann

2017-02-02 16:56:53 CET

It looks like the modules are no build by the linux-signed package.

Comment 2 Stefan Gohmann

2017-02-02 17:18:04 CET


*** This bug has been marked as a duplicate of bug 42048 ***