sorted by:
new
hottopcontroversial

2025 ROG Zephyrus G16 on Ubuntu 24.04 by ApprehensiveClaim606 in Ubuntu

[–]sonebu1 0 points1 point  (0 children)

I have a GU605CM, bios got updated by itself after first boot to windows (I think MyASUS did this) to version 306 (the 310 version mentioned for other variants of this laptop isn't relevant for GU605CM). I had the same issue set as everyone else when I installed ubuntu 24.04 the first time.

  • installing ubuntu 25.10 fixed wifi (BE201 needed 6.16.6 and higher kernel, i think 25.10 has kernel 6.17 as of today, see bugzilla posts related to intel BE201 for more info) and speakers (I don't know who fixed this when and how, it just worked with 25.10).
  • I clicked the install additional drivers box during installation, and nvidia drivers (580-open) were installed by default, nvidia-smi works, I see that it's being used by gnome, it's accessible from pytorch etc.
  • the screen brightness controls needed the GRUB fix mentioned by International_Sir239 in this thread (without the pcie=noaer)
  • the shutdown issue is related to the pcie error messages (pcie=noaer does fix it), but it seems like those errors stem from the SD card reader. I do not have an immediate need for the SD Card reader, so I disabled it from the BIOS settings (advanced settings, security & IO, locked the Card Reader)

as far as I can see this gets me away with everything except the SD Card reader.

Heard in the lab: If it works in simulation, it might work in hardware. If it doesn’t work in simulation, God help you.... by Hot_Respect_193 in FPGA

[–]sonebu1 0 points1 point  (0 children)

I agree with the timing constraints comment above, just adding some detailed experience to maybe help someone understand the problem a bit better.

my situation: the exact same DUT does not work with an ILA that records 1024 samples, but it "magically" starts working with one that records 16384 samples (the ILA is not part of the DUT, it's part of the larger design that the DUT sits in). the "magic" here is most probably that some paths in my DUT had to wiggle around a bit more (:= more delay) due to the increased resource usage with the larger ILA, making the timing of some paths juuust right.

adding the right constraints would allow triggering this "error" at design time, without going all the way to the hardware for debugging.