RE: Ram Disk Rescue approach not booting Linux

 Marcus,

Thanks for the reply.

I don't have a camera that takes CF cards; I've tried reformatting the card
in PPC (don't have access to a true linux host + card reader at the moment)
and have attempted to reformat in Ramdisk Rescue. (Ramdisk Rescue only gives
me the option to format with linux file system, though.) As well as
following the base RDR wiki, I have tried the 'install to another CF card'
option as well. All of the aforementioned give the same result.

I've connected to the device, while it running RDR, over usbnet but am not
sure what utilities might be useful. (Attempting to 'ls' the contents of the
various partitions returns no information, for example. Is that normal?)

I've tried this with more than one CF card (same make and model). I have a
smaller SD card on order and will try with that. I'll let you know if I make
any progress.

Ben

-----Original Message-----
From: Marcus Brown [mailto:marcusbrutus_at_internode.on.net]
Sent: 30 April 2008 01:38
To: Benjamin Priestman
Cc: h2200-port_at_handhelds.org
Subject: Re: [H2200-port] Ram Disk Rescue approach not booting Linux

Ben,

It's hard to tell what the problem is.

The best I can suggest is that you use one of the following methods to
format your card:
(in order of preference)
1. camera
2. ppc (just blank the first "sector" using linux and then insert in wince
machine) 3. Ramdisk Rescue

Additionally, if you have another card (SD or CF), it might be an idea to
see if you can get that to work, and while you're there see what the logs
tell you when you insert the "bad" card.
If you have usbnet setup, you can even log in to Ramdisk Rescue while it's
running and tinker with the card there.

Marcus.

Benjamin Priestman wrote:
> My problem seems to the same or very similar to the one discussed here:
> http://www.handhelds.org/hypermail/h2200-port/52/5211.html. The
> resolution to this seemed to be updated kernal. Does anyone have any
> more information on this?
>
> The problem seems to be with the kernal recognising the CF cards I am
> using (1gb Kingston). Console text viewed over a serial connection
> (see
> below) shows the pcmcia card being detected but nothing further until
> the kernal attempts to load the root-fs, at which point it fails.
>
> From comparison with the ramdisk rescue logs, am I right in saying
> that we'd expect to see some additional lines relating to the ide
> properties of the card?
>
> Ben
>
> Serial Console output (My only deviation from the RR wiki guide was to
> increase the root delay from 5 to 240 seconds):
>
> PLinux version 2.6.15-hh2 (rw_at_sugarcube.dyndns.org
> <mailto:rw_at_sugarcube.dyndns.org>) (gcc version 3.4.4) #1 PREEMPT Tue
> Aug
> 15 01:58:33 CEST 2006
> CPU: XScale-PXA255 [69052d06] revision 6 (ARMv5TE)
> Machine: HP iPAQ H2200
> Memory policy: ECC disabled, Data cache writeback Memory clock:
> 99.53MHz (*27) Run Mode clock: 398.13MHz (*4) Turbo Mode clock:
> 398.13MHz (*1.0, inactive)
> CPU0: D VIVT undefined 5 cache
> CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
> CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
> Built 1 zonelists Kernel command line: root=/dev/hda1 rootdelay=240
> console=ttyS0,115200n8 console=tty0 PID hash table entries: 512
> (order: 9, 8192 bytes)
> Console: colour dummy device 80x30
> Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
> Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
> Memory: 64MB = 64MB total
> Memory: 61952KB available (2335K code, 455K data, 100K init)
> Mount-cache hash table entries: 512
> CPU: Testing write buffer coherency: ok
> NET: Registered protocol family 16
> usbcore: registered new driver usbfs
> usbcore: registered new driver hub
> hamcop: using irq 104-129 on irq 28
> input: samcop ts as /class/input/input0 SAMCOP DMA Driver, (c)
> 2003-2004 Simtec Electronics DMA channel 0 at c4904400, irq 120
> input: gpio-keys as /class/input/input1 Initialising wince bootloader
> suspend workaround NetWinder Floating Point Emulator V0.97 (double
> precision)
> JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
> Initializing Cryptographic API
> io scheduler noop registered
> pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq = 15) is a FFUART
> pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq = 14) is a BTUART
> pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq = 13) is a STUART
> pxa2xx-uart.3: ttyS3 at MMIO 0x41600000 (irq = 0) is a HWUART RAMDISK
> driver initialized: 16 RAM disks of 8192K size 1024 blocksize Battery
> interface for iPAQ h2200 series - (c) 2004 Szabolcs Gyurko Uniform
> Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 50MHz system bus speed for PIO modes; override with
> idebus=xx NAND device: Manufacturer ID: 0x98, Chip ID: 0x75 (Toshiba
> NAND 32MiB 3,3V 8-bit) Scanning device for bad blocks Using builtin
> partition definition Creating 4 MTD partitions on "NAND 32MiB 3,3V
> 8-bit":
> 0x00000000-0x00004000 : "HTC first-stage bootstrap"
> 0x00004000-0x00028000 : "HTC rescue bootloader"
> 0x00028000-0x00168000 : "second-stage loader"
> 0x00168000-0x02000000 : "root fs"
> usbmon: debugfs is not available
> pxa2xx_udc: version 4-May-2005
> input: h2200 buttons as /class/input/input2 i2c /dev entries driver
> I2C: i2c-0: PXA I2C adapter
> Driver for 1-wire Dallas network protocol.
> SAMCOP 1-Wire busmaster driver - (c) 2004 Szabolcs Gyurko 1-Wire
> driver for the DS2760 battery monitor chip - (c) 2004-2005, Szabolcs
> Gyurko
> dmabounce: registered device samcop sdi on platform bus samcop sdi:
> probe: irq=124 irq_cd=31 dma=0.
> samcop sdi: initialisation done.
> MediaQ 1188 chip detected, base IRQ 130 Advanced Linux Sound
> Architecture Driver Version 1.0.10rc3 (Mon Nov 07
> 13:30:21 2005 UTC).
> PXA2xx i2Sound: h2200 Audio activated
> ALSA device list:
> #0: iPAQ h2200 Audio [codec Philips UDA1380]
> NET: Registered protocol family 2
> IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP
> established hash table entries: 4096 (order: 2, 16384 bytes) TCP bind
> hash table entries: 4096 (order: 2, 16384 bytes)
> TCP: Hash tables configured (established 4096 bind 4096) TCP reno
> registered TCP bic registered
> NET: Registered protocol family 1
> Waiting 240sec before mounting root device...
> pccard: PCMCIA card inserted into slot 0
> pcmcia: registering new device pcmcia0.0
> Root-NFS: No NFS server available, giving up.
> VFS: Unable to mount root fs via NFS, trying floppy.
> VFS: Cannot open root device "hda1" or unknown-block(2,0) Please
> append a correct "root=" boot option Kernel panic - not syncing: VFS:
> Unable to mount root fs on
> unknown-block(2,0)
>
> ----------------------------------------------------------------------
> --
> *From:* h2200-port-bounces_at_handhelds.org
> [mailto:h2200-port-bounces_at_handhelds.org] *On Behalf Of *Benjamin
> Priestman
> *Sent:* 19 April 2008 12:23
> *To:* h2200-port_at_handhelds.org
> *Subject:* [H2200-port] Ram Disk Rescue approach not booting Linux
>
> Hi,
>
> I have recently got hold of an h2200 series iPaq with the intention of
> installing Linux on it. Before attempting to replace bootloaders, etc,
> (I am working from Windows host) I thought I would follow the Ram Disk
> Rescue approach as documented here:
> http://handhelds.org/moin/moin.cgi/RamdiskRescue
>
> I downloaded the recommended files (via firefox to Windows
> filesystem) and copied them to a (new, Kingston, Type I, 1GB) CF card
> inserted into the iPaq using ActiveSync in the following structure:
>
> /linux/
> rescue/
> ramdisk-rescue-0.6.4.rootfs.ext2.gz
> custom.txt
> zImage-2.6.15-hh2-h2200-20061028015932
> haret-0.3.8.exe
> startup.txt
> image/
> bootgpe-v0.8.4-h2200.tar
>
> All of the above files being downloaded from the links on the above
> page (I have only tried this with the GPE GUI).
>
> I successfully ran haret and booted into Ramdisk Rescue.
>
> I installed linux onto the same Cf card.
>
> The partition resizing operations reported successful.
>
> After about 50 mins the filesystem expansion reported successful and
> demanded a hard reset,
>
> I then used the stylus to rest the iPaq using the recessed reset
> button at the back (I assume this is what is meant by a hard reset).
>
> I then used File Explorer to navigate to the /linux directory on the
> CF card and ran the copy of haret that could now be found in that
> directory (not the copy in /linux/rescue). Also in that directory were
> a copy of startup.txt and zImage.
>
> I get the penguin and then the penguin with bloodshot eyes and then
> the iPaq screen goes blank (is still backlit - so not simply off!) and
> remains so until the battery dies or I reset the device again.
>
> I attach the RR-syslog.gz file created in /linux/rescue on the CF card
> (presumably from the initial boot to Ramdisk Rescue).
>
> Any suggestions?
>
> Regards,
>
> Benjamin Priestman
>
>
> ----------------------------------------------------------------------
> --
>
> _______________________________________________
> H2200-port mailing list
> H2200-port_at_handhelds.org
> https://handhelds.org/mailman/listinfo/h2200-port
Received on Wed Apr 30 2008 - 19:43:24 EDT