Disclaimer: The following represents what I think I should have done. The route I actually took involved several mis-steps. I'm not Linux expert, just someone who uses Linux all of the time to get real work done. I'm sure there are better ways to do this than I have shown here. No promises. Your mileage may vary.

• The IBM X23 has been my companion for nearly three full years. This is an extremely versitile and effective machine for getting real work done. I highly recommend this machine. Durable, lightweight, long battery life. Very productive. (Update March 29, 2004 -- see note about reliability below)

• Generic RedHat Linux installation stuff. See See original page.

• If you only want single-boot (Linux Fedora Core only) on the Thinkpad X23: Almost all of the little hassles I have encountered are related to the desire to have dual boot with both Windows XP and Linux -- two operating systems that do not play very well together. If you just want only single boot Fedora Core on your Thinkpad X23, and you want to kiss Windows XP goodby forever, the steps are much simpler. If you want to do this you are probably already a pretty hard-core Linux type and so the following one-sentence verbal description will suffice: Boot the RH installation disk, run fdisk, delete XP NTFS and Recovery partitions, make your own Linux partitions and install or -- if you are a partition weeny like me -- stop the installation of Linux at point after you have deleted all partitions, reboot your Linux install CD, select graphical install, default partitions, install, select generic laptop display, note that X works out of the box, and , ta-da, you are all done except for putterting around with your odd devices like the IR port, your wireless LAN, your modem or or maybe (heaven help you) an UltraPort web cam. Phwew!

  For the rest of you who want to put Redhat Fedora Linux on your IBM Thinkpad X23 while retaining the ability to boot and run Windows XP, Please read on.

