Jump to content

SilverSoul

Member
  • Posts

    58
  • Joined

  • Last visited

Everything posted by SilverSoul

  1. I think you're being unfair. openGL is used everywhere on Linux, and making use of NVIDIA's drivers do cause performance issues/bugs. Just because you aren't particularly affected/haven't run into the bugs doesn't mean you get to deny that they exist. Performance is also subpar compared to what it can be and that is the problem, I don't see what's the issue with NVIDIA improving their openGL implementation. EDIT: I'm not trying to give NVIDIA flack for no reason, they do plenty of cool stuff (CUDA is amazing and my main computer is running on a 2070 super). I just want their driver to get better, it's pretty hard to recommend NVIDIA's cards when someone asks me why their compositor isn't behaving properly, or why chrome can't push more than 60fps on Linux. People care about these issues and the sooner NVIDIA sorts them out the better it will be for everyone.
  2. Nvidia's openGL implementation isn't as good as it can be. There is a lot of room for improvement there. Linux uses openGL a lot so it's a very important metric to judge driver quality. Sure the driver "works" but that's about it. It works but it's not as good as it should be. I think that the decision to not implement hardware decoding for videos on web browsers was due to the linux graphics being bad a "few" years ago (could be wrong on this).
  3. @10leejHe definitely uses Linux to some capacity, either way that's not the point I'm trying to make. He also uses macOS and windows. There is nothing wrong with that but it just kinda makes it feel like the script was written by an outsider's perspective (or may contain errors due to him not having enough experience with it). I also agree on the fact that if they want to do it properly they should hire someone else who is more like the other Linux content creators. Anthony couldmake a great cohost though. It's highly unlikely that Linus saw this post, and it's even more unlikely that they do create a Linux channel anyways.
  4. Just going to @ you so that I can get your attention. @LinusTech I want to start this off by saying that I've been a subscriber since around 2012 and that I absolutely adore you guys, I hope that you guys don't take this the wrong way and look at this post as just "feedback for your Linux videos". You guys recently started a channel dedicated to mac users in general, and hired a new staff member who loves macOS and uses it daily. This made me think back to the Linux videos you uploaded a while ago, and while they got better with time, they still had a lot of issues. The Linux videos felt like they were coming from someone who doesn't use Linux daily and some of the information in it was horrible. It honestly felt like I was reading r/linux_gaming which generally has a lot of bad advice, as a lot of the users there are generally new (of course it has good advice too). An example of something that really bothered me was something that sounded a bit like the following: "The NVIDIA blob is not bad, it's just not open source". As someone who has used Linux for 10+ years and is a developer, I assure you that you should avoid the NVIDIA driver like the plague and you SHOULDN'T be recommending it to new users. The reason why I say this is that the NVIDIA driver probably shares most of it's code base with it's windows driver, and it doesn't implement a lot of the Linux specific APIs or even some openGL extensions (or it implements it badly). It may for example make use of busy waiting (causing way higher CPU usage when using something like glFinish), or not support an extension that is used to find the refresh rate of the display (chrome on linux is stuck at 60fps due to this). NVIDIA on Linux generally seems to be less of a priority for all developers, and that includes huge projects like Firefox and Chrome. I don't want to ramble for too long about the other issues in the Linux videos because I feel like the paragraph above drives the point home, it feels like the advice was given by someone who doesn't use Linux that often. In general there is a lot horrible advice on the internet, and Linux is not immune to this. It also can be somewhat difficult to find a good source of information when you don't know where to look. I'm glad that the Linux content is generally well received by the LTT viewer-base. But I still think it's important to give good advice (similar to the quality of stuff you guys put out for other things). I love that you guys have started to cover Linux a bit more and hope to see you guys continue to improve and possibly bring a Linux person on board in the future.
  5. The guy who suggested alpine is right. It's compiled with musl libc and is probably your best bet. If you want your boot time to be ssd like then get a ssd.
  6. https://www.kernel.org/doc/html/latest/sound/designs/powersave.html
  7. Distros don't matter that much, only thing that differs is if one's a rolling release vs fixed most of the time. Some tools like package managers are also slightly different. Pick whichever you want.
  8. To keep things short: Much better CPU / IO schedulers. Better filesystem choices. Package management. Lighter footprint. Plethora of DEs and WMs. Ability to patch things yourself. Documentation. No need to treat stuff like a black box anymore. Deploying to a platform you run is easier. No reboots required between updates! Kernel can livepatch. One can also load kernel modules at will. Systemd unit files / crontab comes in really useful to automate the boring stuff out of your life!
  9. i3-gaps and I check out sway from time to time to see if I it's good enough.
  10. People get so butthurt when someone says something bad about the OS their using. Just because you like IOS doesn't mean that the rest of the planet has to agree with you. It suits your use case not everyone on the planet.
  11. Do you have a nvidia card by any chance? Telling us what you're trying to install Linux on would help.
  12. OpenGL is depreciated. it wasn't being updated properly anyways so you might as well avoid gaming on MacOS, otherwise you would be in for a bad time. If you want to play games just run them under Windows or Linux, you can easily dual boot and leave MacOS for "work".
  13. Macs have subpar Linux support, don't grab one with the intention to run Linux because it's not worth the hassle. You should get it if it's free though, just don't run Linux on it.
  14. It's likely converting your filesystem to APFS every time you install it. The real question is why would you use HFS+ when it's one of the worst filesystems on the planet? Unless you're running something with a heavy write workload (like mongoDB, which you should run on a server) then you should be on APFS. I'd argue it's even worth running it on a hard drive because of how bad HFS+ is.
  15. There should be a fallback driver that works on most hardware, Nvidia cards can run but just extremely slowly and with issues. I don't think even Apple is stupid enough to not have a fallback driver (but maybe they are who knows? They always pull the stupidest shit). This is a direct quote from Nvidia:
  16. MacOS does have graphics drivers you just don't need to download them yourself, most of the time. Also unless the drivers provided by Apple are under performing, there should be no reason to switch. If they are slow, just dual boot another OS or something until Apple and Nvidia stop fighting.
  17. Please be more specific, and only post what happens in a distro with a newer kernel. Also blacklist the AMDGPU kernel module for now with module_blacklist=amdgpu.
  18. they are very similar in syntax, but learn 3
  19. Firstly I have a few questions/comments of my own: Can you please show us your mountpoints? Windows is not installed on a ext4 partition, it's on the NTFS one you formatted (oops?) You need to reinstall GRUB: chroot into your system from a live USB. mount both the Linux partition to /mnt and the boot partition to /mnt/boot reinstall GRUB. if you don't know how to install grub for UEFI then use the command below. Keep in mind that --efi-directory is the refers to the directory holding the EFI directory. So in the command below it will install GRUB to /Boot/EFI and not /Boot. Make sure you have the os-prober package installed. install-grub --bootloader-id=Grub-Fixed --efi-directory=/Boot --target=x86_64-efi Once you fix GRUB you can add a menu entry to boot into Android. EDIT: The proper way to fix this is to refresh your grub configuration or check the grub.cfg file yourself, but a reinstall will be fine.
  20. Wayland DEs tend to have better DPI scaling than X11 (supports setting the DPI per monitor). So I would recommend that instead of the "hacky" X11 fixes.
  21. I think he's referring to where your boot partition is stored, if you run: sudo fdisk -l you will find a small EFI partition, tell the system to mount the partition on /boot by editing the fstab file. Also did you check your BIOS's boot order? If GRUB is not detected by your BIOS then it has nothing to do with the fstab file. You need to reinstall GRUB.
  22. I didn't know people live in houses that were constrained to the point where a laptop's thickness made a difference, I think you need to get a new place ?
  23. People are angry that it does more than what a "normal" init system is supposed to do. I see no problem with it as it's not exactly bloated.
  24. Not sure about this, But I think the driver in the ubuntu repo seems to be out-dated? Compile it yourself (on another computer or the same one) then load the module manually and it should work.
×