GeForce 9400M - only VESA

[vidrep]

HP Mini 311 Nvidia ION Only VESA graphics available

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

vendor 10de: NVIDIA Corporation device 087f: C79 [ION LE]

[rudolfc]

Hi,

Tempting to look at it, isn't it? ;-)

Is ID really nvidia btw? can you upload a syslog here? I see manufacturor ID 0x1025 in nouveau I think..

Let's put it this way: I am currently having a look how hard it would be to add a generation or two to the existing driver (after all). Looking at a GF8400 (wat a beast!) and a 9200M (I think) to see if I get a response I can work with. At this moment it seems register access is down, though mapped correctly (on both), for instance. I did get DDC/EDID going though on the laptop on the external VGA connector. If your card happens to be on the same page and I get it going this way, you're in luck. Don't hold your breath though..

Please upload the syslog from a vesa boot to start with for now. Thanks!

[vidrep]

Here's some info attached

[vidrep]

hrev55862 x86_gcc2h (clean install)

First boot black screen

Second boot, enable fail safe graphics in boot menu, uncomment kernel config "fail_safe_video_mode true"

Third boot, vesa resolution 1024x768

Selecting native resolution (1366x768) or any other listed resolution in screen preferences - black screen

After manually creating "vesa" text file in /boot/home/config/settings/kernel/drivers with mode 1360 768 32, the system will boot into native resolution. However, as before, selecting any other resolution results in black screen.

[vidrep]

Something seems to be wrong in how Haiku detects the display and sets the vesa resolution. Previous syslog and syslog attached.

[rudolfc]

Hmm, strange. So the nivida driver is not in play since it doesn't support it yet, but I see both a message from vesa_accelerant and one called framebuffer. I seem to remember these two were seperated from each other not so long ago (again). Also there were experiments with overwriting the cardBIOS with custom modelines for VESA I think, but I don't know (don't think so) if it's in main git already.

So I guess it's interesting to look at /dev/graphics to see what's loaded.

Oh, make sure you are running a completely upto date system, since EDID info structure was changed in size and content not so long ago: VESA will probably use the info detected at boot for it's use: but will fail if the load stuff and main system are not 'in sync'.

I hope I make sense...