This awesome blog post at MitchRibar.com outlined a great way to improve YouTube’s sometimes crappy load times and performance. It works very well and I’m glad somebody took the time to share this knowledge on the internet.
His method is a local client only option, so if you have alot of computers like I do it may be a pain to set this up on every computer, phone, etc that you have. Instead, I decided to try and block it at my router which I happened to have flashed with DD-WRT.
Here’s how you do it!
Log into your router’s admin interface
Click on “Administration” and then select the “Commands” tab
Paste the following lines into the commands text area: iptables -I FORWARD -s 126.96.36.199/24 -j DROP
iptables -I FORWARD -s 188.8.131.52/16 -j DROP
Now click “Save Firewall”
You should now notice a firewall section with these lines added, which looks like this:
Congratulations! You’ve now improved YouTube’s performance on your entire network. I did this on a DD-WRT enabled router; but this could be done on any device that runs iptables. Open-WRT, Tomato, Linux boxes, etc. If you have ipables, give it a try!
When I was trying to find a way to create an Integrity VM, I had to do alot of research. It was difficult to find updated information and correct syntax for later builds of HP-UX and later versions of the VM software. Being the thoughtful and forward thinking internet citizen that I am, I figured I’d give back a little…
So, without further adieu, here is the steps necessary to create an HP-UX Integrity VM on HP-UX 11.31 using HPVM version 6.x
Create a virtual switch first
hpvmnet -c -S <vswitchname> -n <lanID>
The LanID references the numeric portion of the name. Run netstat -in to find yours
Example: hpvmnet -c -S vswitch1 -n 10
Boot up the switch by running: hpvmnet -b -S <vswitchname>
Run hpvmnet to see a status
Now, create the virtual machine
hpvmcreate -P <servername> -l <label or description> -O HPUX -a network:avio_lan::vswitch:<vswitchname>
This creates the VM with a default network connection.
hpvmmodify -P <servername> -a dvd:avio_stor::file:/path/to/HPUX1131.iso
This will create a virtual DVD device connected to an iso for installation later. If you’re going to install from ignite or something else, dont worry about this part
hpvmmodify -P <servername> -a disk:avio_stor::lv:/dev/vgname/rdevice
This is adding storage for the VM to use. You could also add a disk image file instead of a real logical volume if you wanted
To create a disk image file, run something like hpvmdevmgmt -A -S 10G /path/to/vmdir/diskimage.fd
Your VM is now created! You can run hpvmstart -P <vmname> to boot the VM up
If you need to install via an iso, just connect to the console by using hpvmconsole -P <vmname> and then selecting boot to file from the boot menu, and then selecting removable media. Or, just wait and it should boot automatically if you added the DVD device.
hpvmstart, hpvmstatus, hpvmstop are useful commands to manage your VMs
1/18/2012 was a very interesting day on the Internet.
I was somehow infatuated with what websites were doing to show their opposition and protest to the SOPA and PIPA bills. I think I liked reddit’s blackout page the best of anybody that I personally saw, but there was certainly alot of creativity across the board.
This blog captured many of the screenshots of big players in the blackout day. They somehow left out my site on that blog, so I’ll go ahead and share what my site looked like with you yesterday.
This social media age has ignited a fight in the common people. It’s awesome to see. From insane corporate strategies [Netflix], to the occupy movements, to protests that literally changed the landscape of countries: A small spark can ignite a firestorm.
Where the SOPA and PIPA bills will end up remains to be seen, but yesterday was pretty historic. The Internet bonded together and certainly made an impact on a very key turning point in the information age.
Yesterday was supremely significant, yes, but it’s certainly not over. Watch the video. Share it with friends. Use the form to contact somebody and tell them how you feel. Part of the solution.
This is a viral protest, and many sites are taking part in this campaign. Certainly, ericvb.com and its 50 visits per day are merely a drop in an olympic size swimming pool – but we are all swimming in that pool.
The overall strategy by Google to unify its services drew them to the conclusion that they have to force all Google Reader users to begin using Google+ to fulfill the social aspect of Reader. Friending, following others, and commenting on shared items within Reader would now be discontinued…
I don’t think this really hit me until it actually happened.
As I was greeted with the “Welcome to the new Reader” message last week, I finally got a feel for how big this change truly was. Usually, my first click is to “People you follow” when I log into Google Reader. Well, that’s now gone. There’s no longer a simple way to see shared items, to comment on them, or to get a quick overview of what items my friends are reading. Instead, I’m stuck muddling through Google+ posts trying to find a way to make this social world work again.
I just feel completely lost in the new Reader. The extra clicks/page views necessary to get the same functionality in Google+ make it difficult and inefficient. I don’t like the look of the new Reader. I don’t like having to go back and forth between 2 different sites to see and comment on shared items. It’s just a sad state of affairs. I’m sick of companies trying to force customers/users into a model that they obviously don’t support.
As of yet, there isn’t a very solid alternative to Google Reader. I’ve researched and tested a few, but the social aspect is a key that is missing in nearly every contender. I’m looking forward to trying out hivemined, which seems to be getting alot of e-buzz as a true Google Reader alternative. Until then, I’m struggling to adapt to a new way of doing this. A significant portion of my friends and my own internet activity was spent inside Google Reader, and at this point we’re all trying to re-group as the table cloth was pulled out from under us.
For some time, it appeared that the dreaded “RRoD” had overlooked my Xbox 360 console.
Over the years, I’ve watched as my brother, friends, family members, and co-workers had to send their consoles into Microsoft for warranty repair. Sometimes even on multiple occasions. The ruthless crimson-ringed beast seemed to spare no one. In fact, I’m almost positive that I do not know a single person that has an early-model Xbox that has not “red ringed” at some point.
On Thursday night, as I went to launch my newly downloaded Battle Field 3 beta, my Xbox beeped loudly and froze up. I powered it off, and powered it back on – only for it to freeze at the Xbox boot screen animation. A second power off/on showed me a most unpleasant site framed in a very distinctly reddish hue. It seemed, much like death itself stalking the cast of a Final Destination movie, that this unmerciful demon of console demise had at last found its misguided way to my Xbox
Personally, I feel this has been a long time coming. I’ve somehow managed to dodge this bullet for years. Probably the fact that I have the “2nd printing” of the Xbox 360 Pro with an HDMI port bought me this extra lease on life, but who can be sure. After a night’s rest, the RRoD continued in the morning. I decided it was time to take corrective actions. Microsoft extended warranty coverage for this issue for a period of 3 years. Since I bought my Xbox in November of 2007, I was 11 months past my warranty coverage. This leaves my 1st option: Send the console into Microsoft for 100 dollar repair/refurb.
Since I like 100 dollars in my bank account, I did not even consider this option.
My next thought is to replace the console. I immediately shop on Amazon and Newegg, but I’m not really enjoying the notion of paying $200 plus for a new Xbox and paying for a data migration kit.
A third option, much more my style, began to creep into my frazzled mind. “Why not try to actually try to fix this myself?”. I am a fairly technically savvy person with a family history of MacGyvering – so I saw fit to AT THE VERY LEAST lace up, touch gloves, and slug it out for a few rounds with the RRoD. I commenced work immediately.
I didn’t use a guide to open up my Xbox; but I should have. I used brute force and a couple of plastic tabs that hold the top plastic bezel in place are now snapped off. It was difficult to get this console open my first time, and it probably took me 45 minutes to have the thing completely disassembled to where I had the system board out and all other pieces off to the side.
With everything opened up and my warranty (or, possibility of ever having one) now completely devoid, I started looking at possible fixes. Both the CPU and GPU heat-sinks seemed firmly attached, so I didn’t believe that to be my problem. Overall, the system was pretty clean. I blew out some of the dust plugging up the fans and heat-sinks overall, but that definitely wasn’t enough of a backup to cause a RRoD in my opinion.
So, I decided it must be the memory chips on the bottom of the Xbox system board. These 4 chips sit on the bottom side where no fan/cooling will ever reach them. Microsoft tried to alleviate this by attaching some chintzy thermal pads, but those things were basically a band aid with some high density foam attached to the chips.
I removed the pads and cleaned the memory chips. I used this guide to replace those pads with some custom “penny based” copper heat sinks. You take 2 pennies, wrap them together with electrical tape, and stick them onto those 4 memory chips. From the pic, you can see I have a tube of high-temperature synthetic grease which I layered between the chip and pennies.
The entire process was a pain. Getting the system back together was harder than taking it apart. It’s difficult to get everything to line up correctly while keeping those pennies in place on the chips. After I got it part-way back together, I test-booted the Xbox only to find that the red ring persisted. Even worse, this time it seemed to red ring before even powering on the fans. I took this to mean that I had a short somewhere; and indeed it did seem that the system board was crooked from my penny application. I adjusted screw tension in several places, and removed screws completely in other places – and after some finagling I was able to get the system to boot to it’s “normal” red ring where the fans and everything at least had power.
Further research indicated that the RRoD error code may persist even if you have fixed the problem. The easiest way to clear that error code was to replace it with another error code and/or reset the onboard chips. The easiest way to do THAT is to simply overheat your Xbox. Shouldn’t be too hard, right? I mean, the thing runs at nuclear temperature even in a ventialted area. Google reported the “towel trick” was the key, and I watched this entertaining guy do said trick – which apparently means cooking your Xbox for 20-25 minutes.
Since I had the thing apart already, I decided to expedite this baking process by booting it up without the fans installed. So I turned it on, then wrapped the console in a thick fleece blanket, and about 6 minutes later it completely powered off. I tried to boot it up again, and I got 2 red rings vs 3 (indicating overheat, yay!). So, I let it cool off for about 10 minutes before trying again…
It BOOTED!!! I let it idle for a bit, played some Trials, verified live connectivity, etc etc. Everything was looking great! The penny fix in combination with an overheat to clear it out seemed to do the trick for me.
I put the unit back together, and by this point I was very comfortable getting it back together correctly. I tightened all the screws, got all the tabs back in place, buttoned it up completely.
With everything hooked back up; I tested the console for awhile playing various games. I played Trials. I played Battlefield 3 beta. I reviewed my settings and live connectivity again… And after 1-2 hours, it was still working fine.
I have continued playing throughout the weekend with 2-3 hours per session; totaling probably 8-10 hours of game play; and I feel like everything is very stable. No more red rings. I have done multiple power on/offs, disconnected/reconnected all hardware and storage devices; and at this time I feel very good about my Xbox and its “Non RRoD” status.
In fact, everyone in the family does!
Take that, RRoD… I looked through your intimidating vengeful red eye directly into your villainous soul. After a hard-fought battle, I am confident that on this day, good has triumphed over evil…
This penny fix was only temporary. The red-ring of death resurfaced about 10 days later and asked me for a rematch.
This time I pulled out all the stops and researched every possible fix that typically works for the RRoD. Ultimately, I ended up at 2 main fixes:
Replacing the X-clamps that hold the heat syncs in place for the GPU and CPU, combined with replacing the thermal paste on the cores/heatsinks
Purchase a heat gun and use it to refresh the solder connections by heating the bottom of the circuit board.
I followed this video tutorial pretty much exactly. He does a great job explaining the work done, and gives exact specs for the hardware that replaces the crappy X-clamps. I took it one step further and drilled a grid of holes in the top of my Xbox to improve the airflow over top of the heatsinks.
This work seems to have officially bested the RRoD – as of now it’s been operating for about a month without any further issues. I’ve also noticed it running much quieter now that I’ve drilled the holes, so I think that has improved the airflow and makes it so my fans have to do much less work to move the same amount of air.