Hacker News Reader

HNHacker News

Top New Best Ask Show Jobs

Comment by heeen2 | Hacker News Reader

Parent Full thread

heeen2·

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.

View on HN

And I guess of course "proper resolution grub" is of paramount importance given the time you spend inside grub every day.

At least on my system, the Linux terminal is displayed in the resolution set by grub on boot.

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.

And this is the Linux Kernel's fault, or Nvidia's lousy drivers?

What difference does it make whose fault it is?

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.

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.

Read it as "the Linux experience as a desktop user," and not "the Linux kernel."

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.

Reply on news.ycombinator.com