no usable screen with nVidia 7600 GO

[wretched_dutchman]

When booting Haiku from cd I get a torn screen with my nVidia 7600 GO. Booting-screen looks good, but when I'm entering the installation screen I get an equal blue screen and when I move my mouse I see a horizontally torn screen and vertically streched (based upon the mouse)

Booting with the VESA driver in default resolution is possible, booting with VESA standard resolution fails to display boot-screen.

My graphics card is (based upon lspci -nn): 01:00.0 VGA compatible controller [0300]: nVidia Corporation G72M [GeForce Go 7400] [10de:01d8] (rev a1) and it is detected by haiku's nvidia driver (ls /dev/graphics): 10de_01d8_010000 vesa

[anevilyak]

Likely a duplicate of #4480, rudolf?

[rudolfc]

Hi there,

Can you add a nvidia driver logfile as well? You need nvidia.settings for that with logging enabled and do a reboot (see the other bugreport for details). The resulting logfile will be in your home folder.

Would be handy to have a photo of the distorted screen as well maybe..

Thanks!

Rudolf.

anevilyak: I'll look at the other one and compare it when I have logfiles from both before I'll say anything like that :-) Though the other bug seems 'stuck' as the reported doesn't respond anymore?

[wretched_dutchman]

screen without mouse movement

[wretched_dutchman]

screen with menu opened

[rudolfc]

Hi there,

Thanks for the extra information. I Don't think this is a duplicate to #4480 since there's a picture. The screen is not black, instead shows some small part of the actual desktop. It looks like data-fetching from ram comes to a premature ending, and the pitch is not right (granularity restricions in the hardware). At least from what I can see from static pictures.

From the log:

• EDID channels are all wired, but the panel does not report EDID info.
• cardBIOS programs panel as being 1280x800. (is this indeed the native resolution of the panel?)

My guess is I am missing some programming information for this specific hardware.. Would have to check against a linux driver to see if there's something new for this hardware. The other option is to disable the hardware ID for this card.

Unfortunately I'm unable to do any work on it at this time..

Bye!

Rudolf.

[wretched_dutchman]

Yes, 1280x800 is the native resolution of my panel.

I may be a rookie programmer, but I am willing to get this card to work and try to look into it. Could you please give me some pointers on driver-writing and -debugging (general documentation and/or direction of the possible source of this error). I've looked into the Writing Video Card Drivers In BeOS, but as you might know, this one isn't quite complete.

[tqh]

This guide might be helpful, written by Rudolf even: ​http://haiku-os.org/legacy-docs/writing-video-card-drivers.

[cocobean]

I have a laptop with a GeForce Go 7600 in which Haiku currently works with it, so this may be hardware/laptop specific.

[rudolfc]

This really looks to be a different problem, with RAM access trouble (not for the CPU, but for the CRTC/DAC). Since linux sources need to be checked for a patch for GF6xxx mainboard in-built series, leaving this ticket open for now as it might be more info becomes available yet for this problem. Don't know if Martijn is still around in case some testing would be needed, assuming Martijn still has this hardware?

For completeness: the driver might also be OK enough for this card, as trouble trying to do VESA setmodes etc during boottime could have messed up the card's default setup. In other words, depending on what Haiku does with the card exactly during boot, trouble might arise or go away.. (of course that should not be, but then again, we have limited knowledge about nVidia hardware to make it work OK in all possible configs..)

[rudolfc]

For Geforce 6000-6200, notably Nforce 4 and 4xx, but possibly more cards, added detection of a 25Mhz GPU base frequency crystal. This fixes too low refreshrates, wobbly screens, no picture at all, only part of a picture and that kind of trouble.

Fixed in hrev55039.

Please retest if still possible. If no feedback will come I'll close the ticket assuming it's OK now.. (memory and GPU clocking is also influenced by the change, if the driver is set to program these.)

Thanks!

[cocobean]

@rudolfc - No major video issues as of the current R1/beta3 hrev55181+8 prerelease.

[rudolfc]

OK thank you. Time to close the ticket I think. Since that message above I added two more fixes to the driver even that also might very well have a positive effect on that system

Bye!

PS Feel free to re-open if needed.