RedBoot> load -r -v -b 0x600000 vmlinuz-loft-2.6.18
Using default protocol (TFTP)
/
Raw file loaded 0x00600000-0x0071bfbb, assumed entry at 0x00600000
RedBoot> exec
Using base address 0x00600000 and length 0x0011bfbc
Uncompressing Linux.............................................................................. done, booting the kernel.
Linux version 2.6.18 (gs@gw-lap) (gcc version 3.4.4) #2 PREEMPT Wed Oct 11 19:12:42 EDT 2006
CPU: XScale-IXP42x Family [690541c1] revision 1 (ARMv5TE), cr=0000397f
Machine: Giant Shoulder Inc Loft board
Memory policy: ECC disabled, Data cache writeback
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.  Total pages: 16384
Kernel command line:  noirqdebug console=ttyS0,115200n8 root=/dev/hda1 rootfstype=ext2 rtc-ds1672.probe=0,0x68 rtc-ds1672.h0
IRQ lockup detection disabled
Unknown boot option `rtc-ds1672.hctosys=1': ignoring
PID hash table entries: 512 (order: 9, 2048 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 62464KB available (1960K code, 404K data, 88K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
IXP4xx: Using 16MiB expansion bus window size
PCI: IXP4xx is host
PCI: IXP4xx Using direct access for memory space
PCI: bus0: Fast back to back transfers disabled
dmabounce: registered device 0000:00:05.0 on pci bus
dmabounce: registered device 0000:00:05.1 on pci bus
dmabounce: registered device 0000:00:05.2 on pci bus
SCSI subsystem initialized
NET: Registered protocol family 2
IP route cache hash table entries: 512 (order: -1, 2048 bytes)
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 2048 bind 1024)
TCP reno registered
NetWinder Floating Point Emulator V0.97 (double precision)
JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
Initializing Cryptographic API
io scheduler noop registered
io scheduler deadline registered (default)
Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xc8000000 (irq = 15) is a XScale
serial8250.0: ttyS1 at MMIO 0xc8001000 (irq = 13) is a XScale
RAMDISK driver initialized: 4 RAM disks of 10240K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
IXP4XX-Flash.0: Found 1 x16 devices at 0x0 in 16-bit bank
 Intel/Sharp Extended Query Table at 0x0031
Using buffer write method
cfi_cmdset_0001: Erase suspend on write enabled
Searching for RedBoot partition table in IXP4XX-Flash.0 at offset 0xfe0000
21 RedBoot partitions found on MTD device IXP4XX-Flash.0
Creating 21 MTD partitions on "IXP4XX-Flash.0":
0x00000000-0x01000000 : ""
0x00000000-0x01000000 : ""
0x00000000-0x01000000 : ""
0x00000000-0x01000000 : ""
0x00000000-0x01000000 : ""
0x00000000-0x01000000 : ""
0x00000000-0x01000000 : ""
0x00000000-0x01000000 : ""
0x00000000-0x01000000 : ""
0x00000000-0x01000000 : ""
0x00000000-0x01000000 : ""
0x00000000-0x01000000 : ""
0x00000000-0x01000000 : ""
0x00000000-0x01000000 : "
"
0x00000050-0x00000850 : "RedBoot"
mtd: partition "RedBoot" doesn't start on an erase block boundary -- force read-only
0x00000850-0x00002050 : "zImage"
mtd: partition "zImage" doesn't start on an erase block boundary -- force read-only
0x00002050-0x00004050 : "jffs2"
mtd: partition "jffs2" doesn't start on an erase block boundary -- force read-only
0x0000fe50-0x00f0ff50 : "FIS directory"
mtd: partition "FIS directory" doesn't start on an erase block boundary -- force read-only
0x00130128-0x6f766097 : ".      ."
mtd: partition ".       ." extends beyond the end of device "IXP4XX-Flash.0" -- size truncated to 0xecfed8
mtd: partition ".       ." doesn't start on an erase block boundary -- force read-only
0x0063735f-0x0163735f : ""
mtd: partition "" extends beyond the end of device "IXP4XX-Flash.0" -- size truncated to 0x9c8ca1
mtd: partition "" doesn't start on an erase block boundary -- force read-only
0x00f0ff50-0x0100ff50 : "RedBoot config"
mtd: partition "RedBoot config" extends beyond the end of device "IXP4XX-Flash.0" -- size truncated to 0xf00b0
mtd: partition "RedBoot config" doesn't start on an erase block boundary -- force read-only
i2c /dev entries driver
ds1672 0-0068: chip found, driver version 0.3
ds1672 0-0068: rtc intf: sysfs
ds1672 0-0068: rtc intf: proc
ds1672 0-0068: rtc intf: dev (254:0)
ds1672 0-0068: rtc core: registered ds1672 as rtc0
TCP bic registered
NET: Registered protocol family 1
ds1672 0-0068: setting the system clock to 2006-10-12 11:26:54 (1160652414)
VFS: Cannot open root device "hda1" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)