Black screen when trying to install Fedora 20

asked 2014-04-26 15:56:24 -0600

Asvarduil gravatar image

updated 2014-04-26 16:50:32 -0600

I'm trying to get Fedora 20 to work on an Acer Aspire One A150 netbook. I have used LiveUSB Creator to build a 16GB thumbdrive as a live source, but in both cases, after booting from the thumbdrive and selecting the option to Start Fedora, I get a black screen.

I cannot install via optical medium to this system, as it has no CD/DVD drive and I do not own a USB CD/DVD drive.

These are the full steps I have attempted:

Created Fedora 20 KDE x86 Live USB, 0 MB persistent overlay

Inserted Live USB into Acer Aspire One Netbook

Attempted to boot F20 USB - Failed, black screen

Attempted to boot F20 USB with minimal graphics - Failed, black screen

Ran Memory Test - Passed, 100%

Attempted to boot F20 USB and Test Medium - Failed, black screen

Cleared USB

Created Fedora 20 Desktop x86 Live USB, 1058 MB persistent overlay

Attempted to boot F20 USB - Failed, black screen

Attempted to boot F20 USB with minimal graphics - Failed, black screen

Cleared USB

Created Fedora 19 Desktop x86 Live USB, 1058 MB persistent overlay

Attempted to boot F19 USB - Failed, black screen

Attempted to boot F19 USB with minimal graphics - Failed, black screen.

As you can see, I considered that perhaps F20 includes features that my A150 can't handle, so as a test I attempted an A19 live build as well, but it behaved exactly the same way - after attempting to start Fedora, I received a black screen both with a normal boot and with 'minimal graphics.'

I have of course checked both the netbooks memory, and verified that the USB stick is not corrupted (I bought it last night from a nearby Target). I am hitting the image on the thumbdrive, as I am prompted to actually start Fedora. What am I missing in order to get Fedora to run on my netbook?

edit retag flag offensive close merge delete

Comments

1

The processor Atom N270 is a 32 bits one, did you use a 32 bits iso?

Also, maybe you can try booting with the parameter nomodeset.

remjg gravatar imageremjg ( 2014-04-26 16:19:07 -0600 )edit
1

Yes, I used an x86 live build in all scenarios listed above. Also, the 'minimal graphics mode' includes the nomodeset switch. Is there a better custom command line that I could use instead? EDIT - Oh crud you may be right. I noticed the file has x86_64, which likely denotes a 64-bit build. No wonder it won't work! I'll try 32-bit builds instead.

Asvarduil gravatar imageAsvarduil ( 2014-04-26 16:48:50 -0600 )edit

In the case there is a reason you were open to 20 over 21 or 22 even, id go with a fresh install with those. (if you are still having issues)

I have a netbook as well, [currently using 22], before the upgrade, 21 worked flawlessly on a live boot. BUT I did have to restart my computer again because I did get a black screen on an initial boot, and that seemed to fix it.

BatYaz gravatar imageBatYaz ( 2015-07-20 13:57:30 -0600 )edit