Wasn’t sure where to post this but…
On my system, the Haiku nVidia driver crashes after a minute or so of use. Also, if I try to change the resolution, the whole screen gets scrambled and locks up. When I reboot, it has the new res, color depth, refresh rate (or whatever).
Wasn't sure where to post this but....On my system, the Haiku nVidia driver crashes after a minute or so of use. Also, if I try to change the resolution, the whole screen gets scrambled and locks up. When I reboot, it has the new res, color depth, refresh rate (or whatever).
Sorry, but we need to know more. Which type of card, what are your system specs, etc.
Wasn't sure where to post this but....On my system, the Haiku nVidia driver crashes after a minute or so of use. Also, if I try to change the resolution, the whole screen gets scrambled and locks up. When I reboot, it has the new res, color depth, refresh rate (or whatever).
Hi, my suggestion would be that you’d force PCI mode via nv.settings. What you describe looks like a comms lockup between mainboard and card.
That is, if you currently have the AGP busmanager installed.
If so, and forcing PCI mode solves the prob, you can try to modify the agp manager settings instead of forcing PCI mode. For instance, AGP-FW might be the specific feature locking up your system, or AGP-SB adressing.
On some mainboards, you can also modify the signal strenght settings in the system BIOS setup: might help without even touching any setting for the drivers.
–
If you don’t use AGP mode however, I currently don’t have a clue and I’d suggest sending a logfile to my Email adress: get it from the driver’s homepage, accessible via the bebits entry.
Best regards,
Rudolf Cornelissen.
(author of both the nvidia driver and Agp manager).
CPUGuy wrote:Wasn't sure where to post this but....On my system, the Haiku nVidia driver crashes after a minute or so of use. Also, if I try to change the resolution, the whole screen gets scrambled and locks up. When I reboot, it has the new res, color depth, refresh rate (or whatever).
Sorry, but we need to know more. Which type of card, what are your system specs, etc.
Geforce6800 card.
Asus A7n8x-E (nForce2)
CPUGuy wrote:Wasn't sure where to post this but....On my system, the Haiku nVidia driver crashes after a minute or so of use. Also, if I try to change the resolution, the whole screen gets scrambled and locks up. When I reboot, it has the new res, color depth, refresh rate (or whatever).
Hi, my suggestion would be that you’d force PCI mode via nv.settings. What you describe looks like a comms lockup between mainboard and card.
That is, if you currently have the AGP busmanager installed.If so, and forcing PCI mode solves the prob, you can try to modify the agp manager settings instead of forcing PCI mode. For instance, AGP-FW might be the specific feature locking up your system, or AGP-SB adressing.
On some mainboards, you can also modify the signal strenght settings in the system BIOS setup: might help without even touching any setting for the drivers.
–
If you don’t use AGP mode however, I currently don’t have a clue and I’d suggest sending a logfile to my Email adress: get it from the driver’s homepage, accessible via the bebits entry.
Best regards,
Rudolf Cornelissen.
(author of both the nvidia driver and Agp manager).
System still locks up. Oddly enough, everytime I reboot, the lockups happen quicker and quicker (from a couple mins til lockup, then just less and less each time, very strange).
I also noticed that when changing the resolution and refresh rate, the system locks up as well.
CPUGuy, hardware problems are completely out of question? Like coolers, temperatures?
I used to have this problem here, but it was a GeForceFX 5200 PCI on the first PCI Slot. The mobo is a M537D - the cheapest PC Chips model you can find. Changing the video card to the third slot solved de problem completely - I think that it should be related to some design problem on this cheap motherboard. I’ve heard other ppl complaining about timers and VRM’s not working when using this configuration (high-perf. video board on the two first PCI slots). Other GeForce cards behaved erratically on slot 1 and slot 2 (GeForce2 MX and GeForce4 MX). A simple Trident 9440 works without problems, though.
Since you are using AGP (at least I think so), I really can’t help, but I just wanted to say what happened to me.
Everything runs cool. Hell, I managed to accidently rip out the wires on my CPU cooler that connects it to my throttle, and as such, the dang thing is running at full speed all the time. It’s litterally as loud as a vacuum cleaner, and that’s with the case on.
Mobo’s not cheap, video card is an eVGA, so not really cheap either, not top of the line, but not cheap. It has the standard nVidia cooling heat pipes on it and such, with a big fan. Dont’ have any problems with it outside of BeOS.
Actually, when I went to install Zeta I had to run in video fail-safe mode, as the install would start up completely scrambled and freeze up immediately. Same thing if I try to boot with whatever BeOS uses as it’s default driver for this card. I have to run it in fail-safe mode to get it to boot at all, until I install the Haiku driver.
Who knows, maybe nVidia will start developing drivers for BeOS again now that Zeta is out.
Who knows, maybe nVidia will start developing drivers for BeOS again now that Zeta is out.
They never developed any in the first place, and they wouldn’t even give 3D specs to Be to create a closed-source 3D driver.
Only a few firms wrote their own drivers - Realtek, CMedia, Crystal Semi, and reportedly HP and Epson after R5 was out. No major graphics maker did more than provide spec books.
CPUGuy wrote:Who knows, maybe nVidia will start developing drivers for BeOS again now that Zeta is out.They never developed any in the first place, and they wouldn’t even give 3D specs to Be to create a closed-source 3D driver.
Only a few firms wrote their own drivers - Realtek, CMedia, Crystal Semi, and reportedly HP and Epson after R5 was out. No major graphics maker did more than provide spec books.
I beg to differ. Unless nVidia just provided it on their website, they did indeed develop them.
Bebits even has it at http://www.bebits.com/app/1622
MYOB wrote:CPUGuy wrote:Who knows, maybe nVidia will start developing drivers for BeOS again now that Zeta is out.They never developed any in the first place, and they wouldn’t even give 3D specs to Be to create a closed-source 3D driver.
Only a few firms wrote their own drivers - Realtek, CMedia, Crystal Semi, and reportedly HP and Epson after R5 was out. No major graphics maker did more than provide spec books.
I beg to differ. Unless nVidia just provided it on their website, they did indeed develop them.
Bebits even has it at http://www.bebits.com/app/1622
That was written with reverse-engineered specs, as anyone who used BeOS at that time will remember. Notice the publisher… not nVidia.
The nVidia copyright refers to the extremely tiny set of specs they released to XF86 in 1999, which covered some level of card operation. It was still written, entirely so, by Be and not nVidia.
CPUGuy wrote:MYOB wrote:CPUGuy wrote:Who knows, maybe nVidia will start developing drivers for BeOS again now that Zeta is out.They never developed any in the first place, and they wouldn’t even give 3D specs to Be to create a closed-source 3D driver.
Only a few firms wrote their own drivers - Realtek, CMedia, Crystal Semi, and reportedly HP and Epson after R5 was out. No major graphics maker did more than provide spec books.
I beg to differ. Unless nVidia just provided it on their website, they did indeed develop them.
Bebits even has it at http://www.bebits.com/app/1622
That was written with reverse-engineered specs, as anyone who used BeOS at that time will remember. Notice the publisher… not nVidia.
The nVidia copyright refers to the extremely tiny set of specs they released to XF86 in 1999, which covered some level of card operation. It was still written, entirely so, by Be and not nVidia.
You’re right, for some reason I read Be and through nVidia.
The drivers were, though, available from nVidia’s website at the time.
MYOB wrote:CPUGuy wrote:MYOB wrote:CPUGuy wrote:Who knows, maybe nVidia will start developing drivers for BeOS again now that Zeta is out.They never developed any in the first place, and they wouldn’t even give 3D specs to Be to create a closed-source 3D driver.
Only a few firms wrote their own drivers - Realtek, CMedia, Crystal Semi, and reportedly HP and Epson after R5 was out. No major graphics maker did more than provide spec books.
I beg to differ. Unless nVidia just provided it on their website, they did indeed develop them.
Bebits even has it at http://www.bebits.com/app/1622
That was written with reverse-engineered specs, as anyone who used BeOS at that time will remember. Notice the publisher… not nVidia.
The nVidia copyright refers to the extremely tiny set of specs they released to XF86 in 1999, which covered some level of card operation. It was still written, entirely so, by Be and not nVidia.
You’re right, for some reason I read Be and through nVidia.
The drivers were, though, available from nVidia’s website at the time.
And Matrox and ATi both link to either BeBits or Be for the drivers. No big thing - never means they wrote it.
Not that it matters, or helps me in this situation at all.
I’ve actually noticed that Zeta supports Athlon64 systems, P-400 systems, but not my nForce2 AthlonXP system (as far as getting decent sound drivers, or networking drivers, etc…)
I’ve got exactly the same problem. Also the latest cvs nvidia driver and also while in haiku or with disabled agp / no fw/sb . I also got 6800. Can i log this somehow in haiku, in a file on a disk instead of serial port?