Changes to intimate installation to install over familiar 0.5-pre

I installed intimate yesterday, over the current (as of yesterday,
19 Oct 2001) dump of familiar 0.5-pre. Since the intimate
installation is intended for familiar 0.4, here are the changes I had
to make to install over 0.5-pre:

1. The reiserfs-module package retrieved by the intimate
   beta-installer script does not work with the kernel installed by
   familiar 0.5-pre. To solve this problem, install the appropriate
   reiserfs-module (see below) before beginning the intimate
   installation, and then answer "no" to the question about whether to
   install reiserfs-module.

   (If you don't solve this problem now, the beta-installer script
   will attempt to load the module; the load will fail but the script
   won't catch it; the mount of the HD will fail; and the script will
   try to install intimate into /mnt/hda1 (which isn't mounted on
   /dev/hda1 due to the module being wrong) and your flash will fill
   up. (The script won't catch that either.)

   FIX: Before running beta-installer, retrieve the correct module and
   install it, like this:

    wget http://familiar.handhelds.org/familiar/feeds/unstable/packages/armv4l/reiserfs-modules-2.4.7-rmk3-np1-devfs_hh6_arm.ipk
    ipkg install ./reiserfs-modules-2.4.7-rmk3-np1-devfs_hh6_arm.ipk

2. The installation instructions at
   http://intimate.handhelds.org/install.shtml, in step 3, have you
   wget beta-installer into /tmp/intimate. The script, however,
   expects beta-installer to be in /tmp, so the script fails when
   checking the md5sum of the beta-installer script. (This is a
   generic problem regardless of which version of familiar intimate is
   being installed over.

   FIX: Step 3 of the install.shtml instructions should say:

    cd /tmp && \
      mkdir intimate && \
      wget http://intimate.handhelds.org/installer/beta-installer && \
      sh beta-installer

3. The operations performed by the last step of beta-installer (the
   intimateboot package) don't do quite the right thing. It may be
   possible (easy?) to just not install the intimateboot package and
   do these things by hand, but I didn't do it that way. I installed
   the package and then made manual corrections:

  a. The linuxargs set by this package are incorrect for 0.5-pre. The
     commands to set the correct linuxargs are:

     set linuxargs "noinitrd root=/dev/mtdblock/2 init=/linuxrc.intimate console=ttySA0
     params save

  b. The script /linuxrc.intimate isn't quite correct. The modules
     which are loaded are not correct and/or sufficient to access the
     pcmcia hd. Replace these lines:

        depmod -a
        modprobe pcmcia_core
        modprobe h3600-sleeve
        modprobe h3600_backpaq
        modprobe ds
        cardmgr -q -o -c /etc/pcmcia

     with these lines:

        depmod -a
        modprobe ide-probe-mod
        modprobe pcmcia_core
        modprobe h3600_generic_sleeve
        modprobe ds
        modprobe wvlan_cs
        modprobe ide-cs
        modprobe ide-mod
        modprobe sa1100_cs
        modprobe sa1100-rtc
        modprobe apm
        modprobe h3600-sleeve
        modprobe h3600_ts
        cardmgr -o -c /etc/pcmcia

  If these modules end up not being quite correct for you, based on
  which LAN card you're using, etc., the way to determine the correct
  modules is to boot into (working) familiar, type "lsmod" to see
  which modules are loaded, and arrange them as above with the modules
  required by other modules loaded first. You can glean some of the
  requirements constraints from the output of lsmod, but if that may
  not be sufficient. If not, then change linuxargs, setting
  "init=/bin/sh" and reboot into familiar. Manually execute all steps
  in /linuxargs.intimate prior to the "depmod -a" and then attempt to
  run each modprobe command in sequence. It will tell you what
  prerequisites are missing, so you can rearrange the list. Just keep
  track of what order you had to load the modules manually so you can
  put them into the /linuxrc.intimate script.

4. The cardmgr command will hang if you don't have a DHCP server
   running. (i.e. it will try to configure the network but be
   unable). If you're not running DHCP, and you've manually run your
   ifconfig and route commands to bring up the network, it's time now
   to configure properly. Edit /etc/pcmcia/network.opts and set your
   IP address, netmask, default gateway, etc.

Having accomplished all of the above, intimate should boot for you.

Derrell Lipman
Received on Sat Oct 20 08:32:23 2001