Got the motherboard running, the motherboard was IGNORING the "UEFI
only" BIOS setting, it was attempting to boot my system in BIOS mode, I
found that I had to efibootmgr and tell the stupid BIOS what is what...
why the BIOS doesn't scan the first two directories under /EFI for *.efi
and list them,
>hi.
>
>
>background: ---
>
>previously, i used to run it by this:
>
>> arpwatch -i enp7s0 -m cave...@domain.com -s /usr/sbin/sendmail
>
>but now, after some update, apparently this doesn't work any more.
>
>what seems to have changed is:
>
>* "-m" is replaced by "-w" or "-W". * "-s
hi.
background:
---
previously, i used to run it by this:
> arpwatch -i enp7s0 -m cave...@domain.com -s /usr/sbin/sendmail
but now, after some update, apparently this
doesn't work any more.
what seems to have changed is:
* "-m" is replaced by "-w" or "-W".
* "-s" doesn't
After upgrading my pi64, I get this:
aplay: device_list:274: no soundcards found...
This page implies that the kernel needs to be patched:
https://bbs.archlinux.org/viewtopic.php?id=254406
Can anyone confirm this, and will I be able to upgrade to something
standard soon?
Am Mittwoch, 1. Juli 2020, 03:30:59 CEST schrieb Thomas Mueller:
> > > That's what I did: I found a 2017 stage3 with a still older glibc and
> > > managed to upgrade to a 2020 gentoo while masking the last glibc
> > > versions. That was tricky because I had to git-checkout intermediate
> > > versio
Hi Steve,
On 2020-06-30 20:35, Steve Freeman wrote:
> I have a local gentoo repo mirror that has been running well for
> years. It is essentially the same setup as described at
> https://wiki.gentoo.org/wiki/Local_Mirror except that it runs on a
> non-default port.
I sadly cannot reproduce this
On Wednesday, 1 July 2020 09:15:10 BST Neil Bothwick wrote:
> On Wed, 1 Jul 2020 01:40:54 + (UTC), Alan Grimes wrote:
> > I RMA'd my normal mobo as previously discussed.
> > I went to grab my previous motherboard and it turns out that it had
> > actually released a goodly chunk of it's Magic S
Gerrit:
> On Sun, 21 Jun 2020 10:31:08 +
> Raffaele BELARDI wrote:
>
> > What about the rest of the system, in particular GCC and the C
> > libraries? Do you manage to build the 3.x kernel with up to date
> > system or do you need to ''freeze'' some packages?
>
> 3.2 required an older gcc fo
On Wed, 1 Jul 2020 01:40:54 + (UTC), Alan Grimes wrote:
> I RMA'd my normal mobo as previously discussed.
> I went to grab my previous motherboard and it turns out that it had
> actually released a goodly chunk of it's Magic Smoke (tm) while I
> hadn't been looking. So I went down to the Qui
On Sun, 21 Jun 2020 10:31:08 +
Raffaele BELARDI wrote:
> What about the rest of the system, in particular GCC and the C
> libraries? Do you manage to build the 3.x kernel with up to date
> system or do you need to ''freeze'' some packages?
3.2 required an older gcc for me. I think 5.x and
10 matches
Mail list logo
