I would not expect a microsoft/windows driver to work for anything on Linux. Glad you got it working.

indeed, I wrote about windows,

if windows was boot from grub and it uses default microsoft driver, then above mentioned resolution problem occured, but after installing the Intel drivers in windows it works properly.

so I think grub does not work properly with default drivers in windows

i think those two events (changing the drivers, and grub suddenly working again) are not directly connected, if at all.

therefore i think this statement:
is erroneous.

incidentally, this is the sort of voodoo talk i heard a lot on windows forums, back in the days. that's why i call it "windows voodoo" - but it's also fairly common on ubuntu forums.
nowadays, i prefer to solve my computer problems logically.

My assumption that for some reason, intel driver is able to restore the correct resolution (after booting from grub), but basic microsoft driver not, is likely and completely rational. In addition, my assumption is confirmed empirically.


It's also fairly common in Science

Even in empirical sciences such as physisc it is impossible to prove with 100% certainly that in between any two events is causual relation, but taht does mean that physics is the sort of voodoo ?

Physicists see that event A follows event B, on the basic of this, they conclude that B cause A - of course, this is not strictly logical reasoning, it is only empirical reasoning: https://prezi.com/caktt8qbv49o/empirical-reasoning/

I think that you do not understand what the problem was, read the topic from the beginning (grub was working all the time)

It may have to do with firmware that gets loaded and stays between boots. I had a wireless card that wouldn't come on unless I booted into windows first. Never did figure it out. After a few kernel upgrades on linux it eventually wasn't an issue. Some of that voodoo computing.

Depends how we define boot. Neither Grub Legacy nor Grub2 have ever directly booted windows, whether an older Legacy or a newer UEFI system. If you look in a Grub boot file (menu.lst, grub.cfg) any entry for windows will have "chainloader" in it. It just points to a specific location on the drive where the windows boot files should be whereas with Linux, it points not only to the location on the drive for boot files but to the specific files (kernel) needed to directly start the OS. I don't know what caused this but I don't see how a different driver on your windows system is going to impact Grub as it doesn't do anything on windows. Long as you got it working, the puzzle can be left for those who are/might be interested.

I put on a red sweater today.
When I left my house it was raining.
Therefore, putting on a red sweater makes it rain.
That is completely rational, empirical, and therefore scientific.
qed.