Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)SE
Posts
9
Comments
251
Joined
2 yr. ago

  • I have personally not seen a big hit to my battery life since I started using voyager a month ago. I haven't looked at at individual app battery usage but the screen on time is similar to before and voyager is one of my most used apps.

  • I have the same thought about the price in India. Just ₹200 for the ad free option seems lower than he needs to be. He can increase the price by 50-100% and be low enough that people who were ready to buy at ₹200 will still buy it

  • ....

    Jump
  • this may not be what you have in mind when you said no but this does offer some level of customization of the install. Yes arch is much more configurable during install though

  • ....

    Jump
  • Is there any noticeable difference between endeavourOS and arch after install¿? From what I have heard and in my limited time using arch or endeavourOS, post install, things seem more or less the same.

  • I have the a wifi card from the MT7921 family as well in my MSI laptop and from what I can gather, the issue seems to the power ASPM state that the wifi card is in. This is especially a problem when rebooting your laptop as the card is in unexpected/wrong (for a lack of a better word) power ASPM state during boot up and hence the mt7921e kernel module fails to run. Fastboot also contributes to this so disable that if that is enabled.

    The engineer from mediatek who is responsible for the mt7921 and associated modules was aware of the first issue and has submitted several patches to fix the issue. The most recent seems to have it becuase I dont face this problem anymore. I will link the thread where this issue was discussed if I find it.

    Edit - GitHub thread discussing issue

    Mediatek engineer describing what the issue may have been

  • I am stumped. How can steam/the system exhibit different behaviour when we are executing similar commands. Maybe it is because I have an amd+amd laptop so it automatically dumps the graphically intensive application to the dGPU. Or maybe because in a desktop, the dGPU is connected directly to the display, it not switching to the dGPU automatically as the user had specified the use of the iGPU. In my laptop(which has no mux switch), the iGPU will draw the frame on the screen even if it the dGPU which determines what is to be drawn

  • Odd. I am guessing that use integrated graphics option from the Gnome DE forces the use of the iGPU for everything steam launches. Do you also require to use the DRI_PRIME=1 command if you launch steam through the terminal in which case it automatically switches to the iGPU for the steam client because I sure did not when I was launching steam from the terminal to circumnagivate the issue

    I used the workarounds mentioned in this post's comments to resolve the issue https://lemmy.one/post/151466. With this workaround there no need to use the DRI_PRIME=1 modifier for the games(atleast in my experience)

    Edit : does somebody know to link the post in a way such that it opens within the app you are currently using(voyager for me) and does not open a new lemmy.one tab in the browser

  • and then add DRI_PRIME=1 to the command options of the games you want to use your external GPU.

    No you don't need to do this. The games will use the dGPU automatically. Only the steam client uses the iGPU

  • So if you want to use it for gaming and have and AMD or Intel GPU and not an NVidia one, you'll have to stick to Ubuntu's outdated Mesa and kernel drivers.

    This is not true. Pop OS packages its own kernel and often the kernel version provided by pop is upstream of the Ubuntu version. It is only recently that they have fallen behind ubuntu because they have diverted their resources to creating the Cosmic DE.

    Edit : Also to be noted is the fact that being on the latest version of mesa is only necessary if you have very new hardware which may not be supported well(or at all) in the older versions of mesa. I for example have an RDNA1 gpu and saw no performance difference between mesa 22.5 on pop os and mesa 23.1 on endeavourOS. People using RDNA3 or Intel Arc may see massive performance/stability difference because these are very new hardware and drivers/optimisation for these current gen GPUs is ongoing