[iPAQ] pivoting and flash booting problems?

From: Alan Messer <messer.a.t.tomil.hpl.hp.com>
Date: Thu Jun 06 2002 - 13:54:02 EDT

Hi,

I've been seeing some strange problems on a H3600.

- I've configured it to pivot_root from the ipaq's flash to a 256
SanDisk CF card. However, I have seen a couple of problems. I
frequently get log entries claiming invalidate problems. Any ideas
on how to get rid of these?

invalidate: busy buffer
invalidate: dirty buffer
invalidate: busy buffer
invalidate: dirty buffer

- I've also been trying to get the ipaq to boot the CF card
directly. I've used the instructions from the Wiki
BootingLinuxFromCF, but no luck. It refuses to do anything after
finding the kernel. Looking through the logs I notice that the
pcmcia insert stage doesn't correctly display the name/revision of
the card (despite retrieving them correctly from under Linux). So
perhaps 256M cards (SanDisk) aren't supported under bootldr
2.18.39? I've included my boot log entries below. I'd really like
to get this is going and forget pivoting, but I'm not having much
luck.

boot> set kernel_filename boot/zimage
   setting param <kernel_filename> to value <boot/zimage>
boot> boot vfat
h3600_sleeve_insert: no spi read, defaulting sleeve vendor
h3600_sleeve_insert: no spi read, defaulting sleeve deviceid
  sleeve vendorid=00001125
  sleeve deviceid=0000D7C3
pcmcia_probe_sleeve
   probing for dual pcmcia sleeve
   dual_pcmcia_linkup[0]->prc=000019B0
dual_pcmcia_probe_sleeve
pcmcia_register_ops: ops=0002F428
h3600_sleeve_insert: matched driver Compaq PC Card Sleeve
cis mapping=28000000
cis[0] =00000001
   01 03 00 00 FF
   10 05 07 00 B8 00 16
   17 03 DA 00 FF
end
cis mapping=38000000
cis[0] =00000001
   01 04 DF 72 01 FF
   1C 04 03 D9 01 FF
   18 02 DF 01
   20 04 45 00 01 04
   manfid[0]=00000045
   manfid[1]=00000000
   15 17 04 01 53 75 6E 44 69 73 6B 00 53 44 50 00 35 2F 33 20 30
2E 36 00 FF
   80 03 14 08 00
   21 02 04 01
   funcid=00000004
     fixed disk
   22 02 01 01
   22 03 02 0C 0F
   1A 05 01 07 00 02 0F
   1B 0B C0 C0 A1 27 55 4D 5D 75 08 00 21
   1B 06 00 01 21 B5 1E 4D
   1B 0D C1 41 99 27 55 4D 5D 75 64 F0 FF FF 21
   1B 06 01 01 21 B5 1E 4D
   1B 12 C2 41 99 27 55 4D 5D 75 EA 61 F0 01 07 F6 03 01 EE 21
   1B 06 02 01 21 B5 1E 4D
   1B 12 C3 41 99 27 55 4D 5D 75 EA 61 70 01 07 76 03 01 EE 21
   1B 06 03 01 21 B5 1E 4D
   1B 04 07 00 28 D3
end
  identify command=000000EC
C1A01630: 8A 84 D4 03 00 00 10 00-00 00 40 02 20 00 07 00 |
..........@. ...
C1A01640: 00 A8 00 00 20 20 20 20-20 20 20 20 30 20 30 32 | ....
       0 02
C1A01650: 30 32 31 32 33 32 38 32-02 00 02 00 04 00 64 56 |
02123282......dV
C1A01660: 20 67 2E 31 31 32 61 53-44 6E 73 69 20 6B 44 53 |
g.112aSDnsi kDS
C1A01670: 46 43 2D 42 35 32 20 36-20 20 20 20 20 20 20 20 | FC-B52
6
C1A01680: 20 20 20 20 20 20 20 20-20 20 20 20 20 20 01 00 |
         ..
C1A01690: 00 00 00 02 00 00 00 01-00 00 01 00 D4 03 10 00 |
................
C1A016A0: 20 00 00 A8 07 00 00 01-00 A8 07 00 00 00 00 00 |
...............
C1A016B0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 |
................
C1A016C0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 |
................
C1A016D0: 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 |
................
C1A016E0: 00 00 00 00 | ....

   serial_number: 0 0202123282
   firmware_revision: dV g.112
   model_number: aSDnsi kDSFC-B52 6
   n_sectors_user_addressable=00000000
   bytes_per_sector=00000240
   major_version=00000000
   minor_version=00000000
   flags=0000848A
   bytes_per_track=00000000
   n_sectors_per_track=00000020
   n_cylinders=000003D4
   n_heads=00000010
   cmdset[0]=00000000
   cmdset[1]=00000000
   cmdset[2]=00000000
   cmdset[3]=00000000
   cmdset[4]=00000000
   cmdset[5]=00000000
   ACTUAL bytes_per_sector=00000200
ptable signature=0000AA55
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
+ set linuxargs "initrd root=/dev/rd/0"
   setting param <linuxargs> to value <initrd root=/dev/rd/0>
+ set kernel_filename boot/zImage
   setting param <kernel_filename> to value <boot/zImage>
+
  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
  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
Could not find file.Booting vfat...
kernel partition base C0008000
kernel_magic=E1A00000
kernel_region_words[9]=016F2818
Linux ELF flash_imgstart=C0008000 size=00000000 dest=C0000000
offset=00008000
MMU Control=C19F4071
MMU PIDVAM=00000000
Skipping kernel copy by request.
C0008000: E1A00000
C0008004: E1A00000
C0008008: E1A00000
C000800C: E1A00000
C0008010: E1A00000
C0008014: E1A00000
C0008018: E1A00000
C000801C: E1A00000
C0008020: EA000002
C0008024: 016F2818
root_filesystem_name=ide
Grabbed linuxargs, argc = 00000000
Using mach_type 00000016
setting boot parameters to
initrd root=/dev/rd/0
Makeing core tag at C0000100
Makeing cmdline tag at C0000114
Makeing mem32 tag at C0000174
Makeing ptable tag at C0000184
Makeing initrd tag at C000034C
   initrd.start=C0800000
   initrd.size=00000000
dram_size=04000000
command line is:
mtdpart=bootldr@0x00000000:0x00040000,root@0x00040000:0x00FC0000
initrd root=/dev/rd/0
Disabling LCD controller
linuxEntryPoint=C0008000
Booting Linux image
Uncompressing Linux.............................................
done, booting the kernel.

... then an ominous silence? ...

Alan.

PS: I manually typed the line "set kernel_filename ..." because it
doesn't seem to be evaluating the boot/params file either?
Received on Thu Jun 06 17:53:12 2002

This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:44:51 EDT