[ Date Index ]
[ Thread Index ]
[ <= Previous by date /
thread ]
[ Next by date /
thread => ]
Re: [LUG] Grub Problem
- To: list@xxxxxxxxxxxxx
- Subject: Re: [LUG] Grub Problem
- From: Neil <barnaby@xxxxxxxxxxxx>
- Date: Mon, 17 Aug 2020 08:24:45 +0100
- Content-language: en-GB
- Delivered-to: dclug@xxxxxxxxxxxxxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dcglug.org.uk; s=1586423162; h=Sender:Content-Type: Content-Transfer-Encoding:Reply-To:List-Subscribe:List-Help:List-Post: List-Unsubscribe:List-Id:Subject:In-Reply-To:MIME-Version:Date:Message-ID: From:References:To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner:List-Archive; bh=xaXcxb62PyOpmswlkAxXCuHO6+wDvY4A/6U47L5Cgf4=; b=tpwJRFF4SUmEypboBbSGJpfCJ Z4Xf/IHN5bY3ZcWhYtSN5WuZ/oV6/tpOoFgPeSSOoxBfCZn+q5TEt/ik3OCSI+BiM8Q3Knc9NuZQp 08ctDbF0rSQhHye8YoHAKTzkMYa3BKqd480Zv5JBQED0Rx8Jh5YpGGc2DiPHoR94ftqYw=;
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=pamneil.com ; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=JQtTqjNc3Dd1yk7Lf+lu+FakaXFXeCAzOInMbUdP3z8=; b=CSbNGKgf8BYxdPPr9Gu44ca4+K bHDcOx3bnEV8Vh9+wFWP6VW6cwECkI0YsY3hMAVt1WVRB774crI0mBJDtMMve6d3Ojj/rgaYAbhpb OIUjTOeVW3wQxSImxmqDY7bMZF3pcztzaXHemJnYdGYS1rdP42PgXgGwdKiFrdd33I61u/WE9gOKf uvSW3F9kM75qLDD1CztrxXED/YzfxU7ru6NsGIBNALGsIcPBgejAgJI14iJ3fzJYFIUSdwHBg0dTx rUDNI0oeYfV/cqxZflyFMwSU3vpzLxMnb8/ZQOYOWXmcKmuKuDUOXtWRILEnsEFoGYufSbua8k4xU ioiHWk5Q==;
On 16/08/2020 12:30, Sebastian wrote:
Dear Neil,
Apparently you can use 'apt-get -qq upgrade' to show everything but
errors. I haven't tried this (I use Zypper for packages currently) but
it should make it a bit easier to see problems.
I will have a look at that. Thanks.
Still learning, though. It had never occurred to me that the old
live USB would no longer work. Replacing it with the latest iso for
MX worked. I will remember that.
Hmm. This confuses me. Clearly you have done everything correctly
regarding BIOS boot order, but that you would get the same error
message is most puzzling. Perhaps someone on this list can explain - if
the old Live USB worked originally, why should it be affected by GRUB
problems on the internal hard drive?
As I said, I am confused too. At first I tried to log in with the USB
stick that I had used to install MX in the first place. (That was at the
end of last year when version 19 first came out.) This came up with the
same error. So, as advised, I installed the most recent iso for MX on
the same USB stick, and this worked perfectly. Then I was able to run
the boot repair facility which is provided by MX.
So now it is all fine.
Regards,
Neil
--
The Mailing List for the Devon & Cornwall LUG
https://mailman.dcglug.org.uk/listinfo/list
FAQ: http://www.dcglug.org.uk/listfaq
