u/Head_Artichoke

Ciao a tutti, sto valutando l'acquisto di una casa e mi piacerebbe un parere da chi ha già affrontato una ristrutturazione simile.

Si tratta di una casa indipendente su due piani, circa 200 mq, degli anni '50. La struttura mi sembra sana, ma è chiaramente un immobile che ha bisogno di essere svecchiato.

Le cose che ho notato:

- Umidità di risalita, sia all'interno che sulle facciate esterne (aloni e intonaco che si sfoglia nella parte bassa dei muri, efflorescenze). Non so quanto sia impegnativo intervenire alla radice.

- Impianti datati (elettrico, idrico, riscaldamento con termosifoni), probabilmente originali o comunque vecchi.

Come primo blocco di lavori pensavo di rifare completamente i bagni e, se necessario, gli impianti, per partire da una base sana e sistemare il resto (intonaci, finiture) con più calma.

Le mie domande:

- Per l'umidità di risalita quali sono gli interventi tipici e, indicativamente, che ordine di spesa hanno? Vale la pena affrontarla subito o si può gestire nel tempo?

- Rifare impianti + bagni in una casa di queste dimensioni, a spanne, che cifre comporta? So che dipende da mille fattori, ma anche solo per farmi un'idea dell'ordine di grandezza.

Come vi conviene muovervi voi in questi casi: un unico intervento complessivo o step successivi?

L'idea è capire più o meno a quanto ammonta il "conto totale" oltre al prezzo d'acquisto, anche per usarlo nella trattativa.

Chi ha ristrutturato una casa vecchia di questo tipo: cosa vi ha sorpreso di più, e cosa avreste controllato prima di chiudere?

Grazie a chi vorrà rispondere 🙏

Hi all,

I want to flag something before driver 595 (open, MIT/GPL dual-license) becomes the default here, based on a side-by-side comparison I did between Pop!_OS 24.04 (proprietary 580) and Fedora 44 (nvidia-open 595, niri compositor).

The short version: when a game fills the VRAM completely, on Pop!_OS (proprietary 580) the desktop mostly survives — the kernel logs show the driver attempting a fallback to system memory. On Fedora with the open 595 driver, that fallback attempt never shows up in the logs at all, and the result is a hard freeze: the game locks on a still frame (audio/game logic keep running), and until I kill the game I can't even open GPU-accelerated apps like Kitty, and niri itself gets flaky.

Pop!_OS journal (proprietary 580, GPU fills up under load):

kernel: [drm] [nvidia-drm] [GPU ID 0x00002b00] Failed to allocate NVKMS video memory for GEM object, trying to fall back to sysmem
kernel: [drm] [nvidia-drm] [GPU ID 0x00002b00] Failed to allocate NVKMS video memory for GEM object, trying to fall back to sysmem
kernel: [drm] [nvidia-drm] [GPU ID 0x00002b00] Failed to allocate NVKMS video memory for GEM object, trying to fall back to sysmem
kernel: [drm] [nvidia-drm] [GPU ID 0x00002b00] Failed to allocate NVKMS video memory for GEM object, trying to fall back to sysmem
kernel: [drm:nv_drm_gem_alloc_nvkms_memory_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00002b00] Failed to allocate NVKMS memory for GEM object
kernel: [drm:nv_drm_gem_alloc_nvkms_memory_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00002b00] Failed to allocate NVKMS memory for GEM object

Note it does eventually hit the hard error too (last two lines), but it retries the sysmem fallback several times first and the system stays usable in between — no full freeze, no need to kill anything.

Fedora journal (nvidia-open 595, same GPU, same PC, same VRAM-heavy game):

kernel: [drm:nv_drm_gem_alloc_nvkms_memory_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00002b00] Failed to allocate NVKMS memory for GEM object

No "trying to fall back to sysmem" line ever appears — it just errors out directly, and the freeze doesn't clear until I close the game (running it inside gamescope keeps the game itself alive, but then niri or other GPU apps get stuck instead).

One more data point: checking the driver's registry/module params, the proprietary build on Pop!_OS shows EnableSystemMemoryPools: "", while on Fedora's nvidia-open build that same parameter is set to "529". That lines up pretty well with what the logs show — it looks like the sysmem-pool fallback path may not be wired up (or not enabled by default) on the open kernel module build, at least on 595.

This isn't a Fedora- or niri-specific bug as€” NVIDIA's Linux driver has a long history of not spilling to system RAM the way it does on Windows or the way AMD/Intel do on Linux, and there's an open forum thread from a few weeks ago describing basically the same freeze on nvidia-open-dkms + Niri specifically. But the fact that the proprietary driver on Pop clearly attempts (and mostly succeeds at) a sysmem fallback, while the open one on Fedora doesn't even try, makes me worried the same regression will show up here once #2 (nvidia-graphics-drivers-595) ships as the default.

EDIT: the same issue happened when I tried Cachy OS a month ago with nvidia 610. At that time I tried both Niri and Cosmic and the problem occurs on both DE (both based on smithay so it is somehow expected).

What I'd love feedback on:

• Has anyone on the team already tested nvidia-open (not proprietary) 595/610 under real VRAM pressure on Pop, to see if the "trying to fall back to sysmem" line still shows up?
• Does anyone know if EnableSystemMemoryPools (or an equivalent) is something Pop's packaging sets explicitly, or if it's purely upstream NVIDIA behavior we're at the mercy of?
• If this does reproduce, is proprietary staying available as a fallback option, or is the plan to fully move to nvidia-open going forward?

Not trying to be alarmist — just didn't want this to slip through unnoticed given how disruptive a hard freeze is compared to a graceful (if slower) sysmem fallback. Happy to share the full nvidia-bug-report.log.gz from both machines if that's useful for testing.

Thanks!

Hello guys,

Topic: bootc, ostree, Anaconda, Linux dual booting

I'm new in the world of Atomic distro even if I am a long Linux user (about 10 years but I've only used debian/Ubuntu based distros).

I now want to move to an atomic distro based on fedora (I'm thinking of maintaining my own private spin to keep track of what is installed and what not) anyway I already have a working spin and iso build and everything works as a starting point at least on VM.

The problem now is that I want to dual boot it on my main workstation without losing my actual pop os installation but I read different opinions about installing an atomic distro alongside another Linux distro on the same drive.

Unfortunately I can't afford another drive because they cost too much in this period so I can only dual boot on the same drive.

What do you suggest? Mo actual partition layout (pop os default) is

EFI Recovery Pop OS Root (about 900 GB). Swap

Ideally I would split the root one reserving about 400 GB to the atomic distro. But how? I even read that I may create another EFI partition and select it from the bios boot menu to not interfere with the pop os one and I don't see any issue with that if it is possible.

So it means that I should create A new EFI 1 GB partition, a 2 GB boot partition (for GRUB (?)) and the remaining 400 GB for btrfs root.

Is that right? Hope someone more expert then me can give me some ideas. Thank you very much!

Hello guys,

Topic: bootc, ostree, Anaconda, Linux dual booting

I'm new in the world of Atomic distro even if I am a long Linux user (about 10 years but I've only used debian/Ubuntu based distros).

I now want to move to an atomic distro based on fedora (I'm thinking of maintaining my own private spin to keep track of what is installed and what not) anyway I already have a working spin and iso build and everything works as a starting point at least on VM.

The problem now is that I want to dual boot it on my main workstation without losing my actual pop os installation but I read different opinions about installing an atomic distro alongside another Linux distro on the same drive.

Unfortunately I can't afford another drive because they cost too much in this period so I can only dual boot on the same drive.

What do you suggest? Mo actual partition layout (pop os default) is

EFI Recovery Pop OS Root (about 900 GB). Swap

Ideally I would split the root one reserving about 400 GB to the atomic distro. But how? I even read that I may create another EFI partition and select it from the bios boot menu to not interfere with the pop os one and I don't see any issue with that if it is possible.

So it means that I should create A new EFI 1 GB partition, a 2 GB boot partition (for GRUB (?)) and the remaining 400 GB for btrfs root.

Is that right? Hope someone more expert then me can give me some ideas. Thank you very much!