Opened 10 years ago

Last modified 8 months ago

#4670 new bug

Screen resolution on GeForce Go 6100

Reported by: albb Owned by: rudolfc
Priority: normal Milestone: R1
Component: Drivers/Graphics/nVidia Version: R1/alpha1
Keywords: Cc:
Blocked By: #7662 Blocking: #7659
Has a Patch: no Platform: All

Description

"VGA compatible controller [0300]: nVidia Corporation MCP51 PCI-X GeForce Go 6100 [10de:0247] (rev a2)" looks like is not supported by current revision of nvidia driver.

Attachments (5)

nv_1.05_id_0x0247.zip (89.6 KB ) - added by rudolfc 10 years ago.
nvidia driver 1.05 compiled with gcc2 with added 0x0247 id (hrev33337)
img_syslog.zip (131.3 KB ) - added by albb 10 years ago.
nv.zip (4.9 KB ) - added by albb 10 years ago.
haiku_nv_1.07.zip (89.6 KB ) - added by rudolfc 10 years ago.
nvidia driver 1.07: added fix for gc 6100/6150/6200 black screen
nv.2.zip (4.9 KB ) - added by albb 10 years ago.
Log file with new driver.

Download all attachments as: .zip

Change History (29)

comment:1 by albb, 10 years ago

This problem is observed on hrev33109. Let me know if you need any assistance with testing etc.

comment:2 by rudolfc, 10 years ago

Hi there,

This should be fixed in hrev33337. Please test the driver and let me know how it holds up!

Thanks,

Rudolf.

by rudolfc, 10 years ago

Attachment: nv_1.05_id_0x0247.zip added

nvidia driver 1.05 compiled with gcc2 with added 0x0247 id (hrev33337)

comment:3 by rudolfc, 10 years ago

Hi again,

I just added the compiled driver to the ticket. Please test..

Bye!

Rudolf.

by albb, 10 years ago

Attachment: img_syslog.zip added

comment:4 by albb, 10 years ago

With new driver I obtain strange picture on my screen. In img_syslog.zip photo and /boot/var/log/syslog.

comment:5 by rudolfc, 10 years ago

Hi,

I am going to need the logfile from the driver itself. You need to create a file called 'nvidia.settings' in your home/config/settings/kernel folder. (You'll find a file called 'kernel' already there).

Please use a texteditor to create this file with the following text: logmask 0xffffffff

This will enable logging for the driver upon the next boot. The resulting logfile will be in your home folder, and will be called something like: nvidia.10de_01d1_010000.0.log

This file will probably only survive a reboot if you can orderly shut the system down while having that strange picture. After boot completes (HD becomes idle more or less) try hitting: <ALT><sysRq>, then release the key combination, then hit <ALT><D>. You should now be in kernel debugger land. Since you don't have a working gfx driver, you can not see that though. Now type: reboot (followed by <enter>).

If you now boot in VESA mode (failsave video mode) you should be able to find that file.

Can you upload that file here? Thanks!

Rudolf.

comment:6 by albb, 10 years ago

OK

by albb, 10 years ago

Attachment: nv.zip added

comment:7 by rudolfc, 10 years ago

Hi again,

The driverlog shows that your panel is 1280x800. It seems the driver works correctly, apart from the fact that no I2C buses are found.

The mode it sets is 1024x768, which should normally display OK.

Can you do the following test: install the driver again (if you removed it that is), and before rebooting delete the following files:

in home/config/settings/kernel/drivers, delete the file called 'vesa' if it exists. in home/config/settings/system/app_server, delete the settings file there.

IF you now reboot (don't use the screen prefs panel!!) the app_server will ask the driver for the native resolution of the panel, which it will get.

The app_server will issue a setmode command for the native mode 1280x800. I am curious if this mode will actually work on your system..

Can you take another screenshot and upload that here as well?

Thanks!

Rudolf.

comment:8 by albb, 10 years ago

Hi.

I delete file home/config/settings/kernel/drivers/vesa and delete all files in home/config/settings/system/app_server/ and I get screen as in first post.

comment:9 by rudolfc, 10 years ago

OK, thanks!

I just uploaded a newer version of the driver. Can you drop that in place and see if it works for you?

Can you upload a log from it?

Thanks!

Rudolf.

by rudolfc, 10 years ago

Attachment: haiku_nv_1.07.zip added

nvidia driver 1.07: added fix for gc 6100/6150/6200 black screen

by albb, 10 years ago

Attachment: nv.2.zip added

Log file with new driver.

comment:10 by rudolfc, 10 years ago

Thanks!

So did you have a picture, did the situation change?

Bye!

Rudolf.

comment:11 by michaelvoliveira, 10 years ago

Same as here Rudolf

NVIDIA GeForce6100

vgapci0 at pci0:0:13:0: class=0x030000 card=0x82341043 chip=0x03d010de rev=0xa2 hdr=0x00

vendor = 'Nvidia Corp' device = 'GeForce 6100 nForce 430' class = display subclass = VGA

your nvidia driver don't recognize it

falls back on vesa mode

comment:12 by rudolfc, 10 years ago

Hmm,

On the system on which my driver doesn't recognize the card: Can you open a Terminal window, and type:

listdev

Please grab the output and upload it here. cardID 0x03d0 _is_ recognized by the driver. (Nvidia GeForce 6100 nForce 430)

Strange it doesn't work.

Can you also in the terminal type:

ls /dev/graphics

And tell me what entries you see?

Thanks!

Rudolf.

comment:13 by michaelvoliveira, 10 years ago

Sure! Here we go:

~> ls /dev/graphics 10de_03d0_000d00 vesa

~> listdev device Bridge (Host bridge) [6|0|0]

vendor 1022: Advanced Micro Devices [AMD] device 1103: K8 [Athlon64/Opteron] Miscellaneous Control

device Bridge (Host bridge) [6|0|0]

vendor 1022: Advanced Micro Devices [AMD] device 1102: K8 [Athlon64/Opteron] DRAM Controller

device Bridge (Host bridge) [6|0|0]

vendor 1022: Advanced Micro Devices [AMD] device 1101: K8 [Athlon64/Opteron] Address Map

device Bridge (Host bridge) [6|0|0]

vendor 1022: Advanced Micro Devices [AMD] device 1100: K8 [Athlon64/Opteron] HyperTransport Technology Configuration

device Display controller (VGA compatible controller, VGA controller) [3|0|0]

vendor 10de: nVidia Corporation device 03d0: C61 [GeForce 6150SE nForce 430]

device Bridge (PCI bridge, Normal decode) [6|4|0]

vendor 10de: nVidia Corporation device 03e9: MCP61 PCI Express bridge

device Bridge (PCI bridge, Normal decode) [6|4|0]

vendor 10de: nVidia Corporation device 03e9: MCP61 PCI Express bridge

device Bridge (PCI bridge, Normal decode) [6|4|0]

vendor 10de: nVidia Corporation device 03e8: MCP61 PCI Express bridge

device Mass storage controller (IDE interface) [1|1|85]

vendor 10de: nVidia Corporation device 03f6: MCP61 SATA Controller

device Bridge [6|80|0]

vendor 10de: nVidia Corporation device 03ef: MCP61 Ethernet

device Mass storage controller (IDE interface) [1|1|8a]

vendor 10de: nVidia Corporation device 03ec: MCP61 IDE

device Multimedia controller (Audio device) [4|3|0]

vendor 10de: nVidia Corporation device 03f0: MCP61 High Definition Audio

device Bridge (PCI bridge, Subtractive decode) [6|4|1]

vendor 10de: nVidia Corporation device 03f3: MCP61 PCI bridge

device Serial bus controller (USB Controller, EHCI) [c|3|20]

vendor 10de: nVidia Corporation device 03f2: MCP61 USB Controller

device Serial bus controller (USB Controller, OHCI) [c|3|10]

vendor 10de: nVidia Corporation device 03f1: MCP61 USB Controller

device Memory controller (RAM memory) [5|0|0]

vendor 10de: nVidia Corporation device 03f5: MCP61 Memory Controller

device Serial bus controller (SMBus) [c|5|0]

vendor 10de: nVidia Corporation device 03eb: MCP61 SMBus

device Bridge (ISA bridge) [6|1|0]

vendor 10de: nVidia Corporation device 03e0: MCP61 LPC Bridge

device Memory controller (RAM memory) [5|0|0]

vendor 10de: nVidia Corporation device 03ea: MCP61 Memory Controller

Thanks Rudolf!!

Michael

in reply to:  13 comment:14 by mmadia, 10 years ago

Replying to michaelvoliveira:

> ~> ls /dev/graphics
> 10de_03d0_000d00  vesa
>
> device Display controller (VGA compatible controller, VGA controller) [3|0|0]
>   vendor 10de: nVidia Corporation
>   device 03d0: C61 [GeForce 6150SE nForce 430]
  • Out of curiosity what motherboard is this?
  • What type of connection are you using to the monitor?
  • Does the screen preflet identify your monitor?
  • What's listimage | grep graphics display?

My MSI K9N6PGM2-V uses the same 10de:03d0(C61) and it works here. Using a D-SUB cable, it is connected to a ViewSonic VX900, which is detected by Screen.

comment:15 by michaelvoliveira, 10 years ago

Hi mmadia!

I'm using an ASUS M2N-MX SE, cheap, very common here in Brazil. The screen preflet shows a HP D8904 (HP 72) monitor, very old, but with 15,2", but this monitor is 17" I' using a D-SUB cable too, but I use DVI adapter at top of D-SUB Cable with my Radeon HD 2600 PRO on it, the screen pleflet shows 17".

the listimage command display it:

listimage | grep graphics
  366          /boot/system/add-ons/kernel/drivers/dev/graphics/nvidia 0x805bd000 0x805c0000    0          0
  370            /boot/system/add-ons/kernel/drivers/dev/graphics/vesa 0x8060f000 0x80612000    0          0
TEAM 2142 (/bin/grep graphics):

Is possible vesa driver is in conflict with nvidia driver?

comment:16 by michaelvoliveira, 10 years ago

resolved!! with this command

 listimage | grep accel
  371               /boot/system/add-ons/accelerants/nvidia.accelerant 0x8b0000 0x8e7000    0          0
TEAM 3817 (/bin/grep accel):

Thanks for all the help

comment:17 by rudolfc, 10 years ago

Hi again,

So, what does 'resolved'mean? Does the driver work, or doesn't it? Why did you say the driver did not recognize your card?

As far as I can see upto now it's there it's active and it should work.?

Thanks..

Rudolf.

comment:18 by michaelvoliveira, 10 years ago

Sorry for the delay,

the driver are running right all the time

but I didn't recognize any diference between vesa mode and with your perfect driver ;)

with this command described above I was able to see running here

thanks Rudolf!

in reply to:  10 comment:19 by albb, 10 years ago

Hi!

Apologies for the long silence. Yesterday I downloaded the source tree and build the system. Revision 35505 The situation has not changed, the picture is similar to the previous one.

Replying to rudolfc:

Thanks!

So did you have a picture, did the situation change?

Bye!

Rudolf.

comment:20 by anevilyak, 9 years ago

Blocking: 7659 added

(In #7659) Indeed.

comment:21 by scottmc, 8 years ago

Blocking: 7662 added

comment:22 by rudolfc, 4 years ago

Hi (albb)

This ticket is still open for GeForce 6100 Go (NV44) and alike. The problem can probably only be fixed when I have direct access to such a card though.

Rudolf.

comment:23 by rudolfc, 10 months ago

We have a general GF 61xx card problem, if I remember correctly,this is a card-type which is integrated on the mainboard of systems. I need such a mainboard to be able to test this card type. Which did not happen yet unfortunately.

The GF61x0 problem is the last remaining item which should be fixed in the existing nVidia Haiku driver.

Related tickets: #2780, #4670, #6292, #12955.

comment:24 by waddlesplash, 8 months ago

Blocked By: 7662 added
Blocking: 7662 removed
Note: See TracTickets for help on using tickets.