search for: chipset

Is this expected result for Chipset: G98 (NV98)? $ modinfo nvidia -F version 304.123 $ stat -c %s mmiotrace.log 134659197 $ file mmiotrace.log mmiotrace.log: ASCII text $ grep -i lost mmiotrace.log ; echo $? 1 $ ./envytools/rnn/demmio -f mmiotrace.log | perl -e 'open($fh409c, ">fuc409c"); open($fh409d, "&gt...

...nva8.ctxvals"); -MODULE_FIRMWARE("nouveau/nvaa.ctxprog"); -MODULE_FIRMWARE("nouveau/nvaa.ctxvals"); -MODULE_FIRMWARE("nouveau/nvac.ctxprog"); -MODULE_FIRMWARE("nouveau/nvac.ctxvals"); +#include "nouveau_grctx.h" #define IS_G80 ((dev_priv->chipset & 0xf0) == 0x50) @@ -111,9 +88,34 @@ nv50_graph_init_ctxctl(struct drm_device *dev) NV_DEBUG(dev, "\n"); - nouveau_grctx_prog_load(dev); - if (!dev_priv->engine.graph.ctxprog) - dev_priv->engine.graph.accel_blocked = true; + if (nouveau_ctxfw) { + nouveau_grctx_prog_lo...

4.1.8-200.fc22.x86_64 dmesg: [ 11.809467] nouveau [ DEVICE][0000:02:00.0] BOOT0 : 0x098200a2 [ 11.809493] nouveau [ DEVICE][0000:02:00.0] Chipset: G98 (NV98) [ 11.809508] nouveau [ DEVICE][0000:02:00.0] Family : NV50 4.3.0-0.rc4.git0.1.fc24.x86_64 dmesg: [ 2.483843] nouveau 0000:02:00.0: NVIDIA G98 (098200a2) Where vanished these Chipset & Family super cool lines?

Hello poma, The chipset didn't disappear and is still displayed: it is the G98 you get on the "[ 2.483843] nouveau 0000:02:00.0: NVIDIA G98 (098200a2)" line. The "NV98" was the "Nouveau" chipset, but the switch was made to use the same naming as NVIDIA. So rather than displaying both t...

...ted the backport of Linux commit 03bbcb2e I notice a certain discrepancy with the Xen commit having the same purpose as well as with the actual specification updates: The Linux solution keys off of device IDs 3403 and 3406, as listed in the specification update, but this way fails to cover the X58 chipset, which has - under different numbers (62 and 69) - the same errata (the Linux commit message also only mentions erratum 53 for the 55x0 chipsets, albeit I believe 47 is as much of an issue there as it is for Xen). The Xen solution keys off of ID 342e, with no explanation in the commit description...

On 02.12.2014 14:40, Ilia Mirkin wrote: > On Tue, Dec 2, 2014 at 8:38 AM, poma <pomidorabelisima at gmail.com> wrote: >> Is this expected result for Chipset: G98 (NV98)? > > Yep, 100% expected. [Perhaps you might glance at the wiki page you got > that from for clues as to why.] > "You basically never need to do the mmiotrace, unless you're a nouveau developer."? I did everything by the book[1]. Though I don't need th...

...tria Matthew A. Wolf pS.: THANKS a whole lot for such a fine piece of software! ppS.: SORRY! Forgot the output of lspci in the last mail - here is the output from lspci in the dom0: =================================================================== 00:00.0 Host bridge: Intel Corporation 5000V Chipset Memory Controller Hub (rev b1) 00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 2-3 (rev b1) 00:03.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 (rev b1) 00:08.0 System peripheral: Intel Corporation 5000 Series Chipset DMA Engine (rev b1)...

...ooking at the pci passthrough requirements of Xen4.1 on the VTdHowTo<http://wiki.xensource.com/xenwiki/VTdHowTo>page, I am a little puzzled with the fact that only Intel Core2Duo (with VT-x), Core2Quad, i7 and Core i5 (vPro Brand) CPU''s are supported while motherboards with the i55x0 chipset are supported (for example the Supermicro server mainboard: X8DT3-F<http://www.supermicro.com/products/motherboard/QPI/5500/X8DT3-F.cfm> ). The irony in all this it that above this list of supported CPU''s and motherboards is the statement "Note that in addition to the motherboa...

