#7655: Resolution 640x480 the only one available -- driver using own EDID interp. instead of (more complete) common code's EDID interpretation ---------------------------------------+---------------------------- Reporter: ttcoder | Owner: rudolfc Type: bug | Status: new Priority: normal | Milestone: R1 Component: Drivers/Graphics/nVidia | Version: R1/Development Resolution: | Keywords: Blocked By: | Blocking: Has a Patch: 1 | Platform: All ---------------------------------------+---------------------------- Comment (by ttcoder): Turns out I have to do some voodoo hoodoo to boot now: I have to change the ''VESA resolution in the boot menu safe options'', in order to get a good monitor sync from the ''nVidia'' accelerant.. Behavior if I fail to choose the 800x600 '''VESA''' resolution (or if I pick any other resolution): - VESA does not work (strange... VESA worked in 41834, regardless of whether or not I chose a specific resolution) - '''nVidia''' does not work (even stranger! how can nVidia be affected by the boot menu resolution selection ??): it tries to setup 640x480 at 1900 (!) MHz pixel-clock Behavior if I select 800x600 VESA resolution: - VESA indeed works in 800x600 - nVidia is able to display both 640x480 at a correct 30.5 MHz pixel clock, and 800x600 This could be linked to our above discussion (i.e. the nVidia accelerant does not play nice with create_display_modes()) but I don't think so, since the VESA accelerant is also affected. So I'll file a distinct ticket soon, insisting on the VESA side of the equation as this should be easier to reproduce and debug. (i.e. the fact that VESA requires a specific resolution to be picked otherwise it fails, whereas it was smart enough to pick a resolution on its own in 41834). And when that gets fixed it will probably also fix the nVidia problem, allowing me to boot this PC without trouble. -- Ticket URL: <http://dev.haiku-os.org/ticket/7655#comment:11> Haiku <http://dev.haiku-os.org> Haiku - the operating system.