Description of problem: After kernel update the system don't boot. The new kernel is 3.14.18 and i must return to the previous kernel release (3.12.25) to have my working system. The system went to black screen an remain to this state after the bootloader phase. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
What Hardware / GPU do you have? What driver do you use ? Does 3.14.22 in updates_testing work any better ?
CC: (none) => tmb
@ Thomas Tanks for the reply. My system is: inxi -F System: Host: localhost.localdomain Kernel: 3.12.25-server-3.mga4 x86_64 (64 bit) Desktop: KDE 4.11.4 Distro: Mageia 4 thornicroft Machine: Mobo: ASRock model: 960GM-GS3 FX Bios: American Megatrends version: P1.30 date: 05/21/2012 CPU: Dual core AMD Athlon II X2 270 (-MCP-) cache: 2048 KB flags: (lm nx sse sse2 sse3 sse4a svm) Clock Speeds: 1: 2700.00 MHz 2: 2000.00 MHz Graphics: Card: Advanced Micro Devices [AMD/ATI] RS780L [Radeon 3000] X.Org: 1.14.5 drivers: ati,v4l,radeon Resolution: 1280x1024@60.0hz GLX Renderer: Gallium 0.4 on AMD RS780 GLX Version: 3.0 Mesa 10.0.5 Audio: Card: Advanced Micro Devices [AMD/ATI] SBx00 Azalia (Intel HDA) driver: snd_hda_intel Sound: Advanced Linux Sound Architecture ver: k3.12.25-server-3.mga4 Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: bc:5f:f4:7c:0f:01 Drives: HDD Total Size: 463.1GB (7.0% used) 1: id: /dev/sda model: ST380815AS size: 80.0GB 2: id: /dev/sdb model: SanDisk_SDSSDP06 size: 63.0GB 3: id: /dev/sdc model: SAMSUNG_HM321HI size: 320.1GB Partition: ID: / size: 58G used: 7.1G (13%) fs: ext4 ID: /home size: 48G used: 24G (52%) fs: ext4 ID: swap-1 size: 2.15GB used: 0.00GB (0%) fs: swap RAID: No RAID devices detected - /proc/mdstat and md_mod kernel raid module present Sensors: System Temperatures: cpu: 17.2C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 159 Uptime: 8 min Memory: 1029.2/1753.1MB Client: Shell (bash) inxi: 1.9.17 I have not try the new kernel in testing, I wait for the usual system update.
Today I have upgrade my kernel to the latest version by the Repository. The last is 3.14.23 but this and the previous version 3.14.18 show a black screen after grub (the choice of kernel version). The old kernel version 3.12.25 works.
Today I have update my Mageia 4 to last kernel: after the grub the screen become black ant remain black. I have choice at the grub level the latest kernel (server 3.14.24-1.mga4) and have press F3, choice failsafe and insert this line: root=... failsafe resume=UUID=9380... vga=... the boot is ok until this line: [ OK ] Reached target Paths [ OK ] Reached target Sound Card [Failed] Failed to start Load legacy module configuration. See 'systemctl status fedora-loamodules.service' for details. _ and the system is blocked but ctrl-alt-canc works and the system reboots. Any hints?
systemctl status fedora-loadmodules.service fedora-loadmodules.service - Load legacy module configuration Loaded: loaded (/usr/lib/systemd/system/fedora-loadmodules.service; static) Active: failed (Result: exit-code) since Wed 2014-12-10 18:31:12 EET; 3h 21min ago Process: 625 ExecStart=/lib/systemd/fedora-loadmodules (code=exited, status=1/FAILURE) Main PID: 625 (code=exited, status=1/FAILURE) So my fedora load modules failed to load. Is it a problem? It is a static module. This output is with kernel 3.12.25 that works. Is the problem with new kernel about this failure?
I have check the log file boot.log: http://www.kensan.it/tmp/boot.log.txt and have found this failure with kernel 3.12.25 (this kernel works): $ cat boot.log |grep -n2 fedora 61-[ OK ] Started udev Kernel Device Manager. 62-[FAILED] Failed to start Load legacy module configuration. 63:See 'systemctl status fedora-loadmodules.service' for details. 64-[ OK ] Started udev Wait for Complete Device Initialization. 65- Starting Wait for storage scan... -- 78- Mounting /home... 79-[FAILED] Failed to start Load legacy module configuration. 80:See 'systemctl status fedora-loadmodules.service' for details. 81-[ OK ] Mounted /home. 82-[ OK ] Reached target Local File Systems. -- 105-[ OK ] Reached target Sockets. 106-[FAILED] Failed to start Load legacy module configuration. 107:See 'systemctl status fedora-loadmodules.service' for details. 108-[ OK ] 109-[ OK ] Started Reconfigure the system on administrator request.
Tadoy I have upgrade my mageia4 to the latest kernel 3.14.39 and after grub it shows black screen for minutes. The old kernel 3.12.25 works fine.
can you attach output of lspcidrake -v also, try to remove "splash quiet" from grub kernel command line to hopefully catch some more info of why it hangs
Tanks a lot for your reply Thomas. I have do what you ask some times ago and removing "splash quiet" works a lot. The screen shows a lot of information and freeze after the line: fb: conflicting fb hw usage radeondrmfb vs VESA VGA - removing generic driver ctrl+alt+canc works and the system reboots *** It is the result of lspcidrake: http://www.kensan.it/tmp/lspcidrake.txt *** When I have a photo machine I add a hight resolution screen shot of the boot screen that hang.
is radeon-firmware installed ?
I don't know where to find this infromation. I have execute lsmod (with my working kernel 3.12.25) and ls into firmware directory: http://www.kensan.it/tmp/radeon.txt It is my graphic card: Identification Vendor: âAdvanced Micro Devices, Inc. [AMD/ATI] Description: âRS780L [Radeon 3000] Misc Module: âCard:ATI Radeon HD 4870 and earlier Should be provide other info?
ok, so you are missing the nonfree radeon firmware. Ensure you have the "Nonfree Updates" media enabled, and install radeon-firmware-20140828-1.mga4 it should automatically regenerate the initrds with the needed firmware. after that, try to boot again with the new 3.14.39 kernel
Very well. I have try and now it is all fine. I have send you an email for a gift to you. kind regards. bug closed.
Hi, good to hear, and sorry for not spotting that earlier.
Status: NEW => RESOLVEDResolution: (none) => FIXED