I'm guessing that it isn't to do with uni-multi processor, and more to specific nvidia card. The only thing that Sax2 is going to do is change monitor scanmodes, modelines, dpi, etc (depending on what is reported by the video card about what monitor is there and what it can do) and video card information and driver. Therefore, my money is on Sax2's ability to recognize the card itself. There have been some discussions I've seen on this list about Sax2 not recognizing a card (not have the serial number in data-base). Also, the 629 driver does some more in-depth (I forget what it is called exactly, hmmm) ?DDE? detecting of modes and adjusts modelines. That is why I can't use the 629 driver, I have a widescreen display. If the card you're having trouble with is a newer card or the attached monitor is new tech, this would make sense. So my doing the nv -> nvidia by hand, you leave the older setting in the XF86Config and don't let Sax2 try to be more clever. When this works, it will be nice. Typical growing pains of new tech/features. The difference between GNU/Linux and M$ is that nobody is trying to hide anything in Linux, so you can still override the new stuff and fix yourself! Thank god for open-source! B-) On Tuesday 21 December 2004 05:12 pm, Peter B Van Campen wrote:
On Tuesday 21 December 2004 5:40 pm, Brad Bourn wrote:
make sure XF86Config says 'nvidia' for driver and not 'nv'
make sure you get splash screen on boot
try without sax2
B-)
Yowzers!!!!!!! That worked!?! Got the NVIDIA Logo flash and glxinfo sez "Yes". Now just why does SAX2 mess the proceess up? Itseems to be SMP related since I (with Anders help) got 6629 working perfectly on a uni-processor system = AMD XP2800 with a nvidia 5200 card.
And why is the 'skip sax2' required. There is a screw-up there somewhere!
Thanks Brad! .............. PeterB -- --
Proud SUSE user since 5.2 Loving SUSE 9.2 My BLOG == http://vancampen.org/blog
--