In the forums and on IRC some users reported getting a black screen when booting after last kernel updates. https://forums.mageia.org/en/viewtopic.php?f=7&t=6536 which at first seemed only related to nvidia https://forums.mageia.org/en/viewtopic.php?f=7&t=6536#p42487 but a user on IRC seems to have hit the same problem, with proprietary ati radeon drivers: 2013:12:25:11:04 < geokara> mageia 3 2013:12:25:11:04 < geokara> after the latest kernel update 2013:12:25:11:04 < geokara> ati radeon mobility hd5470 2013:12:25:11:05 < geokara> the system starts and loads into a black screen instead of the user login screen 2013:12:25:11:24 < geokara> I can't login with an older kernel, it's the same situation. 2013:12:25:11:45 < geokara> I had installed the proprietary drivers when I first installed mageia some months ago. Reproducible: Steps to Reproduce:
CC: (none) => doktor5000, jim
(In reply to Marja van Waes from comment #0) > > but a user on IRC seems to have hit the same problem, with proprietary ati > radeon drivers: Guessing more hardware info is going to be required. My ATI radeon cards are working on all 3 of my 64 bit installs Release 3 and 4. Seymour [Radeon HD 6400M/7400M Series] âCedar [Radeon HD 5450 Series] Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8500 Series]
CC: (none) => junknospam
(In reply to Bit Twister from comment #1) > (In reply to Marja van Waes from comment #0) > > > > but a user on IRC seems to have hit the same problem, with proprietary ati > > radeon drivers: > > Guessing more hardware info is going to be required. My ATI radeon cards are > working on all 3 of my 64 bit installs Release 3 and 4. > Yes, I don't doubt the kernel updates were tested with nvidia and ati radeon cards, so something else seems to be going on. I'll ask geokara to give the output of rpm -qa | grep fglrx (if he still has the problem, that is)
(In reply to Marja van Waes from comment #2) > I'll ask geokara to give the output of > rpm -qa | grep fglrx > (if he still has the problem, that is) he isn't on IRC any more
there's a newer kernel (3.10.25) + related packages in 3 updates_testing, btw, it just solved a different problem (laptop overheating to the point of shutting itself down) someone else had with 3.10.24
An other question is if nonfree release & nonfree updates was available / enabled during the update ?
(In reply to Marja van Waes from comment #2) > (In reply to Bit Twister from comment #1) > > (In reply to Marja van Waes from comment #0) > > > > > > but a user on IRC seems to have hit the same problem, with proprietary ati > > > radeon drivers: > > > > Guessing more hardware info is going to be required. My ATI radeon cards are > > working on all 3 of my 64 bit installs Release 3 and 4. > > > > Yes, I don't doubt the kernel updates were tested with nvidia and ati radeon > cards, so something else seems to be going on. > > I'll ask geokara to give the output of > rpm -qa | grep fglrx > (if he still has the problem, that is) The output of the rpm -qa | grep fglrx command is as follows. fglrx-kernel-3.10.24-desktop-2.mga3-13.250.18-5.mga3.nonfree fglrx-kernel-3.8.13.4-desktop-1.mga3-12.104-10.mga3.nonfree fglrx-kernel-3.8.13-desktop-1.mga3-12.104-7.mga3.nonfree fglrx-kernel-desktop-latest-13.250.18-5.mga3.nonfree x11-driver-fglrx-13.250.18-0.1.mga3.nonfree fglrx-control-center-13.250.18.0.1.mga3.nonfree
CC: (none) => blakrose777
(In reply to George Kara from comment #6) > > The output of the rpm -qa | grep fglrx command is as follows. Would not hurt to supply some video card hardware info. I just checked my neighbor's release 3 with all updates and no black screen # lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 520] (rev a1)
(In reply to Bit Twister from comment #7) > (In reply to George Kara from comment #6) > > > > The output of the rpm -qa | grep fglrx command is as follows. > > Would not hurt to supply some video card hardware info. > I just checked my neighbor's release 3 with all updates and no black screen > > # lspci | grep VGA > 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 520] > (rev a1) Thought we just wanted the output of the rpm -qa |grep fglrx command. My video card is an ATI mobility radeon 5470. The output of the lspci | grep VGA is this. 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430/5450/5470]. If any other information should be provided please let me know. Thank you.
(In reply to George Kara from comment #8) > [AMD/ATI] Park [Mobility Radeon HD 5430/5450/5470]. If any other information > should be provided please let me know. Thank you. As root, output from these two commands journalctl | grep "Kernel command" cat /etc/release
> As root, output from these two commands > journalctl | grep "Kernel command" > cat /etc/release The first command generates a ridiculously large file which I couldn't open fully. The output of cat /etc/release is 'Mageia release 3 (official) for x86_64.' Is there some other way to get the information the first command generates?
(In reply to George Kara from comment #10) > > As root, output from these two commands > > journalctl | grep "Kernel command" > > The first command generates a ridiculously large file which I couldn't open > fully. Is there some other way to get the information the first command > generates? Sorry, I forget that I clean the logs on system shutdown/reboots, but it should not have been ridiculously large. You get one on each boot. I just need one and the last one found would be best. Maybe this will help journalctl | grep "Kernel command line:"
two things... if you use journalctl, then add "-b" flag that restricts the log to "only logs since last boot" otoh if you want to see the kernel command line for the running kernel, just do: cat /proc/cmdline
(In reply to Thomas Backlund from comment #12) > two things... if you use journalctl, then add "-b" flag that restricts the > log to "only logs since last boot" Good point. but > otoh if you want to see the kernel command line for the running kernel, just > do: > > cat /proc/cmdline I am not sure if we will get what we need based on the problem. What I was after is the kernel command line for when the black screen occurs. Hopefully George will give the kernel command line when there is a black screen but off hand I can not see how if it is black, :( unless he boots the system and ssh in from another system to give us the information.
Happy new year everyone! During the past few days I have tried some things but I couldn't boot the system and ssh into it. I managed to open the journalctl file and went through it. I created a smaller file containing information about the kernel activity two days before the kernel update up to December 29. The last thing I tried was to remove every fglrx driver I found in my system. Out of luck I rebooted the pc with the previous kernel and was able to log in with no problems. I installed all the necessary drivers for all my kernels through the mageia control center and after that the problem immediately returned. No kernel works although it just have had the correct drivers installed. I don't know if the information provided could be useful but I thought you all should know. Any ideas?
Sounds a bit like my experience. I installed a "bare metal" version of Cauldron RC from KDE Live. Nvidia ran fine until I ran updates. Now I can't run the nvidia driver and xscreensaver complains that No GLX extension on display 0:0 But no "black screen" except that what prompted this reinstall was a Maintenance prompt.
CC: (none) => laidlaws
It turns out that X was running normally or that the system indicates so. After plugging the laptop to an external hdmi screen everything was ok except for the fact that the keyboard lagged at times when typing. I did a clean install today of mageia 3 on my laptop after having rendered my system unusable. The minute it updated to the latest kernel with the latest proprietary drivers the problem reoccured. I rolled back to the 3.8.13-desktop-1.mga3 kernel with the suitable proprietary drivers so as to have a system I can work with. Thank you for your help and your time regarding this issue.
(In reply to Doug Laidlaw from comment #15) > Sounds a bit like my experience. > > I installed a "bare metal" version of Cauldron RC from KDE Live. Nvidia ran > fine until I ran updates. Now I can't run the nvidia driver and > xscreensaver complains that > > No GLX extension on display 0:0 > > But no "black screen" except that what prompted this reinstall was a > Maintenance prompt. Just tried to get graphics in boinc-manager and nothing happened. I didn't realize how extensive the effects of this bug are.
Some further info: I installed Mga4 from scratch, and told the installer I did NOT want the nVidia driver. xscreensaver ran fine. Then I installed the nvidia-kernel etc and a host of other dependencies I didn't expect. Now I get the GLX error. It could have been any one of those dependencies.
Installing the above did not give me a usable driver. I have now uninstalled dkms-nvidia-current nvidia-current kernel (and the -latest file) nvidia-current-doc x11-driver-video-nvidia-current and GLX is back.
Just like Doug I did a clean install of Mageia 4 on my laptop. It booted into a black screen same as before with the 3.10 kernel update. I used the ati proprietary drivers. The HDMI output works fine but the laptop screen remains dead. I have no idea what might be wrong. No error message and X seems to be starting normally. This is very sad, I was really looking forward to Mageia 4.
Please, don't mix totally different issues into this bug. This bug was about a kernel upgrade and graphics driver update on Mageia 3, where afterwards sometimes the wrong graphics driver was used or for nvidia, multiple nvidia kernel module version where in place and X server got confused. This is not about Mageia 4 default installation, and not about multiple monitor output between HDMI and internal display.
OK Florian, but it is still to do with the nvidia driver, except I am in 4. I can't recall ever having multiple nvidia modules. The files for Rel4 and those for the RC are the same. I could file a separate bug, but I feel that fixing this bug will fix everything. What I did in Comment 19 has solved my problems with Bug 11666, so I am reporting there as well. Should I file a separate bug? George describes symptoms, but I am not qualified to say they are related to my experience. Sounds as though he needs a separate bug as well. They can always be marked as duplicates later, if that is the case.
Have split off my problem as Bug 12623.
With some additional search I managed to find that the problem is related to the latest ati drivers and my laptop series. After the ati drivers update to 13.10 the backlight of the screen is off so there is no picture. This also happens in windows as well. I sent a bug form to ati as well in order to have this problem looked at. This is not a mageia 3 or mageia 4 bug it is an ati bug! I am deeply sorry for this misunderstanding.
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD
It is history.