Category Archives: Administrative

Fedora Problem

I’m running Fedora 31 (I know, I should update to at least 32), with two monitors. One monitor is always in Workspace 3 (its primary function is to display a virtual Windows installation). Sometimes, when the machine wakes up, only the main monitor will wake up. I can activate the other one by going into settings, changing it from “Join” to “Mirror,” then reverting. But the problem with this is that, in addition to being a PITA, it for some reason jumbles up my work spaces, moving things around that I then have to rearrange the way I want them. Does anyone have any suggestions?

Continued Light Blogging

I’m sort of on vacation this week. I gave a talk in Omaha on Friday as part of a space panel with General Kwast and Joel Sercel, on the economics of space, to a Free Market Forum sponsored by Hillsdale College. It seemed to go well, and seemed to be an eye opener for many in the audience, so it was great to preach to someone other than the choir.

We’re in Michigan now, visiting family and checking out the fall colors for the first time in a long time. Unfortunately, I’m also boning up for my deposition next week in DC by Mann’s lawyer. So I’ll keep an eye on things, and post if something noteworthy happens, but consider this an open thread for now.

Virtual Box Woes

I just did a Fedora reboot after a kernel upgrade, and when I try to start Windows in Virtual Box, I get this error:

************************************************************

Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing ‘/sbin/vboxconfig’ as root.

If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system’s documentation for more information.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) – The support driver is not installed. On linux, open returned ENOENT.

**************************************************************

When I run /sbin/vboxconfig, I get:

******************************************************************

vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.

There were problems setting up VirtualBox. To re-start the set-up process, run /sbin/vboxconfig as root. If your system is using EFI Secure Boot you may need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system’s documentation for more information.

****************************************************************

Here’s the log:

****************************************************************

Building the main VirtualBox module.
Error building the module:
/tmp/vbox.0/Makefile-header.gmk:100: *** The variable KERN_DIR must be a kernel build folder and end with /build without a trailing slash, or KERN_VER must be set. Stop.

*******************************************************************

Now what?

[Noon update]

So I followed the instructions here, including the reboot, and still no joy. Now the error log is (click on “continue reading if you want to see it):

[Update a while later]

OK, it was the new kernel. I reverted to the previous one and it’s fine. I wonder if I should report this to Oracle, or Fedora, or both?

[Update a while later]

OK, I updated to the new version of VirtualBox, and it now works with the new kernel. I guess VB doesn’t automatically update when I do a general update. I should probably add the repository for it.

Continue reading Virtual Box Woes

Computer Problems

So the parts arrived today, and I’m installing the motherboard. The problem is, in addition to the 24-pin power connector, there are slots for an 8-pin and a 4-pin, right next to each other. But the PSU has no 4-pin connector; it only has an 8-pin, and four 6+2s. What am I supposed to do? I see that on my own X570 board from MSI (similar to the new one, but a different model), I didn’t use it, and it seems to be running OK. So just ignore?

[Update a while later]

Well, it seems to be running fine without it.

The good news: It works. The bad news: The new processor isn’t compatible with Windows 8.1; it says it needs to upgrade to 10. And I can’t get good screen resolution, which will probably get fixed after an upgrade.

[Wednesday-morning update]

OK, $200 later, we upgraded to 10, but still crap resolution. Had to install Nvidia drivers to clean things up. But now all seems well. So far.

Computer Fun

Patricia’s machine has been acting up for months, dying unexpectedly. I tried replacing CPU, memory, and power supply. Also cleaned the CPU heat sink. But to no avail, and now it shuts down almost immediately after boot. So it’s probably the motherboard.

And of course you can’t buy new FM-2 mobos any more, so it means new processor and memory as well, plus a graphics card, because the Ryzen doesn’t support on-board integrated graphics. So we just had to lay out about $600 for an upgrade, but it will be a much better machine, with a Ryzen 5 3600X (same as mine) and 32G of RAM in a single stick (upgradable to 128G). It will also be able to support multiple monitors. Unfortunately, it won’t be here before Tuesday.

[Sunday-morning update]

Wow, time flies. I just realized from an old blog post that her mobo was five years old.

Quarantine Lessons From Spaceflight

Thoughts on the similarities.

