Crucial 16GB Very Low Profile RDIMM Memory Module

Crucial announced the CT204872BV1067Q 16GB DDR3-1066MHz Very Low Profile  RDIMM memory module, the one that is prevalently  used in blade servers and to run memory concentrated applications like server virtualization. It has the dimensions of just 18.75mm in height, the Very Low Profile form factor is ideal for decreasing space taken by memory and enable  for huge airflow through the body of the server,to help in the decrease of thermal power consumption and eventually contributing to diminished cooling expense.

240-pin DIMMs are used to grant DDR3 SDRAM memory for desktop PCs. DDR3 is a leading-edge production of memory with an enhanced architecture that allows it to broadcast data very quick.Dual inline memory module (DIMM) comprise of  many of memory components that are bound to a printed circuit board. The gold pins on the bottom of the DIMM supply a connection intermediate  to the module and a socket on a great in size printed circuit board. The pins on the front and back of a DIMM are not connected to from one to the otherother.

Memory Modules are available in 4,8,16 GB of different options.The price is $199.99 for 4GB, $306.99 for 8GB and $724.99 for 16GB.

Tags:-Crucial RDIMM Memory ,Crucial RDIMM Memory  specs, Crucial RDIMM Memory  features,  Crucial RDIMM Memory  colors, Crucial RDIMM Memory  weight, Crucial RDIMM Memory  functions, Crucial RDIMM Memory  compare, Crucial RDIMM Memory  comments, Crucial RDIMM Memory  reviews, Crucial RDIMM Memory  overviews, Crucial RDIMM Memory  price, Crucial RDIMM Memory  price in India, Crucial RDIMM Memory  pictures, Crucial RDIMM Memory  launch,  Crucial RDIMM Memory  Bluetooth,Crucial RDIMM Memory

Read more...

New asus-switcheroo module

Akex Williamson at RedHat, one of the hybrid graphics linux team members, has written a new kernel module called asus-switcheroo:

https://github.com/awilliam/asus-switcheroo/blob/master/README

This module, that has mostly been tested on an Asus UL30VT and works only with the nouveau drivers, can switch from the Intel to the Nvidia card with the nouveau drivers by presenting the Nvidia card to the Intel drivers. It currently uses jprobe to notify the presence or absence of the nvidia card to the intel i915 driver.

Although using the discrete graphics card with this module is still experimental at the time of this writing (20110419), the module should allow for using both cards with the nouveau drivers, provided the adequate ACPI methods are present in the laptop's BIOS.

Please use the mailing list to give your feedback on this module:

https://launchpad.net/~hybrid-graphics-linux

Read more...

Linux Nouveau intel/nvidia working with github.com/awilliam module for Asus UL30VT - Asus UL50VT - Asus UL80VT 1 0 - HP dm3 - HP SLIC-MPC - Lenovo T410 2516CTO - Lenovo T410s - Lenovo T510 - Sony Vaio VPCZ136GG - Sony Vaio VPCZ13V9E - Sony VGN-Z51XG - Sony VPCZ12C5E

Read more...

github.com/awilliam module explained

An updated README for this module now provides a theory of operation for the vga switcheroo:

https://github.com/awilliam/asus-switcheroo/blob/master/README

To switch between the integrated and discrete cards, a vga switcher subsystem exists in recent Linux kernels that takes into account different clients - the cards - and handles them according to what the user wants - with the handler.

Right now a client has to be associated to an X session, so to switch clients, one has to logout, switch and login again. The Optimus PRIME project for multi-GPU support aims at a more seamless use of both cards at the same time (see http://xorg.freedesktop.org/wiki/SummerOfCodeIdeas).

Back to the awilliam's module, the handler primarily manages the multiplexing of for the displays between the devices using ACPI. This module is an ACPI based handler that makes the right ACPI calls to notify the cards to the X session.

Now one of the tricky bits is that one has to make use of the available ACPI calls, and these are sometimes vendor-specific. A bunch of ASUS models and a few other laptop models have the MXMX-MXDS ACPI method, which works like this: the handler first calls the MXMX method followed by the MXDS method to produce the right hardware switch. The parameters don't seem to matter much for the tested laptops so far, but we might find that this is different for other laptop models. This vendor-specific ACPI calling is not ideal, and it would be better to have the details of the more generic WMI MXM interface, that extends ACPI.

More on this soon.

 

Read more...