Results 1 to 6 of 6
hello everybody, I've tried to boot directly to the command line without going to the graphics.
last time i tried editing the boot directory but i messed things up. how ...
- 10-28-2009 #1Just Joined!
- Join Date
- Jul 2009
- Posts
- 7
booting directly to the command line or tty2
hello everybody, I've tried to boot directly to the command line without going to the graphics.
last time i tried editing the boot directory but i messed things up. how should i go about it.
thanks.
- 10-28-2009 #2
I'm not sure if this is the "proper" way to do it, but Ubuntu doesn't use /etc/inittab, which is how I would normally go about it.
You can disable the login manager at boot, which should drop you to a console right off.
Code:sudo update-rc.d -f gdm remove
- 10-30-2009 #3Just Joined!
- Join Date
- Jul 2009
- Posts
- 7
thanks a lot
thank u very much. but how can restart my graphics in ubuntu when it freezes.?
by the way any linux pdf tutorials for me.
all the best.
- 10-30-2009 #4
You can edit kernel line of Ubuntu in GRUB Menu to switch to command line mode.
Highlight Ubuntu title In GRUB Menu and press 'e'. Select 'kernel' line and press 'e' again. Add <space> 1 at the end of line and hit 'Enter' key.
Press 'b' and Ubuntu will boot up in command line mode and drop you at Login Prompt.
Highlight Ubuntu title -- e -- select Kernel line -- e -- type 1 -- hit Enter key -- b.
You have to do that whenever you want to switch to command line mode.
Alternatively, boot up in Graphical Mode and press Alt+Ctrl+F3 to switch to command line mode.It is amazing what you can accomplish if you do not care who gets the credit.
New Users: Read This First
- 10-30-2009 #5
Better to fix the freezing perhaps? I'm guessing you're using Ubuntu 9.04 and have an intel graphics card. There are many known problems with Jaunty and Intel graphics. Upgrading to 9.10 should pretty much resolve them.
Or there are a couple of workarounds that might help.
HOWTO: Jaunty Intel Graphics Performance Guide - Ubuntu Forums
I was hit with this Intel bug in Arch awhile ago. The only way I could access the machine and not do a hard shutdown was to log in via a ssh connection.
- 10-30-2009 #6


Reply With Quote
