Solving boot to commandline problem
Hello,
I'm a Slackware user, but I installed Ubuntu on my father's netbook and he's been using it fairly happily for the last year or so. He's currently on vacation and says he "gets an error message" when he tries to boot into Ubuntu. It turns out that the message is just the command prompt: Code:
$USER@$COMPUTER $ I figure I could probably muddle my way through and fix it ... if I had the computer in front of me. I've asked if he's booting into a recovery mode (Ubuntu has that as a boot option, right?), but I doubt he's making that simple of a mistake. Coming from a Slackware background and only slightly familiar with Ubuntu my first thought was to get him to try: Code:
sudo init 4 Thanks! |
"init 4" will not help, as Ubuntu will not use runlevels (but of course it can be configured). You should check /var/log/Xorg.0.log for errors after trying to start "service gdm start".
I suspect that you need to recompile video drivers. If you used proprietary then just download and run installer as root in the console. But it can be anything, you need to check log, also /var/log/syslog. |
Quote:
Any other suggestions? Thanks. |
<aside>
One thing to try is to simply type: sudo startx It may work and, if not, could give some clues as to what is not working. </aside> |
Quote:
Code:
startx |
Very probably. I don't think that's ever worked for me though -- I don't seem to have permission to do so.
Edit: When running Ubuntu and Debian whenever I've been dropped into the shell on startup the way I've started X is by sudoing it as it doesn't work without. I know it's different but I tried to run: startx -- :1 vt8 Just now and the result was: X: user not authorized to run the X server, aborting. |
Code:
sudo tellinit:3: Code:
defaultrunlevel |
With out more info it is hard to say what the problem is.
Ubuntu takes you to a # (root) prompt in recovery mode so that does seem to say he is not booting that way. Code:
startx Adding sudo to it would indeed, if it worked, put him in as root and this could only make things worse. |
Ok thanks for the answers. I've just heard back and startx reports (in his words) something like:
Code:
You do not have access to program or feature X Code:
X: user not authorized to run the X server, aborting. As I said, I'd be digging through the X.org logs, but I'd rather not have him do that... though maybe Code:
grep EE /var/log/Xorg.0.log |
Better using context feature
Code:
grep -C 3 EE /var/log/Xorg.0.log Code:
cat /var/log/Xorg.0.log |
Photos are a good idea... results pending.
|
1 Attachment(s)
Ok, finally heard back with the attached jpg, but as you can see the grep command was typed incorrectly so not much to go on. Could a full disk or /tmp partition be behind this I wonder?
|
1. startx will not work without root privilages. Anyway, in Ubuntu to start X with normal login window, is command
Code:
sudo service gdm start Code:
sudo /etc/init.d/gdm start Code:
df -h Code:
grep -C 5 EE /var/log/Xorg.0.log |
Quote:
Quote:
I think in the end, I will probably end up fixing this when he has returned and I have it my own hands! |
Quote:
|
All times are GMT -5. The time now is 10:23 AM. |