Description of problem: Dell Precision 5500 with Nvidia Quadro FX1800 hangs during boot. Last three lines of boot sequence output: [ok] Started Network Time Service. [ok] Reached target Multi-User System. [ok] Reached target Graphical interface. When using kernel 3.12.20.1.mga4 the computer boots normally. Version-Release number of selected component (if applicable): kernel server 3.12.21-1.mga4 How reproducible: Always with this specific system Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
Confirm. Same trouble. Mageia 4 i586, Nvidia GeForce GT 240. After updating to kernel 3.12.21, system doesn't load correct. X-server doesn't start. With kernel 3.12.20 all work successful.
CC: (none) => xxblx.duke
Created attachment 5197 [details] /var/log/Xorg.0.log
I confirm that nvidia module can't load with the last kernel (3.12.21) #modprobe nvidia modprobe: ERROR: could not insert 'nvidia_current': Unknown symbol in module, or unknown parameter (see dmesg) modprobe: ERROR: Error running install command for nvidia modprobe: ERROR: could not insert 'nvidia': Operation not permitted This is the lasst version of nvidia module (331.79) All works fine with the previous kernel (3.12.20-server-1)
CC: (none) => richard
CC: (none) => drew
Same problem here. Geforce GT 220 (not that it makes any difference, since the driver is simply broken).
CC: (none) => mla
CC: (none) => tmb
Me to on 3 computers, both 32&64 :-/ A workaround Change session: ctrl+alt+F2 Login as root urpme dkms-nvidia-current XFdrake Select your Graphic Card and select it again Ok and it should tell you that there are drivers for your card. Say yes to use them. reboot Not really sure if this step is needed: urpme dkms-nvidia-current
CC: (none) => hc
I also have problems. Only I have the video on AMD. Update passed, the system has booted, but the colors are not natural. White steel is like pink. Mageia 4 x86_64
CC: (none) => saikov.vb
Hardware: x86_64 => All
If you are having problems with kernel/nvidia/virtualbox updates please post a brief description of the hardware you are running on. Here's mine: Test platform: Intel Core i7-2600K Sandy Bridge 3.4GHz GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB RTL8111/8168B PCI Express 1Gbit Ethernet DRAM 16GB (4 x 4GB) Mageia 4 64-bit, Nvidia driver virtualbox-4.3.10-1.1.mga4.x86_64 virtualbox-guest-additions-4.3.10-1.1.mga4.x86_64 All three of these are moving parts and when any one of them changes, and there is a different hardware platform, different people can experiance different results. The latest update to the kernel works just fine on my nvidia platform. Do consider being part of the Mageia QA team to help test these updates on as many platforms as possible. Thanks.
CC: (none) => wilcal.int
(In reply to William Kenney from comment #7) > If you are having problems with kernel/nvidia/virtualbox updates please > post a brief description of the hardware you are running on. Here's mine: > Mageia 4, i586. Intel Core2Duo E7600 @ 3.068GHz RAM 4 Gb NVidia GeForce GT 240 Nvidia proprietary driver virtualbox is not installed. After updating to kernel-server-3.12.21 X-server doesn't work. So, I boot with 3.12.20 because with 3.12.20 x-server start fine.
Well, both fglrx and nvidia drivers work, so it seems the dkms timing issue is getting worse... Whats the output of: rpm -qa kernel* and for nvidia users: rpm -qa | grep nvidia and for amd users: rpm -qa |grep fglrx
Here are the drivers I track when I test Kernel/nvidia/Vbox: kernel-desktop-latest nvidia-current-kernel-desktop-latest x11-driver-video-nvidia-current virtualbox virtualbox-kernel-desktop-latest vboxadditions-kernel-desktop-latest All of these are moving parts when any one of them updates. Check to make sure you have the latest installed. I think all installs have some piece of VirtualBox installed.
Mageia 4 x86_64 AMD E-450 APU with Radeon(tm) HD Graphics AMD Radeon HD 6320 Graphics RAM 4 Gb ATI proprietary driver Update passed, the system has booted, but the colors are not natural. White steel is like pink. [xlin@xlin-netbook ~]$ rpm -qa kernel* kernel-desktop-3.8.13.4-1.mga3-1-1.mga3 kernel-desktop-devel-3.8.12-1.mga3-1-1.mga3 kernel-userspace-headers-3.12.21-2.mga4 kernel-server-devel-3.12.20-1.mga4-1-1.mga4 kernel-server-devel-3.12.18-1.mga4-1-1.mga4 kernel-desktop-3.8.12-2.mga3-1-1.mga3 kernel-server-3.12.21-2.mga4-1-1.mga4 kernel-server-devel-latest-3.12.21-2.mga4 kernel-server-3.12.20-1.mga4-1-1.mga4 kernel-desktop-3.12.21-2.mga4-1-1.mga4 kernel-desktop-3.8.8-3.mga3-1-1.mga3 kernel-desktop-devel-3.8.13.4-1.mga3-1-1.mga3 kernel-server-devel-3.12.21-2.mga4-1-1.mga4 kernel-firmware-nonfree-20140119-1.mga4.nonfree kernel-desktop-devel-latest-3.12.21-2.mga4 kernel-desktop-devel-3.8.10-1.mga3-1-1.mga3 kernel-desktop-3.8.13-1.mga3-1-1.mga3 kernel-server-3.12.8-2.mga4-1-1.mga4 kernel-desktop-devel-3.12.20-1.mga4-1-1.mga4 kernel-desktop-latest-3.12.21-2.mga4 kernel-desktop-3.12.20-1.mga4-1-1.mga4 kernel-desktop-devel-3.12.18-1.mga4-1-1.mga4 kernel-server-3.12.13-2.mga4-1-1.mga4 kernel-server-3.12.18-1.mga4-1-1.mga4 kernel-desktop-devel-3.12.21-2.mga4-1-1.mga4 kernel-desktop-3.12.18-1.mga4-1-1.mga4 kernel-server-devel-3.12.13-2.mga4-1-1.mga4 kernel-desktop-devel-3.12.13-2.mga4-1-1.mga4 kernel-desktop-3.10.24-2.mga3-1-1.mga3 kernel-desktop-devel-3.8.13-1.mga3-1-1.mga3 kernel-desktop-devel-3.10.24-2.mga3-1-1.mga3 kernel-desktop-devel-3.8.12-2.mga3-1-1.mga3 kernel-desktop-3.8.10-1.mga3-1-1.mga3 kernel-desktop-3.8.12-1.mga3-1-1.mga3 kernel-firmware-20131013-2.mga4 kernel-server-latest-3.12.21-2.mga4 kernel-server-devel-3.12.8-2.mga4-1-1.mga4 kernel-desktop-3.12.13-2.mga4-1-1.mga4 [xlin@xlin-netbook ~]$ rpm -qa |grep fglrx x11-driver-video-fglrx-14.010.1006-1.mga4.nonfree fglrx-kernel-3.8.12-desktop-1.mga3-12.104-4.mga3.nonfree fglrx-kernel-3.8.13.4-desktop-1.mga3-12.104-10.mga3.nonfree fglrx-kernel-3.12.18-desktop-1.mga4-13.251-13.mga4.nonfree fglrx-kernel-3.12.21-desktop-2.mga4-14.010.1006-2.mga4.nonfree fglrx-kernel-3.12.13-desktop-2.mga4-13.251-12.mga4.nonfree fglrx-kernel-3.8.13-desktop-1.mga3-12.104-7.mga3.nonfree fglrx-kernel-3.8.12-desktop-2.mga3-12.104-5.mga3.nonfree vaapi-driver-fglrx-0.8.0-1.mga2.nonfree fglrx-kernel-3.8.8-desktop-3.mga3-12.104-1.mga3.nonfree fglrx-control-center-14.010.1006-1.mga4.nonfree fglrx-kernel-3.8.10-desktop-1.mga3-12.104-2.mga3.nonfree fglrx-kernel-desktop-latest-14.010.1006-2.mga4.nonfree fglrx-kernel-3.12.20-desktop-1.mga4-13.251-15.mga4.nonfree dkms-fglrx-14.010.1006-1.mga4.nonfree fglrx-kernel-3.10.24-desktop-2.mga3-13.250.18-5.mga3.nonfree
(In reply to William Kenney from comment #10) > Here are the drivers I track when I test Kernel/nvidia/Vbox: > > kernel-desktop-latest > nvidia-current-kernel-desktop-latest > x11-driver-video-nvidia-current > virtualbox > virtualbox-kernel-desktop-latest > vboxadditions-kernel-desktop-latest > > All of these are moving parts when any one of them updates. > Check to make sure you have the latest installed. I think > all installs have some piece of VirtualBox installed. I need the exact output of the commands, not just info that you are using "*-latest" drivers, as it does not tell anything what versions are actually on the system and not all installs have vbox in them
[xlin@xlin-netbook ~]$ rpm -qa | grep virtual virtualbox-kernel-3.12.13-desktop-2.mga4-4.3.10-1.mga4 virtualbox-kernel-3.12.18-desktop-1.mga4-4.3.10-2.mga4 dkms-virtualbox-4.3.10-1.1.mga4 virtualbox-kernel-3.8.13.4-desktop-1.mga3-4.2.16-1.mga3 virtualbox-kernel-3.8.12-desktop-1.mga3-4.2.12-9.mga3 virtualbox-kernel-3.8.13-desktop-1.mga3-4.2.12-11.mga3 virtualbox-kernel-3.12.21-desktop-2.mga4-4.3.10-7.mga4 virtualbox-kernel-3.8.12-desktop-2.mga3-4.2.12-10.mga3 virtualbox-4.3.10-1.1.mga4 virtualbox-kernel-3.8.10-desktop-1.mga3-4.2.12-7.mga3 virtualbox-kernel-3.12.20-desktop-1.mga4-4.3.10-5.mga4 virtualbox-kernel-desktop-latest-4.3.10-7.mga4
CC: (none) => eeeemail
> virtualbox is not installed. Sorry, my fail. VirtualBox was installed. After full virtualbox uninstall system loaded correct with kernel-server 3.12.21, X-server started fine. All work. Okay, may be problem was with virtualbox. But how vbox can interrupt x-server? Strange. [xxblx@localhost ~]$ rpm -qa | grep kernel* nvidia-current-kernel-3.12.21-server-2.mga4-331.79-2.mga4.nonfree kernel-server-3.12.21-2.mga4-1-1.mga4 nvidia-current-kernel-3.12.18-server-1.mga4-331.49-3.mga4.nonfree nvidia-current-kernel-server-latest-331.79-2.mga4.nonfree nvidia-current-kernel-3.12.20-server-1.mga4-331.49-5.mga4.nonfree nvidia-current-kernel-3.12.8-server-2.mga4-325.15-6.mga4.nonfree kernel-server-devel-3.12.9-1.mga4-1-1.mga4 kernel-server-devel-3.12.21-2.mga4-1-1.mga4 kernel-firmware-20131013-2.mga4 kernel-server-3.12.13-2.mga4-1-1.mga4 kernel-server-devel-3.12.20-1.mga4-1-1.mga4 kernel-userspace-headers-3.12.21-2.mga4 kernel-server-devel-3.12.13-2.mga4-1-1.mga4 kernel-server-devel-3.12.18-1.mga4-1-1.mga4 kernel-server-devel-latest-3.12.21-2.mga4 kernel-server-devel-3.12.8-2.mga4-1-1.mga4 kernel-server-latest-3.12.21-2.mga4 kernel-server-3.12.8-2.mga4-1-1.mga4 nvidia-current-kernel-3.12.9-server-1.mga4-325.15-7.mga4.nonfree nvidia-current-kernel-3.12.13-server-2.mga4-331.49-2.mga4.nonfree kernel-server-3.12.18-1.mga4-1-1.mga4 kernel-firmware-nonfree-20140119-1.mga4.nonfree kernel-server-3.12.20-1.mga4-1-1.mga4 kernel-server-3.12.9-1.mga4-1-1.mga4 [xxblx@localhost ~]$ rpm -qa | grep nvidia* nvidia-current-kernel-3.12.21-server-2.mga4-331.79-2.mga4.nonfree dkms-nvidia-current-331.79-1.mga4.nonfree nvidia-current-kernel-3.12.18-server-1.mga4-331.49-3.mga4.nonfree nvidia-current-kernel-server-latest-331.79-2.mga4.nonfree nvidia-current-kernel-3.12.20-server-1.mga4-331.49-5.mga4.nonfree nvidia-current-kernel-3.12.8-server-2.mga4-325.15-6.mga4.nonfree x11-driver-video-nvidia-current-331.79-1.mga4.nonfree nvidia-current-doc-html-331.79-1.mga4.nonfree nvidia-current-kernel-3.12.9-server-1.mga4-325.15-7.mga4.nonfree nvidia-current-kernel-3.12.13-server-2.mga4-331.49-2.mga4.nonfree
Not ok on kernel 3.12.21, Ok on 3.12.20 - AMD phenom II X4 965 - Nvidia NVS300 - Mageia4 64b nvidia driver # rpm -qa|grep nvidia dkms-nvidia-current-331.79-1.mga4.nonfree nvidia-current-doc-html-331.79-1.mga4.nonfree nvidia-current-kernel-3.12.21-server-2.mga4-331.79-2.mga4.nonfree nvidia-current-kernel-server-latest-331.79-2.mga4.nonfree nvidia-current-kernel-3.12.20-server-1.mga4-331.49-5.mga4.nonfree x11-driver-video-nvidia-current-331.79-1.mga4.nonfree # rpm -qa|grep virtual virtualbox-4.3.10-1.1.mga4 virtualbox-kernel-3.12.20-server-1.mga4-4.3.10-5.mga4 virtualbox-kernel-3.12.21-server-2.mga4-4.3.10-7.mga4 virtualbox-kernel-server-latest-4.3.10-7.mga4
(In reply to Oleg Kozlov from comment #14) > > virtualbox is not installed. > Sorry, my fail. VirtualBox was installed. Yep, that can be a challenge during testing. I always test kernel/nvidia/Vbox all in at the same time on my test platform.
I confirm the workaround : - Change session: ctrl+alt+F2 - Login as root - urpme dkms-nvidia-current - urpmi dkms-nvidia-current (and wait for the module building) - reboot It's ok now Why the module was not been made correctly before ?
Confirmed. Removing and re-installing dkms-nvidia-current does the trick. Thanks for that. I can now update the rest of my machines!
Workaround ok for me too! Thanks.
BTW, I've now updated 3 machines to 3.12.21 -- of these two needed the workaround and one did not. Unlike the other two, the one that worked straight away did not have VirtualBox installed. Though, to be fair, being a laptop it differs from the other two in other ways as well. :-)
Ran into this problem with a Giada Atom Nvidia ION 2 box too after upgrade to Mageia 4. However, - Change session: ctrl+alt+F2 - Login as root - urpme dkms-nvidia-current - urpmi dkms-nvidia-current (and wait for the module building) - reboot does not solve it. As far as I can see there is no virtualbox installed. Any suggestions?
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD