Opened 8 years ago

Last modified 10 months ago

#7122 new bug

no usable screen with nVidia 7600 GO

Reported by: wretched_dutchman Owned by: rudolfc
Priority: normal Milestone: R1
Component: Drivers/Graphics/nVidia Version: R1/Development
Keywords: 7600 GO Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86


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

Attachments (4)

syslog (187.1 KB) - added by wretched_dutchman 8 years ago.
nvidia.10de_01d8_010000.0.log (66.8 KB) - added by wretched_dutchman 8 years ago.
20110121_001.jpg (570.8 KB) - added by wretched_dutchman 8 years ago.
screen without mouse movement
20110121_002.jpg (499.9 KB) - added by wretched_dutchman 8 years ago.
screen with menu opened

Download all attachments as: .zip

Change History (11)

comment:1 Changed 8 years ago by anevilyak

Likely a duplicate of #4480, rudolf?

Changed 8 years ago by wretched_dutchman

Attachment: syslog added

comment:2 Changed 8 years ago by 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..



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?

Last edited 8 years ago by rudolfc (previous) (diff)

Changed 8 years ago by wretched_dutchman

Changed 8 years ago by wretched_dutchman

Attachment: 20110121_001.jpg added

screen without mouse movement

Changed 8 years ago by wretched_dutchman

Attachment: 20110121_002.jpg added

screen with menu opened

comment:3 Changed 8 years ago by 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..



comment:4 Changed 8 years ago by 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.

comment:5 Changed 8 years ago by tqh

This guide might be helpful, written by Rudolf even:

comment:6 Changed 10 months ago by cocobean

I have a laptop with a GeForce Go 7600 in which Haiku currently works with it, so this may be hardware/laptop specific (see #4480 for my screenshot). Looks like the reporter's laptop is a Sony VAIO model (similar to a Sony VAIO VGN-FE890).

Last edited 10 months ago by cocobean (previous) (diff)

comment:7 Changed 10 months ago by 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..)

Note: See TracTickets for help on using tickets.