Before I start with the brief tutorial I want to just list the configuration, results may vary based on the specs of the machine.
- 14″ inch 1920 x 1080 display
- i5-4300U 1.9 Base clock 2 core 4 thread
- 8gb DDR3 12800 ADATA RAM
- 180GB 530 2.5′ Intel SSD
I decided to use the latest version of Fedora based on the good experience that I have had with my desktop. The latest version of Fedora runs a very clean, stable and beautiful version of GNOME.
First, I downloaded the .iso and burned it to a USB drive. Since, the laptop might either ship with Windows 7 or 8.1 the BIOS might be set to either UEFI or Legacy Boot. In order to check this power off the machine, at BOOT when at the HP logo screen select ESC.
Once you have selected ESC. You will see a list of options, you will select the option f10.
This will take you to the BIOS setup screen, go to the Advanced Tab at the top right corner.
Make sure that USB boot is selected.
Scroll down further to the Boot Mode and select Legacy Boot. Once you have set these settings make sure to save and exit. You should now be able to boot from your USB bootable drive.
Most of the devices worked out of the box, the only devices that did not were:
- Sound
- Fingerprint Reader
- f8 Mic Disable hot-key (There were so few I had to list it.)
Before I got into resolving the issues with these devices I wanted to get all the updates:
sudo dnf update
After all the updates finished I went to install Google Chrome, Google has really made this easier than in past years.
It should open in Software Updater, then select install and enter root password.
There are a few guides to “Things to Install after Installing Fedora 23”
It will vary based on your usage what will want to install, however here is a link:
http://www.binarytides.com/better-fedora-23/
The issue with the sound driver was related to an incomaptibilty issue with PulseAudio. I was easily able to resolve this by simeple Terminal Command:
sudo dnf|yum remove alsa-plugins-pulseaudio
Once I rebooted the issue was immediately resolved. I have tried so far without success in the past few hours since I have had the machine to probe the FIngeprint driver to see what drivers might exist for it. I will update this blog if I do find a fix for this. Please let me know if you think there are any other important additions.
Rush Simonson III 