since it sounds like the system is going into a non-multi-user mode by default, lets try a test to see if it will go to a full X session.<br><br>boot it to the root login prompt and enter the root password. run telinit 3 and log in as a regular user. run startx and test if the system x will run<br>
<br>If all of that succeeds, logout as regular user and back in as root and run telinit 5. If that's OK then the upgrade broke and didn't finish configuring the grub setting.<br><br>So the file to edit manually in fedora-land is /boot/grub/grub.conf and in ubuntu-land it's /boot/grub/menu.1st (I think). That is what grub uses to know what stuff to pass to the kernel during the initial start up. Odds are you won't find "single" on any kernel line but if you do, delete it.<br>
<br>Maybe I'm being stubborn but I _like_ /etc/inittab. However adding RUNLEVEL=5 to the grub kernel line won't break anything.<br><br><div class="gmail_quote">On Mon, Jul 5, 2010 at 5:18 PM, drifter <span dir="ltr"><<a href="mailto:drifter@oppositelock.org">drifter@oppositelock.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">I continue my descent into madness with this issue.<br>
<br>
{Someone asked about the version of Grub. It is 0.97}<br>
<br>
With the help and hints of this community I have been exploring<br>
the idea that I have an "upstart" problem.<br>
<br>
Watching the boot process carefully, I see that I get an Ubuntu<br>
splash screen, complete with graphic for maybe two tenths of a<br>
second before the command prompt appears. That indicates to<br>
me that for a brief moment the Xserver is running. Then, I'm<br>
guessing, something kills it.<br>
<br>
Hunting around I discovered /usr/share/doc/upstart. This directory contains<br>
the file, README.Debian.gz. Ha, I thought. the answer to my problem may lie<br>
within. But the file is owned by root, and there is no way for Joe user<br>
to unpack the file!!!!!!!! Sometimes I just do not understand the<br>
convoluted minds of programmers. What sort of peeled idiot would make<br>
a README file unreadable?<br>
<br>
Had to chown the file AND the directory to gain access.<br>
<br>
Now the fun begins:<br>
<br>
Reading the README file led me to /etc/init/rc-sysinit.conf<br>
<br>
It contains these lines:<br>
<br>
# Default runlevel, this may be overriden on the kernel command line<br>
#or by faking an old /etc/inittab entry<br>
env DEFAULT_RUNLEVEL=2<br>
<br>
<br>
Further down in the same file these lines appear:<br>
<br>
# Check kernel command-line for typical arguments<br>
for ARG in $(cat /proc/cmdline)<br>
do<br>
case "${ARG}" in<br>
-b|emergency)<br>
# Emergency shell<br>
[ -n "${FROM_SINGLE_USER_MODE}" ] || sulogin<br>
;;<br>
[0123456sS])<br>
# Override runlevel<br>
DEFAULT_RUNLEVEL="${ARG}"<br>
;;<br>
-s|single)<br>
# Single user mode<br>
[ -n "${FROM_SINGLE_USER_MODE}" ] || DEFAULT_RUNLEVEL=S<br>
;;<br>
esac<br>
done<br>
<br>
Doing <cat/proc/cmdline> returns this:<br>
<br>
root=UUID=[long HEX string] ro quiet splash<br>
<br>
<br>
Now I have new questions:<br>
<br>
If I were to change the DEFAULT_RUNLEVEL to 5, would that help?<br>
<br>
----------------------<br>
<br>
To answer some other questions:<br>
<br>
David Tomaschik asked if there any lines above the root prompt?<br>
Nothing the least bit unusual there. The prompt I get needs a login/pswd<br>
pair and then I get a new prompt and can type "startx"<br>
<br>
I tried following David's suggestion of booting in recovery mode. That may<br>
have helped some of the underlying problems, but at the end of that process<br>
I am still looking at the login prompt. The Xserver is not running.<br>
Trying a reboot. Well, that's interesting. Logged in and typed "shutdown<br>
now" only to be told that I have to be root to do that. So tried "sudo<br>
shutdown now" and it still wanted the root password, not my user password.<br>
Only this is Ubuntu, and I have no earthly idea what the root password<br>
might be. I never had a chance to set one.<br>
<br>
So I gave up and hit the power button. on restart I got the login prompt<br>
again.<br>
<br>
Thinking about Brian Pitts comments, how can I check the kernel arguments<br>
and erase the "single" if it appears there? And should I then replace it<br>
with something else?<br>
<br>
My current plan is to backup /home and run a fresh install from the<br>
DVD I have in hand if I can't get this to work pretty damn soon now. :)<br>
<br>
If that doesn't work, then I will try installing FC13.<br>
<br>
For now I'd prefer to stay with Ubuntu, as the new version provides a<br>
driver for the ethernet chip and can use the microphone so I can<br>
use Skype to talk with my grandson. Previous version of Ubuntu<br>
did not support either.<br>
<br>
Sean<br>
<div class="im"><br>
<br>
<br>
On Monday 05 July 2010 12:37:58 Brian Pitts wrote:<br>
> On 07/04/2010 11:34 PM, David Tomaschik wrote:<br>
> > Does it say anything above the root prompt? I rather suspect that<br>
> > something is erroring and aborting the boot. If it's giving you a root<br>
> > prompt with no login, that means it's dropping you into single-user<br>
> > mode, which is triggered either by an error during the boot or by the<br>
> > line "single" being appended to the kernel arguments.<br>
> ><br>
> > You don't really want startx anywhere -- init loads the services<br>
> > requested by the current run environment, and one of those (for<br>
> > Gnome-based "vanilla" Ubuntu) is gdm. GDM will load X and provide you<br>
> > with the login screen you're used to.<br>
> ><br>
> > Menu.lst is not a shell script, so putting startx there will likely<br>
> > only make things worse -- and certainly won't get X going for you.<br>
><br>
> I agree with the above. Your upgrade may not have completed<br>
> successfully.<br>
><br>
> Make sure your computer is plugged into a wired network and turned off.<br>
> Turn it on and hold down shift; this should bring up the GRUB2 menu.<br>
> Select the entry labeled "recovery mode". If you're not in too bad a<br>
> shape, this should eventually load a menu with different automated<br>
> recovery options you can choose. One of them is labeled something like<br>
> "repair broken packages". Choose it and see what happens.<br>
><br>
</div><div><div></div><div class="h5">_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>-- <br>James P. Kinney III<br>Actively in pursuit of Life, Liberty and Happiness <br>Doing pretty well on all 3 pursuits <br><br> Faith is a cop-out. If the only way you can accept an assertion is by faith, then you are conceding that it can’t be taken on its own merits.<br>
Dan Barker, "Losing Faith in Faith", 1992 <br><br>