On 07/02/2015 12:05 PM, Matthew Woehlke wrote:
The display is unchanged; I still see the login dialog / prompt /
whatever was on screen previously. (Although with updated kernels, TTY
switching results in an unrecoverable black screen.)
Have you tried the Magic SysRq key? Even in single-user m
On Thu, Jul 2, 2015 at 1:05 PM, Matthew Woehlke
wrote:
> On 2015-07-02 13:56, Chris Murphy wrote:
>> On Thu, Jul 2, 2015 at 11:41 AM, Matthew Woehlke wrote:
>>> I recently installed F22 (KDE spin) from scratch on a new Dell M6800.
>>> The Live CD seems to run okay, but when I try to boot the insta
On 2015-06-23 21:22, Suvayu Ali wrote:
> On Tue, Jun 23, 2015 at 10:00:14AM -0400, Matthew Woehlke wrote:
>> On 2015-06-22 14:15, Marko Vojinovic wrote:
>>> As a side note, AFAIK now sshd is disabled on fresh installs. Do a
>>> "systemctl enable sshd" and "systemctl start sshd" (and verify with
>>>
On 2015-07-02 13:56, Chris Murphy wrote:
> On Thu, Jul 2, 2015 at 11:41 AM, Matthew Woehlke wrote:
>> I recently installed F22 (KDE spin) from scratch on a new Dell M6800.
>> The Live CD seems to run okay, but when I try to boot the installed OS,
>> it freezes when I try to log in. The machine is e
On Thu, Jul 2, 2015 at 11:41 AM, Matthew Woehlke
wrote:
> I recently installed F22 (KDE spin) from scratch on a new Dell M6800.
> The Live CD seems to run okay, but when I try to boot the installed OS,
> it freezes when I try to log in. The machine is effectively unusable as
> a result.
Is it act
I recently installed F22 (KDE spin) from scratch on a new Dell M6800.
The Live CD seems to run okay, but when I try to boot the installed OS,
it freezes when I try to log in. The machine is effectively unusable as
a result.
Through much pain and anguish I have managed to install updates (up to
dat
On Tue, Jun 23, 2015 at 10:00:14AM -0400, Matthew Woehlke wrote:
> On 2015-06-22 14:15, Marko Vojinovic wrote:
> > As a side note, AFAIK now sshd is disabled on fresh installs. Do a
> > "systemctl enable sshd" and "systemctl start sshd" (and verify with
> > "systemctl status sshd"), and retry to lo
On 2015-06-22 14:15, Marko Vojinovic wrote:
> If the same set of steps don't work and then start working and then
> don't work again, I am thinking memory or the harddrive.
Hmm... and... first try (just now) to boot the LiveCD got stuck ('LSB
init' IIRC). Second worked...
> Boot from a live image
On Mon, 22 Jun 2015 12:16:09 -0400
Matthew Woehlke wrote:
> On 2015-06-20 06:38, Tim wrote:
> > Allegedly, on or about 19 June 2015, Matthew Woehlke sent:
> >> Remember, I *can't log in*. Not via kdm, not in a TTY, not over
> >> ssh, *not at all*. No login --> never even tries to start X (not
> >
On 2015-06-20 06:38, Tim wrote:
> Allegedly, on or about 19 June 2015, Matthew Woehlke sent:
>> Remember, I *can't log in*. Not via kdm, not in a TTY, not over ssh,
>> *not at all*. No login --> never even tries to start X (not as my
>> user, anyway).
>>
>>
>> (Hrm... on that note, it's interesting
On 2015-06-19 20:27, Suvayu Ali wrote:
> On Fri, Jun 19, 2015 at 05:47:49PM -0400, Matthew Woehlke wrote:
>> On 2015-06-19 17:27, Suvayu Ali wrote:
>>> In emergency mode, could you look at what logind was up to in the
>>> previous boot? Something like the following should work:
>>>
>>> # journal
On Fri, 2015-06-19 at 17:04 -0400, Matthew Woehlke wrote:
> On 2015-06-19 16:29, Joe Zeff wrote:
> > On 06/19/2015 01:13 PM, Matthew Woehlke wrote:
> > > I'm increasingly unconvinced that it has anything whatsoever to
> > > do with
> > > X. More like it can't start a login session. I'd guess that
Allegedly, on or about 19 June 2015, Matthew Woehlke sent:
> Remember, I *can't log in*. Not via kdm, not in a TTY, not over ssh,
> *not at all*. No login --> never even tries to start X (not as my
> user, anyway).
>
>
> (Hrm... on that note, it's interesting to note that the one and only
> GUI pr
On Fri, Jun 19, 2015 at 05:47:49PM -0400, Matthew Woehlke wrote:
> On 2015-06-19 17:27, Suvayu Ali wrote:
> > In emergency mode, could you look at what logind was up to in the
> > previous boot? Something like the following should work:
> >
> > # journalctl -b -1 -u systemd-logind
> >
> > You
On 06/19/2015 02:47 PM, Matthew Woehlke wrote:
(@Joe, boot.log seems to just be the systemd startup output... nothing
obvious there...)
Oh well, it was worth looking. BTW, I don't know if this will work from
the emergency shell, but have you tried logging in from there as
yourself? Just typ
On 2015-06-19 17:27, Suvayu Ali wrote:
> In emergency mode, could you look at what logind was up to in the
> previous boot? Something like the following should work:
>
> # journalctl -b -1 -u systemd-logind
>
> You could compare with the current boot by switching the -1 to 0. Maybe
> this wil
On Fri, Jun 19, 2015 at 05:04:40PM -0400, Matthew Woehlke wrote:
>
> The only way I can interact with the system *in any way* is in emergency
> mode.
In emergency mode, could you look at what logind was up to in the
previous boot? Something like the following should work:
# journalctl -b -1 -
On 06/19/2015 02:04 PM, Matthew Woehlke wrote:
Yes.*No* user can log in. Not the user I created at install, not a
newly created user, ***not root***.
The only way I can interact with the system*in any way* is in emergency
mode.
Thank you. I'm sure that you mentioned this at the beginning, b
On 2015-06-19 16:29, Joe Zeff wrote:
> On 06/19/2015 01:13 PM, Matthew Woehlke wrote:
>> I'm increasingly unconvinced that it has anything whatsoever to do with
>> X. More like it can't start a login session. I'd guess that recovery
>> mode does something that's just a bit different, as that is the
On 06/19/2015 01:13 PM, Matthew Woehlke wrote:
I'm increasingly unconvinced that it has anything whatsoever to do with
X. More like it can't start a login session. I'd guess that recovery
mode does something that's just a bit different, as that is the*only*
way I can get to a usable environment o
On 2015-06-19 15:10, Joe Zeff wrote:
> On 06/19/2015 11:26 AM, Matthew Woehlke wrote:
>> On 2015-06-18 17:47, Joe Zeff wrote:
>>> >There should also be a ~/.xsession-errors.old and with luck, it
>>> >might have something in it.
>> There isn't. (I'd be inclined to suspect that things have only gotte
On 06/19/2015 11:26 AM, Matthew Woehlke wrote:
On 2015-06-18 17:47, Joe Zeff wrote:
>There should also be a ~/.xsession-errors.old and with luck, it
>might have something in it.
There isn't. (I'd be inclined to suspect that things have only gotten to
the point where a .xsession-errors would be
On 2015-06-18 17:46, Rick Stevens wrote:
> Maybe we can catch log entries before it completely dies. Bring the
> system up in single user mode, then edit /etc/systemd/journald.conf.
> Find the line:
>
> #ForwardToSyslog=no
>
> Change it to:
>
> ForwardToSyslog=yes
>
> and save the file.
On 2015-06-18 17:47, Joe Zeff wrote:
> There should also be a ~/.xsession-errors.old and with luck, it
> might have something in it.
There isn't. (I'd be inclined to suspect that things have only gotten to
the point where a .xsession-errors would be created the one time.)
--
Matthew
--
users m
On 06/18/2015 02:27 PM, Matthew Woehlke wrote:
On 2015-06-18 17:16, Rick Stevens wrote:
On 06/18/2015 01:52 PM, Matthew Woehlke wrote:
On 2015-06-18 14:04, Paul Cartwright wrote:
On 06/18/2015 12:54 PM, Matthew Woehlke wrote:
(¹ *Once and only once* I was able to log in, but the system froze
On 06/18/2015 02:27 PM, Matthew Woehlke wrote:
Nothing in any of the Xorg.*.log*'s jumps out at me.
~user/.xsession-errors is empty.
That would probably tell us quite a bit if we knew just when in the
session the file gets created. Alas, I don't, but maybe somebody else
will. There should a
On 06/18/2015 02:27 PM, Matthew Woehlke wrote:
On 2015-06-18 17:16, Rick Stevens wrote:
On 06/18/2015 01:52 PM, Matthew Woehlke wrote:
On 2015-06-18 14:04, Paul Cartwright wrote:
On 06/18/2015 12:54 PM, Matthew Woehlke wrote:
(¹ *Once and only once* I was able to log in, but the system froze
On 2015-06-18 17:16, Rick Stevens wrote:
> On 06/18/2015 01:52 PM, Matthew Woehlke wrote:
>> On 2015-06-18 14:04, Paul Cartwright wrote:
>>> On 06/18/2015 12:54 PM, Matthew Woehlke wrote:
(¹ *Once and only once* I was able to log in, but the system froze as
soon as I tried to run an appli
On 06/18/2015 01:52 PM, Matthew Woehlke wrote:
Hmm... is it expected that there are no entries*at all* for the last
few boots? The only entries I have are for June 5. (And yes, my system
date is correct: June 18.) Anyway, I have no idea what I'd be looking for.
If memory serves, most of the fi
On 06/18/2015 01:52 PM, Matthew Woehlke wrote:
On 2015-06-18 14:04, Paul Cartwright wrote:
On 06/18/2015 12:54 PM, Matthew Woehlke wrote:
(¹ *Once and only once* I was able to log in, but the system froze as
soon as I tried to run an application. Also, I can log in in single-user
mode, but this
On 2015-06-18 12:54, Matthew Woehlke wrote:
> I just installed F22 (KDE spin) from scratch on a new Dell M6800. The
> Live CD seemed to run okay, but when I try to boot the installed OS, it
> (almost¹) invariably freezes when I try to log in. The machine is
> effectively unusable as a result.
HEY!
On 2015-06-18 14:04, Paul Cartwright wrote:
> On 06/18/2015 12:54 PM, Matthew Woehlke wrote:
>> (¹ *Once and only once* I was able to log in, but the system froze as
>> soon as I tried to run an application. Also, I can log in in single-user
>> mode, but this isn't good for much but running dnf and
On 18.06.2015, Matthew Woehlke wrote:
> I don't know offhand how to set up serial login
Set up the console and output in grub.cfg:
serial --speed=115200 --unit=0 --word=8 --parity=no --stop=1
terminal_input serial
terminal_output serial
Then tell the kernel to use it (grub.cfg, as a kernel par
On 06/18/2015 12:54 PM, Matthew Woehlke wrote:
> (¹ *Once and only once* I was able to log in, but the system froze as
> soon as I tried to run an application. Also, I can log in in single-user
> mode, but this isn't good for much but running dnf and fiddling with
> enabled services. I *have* appli
(First try apparently got eaten; apologies if this is a duplicate.)
I just installed F22 (KDE spin) from scratch on a new Dell M6800. The
Live CD seemed to run okay, but when I try to boot the installed OS, it
(almost¹) invariably freezes when I try to log in. The machine is
effectively unusable a
35 matches
Mail list logo
