[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Need help Booting 2.6.8!



Greetings;

I know someone must be running this version, but I can't get it to boot.

I have installed vmlinuz-2.6.8-2-s390 and initrd.img-2.6.8-2-s390
right from debian/testing. I think it is a problem with my
kernel parameters but I can't find the right combination.

The best results that I ever get end up like this:

devfs_mk_dev: could not append to parent for <NULL>0
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 1024 bind 2048)
NET: Registered protocol family 1
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
RAMDISK: cramfs filesystem found at block 0
RAMDISK: Loading 1580 blocks -1 disk- into ram disk... done.
VFS: Mounted root (cramfs filesystem) readonly.
Freeing unused kernel memory: 84k freed
initrd-tools: 0.1.77
/sbin/init: 363: cannot open bin/root: No such file
umount: bin: not mounted
/sbin/init: 365: cannot create proc/sys/kernel/real-root-dev: Directory
nonexistent
cat: proc/cmdline: No such file or directory
umount: proc: not mounted
pivot_root: No such file or directory
/sbin/init: 431: cannot open dev/console: No such file
Kernel panic: Attempted to kill init!
15:36:55 00: HCPGSP2629I The virtual machine is placed in CP mode due to a
SIGP stop from CPU 01.

I get these messages right after I boot:

00: Booting default...
Linux version 2.6.8-2-s390 (waldi@lophos) (gcc version 3.3.5 (Debian
1:3.3.5-6)) #1 SMP Tue Jan 25 11:22:37 CET 2005
We are running under VM (31 bit mode)
This machine has an IEEE fpu
Built 1 zonelists
Kernel command line: dasd=autodetect   BOOT_IMAGE=0
PID hash table entries: 256 (order 8: 2048 bytes)

Any assitance or suggestions greatly appreciated!

TIA!
Dennis
--
Dennis G. Wicks             Systems Programmer      dennisw@cdg.ws
Communications Data Group   Tel: (217)355-7117  Fax: (217)351-6994
102 S. Duncan Rd.
Champaign, IL  61822



Reply to: