Difference between revisions of "User:Nosebreaker"

From LinuxMCE
Jump to: navigation, search
Line 5: Line 5:
 
A logical diagram of my network:
 
A logical diagram of my network:
 
http://wiki.linuxmce.org/index.php/Image:Nosebreaker_lmce_diagram.png
 
http://wiki.linuxmce.org/index.php/Image:Nosebreaker_lmce_diagram.png
 +
 +
I am running 7.10
 
<h2>Core</h2>
 
<h2>Core</h2>
 
* Mainboard: [[ASUS M2N-SLI Deluxe]] (be sure to disable acpi in the BIOS or grub, see this link: http://wiki.linuxmce.org/index.php/ASUS_M2N-SLI_Deluxe)
 
* Mainboard: [[ASUS M2N-SLI Deluxe]] (be sure to disable acpi in the BIOS or grub, see this link: http://wiki.linuxmce.org/index.php/ASUS_M2N-SLI_Deluxe)

Revision as of 15:44, 27 July 2010


Setup

A logical diagram of my network: http://wiki.linuxmce.org/index.php/Image:Nosebreaker_lmce_diagram.png

I am running 7.10

Core

  • Mainboard: ASUS M2N-SLI Deluxe (be sure to disable acpi in the BIOS or grub, see this link: http://wiki.linuxmce.org/index.php/ASUS_M2N-SLI_Deluxe)
  • CPU: AMD 5000+
  • Memory: 4 GB Corsair DDR2-800
  • Case: APEVIA Black X-MASTER - I would spring for a better/larger case next time, this is a tight fit and the PSU is reported to have issues. Looks nice though!
  • HDD: 3x 1.5TB SATA in hardware raid5. software RAID5 (2.7TB in /home). I used this guide: http://ubuntuforums.org/showthread.php?t=699075
  • 3Ware 9650SE-4LPML RAID controller for hardware RAID5. Note that you need to create a boot volume in the bios since Ubuntu won't boot off a drive over 2TB!
  • NIC: Dual Onboard Gigabit (eth0 and eth1 swapped randomly once, I just swapped the wires after I realized the problem)
  • Video: XFX Geforce 8500
  • PVR-150 - installed, but not in use (I have a HDhomerun that I use instead)
  • Fiire Chief Remote (works great)
  • USB-UIRT (not used yet)
  • Panasonic TH-42PZ80U 42" 1080p plasma TV (be sure to remove any EDID, screen resolution, and refresh rate lines from your xorg.conf file otherwise it will overscan and be blurry).

So far this is working as a basic system, however I am not finished setting things up. The 1st onboard NIC shut off after I got Kubuntu installed and I had to add the 3Com for now, it appears to be an issue with the driver (see here: http://www.nvnews.net/vbulletin/showthread.php?t=89621). Note: this was resolved after I reinstalled from scratch, also the sound started working properly. Apparently Ubuntu doesn't like it when you change motherboards after it is installed.

I did a normal Kubuntu 7.10 install following the RAID5 instructions in the link above first, then I installed LMCE with the CD's.

Media Director

  • Mainboard: Jetway JNC62K (FYI - comes with a slim fan/cooler)
  • Processor: AMD 4850e (45W)
  • RAM: Crucial 2GB stick
  • Video: onboard NVidia 8200

I discovered that if I have certain USB devices plugged in while this is doing a diskless boot, it fails. I had to disable one of the onboard NIC's to get it to start to boot off the network. I also had to use the r8168 fix (see my fun here). I had to manually install the nvidia driver as well, but this board is working now.

I have 2 of these, one in a Morex T-3310 case and the other is a INWIN BM639 (it can hold a regular DVD and one hard drive. Be sure to get 45W processors with these cases, as the power supplies are only about 70W total!

Mobile Orbiters

  • Fujitsu LT500C First try I used a nuforce skin, which doesn't seem to work at all. It receives updates but clicking on buttons does nothing. The UI1 skin works fine, it runs at 800x600 without issue. I have a generic 802.11g PCMCIA card in here for wireless. This device runs Windows 2000.

Home Automation

Z-Wave

  • Micasaverde USB stick (not working yet, sent it back for replacement)
  • Generic Motion Sensor (like in 0704 video)
  • Generic Appliance Module
  • Generic Lamp Modules

This section is a bit outdated, I have many wall switches and wall dimmers now. I discovered a problem where if you unplug one or more zwave unit(s) from the system it takes forever to send the signal to other units. I first noticed my new wall switches weren't working, so I thought it was the units but all I had to do was plug in all the modules that I had added to the system and then it worked fine again. Someone else postulated that it was trying to send to that unit, and the system was bogged down.