Bug 18019 - Can't boot x86_64 6dev1 kde install /boot/vmlinuz missing
Summary: Can't boot x86_64 6dev1 kde install /boot/vmlinuz missing
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Anne Nicolas
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-16 00:54 CET by Dave Hodgins
Modified: 2016-03-16 23:55 CET (History)
4 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
report.bug from install failing to create vmlinuz files (169.80 KB, application/x-xz)
2016-03-16 00:56 CET, Dave Hodgins 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Dave Hodgins 2016-03-16 00:54:33 CET 
After installing 6dev1 kde x86_64, boot fails with vmlinuz not found. In the
installed filesystem, /boot has broken symlinks
vmlinuz -> vmlinuz-4.4.5-desktop-1.mga6 and
vmlinuz-desktop -> vmlinuz-4.4.5-desktop-1.mga6

The initrd files are there. I'll attach /root/drakx/report.bug.xz

The i586 install is working. I tried the x86_64 twice, just to be sure there
wasn't some user brain damage involved. :-)
Comment 1 Dave Hodgins 2016-03-16 00:56:20 CET 
Created attachment 7574 [details]
report.bug from install failing to create vmlinuz files
Dave Hodgins 2016-03-16 00:57:27 CET

CC: (none) => mageia
Assignee: bugsquad => ennael1

Comment 2 Dave Hodgins 2016-03-16 01:29:22 CET 
Adding tmb as vmlinuz should be created as part of kernel install

CC: (none) => tmb

Dave Hodgins 2016-03-16 01:30:11 CET

CC: (none) => eeeemail, wilcal.int

Comment 3 Anne Nicolas 2016-03-16 23:12:07 CET 
Isos was including 2 versions of radeon-firmware. During installation old one was tried to be installed which just remove any chance to install kernel.

Fixed in coming iso. Please check and close this bug
Comment 4 Dave Hodgins 2016-03-16 23:55:28 CET 
Confirming fixed

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