On 8/18/24 7:40 AM, Frank Bures wrote:
On 2024-08-18 09:10, François Patte wrote:
Bonjour,
I installed f40 with raid1 partitions.
Every sunday an automatic program resync the partitions and a lot of
programs "pedal in the sauerkraut" (french idiom) because of this
automatic resync...
I hav
Tim:
> > I've never come across a charge-only cable. I understand why someone
> > would use one (e.g. public charging), but I thought some use of the
> > data pins was necessary to switch from lower power mode.
> >
> > If you keep unusual cables, label them. It'll save you from some
> > headache
On 2024-08-18 09:10, François Patte wrote:
Bonjour,
I installed f40 with raid1 partitions.
Every sunday an automatic program resync the partitions and a lot of
programs "pedal in the sauerkraut" (french idiom) because of this automatic
resync...
I have looked in cron.d directory, cron.weekl
Hi.
On Sun, 18 Aug 2024 14:59:09 +0200 François Patte wrote:
> Le 2024-08-17 06:07, Robert McBroom via users a écrit:
>> The 6.10.x kernels are not yet supported for nvidia.
I checked past friday with the 6.10.4-200.fc40 kernel and the 4
drivers provided by rpmfusion.
akmods succeded to compil
Bonjour,
I installed f40 with raid1 partitions.
Every sunday an automatic program resync the partitions and a lot of
programs "pedal in the sauerkraut" (french idiom) because of this
automatic resync...
I have looked in cron.d directory, cron.weekly, and other cron program
in order to disab
Le 2024-08-17 06:07, Robert McBroom via users a écrit :
On 8/16/24 10:32 AM, François Patte wrote:
Bonjour,
Yesterday I updated my fc40 installation. I have an nvidia GPU with
nvidia driver from rpm-fusion.
I think that the akmod compilation of the driver went wrong and I
could not boot unt
On 17/08/2024 17:48, Tim via users wrote:
On Sat, 2024-08-17 at 16:08 +0700, Frederic Muller wrote:
Obviously I was using one of those non-data capable cable and no data
was going through that port.
I've never come across a charge-only cable. I understand why someone
would use one (e.g. public
I don't know specifically on this bug. But the 2 common mistakes fall
into some piece failing and causing dracut to not properly detect what
modules the boot device needs to use. And when that happens dracut
times out looking for root. I have also seen bugs where the
necessary module needed to
Hi,
I had changed from Fedora to openSUSE due to an error on LUKS during
boot (it would not see the correct devices, dracut would timeout). I
could boot using an older kernel but couldn't figure out what the
issue was/hadn't had the patience.
Yesterday it happened on openSUSE and, in that case, no
