• 13 Posts
  • 29 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle
  • The unfortunate reality is that some people will buy anything that expires, on the remote chance someone might be interested. If they’re set on doing that there’s nothing you can do, they will grab it and block it for at least one more year.

    IMHO the best thing you can do is nothing. I mean nothing beyond discreetly checking the domain state in whois. Don’t inquire explicitly about the domain. Don’t use the WHOIS form on websites you don’t trust to exploit such queries into grabbing domains themselves.

    You can use whois from the command line (best way). Alternatively, the TLD registry will have a WHOIS form on their official website.

    If you don’t generate any apparent interest they will eventually let the domain lapse. Check back a year from now.


  • lemmyvore@feddit.nltoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    14
    ·
    7 months ago

    Things like desktop automation, screen sharing, screen recording, remote desktop etc. are incredibly broken, with no hope in sight because the core design of Wayland simply didn’t account for them(!?), apparently.

    Add to that the decision to push everything downstream into compositors, which led to widespread feature fragmentation and duplicated effort.

    Add to that antagonizing the largest graphics chipset manufacturer (by usage among Linux desktop users) for no good reason. Nvidia has never had an incentive to cater to the Linux desktop, so Linux desktop users sending them bad vibes is… neither here nor there. It certainly won’t make them move faster.

    Add to that the million little bugs that crop up when you try to use Wayland with any of the desktop apps whose developers aren’t snorting the Koolaid and not dedicating oustanding effort to catching up to Wayland – which is most of them.

    people dont like change

    I cannot use Wayland.

    I’m an average Linux desktop user, who has an Nvidia card, has no need for Wayland “security”, doesn’t have multiple monitors with different refresh rates, uses desktop automation, screen sharing, screen recording, remote desktop on a daily basis, and uses lots of apps which don’t work perfectly with Wayland.

    …how and why would I subject myself to it? I’d have to be a masochist.


  • lemmyvore@feddit.nlOPtoLinux@lemmy.mlCPU errors?
    link
    fedilink
    English
    arrow-up
    3
    ·
    8 months ago

    Honestly I’ll just send it back at this point. I have kernel panics that point to at least two of the cores being bad. Which would explain the sporadic nature of the errors. Also why memcheck ran fine because it only uses the first core by default. Too bad I haven’t thought about it when running memtest because it lets you select cores explicitly.




  • lemmyvore@feddit.nlOPtoLinux@lemmy.mlCPU errors?
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    8 months ago

    This sounds like my best shot, thank you.

    I’ve installed the amd-ucode package. It already adds microcode to the HOOKS array in /etc/mkinitcpio.conf and runs mkinitcpio -P but I’ve moved microcode before autodetect so it bundles code for all CPUs not just for the current one (to have it ready when I swap) and re-ran mkinitcpio -P. Also had to re-run grub-mkconfig -o /boot/grub/grub.cfg.

    I’ve seen the message “Early uncompressed CPIO image generation successful” pass by, and lsinitcpio --early /boot/initramfs-6.12-x86_64.img|grep micro shows kernel/x86/microcode/AuthenticAMD.bin, there’s a /boot/amd-ucode.img, and an initrd parameter for it in grub.cfg. I’ve also confirmed that /usr/lib/firmware/amd-ucode/README lists an update for that new CPU (and for the current one, speaking of which).

    Now from what I understand all I have to do is reboot and the early stage will apply the update?

    Any idea what it looks like when it applies the microcode? Will it appear in dmesg after boot or is it something that happens too early in the boot process?



  • lemmyvore@feddit.nlOPtoLinux@lemmy.mlCPU errors?
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    8 months ago

    All hardware is the same, I’m trying to upgrade from a Ryzen 3100 so everything should be compatible. Both old and new CPU have a 65W TDP.

    I’m on Manjaro, everything is up to date, kernel is 6.12.17.

    Memory runs at 2133 MHz, same as for the other CPU. I usually don’t tweak BIOS much if at all from the default settings, just change the boot drive and stuff like “don’t show full logo at startup”.

    I’ve add some voltage readings in the post and answered some other posts here.





  • lemmyvore@feddit.nlOPtoLinux@lemmy.mlCPU errors?
    link
    fedilink
    English
    arrow-up
    2
    ·
    8 months ago

    Motherboard is a Gigabyte B450 Aorus M. It’s fully updated and support for this particular CPU is explicitly listed in a past revision of the mobo firmware.

    Manual doesn’t list any specific CPU settings but their website says stepping A0, and that’s what the defaults were setting. Also I got “core speed: 400 MHz”, “multiplier: x 4.0 (14-36)”.

    even some normal batch cpus might sometimes require a bit more (or less) juice or a system tweak

    What does that involve? I wouldn’t know where to begin changing voltages or other parameters. I suspect I shouldn’t just faff about in the BIOS and hope for the best. :/





  • Wow, basically everything you wrote about Manjaro was wrong:

    • It doesn’t need constant maintenance, and it doesn’t break. The whole point of it is to be a stable variation of Arch.
    • It doesn’t have a highly irregular update schedule, it’s quite regular — every two weeks. There are also updates for outstanding security issues which can come faster (as needed). Occasionally very large updates can take longer in order to weed out all the issues, such as the recent example with Plasma 6 — those are announced in advance.
    • AUR doesn’t “expect” anything, it’s a dumping ground where anybody can put anything. I successfully run about 100 AUR packages on Manjaro without any issues, but nobody can guarantee anything when it comes to AUR. It’s officially unsupported on Arch and every Arch-based distro. If you want to call it dangerous that’s fine (if a bit hyperbolic) but don’t blame that on Manjaro, it just shows that you don’t understand how AUR works.







  • Only the Tailscale pairing server is proprietary but there’s a FOSS self-hostable alternative called Headscale.

    The Tailscale clients are FOSS.

    There isn’t much of a guide, you install the Tailscale clients and make an account on their website. After you enroll your devices to the account with a code they’ll be able to access each other via private IPs on an encrypted network based on WireGuard.

    You can connect among devices with unsecured protocols like VNC because they’ll be inside the encrypted network. And this works with any app and any protocol not just remote desktop — you can use Syncthing, access files, access any services you want securely etc.