linuxbios on geode gx1 with sst-39SF020A and CompactFlash [PMX:#]

[ramesh bios]

Ah, I had assumed that filo could only load an elf
image. Okay. Replaced that with a fresh bzImage with
early printk enabled. Looks to fail at the same point.
I noticed filo is now able to show the kernel version
and build date so I'd guess that this is getting
better. Here's the debug output. I'm not sure what to
look at next. Is it correct to expect to see the
kernel report it's version after the "Jumping to entry
point..."? I guess I should look for the code that
uncompresses the bzImage and see if there's any
problem with memory there. What do you guys think?

boot: hdc1:/bzImage root=/dev/hdc2 console=tty0
console=ttyS0,38400
malloc_diag: alloc: 288 bytes (5 blocks), free: 16088
bytes (1 blocks)
malloc_diag: alloc: 304 bytes (6 blocks), free: 16072
bytes (1 blocks)
file_open: dev=hdc1, path=/bzImage
find_ide_controller: found PCI IDE controller
1078:0102 prog_if=0x80
find_ide_controller: secodary channel: compatibility
mode
find_ide_controller: cmd_base=0x170 ctrl_base=0x374
ide_software_reset: Waiting for ide1 to become ready
for reset... ok
init_drive: Testing for hdc
init_drive: Probing for hdc
init_drive: LBA mode, sectors=250368
init_drive: Init device params... ok
hdc: LBA 128MB: TOSHIBA THNCF128MMG
init_drive: Testing for hdd
init_drive: Testing for hdd
devopen: Partition 1 start 32 length 12000
Mounted ext2fs
malloc_diag: alloc: 288 bytes (5 blocks), free: 16088
bytes (1 blocks)
elf_load: Not a bootable ELF image
malloc_diag: alloc: 304 bytes (6 blocks), free: 16072
bytes (1 blocks)
file_open: dev=hdc1, path=/bzImage
devopen: already open
malloc_diag: alloc: 288 bytes (5 blocks), free: 16088
bytes (1 blocks)
Found Linux version 2.6.8.1 (root at rambox) #12 Thu Jan
27 04:31:34 IST 2005 (protocol 0x203) (loadflags 0x1)
bzImage.
init_linux_params: Setting up paramters at 0x90000
set_memory_size: 00000000000006c8 - 00000000000a0000
set_memory_size: 0000000000100000 - 0000000003c00000
set_memory_size: ramtop=0x3c00000
set_memory_size: ext_mem_k=60416, alt_mem_k=60416
parse_command_line: original command line:
"root=/dev/hdc2 console=tty0 console=ttyS0,38400"
parse_command_line: kernel command line at 0x91000
parse_command_line: kernel command line (47 bytes):
"root=/dev/hdc2 console=tty0 console=ttyS0,38400"
load_linux_kernel: offset=0xc00 addr=0x100000
size=0x1b49ab
Loading kernel... ok
start_linux: eip=0x100000
Jumping to entry point...


--- "Ronald G. Minnich" <rminnich at lanl.gov> wrote:

> Before you do anything else, set your kernel up with
> CONFIG_EARLY_PRINTK
> 
> You'll get output you might not get otherwise.
> 
> > I
> > think filo isn't able to read the version info out
> of
> > the kernel for some reason. 
> 
> I don't think that is it. 
> 
> filo will work fine with a normal bzImage anyway,
> you don't really need 
> mkelfImage for filo
> 
> ron
> _______________________________________________
> Linuxbios mailing list
> Linuxbios at clustermatic.org
>
http://www.clustermatic.org/mailman/listinfo/linuxbios
> 



	
		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - You care about security. So do we. 
http://promotions.yahoo.com/new_mail