On 02/09/2021 23:11, Neil Bothwick wrote:
On Thu, 2 Sep 2021 23:49:40 +0200, David Haller wrote:
Yes it does, but only on the testing version. If you are running
stable, you won't have it.
I beg to differ on that point:
My bad, I was looking in the wrong part of the eix output.
It seems a
On Thu, 2 Sep 2021 23:49:40 +0200, David Haller wrote:
> >Yes it does, but only on the testing version. If you are running
> >stable, you won't have it.
>
> I beg to differ on that point:
My bad, I was looking in the wrong part of the eix output.
It seems a trip to Barnard Castle is in
Hello,
On Thu, 02 Sep 2021, David Haller wrote:
>On Thu, 02 Sep 2021, Neil Bothwick wrote:
>>Yes it does, but only on the testing version. If you are running stable,
>>you won't have it.
>
>I beg to differ on that point:
>
>$ cd $(portageq get_repo_path / gentoo)
>$ for f in
Hello,
On Thu, 02 Sep 2021, Neil Bothwick wrote:
>Yes it does, but only on the testing version. If you are running stable,
>you won't have it.
I beg to differ on that point:
$ cd $(portageq get_repo_path / gentoo)
$ for f in sys-libs/glibc/glibc-*.ebuild; do \
if grep -q 'KEYW.* amd64'
Replied to the list.
On Thu, 2 Sep 2021 15:50:37 -0400, Alan Grimes wrote:
> Neil Bothwick wrote:
>
> If you wish to manually migrate now, there are a series
> of steps described on the wiki (see below), but the outline is:
> * unforce the crypt USE flag of sys-libs/glibc and disable it
> *
Chromium has been a heaping pile of crash these days so I've been
running update every few days to try to get a working version.
Ok, apparently gcj is not a thing anymore and has broken libidn (iirc),
I got around that with a useflag...
As always, Gentoo finds new and more bizare ways to
On Thu, 2 Sep 2021 10:35:49 -0400, Alan Grimes wrote:
> Chromium has been a heaping pile of crash these days so I've been
> running update every few days to try to get a working version.
>
>
> Ok, apparently gcj is not a thing anymore and has broken libidn (iirc),
>
> I got around that with a
On 01/29/2017 09:29 AM, Alan Grimes wrote:
> Mick wrote:
>> - You have run the efibootmgr command with the right syntax, options and
>> parameters and have run it a second time as 'efibootmgr -v' to verify its
>> output shows correctly the path to your gentoo kernel image.
>
> Can't do this
On 01/29/2017 09:07 AM, Alan Grimes wrote:
> Mick wrote:
>> On Saturday 28 Jan 2017 20:24:34 Alan Grimes wrote:
>
> Dudes, sorry, I obviously have a crossed-neuron in my brain and can't
> remember MFT versus GPT because they are so conceptually similar, Give
> it a rest. Please don't waste more
On Sun, 29 Jan 2017 12:29:52 -0500, Alan Grimes wrote:
> > - You have run the efibootmgr command with the right syntax, options
> > and parameters and have run it a second time as 'efibootmgr -v' to
> > verify its output shows correctly the path to your gentoo kernel
> > image.
>
> Can't do
Mick wrote:
> - You have run the efibootmgr command with the right syntax, options and
> parameters and have run it a second time as 'efibootmgr -v' to verify its
> output shows correctly the path to your gentoo kernel image.
Can't do this step because of chicken and egg conflict.
--
Strange
Mick wrote:
> On Saturday 28 Jan 2017 20:24:34 Alan Grimes wrote:
Dudes, sorry, I obviously have a crossed-neuron in my brain and can't
remember MFT versus GPT because they are so conceptually similar, Give
it a rest. Please don't waste more than a single line correcting me. =(
I'll be first in
On Sat, 28 Jan 2017 20:24:34 -0500, Alan Grimes wrote:
> Neil Bothwick wrote:
> > On Sat, 28 Jan 2017 12:11:28 -0500, Alan Grimes wrote:
> >
> > It appears to be a 2-stage boot process:
> >
> > BIOS boot -> Binary of GRUB bootstrap loader.
> > You don't have a BIOS with a UEFI system.
>
> We
On Saturday 28 Jan 2017 20:24:34 Alan Grimes wrote:
> Neil Bothwick wrote:
> > On Sat, 28 Jan 2017 12:11:28 -0500, Alan Grimes wrote:
> >
> > It appears to be a 2-stage boot process:
> >
> > BIOS boot -> Binary of GRUB bootstrap loader.
> > You don't have a BIOS with a UEFI system.
>
> We were
On 01/28/2017 05:24 PM, Alan Grimes wrote:
> Neil Bothwick wrote:
>> On Sat, 28 Jan 2017 12:11:28 -0500, Alan Grimes wrote:
>>
>> It appears to be a 2-stage boot process:
>>
>> BIOS boot -> Binary of GRUB bootstrap loader.
>> You don't have a BIOS with a UEFI system.
>
> We were discussing BIOS
Neil Bothwick wrote:
> On Sat, 28 Jan 2017 12:11:28 -0500, Alan Grimes wrote:
>
> It appears to be a 2-stage boot process:
>
> BIOS boot -> Binary of GRUB bootstrap loader.
> You don't have a BIOS with a UEFI system.
We were discussing BIOS boot on a MFT partition scheme, which is what
I'm using
On Sat, 28 Jan 2017 12:11:28 -0500, Alan Grimes wrote:
> >> Device Start End Sectors Size Type
> >> /dev/sdc12048264191262144 128M EFI System
> >> /dev/sdc2 526336 537233407 536707072 255.9G Linux filesystem
> >> /dev/sdc3 264192526335262144 128M BIOS boot
On Fri, Jan 27, 2017 at 10:07 AM, Alan Grimes wrote:
>
> Had another learning experience with respect to how GPT disks work.,
> system is buttoned up and operating in GPT mode. In old systems, the
> boot sectors and bootstrap loaders were kinda consigned to a digital
>
Neil Bothwick wrote:
> On Fri, 27 Jan 2017 08:41:44 -0500, Alan Grimes wrote:
>
>> Device Start End Sectors Size Type
>> /dev/sdc12048264191262144 128M EFI System
>> /dev/sdc2 526336 537233407 536707072 255.9G Linux filesystem
>> /dev/sdc3 264192526335262144
On Fri, 27 Jan 2017 08:41:44 -0500, Alan Grimes wrote:
> Device Start End Sectors Size Type
> /dev/sdc12048264191262144 128M EFI System
> /dev/sdc2 526336 537233407 536707072 255.9G Linux filesystem
> /dev/sdc3 264192526335262144 128M BIOS boot
You don't
Alan Grimes wrote:
[]
Had another learning experience with respect to how GPT disks work.,
system is buttoned up and operating in GPT mode. In old systems, the
boot sectors and bootstrap loaders were kinda consigned to a digital
pergatory on the drive, now you just have to give it its own 1mb
To make a boot disk in DOS you have two options.
Format /s x:
and
Sys x:
Once this is done, the new disk will boot perfectly [period] .
So what I did was I deleted my botched UEFI partition, and created two
new partitions, each of half-size.
I mark ... well.:
#33
On Wed, Jan 25, 2017 at 6:58 PM, Alan Grimes wrote:
> Tom H wrote:
>> AFAIK, when you load the kernel directly from the EFI firmware, it has
>> to have the ".efi" suffix. But that doesn't explain why it would stall
>> when loaded from grub...
>>
>> Somewhat OT: Regarding
Bill Kenworthy wrote:
> On 27/01/17 08:33, Alan Grimes wrote:
>> Neil Bothwick wrote:
>>> On Thu, 26 Jan 2017 17:07:03 -0500, Alan Grimes wrote:
>>>
4. Create MFT partition table.
>>> MFT? Isn't that something to do with NTFS? You need a GPT partition table
>>> if you want to boot with UEFI.
On 27/01/17 08:33, Alan Grimes wrote:
> Neil Bothwick wrote:
>> On Thu, 26 Jan 2017 17:07:03 -0500, Alan Grimes wrote:
>>
>>> 4. Create MFT partition table.
>> MFT? Isn't that something to do with NTFS? You need a GPT partition table
>> if you want to boot with UEFI.
>>
>
> yeah, my bad memory,
Neil Bothwick wrote:
> On Thu, 26 Jan 2017 17:07:03 -0500, Alan Grimes wrote:
>
>> 4. Create MFT partition table.
> MFT? Isn't that something to do with NTFS? You need a GPT partition table
> if you want to boot with UEFI.
>
yeah, my bad memory, it was MFT, as offered by gparted. I don't seem to
On Thu, 26 Jan 2017 17:07:03 -0500, Alan Grimes wrote:
> 4. Create MFT partition table.
MFT? Isn't that something to do with NTFS? You need a GPT partition table
if you want to boot with UEFI.
--
Neil Bothwick
deja vous - the act of forgetting someone's name /again/ despite being
introduced
My ordeal with grub continues.
I tried the bleeding edge GRUB, no change in behavior.
I realized that I had an additional source of information that I had
been neglecting. The boot fixer thumb drive I had in the back of the
mascheen was booting UEFI into a crappy bloating debian-ish thingy.
Tom H wrote:
> On Wed, Jan 25, 2017 at 1:05 PM, Alan Grimes wrote:
>> The linux kernel stalls stone cold dead in either direct from firmware
>> or pass through grub mode.
> AFAIK, when you load the kernel directly from the EFI firmware, it has
> to have the ".efi" suffix.
On Wed, Jan 25, 2017 at 1:05 PM, Alan Grimes wrote:
>
> The linux kernel stalls stone cold dead in either direct from firmware
> or pass through grub mode.
AFAIK, when you load the kernel directly from the EFI firmware, it has
to have the ".efi" suffix. But that doesn't
I re-installed grub and now it boots through the grub menu to the point
of handing off to the linux kernel. The linux kernel stalls stone cold
dead in either direct from firmware or pass through grub mode.
So I think Grub is 97.6% exonerated at this point.
This is my standard kernel.org pure
After 7 long years, the peace of mind feature on my Velociraptor HD had
finally given up the ghost.
So I get a new SSD, that's slightly smaller but still a large multiple
of what I actually need the drive for. =P
To be fully trendy (and finally wanting to put the 1980's to bed) I try
to set up
32 matches
Mail list logo