 |
 |
 |
 |
| F14 Development The proper place for all things "F14." This section will be archived once F14 reaches final release. |

3rd October 2010, 11:58 AM
|
 |
Registered User
|
|
Join Date: Oct 2005
Location: /home/Coburg
Age: 31
Posts: 13

|
|
|
blank screen on boot
Hi Folks,
I've got a strange problem with my Fedora 14: Sometimes when I boot my machine the screen stays blank but when shut down and reboot the normal boot screen is shown.
Any hints how to solve this?
|

3rd October 2010, 04:09 PM
|
|
Registered User
|
|
Join Date: Feb 2009
Posts: 2,535

|
|
|
Re: blank screen on boot
When the screen remains blank, can you still get to a virtual console (Ctrl-Alt-F2)? Did you already look into /var/log/messages and /var/log/Xorg.0.log after the screen stayed blank?
As always, some more info about the hardware you are using could be helpful in order to diagnose the problem.
|

3rd October 2010, 05:39 PM
|
 |
Registered User
|
|
Join Date: Oct 2005
Location: /home/Coburg
Age: 31
Posts: 13

|
|
|
Re: blank screen on boot
There is no chance to get a virtual console on the blank screen.
If it helps, my smolt profile is: http://www.smolts.org/client/show/pu...d-1ff52222d4be
Carification: The boot process runs normal everytime until plymouth starts. From that point one time the screen leaves blank and next time everything works fine.
Last edited by HeikoAdams; 3rd October 2010 at 06:21 PM.
|

4th October 2010, 07:51 AM
|
|
Registered User
|
|
Join Date: Feb 2009
Posts: 2,535

|
|
|
Re: blank screen on boot
Have you already tried the workarounds from the common bugs section of the F13 Release Notes (I know you are using F14 but it may be worth trying)?
http://fedoraproject.org/wiki/Common...hical_problems
|

4th October 2010, 07:56 PM
|
 |
Registered User
|
|
Join Date: Oct 2005
Location: /home/Coburg
Age: 31
Posts: 13

|
|
|
Re: blank screen on boot
Okay, after playing around with the kernel parameters it seems that
was the source of all evil
|

5th October 2010, 11:04 PM
|
 |
Banned
|
|
Join Date: Jul 2006
Location: Transgression
Age: 33
Posts: 1,183

|
|
|
Re: blank screen on boot
I had the same problem, but solved it by removing "nouveau.modeset=0" from the kernel/boot parameters. The funny thing is, before, if i did not use this arg, then i could get a GUI. Now, if i DO use it, i can't get a GUI, AND, lol, my desktop is finally displaying everything in the correct proportions (it was stretched wide when using that arg).
FWIW, another funny thing is that i keep loosing my wireless connection to my router. Not sure if it's related...
|

6th October 2010, 07:04 AM
|
|
Registered User
|
|
Join Date: Feb 2009
Posts: 2,535

|
|
|
Re: blank screen on boot
I don't think that nouveau.modeset is related to your wireless problems, since nouveau.modeset is for kernel mode setting of the graphics card.
http://fedoraproject.org/wiki/Featur...eauModesetting
|

6th October 2010, 08:27 AM
|
 |
Registered User
|
|
Join Date: Jun 2007
Location: Czech republic
Posts: 178

|
|
|
Re: blank screen on boot
I had blank screen today and it casued xorg-x11-server v1.9.0-12. With new version 1.9.0-13 it is OK.
__________________
Now 5 running Fedora instances at home ...
|

6th October 2010, 12:29 PM
|
 |
Banned
|
|
Join Date: Jul 2006
Location: Transgression
Age: 33
Posts: 1,183

|
|
|
Re: blank screen on boot
Quote:
Originally Posted by CSchwangler
|
Oh, i'm quite sure that it didn't. I was just rambling a bit, and thought that i'd mention that as well, even though it had nothing to do with this thread. I tend to do that sometimes, sorry  .
|

6th October 2010, 06:42 PM
|
 |
Fedora QA Community Monkey
|
|
Join Date: Dec 2008
Location: Vancouver, BC
Posts: 3,832

|
|
|
Re: blank screen on boot
vector: with that parameter you would have been getting the vesa driver rather than nouveau. nouveau (and intel) will no longer work at all with modesetting disabled, they simply refuse to load and X falls back to vesa.
|

6th October 2010, 09:51 PM
|
 |
Banned
|
|
Join Date: Jul 2006
Location: Transgression
Age: 33
Posts: 1,183

|
|
|
Re: blank screen on boot
Yeah, i figured that it either affected the WAY the nouveau driver works, or disables it completely.
So that would suggest that the bug is in the vesa drivers, since enabling nouveau made X work again (where it had to be DISABLED for X to work prior to this incident)?
Thanks.
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
Current GMT-time: 00:34 (Wednesday, 19-06-2013)
|
|
 |
 |
 |
 |
|
|