Ever since I updated my network to include 3 routers my Wii has been grumpy. It continually included a few extra 0s after you input the settings. (I do not use DHCP).

You would enter the numbers

IP: 192.168.0.37

Router: 192.168.0.1

DNS: 192.168.0.1

and it would turn them into:

IP: 192.168.000.037

Router: 192.168.000.001

DNS: 192.168.000.001

This will not do! So finaly what I did was to NOT conferm settings and just press on until it made3 me test my settings. Low and behold they worked, but not if I confermed my settings first.

So a word to the wise when using a Wii with Wifi on a network with static IP addresses “Don’t conferm” your settings, just click the next arrow until you’ve looped through the settings and continue.

TTFN,

Justin

I’m a glutton for punishment I guess; but when a new version of what ever I’m using comes out, I must have it! In this case I’ve been running Ubuntu’s Intrepid Ibex 8.10 and VirtualBox 1.0.6 with XP inside (friggin’ Garmin Forerunner 405 w/not work with my Mac or this Linux box). All was working great, UNTIL I upgraded to VirtualBox 2.1.0.

USB has always been touch and go with me and VirtualBox but this time there wasn’t much on the WWW to help a guy out. Until I Googled my brains out! That’s when I ran across David Grant’s blog with just such a fix. Here is the link for his tutorial.

All you need to do in Ibex to get usb working with the non OSE version of VirtualBox (EG Download the package from VirtualBox.org so you may enable USB support. I never understood why someone would want to install the default package provided by Ubuntu when you can just as easily install it yourself with the .deb package provided by Sun/VirtualBox.

Anyhow; fire up your favorite terminal and lets get to the dirt:

First find out what the <GID> is for your vboxuser group -

$ grep vbox /etc/group
vboxusers:x:127:justin
(mine is 127)

Second fire up nano or gedit (gedit is just too slow for me) -

$ sudo nano -w /etc/init.d/mountkernfs.sh
or for the CLI challanged:
$ sudo gedit /etc/init.d/mountkernfs.sh

You’ll want to add this next line, just below the line where /proc is mounted -

domount usbfs "" /proc/bus/usb usbdevfs -onoexec,nosuid,nodev,devgid=<gid>,devmode=664

Change the <gid> to match yours from our first entry and save this duck.

Reboot and fire up that V-Box dawg! I struggled with this for about a week until I found Dave’s tutorial. In’Google Grand?

Justin

P.S. I hear there is some experimental OpenGL action going on in this version of VirtualBox as well. Hopefully it wont be long until I can fire up a clean install of Windows ’98 and run me some Carmageddon II: Carpocalypse Now!! HELL YEAH!

I’m running a pretty simple file server out of my mom’s old Gateway box (PIII 450mhz, 512mb Ram, 133fsb; a 4.5gig OS HDD, 320gig File Server HDD and a 500gig Backup HDD). It’s been running like a champ with minimal Debian installed (No monitor or keyboard) but today it simply “quit”. I came over and mashed the power button for a good hard restart and nothing. Not even a flicker of the hdd light. I broke down, fired up Gentoo’s minimal live cd and moved some of the /etc/ files over to the backup drive, then proceded to re-install Debian Etch from scratch again.

Rebooted and BLANK, nothing AGAIN! I headed to the Debian IRC room to ask for some direction on trouble shooting this, and they pretty much questioned me in circles. Guess I don’t usually ask the typical “noob” questions anymore. I know pretty much “how” to find whats wrong, but sometimes I hope that some one else could guide me along a path of eventual completion.

Anyhow, I went and downloaded a fresh ISO of Debian Lenny net install 80mb size and installed it. BLANK screen AGAIN! So I patiently changed the main OS hard drive, rebooted into the new net install cd this time, and walla .. BLANK! Only after boot to a hard drive though.

I got into the BIOS to see if “maybe” something was fishy and noticed right away the clock was more than a decade slow. I fixed that, rebooted to blackness again and reset the box again and dove into the BIOS. The clock was okay, so I went to boot order and it appeared “okay”. Then I went to IDE priority and walla! The HDD that had the OS on it wasn’t first, but last. So I moved it back up and rebooted into grun, and eventual login prompt. A reboot later, and it went black again with the hdd order all out of whack again. My assumption now is it needs a new BIOS battery. So tomorrow sometime I’ll head around to here and there in search of a new BIOS battery for this old mobo. My question is why didn’t it spit out that “No Operating System Found” error? Grrrr, hardware is evil when it gets old.

You can keep an eye on my boxes at http://munin.openlug.com . The breakdown is like this:

Ares – My Workstation (Ubuntu 8.10) P4 2.8ghz/1gig ram

Hecate – My kids HP Notebook (Ubuntu 8.10) Pentium M 1.6ghz/1gig ram

Metope – Livingroom Media Box (Mythbuntu 8.10) P4 3ghz/1gig ram

Neptune – File/Music Server (Debian Lenny) PII 450mhz/512mb ram

Pluto – Web Server Backup (Debian Etch) PIII 450mhz/96mb ram

Thor – Web Server (Ubuntu Server Edition 8.04 LTS) AMD 3200+ 1.8ghz/2gig ram (I friggin’ HATE AMD)

Titus – Bedroom Media Box (Mythbuntu 8.10) PIII 900mhz/512mb ram

Triton – Movie Server/MySQL Box (Debian Etch) Cyrix M 233mhz/131mb ram

Zeus – Kids Workstation (Ubuntu 8.10) P4 2.6ghz/1gig ram

We’ve also got two MacBook Pros, two iPod Touches and about 4 more computers in pieces waiting for my attention or a use. I’m thinking about building them to be backup computers for misc stuff around the house. Maybe even figure out how to make one control our houses lights and such. Saw that on YouTube once =) .