Hello, Gentoo.
On Sat, Apr 29, 2017 at 11:56:35 +, Alan Mackenzie wrote:
> On Fri, Apr 28, 2017 at 20:16:37 +, J. Roeleveld wrote:
> > Have you tried connecting using ssh after boot?
> > Also, do you have the EFI console support in your kernel?
> I didn't, but do now.
> More to the
Hello, Joost.
On Fri, Apr 28, 2017 at 20:16:37 +, J. Roeleveld wrote:
> On April 28, 2017 9:51:07 PM GMT+02:00, Alan Mackenzie wrote:
> >In the end, I went with grub2, and it has taken a lot of effort to get
> >not very far. Grub's documentation is suboptimal.
> >The state
On Saturday, April 29, 2017 1:17:11 AM CEST Daniel Frey wrote:
> On 04/28/2017 12:51 PM, Alan Mackenzie wrote:
> > Hello, Mick and the whole World.
> >
> > # Load a linux kernel, passing the root filesystem and init process as
> > parameters echo "Loading kernel..."
> > echo
On Sat, 29 Apr 2017 07:57:49 +0800, Bill Kenworthy wrote:
> I failed to get grub working (rather, gave up because of the lack of
> docs) and went with rEFIt.
info grub
or
https://www.gnu.org/software/grub/manual/grub.html
Not that I would advise using GRUB on a UEFI system, it's such overkill,
>>> --
>>> Regards,
>>> Mick
>
> Have you tried connecting using ssh after boot?
> Also, do you have the EFI console support in your kernel?
>
> Not near my desktop to check which ones exactly.
>
> --
> Joost
>
Second this - check the kernel options for EFI but also add the NVME drives.
I
On 04/28/2017 12:51 PM, Alan Mackenzie wrote:
> Hello, Mick and the whole World.
>
> # Load a linux kernel, passing the root filesystem and init process as
> parameters
> echo "Loading kernel..."
> echo "grub_platform = " $grub_platform
> gfxpayload=text # For debugging.
On April 28, 2017 9:51:07 PM GMT+02:00, Alan Mackenzie wrote:
>Hello, Mick and the whole World.
>
>On Tue, Apr 25, 2017 at 00:00:07 +0100, Mick wrote:
>
>> Have a look here in case it helps:
>
>> https://wiki.archlinux.org/index.php/GRUB#RAID
>
>In the end, I went with grub2, and it
Hello, Mick and the whole World.
On Tue, Apr 25, 2017 at 00:00:07 +0100, Mick wrote:
> Have a look here in case it helps:
> https://wiki.archlinux.org/index.php/GRUB#RAID
In the end, I went with grub2, and it has taken a lot of effort to get
not very far. Grub's documentation is suboptimal.
On Monday 24 Apr 2017 19:56:22 Alan Mackenzie wrote:
> Hello, Peter.
>
> On Fri, Apr 21, 2017 at 06:56:32 +0100, Peter Humphrey wrote:
>
> [ ]
>
> > I also have an Asus motherboard, but for Intel hardware.
> >
> > In your BIOS secure-boot page, do you have a section called Key
> >
On Monday 24 Apr 2017 19:56:22 Alan Mackenzie wrote:
> I think I'll look at bootctl. It's looks far more likely to give me
> what I want than grub2. Does it cope OK with mdadm RAID setups?
I don't see why not. Detecting and setting up RAID comes after choosing the
system to be booted.
--
Hello, Peter.
On Fri, Apr 21, 2017 at 06:56:32 +0100, Peter Humphrey wrote:
[ ]
> I also have an Asus motherboard, but for Intel hardware.
> In your BIOS secure-boot page, do you have a section called Key Management?
> When I was working on getting my machine to boot, a year ago, I was
On Thursday 20 Apr 2017 19:32:54 Alan Mackenzie wrote:
> Hello, Mick.
>
> On Thu, Apr 20, 2017 at 20:11:33 +0100, Mick wrote:
> > On Thursday 20 Apr 2017 18:26:43 Alan Mackenzie wrote:
--->8
> > > Can anybody suggest ideas to get this machine booting? Would
> > > partitioning the drives with
On Thu, Apr 20, 2017 at 3:10 PM, Mick wrote:
> Boot with a LiveCD or LiveUSB which offers UEFI booting capability; e.g.
> sysrescuecd.
>
> Make sure your kernel has been configured and built for the boot system you
> will be using.
>
> Prepare a UEFI boot partition/fs
On Thursday 20 Apr 2017 19:32:54 Alan Mackenzie wrote:
> Hello, Mick.
>
> On Thu, Apr 20, 2017 at 20:11:33 +0100, Mick wrote:
> > On Thursday 20 Apr 2017 18:26:43 Alan Mackenzie wrote:
> > > Hello, Gentoo.
> > >
> > > The saga of my new AMD Ryzen machine: I've installed Gentoo onto
> > >
Hello, Mick.
On Thu, Apr 20, 2017 at 20:11:33 +0100, Mick wrote:
> On Thursday 20 Apr 2017 18:26:43 Alan Mackenzie wrote:
> > Hello, Gentoo.
> > The saga of my new AMD Ryzen machine: I've installed Gentoo onto
> > (mdadam) RAID-1 on two MVMe Samsung 960 EVO M.2 SSDs, one of them being
> >
On Thursday 20 Apr 2017 18:26:43 Alan Mackenzie wrote:
> Hello, Gentoo.
>
> The saga of my new AMD Ryzen machine: I've installed Gentoo onto
> (mdadam) RAID-1 on two MVMe Samsung 960 EVO M.2 SSDs, one of them being
> plugged into the motherboard, the other in a carrier card plugged into
> the
Hello, Gentoo.
The saga of my new AMD Ryzen machine: I've installed Gentoo onto
(mdadam) RAID-1 on two MVMe Samsung 960 EVO M.2 SSDs, one of them being
plugged into the motherboard, the other in a carrier card plugged into
the second PCIe x16 slot.
At least, I've got as far as the point where I
On 170417-11:19+0200, Miroslav Rovis wrote:
> On 170415-13:50+, Alan Mackenzie wrote:
...
> It's --zero, I don't remember well at all. Use mdadm to zero
> the mdadm-related stuff.
It's --zero-superblock or very similar to that...
Happy Easter to all believers!
--
Miroslav Rovis
Zagreb,
On 170415-13:50+, Alan Mackenzie wrote:
> Hello, Alan.
>
> On Mon, Apr 10, 2017 at 21:12:44 -0400, Alan Grimes wrote:
...
> I've got 90% through a Gentoo installation on it, and I'm just
> considering how best to un-mdadm my boot partition (which I mistakenly
> turned into a RAID partition
Hello, Mick.
On Mon, Apr 10, 2017 at 22:46:14 +0100, Mick wrote:
> On Monday 10 Apr 2017 21:24:21 Alan Mackenzie wrote:
> > Another idea I've had is that I've got duff RAM. The various bootable
> > images that crash don't always crash in _exactly_ the same places. And
> > the BIOS mouse and
Hello, Alan.
On Mon, Apr 10, 2017 at 21:12:44 -0400, Alan Grimes wrote:
> On these new mobos, it's important to update the BIOS as soon as
> possible. I DL'd a Bios with my 'doze 7 machine first thing and flashed
> it. The original bios I had was version 418 from February, the new one
> was 520
On these new mobos, it's important to update the BIOS as soon as
possible. I DL'd a Bios with my 'doze 7 machine first thing and flashed
it. The original bios I had was version 418 from February, the new one
was 520 from a few days before I started... It is very important this is
done before
On 04/10/2017 12:07 PM, Alan Mackenzie wrote:
>> He [Alan Grimes] has new hardware (Ryzen) that needs 4.10 for proper support.
>
> I too have new hardware (An Asus Prime X370-PRO MB with a Ryzen 1700X
> processor), indeed so new that my first attempt to boot a minimal CD was
> less than an hour
On Monday 10 Apr 2017 21:24:21 Alan Mackenzie wrote:
> Another idea I've had is that I've got duff RAM. The various bootable
> images that crash don't always crash in _exactly_ the same places. And
> the BIOS mouse and keyboard freezing up don't inspire confidence. I do
> hope it's not the
On Mon, Apr 10, 2017 at 21:23:18 +0100, Mick wrote:
> On Monday 10 Apr 2017 19:07:49 Alan Mackenzie wrote:
> > I too have new hardware (An Asus Prime X370-PRO MB with a Ryzen 1700X
> > processor), indeed so new that my first attempt to boot a minimal CD was
> > less than an hour ago.
> > The
On Monday 10 Apr 2017 19:07:49 Alan Mackenzie wrote:
> Hello, Daniel.
>
> On Fri, Apr 07, 2017 at 08:48:22 -0700, Daniel Frey wrote:
> > On 04/06/2017 10:03 AM, Nikos Chantziaras wrote:
> > > On 04/05/2017 05:15 PM, Alan Grimes wrote:
> > >> I'm still running on my old kernel as I re-build my
Hello, Daniel.
On Fri, Apr 07, 2017 at 08:48:22 -0700, Daniel Frey wrote:
> On 04/06/2017 10:03 AM, Nikos Chantziaras wrote:
> > On 04/05/2017 05:15 PM, Alan Grimes wrote:
> >> I'm still running on my old kernel as I re-build my system, Nvidia
> >> drivers just barfed
> > 381.09 was released
27 matches
Mail list logo