Linux – LearnByDoingIT

Solved HDMI not working on Raspberry Pi 3 for Vizio P-Series

There is the theory that the HDMI output of the Raspberry Pi is only initialized if a monitor/television is connected and powered up before a Raspberry Pi 3 is turned on.
Yet when I connect my Raspberry Pi 3 to a old Panasonic Plasma display the Raspberry Pi actually turns on the device and the screen activates every time.
Not so with the Vizio P series I just hung on the wall.

Aside: some of the Panasonic HDMI ports were damaged in a painting disaster…never use a 20lb weight to hold a tarp.

With the Vizio, whether the monitor is on or off and the correct HDMI port is selected or not, the Raspberry Pi 3 simply never brings up HDMI output.

Edit the /boot/config.txt file and uncomment these two lines

#hdmi_force_hotplug=1

#hdmi_drive=2

And the device works every time from every state. The first line is as it appears, the second activates HDMI and enables sound rather than DVI mode which does not.

I did like that the Vizio takes edits the HDMI connection in its table to Raspberry

Installing WiFi with Fedora 24 on HP ProBook 6570b

I have a HP ProBook 6570b as my work machine and while installing Cinnamon and Fedora 24 I found myself challenged to get WiFi working with the Broadcom WiFi adapter.

How did I solve it? Well, there were two likely methods that really are the same method, installing the WiFi drivers from the HP Support Site, however, they require a few additional dependencies, notably gcc and the kernel-devel packages. And the instructions weren’t provided. Just as I was determining what it was missing I happened across this command:

wget http://git.io/vuLC7 -v -O fedora23_broadcom_wl_install.sh && sh ./fedora23_broadcom_wl_install.sh;

The details of which are located here on a site which some browsers may not like as the site isn’t configured correctly. Still, the script is available and easily understood from the documentation.

The best part is I now have WiFi and it wasn’t so bad after all.

Upgrading to Fedora 24

Fedora 24 is official. I decided to jump in on my production server as I had just risked everything taking care of the Ants. Seriously, my Cisco, Server, and Printer/Scanner were infested in their temporary location. They have never been so clean.

I was going to go straight to FedUp like I had in the past; however, according to the documentation page:

FedUp (FEDora UPgrader) was the official tool for upgrading between Fedora releases, until the introduction of the DNF system upgrade plugin. FedUp is now obsolete and should not be used in any circumstances.

And I imagine I had been using it one or two updates too many, being slow to convert to DNF. Installing the DNF upgrade plugin, which appears to be default is the recommended and supported way to upgrade from Fedora 23 to Fedora 24.

I have also seen that you should be able to update to Fedora 24 Workstation using the Software app, although I haven’t tested it and my system is “headless”.

Assuming you have backed up your system Smile , perhaps using deja-dup. Update your machine and install the DNF plugin

$ sudo dnf upgrade --refresh

$ sudo dnf install dnf-plugin-system-upgrade

Part 1 – download upgrades to prepare for the upgrade

$ sudo dnf system-upgrade download --releasever=24

This command will begin downloading all of the upgrades for your machine locally to prepare for the upgrade. You may wish

If you have issues when upgrading because of packages without updates, broken dependencies, or retired packages, add the --allowerasing flag when typing the above command. This will allow DNF to remove packages that may be blocking your system upgrade.

Part 2 – Reboot and upgrade

$ sudo dnf system-upgrade reboot

Your system will restart after this. In past releases, the fedup tool would create a new option on the kernel selection / boot screen. With the new dnf-plugin-system-upgrade package, your system reboots into the current kernel installed for Fedora 23; this is normal. Shortly after the kernel selection screen, your system begins the upgrade process.

Now might be a good time for a coffee break! Once it finishes, your system will restart and you’ll be able to log in to your newly upgraded Fedora 24 Workstation.

I flew through without any issues, but if there are issues, check out the DNF system upgrade wiki page as well as Fedora Magazine’s Upgrading Fedora 23 to Fedora 24 article. I followed their directions for the most part and have put the salient ones in here so I can remember as I upgrade all my workstations.

First Step After Using Fedup To Install Fedora 21

The primary problem this post addresses is removing old versions of the Kernel as Grub is apparently not booting the version it is visually confirming that it is booting.

The details are that on my first three Fedora 21 installations I used FedUp to upgraded existing Fedora installations with some unusual but simple to fix problems as a result. The original installations were Fedora 20 and Fedora 19 so the issue seems to be within the Fedora 21 ecosystem. While the problems were different on all machines, depending on the services the servers provided, and my primary Linux workstation, the fix was to remove old versions of the Kernel.

I used the following steps

1. Check Installed Kernels

rpm –q kernel

2. Delete / Remove Old Kernels

yum install yum-utils

package-cleanup –-oldkernels –-count=1

Why Owncloud was Build and Made OpenSource

"Open source is the only option for file storage that is really safe and secure.,” says ownCloud Founder Frank Karlitschek.

Frank Karlitschek is founder of ownCloud and maintainer of the project’s general architecture.

There I was, 4 years ago (this past January) at CampKDE in San Diego, giving a talk on data privacy, warning the audience about the risks to their privacy from cloud vendors – in particular, Dropbox. So, build it yourself they said. Sure, I’ve built things in the past, so sure, I’ll do it. And there is where I started my odyssey, first, to protect myself, my friends and my colleagues from the snooping of governments, and other bad guys, and later – as I saw the worldwide interest grow – to build a real and successful project.

I had to decide a few things before I got started of course, including what it is I wanted ownCloud to do, what development platform to use, how I wanted to structure ownCloud, and of course, to name it ownCloud.

My friends and I needed a way we could sync our pictures, documents and even videos to our various devices (instead of using a thumb drive), and even to share those files with friends and family. Dropbox was by then becoming very popular, but I just didn’t want to send my data through a third-party service to be stored who-knows-where. I wanted to create a platform that friends could use the storage they already had – instead of the cloud — but not just for syncing and sharing, but a platform flexible enough to build apps beyond that.

Of course ownCloud would be open source.