Ok, here's a question for all you gurus out there. I have a problem, and I know how to fix it, but I can't get to a point where I can fix it. I got frustrated, and decided to beg for help.
I used yum to update a FC3 T2 system to a T3 system. All went well enough I thought. I noticed that I had installed a new kernel, so I decided to reboot to see how it worked. Well, the upgrade has trashed X. I thought, no problem, I'll just disable rhgb, and boot, X will go a little crazy, but I'll go to tty2 and roll back X, and then ask here why the new X messed me up.
So, I boot to GRUB and remove rhgb from the kernel arguments. But, rhgb is still used, and everytime it screws up. By the time the system is booted, X is respanwing like crazy and you can't log in even at non-graphical screen. I go to tty2 and type in root and it blinks and it asks me for my login again. No opportunity to enter my password.
So, from the grub screen how can I disable rhgb and boot to 3 instead of 5? I've thought about using the rescue cd to edit my grub.conf file, but I don't understand why editing the kernel args at boot doesn't work.
I would appreciate any ideas on how I can eliminate X from my boot sequence long enough to roll-back X.
BTW: does anyone have any idea why X.org 6.8.1-12 trashed my installation?
Thanks andy
On Tue, 2 Nov 2004, achoens@frontiernet.net wrote:
So, I boot to GRUB and remove rhgb from the kernel arguments. But, rhgb is still used, and everytime it screws up. By the time the system is booted, X is respanwing like crazy and you can't log in even at non-graphical screen. I go to tty2 and type in root and it blinks and it asks me for my login again. No opportunity to enter my password.
So, from the grub screen how can I disable rhgb and boot to 3 instead of 5? I've thought about using the rescue cd to edit my grub.conf file, but I don't understand why editing the kernel args at boot doesn't work.
I would appreciate any ideas on how I can eliminate X from my boot sequence long enough to roll-back X.
BTW: does anyone have any idea why X.org 6.8.1-12 trashed my installation?
Sounds like removing 'rhgb' worked, but adding '3' didn't. I'd try 'single' instead of '3'
I might have seen '3' not working before - but not sure. Perhaps its a bugzilla item.
Satish
remove rhgb from boot parameters and add single This will boot you in single user mode (no X) Here you can update your machine to get latest Xorg which should be quite stable: yum update
,Folke
On Tue, 2 Nov 2004 14:42:56 +0000, achoens@frontiernet.net achoens@frontiernet.net wrote:
Ok, here's a question for all you gurus out there. I have a problem, and I know how to fix it, but I can't get to a point where I can fix it. I got frustrated, and decided to beg for help.
I used yum to update a FC3 T2 system to a T3 system. All went well enough I thought. I noticed that I had installed a new kernel, so I decided to reboot to see how it worked. Well, the upgrade has trashed X. I thought, no problem, I'll just disable rhgb, and boot, X will go a little crazy, but I'll go to tty2 and roll back X, and then ask here why the new X messed me up.
So, I boot to GRUB and remove rhgb from the kernel arguments. But, rhgb is still used, and everytime it screws up. By the time the system is booted, X is respanwing like crazy and you can't log in even at non-graphical screen. I go to tty2 and type in root and it blinks and it asks me for my login again. No opportunity to enter my password.
So, from the grub screen how can I disable rhgb and boot to 3 instead of 5? I've thought about using the rescue cd to edit my grub.conf file, but I don't understand why editing the kernel args at boot doesn't work.
I would appreciate any ideas on how I can eliminate X from my boot sequence long enough to roll-back X.
BTW: does anyone have any idea why X.org 6.8.1-12 trashed my installation?
Thanks andy
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-test-list
On Tue, 2004-11-02 at 15:54 +0100, Folke Lemaitre wrote:
remove rhgb from boot parameters and add single This will boot you in single user mode (no X) Here you can update your machine to get latest Xorg which should be quite stable: yum update
,Folke
<snip> Just to clear some thing up...
The boot perameter "single" aka "1" brings the machine to "single user level" this does not start any networking services, an a WHOLE bunch of other stuff. This is a bare bones running system, with minimal applications running. If the user was to "update" there system after booting to single, they would have to run service network start (or manually configure ethX).
The boot parameter "3" brings the system to "multi user, no X".
They are significantly different.
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 guess to get networking - he could do (after booting into single user mode):
init 3
And then get the latest kernel/xorg packages and try again.
Satish
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.
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
-
Andrew Choens -
Douglas Furlong -
Folke Lemaitre -
Paul Iadonisi -
Satish Balay