Bug 22922

Summary: Mouse, keyboard and network does not work after booting
Product: Mageia Reporter: Bernard MAUDRY <ramaspaceship>
Component: RPM PackagesAssignee: Kernel and Drivers maintainers <kernel>
Status: RESOLVED INVALID QA Contact:
Severity: critical    
Priority: Normal CC: marja11, zen25000
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: kernel-4.14.34-1.mga7.src.rpm CVE:
Status comment:

Description Bernard MAUDRY 2018-04-18 00:07:19 CEST 
Description of problem:
Kernel desktop 4.14.34-1.mga7 64-bits identifies itself as 4.14.28-desktop-1.mga7 as logged in the journal:
Linux version 4.14.28-desktop-1.mga7 (iurt@ecosse.mageia.org) (gcc version 7.3.0 (Mageia 7.3.0-3.mga7)) #1 SMP Mon Mar 19 14:03:02 UTC 2018
This causes the modules to be not found and leads to devices not available

Version-Release number of selected component (if applicable):
kernel desktop 4.14.34-1 64-bits

How reproducible:
Every boot

Steps to Reproduce:
1. boot the kernel
2. DE appears
3. Mouse, keyboard and network does not work
Comment 1 Marja Van Waes 2018-04-18 08:39:37 CEST 
it identifies itself fine, here

apr 18 07:19:37 localhost kernel: Linux version 4.14.34-desktop-1.mga7 (iurt@rabbit.mageia.org) (gcc version 7.3.0 (Mageia 7.3.0-3.mga7)) #1 SMP Sat Apr 14 01:21:01 UTC 2018

and 

[marja@localhost ~]$ uname -a
Linux localhost 4.14.34-desktop-1.mga7 #1 SMP Sat Apr 14 01:21:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
[marja@localhost ~]$ 


Please attach the output of 

   ls -al /boot


Was the bootloader last written from this install, or from another install on the same hardware?

Assignee: bugsquad => kernel
CC: (none) => marja11, Zenitur

Marja Van Waes 2018-04-18 08:40:14 CEST

CC: Zenitur => zen25000

Comment 2 Bernard MAUDRY 2018-04-18 09:20:44 CEST 
You found the trick. The boot entry was written by my Mageia6 install, and there was a mistake in one Cauldron entry.

I recently moved my Cauldron install to a partition on a new SSD and the default entry in the grub2 config indicated a wrong root partition in one place (grub 2 is error prone for that as the root partition is to be put in 4 places for each entry).

I was misleaded because kernel 4.14.14 booted correctly.

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