public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Wol <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Do I need firmware for an integrated graphics unit?
Date: Fri, 23 Aug 2024 10:42:54 +0100	[thread overview]
Message-ID: <899c8f36-f77b-4678-a74c-37c36f174fba@youngman.org.uk> (raw)
In-Reply-To: <ZsdpQtcQhtSJ5x4z@ACM>

On 22/08/2024 17:37, Alan Mackenzie wrote:
> Yes, 6.6.47 has become the new stable Gentoo kernel, and I've now
> updated my old machine, and this worked without problem.  This was
> mainly to test that nothing RAID-wise had gone missing in the kernel.
> It hadn't

What version of mdraid? 0.97? or 1.x?

0.97 is in-kernel, and deprecated - as in "if it ain't broke, don't fix 
it. If it is broke, it's not supported". I think there are a fair few 
people who depend on it, though, so it tends to get fixed if something 
goes wrong.

1.x is assembled in user space, so there are probably races with other 
stuff in user space for completion. I run a somewhat messy boot stack, 
but iirc my root space is just "rust, mdraid, lvm, root partition", and 
it works just fine. But I do run systemd, and I might have had to make 
sure there's something in the boot stack waiting for each bit to 
complete in order.

My /home stack has dm-integrity between rust and raid, and boy did that 
really cause some grief getting that to behave. But that makes sure that 
my raid-5 never sees a corrupt read, so I can recover from a damaged 
disk as well as a lost disk.

I - allegedly - know about raid :-) , so if you give me a bit more info 
I might be able to help. Or I might not ...

Cheers,
Wol


  parent reply	other threads:[~2024-08-23  9:43 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-20 20:05 [gentoo-user] Do I need firmware for an integrated graphics unit? Alan Mackenzie
2024-08-20 21:16 ` Peter Böhm
2024-08-21 10:32   ` Wol
2024-08-21 10:59     ` Alan Mackenzie
2024-08-21 13:03       ` [gentoo-user] " Grant Edwards
2024-08-21 11:15   ` [gentoo-user] " Alan Mackenzie
2024-08-21 11:37     ` Michael
2024-08-21 12:04       ` Alan Mackenzie
2024-08-21 13:49         ` Michael
2024-08-21 15:22           ` Wol
2024-08-21 15:47             ` Peter Humphrey
2024-08-21 15:49             ` [gentoo-user] " Grant Edwards
2024-08-21 14:43       ` Grant Edwards
2024-08-21 12:03     ` [gentoo-user] " Peter Böhm
2024-08-21 17:26       ` Alan Mackenzie
2024-08-21 18:10         ` Peter Böhm
2024-08-22 11:57           ` Alan Mackenzie
2024-08-22 14:46             ` Peter Humphrey
2024-08-22 15:05               ` Michael
2024-08-22 16:37                 ` Alan Mackenzie
2024-08-22 23:22                   ` Peter Humphrey
2024-08-23  9:42                   ` Wol [this message]
2024-08-23 16:41                     ` Alan Mackenzie
2024-08-21  0:30 ` [gentoo-user] " Grant Edwards
2024-08-21 11:39   ` Alan Mackenzie
2024-08-21 11:54     ` Michael
2024-08-21 13:02     ` Grant Edwards
2024-08-23 16:28       ` Alan Mackenzie
2024-08-23 21:28         ` Grant Edwards
2024-08-22  0:34 ` [gentoo-user] " corbin bird
2024-08-22  8:28   ` Michael

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=899c8f36-f77b-4678-a74c-37c36f174fba@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox