Step 1: Upgrade my wireless router's firmware
I have an old US Robotics 8054 router/wireless access point. It was running the original firmware (1.17, Fri, 25 July 2003) from when I bought it two years ago. I had been noticing some problems with it. The primary problem is that it seems to reset frequently on long sessions, e.g. long downloads or long VPN connections while working at home all day. It's very annoying. Since I was about to download a rather large set of files (the FC4 ISO images), it seemed like a good time to look for a fix.
I decided that the easiest possible fix would be to upgrade to the latest firmware. I downloaded rev. 1.67b44 from USR's 8054 support page I installed the new firmware via the 8054's web interface, and it looks like it went OK:
I assumed the old settings file wouldn't work and re-entered all the settings by hand. One interesting side effect of the upgrade is that I couldn't use my old SSID. The old SSID had two space characters in it, which the new firmware disallowed. I removed the spaces from the SSID and reset all the WiFi adapters in the house to use the new SSID.
Step 2: Deal with SpeakEasy
At my old home, I had a Comcast cable modem connection to the Internet. Everything was great. Then I moved. At the new place, I ordered Comcast Internet service again, but this time, I couldn't get an IP address. Their technicians and support people weren't very helpful, so I canceled the order.
I had heard good things about SpeakEasy DSL, so I decided to give them a try. The installation was a piece of cake.
One nice thing about SpeakEasy is that they encourage you to share your Internet connection with your neighbors. I had registered to be a provider (although I don't have any subscribers yet--if you are interested, subscribe here, using subscription code
kasperowski). My subscribers need to know my SSID, so I logged in to my SpeakEasy NetShare account and changed the SSID.
The next thing I had to do was deal with one final installation issue. SpeakEasy's technical support staff informed me that I wasn't getting the full bandwidth that I ordered. I still haven't clarified whether I ordered 3 or 6 Mbps download bandwidth, but that's irrelevant because my actual download bandwidth was about 1750 kbps. (SpeakEasy has a nice test tool on their web site that you can use to measure the bandwidth you are getting.) As I was about to download some large files (the FC4 ISOs), it was time to take care of this. I called SpeakEasy and asked for help. Their technical support guy was very helpful. He ran some tests on my loop and noticed some line noise. He agreed that the bandwidth I was receiving was lower than I ordered, but explained that because my home is about 1300 feet from the central office, 1.5 Mbps is probably the best I can hope for. I agreed, and he downgraded my account so I won't have to pay as much.
Step 3: Download FC4
BitTorrent is the best way to download a Linux distribution, so I downloaded the FC4 torrent.
BitTorrent doesn't give you any improvement over a single-source download if you don't also act as a server, so I opened up the BitTorrent ports on the USR 8054. I think this was the right way to do it, and it seems to have worked:
I burned the ISOs to CDs.
Step 4: Install FC4
I installed FC4 on the laptop. I used all defaults except for what I mention below. There were a few glitches, which I will also discuss.
First, in the Installation Type screen, I chose Workstation and clicked Next.
In the Disk Partitioning Setup screen, I chose the default, Automatically partition, and clicked Next. In the next screen, Automatic Partitioning: I choose the default, Remove all Linux partitions on this system, and clicked Next. A window appeared, displaying the following text:
You have chosen to remove all Linux partitions (and ALL DATA on them) on the following drives:
are you sure you want to do this?
I clicked Yes. Another window appeared, displaying this text:
Could not allocate requested partitions:
Partitioning failed: Could not allocate partitions as primary partitions.
I clicked OK, and yet another window appeared:
Automatic Partitioning Errors
The following errors occurred with your partitioning:
You have not defined a root partition (/), which is required for installation of Fedora Core to continue.
This can happen if there is not enough space on your hard drive
(s) for the installation.
You can choose a different automatic partitioning option, or click 'Back' to select manual partitioning.
Press 'OK' to continue.
I clicked OK and then I clicked Back.
Again in the Disk Partitioning Setup screen, I selected the default, Automatically partition and clicked Next.
In the Automatic Partitioning window, I selected Remove all partitions on this system and clicked Next.
In the Time Zone Selection screen, I selected System clock uses UTC and clicked Next
The Installing packages screen appeared, and a window appeared, displaying this less than wonderful text:
Error informing the kernel about modifications to partition /dev/
sda2 - Device or resource busy. This means Linux won't know
about any changes you made to /dev/sda2 until you reboot - so
you shouldn't mount it or use it in any way before rebooting.
I clicked Ignore, and another less than wonderful screen appeared:
An unhandled exception has occurred. This is most likely a bug. Please copy
the full text of this exception and file a detailed bug report against anaconda at
Traceback (most recent call last):
File "/usr/lib/anaconda/gui.py", line 1137, in handleRenderCallback
File "/usr/lib/anaconda/iw/progress_pui.py", line 244, in renderCallback
File "/usr/lib/anaconda/pui.py", line 873, in nextClicked
File "/usr/lib/anaconda/dispatch.py", line 174, in gotoNext
File "/usr/lib/anaconda/dispatch.py", line 242, in moveStep
rc = apply(func, self.bindArgs(args))
File "/usr/lib/anaconda/packages.py", line 579, in turnOnFilesystems
File "/usr/lib/anaconda/partedUtils.py", line 726, in savePartitions
error: Error: Error informing the kernel about modifications to partition /dev/sda2 - Device or resource busy. This means Linux won't know about any changes you made to /dev/sda2 until you reboot - so you shouldn't mount it or use it in any way before rebooting.
I clicked OK, and the GUI installer terminated. That screen displayed:
install exited abnormally
Damn. I pressed Ctrl-Alt-Del and tried again. This time, the install went smoothly. Instead of the error windows, I saw
Formatting / file system...
and the installation completed without a hitch.
Step 5: Boot and configure FC4
When you boot FC4 for the first time, a GUI appears, prompting you to configure the OS. For brevity, I will discuss only the items for which my choice was non-default or that produced interesting results.
In the License Agreement screen, I chose Yes, I agree to the License Agreement and clicked Next. (Not very interesting, but it's not the default.)
In the Date and Time screen, I clicked the Network Time Protocol tab and checked Enable Network Time Protocol. I clicked Next.
The Display screen appeared. According to Dell, the Latitude D610 has native screen resolution of 1400x1050 and 16.7M colors. For Unknown monitor with ATI Radeon Mobility M300, I clicked Configure.... In the Monitor window, I chose Dell 1400x1050 Laptop Display Panel and clicked OK. For Resolution, I chose 1400x1050. I clicked Next.
The Sound Card screen appeared, listing these tidbits:
Model: Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller
I clicked Play test sound. I do have a slight hearing problem, but I don't think that was why the PC was silent. A window appeared, asking:
Did you hear the sample sound?
I clicked No. Another window appeared:
Automatic detection of the sound card did not work. Audio will
not be available on the system. Please click OK to continue.
This is a work computer, so I guess that's OK for now. I clicked OK to exit the window, and Next> to move on.
Step 6: Log in and finish configuring
Dvorak key layout
About 15 years ago, I started using the Dvorak keyboard layout as part of an effort to decrease typing related stress on my hands. Configuring the keyboard on FC4 was too easy compared to my experience with other, older Linux distributions. To get a Dvorak key layout, select Desktop/Preferences/Keyboard. Click the Layouts tab. In the Keyboard Preferences window, click Add.... In the Choose A Layout window, select Dvorak. Click OK. In the Selecetd layouts: list, select Dvorak. Click Up. Click Close. Done!
This is a laptop. Suspend/resume is the normal use case. If I can't get suspend/resume to work, maybe I shouldn't be running Linux on it.
The easiest way to test whether suspend/resume works is to close the laptop's lid. I tried that, but nothing happened: the PC stayed powered on.
yum update sounds like a good idea, to make sure I have the latest kernel. The current kernel is 2.6.11-1.1369_FC4.
yum update downloaded and installed a lot of stuff, including a new kernel. I rebooted, and the new kernel booted up: 2.6.14--1.1653_FC4.
With the new kernel and all the other updates, a battery status applet is running on the GUI panel. It look the update worked things out, and acpi is running:
ps -ef | grep acp shows that
/usr/sbin/acpid is running. This is good.
yum search acpi, one of the results is
acpitool. It sounds useful, so I
yum install acpitool.
acpitool -s suspended everything perfectly. Unfortunately, it didn't resume properly. Everything came up looking good, but the disk LED was lighted, and it seemed like any command that accessed the disk caused everything to freeze. Eventually, the GUI desktop froze. I tried to log in on a text console, but it froze after I type my user name and pressed
Time for a reboot. After it came up, I tried
acpitool -S, but it didn't do anything.
I found some useful tips for the D600, which is only 10 less than the D610. I followed the instructions, except for
acpid start, which failed. Instead, I rebooted.
While running on AC power, the screen lid button turns off the LCD. Releasing the screen lid button turns the LCD back on. This is a good start.
Touching the power button quickly shuts down and powers down. Touching the power button again powers up. OK again.
While running on battery power, the lid button suspends... But does it resume when I release the lid button? Nope: same old resume problem. This is disappointing.
I think I'm going to have to stop here and live with it as is. While on AC power, the lid button does what I want. The power button performs a clean shutdown. This is good enough for now.
In Desktop/Preferences/Screensaver, I changed the setting to Lock Screen After 10 minutes. In the Advanced tab, I changed these settings: In the Display Power Management area, I chose Power Management Enabled, Standbay After 20 minutes, Suspend After 30 minutes, and Off After 40 minuts. Back in the Display Modes, I selected File/Restart Daemon.
More to do
This is good enough for today, but I have a few more things left to do:
- WiFi set up: The cabled Ethernet connection works fine, so I'll put this off. Quick HOWTO: Linux Wireless Networking looks like a good resource.
- VPN: To use this effectively while I'm not at the office, I will want a VPN or an SSH reverse tunnel. I prefer to use VPN.
- Pocket PC sync: I want to be free of windows on the desktop, but I like my Pocket PC. I want to keep the Pocket PC's meeting calendar synchronized with my work calendar.
- Audio: It would be nice to get audio working.