i can`t log on to my Trusty 14.04 LTS
i can`t log on to my Trusty 14.04 LTS because when i run a boot sequence i get a black background with white window that say
"The system is running in low graphics mode, your screen, graphics card and input device could not be detected correctly, you will need configure these your self".
And when i press ok button Ubuntu gives me an option that i run system in low res mode and to configure things by my self, but non of this dont work when it`s pressed, Please give me some Help here guys, this all happend after some regular video update.
I am now on my pendrive and looking for some quick and fine Help from you guy`s and developers, i am new to Ubuntu and all Help will be very Appreciated and Welcome.
p.s.- because of bugs i have reinstalled my system twice already, it`s a real bad trip because this is LTS edition and i think it should be more stable, but I fell in love with Ubuntu on first sight and nothing is hard for me to do to have him.Now it seems to me like i dont have too much luck with Ubuntu because when i set up my system like i want him to be 100%, something come up and spoil all my work on my machine, :p -_-
.◦○●ᵖsy444ºᵖs●
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Ubuntu Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- psy444ops
- Solved:
- Last query:
- Last reply:
Revision history for this message
|
#1 |
Does the system have a make and model?
Have you ran full updates?
What video chip does the system have?
Revision history for this message
|
#2 |
Trusty is LTS but is currently prerelease so is officially unstable.
Revision history for this message
|
#3 |
yes i have run full updates, one was partial, must say that...
Motherboard is Gygabyte nVidia nForce 560 DDR2 800Mhz GA-M56S-S3, AMD Dual Core Athlon 64 X2.
Graphics card - GeForce 8500 GT 512mb GDDR2 Turboforce edition. NX85T series Graphics Accelerator.
Sound-Realtec HD Audio 7.1
Video - Leadtek WinFast TV 2000 XP Expert PCI 2.3 32bit.
all was fine untill last night when i got update for some video stuff, i dont know what they are for, Sorry...
.◦○●ᵖsy444ºᵖs●
Revision history for this message
|
#5 |
If you run :
sudo lshw -C display
Do you only see an Nvidia GPU or do you see others?
Revision history for this message
|
#6 |
* - display: UNCLAIMED
description:VGA compatible controller
product:G86 GeForce 8500 GT
vendor:nVidia Corporation
physical id:0
bus info:PCI@
version:a1
width:64bits
clock:33MHz
capabilities:pm msi pci express VGA controller bus_master.cap list
Configuration:
resources:memory:f 4000000-f4ffffff
and some other line with numbers under all this
Revision history for this message
|
#7 |
Ok and the output of:
dpkg -l | grep nvidia
Thanks
Revision history for this message
|
#8 |
Here is output of dpkg -l | grep nvidia
ii nvidia -cg -dev :amd64 3.1.0013-1
HEADERS
ii nvidia -cg -dev :amd64 3.1.0013-1
Revision history for this message
|
#9 |
nvidia is in red font...
after first line it`s just writen HEADERS and a first line again under HEADERS
Revision history for this message
|
#10 |
Thank you...
ॐ ∷⌘ •ᘤ ᔣ ᖻ ᔰ ᔰ ᔰ Ꭴ ᘤ ᔣ•☼☼☼☼
Revision history for this message
|
#11 |
i have to Apologize because of my inability to log in earlier, it`s really urgent for me to enable my system as soon as possible, but i was prevented due to force majeure...
Revision history for this message
|
#12 |
and i must give this info too, i have install this, might have something to do with it...
sudo apt-get update
sudo apt-get install numlockx
sudo sh -c 'echo "greeter-
it`s for numpad to start on logon.
Revision history for this message
|
#13 |
output of dpkg -l | grep nvidia
ii nvidia -cg -dev :amd64 3.1.0013-1
HEADERS
ii nvidia -cg -dev :amd64 3.1.0013-1
Revision history for this message
|
#15 |
Please Guys Help me, i can`t log on to my system due to the above mentioned problems, all help will be very Appreciated and Welcome.
Revision history for this message
|
#16 |
I assume that the output of the "dpkg -l | grep nvidia" command resulted in "...nvidia-
If the only output of "output of dpkg -l | grep nvidia" is "nvidia-cg-dev", then you just have a nvidia toolkit, but not the real nvidia display drivers installed.
Try the following:
Reboot your sytem in "root shell prompt" mode (see http://
Then issue the command
ubuntu-drivers list
You should see that there is a dedicated nvidia driver for your video card that can be installed.
Please provide the exact output of that command.
Revision history for this message
|
#18 |
Output is:
nvidia-304
nvidia-331-updates
nvidia-331
nvidia-304-updates
nvidia-173
Revision history for this message
|
#19 |
Then try
ubuntu-drivers autoinstall
and reboot.
Revision history for this message
|
#20 |
when i add the command: ubuntu-drivers autoinstall
output is:
W:Not using locking for read only lock file /var/lib/dpkg/lock
E:Unable to write to /var/cache/apt/
E:The package lists or status file could not be parsed or opened
Revision history for this message
|
#21 |
Run:
sudo mount -o rw,remount /
Then try again
Revision history for this message
|
#22 |
when i add the command: sudo mount -o rw,remount /
and then: ubuntu-drivers autoinstall
output is the same as the previous time:
W:Not using locking for read only lock file /var/lib/dpkg/lock
E:Unable to write to /var/cache/apt/
E:The package lists or status file could not be parsed or opened
Revision history for this message
|
#23 |
It seems that your root file system is still mounted readonly.
Is there any output of the "sudo mount ..." command?
Revision history for this message
|
#24 |
Dear sir, output is still same as previous time:
W:Not using locking for read only lock file /var/lib/dpkg/lock
E:Unable to write to /var/cache/apt/
E:The package lists or status file could not be parsed or opened
when i try to log on in regular way, it still displays the same white window giving me options to run system in low res mode
but when i press ok, nothing happens, neither option is not working.
Revision history for this message
|
#25 |
That is not the output that I asked for, but never mind.
Try rebooting into recovery mode - command prompt. Log in with your name and password and issue the "sudo ubuntu-drivers autoinstall" command.
Please inform us about any warnings or error messages from that command.
Revision history for this message
|
#26 |
unfortunately output is same as previous one:
W:Not using locking for read only lock file /var/lib/dpkg/lock
E:Unable to write to /var/cache/apt/
E:The package lists or status file could not be parsed or opened
Revision history for this message
|
#27 |
in recovery mode, when i press an up arrow and issue command:gk sudo gedit/etc/
output is:(gksudo:
Revision history for this message
|
#28 |
Please can somebody provide some Help Please.
Revision history for this message
|
#29 |
Does anybody have a clue how to resolve this problem?.
Revision history for this message
|
#30 |
ok Guy`s...this is a third time that i have installed again Trusty 14.04, it seems it`s not Trusty at all, must say, i`m literally afraid
to install updates because i never know will my system will go up on next boot, i was thinking that unstable means minor fixes, not reinstalling again, again and again, because of huge experiments with "LTS", and i thought that here are some hard core tuff coders that are willing to help a new guy to overide some troubles, but again i thought wrong...but i still want to see how you guy`s will do a workaround concerning this bug, i still hope there is an someone who is competent to solve this problem...
Revision history for this message
|
#31 |
ok Guy`s...this is a third time that i have installed again Trusty 14.04, it seems it`s not Trusty at all, must say, i`m literally afraid
to install updates because i never know will my system will go up on next boot, i was thinking that unstable means minor fixes, not reinstalling again, again and again, because of huge experiments with "LTS", and i thought that here are some hard core tuff coders that are willing to help a new guy to overide some troubles, but again i thought wrong...but i still want to see how you guy`s will do a workaround concerning this bug, i still hope there is an someone who is competent to solve this problem...
Revision history for this message
|
#32 |
must say Big Thank you goes to Mr.Malfred Hampl and Mr.actionparnsnip for honest Help and devotion to a coz.
Revision history for this message
|
#33 |
If you are booting in recovery mode - root command prompt and then execute the command
mount -o rw,remount /
exactly as written here, and if you then still are having a readonly file system, then you are doing something so much different from what we expect that I do not know how to continue.
Can you please try this again, and then issue the command
ubuntu-drivers autoinstall
and tell us what happens.
Revision history for this message
|
#34 |
Dear sir, i don`t have nerves to wait several day`s for help, i have work to run, i have installed a whole new Trusty 14.04 and all software that i need including ones that run over Wine app, i have installed over 300 programs and whole new system because my customers dont have patient and they dont have to know about my problems, they need output only and quality one Dear sir.
Greetings for you and Mr.actionparnsnip for true dedication, Help, courtesy and real commitment to a thing called Ubuntu.
Revision history for this message
|
#35 |
And to answer to your question about issuing provided commands, before i have installed a whole new system i already did exactly as you told me now and before, and output is:
W:Not using locking for read only lock file /var/lib/dpkg/lock
E:Unable to write to /var/cache/apt/
E:The package lists or status file could not be parsed or opened