LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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 09-14-2010, 01:04 PM   #1
Vegan
Member
 
Registered: Aug 2010
Location: Idaho
Distribution: Arch, Ubuntu, Fedora
Posts: 114
Blog Entries: 2

Rep: Reputation: 10
Fedora bubble loads, then blank screen with blinking cursor. no gui.


My computer was working fine yesterday.
This morning i booted up and grub loaded fine, the fedora bubble did its loading thing.
after the bubble i get a blank screen with a flashing cursor in the top left.
I can ctrl+alt to a terminal screen, but i dont know what to do from there...
Please help. i dont want to have to reload Fedora again.

I am using Fedora 12 on a dual boot with win7
dual monitors
ati 4650 video card.
if you need any other info, just ask
 
Old 09-14-2010, 01:18 PM   #2
ronlau9
Senior Member
 
Registered: Dec 2007
Location: In front of my LINUX OR MAC BOX
Distribution: Mandriva 2009 X86_64 suse 11.3 X86_64 Centos X86_64 Debian X86_64 Linux MInt 86_64 OS X
Posts: 2,369

Rep: Reputation: Disabled
If Fedora started to boot what happens if you pressed the escape key ?
Give If it the chance to boot a other kernel than the standard kernel .
If it gives you that chance what happens if you choose a older kernel
After update a kernel Fedora left older kernels just in case you need them
 
Old 09-14-2010, 01:23 PM   #3
Vegan
Member
 
Registered: Aug 2010
Location: Idaho
Distribution: Arch, Ubuntu, Fedora
Posts: 114
Blog Entries: 2

Original Poster
Rep: Reputation: 10
Quote:
Originally Posted by ronlau9 View Post
If Fedora started to boot what happens if you pressed the escape key ?
Give If it the chance to boot a other kernel than the standard kernel .
If it gives you that chance what happens if you choose a older kernel
After update a kernel Fedora left older kernels just in case you need them
I've never updated it (crappy internet)
so i don't think i will have the option for an older kernal
 
Old 09-14-2010, 01:48 PM   #4
ronlau9
Senior Member
 
Registered: Dec 2007
Location: In front of my LINUX OR MAC BOX
Distribution: Mandriva 2009 X86_64 suse 11.3 X86_64 Centos X86_64 Debian X86_64 Linux MInt 86_64 OS X
Posts: 2,369

Rep: Reputation: Disabled
But still it gives some options one of the options is to get the a command line
Ask fore the command line
Type on the command line verbose than continue the boot process.
Hopefully it comes with a error messages that give some clue of you're oproblem
 
Old 09-14-2010, 02:02 PM   #5
Vegan
Member
 
Registered: Aug 2010
Location: Idaho
Distribution: Arch, Ubuntu, Fedora
Posts: 114
Blog Entries: 2

