Bug 1018825

Summary: X does not start
Product: [Fedora] Fedora Reporter: Germano Massullo <germano.massullo>
Component: xorg-x11-drv-nouveauAssignee: Ben Skeggs <bskeggs>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: airlied, ajax, bskeggs, germano.massullo, sergio
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-17 14:19:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg
none
/proc/interrupts
none
lshw
none
lsmod none

Description Germano Massullo 2013-10-14 13:16:55 UTC 
Created attachment 812009 [details]
dmesg

Description of problem:
After having filled bugreport
https://bugzilla.rpmfusion.org/show_bug.cgi?id=2990
about propertary nVidia drivers, I decided to move to nouveau drivers.
So I removed packages
akmod-nvidia
kmod-nvidia
xorg-x11-drv-nvidia
xorg-x11-drv-nvidia-libs

Then removed /etc/X11/xorg.conf and recreated Grub menu by doing 
# grub2-mkconfig -o /boot/grub2/grub.cfg

I rebooted but X does not start, like when I was using propertary drivers.
(I check by doing ps cax | grep X  because I am connected to the machine through SSH).
I passed the entire morning trying to resolve the problem on IRC, but I think there should be something that can interest a bugreport.

Additional info:
kernel 3.11.3-201.fc19.x86_64
Comment 1 Germano Massullo 2013-10-14 13:17:38 UTC 
Created attachment 812010 [details]
/proc/interrupts
Comment 2 Germano Massullo 2013-10-14 13:17:59 UTC 
Created attachment 812011 [details]
lshw
Comment 3 Germano Massullo 2013-10-14 13:18:18 UTC 
Created attachment 812012 [details]
lsmod
Comment 4 Ben Skeggs 2013-10-17 00:26:34 UTC 
I strongly suspect a config issue here as a result of not removing the binary driver fully, or something.  What does your /var/log/Xorg.0.log say after trying to start X?
Comment 5 Germano Massullo 2013-10-17 08:31:49 UTC 
(In reply to Ben Skeggs from comment #4)
> I strongly suspect a config issue here as a result of not removing the
> binary driver fully, or something.  What does your /var/log/Xorg.0.log say
> after trying to start X?

Yesterday I tried to start X from console with the command
startx
and it started! So why it does start manually and not automatically?
Comment 6 Germano Massullo 2013-10-17 14:19:28 UTC 
No problem with nouveau driver, the trouble is KDM fault:
https://bugzilla.redhat.com/show_bug.cgi?id=967521

I found out that it was a KDM problem because X started if I restarted KDM service.
I solved by doing rm -rf /var/log/journal/* ; reboot
Comment 7 Sergio Basto 2013-10-17 16:43:41 UTC 
(In reply to Germano Massullo from comment #6)
> No problem with nouveau driver, the trouble is KDM fault:
> https://bugzilla.redhat.com/show_bug.cgi?id=967521
> 
> I found out that it was a KDM problem because X started if I restarted KDM
> service.
> I solved by doing rm -rf /var/log/journal/* ; reboot

why is a KDM problem , what KDM have to do with /var/log/journal/ ?
Comment 8 Germano Massullo 2013-10-17 16:59:25 UTC 
My mistake, I meant systemd-journald that influenced KDM in a way that we don't know