Michael wrote:
> On Sunday, 29 October 2023 10:40:19 GMT Neil Bothwick wrote:
>> On Sun, 29 Oct 2023 03:16:05 -0500, Dale wrote:
>>> I have several external hard drives. I have one that is, weird. Others
>>> work fine. When I first power up the drive, cryptsetup can't open it
>>> because it
On 29/10/2023 14:28, Dale wrote:
I don't see anything different between the two types of enclosures
except I have to restart LVM with one of them. Weird for sure.
Well, on the linux raid wiki I explicitly tell people not to use USB
drives for raid. "We don't know why, but it seems guaranteed
On 22/10/2023 09:50, Dale wrote:
I've read about using rsync as a daemon. It is supposed to be faster.
For some reason, I just never got around to trying it. It would likely
be a good idea to work on that. It would likely be really handy when
moving large amounts of data. I may try to read
netfab wrote:
>
> Have a look at ¹ to see if it matches your case.
> Please try the workaround suggested in comment 4 (set CPU_FLAGS_X86
> and re-emerge ffmpeg). Does it help ?
> 1. https://bugs.gentoo.org/915384
Yes, it helped. I have provided some more information in
that bug report. (Of
Neil Bothwick wrote:
> On Sun, 29 Oct 2023 03:16:05 -0500, Dale wrote:
>
>> I have several external hard drives. I have one that is, weird. Others
>> work fine. When I first power up the drive, cryptsetup can't open it
>> because it doesn't exist yet.
> Is it the drive/enclosure taking too long
On Sunday, 29 October 2023 10:40:19 GMT Neil Bothwick wrote:
> On Sun, 29 Oct 2023 03:16:05 -0500, Dale wrote:
> > I have several external hard drives. I have one that is, weird. Others
> > work fine. When I first power up the drive, cryptsetup can't open it
> > because it doesn't exist yet.
>
On 19/10/2023 12:55, Neil Bothwick wrote:
On Wed, 18 Oct 2023 23:49:25 -0500, Dale wrote:
That config kinda reminds me of the old grub. A title line, location of
kernel and then options. Sounds easy enough. The new grub config is
almost impossible to config by hand. They had to make a tool
Hi,
Le 29/10/23 à 11:29, Matthias Hanft a tapoté :
> I don't have anything special in /etc/portage/make.conf - just
> as usual:
>
> CFLAGS="-march=native -O2 -pipe"
> CXXFLAGS="${CFLAGS}"
> MAKEOPTS="-j2"
> CHOST="x86_64-pc-linux-gnu"
>
> Any hints?
Have a look at ¹ to see if it matches
On Sun, 29 Oct 2023 03:16:05 -0500, Dale wrote:
> I have several external hard drives. I have one that is, weird. Others
> work fine. When I first power up the drive, cryptsetup can't open it
> because it doesn't exist yet.
Is it the drive/enclosure taking too long to power up? There are
Hi,
after compiling ffmpeg (which includes libavcodec) with gcc 13,
everything which uses libavcodec crashes with general protection
fault. This includes stand-alone use of ffmpeg, but also
minidlna (and supposedly some more packages).
Oct 29 11:16:08 home01 kernel: traps: minidlnad[11961]
Howdy,
I have several external hard drives. I have one that is, weird. Others
work fine. When I first power up the drive, cryptsetup can't open it
because it doesn't exist yet. This is the relevant part of lsblk -f
when it doesn't work:
NAME FSTYPE FSVER LABEL
11 matches
Mail list logo
