Linux.com

interesting observations about hardware detection

Posted by: Administrator on October 17, 2006 12:57 AM
At the outset of your review, you specified:

"I tested Nexenta under VMware and on a Pentium 4 notebook with 1GB RAM, an ATI Radeon R250, Intel sound card, built-in RealTek Ethernet, Intersil Prism wireless, and 60GB hard drive."

You then say that the install failed to detect your wireless card, improperly set the duplex of your Ethernet adapter, but sound and video worked great.

If you look in your lspci output, you will probably not see your vendor's hardware for the most part listed there. Why? Hmmm...

Well, maybe it's because you're testing your distro in a VIRTUAL MACHINE.

Depending on how you have configured VMware Server, and consequently the vmx file for the VM itself, THAT is the hardware that is being presented (virtual hardware), the installer has no visibility of the real metal it's running on. And VMware Server is a 'hosted' product, meaning it is itself running on top your native desktop OS.

The network speed reported is usually not correct in a VM anyway, and the network performance within the VM being poor is simply a result of the fact that you haven't installed the enhanced "VMware Etherenet Driver" as part of the VMware Server Tools package. Since this is based on OpenSolaris, you might get the recently-supported Solaris VMware Tools working to fix your speed issue, although this new Operating System almost certainly is not an officially supported Guest OS by VMware, so there are no custom tools rolled for it yet.

If you're going to test and review an operating system's ability to detect and install hardware drivers, at least give it access to the ACTUAL HARDWARE .

Jeesh.

#

Return to Nexenta combines OpenSolaris, GNU, and Ubuntu