From: Hicks, Jamey (Jamey.Hicks@compaq.com)
Date: Wed Mar 13 2002 - 15:16:41 EST
Erik,
A 32MB FAT filesystem will be FAT12, which I have not implemented yet. I know the partition type is FAT16, but that does not seem to mean anything.
It would be nice to see the copious debugging output that the bootldr generates when you run 'boot vfat' so I could verify that it is correctly parsing the FAT info.
Jamey
> -----Original Message-----
> From: Erik Karlin [mailto:e_karlin@yahoo.com]
> Sent: Wednesday, March 13, 2002 3:06 PM
> To: familiar@handhelds.org; bootldr@handhelds.org
> Subject: [Bootldr] Problems dual-booting and soft-reset
>
>
> I've been trying to dual-boot both a 3670 and a 3760. I cannot get
> either to work. Both running bootldr 2.18.16. My 3670 is running
> familiar 0.5.1 fine. The 3760 is running wince 2002.
>
> First the soft-reset problem. With 2.18.16, every time the
> power button
> was used to turn off the ipaq, and turn it on, it always came up with
> the red/white welcome screen with the version numbers in the lower
> right corner. I finally had to revert it to 2.18.01. That works no
> problem, just no dual-boot ability.
>
> Now, I've followed http://www.handhelds.org/z/wiki/BootingLinuxFromCF
> to setup my 32m CF card:
>
> sh-2.03# fdisk /dev/hda
>
> Command (m for help): p
>
> Disk /dev/hda: 4 heads, 32 sectors, 496 cylinders
> Units = cylinders of 128 * 512 bytes
>
> Device Boot Start End Blocks Id System
> /dev/hda1 1 81 5168 6 FAT16
> /dev/hda2 82 496 26560 83 Linux
>
> Right now, under familiar, hda1 is /mnt/cf and hda2 is /mnt/root
> sh-2.03# ls -CRF /mnt/cf
> /mnt/cf:
> boot/
>
> /mnt/cf/boot:
> initrd* params* zimage*
>
> and that params file is:
> set linuxargs "initrd root=/dev/ram0 init=/linuxrc console=ttySA0"
> set kernel_filename boot/zimage
>
> I downloaded the kernel/initrd/params off that webpage, and I unpacked
> the task-complete onto the linux partition (ext2). The task-bootstrap
> file was corrupt. I tried to boot with the 'Q' key, but that didn't
> work, same message as below. Next, I did a mv zImage foo; mv
> foo zimage
> but that didn't change anything.
>
> Here's the output, it doesn't seem to find zimage:
>
> boot> boot vfat
> booting 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=00000000
> pcmcia_register_ops: ops=0002C3CC
> h3600_sleeve_insert: matched driver Compaq PC Card Sleeve
> cis mapping=28000000
> cis[0] =00000101
> <blah blah>
> cis mapping=38000000
> cis[0] =00000C02
> end
> 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
> 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
> read zimage failed rc=FFFFFFFE
>
> The dual-boot FAQ http://www.handhelds.org/handhelds-faq/dualboot.html
> suggests:
> set linuxargs "initrd root=/dev/rd/0 console=/dev/ttySA0
> init=/linuxrc"
>
> but I don't think i'm getting that far, and the only obvious
> difference
> is the root device, does it matter?
>
> Any suggestions. This seems like a nice way to test a new kernel, and
> also ease users into linux, both things I'm trying to do.
>
>
> __________________________________________________
> Do You Yahoo!?
> Try FREE Yahoo! Mail - the world's greatest free email!
> http://mail.yahoo.com/
> _______________________________________________
> Bootldr mailing list
> Bootldr@handhelds.org
> http://handhelds.org/mailman/listinfo/bootldr
>
This archive was generated by hypermail 2.1.5 : Fri Jan 17 2003 - 17:47:03 EST