Jump to content
LaptopVideo2Go Forums

56.72 with Version 9.6 INF needs Guinea Pigs.


mobilenvidia

Recommended Posts

Right I have attempted to recreate the 52.16 driver v9.6 INF for 56.72

I have added support for all GPU's (NV36 section sucked from 53.82 Dell INF)

v 9.6 is entirely Dell based but apparently is only INF that works with Toshiba's with black bar (52.16 anyway)

The INF is mostly the same as 52.16 v9.6, but some changes had to be made to allow for new driver models (52.16 is 50 series 56.72 is 55 series)

The main difference is I disabled the multi-disp install, it is very easily enabled again if required.

Give it a whirl, and report back.

Here is INF.

Pieter

Link to comment
Share on other sites

Guest Guest

Tried it out, still get black bar (52.16/9.6 work on my system but are slow as molasses). So, it doesn't see to be an inf problem.

Satellite 5105 S501, GeForce4 440GO 32mb (4.17.00.41.C5).

Link to comment
Share on other sites

Non-Working

Satellite 2415-S205 (15V) | GeForce4 420 Go 16MB (4.17.00.41.C7) | ... - Tenstrum

Satellite 5105 S501 (??V) | GeForce4 440 Go 32MB (4.17.00.41.C5) | 56.72 - ...

Satellite 5105-S501 (15V) | GeForce4 440 Go 32MB (4.17.00.41.C5) | 54.01, 56.72, 56.82 - FastFret (1400x1050)

Satellite Pro 6100 (15V) | GeForce4 420 Go 32MB (4.17.00.41.C7) | ... - ministeve (1024x768)

Satellite Pro 6100 (??V) | GeForce4 420 Go (4.17.00.41.C7) | ... - atakki (1600x1200)

Working

Satellite 2410-S404 (15V) | GeForce4 420 Go 32MB () | 52.16 - HighShot

Satellite 2410-S514 (15V) | GeForce4 420 Go 32MB (4.17.00.41.C7) | 52.16 - Wolfman

Satellite 2455-S305 (15V) | GeForce4 420 Go 32MB (4.17.00.59.F9) | 60.72 - Raptor (1024x768)

Satellite 3000-S514 (19V) | GeForce2 Go () | 42.51 - splintah ()

Satellite 5100-S201 (????) | ? () | 56.82 - thosch ()

Satellite 5200-S801 (15V) | GeForce4 460 Go 64MB () | "Most drivers work ATM" - Morbid2002 (1600x1200)

Satellite 5205-S703/4 (15V) | GeForce4 460 Go 64MB (v4.17.00.59 D3) | (1600x1200), NO BlackBars, but Standby problem beginning with driver v54.01 - Dakotah

Dell 8100 (20V) | GeForce2 Go 32MB (3.11.01.44.B4) | * - Teraphy (1600x1200) :)

Pieter's List (Apr 19)

Toshiba (15v) assembled machines : 
1410-s303 Doesn't work
1415-s105 Doesn't work with 5x.xx
1415-s173 Doesn't work with 5x.xx
2410-s303 Doesn't work
2410-s404 52.16 works with INF v9.6
2410-s514 52.16 works with INF v9.6
2415-s205 with problems. 
2455-s305 with NO problems
5100-s201 works with 45.62 and 56.82 !!
5105-s501 Doesn't work with 5x.xx
5200-s801 Works up to 52.xx, then games fail.
5205-s703/4 with NO problems (dontknow's machine).
5205-s705 with NO problems. 
6100- Doesn't work

Compal (19v) assembled machines : 
1950-s801 with NO problems
1955-s805 with NO problems
2430-s??? with NO problems 
2435-s255 with NO problems
3000-s514 with NO problems

Edited by Teraphy
Link to comment
Share on other sites

Attched is a nother version more closely related to the original v9.6.

I've re-enabled the multi device install and inserted back in the Dual view settings it tries to install.

Give this a try as well, I've named this inf 9.61

Good luck,

Pieter.

nv4_disp.inf

Link to comment
Share on other sites

Guest Guest

Hi Pieter,

Tried 9.61 with 56.72 - still get black bar I'm afraid. The inf does induce some unusual behavior, though. It installs MultiView upon reboot. Afterwards, multiple monitors is the only monitor choice in the display cpl (no option for plug and play monitor). I do get a choice of both 1372x1050 and 1400x1050 as resolutions (this is the first time this has happened), but if I select 1400x1050 I still get the black bar. If I check in the nVidia properties it tells me that the max res of my monitor is 1372x1050 which is incorrect, just like the other black bar inducing Forceware.

Link to comment
Share on other sites

Guest Angel77_80

Hi Pieter,

same here ; try both of your modded 9.6 inf for 52.76 detonators, but still black bar - only difference is the multiview installation and that I can - in my case - select 1024*768, exactly as "Guest" describe it just above". I tried to play a little with settings of your inf, and added :

"HKR,, Mobile, %REG_DWORD%, 2"

setting in the NV17 Software Device Settings too, but nothing more...

By the way, I tried to edit the nv4_mini.sys to see if something could give us a clue here... I noticed that until 52.16, the setting SoftEDID is referenced on this file. But since 53.03, nothing about this... Don't know if this can help you, but I am trying to explore this way to see if I can point something out.

Anyway, thanks for your work for us Toshiba user's who have this black bar problem !

Link to comment
Share on other sites

V9.62 is attached this has SoftEDIDs=1 (default setting)

Give this a try also.

Pieter.

nv4_disp.inf

Link to comment
Share on other sites

v9.63 another INF with Mobile=2, SoftEDIDs=0

These settings works for Toshibas using FreeBSD.

Pieter.

nv4_disp.inf

Link to comment
Share on other sites

Guest Guest

Tried 9.62, same behavior, same black bar.

Did not see a link to the 9.63 attachment, so I manually changed all instances of SoftEDIDs to 0 and Mobile to 2 in 9.62 and reinstalled. Interesting behavior in that the computer went through a found new hardware dialogue for the plug and play monitor as well as for multiview. This is a behavior of the working (no black bar), but not of the non-working (black bar) drivers. Unfortunately, I still get a black bar after the 9.63 installation and even though I can set the monitors setting to 1400x1050 under display settings, nView display properties still thinks the max res is 1372x1050.

Link to comment
Share on other sites

Mobile=2 is required for non-compal Toshibas. No way around this value. SoftEDID's I believe is irrelevant.

Link to comment
Share on other sites

'Mobile' only works when 'SoftEDIDs = 0', when SoftEDIDs = 1 it has no affect.

I read this on one of the nVidia docs somewhere.

So why does my 9.6 work on 52.16 and the others don't, there miust be an INF setting.

But which one ??

Pieter.

Link to comment
Share on other sites

Guest Guest

Pieter, I wonder if this is not an inf problem at all, but that the EDID is being set by some other component of the driver. Ministeve has looked into this in detail, and that seems to be the conclusion he's come to (see other threads in this and in the technical forum). 52.16 probably has some other part of the software that is similar to the 4x.xx series that is different in the 5x.xx series.

Link to comment
Share on other sites

So why does my 9.6 work on 52.16 and the others don't,

As far as i read, the 11.x INFs also work. All INFs below 13.xx/20.xx work with 52.16. Beginning with 9.6 (?). So it would be easier to look what you've added to the 9.6 INF (from 9.5)...

Link to comment
Share on other sites

By the way, I tried to edit the nv4_mini.sys to see if something could give us a clue here... I noticed that until 52.16, the setting SoftEDID is referenced on this file. But since 53.03, nothing about this... Don't know if this can help you, but I am trying to explore this way to see if I can point something out.

Could be interesting to check whether SoftEDID is referenced in nv4_mini.sys files shipped with 44.68, 46.34, 46.90, and 47.12 Those constitute a mix of black bar/non black bar drivers on my system.

In all the aforementioned drivers, SoftEDIDs is indeed referenced in nv4_mini.sys, just checked

Link to comment
Share on other sites

Guest Angel77_80

Hi everyone,

Ministeve, I did look into nv4_mini.sys for a lot of drivers ; it is always the same : drivers up to 52.16 do have the reference to SoftEDIDs, and after that, did not appear anymore in this driver. I think this value is no more controlled by the registry ; it may have been set at "1" forever without any option for us to modify that (except if we add source code of the driver, maybe).

Here an explanation of SoftEDIDs value quoted from the README.TXT from the official nvidia freebsd driver :

" The SoftEDIDs registry key enables dynamic generation of an appropriate EDID for mobile LCD displays from data stored in the video BIOS. If this is turned off, then on mobile systems, a hardcoded EDID will be chosen from a table, based on the value of the Mobile registry key."

From what I understand from our problem (I am not an expert into graphic drivers, not even into drivers at all), the situation is the following : the drivers, with our Toshiba, should normally go and pick up onto a table of multiple value the EDID of our panels, which is referenced in this table with the mobile value (2, in our case). But, as the SoftEDIDs value is now unchangeable for some reason that only nvidia know, it will go everytime searching the EDID value from the bios of the video card.

That's why with old drivers, the key in registry you pointed out Ministeve (which I think is picked up from the video bios at every boot), is irrelevant because the driver do not look for this value. It goes searching somewhere, don't know if it is on the registry, or in a file, the right EDID. I think this explain why the EDID value in the registry is always the same, with an old or a new driver.

So, here is my question : is it possible to find the table of EDIDs which are pre-configured for "mobile" values ? And is it possible to reinject this EDID in the bios of our video cards ?

Just an idea, I do not know if this is makeable, but I do not see any other way to resolve this problem for now...

Link to comment
Share on other sites

It could very well be the case that the new drivers have different initial values. We're all flying by what the Linux drivers readme says and the knowledge and assumptions we have made thus far.

To see those registry keys disappear would not be crazy. They could easily be hardcoded.

Google for 1372x1050 came up with : http://freebie.miraclenet.co.th/notebook/satellitepro-6100/

Link to comment
Share on other sites

What that page is saying is appalling: the EDID of the notebook would only allow for a smaller, nonstandard horizontal resolution. Furthermore not in contradiction with what you wrote Angel77_80. In fact, in the nv4_mini.sys there are quite a few EDIDs. One matches an EDID found in Craig Corp's registry ("NVIDIA_UXGA"). Another EDID in nv4_mini.sys is what I get in my registry when there is no black bar ("Toshiba Internal 1024x768 Panel" ). In both cases, the only difference is a consistent replacement of carriage returns with new lines in the monitor description string.

Assuming that the "Toshiba Internal 1024x768 Panel" EDID stored in nv4_mini.sys is copied to the registry key, where does the "Nvidia default panel" EDID comes from, with its 969x768 timing? The string "Nvidia default panel" occurs in nv4_mini.sys; not in an EDID though. :)

Link to comment
Share on other sites

I must have been really tired one night. I attempted to look for that string and couldn't find it. Either that or my searches didn't include the sys. Anyway, a few lines up above that string is what you need to do: OverridePanelStrapAndIndex. It is a registry key...

--

I confirm the lack of SoftEDIDs registry key in newer drivers and the addition of OverridePanelStrapAndIndex in newer drivers.

Link to comment
Share on other sites

Have any of you Black Barians tried 56.63 with the NVCT.INF? (Compal Toshiba ?)

In here are specialised Panel settings.

Worthy of a try,

Pieter.

Link to comment
Share on other sites

copy&pasted from latest Leadtek Linux driver (v1.0-5336)

Option "UseEdidFreqs" "boolean"

This option causes the X server to use the HorizSync

and VertRefresh ranges given in a display device's EDID,

if any. EDID provided range information will override

the HorizSync and VertRefresh ranges specified in the

Monitor section. If a display device does not provide an

EDID, or the EDID does not specify an hsync or vrefresh

range, then the X server will default to the HorizSync

and VertRefresh ranges specified in the Monitor section.

Option "IgnoreEDID" "boolean"

Disable probing of EDID (Extended Display Identification

Data) from your monitor. Requested modes are compared

against values gotten from your monitor EDIDs (if any)

during mode validation. Some monitors are known to lie

about their own capabilities. Ignoring the values that

the monitor gives may help get a certain mode validated.

On the other hand, this may be dangerous if you do not

know what you are doing. Default: Use EDIDs.

Option "NoDDC" "boolean"

Synonym for "IgnoreEDID"

Option "FlatPanelProperties" "string"

Requests particular properties of any connected flat

panels as a comma-separated list of property=value pairs.

Currently, the only two available properties are 'Scaling'

and 'Dithering'. The possible values for 'Scaling' are:

'default' (the driver will use whatever scaling state

is current), 'native' (the driver will use the flat

panel's scaler, if it has one), 'scaled' (the driver

will use the NVIDIA scaler, if possible), 'centered'

(the driver will center the image, if possible),

and 'aspect-scaled' (the driver will scale with the

NVIDIA scaler, but keep the aspect ratio correct).

The possible values for 'Dithering' are: 'default'

(the driver will decide when to dither), 'enabled' (the

driver will always dither when possible), and 'disabled'

(the driver will never dither). If any property is not

specified, it's value shall be 'default'. An example

properties string might look like:

"Scaling = centered, Dithering = enabled"

Link to comment
Share on other sites

Have any of you Black Barians tried 56.63 with the NVCT.INF? (Compal Toshiba ?)

In here are specialised Panel settings.

I considered NVCT.INF when I installed 56.63, but there is no provision for my SUBSYS. Therefore I used NVTS.INF.

Link to comment
Share on other sites

  Anyway, a few lines up above that string is what you need to do:  OverridePanelStrapAndIndex.  It is a registry key...

That string caught my attention too. With 56.63/NVTS.INF it has no effect, set to 0 or 1 as DWORD (is the type right? Any docs on this setting?)

However, it SHOULD be possible to activate the EDIDs in nv4_mini.sys, somehow. Why should nVIDIA leave them there?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...