Original Poster
Rep: Reputation: 10
Quote:
Originally Posted by ronlau9 View Post
But still it gives some options one of the options is to get the a command line
Ask fore the command line
Type on the command line verbose than continue the boot process.
Hopefully it comes with a error messages that give some clue of you're oproblem
Awesome i will try that when i get home (i'm at work at the moment) and then post the results.
Thank you
 
Old 09-14-2010, 08:46 PM   #6
Vegan
Member
 
Registered: Aug 2010
Location: Idaho
Distribution: Arch, Ubuntu, Fedora
Posts: 114
Blog Entries: 2

Original Poster
Rep: Reputation: 10
on the line
"Starting libvirtd daemon"
the screen starts flashing on and off.
then the screen turns off or it stops booting there and the screen stays on
 
Old 09-14-2010, 09:04 PM   #7
jschiwal
LQ Guru
 
Registered: Aug 2001
Location: Fargo, ND
Distribution: SuSE AMD64
Posts: 15,733

Rep: Reputation: 671Reputation: 671Reputation: 671Reputation: 671Reputation: 671Reputation: 671
One easy thing to check for is whether you have a partition that is full. A full partition could cause failures in services starting the need to write to /var/run, such as the pid file.
 
Old 09-14-2010, 09:06 PM   #8
Vegan
Member
 
Registered: Aug 2010
Location: Idaho
Distribution: Arch, Ubuntu, Fedora
Posts: 114
Blog Entries: 2

Original Poster
Rep: Reputation: 10
Quote:
Originally Posted by jschiwal View Post
One easy thing to check for is whether you have a partition that is full. A full partition could cause failures in services starting the need to write to /var/run, such as the pid file.
i wish it was that easy lol.
i have 94 gigs free though...
 
Old 09-15-2010, 03:38 AM   #9
jschiwal
LQ Guru
 
Registered: Aug 2001
Location: Fargo, ND
Distribution: SuSE AMD64
Posts: 15,733

Rep: Reputation: 671Reputation: 671Reputation: 671Reputation: 671Reputation: 671Reputation: 671
Since you can get to a virtual terminal, check the /var/log/Xorg.0.log file. The lines starting with (EE) are errors.

Still looking for simple solutions, I've dealt with personally, a syntax error in xorg.conf (or xorg.conf.d/*) can cause X to quickly abort. Other problems could be indicated. Look at the date and time the file was created. Is the file from the current boot time. There may be other problems indicated, such as a missing kernel module or xorg driver.

The dmesg command will list the boot messages from the kernel ring buffer. There may be more details there. There is also /var/log/messages. It is a running log of kernel messages.
 
1 members found this post helpful.
Old 09-15-2010, 07:48 AM   #10
ronlau9
Senior Member
 
Registered: Dec 2007
Location: In front of my LINUX OR MAC BOX
Distribution: Mandriva 2009 X86_64 suse 11.3 X86_64 Centos X86_64 Debian X86_64 Linux MInt 86_64 OS X
Posts: 2,369

Rep: Reputation: Disabled
Quote:
Originally Posted by Vegan View Post
on the line
"Starting libvirtd daemon"
the screen starts flashing on and off.
then the screen turns off or it stops booting there and the screen stays on
No this is not what you should look for .
If you are there press c key it will gives you a command line .
The tab key give you the possible commands
One of the possible commands is verbose
Type that command on the command line
Fedora will continue the boot process in the verbose mode (Text mode}
First we can find where she stops booting .
Second we hope for use full error messages
 
1 members found this post helpful.
Old 09-15-2010, 12:53 PM   #11
Vegan
Member
 
Registered: Aug 2010
Location: Idaho
Distribution: Arch, Ubuntu, Fedora
Posts: 114
Blog Entries: 2

Original Poster
Rep: Reputation: 10
Quote:
Originally Posted by jschiwal View Post
Since you can get to a virtual terminal, check the /var/log/Xorg.0.log file. The lines starting with (EE) are errors.

Still looking for simple solutions, I've dealt with personally, a syntax error in xorg.conf (or xorg.conf.d/*) can cause X to quickly abort. Other problems could be indicated. Look at the date and time the file was created. Is the file from the current boot time. There may be other problems indicated, such as a missing kernel module or xorg driver.

The dmesg command will list the boot messages from the kernel ring buffer. There may be more details there. There is also /var/log/messages. It is a running log of kernel messages.
It ended up not booting at all last night. i think i messed up grub through my probing around.
so i went in and reinstalled FC12

The strange thing is when i did go in to check the xorg file. i didn't have one. so i made one and it didn't make any difference.

i will stay subscribed to this thread though, since this isn't the first time this has happened to my system in the last couple weeks.
so i might be calling on you guys to help again...

Thank you
 
Old 09-15-2010, 01:17 PM   #12
hughetorrance
Member
 
Registered: Aug 2009
Location: London North West
Distribution: x86_64 Slack 13.37 current : +others
Posts: 459

Rep: Reputation: 59
I think you gave up on it far too soon,I have problems going for months and sometimes they are so old they just fade away and were never resolved,in this case though there was much still to try...i.e. I would have tried to boot up with the "vesa" driver LOL good luck

ps thats why we have multiple operating systems,its so as we don,t have any pressure when something goes wrong and its very handy to be able to use one system on another,like swap files and folders or whatever.
 
Old 09-15-2010, 01:22 PM   #13
Vegan
Member
 
Registered: Aug 2010
Location: Idaho
Distribution: Arch, Ubuntu, Fedora
Posts: 114
Blog Entries: 2

Original Poster
Rep: Reputation: 10
Quote:
Originally Posted by hughetorrance View Post
I think you gave up on it far too soon,I have problems going for months and sometimes they are so old they just fade away and were never resolved,in this case though there was much still to try...i.e. I would have tried to boot up with the "vesa" driver LOL good luck

ps thats why we have multiple operating systems,its so as we don,t have any pressure when something goes wrong and its very handy to be able to use one system on another,like swap files and folders or whatever.
I did give up way too early..
I started to regret it as soon as i started to reinstall it..
But i am going to put on another linux distro and have a triple boot so if something like this does happen again i will have another system to boot to. just dont know which one yet..
I just need to stop thinking of these glitches as problems and treat them as learning experiences.

Thank you for your advice.

And ps. i did try booting with vesa driver
 
Old 09-16-2010, 11:43 AM   #14
hughetorrance
Member
 
Registered: Aug 2009
Location: London North West
Distribution: x86_64 Slack 13.37 current : +others
Posts: 459

Rep: Reputation: 59
Don,t worry you are on a well trodden road and as you might have guessed I am still on it... there is always a distant horizon to reach for,you are right its about having fun and just being patient and persistent and sometimes knowing when to move on and find another way but having said that the day arrives when you can take it a bit easier,one thing is for sure and that is... its all worth it LOL

ps I have tons of problems but fortunately nothing that cant wait until I am ready... this is about having fun and learnig at the same time.
 
Old 09-20-2010, 12:19 PM   #15
jschiwal
LQ Guru
 
Registered: Aug 2001
Location: Fargo, ND
Distribution: SuSE AMD64
Posts: 15,733

Rep: Reputation: 671Reputation: 671Reputation: 671Reputation: 671Reputation: 671Reputation: 671
On newer distros, the old xorg.conf file is contained in separate files in /etc/X11/xorg.conf.d/.
The files represent the "Sections" of the old xorg.conf file.
e.g.:
Code:
/etc/X11/xorg.conf.d/10-evdev.conf      /etc/X11/xorg.conf.d/20-wacom.conf    /etc/X11/xorg.conf.d/50-screen.conf
/etc/X11/xorg.conf.d/11-mouse.conf      /etc/X11/xorg.conf.d/50-device.conf   /etc/X11/xorg.conf.d/50-vmmouse.conf
/etc/X11/xorg.conf.d/20-synaptics.conf  /etc/X11/xorg.conf.d/50-monitor.conf  /etc/X11/xorg.conf.d/90-keytable.conf
So look at editing the 50-device.conf file to change the device driver. If you have a comprehensive /etc/X11/xorg.conf file, it will be used instead AFAIK.

Also the newer xorg server is supposed to configure itself on the fly when it starts but uses the config file(s) if they exist.

I have a laptop with a nvidia card, and a netbook with an ati card. In both cases, I've needed to add "nomodeset" to the kernel boot options.

You didn't respond about errors found in the /var/log/xorg.0.log file.

Last edited by jschiwal; 09-20-2010 at 12:21 PM.
 
  


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
[SOLVED] Blank screen with a blinking cursor after installing Slackware 13.1 TheIndependentAquarius Slackware - Installation 18 07-20-2010 06:58 AM
[SOLVED] Fedora live cd - Screen goes blank right before login screen loads deadalus.globalnode Fedora 5 04-21-2010 04:36 PM
blank screen and blinking cursor,, ecesuren Linux - Software 1 02-28-2010 07:36 AM
Blank screen with blinking cursor divijvaidya13 Linux - Software 1 02-22-2010 06:39 PM
Blank screen with blinking cursor on boot (yoper) Fisslefink Linux - Newbie 3 02-15-2005 06:16 PM


All times are GMT -5. The time now is 01:41 PM.

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