Andy Walls wrote: > On Sat, 2009-01-31 at 21:05 -0800, Scott Harris wrote: >> Andy Walls wrote: > >>> So all that's nice, but what to do? >>> >>> 1. With the HVR-1600 installed, you could try: >>> >>> a. unload the nvidia module(s) >>> b. manually fixup the PCI-AGP bridge and Nvidia device BARs >>> with setpci >>> c. reload the nvidia module >>> >>> Good luck. >>> >>> Andy >>> >> I can't tell you how much I appreciate you taking the time to delve that >> deeply into the issue. It is really greatly appreciated. >> >> I was able to spend 2-3 hours on this issue today between the kids naps. >> Good news and bad news. The good news is I now have everything working. > > Good. > >> The bad news is it had nothing to do with any of the suggestions above ;) > >> If you can't tell I was avoiding #1 as I've never done that before >> I figured it would take a long time to learn. > > I would have started with that. It's actually the most deterministic as > you are in full control. Yes the learning curve would have taken more > time, but you spent a lot of time anyway... ;)
Yeah, in the end I'll take the time to learn it, but I'm sure you know with kids any time you get to mess around with the computers is precious. > > >> So spent 30 minutes digging out the manual from the moving boxes and >> started reading through and happened to notice "AGP aperture size" in >> the bios. Hmmmmm I said. I check the current setting and it was at >> 128M. I boosted up to 256M and rebooted and now everything works great >> without and extra kernel command like options. > > > Right, but if you add or remove a card from your system (or enable > disbale other devices in your BIOS) your problem has a good chance of > returning. I'm likely to see this sooner rather than later as I'd like to add a 2nd 1600 to this machine now that I've demonstrated to myself that they work. > > The AGP aperature size is the window size set on the CPU-PCI host bridge > into main memory. It is not the size of the window set on the PCI-AGP > bridge. However, since that PCI-AGP bridge window was misaligned by > 128M, by bumping up some other window by 128M, you pushed the alignement > of all the other windows that get set after it by 128M. > > So again, I'm glad it worked, but realize if you change hardware > configuration, thus changing device memory windows, the problem will > likely resurface. Now would be a good time to learn how to use setpci > and write down some notes. :) Point taken. I'll spend the necessary time now that I have something at least working. Always a good thing to have more knowledge. > > >> Again, Andy, I can't tell you how much I appreciate you spending the >> time on such minute details. I really do appreciate it. > > You're welcome. I didn't spend a lot of time. I was mosty taking kids > to birthday parties and horseback riding lessons yesterday. Ah the days > when they take naps are gone for me... > And I bet so are the days of potty training and moving into big boy beds ;) which is what we spent the rest of the weekend and this week doing, hence my late reply. Thanks again for all the help, really appreciated. Scott _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
