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.

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.

I already use Bash scripts to run my rsync backups automatically, more to avoid mistakes in the rsync syntax (copying the wrong directory) than anything else.

I've been wanting to improve the script both to enhance portability by setting the target and destination directories with variables and to auto-mount the destination drive if it is not mounted already.

I decided to start with a Google search, and this entry from Frustrated Tech does exactly what I need:

• Bash Script: Mount Drive Automatically to Backup Using Rsync

I'm probably using more Linux than ever. My laptop runs Fedora. I'm the admin on a server running CentOS.

I will keep doing those things.

But today I unsubscribed from most of the mailing lists that have been flowing through my Gmail account over the past few years.

The Debian, Fedora, Xubuntu and Lubuntu users list? All gone. So are the development lists for Debian, Fedora and Xubuntu, and most of the others. I'm keeping a few low-volume lists. For now anyway.

I was always more of a lurker than active participant on all of those mailing lists.

Lately, and probably before that, I didn't find much of value in most of that mail. Even though the quality of the Fedora lists is a bit higher than average, I wasn't getting a whole lot out of them. I'd scan the mail, maybe read one or two posts every few days, then delete the whole lot.

At this point, I see my operating system as a tool. To get things done.

I'm not interested in Linux evangelism. If you want to use it, that's great. I still do and will do.

If not, that's cool. Do what makes you happy.

I'm still a satisfied user of Linux. It's pretty much all I've run on my laptops since maybe 2009, and I messed around a whole lot with it before that, starting in late 2006 if I remember correctly.

There's more to life.

There's my family. I sure as hell want to do better where they're concerned.

Putting together coherent sentences? I'm still very much interested.

I've threatened to write about more than Linux for years. I'd like to write about things that aren't technology. It's been in the sidebar of this particular blog for as long as I've been writing it.

I see the "tech guy" on the morning news, and I wince. Is that me? Other than the fact that I'm very obviously not on TV, I worry that it is.

There's more to life than gadgets and apps.

That being said (there's always a that being said) ...

It sounds like I'm just on the other end of the same pool, but lately programming has dominated what little free time I have. I read a whole lot about it. And occasionally do it. Maybe I'll be able to tip the scales toward more doing in the near future.

I've been playing with Go, Perl, Python and Ruby. I need to focus.

Coding is what interests me at the moment.

What I'm not playing with are Linux distributions. I don't burn ISOs of anything, don't install just to see what something's like.

New releases of obscure distributions, or even not-so-obscure ones? I'm just not into it.

The ins, outs, politics and boiling pots of the Linux world? Not interested.

Give me my working Fedora system (or maybe Debian if the hardware is willing) and let me do my work, write my code, live my life.

If that sounds melodramatic, so be it.

I reserve the right to change my mind. But for now, I'm 50 other things first and a Linux user after that.