4 ms·

This is a poor rant. You never managed to change the terminal in grub? You couldn't change the background in KDE? These are PICNIC problems. It seems like you'r

by powmonk 10y ago

This is a poor rant. You never managed to change the terminal in grub? You couldn't change the background in KDE? These are PICNIC problems. It seems like you're frustrated about a lot of things, which is understandable, linux desktop is very far from perfect. You're also sticking with a distro that's essentially for enterprise server use. Throw that in with a few questionable practices (30 terminals windows?) then yes, I can see why you're not very happy. It seems like you're just taking out _your_ frustration on the linux desktop experience. I finally binned off windows in the last bastion it had in my personal life about 6 months ago (laptop) and it's been great. YMMV.

heeen2 10y ago
with nvidia you can have either but not both of: * proper resolution grub * proprietary (fast, feature complete) drivers due to the nvidia drivers not supporting fbdev properly (AFAIK). also you should see how slowly grub draws its menu on 4k resolution. My whole system is booted half way in that time.
- anonbanker 10y ago
  And this is the Linux Kernel's fault, or Nvidia's lousy drivers?
  - otterley 10y ago
    What difference does it make whose fault it is?
    - anonbanker 10y ago
      So, by that logic, when AMD/ATI's notoriously buggy drivers were failing in windows, you blamed NTOSKRNL and Windows? I guess I'm looking for consistency in the argument the great-grandparent was making.
      - pwinnski 10y ago
        For most Mac users, there's a kind of consistency: It doesn't matter whether the drivers or the kernel are to blame; either way, avoiding Windows means avoiding the whole mess.
      - otterley 10y ago
        Read it as "the Linux experience as a desktop user," and not "the Linux kernel."
        anonbanker 10y ago
        classy late downvote/reply/moving goalposts combo. Post was at +2 before your reply. either way, you're proving the inconsistency. ATI drivers for windows suck, but you don't blame windows. NVidia drivers suck in Linux (to the point that Linus Torvalds says "Fuck you NVidia", creating news headlines), and you blame Linux.
- djfm 10y ago
  And I guess of course "proper resolution grub" is of paramount importance given the time you spend inside grub every day.
  - elpocko 10y ago
    At least on my system, the Linux terminal is displayed in the resolution set by grub on boot.
- ac29 10y ago
  My only Linux computer that uses grub uses the Nvidia proprietary driver and boots grub in the monitor's native resolution. GRUB is using it's default config, I didn't hardcode any resolutions or anything. Whatever your issue is, its not caused by Grub or Nvidia's binary drivers.
Jonathanks 10y ago
I used Windows in 2015 (I never used it as my primary OS for more than a year) alongside some Linux distros (Ubuntu, Fedora, Debian, Slackware and a few others). I finally settled for Debian, at least for now. Whenever I need to do something with Windows, I just fire up VirtualBox and it's working well so far. I miss games on Windows and I'm not aware of anything comparable (without SteamOS) on Debian.

by powmonk 10y ago

heeen2 10y ago

with nvidia you can have either but not both of: * proper resolution grub * proprietary (fast, feature complete) drivers due to the nvidia drivers not supporting fbdev properly (AFAIK). also you should see how slowly grub draws its menu on 4k resolution. My whole system is booted half way in that time.

anonbanker 10y ago
And this is the Linux Kernel's fault, or Nvidia's lousy drivers?
- otterley 10y ago
  What difference does it make whose fault it is?
  - anonbanker 10y ago
    So, by that logic, when AMD/ATI's notoriously buggy drivers were failing in windows, you blamed NTOSKRNL and Windows? I guess I'm looking for consistency in the argument the great-grandparent was making.
    - pwinnski 10y ago
      For most Mac users, there's a kind of consistency: It doesn't matter whether the drivers or the kernel are to blame; either way, avoiding Windows means avoiding the whole mess.
    - otterley 10y ago
      Read it as "the Linux experience as a desktop user," and not "the Linux kernel."
      - anonbanker 10y ago
        classy late downvote/reply/moving goalposts combo. Post was at +2 before your reply. either way, you're proving the inconsistency. ATI drivers for windows suck, but you don't blame windows. NVidia drivers suck in Linux (to the point that Linus Torvalds says "Fuck you NVidia", creating news headlines), and you blame Linux.
djfm 10y ago
And I guess of course "proper resolution grub" is of paramount importance given the time you spend inside grub every day.
- elpocko 10y ago
  At least on my system, the Linux terminal is displayed in the resolution set by grub on boot.
ac29 10y ago
My only Linux computer that uses grub uses the Nvidia proprietary driver and boots grub in the monitor's native resolution. GRUB is using it's default config, I didn't hardcode any resolutions or anything. Whatever your issue is, its not caused by Grub or Nvidia's binary drivers.

Jonathanks 10y ago

I used Windows in 2015 (I never used it as my primary OS for more than a year) alongside some Linux distros (Ubuntu, Fedora, Debian, Slackware and a few others). I finally settled for Debian, at least for now. Whenever I need to do something with Windows, I just fire up VirtualBox and it's working well so far. I miss games on Windows and I'm not aware of anything comparable (without SteamOS) on Debian.