public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: scanner problem : latest
Date: Tue, 24 Jul 2018 15:38:35 +0100	[thread overview]
Message-ID: <2621760.4p9lDnPvMA@dell_xps> (raw)
In-Reply-To: <20180724141432.GE1955@ca.inter.net>


[-- Attachment #1.1: Type: text/plain, Size: 1198 bytes --]

On Tuesday, 24 July 2018 15:14:32 BST Philip Webb wrote:
> 180723 Neil Bothwick wrote:
> > On Fri, 20 Jul 2018 09:04:26 -0400, Philip Webb wrote:
> >> Linux Mint 19 leads you along to a point where you've told it
> >> where to install, you click 'proceed' & it chugs along nicely,
> >> then it says it's trying to install a bootloader
> >> without asking whether you want it to or where to do it.
> > 
> > For future reference, start the Mint installer with "ubiquity -b",
> > then it doesn't install a boot loader at all
> > and you can add it to your Gentoo bootloader after rebooting.
> 
> I started the Mint installer by clicking on its desktop button.
> What is 'ubiquity' & how would I use it ?
> 
> > WinErr 018: Unrecoverable error - System has been destroyed.
> > Buy a new one. Old Windows licence is not valid anymore.
> 
> That's how I felt for  30 min  after Mint played its dirty trick above
> (grin).


See attached screenshot.

Meanwhile I'm still at a loss why on a BIOS with GPT system GRUB installed 
fine without any mishaps, but upon a GRUB update some days later it refused to 
install without me creating a new protective MBR partition marked as ef02.

:-/

-- 
Regards,
Mick

[-- Attachment #1.2: Screenshot_20180724_134554.png --]
[-- Type: image/png, Size: 419506 bytes --]

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-07-24 14:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-17  6:38 [gentoo-user] scanner problem Philip Webb
2018-07-17 14:18 ` Steven Lembark
2018-07-17 14:23 ` Jack
2018-07-17 14:43   ` Mick
2018-07-18  8:16 ` Philip Webb
2018-07-18  9:50   ` Andrew Udvare
2018-07-19  6:03   ` Raffaele Belardi
2018-07-19  9:29   ` [gentoo-user] scanner problem : latest Philip Webb
2018-07-19 10:03     ` Mick
2018-07-19 16:08     ` [gentoo-user] " Ian Zimmerman
2018-07-20 13:04       ` Philip Webb
2018-07-20 13:25         ` [gentoo-user] Re: scanner problem : PS Philip Webb
2018-07-20 22:10         ` [gentoo-user] Re: scanner problem : latest Mick
2018-07-23 22:29         ` Neil Bothwick
2018-07-24 14:14           ` Philip Webb
2018-07-24 14:38             ` Mick [this message]
2018-07-26 14:30               ` Mick
2018-07-24 20:10             ` Neil Bothwick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2621760.4p9lDnPvMA@dell_xps \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox