9:17 p.m.
I replaced the ATI video card with my old GEForce 9600GT.
Also, the cat unplugged my USB ATI TV Wonder 650.
The F14 Alpha install got an unhandled exception when I
tried to tell it to mount sda1 as an NTFS file system.
I restarted the DVD installation, which completed nominally.
I then reran Ubuntu's grub-mkconfig and booted F14.
The system>install still does not bother to install anything,
but is useful for identifying files to install with yum.
After a couple of yum upgrade cycles F14 is starting to
look like Linux again. It does require a manual
root login and init 5 to get to the Krypton crystal
login.
--
Chuck Forsberg WA7KGX N2469R caf(a)omen.com www.omen.com
Developer of Industrial ZMODEM(Tm) for Embedded Applications
Omen Technology Inc "The High Reliability Software"
10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430
4:11 a.m.
On Thu, 2010-08-26 at 19:17 -0700, Chuck Forsberg WA7KGX N2469R wrote:
After a couple of yum upgrade cycles F14 is starting to
look like Linux again. It does require a manual
root login and init 5 to get to the Krypton crystal
login.
My F14 system is doing this as well, updated as of yesterday. Looks
like it stops during boot and requires root password for maint. But
after that, you can init 5 and boot continues to gdm login screen.
--
Mike Chambers
Madisonville, KY
"Best lil town on Earth!"
4:24 a.m.
2010/8/27 Mike Chambers <mike(a)miketc.net>
On Thu, 2010-08-26 at 19:17 -0700, Chuck Forsberg WA7KGX N2469R
wrote:
> After a couple of yum upgrade cycles F14 is starting to
> look like Linux again. It does require a manual
> root login and init 5 to get to the Krypton crystal
> login.
My F14 system is doing this as well, updated as of yesterday. Looks
like it stops during boot and requires root password for maint. But
after that, you can init 5 and boot continues to gdm login screen.
could be this:
https://fedoraproject.org/wiki/Common_F14_bugs#systemd_package_update_bre...
4:27 a.m.
On Fri, 2010-08-27 at 12:24 +0300, cornel panceac wrote:
2010/8/27 Mike Chambers <mike(a)miketc.net>
On Thu, 2010-08-26 at 19:17 -0700, Chuck Forsberg WA7KGX
N2469R wrote:
> After a couple of yum upgrade cycles F14 is starting to
> look like Linux again. It does require a manual
> root login and init 5 to get to the Krypton crystal
> login.
My F14 system is doing this as well, updated as of yesterday.
Looks
like it stops during boot and requires root password for
maint. But
after that, you can init 5 and boot continues to gdm login
screen.
could be this:
https://fedoraproject.org/wiki/Common_F14_bugs#systemd_package_update_bre...
And it should be fixed with systemd-8-2 IIRC.
Martin
9:18 a.m.
On Fri, 2010-08-27 at 11:27 +0200, Martin Sourada wrote:
On Fri, 2010-08-27 at 12:24 +0300, cornel panceac wrote:
>
>
> 2010/8/27 Mike Chambers <mike(a)miketc.net>
> On Thu, 2010-08-26 at 19:17 -0700, Chuck Forsberg WA7KGX
> N2469R wrote:
>
> > After a couple of yum upgrade cycles F14 is starting to
> > look like Linux again. It does require a manual
> > root login and init 5 to get to the Krypton crystal
> > login.
>
>
> My F14 system is doing this as well, updated as of yesterday.
> Looks
> like it stops during boot and requires root password for
> maint. But
> after that, you can init 5 and boot continues to gdm login
> screen.
>
> could be this:
>
https://fedoraproject.org/wiki/Common_F14_bugs#systemd_package_update_bre...
And it should be fixed with systemd-8-2 IIRC.
Still not fixed, with updates as of this morning.
--
Mike Chambers
Madisonville, KY
"Best lil town on Earth!"
9:49 a.m.
> > My F14 system is doing this as well, updated as of
yesterday.
> > Looks
> > like it stops during boot and requires root password for
> > maint. But
> > after that, you can init 5 and boot continues to gdm login
> > screen.
> >
> > could be this:
> >
https://fedoraproject.org/wiki/Common_F14_bugs#systemd_package_update_bre...
> And it should be fixed with systemd-8-2 IIRC.
Still not fixed, with updates as of this morning.
The prefdm problem is new. It appears to be that for some reason it won't
run properly during the boot, but you can start it by the time you get
the maintenance prompt.
I had thought that I might have hosed up my systems on my own, but since
other people are seeing this, I'll make sure there is a bug filed.
10:01 a.m.
On Sat, 28 Aug 2010 09:49:13 -0500
Bruno Wolff III wrote:
The prefdm problem is new. It appears to be that for some reason it
won't
run properly during the boot, but you can start it by the time you get
the maintenance prompt.
Weird, I have all the updates and I'm getting a normal login prompt
(I did have to fix the default.target symlink by had a couple of
updates ago). I wonder if it is a GDM versus KDM problem? - I'm
running KDM.
10:34 a.m.
On Sat, Aug 28, 2010 at 11:01:36 -0400,
Tom Horsley <horsley1953(a)gmail.com> wrote:
On Sat, 28 Aug 2010 09:49:13 -0500
Bruno Wolff III wrote:
> The prefdm problem is new. It appears to be that for some reason it won't
> run properly during the boot, but you can start it by the time you get
> the maintenance prompt.
Weird, I have all the updates and I'm getting a normal login prompt
(I did have to fix the default.target symlink by had a couple of
updates ago). I wonder if it is a GDM versus KDM problem? - I'm
running KDM.
I'm using gdm by fallback.
I tested for path issues and tried removing --nodaemon (as that doesn't
seem to be a documented gdm option and may just be for kdm).
Maybe /home isn't available when it is starting. Someone mentioned that gdm
might be looking at ~gdm for some setup information. My /home is a separate
encrypted partition on the machines I have seen the problem on. I have a laptop
that isn't set up that way, but that I haven't updated for a few days. Seeing
if it has the problem after updating to current F14 would be a good test for
me to do.
11:11 a.m.
On Sat, Aug 28, 2010 at 11:55:59 -0400,
Tom Horsley <horsley1953(a)gmail.com> wrote:
On Sat, 28 Aug 2010 10:34:40 -0500
Bruno Wolff III wrote:
> My /home is a separate
> encrypted partition on the machines I have seen the problem on.
I just have one partition at the moment and no encryption
going on, so that is a difference.
It looks like it is probably related to the dbus service. I had been mostly
been trying stuff on my work machine yesterday and the one here was a bit
different. The prefdm service still wasn't starting even in maintenance
mode. I ran gdm directly as otherwise the error was sent to /dev/null.
It complained about dbus. I started the dbus service and then I was able to
start the prefdm service.
So I am back to not knowing if something got stuffed up locally due to
upgrading and down grading or if there is an actual problem with the
default setup not making sure dbus was up before trying to start prefdm.
11:54 a.m.
On Sat, Aug 28, 2010 at 11:11:26 -0500,
Bruno Wolff III <bruno(a)wolff.to> wrote:
So I am back to not knowing if something got stuffed up locally due to
upgrading and down grading or if there is an actual problem with the
default setup not making sure dbus was up before trying to start prefdm.
It was a matter of dbus.service not being enabled. This probably got busted
as I was doing upgrades and down grades to keep in sync with F14 + testing.
I also needed to change default.target to point into /lib instead of /etc.
So the two f14 machines I have at home are working.
At work I thought I had tried enabling dbus.service, but maybe I did
something wrong. I'll take a look at it Monday.
5014
days inactive
5015
days old
10 comments
6 participants
participants (6)
-
Bruno Wolff III -
Chuck Forsberg WA7KGX -
cornel panceac -
Martin Sourada -
Mike Chambers -
Tom Horsley