Monday, April 29, 2024
 Popular · Latest · Hot · Upcoming
1
rated 0 times [  1] [ 0]  / answers: 1 / hits: 9604  / 1 Year ago, sat, may 20, 2023, 5:29:40

Everything was working fine this morning. In the afternoon, I tried to boot into Ubuntu Lucid Lynx once again and I see no display. I hear the sound prompts of the login screen, so I press enter and type in my password, and I hear the sound of the Ubuntu Desktop. Which means that everything is working fine except that it does not display anything on my screen.



What can be a solution to this?



UPDATE: It Fixed itself, somehow. I still dont have a clue what the problem was so I will provide the details:



When I see the GNU grub menu, I see the following options



Ubuntu, with Linux 2.6.38.10 - generic
Ubuntu, with Linux 2.6.38.10 - generic (recovery mode)
Ubuntu, with Linux 2.6.33.10 - generic
Ubuntu, with Linux 2.6.33.10 - generic(recovery mode)


I normally use the first option to login, but I would just see a message (I remember it had something like RAM not loaded, or detected) and then it will go into blank screen.



I tried logging with the second option (recovery mode) as it looked like what I needed, and it had the oldschool dos-style blue menu, where I checked the option 'load ubuntu normally' and I was taken to a CLI.



I tried pwd, and it was showing my home directory. I navigated to one of my directories and compiled and executed a C++ program and it seemed everything was working fine. So I manually restarted and checked the first booting option, and everything is fine.



What could be a possible diagnosis of the problem I faced so that I dont face it again?


More From » display

 Answers
6

Without knowing what the exact error message was it will be difficult to diagnose. The basic sequence of events is :




  1. You failed to boot into ubuntu

  2. You tried recovery mode

  3. Recovery mode runs some extra checks on the system and repairs stuff when it can

  4. Whatver problem was fixed by the recovery mode basic tools

  5. You rebooted and it started normally



This could have been caused by anything from a bad shutdown to some intermittent hardware fault, so its hard to tell exactly what caused it to begin with.



Recovery mode does not automatically start X (the graphic display system) which is why you were dropped into a shell (This is done so you can repair a broken Xconfig from recovery mode). You can start X manually by typing startx as a command next time if you don't want to reboot. If you are running vanilla ubuntu that should start X and run your default display manager (Unity or Gnome).


[#43910] Sunday, May 21, 2023, 1 Year  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
chilgirlguid

Total Points: 123
Total Questions: 114
Total Answers: 121

Location: Macau
Member since Mon, Nov 16, 2020
4 Years ago
;