Title photo
frugal technology, simple living and guerrilla large-appliance repair
Mon, 28 Sep 2015

Working on my networking issue after suspend/resume in Fedora 22

Briefly, for no good reason, my networking on the HP Pavilion g6 2210-us is broken after suspend/resume in Fedora 22.

It's not broken on live Fedora 22 and Xubuntu 15.04 images. It wasn't broken a week ago in the Fedora 22 system I've been upgrading since I started it with F18 in 2012.

I should probably just reinstall. And I probably will. Xubuntu on a new drive. Soon.

But until then, I need networking to return after a suspend/resume.

I've tried lots of things. Nothing has really worked. Closest is Wake-On-Lan issue with Realtek r8169: immediate resume after suspend from the Ubuntu Forums.

That script doesn't work.

But it did give me the idea to just run the modprobe lines:

$ sudo modprobe -r r8169
$ sudo modprobe r8169

That works. The network comes back (both wired and wireless, even though this only addresses the wired Ethernet network).

The script in /etc/pm/sleep.d seems to do nothing.

But running this script, which I titled jump_start, does work:

#! /bin/bash

modprobe -r r8169
modprobe r8169

exit 0

As a workaround, I created a launcher in Xfce, hooked it up to this two-line Bash script, and made an exception for it with visudo so I could run it from the launcher.

Now I resume the laptop, click my "jumpstart the network" icon in the panel, and I'm ready to go.

It's less than automatic, but for now it works.

I have no idea why this happened, but since every new live system I try suspends and resumes with no problems at all, this hack will keep me going until I build my new Linux system on a new hard drive. (This is a "production" laptop, and I want to avoid the anxiety of having to rebuild and configure it under pressure, so I'm opting for a new hard drive that will be a single-boot Linux system.)

Update: I may be putting my scripts in the wrong place for automatic execution in a Systemd environment. Fedora users suggest /usr/lib/systemd/system-sleep/

This is the script I put in /usr/lib/systemd/system-sleep/:

#!/bin/sh

case "$1" in
    hibernate|suspend)
   systemctl stop NetworkManager.service
        modprobe -r r8169
        ;;
    thaw|resume) 
        modprobe r8169
  systemctl start NetworkManager.service

        ;;
esac

I'm not convinced that any of this (other than running my jump_start script with the two modprobe lines) is working.

Further update: A day later, I've been using WiFi only, and the network has been available after suspend/resume with no trouble. Not sure why.

Further further update: It's spotty. I'm taking the script out of /usr/lib/systemd/system-sleep/ -- I don't think it's doing a damn thing. I still need my local script sometimes to jump-start the network.

Oct. 10 update: Things seem a lot better. I'm not 100 percent sure the problem has been solved. Maybe 80 percent.

Sat, 26 Sep 2015

Rebuilding GRUB 2 entries in Fedora 22 for UEFI systems after modifying /etc/default/grub

I'm surprised that the Fedora documentation for working with GRUB 2 doesn't address rebuilding GRUB 2 entries for EFI booting.

They do address it, but they get it wrong.

The grub2-mkconfig instructions for both BIOS and UEFI systems are the same. The problem is that this instruction will only build the BIOS entries. The UEFI entries won't be rebuilt.

Once you have your changes set in /etc/default/grub, here is how to rebuild the GRUB 2 entries for BIOS and UEFI systems?

BIOS systems

# grub2-mkconfig -o /boot/grub2/grub.cfg

UEFI systems

# grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg

It is perfectly OK to do both of these commands (using root, hence the # prompt, or with sudo), but you do need the one that matches your booting method (BIOS for older systems, optionally UEFI for newer systems).

The only reason I figured this out is because I poked around quite a bit when having dual-booting issues. Someone should fix the Fedora GRUB page. I'm a Fedora member and could probably make the fix myself, but I'm not 100 percent sure what I'm doing here is the absolute best method because my GRUB bootlines after doing this look different then they do when the system (either yum or dnf) does a kernel update.

Ubuntu wired network unavailable after suspend/hibernate/resume

Ubuntu wired network unavailable after suspend/hibernate/resume http://voluntocracy.blogspot.com/2012/02/ubuntu-wired-network-unavailable-after.html

Fri, 25 Sep 2015

Getting a network to work after suspend/resume in Linux

Getting a network to work after suspend/resume in Linux http://www.webupd8.org/2013/01/fix-wireless-or-wired-network-not.html

Page views are so 2000s

Media especially needs to get over page views because that's not the way the modern web works

Fix for Unetbootin with root in Fedora 22

Fix Unetbootin blank-window error with root in Fedora 22 https://bugzilla.redhat.com/show_bug.cgi?id=1229874#c4

Irfanview under Wine in Linux: Fix the

In Irfanview under Wine in Linux, fix the "JPEG save error" https://irfanview-forum.de/showthread.php?t=8723&p=38109&viewfull=1#post38109

Wed, 23 Sep 2015

Bob Strauss on 'A Brave Heart: The Lizzie Velasquez Story'

Great story by @bscritic on inspirational 'A Brave Heart: The Lizzie Velasquez Story' http://www.dailynews.com/arts-and-entertainment/20150922/dealing-with-disorder-lizzie-velasquez-displays-a-brave-heart

Tue, 22 Sep 2015

How to fix LibreOffice spell check in Fedora 22

I needed to use LibreOffice today. It's not something that happens very often. I almost always write or edit in a text editor, web form or Google Docs. But today I opened up LibreOffice.

I wanted to use "automatic" spell-checking in LibreOffice, which you invoke with shift-F7. But it didn't work.

I looked at my default "language," which was U.S. English. There was no little blue check next to it that indicated it had a dictionary. I checked my packages. I wasn't missing English.

It turns out there's a hack that gets spell-checking working and gives me the red squiggly lines under my misspelled words (that's the way I like to do it.

I found the answer in LibreOffice's "Ask LibreOffice" forum (which uses the same software as Ask Fedora).

Here is the fix from that helpful post:

Under Tools -> Options -> Language Settings: Writing Aids, the list of available language modules showed almost everything set. I unchecked and then re-checked "Hunspell SpellChecker" and "Libhyphen Hyphenator" and hit OK. (I strongly suspect that the hunspell was the significant checkbox). Then, when I go back to Language and look at the default language settings, the "English (USA)" entry has the ABC✔ by it, and now spell checking is working.

Best guess is that some results of invoking something from hunspell is saved by libreoffice and that with updating versions, the cached output is no longer valid. Re-invoking (when re-checking the checkbox) refreshes the cached data and now everything is all better.

It sure worked for me.

Wed, 16 Sep 2015

Fedora 22 updates Ruby to 2.2.3

Fedora 22 updates to Ruby 2.2.3. So easy to have the latest in a surprisingly stable Linux system.