• Why even mess with Windows XP? As a physicist doing teaching and research, I spend 90 percent of my time working in Linux. Unix is the first "real" operating system I ever used, and I've been doing almost all of my useful work on a Unix box of some flavor since 1984. But with annoying frequency I still get stuff from colleagues, administrators, and funding agencies that require Microsoft Windows on a PC just to look at. And while current Linux tools provide a certain level of being able to look at MSWin stuff while running Linux (i.e. Win4Lin is a cute product lets me see about 90 percent of all MS Word documents I get in the mail using my old Win98 software inside of Linux). Still, on occasion, I need to boot Windows native to see in bug-free detail someone's complicated latest-version PowerPoint display with all of the bells and whistles. So there is no way out -- especially since on occasion I need to edit or even create such documents. And besides, my wife likes to run Eudora and Quicken when we travel together. And finally, when I travel I can invoke my ATT ISP seamlessly in Windows-land using the preloaded access numbers and auto-configuring software. I will wait for a rainy day later to sort out how to kick in the modem under Linux.

  So dual boot it is. And since XP comes with the box it seems alot simpler to stick with XP than to load an old Windows 98 (which would probably work but I'd have to track down and install all of the new drivers) or worse yet shell out new dollars for Bill Gates to buy Windows ME. The drawback, of course, is that XP -- being a derivative of Windows NT and 2000 -- does not get along with Linux as well as Win95/98/ME does. In the latter case, you can automatically mount your "C:" drive by adding a appropriate line to your fstab. However, with the kernel that ships with RH 9 you cannot "simply" mount the Windows XP NTFS file system partition in Linux, and -- apparently -- you cannot or should not simply install LILO over the Master Boot Record lest you risk getting it entangled with XP's overwhelming desire to keep it's mitts on the boot process. And doing this this may disconnect you from easy access to the XP recovery partition which you will need if your XP system gets corrupted.

  So, Linux and Windows XP are like two unruly siblings sitting in the back of your car and you need to set the rules down carefully to ensure they do no damage to each other. But it can happen so carry on -- with care.

• Hardware Details of the IBM Thinkpad X23: I got this delivered straight from IBM Direct:
  • Windows XP,
  • 800 Mhz Pentium iii,
  • 128 meg memory originally. Boosted this by 512 meg -- RAM is very inexpensive direct from IBM. This has been most useful for running memory-hungry "Open Office" Impress.
  • 30 Gbyte internal drive (big is good!),
  • Built-in wireless (this is great for home and trips!)
  • Ethernet and modem are built-in.
  • IBM Ultrabase X2 with a CD-RW/DVD put in the bay.
  • An extra battery (two are plenty for coast-to-coast air flight). Note: As of November, 2004, both batteries are still working perfectly! This is remarkable performance for a laptop battery.
  • AC car/airplane power adaptor. I can plug in many places now.
  The Ultrabase also comes with a handy floppy drive and parallel and serial ports. Very nice. When I travel light, I leave the Utrabase at home and at 3.5 pounds, the Thinkpad laptop proper is both light and strong with the titanium alloy cover. This is good because this laptop is not so cheap and I want to keep this thing for a good while -- I physically killed my previous unnamed "bargain" laptop before it could achieve technological obsolescence. First the screen got scrozzled, then the "N" key popped off, then the floppy failed, and finally the display cover cracked at the hinges. After over a year of similar abuse no obvious signs of any wear or tear on the X23.

  An aside -- the XP system on the Thinkpad X23 comes with a whole bunch of little fancy IBM tools and widgets. Some of these, like power management, are kinda cute. If you click on the battery icon it tells you everything there is to know about your battery, like, for example, the date it was first used in your PC and the number of times it has been cycled.

• Factory delivered partitioning: Most important is the fact that the factory-delivered hard drive comes partitioned into two pieces. The first partition is the NTFS file system where XP is pre-installed. The second partition is the FAT32 IBM "recovery" partition which, in case you inadvertantly trash your XP partition, you can boot the recovery partition and it will automatically re-format the main partition and reinstall XP from scratch including any pre-bundled stuff that came with your PC. I had the misfortune of having to do this and the re-install takes about 90 minutes and it is both illuminating and scary to watch the XP recovery process go by -- you can learn alot about how very strange Microsoft is by watching the scheme by which the XP disk is recovered. Anyway, there was no XP recovery CD or anything like this shipped with the laptop from IBM -- gulp! If you plan to dual-boot with XP and Linux, as I did, one of the first steps you want to take is to invoke the recovery partition (F11 key) in the IBM boot manager and make your own recovery boot floppy. This way, in case you somehow screw up and trash the XP partition and the master boot sector on your hard drive, you can still use your recovery floppy to reinstalled Windows XP from the recovery partition -- assuming that you have not trashed this as well. I am a strong advocate of making recovery and boot disks whenever you can since they can save you if you make a mis-step and I certainly made my share of these. I know, we are all supposed to be moving to a brave new world with no floppies. Call me old fashioned.

• Get Partition Magic So here's what I did: I bought a copy of Partion Magic Version 8 from Power Quest Software. Note: November, 2004: Apparently this company and product have been assimilated into Symantec. You can get this in minutes online with a credit card, $70. This latest version of PM includes Boot Magic, it recognizes the ext3 file system, and it properly handles access to "hidden partitions" with XP. I realize that shelling how dollars for this product will be a very bothersome option when in principle this can be done by hand. Perhaps I am just thick but it seems every time I try to mess with partitions "manually" with fdisk or even disk druid I somehow mess things up and need to start from scratch. With Partition Magic it is (mostly) a breeze. Not too bad for $70.

• Use partition magic to set up your non-Linux partitions: Here is what I did with Parition Magic. Note, I would strongly recommend that you do these steps one at a time. That is, you set up a single change and then you ask Partition Magic to invoke the change. In principle you can ask Partion Magic to set up and invoke all of these things in one throw, but if something gets scrozzled it might not be so clear where you are. Better to go one step at a time. Some of these steps Partition Magic will ask for a reboot.
  • First, I reduced the size of the XP partition from about 27 Gig to about 4.5 gig. WARNING. There is a "gotcha" here. If you use the "resize" wizard option on Partition Magic and you ask to reduce the size of the XP partitionm, it also sets up to move the Recovery partition from the end of the disk down to next to the smaller XP partition. I am pretty sure that you do not want to do this. Do not move/resize or otherwise touch the XP recovery partition. I think if you do, this would be a Bad Thing since I am guessing that neither your boot handler nor your recovery floppy will be able to find the partition if you mess up. You simply want to resize the NTFS XP partition without moving the other partition so that the unused space appears between them on the disk. Make sure that you only have this one action -- resize -- before you commit Partition Magic to execute the change. This will force a reboot.

  • Second, I used Partition Magic to create a new FAT partition just beyond the now smaller NTFS partition. You need this if you are going to use a boot handler like Boot Magic which comes for free with Partition Magic. The size of the FAT partition can be quite small -- I chose 900 meg but you can probably get away with much less. However, you might want a partition this large if you use it as a "shared space" between Linux and XP.

  • Third, Check it all out again. When you are done you will have three partitions and a large region of unused space on your disk. At this point it it worth rebooting XP, running Partition Magic one more time just to make sure that the partition look okay after a reboot, and then reboot yet one more time, and use F11 to make yet another up-to-date recovery boot disk.

• Install from the ISO's (finally!) This is easy as pie. Reboot, hit F12 and boot from CD rom the first of four Fedora Core install CD's. (Alternately you can install from the network. See elsewhere for details on how to obtain and burn ISO's) The Really Good News: Fedora installs on your Thinkpad X23 like a charm. I chose the graphical Laptop configuration with automatic partitioning option and of course it set up the Linux partitions in the unused space and left the NTFS, FAT, and recovery partitions alone. Installation is extremely straightforward and you just chose defaults for everything except the instalation of the boot record. If you want to keep the IBM boot handler (probably a good thing) and you want to make use of Boot Magic to handle your dual boot, then you need to avoid having Linux installing GRUB into the MBS (master boot sector). You want to boot Linux only from grub and you want put this on the Linux /boot partition and NOT the master boot record (MBR). Check the appropriate boxes in the dialog window.

  After this, you just still the CD's in, one, two, three, four, and in less than two hours your Linux installation is done. When you get to the end and it is time to deal with X windows, chose the Generic LCD Laptop display -- NOT the one that the package picks for you. I run KDE and it appears to run completely bug-free.

• Trackpoint -- One possibly little gotcha -- depending on exactly what you are doing, you might find that the little TrackPoint nub comes up in a sort of "hyper" state where the slitest touch sends the mouse skittering into the corner. I fixed this by disabling the trackpoint in BIOS, rebooting, then rebooting again, re-enabling the trackpoint, and then using PS2 mouse options when blue-screened Kudzu autmatically kicked in to configure my "new" device. Honestly, I do not remember exactly what I did in Kudzu but I selected reasonable choices here and the trackpoint works fine now -- whether or not I also have my USB mouse plugged in. Once I did this, I find that the mouse can be plugged/unplugged/replugged and it works fine.

• Reboot back to XP and check things out: It's time to set up your dual boot and since you got Boot Magic for free when you bought Partition Magic why not use it? Warning: do not try to use Boot Magic until you get to the right place as indicated below. I know from personal experience that if you invoke Boot Magic before you are certain that your partitions and operating systems are in their final form, things can get completely messed up. So when you are done with Linux instalation, reboot. Then I would follow the following what I think this is the safest possible sequence of steps:
  • First, reboot, and you will go back to XP. Here, first, immediately invoke Partition Magic. If something got scrozzled on your parition table when Linux installed, Partition Magic will fix it automatically for you (hopefully). This happened to me once or twice -- I do not know why. If this happens, reboot again and double check a second time with Partition Magic

  • Second Reboot again, invoke F11 and make a Third Recovery Boot disk for XP. This is last and best recovery boot disk. Throw the other two that you made earlier away.

  • Third Reboot yet again and invoke Partition Magic. Look at the FAT partition. You should do two things (1) reformat it as a FAT file system, and (2) if it is hidden, you should make it visible. This is an option under the "advanced" menu item.

  • Fourth Once this is done, reboot yet even again, and go into Partition Magic again to double check that all is well.

  • Important Warning: Now is the time to run the install program for Boot Magic. As I found out the hard way it is important that you not do this before this point since Boot Magic really want everything completely all set and ready to go with your partitions and your operating systems. In particular, if you try to install Boot Magic before you have your FAT partition ready, it just won't work. Also, there is a little problem with a "trap door" on Boot Magic. Once you install it on your visible FAT partition, that partition become hidden again (apparently since it is now bootable) and so you cannot simply modify things if you are unhappy -- you need to reformat the FAT partition and start all over with installing Boot Magic. Also check out the option in the (very long) PDF manual for unhiding partitions in XP. You will want to do this is you want this disk space accessable to both XP and Linux. So go slow.

• Setting up your dual boot with Boot Magic: Okay, you now have XP installed in the first partition. An empty, formatted and visible FAT partition is second. The Third partition is extended and includes all of your newly installed Linux stuff. The forth partition is the recovery partition which has remained unmolested since the start. Partition magic tells you that everything is as above and happy. You have your latest recovery boot disk. You are now all set to set up dual boot:
  • First, Run Boot Magic install. This looks like a setup Install Shield wizard thingy that is supposed to just install Boot Magic but it is much more and running the installation program immediately kicks in the new boot scheme. In other words, you do not first install, then run Boot Magic. Rather, the installer does everything in one step. By the way, you weill get yet another recovery disk. By now you have a stack of these. Note, if you do not have a visible, primary FAT partition on your disk Boot magic will simply give up immediately.

  • Second, when Boot Magic install appears complete you will have popped up a Boot Magic configuration window. Take the time to configure this now since it will be harder later for the annoying reason that your FAT partition will revert back to being hidden once you install Boot Magic for good. (I suspect that there is a way to inhibit this in Boot Magic but I cannot figure it out). You need to decide if you will default boot to Linux or XP. You probably do not want to boot the FAT sector -- what will happen (an infinite boot loop?) You probably want to rename each of the boot options -- especially the last boot option something like XP recovery.

  • Third, Okay, cross your fingers. All goes well and now on your way to Linux, three boot handlers go by -- the IBM one, Boot Magic, and finally GRUB. After arriving happily in Linux land, you probably want to reboot to XP, use Partition Magic to verify your partitions one last time. Maybe even make one more recovery boot disk for XP. Yes, I know I am probably paranoid about this.

• Printer stuff. Between CUPS and the Gnome printer GUI it was easy to setup connections to network printers.

• Redhat Network (up2date) -- This is a subscription service that automatically tells you when you need a new RPM for security or whatever reason and then it downloads and installs them. It's great, but kinda slow. For Fedora Core 3 a better (faster) solution is "yum". See the yum home page:.

• Ethernet works out of the box for DHCP configurations. You can configure this using the KDE network configuration tool. I set things up so that eth0 (Intel Express 10/100) is deactivated on boot and activatable by the user.

• I have not tried the modem.

• Wireless LAN -- With Fedora Core 2 and Core 3 this "just works" right out of the box. This is so much better than the "old days" of having to install a suite of drivers by hand. One "gotcha": Apparently there are many flavors of built-in WiFi cards for different makes and models of IBM Thinkpads so one driver does not serve all. For my X23 apparently the WiFi is or looks like an orinoco device. This is automatically recognized and supported by Fedore Core 2 and 3 but this may not be true for everyone. I understand that some of the newer WiFi cards are not (yet) supported.

• Advanced Power Mamagement (APM) came up but I turned it off. I do not understand why so many laptop users really want this to go. There's alot of bandwidth on Linux for Think Pads (ltp) mailing list about troubles with APM, suspend-to-disk, resume from hibernate, etc., etc. For me all of these features are not even worth the trouble. A clean, cold, boot into Linux about two or three times a day (once each morning in the office, once at home in the evening) does not represent a huge waste of time, especially since I can do other things like chaging out of my boots or making a cup of tea whilst booting. If I want to move the laptop off of my desk and into the lab or someone's office, I just fold down the clamshell, leave the power and display on, and carry it. If I am going to be away from my desk for more than an hour, I'll throw the AC adaptor into a bag and carry them both along. If I am walking or driving I take half a minute to turn off my apps and shutdown. The only time I can think of where I have any real worries about power saving is when I travel, and so far there is no situation where two batteries, a 12V DC adapter, and a set of universal AC pass-through adapters haven't given me everything I need. Finally, since presentations are critical, the last thing I need is for my laptop to decide to hibernate in the middle of my OpenOffice presentation because it has decided that it should be saving power or haven't hit a key for a while or whatever. So I just turned the whole kit and kaboodle off. Note added March 29, 2004 -- I would not be surprized to learn that my regular reboot and an avoidance of suspend and hibernate functions has constributed substantially to the remarkable level of reliability I have experienced with this system. See Update March 29, 2004 below.v

• I havent tried reading a DVD.

• I have managed to burn CD's from linux. Actually this is a great way to do backups: Here is my script called cdbackup.

• I have a little web cam that sits on the top of the screen. It works very nicely in XP with associated software. I have not tried this under Linux, although there is apparently a driver for it out there somewhere.

Update: November 30, 2004, Updated to Fedora Core 3

Last summer I backed up everything, and did a clean install of Fedora Core 2. I installed everything. The installation was very similar to that of Red Hat 9. Fedora Core 2 worked great at first, but then I had some problems in that some of the kernel distributions (obtained with yum) would not boot at all. Eventually I just stuck with a stable kernel and life was good. All of the hardward that worked under RedHat 9 worked at least as well under Fedora Core 2 -- except I had to do some real trial and error to get the IR port to work to hot-sync my palm. I especially like the fact that Fedora Core 2 handles the wireless LAN seamlessly as device "eth1".

This November, I decided to upgrade to Fedora Core 3. As an experiment I decided to upgrade using yum instead of buring four disks. I followed the procedure on this web page. Everything worked like a charm, except:

• Be sure you have at least a few gigabytes of spare disk space. If you are tight on space you will run out of room for the rpm's. Annoying.
• The whole process takes a Very Long Time (for me roughly 10 hours) and will depend on your network speed.
• Every time I upgrade Redhat or Fedora, my scheme for accessing the IR port breaks. See below for a work-around.

IR Port

The process I took to make IR work boil down to these -- examimining the Infrared HOWTO, ignore what appears to be a bunch of information that does not apply, reading a whole bunch of web pages that have partial, incomplete, and/or confusing instruction, and ultimately trying out various things until it works. Warning: I made no attempt at a systematic installation. I have no idea which of the following steps are critical, which are useless, and whether or not there is really a better way.

Specifically the following things work for me:

• Make sure that the IR port is enabled in bios. That would be IRQ set to 3 and the address set to 0x2f8.
• My /etc/sysconfig/irda file looks like this:

  IRDA=yes
  DEVICE=/dev/ttyS1
  #DONGLE=actisys+
  DISCOVERY=yes
  

• My /etc/modprobe.conf has the following lines which I stole:

  #
  # The following were added Aug 27, 2004
  # From web site: IrDA quick Tutorial:
  # http://www.hpl.hp.com/personal/Jean_Tourrilhes/IrDA/IrDA.html
  #
  alias tty-ldisc-11 irtty-sir
  alias char-major-161 ircomm-tty
  alias irda-dongle-0 tekram-sir
  alias irda-dongle-1 esi-sir
  alias irda-dongle-2 actisys-sir
  alias irda-dongle-3 actisys-sir
  alias char-major-10-187 irnet
  

• After a clean reboot I type the following commands as root:

  /sbin/modprobe ircomm-tty
  /usr/sbin/irattach /dev/ttyS1
  

• As root, invoke irdadump, and hit the sync button on your Palm. If you are lucky you will see a nice output like:

  20:03:24.160272 xid:cmd ffffffff < 82309066 S=6 s=2 (14)
  20:03:24.309312 xid:cmd ffffffff < 82309066 S=6 s=3 (14)
  20:03:24.459288 xid:cmd ffffffff < 82309066 S=6 s=4 (14)
  20:03:24.609187 xid:cmd ffffffff < 82309066 S=6 s=5 (14)
  20:03:24.610194 xid:rsp 91467ef8 > 82309066 S=6 s=5 hea1 hint=0400 [ Computer ](20)
  20:03:24.694300 xid:cmd ffffffff < 82309066 S=6 s=* IrCOMM hint=8204 [ PDA/Palmtop IrCOMM ] (23)
  

• Install/Use Jpilot -- How to sync? I tried "kpilot" - it worked, sort of. I found that KOrganizer was not so compatible with my Palm IIIxe. Specifically every time I synched each entry was put into multiple catagories. My hands-down favorite syncing and calendar app is jpilot which is terse, simple, functional, and has never failed to sync properly. It comes with the complete Fedora Core 3. You need to set up for syncing as follows: Under File: Preferences: Setting: Serial Port: /dev/ircomm0 and Serial Rate 115200.

Update: August 26, 2003

I stumbled onto the program "gkrellm" which is the most compact and informative graphical system performance monitor I have had the pleasure to use. Meanwhile, I still cannot say enough good things about jpilot for syncing my PDA. This single piece of software has freed me from daily booting XP. Now I boot XP perhaps once a week.

Update: March 29, 2004: A Word about the reliability of the Thinkpad X23

==========================================================================
Corbin E. Covault, Department of Physics, Case Western Reserve University
Mailing Address: 10900 Euclid Avenue, Cleveland OH 44106-7079
Office: Room 207 Rockefeller Physics Bldg.  Phone:     (216)-368-4006
Secy:  Lori Rotar: (216)-368-4257           Fax:       (216)-368-4671
Home Phone: (216)-707-1618                  Mobile:    (216)-496-2077
Lab:   Room 11 A.W. Smith Building          Lab Phone: (216)-368-3632
Email: corbin.covault@case.edu              Web: http://hea.case.edu
Research: Experimental Physics -- Ground-based High Energy Astrophysics
--------------------------------------------------------------------------
()  ascii ribbon campaign - against html e-mail:  http://arc.pasp.de/
/\
==========================================================================