Comment 5 for bug 221703

I looked into this a bit yesterday but didn't come up with solid ideas. I checked other bug reports where Hardy came up with -vesa instead of the expected driver, but in all cases the issue was something clearly unrelated to this. Those were not using nvidia hardware, though. Have you had install issues with this system before? Maybe it's just a peculiar piece of hardware?

I also doublechecked that your pci id is listed for the driver, and yes it is. ( { 0x10DE0112, "GeForce2 Go" }, ) so there seems little reason why the xserver ought to pick -vesa for it. One thing you could doublecheck next time you have the system on would be to do ` grep 10DE0112 /usr/share/xserver-xorg/pci/nv.ids` to verify the id is actually in the system where the X server can see it. But I'd be surprised if this was the cause.

Next time I see you, if you can lend me the hw I can take a more involved look into it (I'd like to be able to do some re-installs on it).