Meanwhile, we’re back home. As noted, we did drive up to Cambria (with the cats, which was…interesting — it was their first road trip, and Ember cried most of the way). It was relaxing up there, but a little weird, with all the restaurants being closed except for delivery or carry out, and most of the motels empty (we had a vacation rental across the street from the beach). We drove up to Ragged Point on Saturday (which was also closed except for gas and the general store), but no further into Big Sur, then perused the elephant seals on the way back to town. Not that many on the beach; it was just past mating season. A few week ago the beach at Piedras Blancas would have been full of them, fighting and fu**ing (I could have just written “mating,” but I liked the alliteration), and the mothers and pups trying to avoid being crushed by the bulls.

Did a three-mile hike Sunday on the bluffs above the ocean, and shot lots of pictures of breaching and fluking gray whales and their spouts as they migrated north. Very weird being up there on a weekend with so little traffic. I may post some, after we look at them to see how they came out.

Got back to Redondo Beach yesterday (the lack of heavy traffic on the 405 through Sepulveda Pass and West LA on a Monday afternoon was a little eerie), and now get to put the house back together after fumigation. The cats (who cried all the way back) are looking around and at each other like they’re wondering “Was that all some sort of weird dream?” Not infected, as far as we know (seems unlikely, considering that we were already hermits before this all started; it’s an introvert’s paradise).

[Update mid-morning]

One thing we saw up there that we never see in LA: Stars. We were across the street from the beach, and it was quite a dark neighborhood. Orion was very obvious, and I could easily see the Pleides naked eye. Milky Way wasn’t obvious, though.

Safer At Someone Else’s Home

California turned up the screws last night, but extermination is an exempted activity, so the fumigators are still coming today, and we’re still driving up to Cambria (and returning Monday) with the cats. If anyone stops us, I’m pretty sure that once we explain the situation, we’ll be waved on. But there is still plenty of traffic on the highways (though nothing like normal), so no reason to pull us over (unless I actually do something wrong). I may be a little less leadfoot than usual.

[Saturday-morning update]

Probably the quickest trip from LA to Cambria ever–about three and a half hours, which was good because we had a crying cat. Traffic was light, and moving along at 80 mph on the freeways. More anon.

Internet Problems

I seem to have lost the ethernet connection to my desktop. There is nothing to indicate a problem; Fedora tells me it’s connected, but I can’t ping anything. Not sure how to troubleshoot. I’ve tried switching cables, but it doesn’t help. But I know that there’s no problem with the router, because wireless is up (I’m typing this from my notebook).

(Monday-morning update)

Still haven’t solved it, but on a flight to Denver for suborbital researchers conference, so won’t get to it until Thursday.

[Thursday-morning update]

It’s clearly a weird DNS problem. I can ping Google’s IP, but I cannot ping google.com. I can ping 8.8.8.8, but when I manually set that as DNS, it still doesn’t work.

I tried plugging directly into the router instead of the Orbi, with same results.

I have not changed anything in the configuration; it had been working fine for many months as it was set up, with the router feeding the main Orbi via ethernet, and the Orbi providing both ethernet and wifi to my desktop and the house. But for some reason, I woke up almost a week ago, and the desktop had no Internet.

[Bumped]

[Afternoon update]

Well, this is fun. It’s clearly a software issue.

I just pulled the SSD off my laptop and booted the desktop from it, and it now works. I’m suspecting that it has something to do with expressvpn. Since I installed it, I don’t have Internet until I connect it. But on the machine that has problems, I couldn’t connect, so I removed it, but it didn’t solve the problem. There must be some setting that doesn’t allow the machine to do DNS without expressvpn, which somehow went haywire last week.

I’m wondering if the best solution would be to just install a clean version of Fedora 31 (I’m currently using 30) on either the old SSD, or a new one.

[Friday update]

OK, it turned out that ExpressVPN was locking out the Internet when it wasn’t connected (for my “safety”), which meant that if something went wrong with the connection, it made it impossible to reconnect to ExpressVPN, or the Internet. After spending several hours this morning on chat with someone at ExpressVPN, and wasting my time going down various rabbit holes, I finally found someone who told me to just blow away /etc/resolv.conf, and reconnect, which gave me Internet again.

I did manage to convey that they had some serious bad practices that resulted in this frustration, and gave them some recommendations.

  1. Let the icon tell me whether I have a good connection. Ever since I installed the expressvpn package, it always has a question mark on it, whether it is connected or not.
  2. Have an autoconnect that actually works on login, rather than having to go into shell each time and manually connect.
  3. Provide an ability to override the lock (with a warning) rather than simply lock it when ExpressVPN isn’t connected.

They said they’d try to incorporate into the next version.