Re: Runlevel 3 after fedup

2013-05-02 Thread ellis
To add to this, I've recently found out the problem also happens when I come up in runlevel 5 and then later switch to 3. -- http://yosemitenews.info/ -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinf

Re: Runlevel 3 after fedup

2013-02-18 Thread ellis
> And, out of simple curiosity, do you ever have X driver issues if there's not > been a kernel > or driver update? None that I can remember. But coming up in text mode is also handy when I'm doing a lot of reboots (e.g. trying to fix this current problem). And I have had the system hang when I

Re: Runlevel 3 after fedup

2013-02-17 Thread Joe Zeff
On 02/17/2013 01:20 PM, el...@spinics.net wrote: Yes, I always boot into runlevel 3. If nothing else, it allows me to deal with X driver problems. OK, thanx. Knowing that removes some possibilities. And, out of simple curiosity, do you ever have X driver issues if there's not been a kernel

Re: Runlevel 3 after fedup

2013-02-17 Thread ellis
> I assume you can login as a normal user on a VT from graphical mode? Yes, if I come up as runlevel 5 logins work as they should on both graphical and vt screens. > systemd auto-spawns VTs on-demand so they're started a little > differently. If that's working, the only thing I can think of is

Re: Runlevel 3 after fedup

2013-02-17 Thread T.C. Hollingsworth
On Sun, Feb 17, 2013 at 2:32 PM, wrote: >> So you get a normal login prompt, just nobody else but root can login? >> That's probably not systemd. > > I suspect there's a flag that gets set somewhere when the boot scripts > finsih running. Just don't know where it is or what sets it. I assume yo

Re: Runlevel 3 after fedup

2013-02-17 Thread ellis
> So you get a normal login prompt, just nobody else but root can login? > That's probably not systemd. I suspect there's a flag that gets set somewhere when the boot scripts finsih running. Just don't know where it is or what sets it. > Okay that looks good. Does > /etc/systemd/system/getty.ta

Re: Runlevel 3 after fedup

2013-02-17 Thread T.C. Hollingsworth
Oops, I seem to have misread the original post. I was under the impression that you weren't getting a login prompt at all, but upon rereading I see you said: > After upgrade from 17 to 18 with fedup and installing all the updates I was > unable to login as any user other than root. When I tried I

Re: Runlevel 3 after fedup

2013-02-17 Thread ellis
> Are you normally in the habit of booting that way, or was this something > special you were doing after the upgrade? Yes, I always boot into runlevel 3. If nothing else, it allows me to deal with X driver problems. -- http://yosemitenews.info/ -- users mailing list users@lists.fedoraproject.

Re: Runlevel 3 after fedup

2013-02-17 Thread ellis
> Do you get a login prompt if you switch VTs from graphical mode (e.g. > CTRL+ALT+F[2-6])? Yes. > What is the output of: > systemctl show default.target Id=multi-user.target Names=default.target runlevel2.target multi-user.target runlevel4.target runlevel3.target Requires=basic.target Wants=

Re: Runlevel 3 after fedup

2013-02-17 Thread Joe Zeff
On 02/16/2013 03:53 PM, el...@spinics.net wrote: After beating my head against the wall I finally tried booting to runlevel 5 instead of 3. That fixed the issue. But booting to runlevel 3 and switching to 5 doesn't work. Are you normally in the habit of booting that way, or was this something

Re: Runlevel 3 after fedup

2013-02-16 Thread T.C. Hollingsworth
On Sat, Feb 16, 2013 at 4:53 PM, wrote: > After upgrade from 17 to 18 with fedup and installing all the updates I was > unable to login as any user other than root. When I tried I was greeted with > the message: "System is booting up". > > After beating my head against the wall I finally tried bo

Runlevel 3 after fedup

2013-02-16 Thread ellis
After upgrade from 17 to 18 with fedup and installing all the updates I was unable to login as any user other than root. When I tried I was greeted with the message: "System is booting up". After beating my head against the wall I finally tried booting to runlevel 5 instead of 3. That fixed the is