7:57 a.m.
recently, i upgraded my ASUS G74S laptop to fedora rawhide and it
was running nicely. then this morning, i did another "yum update",
which appeared to update well over 200 packages (including a slightly
newer kernel), after which, when i booted, i had no graphical desktop
anymore, just the little blue and white fedora logo.
i can still switch to VC2 and log in at the command line (where i am
now), so i can certainly check log files, but i don't see anything
immediately amiss.
i rebooted both to the earlier rawhide kernel, and even back to the
latest fedora 20 official kernel -- same result, the fedora logo in
the middle of the screen on VC1, but the ability to log in on another
virtual console.
has anyone else run into this? i have an nvidia graphics card, and
am running the nouveau driver. i'll keep poking around the log files,
and if you have any suggestions, i'm all ears.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
8:20 a.m.
On Thu, 13 Mar 2014, Robert P. J. Day wrote:
On Thu, 13 Mar 2014, Kevin Martin wrote:
> On 03/13/2014 07:57 AM, Robert P. J. Day wrote:
> >
> > recently, i upgraded my ASUS G74S laptop to fedora rawhide and it
> > was running nicely. then this morning, i did another "yum update",
> > which appeared to update well over 200 packages (including a slightly
> > newer kernel), after which, when i booted, i had no graphical desktop
> > anymore, just the little blue and white fedora logo.
> >
> > i can still switch to VC2 and log in at the command line (where i am
> > now), so i can certainly check log files, but i don't see anything
> > immediately amiss.
> >
> > i rebooted both to the earlier rawhide kernel, and even back to the
> > latest fedora 20 official kernel -- same result, the fedora logo in
> > the middle of the screen on VC1, but the ability to log in on another
> > virtual console.
> >
> > has anyone else run into this? i have an nvidia graphics card, and
> > am running the nouveau driver. i'll keep poking around the log files,
> > and if you have any suggestions, i'm all ears.
> >
> > rday
> >
> Hmm, sounds similar to what I'm experiencing. When you go into VC2
> what does "lsmod | grep nouveau" show? I've found that I've been
> having to manually "modprobe nouveau modeset=1" since doing my
> update about 4 days ago. I'm not sure why nouveau won't load and I
> find that if I don't set the modeset=1 when I do the manual modprobe
> that I still can't get X.
here's mine:
nouveau 1087913 2
mxm_wmi 12865 1 nouveau
i2c_algo_bit 13257 1 nouveau
drm_kms_helper 50287 1 nouveau
ttm 80479 1 nouveau
drm 283937 4 ttm,drm_kms_helper,nouveau
i2c_core 38476 6
drm,i2c_i801,drm_kms_helper,i2c_algo_bit,nouveau,videodev
wmi 18804 3 mxm_wmi,nouveau,asus_wmi
video 19206 2 nouveau,asus_wmi
i could, i guess, manually unload all modules dependent on nouveau,
or just reboot and add "nouveau.modeset=1" at the kernel command line,
right?
i also checked /sys/module/nouveau/parameters/modeset, which
currently has a value of -1, which i don't understand. still, if it's
a module issue, why would rebooting under an earlier, working kernel
not have fixed this?
so i did the above, checked that the value of the nouveau.modeset
parameter under /sys in indeed "1" after rebooting, but no luck, same
symptoms. and given that the same thing happens even under earlier,
working kernels, it seems clear(?) that the problem must be in a
userspace package somewhere that was updated during this morning's
"yum update". still open to suggestions ...
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
8:43 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/13/2014 02:58 PM, Robert P. J. Day wrote:
On Thu, 13 Mar 2014, Kevin Martin wrote:
> On 03/13/2014 07:57 AM, Robert P. J. Day wrote:
>>
>> recently, i upgraded my ASUS G74S laptop to fedora rawhide and it was
>> running nicely. then this morning, i did another "yum update", which
>> appeared to update well over 200 packages (including a slightly newer
>> kernel), after which, when i booted, i had no graphical desktop
>> anymore, just the little blue and white fedora logo.
>>
>> i can still switch to VC2 and log in at the command line (where i am
>> now), so i can certainly check log files, but i don't see anything
>> immediately amiss.
>>
>> i rebooted both to the earlier rawhide kernel, and even back to the
>> latest fedora 20 official kernel -- same result, the fedora logo in the
>> middle of the screen on VC1, but the ability to log in on another
>> virtual console.
>>
>> has anyone else run into this? i have an nvidia graphics card, and am
>> running the nouveau driver. i'll keep poking around the log files, and
>> if you have any suggestions, i'm all ears.
>>
>> rday
>>
> Hmm, sounds similar to what I'm experiencing. When you go into VC2 what
> does "lsmod | grep nouveau" show? I've found that I've been having
to
> manually "modprobe nouveau modeset=1" since doing my update about 4 days
> ago. I'm not sure why nouveau won't load and I find that if I don't set
> the modeset=1 when I do the manual modprobe that I still can't get X.
hmmmm ... it's possible this is not related to rawhide at all, and is due
to something silly i did earlier this morning. could the following be the
cause?
in order to install drupal 8.x on my fedora (rawhide) system, i had to
disable selinux ("setenforce 0"). i *think* that while selinux was thus
disabled, i may have done "yum update", which would have of course updated
those 200+ packages while my system was in permissive mode. once i saw i
had a new kernel due to the update, i of course rebooted, which rebooted
with selinux back in enforcing mode, and the problems started. simply
putting selinux back into permissive mode fixed everything.
i'm by no means an selinux expert -- is that how i caused my problem?
rday
What AVC messages are you getting?
ausearch -m avc -ts today
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlMjB30ACgkQrlYvE4MpobPkTwCfS2ZwxCYQVkgnLwrjKAn0yYct
MR8AoNH1bSq3XdCM/rELRPB5zAL3KZTO
=tLQG
-----END PGP SIGNATURE-----
2:25 p.m.
On Mar 13, 2014 12:58 PM, "Robert P. J. Day" <rpjday(a)crashcourse.ca>
wrote:
On Thu, 13 Mar 2014, Kevin Martin wrote:
> On 03/13/2014 07:57 AM, Robert P. J. Day wrote:
> >
> > recently, i upgraded my ASUS G74S laptop to fedora rawhide and it
> > was running nicely. then this morning, i did another "yum update",
> > which appeared to update well over 200 packages (including a slightly
> > newer kernel), after which, when i booted, i had no graphical desktop
> > anymore, just the little blue and white fedora logo.
> >
> > i can still switch to VC2 and log in at the command line (where i am
> > now), so i can certainly check log files, but i don't see anything
> > immediately amiss.
> >
> > i rebooted both to the earlier rawhide kernel, and even back to the
> > latest fedora 20 official kernel -- same result, the fedora logo in
> > the middle of the screen on VC1, but the ability to log in on another
> > virtual console.
> >
> > has anyone else run into this? i have an nvidia graphics card, and
> > am running the nouveau driver. i'll keep poking around the log files,
> > and if you have any suggestions, i'm all ears.
> >
> > rday
> >
> Hmm, sounds similar to what I'm experiencing. When you go into VC2
> what does "lsmod | grep nouveau" show? I've found that I've been
> having to manually "modprobe nouveau modeset=1" since doing my
> update about 4 days ago. I'm not sure why nouveau won't load and I
> find that if I don't set the modeset=1 when I do the manual modprobe
> that I still can't get X.
hmmmm ... it's possible this is not related to rawhide at all, and
is due to something silly i did earlier this morning. could the
following be the cause?
in order to install drupal 8.x on my fedora (rawhide) system, i had
to disable selinux ("setenforce 0"). i *think* that while selinux was
thus disabled, i may have done "yum update", which would have of
course updated those 200+ packages while my system was in permissive
mode. once i saw i had a new kernel due to the update, i of course
rebooted, which rebooted with selinux back in enforcing mode, and the
problems started. simply putting selinux back into permissive mode
fixed everything.
i'm by no means an selinux expert -- is that how i caused my
problem?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
Drupal should not only install but also function (given appropriate
labeling) with SELinux enforcing - as should any package. If you can't even
install the package, chances are there is a packaging problem that should
be corrected.
This is where working with test@ to verify and isolate comes in :)
--Pete
2:14 p.m.
On 03/13/2014 11:58 AM, Robert P. J. Day issued this missive:
On Thu, 13 Mar 2014, Kevin Martin wrote:
> On 03/13/2014 07:57 AM, Robert P. J. Day wrote:
>>
>> recently, i upgraded my ASUS G74S laptop to fedora rawhide and it
>> was running nicely. then this morning, i did another "yum update",
>> which appeared to update well over 200 packages (including a slightly
>> newer kernel), after which, when i booted, i had no graphical desktop
>> anymore, just the little blue and white fedora logo.
>>
>> i can still switch to VC2 and log in at the command line (where i am
>> now), so i can certainly check log files, but i don't see anything
>> immediately amiss.
>>
>> i rebooted both to the earlier rawhide kernel, and even back to the
>> latest fedora 20 official kernel -- same result, the fedora logo in
>> the middle of the screen on VC1, but the ability to log in on another
>> virtual console.
>>
>> has anyone else run into this? i have an nvidia graphics card, and
>> am running the nouveau driver. i'll keep poking around the log files,
>> and if you have any suggestions, i'm all ears.
>>
>> rday
>>
> Hmm, sounds similar to what I'm experiencing. When you go into VC2
> what does "lsmod | grep nouveau" show? I've found that I've been
> having to manually "modprobe nouveau modeset=1" since doing my
> update about 4 days ago. I'm not sure why nouveau won't load and I
> find that if I don't set the modeset=1 when I do the manual modprobe
> that I still can't get X.
hmmmm ... it's possible this is not related to rawhide at all, and
is due to something silly i did earlier this morning. could the
following be the cause?
in order to install drupal 8.x on my fedora (rawhide) system, i had
to disable selinux ("setenforce 0"). i *think* that while selinux was
thus disabled, i may have done "yum update", which would have of
course updated those 200+ packages while my system was in permissive
mode. once i saw i had a new kernel due to the update, i of course
rebooted, which rebooted with selinux back in enforcing mode, and the
problems started. simply putting selinux back into permissive mode
fixed everything.
i'm by no means an selinux expert -- is that how i caused my
problem?
It's possible. Generally speaking, files installed by an RPM should
have the correct selinux contexts set, but if a file is _generated_
by a scriptlet in the RPM, it may not have the correct context.
I'd recommend, as root "touch /.autorelabel" and reboot. That should
force the system to set the correct selinux contexts on your files.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 -
- -
- Millihelen (n): The amount of beauty required to launch one ship. -
----------------------------------------------------------------------
1:58 p.m.
On Thu, 13 Mar 2014, Kevin Martin wrote:
On 03/13/2014 07:57 AM, Robert P. J. Day wrote:
>
> recently, i upgraded my ASUS G74S laptop to fedora rawhide and it
> was running nicely. then this morning, i did another "yum update",
> which appeared to update well over 200 packages (including a slightly
> newer kernel), after which, when i booted, i had no graphical desktop
> anymore, just the little blue and white fedora logo.
>
> i can still switch to VC2 and log in at the command line (where i am
> now), so i can certainly check log files, but i don't see anything
> immediately amiss.
>
> i rebooted both to the earlier rawhide kernel, and even back to the
> latest fedora 20 official kernel -- same result, the fedora logo in
> the middle of the screen on VC1, but the ability to log in on another
> virtual console.
>
> has anyone else run into this? i have an nvidia graphics card, and
> am running the nouveau driver. i'll keep poking around the log files,
> and if you have any suggestions, i'm all ears.
>
> rday
>
Hmm, sounds similar to what I'm experiencing. When you go into VC2
what does "lsmod | grep nouveau" show? I've found that I've been
having to manually "modprobe nouveau modeset=1" since doing my
update about 4 days ago. I'm not sure why nouveau won't load and I
find that if I don't set the modeset=1 when I do the manual modprobe
that I still can't get X.
hmmmm ... it's possible this is not related to rawhide at all, and
is due to something silly i did earlier this morning. could the
following be the cause?
in order to install drupal 8.x on my fedora (rawhide) system, i had
to disable selinux ("setenforce 0"). i *think* that while selinux was
thus disabled, i may have done "yum update", which would have of
course updated those 200+ packages while my system was in permissive
mode. once i saw i had a new kernel due to the update, i of course
rebooted, which rebooted with selinux back in enforcing mode, and the
problems started. simply putting selinux back into permissive mode
fixed everything.
i'm by no means an selinux expert -- is that how i caused my
problem?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
9:37 a.m.
On Thu, 13 Mar 2014, Patrick O'Callaghan wrote:
On Thu, Mar 13, 2014 at 12:57 PM, Robert P. J. Day
<rpjday(a)crashcourse.ca> wrote:
> recently, i upgraded my ASUS G74S laptop to fedora rawhide
Wrong list. You want the Fedora Test list.
ah, quite so, i'd forgotten there was a separate ML for rawhide.
apologies.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
9:11 a.m.
New subject: after upgrading fedora rawhide this morning, no graphical desktop [SOLVED?]
On Thu, 13 Mar 2014, Kevin Martin wrote:
On 03/13/2014 07:57 AM, Robert P. J. Day wrote:
>
> recently, i upgraded my ASUS G74S laptop to fedora rawhide and it
> was running nicely. then this morning, i did another "yum update",
> which appeared to update well over 200 packages (including a slightly
> newer kernel), after which, when i booted, i had no graphical desktop
> anymore, just the little blue and white fedora logo.
>
> i can still switch to VC2 and log in at the command line (where i am
> now), so i can certainly check log files, but i don't see anything
> immediately amiss.
>
> i rebooted both to the earlier rawhide kernel, and even back to the
> latest fedora 20 official kernel -- same result, the fedora logo in
> the middle of the screen on VC1, but the ability to log in on another
> virtual console.
>
> has anyone else run into this? i have an nvidia graphics card, and
> am running the nouveau driver. i'll keep poking around the log files,
> and if you have any suggestions, i'm all ears.
>
> rday
>
Hmm, sounds similar to what I'm experiencing. When you go into VC2
what does "lsmod | grep nouveau" show? I've found that I've been
having to manually "modprobe nouveau modeset=1" since doing my
update about 4 days ago. I'm not sure why nouveau won't load and I
find that if I don't set the modeset=1 when I do the manual modprobe
that I still can't get X.
it appears to be an SELinux thing -- i did:
# setenforce 0
then:
# systemctl isolate multi-user.target
# systemctl isolate graphical.target
and i have my desktop back. i was inspired to try this by running:
# journalctl _SYSTEMD_UNIT=gdm.service
and, down toward the bottom of 40K+ lines of output, saw:
... snip ...
Mar 13 09:54:44 localhost.localdomain gdm-launch-environment][2508]:
pam_systemd(gdm-launch-environment:session): Failed to create session: Access denied
Mar 13 09:54:44 localhost.localdomain gdm-launch-environment][2508]:
pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
Mar 13 09:54:44 localhost.localdomain gdm[2446]: GLib: g_variant_new_string: assertion
'string != NULL' failed
Mar 13 09:54:44 localhost.localdomain gdm[2446]:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit
was not provided by any .service files
Mar 13 09:54:45 localhost.localdomain /usr/bin/dbus-launch[2519]: libGL error: failed to
open drm device: Permission denied
Mar 13 09:54:45 localhost.localdomain /usr/bin/dbus-launch[2519]: libGL error: failed to
load driver: nouveau
Mar 13 09:54:45 localhost.localdomain /usr/bin/dbus-launch[2519]:
gnome-session-is-accelerated: llvmpipe detected.
Mar 13 09:54:45 localhost.localdomain gnome-session[2519]: gnome-session[2519]: WARNING:
Could not get session id for session. Check that logind is properly installed and
pam_systemd is getting used at login.
Mar 13 09:54:45 localhost.localdomain gnome-session[2519]: WARNING: Could not get session
id for session. Check that logind is properly installed and pam_systemd is getting used at
login.
Mar 13 09:54:45 localhost.localdomain gnome-session[2519]: WARNING: Could not parse
desktop file orca-autostart.desktop or it references a not found TryExec binary
Mar 13 09:54:45 localhost.localdomain gnome-session[2519]: gnome-session[2519]: WARNING:
Could not parse desktop file orca-autostart.desktop or it references a not found TryExec
binary
Mar 13 09:54:45 localhost.localdomain gnome-session[2519]: Entering running state
Mar 13 09:54:45 localhost.localdomain gdm-Xorg-:1[2483]: (II) NOUVEAU(0): EDID vendor
"CMO", prod id 5926
Mar 13 09:54:45 localhost.localdomain gdm-Xorg-:1[2483]: (II) NOUVEAU(0): Printing DDC
gathered Modelines:
Mar 13 09:54:45 localhost.localdomain gdm-Xorg-:1[2483]: (II) NOUVEAU(0): Modeline
"1920x1080"x0.0 138.70 1920 1968 2000 2080 1080 1083 1088 1111 -hsync -vsync
(66.7 kHz eP)
Mar 13 09:54:45 localhost.localdomain gnome-session[2519]: libGL error: failed to open drm
device: Permission denied
Mar 13 09:54:45 localhost.localdomain gnome-session[2519]: libGL error: failed to load
driver: nouveau
... snip ...
as soon as i saw permission errors, i decided on a hunch to turn off
selinux and ... voila. i still don't understand *why* that fixed it,
so i'm open to advice.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
8 a.m.
On 03/13/2014 07:57 AM, Robert P. J. Day wrote:
recently, i upgraded my ASUS G74S laptop to fedora rawhide and it
was running nicely. then this morning, i did another "yum update",
which appeared to update well over 200 packages (including a slightly
newer kernel), after which, when i booted, i had no graphical desktop
anymore, just the little blue and white fedora logo.
i can still switch to VC2 and log in at the command line (where i am
now), so i can certainly check log files, but i don't see anything
immediately amiss.
i rebooted both to the earlier rawhide kernel, and even back to the
latest fedora 20 official kernel -- same result, the fedora logo in
the middle of the screen on VC1, but the ability to log in on another
virtual console.
has anyone else run into this? i have an nvidia graphics card, and
am running the nouveau driver. i'll keep poking around the log files,
and if you have any suggestions, i'm all ears.
rday
Hmm, sounds similar to what I'm experiencing. When you go into VC2 what does
"lsmod | grep nouveau" show? I've found that I've
been having to manually "modprobe nouveau modeset=1" since doing my update about
4 days ago. I'm not sure why nouveau won't load
and I find that if I don't set the modeset=1 when I do the manual modprobe that I
still can't get X.
Kevin
8:11 a.m.
On Thu, 13 Mar 2014, Kevin Martin wrote:
On 03/13/2014 07:57 AM, Robert P. J. Day wrote:
>
> recently, i upgraded my ASUS G74S laptop to fedora rawhide and it
> was running nicely. then this morning, i did another "yum update",
> which appeared to update well over 200 packages (including a slightly
> newer kernel), after which, when i booted, i had no graphical desktop
> anymore, just the little blue and white fedora logo.
>
> i can still switch to VC2 and log in at the command line (where i am
> now), so i can certainly check log files, but i don't see anything
> immediately amiss.
>
> i rebooted both to the earlier rawhide kernel, and even back to the
> latest fedora 20 official kernel -- same result, the fedora logo in
> the middle of the screen on VC1, but the ability to log in on another
> virtual console.
>
> has anyone else run into this? i have an nvidia graphics card, and
> am running the nouveau driver. i'll keep poking around the log files,
> and if you have any suggestions, i'm all ears.
>
> rday
>
Hmm, sounds similar to what I'm experiencing. When you go into VC2
what does "lsmod | grep nouveau" show? I've found that I've been
having to manually "modprobe nouveau modeset=1" since doing my
update about 4 days ago. I'm not sure why nouveau won't load and I
find that if I don't set the modeset=1 when I do the manual modprobe
that I still can't get X.
here's mine:
nouveau 1087913 2
mxm_wmi 12865 1 nouveau
i2c_algo_bit 13257 1 nouveau
drm_kms_helper 50287 1 nouveau
ttm 80479 1 nouveau
drm 283937 4 ttm,drm_kms_helper,nouveau
i2c_core 38476 6 drm,i2c_i801,drm_kms_helper,i2c_algo_bit,nouveau,videodev
wmi 18804 3 mxm_wmi,nouveau,asus_wmi
video 19206 2 nouveau,asus_wmi
i could, i guess, manually unload all modules dependent on nouveau,
or just reboot and add "nouveau.modeset=1" at the kernel command line,
right?
i also checked /sys/module/nouveau/parameters/modeset, which
currently has a value of -1, which i don't understand. still, if it's
a module issue, why would rebooting under an earlier, working kernel
not have fixed this?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
3747
days inactive
3748
days old
10 comments
6 participants
participants (6)
-
Daniel J Walsh -
kevin martin -
Patrick O'Callaghan -
Pete Travis -
Rick Stevens -
Robert P. J. Day