Can someone make a recommedation as far as best chipset for Centos 5.0 or 5..1 using a Q6600 series CPU?with chipsets that have onboard VGA?? From poking around it looks like the G33 and P35 are not supported or have problems until the newer 2.6.22 kernel (the?iso's appear to be earlier than that, think it was?.18)?? So I am considering boards with...

On Tue, Dec 2, 2014 at 8:38 AM, poma <pomidorabelisima at gmail.com> wrote: > Is this expected result for Chipset: G98 (NV98)? Yep, 100% expected. [Perhaps you might glance at the wiki page you got that from for clues as to why.] > > $ modinfo nvidia -F version > 304.123 > > $ stat -c %s mmiotrace.log > 134659197 > > $ file mmiotrace.log > mmiotrace.log: ASCII text > > $ grep...

...gging a drive into ports 5 or 6 generates no events in dmesg or the system log... it's like those ports are turned off or something. I've checked the bios, and nothing jumped out at me as an obvious switch that says "turn on ports 5 and 6". This board is using Intel's 5000P chipset, and linux appears to have chosen the generic intel_piix driver to access the onboard sata. I have a second sata hba on the system, a supermicro 8 port card, which loads up later using the sata_mv driver, It has no problems right now, and is currently Any ideas? Thanks, Gordon I'm running...

I have 2 new boxes that I cannot use yet because of problems supporting these newer chipsets in 5.1. Does anyone know when the CD version of 5.0 x86-64 that has support for these chipsets be available on any on a Centos mirror? Has the support for these chipsets been added to yum yet? Here are my latest results with these chipsets and Centos 5.1 1. Asus P5K, E6850, P35 Chipset: Doe...

Hello all..... I would like to know if anyone here has had good experience with this Supermicro motherboard.....http://supermicro.com/products/motherboard/P4/E7221/P8SCT.cfm I am thinking about using it in an entry level mail and file server with a 3ware card and 200 GB SATA drives. Cost is a factor here otherwise I would go for an Opteron board instead. JC

...vpe_mb_dct_blocks_84(dec, mb); + else + nouveau_vpe_mb_dct_blocks_31(dec, mb); + } else { nouveau_vpe_mb_data_blocks(dec, mb); + } } } @@ -528,6 +557,8 @@ nouveau_create_decoder(struct pipe_context *context, goto vl; if (screen->device->chipset >= 0x98 && screen->device->chipset != 0xa0) goto vl; + if (screen->device->chipset < 0x31) + goto vl; dec = CALLOC_STRUCT(nouveau_decoder); if (!dec) @@ -577,6 +608,7 @@ nouveau_create_decoder(struct pipe_context *context, dec->base.end_frame...

Hello, Am Donnerstag, 3. Oktober 2019, 01:10:58 CEST schrieb Akemi Yagi: > On Wed, Oct 2, 2019 at 3:35 PM G?nther J. Niederwimmer <gjn at gjn.priv.at> wrote: > > This Board have 2 Controller!? > > 00:1f.2 RAID bus controller: Intel Corporation C600/X79 series chipset > > SATA > > RAID Controller (rev 06) > > > > On this controller all drives are found and it is possible to create a > > Raid1! > > > > 07:00.0 Serial Attached SCSI controller: Intel Corporation C602 chipset > > 4-Port SATA Storage Control Unit (rev...

...edu> --- src/nv_driver.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/nv_driver.c b/src/nv_driver.c index b83b822..44e7496 100644 --- a/src/nv_driver.c +++ b/src/nv_driver.c @@ -836,7 +836,7 @@ NVPreInit(ScrnInfoPtr pScrn, int flags) dev = pNv->dev; pScrn->chipset = malloc(sizeof(char) * 25); - sprintf(pScrn->chipset, "NVIDIA NV%02x", dev->chipset); + sprintf(pScrn->chipset, "NVIDIA NV%02X", dev->chipset); xf86DrvMsg(pScrn->scrnIndex, X_PROBED, "Chipset: \"%s\"\n", pScrn->chipset); switch (dev-&...

The following 2 patches make it possible to run Mesa programs on GK20A (Tegra K1). GK20A is very similar to GK104, but uses a new (backward-compatible) 3D class as well as the same ISA as GK110 (SM35). Taking these differences into account is sufficient to successfully render simple off-screen buffers. Alexandre Courbot (2): nvc0: add GK20A 3D class nvc0: use SM35 ISA with GK20A

...4.0 from Squeeze (xen-hypervisor-4.0-amd64) the behavior is the same (it hangs with Linux 3.2). The systems are all running 2 quad-core Xeon (E5320 or E5405) with 32Gb to 64Gb of RAM, with Supermicro X7DB8 motherboards. Here is a LSPCI on one of them : 00:00.0 Host bridge: Intel Corporation 5000P Chipset Memory Controller Hub (rev b1) 00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 2-3 (rev b1) 00:04.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 4-5 (rev b1) 00:06.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 6-7 (rev...

http://www.intel.com/content/www/us/en/chipsets/5520-and-5500-chipset-ioh-specification-update.html Stepping B-3 has two errata (#47 and #53) related to Interrupt remapping, to which the workaround is for the BIOS to completely disable interrupt remapping. These errata are fixed in stepping C-2. Unfortunately this chipset is very common and...

...address 7,error -110 ///////////////////////////////////////////////////////// the following infomation is the out of lspci on my Dell PowerEndger 1950: ////////////////////////////////////////////////////////////////////////////////////////////////// 00:00.0 Host bridge: Intel Corporation 5000X Chipset Memory Controller Hub (rev 12) 00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 2 (rev 12) 00:03.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 (rev 12) 00:04.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 4-5 (rev 12)...