This may be quite a bit more serious than I suspected. No matter what I do, the rhgb client tries to start to, but adding sigle to the kernel arguments did succeed in getting me a command prompt.
I then went to:
/var/cache/yum/development/packages
and tried to:
rpm -Uvh --force xorg*6.8.1-6*
I thought this would fix all my woes. Instead, it made the mystery even deeper. I was told that /usr/lib/libpopt.so.0 has invalid ELF headers.
I tried booting this was twice to see if somehow the kernel had any affect on this, although I couldn't see how it could. I used the kernel that came with T2 and the latest one yum downloaded yesterday. Same result either way.
It would appear that yum trashed more than just my x setup.
If anyone has any ideas I sure would like to hear them.
--andy
Quoting Paul Iadonisi pri.rhl3@iadonisi.to:
On Tue, 2004-11-02 at 10:36 -0600, Satish Balay wrote:
On Tue, 2 Nov 2004, Douglas Furlong wrote:
The boot parameter "3" brings the system to "multi user, no X".
The OP has problem with runlevel-3 - hence 'single' was sugested.
I'm suspecting that since there was a problem both with rhgb stilling being run *and* runlevel 3 being ignored that maybe the OP hit escape instead of enter after changing the grub kernel parameters. I'd suggest trying again, but after hitting escape before the three second timeout expires and hitting 'a' to edit the kernel command line (placing the cursor at the end of the command line), delete the rhgb parameter and add '3' and then be sure to hit enter to boot the kernel with the new command line.
-- -Paul Iadonisi Senior System Administrator Red Hat Certified Engineer / Local Linux Lobbyist Ever see a penguin fly? -- Try Linux. GPL all the way: Sell services, don't lease secrets
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-test-list