Hi team Mageia
Description of problem:
Since 1 week, Mageia Cauldon can't start X.
Version-Release number of selected component (if applicable):
I don't know if it's kernel, X, MESA or other component.
I try to use vesa, same problem.
Here, a photo of my screen to see the message (too long to write it here)
Steps to Reproduce:
1. Update Cauldron
Can you fix it ?
Created attachment 7694 [details]
Picture to illustrate the problem
I confirm this issue, same here on my Cauldron for x86_64 in a VB.
Since I have updated my Cauldron yesterday I get this issue. Probably an xorg or vbox driver problem.
I think it's a problem with VirtualBox Video Driver.
I have Video if I made that :
and install vbox additions from official image downloaded from Oracle Website.
X won't start =>
X won't start in VirtualBox
I had the same problem and found a solution by searching on the web: I had to remove "/etc/X11/xorg.conf" file (actually, I moved that file into "/etc/X11/xorg.conf.save").
Could one of you provide a diff between /etc/X11/xorg.conf.save and /etc/X11/xorg.conf? That might help narrow down the issue.
I have no /etc/X11/xorg.conf file anymore (mv /etc/X11/xorg.conf /etc/X11/xorg.conf.save).
Ah, I assume a new one would be initialized when booting, but I guess nowadays Xorg can boot without this file.
mv /etc/X11/xorg.conf /etc/X11/xorg.conf.old => solve the problem.
[root@localhost ~]# LANG=C diff -rus /etc/X11/xorg.conf.old /etc/X11/xorg.conf
diff: /etc/X11/xorg.conf: No such file or directory
*** Bug 18337 has been marked as a duplicate of this bug. ***
It happens with both 6sta1 x86-64 and 6st1 i586 VMs.
(In reply to Nicolas Salguero from comment #6)
> I have no /etc/X11/xorg.conf file anymore (mv /etc/X11/xorg.conf
I can confirm that moving away the file fixes the problam in 6sta1 i586 Classic DVD. However, after that I have a problem that the networking does not work until I do "service shorewall stop" as root.
Thanks for the tip (mv /etc/X11...) to get X to start.
For the network issue, another workaround is to go to the Network center, configure the connection, and allow users to manage it. Then I disconnect and reconnect it. And the network is up.
I've encountered the same issue.
Installing from Mageia-Cauldron-netinstall-nonfree-x86_64.iso into VirtualBox results in a system with broken Xorg configuration. The file Xorg.0.log shows some errors.
$ grep EE Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 1040.289] (EE) Failed to load module "vboxmouse" (module does not exist, 0)
[ 1040.308] (EE) No devices detected.
[ 1040.308] (EE)
[ 1040.308] (EE) no screens found(EE)
[ 1040.310] (EE)
[ 1040.310] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 1040.310] (EE)
Executing "Xorg -configure" and then trying to execute "Xorg -config /root/xorg.conf.new" also fails.
Removing the file /etc/X11/xorg.conf and then executing "startx" starts Xorg for a few seconds but then terminates without showing the desktop.
Executing "Xorg" starts Xorg and then to start Plasma I execute "DISPLAY=:0 startkde".
Will attach the following files:
xorg.conf.install - config file generated during installation
xorg.conf.new - config file generated by "Xorg -configure"
Xorg.0.log.install - log file of "Xorg -config xorg.conf.install"
Xorg.0.log.new - log file of "Xorg -config xorg.conf.new"
Xorg.0.log.noconfig - log fine of "Xorg" without config file.
Guest package versions:
# rpm -qa | grep -Ei 'kernel|virtualbox|vbox' | sort
Host package versions:
$ rpm -qa | grep -Ei 'kernel|virtualbox|vbox' | sort
Created attachment 8021 [details]
xorg.conf generated during installation
Created attachment 8022 [details]
xorg.conf generated by "Xorg -configure"
Created attachment 8023 [details]
log file of "Xorg -config xorg.conf.install"
Created attachment 8024 [details]
log file of "Xorg -config xorg.conf.new"
Created attachment 8025 [details]
log fine of "Xorg" without config file.
Woow, this issue still exists when booting Mageia 6 sta1 Netinstall that I installed yesterday evening in a VM (VESA driver, 1024x768px).
Screenshot upon first boot after install : http://pic.al/sHd
Solved as per comment #4.
Sometimes the "nomodeset" option on the kernel command line helps too.
*** This bug has been marked as a duplicate of bug 18724 ***