A lot of the info at the Intimate site seems rather out-of-date, and what
I'm trying is not working, so I'll ask:
I have an iPAQ 3765 with a single PCMCIA sleeve, and a 3955 with a dual
PCMCIA sleeve. I also have an Ethernet card, and a couple Toshiba MK5002MPL
5 gig PCMCIA hard drives. Both iPAQs are flashed with the 2.21.12
bootloader, and Familiar 0.7.2, and everything works pretty well. I have gcc
running, and I've been able to do native rebuilds of bison, flex, and gcc
under Familiar with a hard drive.
I want to be able to boot the Intimate distribution from a hard drive. I
partitioned the drives, loaded zimage, params, and initrd to /boot on the
vfat partition. Both iPAQs are unable to load the zimage file.
Here is the partitioning setup:
Disk /dev/hda: 255 heads, 63 sectors, 611 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 4 32098+ 6 FAT16
/dev/hda2 5 611 4875727+ 83 Linux
At one point I used Windows XP to repartition the drive, and the
head/sectors/cylinders organization was changed. When I first got the drive
it reported 980 cylinders. I assume that since this organization is virtual
anyhow, it doesn't much matter. (I hope).
I didn't realize how many versions of "FAT" there are. I have tried both
type 4 and type 6. The documentation doesn't specify which FAT variant(s)
are supported by the bootloader.
I've tried using both Windows XP and Familiar with fdisk/mkdosfs to
partition and format the vfat partition.
I started off assuming that the paragraph in the install doc that was
written about a year ago saying that the new bootloaders don't work is now
obsolete, but now I'm thinking that I might need an older bootloader and
that it will only run on the 3765. I already tried flashing 2.18.54 to the
3955, but it rejected the attempt, probably because the old bootloader
architecture code is not supported on the 3955. MANY THANKS TO WHOEVER PUT
THAT CHECK IN THE BOOTLOADER!!! You probably saved me from a bricked iPAQ.
The tails of the boot logs follow my .sig
Can somebody tell me if it will be possible to run Intimate on the hardware
I have, and what is the key that I'm missing?
Is the Intimate project still alive? Is there now a better way of running a
fullblown handheld Linux?
-- Jonathan Engdahl Rockwell Automation Principal Research Engineer 1 Allen-Bradley Drive Advanced Technology Mayfield Heights, OH 44124 http://users.safeaccess.com/engdahl jrengdahl@hotmail.com "The things which are seen are temporary, but the things which are not seen are eternal." II Cor. 4:18 ====================================================== On the 3955 I get: .. pcmcia_insert: funcid = 00000000 Mounting vfat on partition 00000000 cmd vfat mount: partid=00000000 vfat mount: reading bpb_info Reading params from file: /boot/params vfat_find_file_entry: fname='boot/params' dirname='boot' basename='PARAMS' vfat_find_dir_entry: fname='boot' dirname='' basename='boot' searching root_dir_entries Invalid long filename entry: filename too long Reading kernel from file: boot/zImage vfat_find_file_entry: fname='boot/zImage' dirname='boot' basename='ZIMAGE' vfat_find_dir_entry: fname='boot' dirname='' basename='boot' searching root_dir_entries Invalid long filename entry: filename too long read zimage failed rc=FFFFFFFE ====================================================== On the 3765 I get: .. pcmcia_insert: funcid = 00000000 ptable signature=0000AA55 Mounting vfat on partition 00000000 cmd vfat mount: partid=00000000 vfat mount: reading bpb_info oemname=mkdosfs Reading params from file: /boot/params vfat_find_file_entry: fname='boot/params' dirname='boot' basename='PARAMS' vfat_find_dir_entry: fname='boot' dirname='' basename='boot' searching root_dir_entries vfat_read_clusters_offset: reached VFAT_EOC at bytes_read=00000800 find_file_in_dir: INITt"ŸÁh"ŸÁ,ë attr=00000010 first_cluster=00000002 n_bytes=00000000 find_file_in_dir: INITt"ŸÁh"ŸÁ,ë attr=00000010 first_cluster=00000000 n_bytes=00000000 find_file_in_dir: ZIMAGE attr=00000020 first_cluster=00000FFE n_bytes=000B8AD0 find_file_in_dir: ZIMAGE attr=00000020 first_cluster=00000FFE n_bytes=000B8AD0 find_file_in_dir: PARAMS attr=00000020 first_cluster=00000FFD n_bytes=000000A9 + set linuxargs "init=/linuxrc root=/dev/ram0 ramdisk_blocksize=4096 console=ttySA0" setting param <linuxargs> to value <init=/linuxrc root=/dev/ram0 ramdisk_blocksize=4096 console=ttySA0> + set kernel_filename boot/zimage setting param <kernel_filename> to value <boot/zimage> + set initrd_filename boot/initrd setting param <initrd_filename> to value <boot/initrd> + set rootfstype cramfs setting param <rootfstype> to value <cramfs> Reading kernel from file: boot/zimage vfat_find_file_entry: fname='boot/zimage' dirname='boot' basename='ZIMAGE' vfat_find_dir_entry: fname='boot' dirname='' basename='boot' searching root_dir_entries vfat_read_clusters_offset: reached VFAT_EOC at bytes_read=00000800 find_file_in_dir: PARAt"ŸÁh"ŸÁ,ë attr=00000010 first_cluster=00000002 n_bytes=00000000 find_file_in_dir: PARAt"ŸÁh"ŸÁ,ë attr=00000010 first_cluster=00000000 n_bytes=00000000 find_file_in_dir: ZIMAGE attr=00000020 first_cluster=00000FFE n_bytes=000B8AD0 Reading initrd from file: boot/initrd vfat_find_file_entry: fname='boot/initrd' dirname='boot' basename='INITRD' vfat_find_dir_entry: fname='boot' dirname='' basename='boot' searching root_dir_entries vfat_read_clusters_offset: reached VFAT_EOC at bytes_read=00000800 find_file_in_dir: ZIMAt"ŸÁh"ŸÁ,ë attr=00000010 first_cluster=00000002 n_bytes=00000000 find_file_in_dir: ZIMAt"ŸÁh"ŸÁ,ë attr=00000010 first_cluster=00000000 n_bytes=00000000 find_file_in_dir: ZIMAGE attr=00000020 first_cluster=00000FFE n_bytes=000B8AD0 find_file_in_dir: ZIMAGE attr=00000020 first_cluster=00000FFE n_bytes=000B8AD0 find_file_in_dir: PARAMS attr=00000020 first_cluster=00000FFD n_bytes=000000A9 find_file_in_dir: PARAMS attr=00000020 first_cluster=00000FFD n_bytes=000000A9 find_file_in_dir: INITRD attr=00000020 first_cluster=00000176 n_bytes=00743734 vfat_find_file_entry: fname='boot/initrd' dirname='boot' basename='INITRD' vfat_find_dir_entry: fname='boot' dirname='' basename='boot' searching root_dir_entries vfat_read_clusters_offset: reached VFAT_EOC at bytes_read=00000800 find_file_in_dir: INITt"ŸÁh"ŸÁ,ë attr=00000010 first_cluster=00000002 n_bytes=00000000 find_file_in_dir: INITt"ŸÁh"ŸÁ,ë attr=00000010 first_cluster=00000000 n_bytes=00000000 find_file_in_dir: ZIMAGE attr=00000020 first_cluster=00000FFE n_bytes=000B8AD0 find_file_in_dir: ZIMAGE attr=00000020 first_cluster=00000FFE n_bytes=000B8AD0 find_file_in_dir: PARAMS attr=00000020 first_cluster=00000FFD n_bytes=000000A9 find_file_in_dir: PARAMS attr=00000020 first_cluster=00000FFD n_bytes=000000A9 find_file_in_dir: INITRD attr=00000020 first_cluster=00000176 n_bytes=00743734 C0800000: 31 39 36 0D 0A 48 54 54-50 2F 31 2E 31 20 32 30 | 196..HTTP/1.1 20 C0800010: 30 20 4F 4B 0D 0A 44 61-74 65 3A 20 4D 6F 6E 2C | 0 OK..Date: Mon, C0800020: 20 32 38 20 4A 75 6E 20-32 30 30 34 20 30 34 3A | 28 Jun 2004 04: C0800030: 30 34 3A 31 32 20 47 4D-54 0D 0A 53 65 72 76 65 | 04:12 GMT..Serve cmd vfat mount: partid=00000000 vfat mount: reading bpb_info oemname=mkdosfs pcmcia_remove_sleeve Booting vfat... kernel partition base C0008000 kernel_magic=0D343931 kernel_region_words[9]=206E754A Unrecognized kernel imageReceived on Mon Jun 28 2004 - 21:34:21 EDT
This archive was generated by hypermail 2.2.0 : Mon Jul 25 2005 - 17:21:16 EDT