LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 10-15-2013, 05:45 AM   #1
Jigsaw Syd
LQ Newbie
 
Registered: Oct 2013
Location: Weymouth Dorset
Distribution: Linux Mint
Posts: 8

Rep: Reputation: Disabled
Getting Terminal not OS on start


It was to hell with windows and I have reinstalled Mint but with the 64 bit version.
Once installed I started loading some of my docs and left the laptop for lunch.
Now when I turn it on I get a full screen terminal.
I have little terminal knowledge but it appears that I can load and install from the command line but that is all,and I cannot as yet confirm my installations.
I cannot get into the OS as I am unsure of the command and I don't know what if anything I have done to get here or what I must do to get back into my OS.
Can I get rid of this terminal?
Not only a newbie but a silly "old" sod.

Syd


Info: before the terminal I get
....ubuntu 13.04.....
usb 1-1.1:string descriptor 0 read error:22

Checking dist drive for errors
This may take several minutes

Press C to cancel all checks


Then up pops the full screen terminal

Hope this helps
 
Old 10-15-2013, 06:40 AM   #2
zeebra
Member
 
Registered: Dec 2011
Distribution: Mageia 3, Debian Wheezy, Maemo, Linux Mint 14.
Posts: 200

Rep: Reputation: Disabled
The USB error is not relevant. You are probably having issues with your Xorg, which causes it to display a terminal instead. Or maybe there is some kind of partition issues.

Try "startx" in the terminal. It will try to start X and will tell you where it fails. Also, you can check /home/user/.xsession-error for further details or /var/log/Xorg.0.conf
Running "dmesg > dmesg.file", "glxinfo > glxinfo.file" could also provide helpful. Attach those files here if you can. You should be able to do that using a USB stick or something similar.

If you print those logs here you should get further help. The terminal is a successfull OS boot btw.

"lspci > lspci.file" and "lsmod > lsmod.file" could help people on this forum get further ideas of what is missing.

Last edited by zeebra; 10-15-2013 at 06:45 AM.
 
1 members found this post helpful.
Old 10-16-2013, 06:20 AM   #3
Jigsaw Syd
LQ Newbie
 
Registered: Oct 2013
Location: Weymouth Dorset
Distribution: Linux Mint
Posts: 8

Original Poster
Rep: Reputation: Disabled
Getting Terminal not OS on start for Zeebra

Hi Zeebra,
I have run startx and am nto the OS but the problem still remains, obviously.

I have also run as best as I can the other commands as instructed and here is my copy of the results. Lets hope this is what is required and my problem will be - the result of me being and doing something really silly - solved.
A question I do have. Would it be better for me to backup and re-install?

Thank you,

Syd

Results of terminal commands:-

bash: /usr/bin/mint-fortune: No such file or directory
syd@syd-Aspire-V3-571 ~ $ home/user/.xsession-error
bash: home/user/.xsession-error: No such file or directory
syd@syd-Aspire-V3-571 ~ $ /home/user/.xsession-error
bash: /home/user/.xsession-error: No such file or directory
syd@syd-Aspire-V3-571 ~ $ /home/syd/.xsession-error
bash: /home/syd/.xsession-error: No such file or directory
syd@syd-Aspire-V3-571 ~ $ /var/log/Xorg.Oconf
bash: /var/log/Xorg.Oconf: No such file or directory
syd@syd-Aspire-V3-571 ~ $ dmesg > dmesg.file , gixinfo > gixinfo.file

Usage:
dmesg [options]

Options:
-C, --clear clear the kernel ring buffer
-c, --read-clear read and clear all messages
-D, --console-off disable printing messages to console
-d, --show-delta show time delta between printed messages
-E, --console-on enable printing messages to console
-f, --facility <list> restrict output to defined facilities
-h, --help display this help and exit
-k, --kernel display kernel messages
-l, --level <list> restrict output to defined levels
-n, --console-level <level> set level of messages printed to console
-r, --raw print the raw message buffer
-s, --buffer-size <size> buffer size to query the kernel ring buffer
-T, --ctime show human readable timestamp (could be
inaccurate if you have used SUSPEND/RESUME)
-t, --notime don't print messages timestamp
-u, --userspace display userspace messages
-V, --version output version information and exit
-x, --decode decode facility and level to readable string

Supported log facilities:
kern - kernel messages
user - random user-level messages
mail - mail system
daemon - system daemons
auth - security/authorisation messages
syslog - messages generated internally by syslogd
lpr - line printer subsystem
news - network news subsystem

Supported log levels (priorities):
emerg - system is unusable
alert - action must be taken immediately
crit - critical conditions
err - error conditions
warn - warning conditions
notice - normal but significant condition
info - informational
debug - debug-level messages

syd@syd-Aspire-V3-571 ~ $ lspci > lspcifile
syd@syd-Aspire-V3-571 ~ $ lspci > lspcifile, lsmod > lsmod.file
Usage: lspci [<switches>]

Basic display modes:
-mm Produce machine-readable output (single -m for an obsolete format)
-t Show bus tree

Display options:
-v Be verbose (-vv for very verbose)
-k Show kernel drivers handling each device
-x Show hex-dump of the standard part of the config space
-xxx Show hex-dump of the whole config space (dangerous; root only)
-xxxx Show hex-dump of the 4096-byte extended config space (root only)
-b Bus-centric view (addresses and IRQ's as seen by the bus)
-D Always show domain numbers

Resolving of device ID's to names:
-n Show numeric ID's
-nn Show both textual and numeric ID's (names & numbers)
-q Query the PCI ID database for unknown ID's via DNS
-qq As above, but re-query locally cached entries
-Q Query the PCI ID database for all ID's via DNS

Selection of devices:
-s [[[[<domain>]:]<bus>]:][<slot>][.[<func>]] Show only devices in selected slots
-d [<vendor>]:[<device>] Show only devices with specified ID's

Other options:
-i <file> Use specified ID database instead of /usr/share/misc/pci.ids.gz
-p <file> Look up kernel modules in a given file instead of default modules.pcimap
-M Enable `bus mapping' mode (dangerous; root only)

PCI access options:
-A <method> Use the specified PCI access method (see `-A help' for a list)
-O <par>=<val> Set PCI access parameter (see `-O help' for a list)
-G Enable PCI access debugging
-H <mode> Use direct hardware access (<mode> = 1 or 2)
-F <file> Read PCI configuration dump from a given file
syd@syd-Aspire-V3-571 ~ $


Thanks once again
 
Old 10-16-2013, 10:52 AM   #4
GNU/Linux
Member
 
Registered: Sep 2012
Distribution: Slackware-14
Posts: 118

Rep: Reputation: Disabled
What zeebra suggested, you did not follow correctly I'm afraid. For example, in '/home/user/.xsession-error' user is your username which is 'syd' from your output, and '.xsession-error' is a text file. To read it's contents you can use 'less' or 'cat' ('less' will allow you to scroll while 'cat' will dump the contents on screen. To get out of 'less' press 'q')
Code:
syd@syd-Aspire-V3-571 ~ $ less .xsession-error
syd@syd-Aspire-V3-571 ~ $ cat .xsession-error
The '~' above shows that your current location is your home directory (/home/syd). '/home/syd/.xsession-error' is the absolute path of the file '.xsession-error'. Also these are separate commands, type one at a time in your Terminal:
Code:
dmesg > dmesg.file
glxinfo > glxinfo.file
In the first command 'dmesg' will show you messages generated by kernel, '>' will redirect the output (lot of text) to a file 'dmesg.file' rather than to your screen. This will be useful since you can attach that resulting file (dmesg.file) to your post. Same goes for 'lspci > lspci.file' and 'lsmod > lsmod.file'.

If you want to look for '/var/log/Xorg.Oconf' then it's inside '/var/log', you can change your current directory to that by:
Code:
syd@syd-Aspire-V3-571 ~ $ cd /var/log
syd@syd-Aspire-V3-571 /var/log $ ls
See how your current directory is changed from '~' (your home directory) to '/var/log', in the second command. Now you can see what's inside that directory by issuing an 'ls' command. Try to find a file that starts with 'Xorg.0.' (Xor.0.log most probably is the one you want). See it's contents for some errors.

Note: Some commands like 'dmesg' are not be run by a normal user so you have to add 'sudo' before the command (sudo dmesg), and just type syd's password when prompted.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Compiz won't start + trying to start compiz from terminal gets errors Stevithen Linux - Desktop 7 04-03-2010 07:45 PM
Can't start a terminal!!! FXRS Slackware 17 08-31-2008 11:15 AM
start programs in terminal jtravnick Linux - Software 6 03-31-2006 07:18 PM
Mandrake 10.1 terminal start Adriann Mandriva 5 05-11-2005 02:24 PM
Can't start a terminal blixel Linux - Newbie 1 10-06-2003 07:11 PM


All times are GMT -5. The time now is 07:35 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration