BeBits - Haiku nVidia TNT/GF driver - Talkback

BeBits

Haiku nVidia TNT/GF driver

Talkback

Go back to the Haiku nVidia TNT/GF driver page

Post a new Talkback comment!

card not supported

By rephi - Posted on March 18, 2004 - 12:41:55 (#11515)
Current version when comment was posted: 0.09

Hello Rudolf!

It seems, that your driver doesn't support my GeForce Card. Its a GeForce4Go with 64 MB memory built in a Laptop. I don't know how to make it work. If it is not supported, how can I help you. Here are some Specs of the card from the Devices panel in Zeta RC2:
Vendor: Nvidia Corporation (0x10de)
Card ID: 179

Btw I also tried the 0.10-7 build from the obos cvs, which doesn't work either (neither with the internal panel nor external monitor)

regards,
Philipp

By NathanW - Posted on March 15, 2004 - 23:32:21 (#11484)
Current version when comment was posted: 0.09

That doesn't work. I also tried it on a GeForce 4 440 and it does exactly the same thing.

GF2Go and 0.09?

By rudolfc - Posted on March 15, 2004 - 21:01:17 (#11482)
Current version when comment was posted: 0.09

Hi Nathan,

How about if you try with the standard 0.09 as released using that trick??

Thanks.. :)

BTW GF FX5200Go is working just nicely on internal panel now it seems. GF2 (NV11) unfortunately is a bit special regarding dualhead stuff, which is probably what we are bumping into here.

Please let me know about std 0.09, I'll wait a few days to get more feedback on GF2Go, and I'll come up with something new to test then.

Rudolf.

By NathanW - Posted on March 15, 2004 - 20:35:32 (#11480)
Current version when comment was posted: 0.09

I tried that. It didn't work. I should also note that I was using the CVS build .5, which had the DFP support. When I connected the external monitor, it complained about out-of-range sync values.

DVI/laptop panel support

By rudolfc - Posted on March 15, 2004 - 14:08:15 (#11477)
Current version when comment was posted: 0.09

Hi,

On a seperate note I can tell you the driver should(could?) support laptop internal panels now. That is, if you use the current CVS version (0.10-4 or higher: see included README.html for version).
When the obos build factory refreshes, you can download it there (date > 14 march).

Also external DVI panels should work now. Over here it does on my GeForce FX5200, on both DVI outputs.

Support is not yet 100% completed, so the driver is not yet foolproof.

Anyway: If you test this, please tell me what happens!
I really need the feedback to get this working decently!

Mail me or post on the zetanews site in the nVidia forum in this thread:
http://www.zetanews.com/module.php?mod=forums&op=topic&id=347

Thanks!!

Rudolf.

GF2Go should work?

By rudolfc - Posted on March 15, 2004 - 12:18:57 (#11474)
Current version when comment was posted: 0.09

Hi,

I just got a report from someone using a trick to get external output going:

->bootup on internal panel with _no_ external monitor connected.
->wait until booting finishes (you heard the startup sound).
->now connect an external monitor and you should have a picture.

Please tell me if this helps...!

Rudolf.

Re: GeForce2Go

By NathanW - Posted on March 15, 2004 - 03:40:23 (#11471)
Current version when comment was posted: 0.09

I can't get mine to work either. The external monitor simply shuts off as soon as BeOS boots. The system isn't hanging - I can telnet into it - but there is just no image.

NVidia Geforce2Go hangs BeOS

By Nek - Posted on March 13, 2004 - 04:01:30 (#11444)
Current version when comment was posted: 0.09

Hi there,

my NVidia Geforce2Go card (in a Toshiba Satellite 3000-100 laptop) will make BeOS (Developer Edition 1.1) hang right after installing Rudolf's Open Drivers. The system will just continue booting if I by-pass the add-ons. Manipulating the settings file didn't help either :(.
Has anybody tried this grafic card with BeOS successfully yet??

And another weird thing: Be wont let me change the screen properties in it's 'Screen' application. I can only update them using the VESA utility.

Cheers,

Nek.

laptop support

By rudolfc - Posted on February 5, 2004 - 20:15:11 (#10948)
Current version when comment was posted: 0.08

Hi,

Support for internal laptop panels is planned for V0.10. As soon as V0.09 is released, I'll be working on it. In the meantime I'd like to point out that the zetanews size has a forum dedicated to the nVidia driver. I'd like to gather info on panels there:
http://www.zetanews.com/module.php?mod=forums&op=forum&id=42

I don't know exactly what will be needed to get them working, but I can use testers to help me get on the road later on. Unfortunately I don't have access to a laptop with a nVidia chipset myself.. :-/

Thanks!

Rudolf.

NV11 bug (hopefully) fixed!

By rudolfc - Posted on February 5, 2004 - 20:09:21 (#10947)
Current version when comment was posted: 0.08

Hi,

Just a quick note: I just updated openBeOS CVS with a fix for the NV11 trouble introduced in V0.08. The build factory will probably be up-to-date within 24hours. Some ten users just received the fix per Email.

I will try to get the FX5700 fully working OK, and then release a V0.09 for just those two fixes...

All other cards seem to be stable :)

Rudolf.

Geforce2go internal monitor

By tmbeihl - Posted on February 5, 2004 - 02:02:50 (#10940)
Current version when comment was posted: 0.08

How much work would it take to make this driver use the internal monitor on my geforce2go laptop? I'm new to BeOs and would like to have color and 1280 X 1024 (& am willing to do some coding to have it ;-)

Dualhead capabilities

By rudolfc - Posted on February 4, 2004 - 12:41:41 (#10939)
Current version when comment was posted: 0.08

Hi,

AFAIK the ATI driver has dualhead 'stretch' mode capability, just like the nVidia and MAtrox driver. On BeOS the stretch mode displays for instance the left part of your desktop on one monitor, while the right part is shown on another.

If this option is not offered for your card, then the ATI driver has a fault, your card does not have that capability, or the specs for your card are unknown for this specific feature.
The ATI driver _does_ support the feature for at least some cards: Thomas showed it to me once..

You _do_ need a special version of the 'Screen' preference app BTW!

---

resolutions:

AFAIK the ATI panel offers all modes exported by the driver, instead of a fixed set of modes like the R5 panel does. As the ATI, nVidia and (0.16CVS) Matrox driver have high res modes above 1600x1200, you should be able to use them if you use the right panel.

For the Matrox and nVidia driver the right panel (for now at least) is the Dualhead Setup app on BeBits (see related links on bottom of the driverpage here on BeBits).

The Matrox and nVidia driver support upto 2048x1536 modes on newer cards (single head). While the second head can probably do this also on nVidia cards (Matrox cards have lower limitations AFAIK), this still does not automatically mean you can use both heads simultaneously in such a high-res mode.

You see, the data that has to be displayed on both heads has to be fetched from the cards memory. Displaying two heads requires much more bandwidth than displaying one. This means that not only the max DAC speed has to be high enough: this also applies for the GPU core speed and the board RAM speed.

Currently the nVidia cards do 1600x1200 in dualhead stretched modes: higher modes currently don't work: only in singlehead mode. This _might_ change in the future though: it depends on the (validity of) information I can gather on those speeds, and the ability to program the cards RAM and CORE speed: which currently is not implemented.

Hope you now know enough about the subject..

Best regards,

Rudolf.

BTW: I would advice a nVidia card for dualhead, and not a Matrox card (nVidia cards have more hardware options/possibilities). ATI will be as good as nVidia. ATI has better chances for good 3D in the future though (specs! ;-)

DualHead, Matrox v ATI v nVidia

By JJ - Posted on February 4, 2004 - 11:27:31 (#10938)
Current version when comment was posted: 0.08

I finally bought a DualHead ATI radean7000 card from CompUSA brand for $60. It works well enough for W2K but has max play DH of 3200x1600 even though SH can go to 2500x2000. It almost works for BeOS, 2nd page is same as 1st but desktop is doubled so I can't see rt side.

Question should I have chosen an nVidia or matrox card. The G550 esp low profile looks nice but its $130 and wouldn't impress W2K, my monitors can go to 2K or near. I have had a SH matrox and nVidia before which I liked but I must get a low profile DH if possible.

Any recomendations on nVidia DH that is also low cost <$100, low profile, no fan, no mega heatsink, lite on 3d.

Is Rudi saying a BeOS desktop can now go over 1600.1200 if monitor allows, that would make me jump right out the door.

NV11 cards...

By rudolfc - Posted on February 3, 2004 - 21:10:47 (#10927)
Current version when comment was posted: 0.08

Hi,

Just a quick note:
It is now confirmed NV11 cards have trouble with version 0.08 of the driver. Rest assured I will try my best to nail this problem.

In the meantime NV11 users are advised to keep using 0.07, unless the 0.08 driver works for them of course. Over here 0.08 works OK on my GF2MX400..

Sorry about this, but it couldn't be helped I'm afraid. That's what you get when no specs are available :-/

Best regards,

Rudolf.

By claydoh - Posted on February 3, 2004 - 20:08:55 (#10926)
Current version when comment was posted: 0.08

It *was* just me :)
My install had issues (that's what I get for not booting beOS more often:;) ), as in sound/multimedia drivers not loading
Did a clean install and everything is as it should have been to begin with :)

bugreport fanskapet

By rudolfc - Posted on February 3, 2004 - 14:04:49 (#10919)
Current version when comment was posted: 0.08

Hi,

First off, I want to make sure everyone that has bugs to report, knows about the bug-report form on the drivers site. It's here:
http://web.inter.nl.net/users/be-hold/BeOS/NVdriver/bugreport.html

In your case fanskapet, I expect you have something called 'bandwidth trouble'. If you can set a lower colordepth, refreshrate or resolution the trouble should be less evident or go away completely. While you probably can't influence that in fullscreen mode, you _can_ set modes normally yourself and move around some big window. If I am correct, you can find a high-res mode that also exhibits this problem, while setting a lower mode will let it go away.

Currently I have no 'fix' yet for this specific problem. It's known to exist on _some_ cards outthere. One thing that _might_ do the trick (according to reports I've had for instance) is updating your cards BIOS with a newer version.

If you want, you can send me a screenshot BTW: I'll probably be able to confirm my theory with that. You can try a normal screenshot, or a screenshot made by digital camera as some problems might not be visible with a 'normal' screenshot _although_ you see it on your screen..

Best regards,

Rudolf.

boot times..

By rudolfc - Posted on February 3, 2004 - 13:55:56 (#10918)
Current version when comment was posted: 0.08

The boottime will probably be shorter compared to V0.05 or before (or VESA mode), as no 2D acceleration existed for the driver back then. Building the screen content costs way more time then.. ;-)

Apart from that I don't think the driver should make any difference..

GF2MX bugreport

By rudolfc - Posted on February 3, 2004 - 13:52:27 (#10917)
Current version when comment was posted: 0.08

Hi there cvincent,

Can you contact me via Email, and send me a logfile from the driver 0.08 with logging fully enabled?
This might give me some insights in what's going wrong.

I'd like to send you a testversion or two also to see if we can nail why 0.07 works and 0.08 doesn't.
One thing that comes to mind is the new dualhead support: NV11 cards (yours for instance) differ from later cards in this respect, and I had to make some assumptions to get it working.

Maybe your tests can verify/deny my assumptions and set me on the right track...

Also you probably want dualhead working (at least I want that ;-), although you probably don't have a second VGA output. The TVout signal can be connected to the secondary head though.. ;-)

Rudolf.

Bug-report!

By fanskapet - Posted on February 3, 2004 - 08:37:24 (#10904)
Current version when comment was posted: 0.08

Great to see that this driver-project still lives :) this version worked, but i noticed some very disturbing graphic-glitches when playing Corum3 in fullscreen together with this driver.. maybe i could make a screenshot or something and send it to you? cheers!

Wow! is it just me..

By claydoh - Posted on February 3, 2004 - 01:13:00 (#10901)
Current version when comment was posted: 0.08

or does version 0.08 radically reduce boot times compared to previous versions???
I spend almost xero time at the boot splash compared to a rather lengthy (for BeOS) time there, then POW I'm at my desktop. Just like the old days :)

Athlon 1200
512mb sdram
geforce4 mx 440 64mb video
BeOS Max version 3

By cvincent - Posted on February 2, 2004 - 20:07:30 (#10899)
Current version when comment was posted: 0.08

I have GForce 2 MX 400
Device Type : Display controller
Base : 3 SubType : 0 Interface : 0
Vendor Nvidia Corporation (0x010de)
Card ID : 110

with v0.0.7 all is ok, i just installed v0.0.8 and i get on my screen a "signal to turn off the screen is getting" (sorry for bad english)

I must to restart in safe video mode to reinstall old drivers. my screen is a LG Flatron L1710S (1280*1024 in 16bits)

Regards,

By rudolfc - Posted on January 25, 2004 - 09:49:32 (#10757)
Current version when comment was posted: 0.07

Hi,

Hit the spacebar on booting on the first moment you see the icons screen. Choose 'disable user add-ons' and continue booting.

This will take you to B/W video mode probably, so you can edit the nv.settings file for the softcursor setting.

Modify the file, save it, and just reboot again :-)

------

If you keep having trouble, mail me: I'll send you the latest CVS version (0.08-6 ATM).

There is a big improvement in setting up cursor and CRTC stuff that just _might_ fix the trouble you are experiencing. :-)

Best regards,

Rudolf.

softcursor ?

By malat - Posted on January 25, 2004 - 04:18:48 (#10755)
Current version when comment was posted: 0.07

How do I set the cursor to soft now that I can't move it ? Is there something easier than deinstall BeOS and reinstall ?
thanks

push aside any vesa from startup

By jdd - Posted on January 16, 2004 - 08:53:43 (#10595)
Current version when comment was posted: 0.07

There is a config file named -
/boot/home/config/settings/kernel/drivers/vesa

I think that was there from VesaAccepted, or sommat like it.

I renamed it to xx_vesa, and all the fiddlies I beefed about (in long-winded November rant) are all gone.

Kudos to Rudolf (and votes).

Overlay at last

By InactiveX - Posted on January 15, 2004 - 05:49:59 (#10569)
Current version when comment was posted: 0.07

Finally got overlay in VLC 0.7.0 with my TNT2Ultra. BeOS R5.0.3.

Thank you for all your work Rudolf. This gets my vote.

translation project

By rudolfc - Posted on December 6, 2003 - 11:19:50 (#9887)
Current version when comment was posted: 0.07

Hi,

You are right: it's stalled, because I needed to get the GeForce driver off the ground first :)
(Technix and me decided that I'd do the translation myself after all because otherwise we'd get stuck one way or the other.)

The good news is I have started on the translation again a week ago. I am starting from scratch again, in plain 'word' format. I figured I'd also do these first three chapters again, to remove possible faults that were introduced in the current online version. The new version will be in my own words. I'll publish it myself and relay this version to Technix.

People are free to improve it after that, as 'my own words' might result in some strange English sentences sometimes. Of course I could have made technical mistakes also, though I am still learning every day :).

I am keeping it up-to-date with my increasing knowledge until it's completed. I am working slow, doing a day every week or two: in which I'll lock-up myself in a remove quiet room ;-)

Rudolf.

Video Driver Creation Guide - Call for Dutchmen

By s_d - Posted on December 5, 2003 - 22:01:40 (#9879)
Current version when comment was posted: 0.07

Too sad that translation project of your wonderful BeVideoDriverBooks was stalled:(
I enjoyed reading of first chapters and found there a lot of helpful info and tips.

People, maybe someone with good knowledge of both languages can help Technix and Rudolf?

By rudolfc - Posted on December 5, 2003 - 17:34:25 (#9871)
Current version when comment was posted: 0.07

Hi,

Go cards should be recognized by the driver, but most of them won't actually work just yet with it if you are using the internal flatpanel.

If you connect an extenal monitor however, you should probably be able to safely use the driver, though some users reported the hardcursor not working (set hardcursor false in nv.settings as a workaround).

It might be overlay is also not working on some cards. You can disable use of that in the various mediaplayers.

2D acceleration should be up and running OK, so the speed will be as you expect from a 'normal' BeOS driver.

----

Currently my drivers are in the process of being placed in openBeOS CVS. Once that is complete (soon), I will be working on the drivers via CVS. I will keep releasing drivers as soon as I have improvements that are significant enough, as usual.

The first thing that will be done on this drive are the things listed under 'fixes' on my nVidia driver webpage, along with dualhead support on cards that can do that.

Once that is up and running, I'll implement laptop specific code, because this is the logical order for me to do things.

At the moment however, I am concentrating once again on the (open)BeOS Matrox driver. Version 0.15 will be released soon, containing important bugfixes and enhancements (see 'fixes' on the Matrox driver page).

After Matrox 0.15 is released, I will be working via CVS.

Hope this helps a bit. Please be patient: can't do it all at once! (Seemingly small fixes can take up a lot of time to workout. This is the nature of (graphics)drivers...)

Best regards,

Rudolf.

By DustBird - Posted on December 1, 2003 - 00:32:22 (#9803)
Current version when comment was posted: 0.07

I haven't really understood or followed the discussions around GF 2 Go! cards, but I wonder if any progress is made or if there are anything I can do to help progress... this VESA mode or whatever I am running sucks really hard... though I would like my graphics card to stay in a working condition, so please don't ask me to do anything dangerous... :-)

By the way, I am running Zeta RC1 with the 1st service pack installed. Just to let you know :-)

By rudolfc - Posted on November 24, 2003 - 22:15:55 (#9744)
Current version when comment was posted: 0.07

Hmm. I meant _leading_ # character of course ;-)

By rudolfc - Posted on November 24, 2003 - 22:13:16 (#9743)
Current version when comment was posted: 0.07

Hi,

If you want to specify the RAM amount manually, please remove the trailing # character on the line in the nv.settings file.

nForce1 (GF2 0x1a0) owners beware: Mail me or wait for V0.08 if the driver hangs your system, we tracked down a bug that needs to be removed. V0.04 is the latest version that should work ATM..

Sorry about that.

Dual head recommendation

By shatty - Posted on November 24, 2003 - 18:48:03 (#9734)
Current version when comment was posted: 0.07

Hello all,

A recommendation especially for shuttle box users but also for other dual head cards: try the other head if you have problems getting good video.

Andrew

nvidia on shuttle boxen

By shatty - Posted on November 24, 2003 - 18:46:54 (#9733)
Current version when comment was posted: 0.07

Hello fellow shuttle users,

I would like to seriously recommend you to upgrade your bios or you may (will?) have serious problems using the onboard video. (and more?) I did this and it solved a laundry list of problems.

-Andrew

nForce2 IGP (nv17 at 4x, not nv18) northbridge on Shuttle mn31n is cranky

By jdd - Posted on November 24, 2003 - 05:53:19 (#9727)
Current version when comment was posted: 0.07

tried this driver on nForce2 northbridge IGP of Shuttle mn31n, using older Be5peMaxEdV2b and older BeDevEd.
Also tried recent Be5peMaxEdV3, which includes this driver's (2003q3) nForce2 capability, according to driver changelog.

All of the above hw-platforms and OS versions boot into a humorously shifted-right desktop.

Icons are visible, and icon Titles are 99% legible, escept that .. although the top stuff is at the top, bottom stuff at bottom, alright ..

TheLeftEdgeOfScreen starts about 2/5th of the way across the screen.

The rightmost-portion of screen spills off the right hand side and magically reappears on the screen from left edge.

Workaround: This is corrected by turning OFF hardware cursor.
_ _ _ _ _ _ _ _ _ _

( Separately: .. told cmos-setup to use 32mB and told the nv.settings that it was 31mB; as suggested by driver docs. The accelerant line does not seem to make any difference. )

BeOS display resolution adjust'g utility _Screen_ would not allow any change away from 800x600, although WE DO a clue that the nvid driver is in use, because, unlike the VESA/fb modes, we ARE offered other resolutions.

I was able to increase the colors from 16bpp up to 32bpp, with the normal interaction and dialog & 15second approval-window. Same for bumping the refresh up to 75 from 61.0 Hz; at least, that is what Screen now says is being displayed, however, the monitor reports 38.1kHz/61.0Hz.

Attempts to make it run in 1024x768, 1154x864 or 1280x1024 show clearly wrong resulting HSync & VSync frequencies on my LGE 775FFT. When this monitor cannot resolve what a video card is telling it to do, a nifty internal chargen spells out the offending display params in a nice large report, on screen. When it _is_ happy, tap the menu key, for OnScreenDisplay of current operating freq'cys.

Further, coming from 800x600, and asking Screen for .. or 1154 .. or .. 1280 (and whatever bpp, Hz) delivers the monitor into a state beyond its ability to show ANY image, and its snooze/no-signal/power light quickly goes to no-signal state; until 15sec later. We do _not_ benefit from the monitor's chargen report when asking for those modes.

Maybe there is a hex number (or 0x02) being passed into a decimal coded variable.

Maybe I have not yet found the text-based config file that can give me about 6 or 9 workspaces, each with higher & higher resolutions and depths.

Hope this helps improve the driver. Cool that it is doing the Fx5200; that is a peppy, affordable card.

smiles
jdd

DVI support: not for now.

By rudolfc - Posted on November 17, 2003 - 18:55:26 (#9663)
Current version when comment was posted: 0.07

Hi,

DVI support is not planned because as far as I know there is no information available on this. :-/

If this changes, it can be added of course.

Best regards,

Rudolf.

DVI

By hps - Posted on November 17, 2003 - 05:15:30 (#9658)
Current version when comment was posted: 0.07

Does anyone know if DVI flatpanel support is planned for future releases?

By rudolfc - Posted on November 11, 2003 - 09:53:22 (#9589)
Current version when comment was posted: 0.07

Thanks for the update!
This behaviour awfully looks like another register lockdown: me programming registers but they don't get written. :-/

So your explanation about bitdepth makes perfect sense then.

I might have a clue already, I'll look into it. Got to fix one other bug two users reported before that though (0.04 working / 0.05 hanging).

Best regards,

Rudolf.

Re: Overlay (again)

By vegac - Posted on November 10, 2003 - 23:04:37 (#9578)
Current version when comment was posted: 0.07

Actually, I was just trying to change the bitdepth in the Screen Preferences, not the resolution, stupid typo in the previous post. Changing the bitdepth caused the screen to go off...it looked like BeOS was trying to do everything in 32bit, but it was still displaying in 16bit mode, hence everything magnified (half the data per pixel = only seeing half of the resolution, which could be why it was all scaled up etc.

By rudolfc - Posted on November 8, 2003 - 22:00:03 (#9554)
Current version when comment was posted: 0.07

Hi vegac,

So the overlay engine doesn't kick in at all on your card. Disabling colorkeying does by itself not mean menu's should disappear. That only happens when the engine is in fact working, and only in the exact area actually displaying video.

Thanks for this test, now we know another 'bit' more ;-)

About the screenprefs panel: you speak about changing resolution with it which messes up video. Well, that's to be expected. You may _not_ do that: only try to change the _colordepth_ with it.

32bit mode BTW mostly isn't supported in VESA modes: just 8 and 16 bit.

Best regards,

Rudolf.

Re: and more overlay

By vegac - Posted on November 6, 2003 - 22:15:27 (#9529)
Current version when comment was posted: 0.07

I did try recompiling the driver with bit 20 set to 0, however, overlay still did not work, but also, any popup menus over the overlay window (which was showing up grey) was will showing over it, not disappearing which I take it is odd.

For the color depth, I had tried setting the color depth to 32 in the vesa file (mode 1024 768 32) but that does not initialize my video, so I set it back to what it was (mode 1024 768 16) and it worked, then when attempting to set the screen resolution via the screen prefs window, the screen would get messed up (everything was large, duplicated, etc.)



	Comment Pages: << prev \| 1 \| 2 \| 3 \| 4 \| 5 \| 6 \| 7 \| next >>













			Recent Downloads - # 62 Total Downloads - # 30 Total Views - # 16 User Ratings - # 12




			Video Drivers




			1. BePodder - 9.80 2. QEMU - 9.68 3. ScummVM - 9.57 4. cpu_fix - 9.42 5. Jukebox - 9.40 6. libdl.so - 9.40 7. Haiku AGP busm... - 9.35 8. vim6 - 9.31 9. Beezer - 9.26 10. HandBrake - 9.25




			1. BeOS 5 Perso... - 13,615 2. Realtek RTL8... - 13,120 3. Ati Radeon G... - 12,587 4. Ensoniq Audio... - 7,570 5. ATI Rage 128... - 7,443 6. USB Joystick... - 5,665 7. Broadcom 440x... - 5,413 8. S3 Trio 64 v2... - 4,728 9. USB Serial dr... - 4,709 10. Intel Extreme... - 4,472




			You are not logged in. Login


	Unless otherwise noted, everything is copyright © 1999-2009 Haikuware. All Rights Reserved. For more legal trivia, take a gander at our Legal Stuff page and our Privacy Statement.