Tag Archive | UEFI

OpenSUSE Leap 15 — an early look

Work on Leap 15 is underway.  There was a short discussion on the factory mailing list, beginning HERE.

Two months after my last status update Leap 15 is almost rolling.  Following SLE 15 I’d like to aim for a release in April.

It is worth reading that whole message, and perhaps the other emails that follow it.  As the message indicates, there is now a download site for isos, in case you want to try Leap 15 for yourself.

I went to the openQA site to look at failures.  And they didn’t seem too bad.  So I downloaded an iso from there.  It was “openSUSE-Leap-15.0-DVD-x86_64-Build48.1-Media.iso”.

Read More…

Advertisements

Solus booting woes

Solus is a nicely themed linux distro.  I particularly liked the Budgie desktop, which comes from the Solus team.  Solus would not be my personal choice,  because I’m a command line type of person and Solus seems more oriented to people used to Windows.

While it would not be my preferred distro, it is still disappointing that Solus does not seem to handle booting well.  I’ve had Solus installed in an extra partition for some time now, and how it handles booting is an issue.  Perhaps I’ll report on the problems that I have seen in another post.  But, for now, I will just be describing my tests.

Read More…

Install Tumbleweed into existing VM

Last month, I created a Tumbleweed Virtual Machine (or VM), using KVM.  Yesterday’s project was to install into that existing VM.  I wanted a clean install, retaining “/home” but reformatting everything else.

Fortunately, that previous install was for UEFI booting.  I’m not sure how easy it would have been to do new install into the same BIOS based virtual machine.

Downloading

I started by downloading the DVD installer for Tumbleweed snapshot 20171007.  As usual, I downloaded the sha256 checksum file with “wget”, and I downloaded the iso itself using “aria2c”.

I then verified the gpg signature on the sha256 checksum file, using gpg.  Then I used “sha256sum -c” to verify the checksum of the download iso file.

Read More…

Creating a virtual machine

In my previous post, I explained how I setup KVM.  Today, I’ll describe creating virtual machines that run under KVM.

Creating with Yast

The easiest way to do this with openSUSE, is to use Yast.  Click on “Virtualization” and then on “Create virtual machines …”.

In the first step (step 1 of 5), you specify whether the source for the virtual machine is an iso file, a network install, a PXE network boot or an existing disk image.  For me, the iso file is the most suitable source.  On the second screen (step 2 of 5), I can browse for the iso file.

On the third screen, I can specify how much memory to use.  On my system, it defaults to 1G (or 1024M).  For my first install, I took that default.  Since that time, I have been upping it to 2G or 4G.  I can also specify how much CPU to assign.  I have 4-core machine.  This defaults to assigning 1 cpu.  I have been increasing that to 2 cpu.  For my first install, however, I left it at the default of 1 cpu.

Read More…

Linux multi-boot part 2 (booting)

In yesterday’s post, I discussed ways of having multiple linux installs on that same computer, using my laptop as an example.  Today, I continue with that, but mostly concentrate on the details of booting.

If you have multiple versions of linux installed, then you presumably want to be able to boot any of them.  Fortunately, linux usually installs a boot manager, typically grub2, which provides a menu that allow selecting which system to boot.

The problem

There are a couple of problems with this.  Firstly, the most recent linux that is installed usually takes over the booting.  And that might not be what you want.  And, secondly, if there is a kernel update on one of the installed linux versions that is not controlling the boot, that might cause problems on the next boot unless the boot menu that you use is updated.

Read More…

UEFI and opensuse Leap 42.1

Leap 42.1 started out with some UEFI problems.  The last of those were fixed in an update yesterday.  However, the fix only solves the problem for already installed systems.  The install media still have these problems.  Since opensuse usually does not re-release install isos, it is unlikely that install problems will completely go away.

In this post, I’ll describe what were the problems and how to deal with them on a fresh install.

I’ll describe these problems in terms of the associated bug number.

  • bug 950569: with this bug, the computer would seem to lockup during boot, though CTRL-ALT-DEL did work to retry the boot.  Disabling secure-boot allowed the system to boot.
  • bug 954126: this bug prevented booting Windows in a UEFI box, unless secure-boot was disabled.
  • bug 917427: if you installed into an encrypted LVM, and if you did not use a separate unencrypted “/boot”, then the secure-boot method of booting did not work.

Boot files for UEFI

I’ll start by describing what the various files do during booting.

Read More…

My Tumbleweed install for December 2015

For this month, I installed snapshot 20151218.  The install was done on Monday morning.

I had recently replaced the hard drive on my main desktop, so this was a new install to replace what I had installed on the previous drive.  I had already created partitions, including an encrypted LVM with space for several root file systems, a swap file system and a home file system.  So I wanted to install Tumbleweed into the encrypted LVM.

Using btrfs

Up until now, I have avoided “btrfs”, except for a brief trial with a beta release of 13.1.  It is about time for more serious testing.  So I decided to use “btrfs” for the root file system with this Tumbleweed install.  Apparently, “btrfs” works best if “/boot” is part of the root file system.  So this meant no separate unencrypted “/boot”.

Read More…

UEFI and opensuse Leap 42.1

There have been several problems with UEFI on Leap.

As originally installed, it suffered from bug 950569, where some hardware would hang during boot unless secure-boot was disabled.  This bug was originally reported for Tumbleweed, but also showed up in Leap.  It was recently fixed in Tumbleweed.  And today, an update showed up for Leap to fix this bug.  The update also fixed a MokManager problem, which I have not personally experienced.

There’s a problem, though.  The updated shim package has been installed.  But the updated shim.efi was not installed in the EFI boot settings (normally in “/boot/efi/EFI/opensuse”).

Read More…

My Tumbleweed install for October

I said there would not be a Tumbleweed install this month.  But I changed my mind on that.  Snapshot 20151017 came out after I had finished my Leap 42.1-RC1 installs, and I had a little free time.

For this install, I used a 1T disk.  It had previously been used for Windows.  I plugged the disk into a SATA disk docking station, and planned to use the entire disk for the Tumbleweed install.  I connected the docking station to a UEFI computer (via a USB cable).

First attempt

My plan was to try installing to an encrypted LVM.  There are some open bug reports indicating problems, so I wanted to see what would happen.

Read More…

Testing KaOS 2015.08

I saw a Distrowatch announcement of a new release of KaOS, so decided to give it a try.  From there, I followed the link to the release announcement.

My previous experience with KaOS was in April, where it failed to install.  This time, I had a better experience.

KaOS is a rolling KDE based distro.  It is using plasma 5.  The new version came with a beta release of plasma 5, so gives me an early look of what I can soon expect to see in opensuse Tumbleweed.  The downloaded system uses a release-candidate for Plasma 5.4.

Downloading

I check the torrent link, but that seemed to be for an earlier release.  My understanding is that torrent downloads are provided by users, and I probably looked before they had set it up for the new release.

Read More…