JS-20 and generic kernel 2.6.13.3

[Steve Millman]

Hi,
I have downloaded and compiled the generic Linux kernel 2.6.13.3 for my 
JS-20 PPC IBM BladeServer.  When I attempt to boot the new kernel I get 
the following output.  Has anyone successfully tried to run the generic 
2.6.13.3 kernel on a JS-20 or have any idea what I am doing wrong?  As a 
word of caution, I am a Kernel newbie, so I might have done, or omitted 
something stupid.

boot: newlinux
Please wait, loading kernel...
   Elf64 kernel loaded...
Loading ramdisk...
ramdisk loaded at 02300000, size: 1563 Kbytes
OF stdout device is: /vdevice/vty at 0
Hypertas detected, assuming LPAR !
command line: root=/dev/VolGroup00/LogVol00 ro console=hvc0 rhgb quiet
memory layout at init:
  memory_limit : 0000000000000000 (16 MB aligned)
  alloc_bottom : 0000000002487000
  alloc_top    : 0000000008000000
  alloc_top_hi : 000000001e000000
  rmo_top      : 0000000008000000
  ram_top      : 000000001e000000
Looking for displays
instantiating rtas at 0x0000000007a70000 ...rtas_ram_size = 2c8000
fixed_base_addr = 7a70000
code_base_addr = 7afa000
Code Image Load Complete.
registered vars:
name                              addr               size  hash align
--------------------------------  ----------------   ----  ---- -----
glob_rtas_trace_buf             : 0000000007ab9100  65552     7      0
prtas_was_interrupted           : 0000000007aca100      4     9      1
callperf                        : 0000000007aca400  12496     9      1
pglob_os_term_state             : 0000000007acd700      4    12      1
hypStopWatch                    : 0000000007ac9400   1800    14      8
prtas_in_progress               : 0000000007ac9e00      4    20      1
last_error_log                  : 0000000007acdc00   1024    30      0
nmi_work_buffer                 : 0000000007ace000   4096    31     12
 done
0000000000000000 : boot cpu     0000000000000000
0000000000000001 : starting cpu hw idx 0000000000000001... done
copying OF device tree ...
Building dt strings...
Building dt structure...
Device tree strings 0x0000000002788000 -> 0x0000000002788e7b
Device tree struct  0x0000000002789000 -> 0x000000000278f000
Calling quiesce ...
returning from prom_init
Found initrd at 0xc000000002300000:0xc000000002486c00
firmware_features = 0x55f
Starting Linux PPC64 2.6.13.3
-----------------------------------------------------
ppc64_pft_size                = 0x17
ppc64_debug_switch            = 0x0
ppc64_interrupt_controller    = 0x2
systemcfg                     = 0xc0000000003d0000
systemcfg->platform           = 0x101
systemcfg->processorCount     = 0x2
systemcfg->physicalMemorySize = 0x1e000000
ppc64_caches.dcache_line_size = 0x80
ppc64_caches.icache_line_size = 0x80
htab_address                  = 0x0000000000000000
htab_hash_mask                = 0xffff
-----------------------------------------------------
[boot]0100 MM Init
[boot]0100 MM Init Done
Linux version 2.6.13.3 (root at dyn9002211199.watson.ibm.com) (gcc version 
3.4.3 20
041212 (Red Hat 3.4.3-9.EL4)) #1 SMP Wed Jan 4 14:50:45 EST 2006
[boot]0012 Setup Arch
Top of RAM: 0x1e000000, Total RAM: 0x1e000000
Memory hole size: 0MB
Syscall map setup, 246 32 bits and 222 64 bits syscalls
PPC64 nvram contains 16384 bytes
Using default idle loop
[boot]0015 Setup Done
Built 1 zonelists
Kernel command line: root=/dev/VolGroup00/LogVol00 ro console=hvc0 rhgb 
quiet
scan-log-dump not implemented on this system
Red Hat nash version 4.1.18 starting
Unable to find device-mapper major/minor
File descriptor 3 left open
  Reading all physical volumes.  This may take a while...
File descriptor 3 left open
File descriptor 3 left open
  Found volume group "VolGroup00" using metadata type lvm2
  /dev/mapper/control: open failed: No such file or directorymount: error 
6 moun
ting ext3
mount: error 2 mountin
system:blade[7]>

Connection to host lost.



Thanks,
Steve Millman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ozlabs.org/pipermail/linuxppc64-dev/attachments/20060109/72f3e036/attachment.htm