Steven Lembark wrote:
> (dev-python/idna-3.1:0/0::gentoo, ebuild scheduled for merge)
> (no parents that aren't satisfied by other packages in this slot)
>
> (dev-python/idna-2.10-r1:0/0::gentoo, ebuild scheduled for merge)
>
пн, 15 февр. 2021 г. в 22:18, Oli Schmidt :
>
> ata5.04: SATA link down (SStatus 0 SControl 0)
> ata5.04: hard resetting link
> ata5.04: failed to resume link (SStatus 0 Scontrol 0)
>
> and
>
> ata5.04: SATA link down (SStatus 0 SControl 0)
> ata5.04: hard resetting link
> ata5.04: failed to
ata5.04: SATA link down (SStatus 0 SControl 0)
ata5.04: hard resetting link
ata5.04: failed to resume link (SStatus 0 Scontrol 0)
and
ata5.04: SATA link down (SStatus 0 SControl 0)
ata5.04: hard resetting link
ata5.04: failed to resume link (SStatus 0 Scontrol 0)
beside all the
пн, 15 февр. 2021 г. в 20:59, Jude DaShiell :
>
> Check the date and time when you boot and if it isn't correct, you
> probably have a dead battery on your motherboard. I had to replace one a
> couple days ago. Fortunately the kind of battery my computer uses is sold
> in pharmacies since blood
Check the date and time when you boot and if it isn't correct, you
probably have a dead battery on your motherboard. I had to replace one a
couple days ago. Fortunately the kind of battery my computer uses is sold
in pharmacies since blood sugar meters also use them.
On Mon, 15 Feb 2021,
Yesterday, my relatively new install of Gentoo failed to boot with the
following repeated messages:
ata5.04: SATA link down (SStatus 0 SControl 0)
ata5.04: hard resetting link
ata5.04: failed to resume link (SStatus 0 Scontrol 0)
My first thought was that something is wrong with my old IDE (ATA)
On February 15, 2021 4:15:43 AM PST, Peter Humphrey
wrote:
>On Sunday, 14 February 2021 21:48:36 GMT Frank Steinmetzger wrote:
>> Am Sun, Feb 14, 2021 at 12:51:30PM -0500 schrieb Jack:
>> > As I remember, /lib and /usr/lib hold not only 32 bit libraries,
>but
>> > non-arch or arch-irrelevant
Greetings,
since my last routine Gentoo upgrade on 2021-02-01 "fwupd" is no longer
started in the "default" run level. Reason is that "fwupd" erroneously
thinks its prerequisite "elogind" is not yet running, starts it again,
interprets the error message "already started" and the non-zero
On Mon, Feb 15, 2021 at 3:17 AM Walter Dnes wrote:
>
> On Sun, Feb 14, 2021 at 06:09:58PM -0700, Grant Taylor wrote
> > On 2/14/21 10:51 AM, Jack wrote:
> > > I don't think you can completely get rid of it.
> >
> > My (long term) desire is to do away with /lib32 and /lib64, ultimately
> > only
Peter,
On Monday, 2021-02-15 12:15:43 +, you wrote:
> ...
> No, it should be arch-neutral. Agnosticism is about religion and has nothing
> to do with it.
First sentence: arch-independent?
Second sentence: yep :-)
Sincerely,
Rainer
On Sunday, 14 February 2021 21:48:36 GMT Frank Steinmetzger wrote:
> Am Sun, Feb 14, 2021 at 12:51:30PM -0500 schrieb Jack:
> > As I remember, /lib and /usr/lib hold not only 32 bit libraries, but
> > non-arch or arch-irrelevant (I know there's a better term) files.
>
> arch-agnostic? ;-)
No, it
On Sun, Feb 14, 2021 at 06:09:58PM -0700, Grant Taylor wrote
> On 2/14/21 10:51 AM, Jack wrote:
> > I don't think you can completely get rid of it.
>
> My (long term) desire is to do away with /lib32 and /lib64, ultimately
> only using /lib. Likewise for the other library directories in /usr or
12 matches
Mail list logo
