Bug 16076

Summary:	unable to start x server
Product:	Mageia	Reporter:	Christian Neufselle <informatique>
Component:	Release (media or process)	Assignee:	Kernel and Drivers maintainers <kernel>
Status:	RESOLVED OLD	QA Contact:
Severity:	critical
Priority:	Normal	CC:	marja11, nic, sysadmin-bugs, thierry.vignaud, tmb
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	kernel, x11-driver-video-intel	CVE:
Status comment:
Attachments:	xorg.conf Xorg.0.log report.bug syslog.txt NEW syslog.txt NEW xorg.conf NEW Xorg.0.log

Description Christian Neufselle 2015-06-03 18:45:31 CEST

Description of problem:
after the choice "mageia" in the grub2 menu, boot stops after around 9 seconds.
After the choice "mode de dépannage", boot stops after :
"acpi warning system IO range range 0x0... conflicts with OpRegion 0x0...
ACPI : if an acpi driver is avaible for this device, you should use it instead of the native driver "
I tried to edit "mageia avec linux desktop" (options avancées) with options: acpi=off and runlevel 3. I can log in "localhost login" (command line), but  the command "startx" returns :
/home/[user]/.serverauth.xxxx does not exist
modprobe: error could not insert 'i915'no such device
xinit: giving up
xinit: unable to connect to x server : connection refused
xinnit : server error

I tried to change the driver "intel 810 or later" by vesa, or intel xorg, but it's a failure

hardware: asus X553M ; pentium N3540 ; platform Intel BayTrail ; intel HD graphics

Version-Release number of selected component (if applicable):


How reproducible:
every time I boot

Steps to Reproduce:
1.see up
2.
3.


Reproducible: 

Steps to Reproduce:

Christian Neufselle 2015-06-03 18:48:33 CEST

Component: Installer => Release (media or process)
CC: (none) => sysadmin-bugs

Comment 1 Christian Neufselle 2015-06-03 19:18:03 CEST

same problem with kernel 3.19.4 or 3.19.8

Comment 2 Thierry Vignaud 2015-06-04 06:26:38 CEST

Please attach (not paste) the following files:
/root/drakx/report.files
/etc/X11/xorg.conf
/var/log/Xorg.0.log

Keywords: (none) => NEEDINFO
CC: (none) => thierry.vignaud, tmb

Comment 3 Thierry Vignaud 2015-06-04 10:02:49 CEST

And the /tmp/syslog.txt file resulting from running the following command after having a X11 failure:
journalctl -b > /tmp/syslog.txt

Comment 4 Christian Neufselle 2015-06-04 18:15:06 CEST

Created attachment 6700 [details]
xorg.conf

Comment 5 Christian Neufselle 2015-06-04 18:15:41 CEST

Created attachment 6701 [details]
Xorg.0.log

Comment 6 Christian Neufselle 2015-06-04 18:41:14 CEST

Created attachment 6702 [details]
report.bug

Comment 7 Christian Neufselle 2015-06-04 18:41:47 CEST

Created attachment 6703 [details]
syslog.txt

Comment 8 Christian Neufselle 2015-06-04 18:43:39 CEST

4 files attached. No report.files in drakx but report.bug.
Thanks for help

Marja Van Waes 2015-06-04 19:05:51 CEST

CC: (none) => marja11
Attachment 6701 mime type: text/x-log => text/plain

Marja Van Waes 2015-06-04 19:06:27 CEST

Attachment 6702 mime type: application/octet-stream => text/plain

Comment 9 Thierry Vignaud 2015-06-05 15:15:34 CEST

Humm, xorg.0.log shows:
[  1636.130] intel: waited 2020 ms for i915.ko driver to load

Are you sure you run the journalctl command _after_ a X11 failure?

Source RPM: (none) => kernel, x11-driver-video-intel

Comment 10 Christian Neufselle 2015-06-05 17:39:13 CEST

I boot with : edit "mageia avec linux desktop" (options avancées) options: acpi=off and runlevel 3. I run startx (returns failure).
I run journalctl, and I copy the file syslog.txt in /home/user. I reboot with a live usb (mint, because mageia don't work with usb) and I recover the file for attachment (with other pc, no other OS on the laptop).
I try again

Comment 11 Christian Neufselle 2015-06-05 17:54:16 CEST

Created attachment 6709 [details]
NEW syslog.txt

Comment 12 Christian Neufselle 2015-06-05 17:55:03 CEST

Created attachment 6710 [details]
NEW xorg.conf

Comment 13 Christian Neufselle 2015-06-05 17:55:36 CEST

Created attachment 6711 [details]
NEW Xorg.0.log

Comment 14 Thomas Backlund 2015-06-05 18:36:22 CEST

Why are you running with "acpi=off" ?

It most definately gets the i915 module loading in trouble, and probably creates other hw issues...

Comment 15 Christian Neufselle 2015-06-08 18:43:10 CEST

to Thomas:
because it don't start with acpi on (see description)

Comment 16 Nic Baxter 2016-01-04 04:10:08 CET

Any thing to do?

CC: (none) => nic

Comment 17 Marja Van Waes 2016-01-04 09:19:56 CET

(In reply to Nic Baxter from comment #16)
> Any thing to do?

yeah, remove the "NEEDINFO" since all information that was asked for was given :-)

Keywords: NEEDINFO => (none)

Samuel Verschelde 2016-11-01 13:10:46 CET

Assignee: bugsquad => kernel

Comment 18 Aurelien Oudelet 2020-08-29 21:11:19 CEST

Since there are sufficient details provided in this report for us to investigate the issue further, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of our distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

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