Re: Re: stuck with haret CF boot...

Hello Morgan,

I resurrected my CF and booted my H2200 from it.

The COMMAND line and fstab that I gave in the last email was wrong. I
thought I had copied it direct from the CF, but I was obviously wrong.

I am using haret-0.3.8.exe, while you are using haret-0.5.1.exe, so I am
not sure how valid my setup is for you.

(Probably a dumb question, but you did not mention that you unzipped
bootgpe-v0.8.4-h2200.tar.bz2 into the second partition of the CF.)

Following is the startup.txt and /etc/fstab, taken straight off the
first and second partitions, respectively, of the CF that I just
booted. Also, the partition information of the CF. The only
significant difference that I see is the order of fstab, and the fact
that I commented out the /dev/hda1 entry.

Is there perhaps a problem with the new version of haret?

Hope this helps.

Jack Dodds

set KERNEL zImage
set MTYPE 341
set CMDLINE "root=/dev/hda2 rootdelay=5 console=ttyS0,115200n8
console=tty0"
bootlinux

proc /proc proc defaults 0 0
sys /sys sysfs defaults 0 0
tmpfs /var tmpfs defaults 0 0
#
# Changed by Jack 2006-11-22 per wiki
#
#/dev/hda1 /media/cf auto
 defaults,sync,noauto,noatime,exec,suid 0 0
/dev/hda2 / ext2 defaults 1 1
/dev/mmcblk0p1 /media/card auto
 defaults,sync,noauto,noatime,exec,suid 0 0
 

   Device Boot Start End Blocks Id System
/dev/sdb1 1 21 5177 6 FAT16
/dev/sdb2 22 1011 245520 83 Linux

Morgan Read wrote:
> Below...
>
> Jack Dodds wrote:
>> Hello Morgan,
>>
>> I have successfully booted my H2200 from a CF. I'm now booting from SD,
>> but I kept some of the files from the CF, so I hope this helps:
>>
>> Your startup.txt CMDLINE is different from mine. I have:
>>
>> set CMDLINE "root=/dev/mmcblk0p2 rootdelay=5 console=ttyS0,115200n8
>> console=tty0"
>>
>> My /etc/fstab is also different (don't ask me to explain - I don't
>> remember the reasoning behind this!):
>>
>> /dev/mtdblock3 / jffs2 defaults 1 1
>> proc /proc proc defaults 0 0
>> sys /sys sysfs defaults 0 0
>> tmpfs /var tmpfs defaults 0 0
>> #
>> # Changed by Jack 2006-11-22 per wiki
>> #
>> #/dev/hda1 /media/cf auto
>> defaults,sync,noauto,noatime,exec,suid 0 0
>> /dev/hda2 / ext2 defaults 1 1
>> /dev/mmcblk0p1 /media/card auto
>> defaults,sync,noauto,noatime,exec,suid 0 0
>>
>> Note that the screen goes blank during the boot process for quite a
>> while - like 2 - 4 minutes.
> Well, perhaps all I need is a little more patience...
>
> But, isn't /dev/mmcblk0p2 for sd/mmc cards?
> http://handhelds.org/moin/moin.cgi/CardBoot#head-1f93f400f79f54a192be22a95e492347b299e4e7
>
> Like what you say you're booting now?
>
> Thanks,
> M.
>
>>
>> Good luck.
>>
>> Jack Dodds
>>
>>
>>
>>
>>
>> Morgan Read wrote:
>>> Hi Folks
>>>
>>> I figure the two most likely places I've stuffed up are writing
>>> /etc/fstab and startup.txt correctly...
>>>
>>> Here's what I've done -
>>>
>>> I've followed the instructions for a haret boot here:
>>> http://handhelds.org/moin/moin.cgi/CardBoot
>>>
>>> Got the tar file from:
>>> http://handhelds.org/familiar/releases/v0.8.4/install/download.html
>>> And ended up with a directory like (minus haret-0.5.1.exe
>>> startup.txt):
>>> [root_at_morgansmachine bootgpe-v0.8.4-h2200]# ls
>>> bootgpe-v0.8.4-h2200.jffs2 haret-0.5.1.exe startup.txt
>>> bootgpe-v0.8.4-h2200.tar.bz2 LAB-image-h2200.htc
>>> zImage-2.6.15-hh2-h2200
>>> [root_at_morgansmachine bootgpe-v0.8.4-h2200]#
>>>
>>> Got haret following this link:
>>> http://handhelds.org/moin/moin.cgi/HaRET
>>> From here:
>>> http://www.handhelds.org/~koconnor/haret/haret-0.5.1.exe
>>>
>>> Created startup.txt, like so:
>>> set KERNEL zImage
>>> set MTYPE 341
>>> set CMDLINE "root=/dev/hda2 rootdelay=5 console=tty0"
>>> bootlinux
>>>
>>> (With a return following the last line "bootlinux".)
>>>
>>> Formatted my CF card like so:
>>> [root_at_morgansmachine bootgpe-v0.8.4-h2200]# fdisk -l
>>>
>>> Disk /dev/sda: 40.0 GB, 40007761920 bytes
>>> ...
>>> Disk /dev/sdc: 4009 MB, 4009549824 bytes
>>> 124 heads, 62 sectors/track, 1018 cylinders
>>> Units = cylinders of 7688 * 512 = 3936256 bytes
>>> Disk identifier: 0x000a6aa7
>>>
>>> Device Boot Start End Blocks Id System
>>> /dev/sdc1 * 1 2 7657 6 FAT16
>>> /dev/sdc2 3 1018 3905504 83 Linux
>>> [root_at_morgansmachine bootgpe-v0.8.4-h2200]#
>>>
>>> (Both wince and linux can see what you'd expect them to see.)
>>>
>>> This is what /etc/fstab looks like:
>>> /dev/hda2 / ext2 defaults 1 1 proc
>>> /proc proc defaults 0 0
>>> sys /sys sysfs defaults 0 0
>>> tmpfs /var tmpfs defaults 0 0
>>> /dev/hda1 /media/cf auto
>>> defaults,sync,noauto,noatime,exec,suid 0 0
>>> /dev/mmcblk0p1 /media/card auto
>>> defaults,sync,noauto,noatime,exec,suid 0 0
>>>
>>> (With a return on the last line.)
>>>
>>> Copied with the following to /dev/sdc1:
>>> # cp startup.txt /mnt/sdc1/startup.txt
>>> # cp zImage-2.6.15-hh2-h2200 /mnt/sdc1/zImage
>>> # cp haret-0.5.1.exe /mnt/sdc1/haret.exe
>>>
>>> I put the CF card in the ipaq and haret seems to start ok:
>>> "Haret booting linux ..."
>>>
>>> Followed by a blank screen with some white text that's too quick to
>>> catch, but something looking like it might be a boot start, then the
>>> screen darkens (back light seems to go out) with the boot start
>>> messages still visible - then they disappear and I'm left with a blank
>>> screen.
>>>
>>> As, I said - I suspect my writing of either "startup.txt" or "fstab"
>>> to be at issue. Can anyone confirm and give me a pointer?
>>>
>>> Many thanks.
>>> Morgan.
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> H2200-port mailing list
>> H2200-port_at_handhelds.org
>> https://handhelds.org/mailman/listinfo/h2200-port
>
>

-- 
=================================================
This email is digitally signed using the Enigmail
and GnuPG packages (http://enigmail.mozdev.org), 
which can also be used by the recipient to verify
the digital signature.
=================================================