Hello once again.
Yesterday, I was updating our Red Hat image. I fed some new network info
into the setup program and attempted to re-ipl. On boot-up, I was presented
with this:
"Ready; T=0.01/0.02 07:28:09
Ready; T=0.01/0.01 07:28:09
i 401
hwc low level driver: can write messages
hwc low level driver: can not read state change notifications
hwc low level driver: can read commands
hwc low level driver: can read priority commands
Linux version 2.4.9-13.4 (laroche@s390.redhat.de) (gcc version 2.95.3
20010315 (
release)) #1 SMP Thu Nov 15 13:16:06 CET 2001
We are running under VM
This machine has an IEEE fpu
On node 0 totalpages: 32768
zone(0): 32768 pages.
,
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: # default: off
# description: The talk server accepts talk requests for chatting with
users \
# on other systems.
service talk
{
disable = yes
socket_type = dgram
wait = yes
user = nobody
group = tty
server = /usr/sbin/in.talkd
}
Highest subchannel number detected (hex) : 000A
Calibrating delay loop... 398.95 BogoMIPS
Memory: 125308k/131072k available (1712k kernel code, 0k reserved, 850k
data, 64
k init)
Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes)
Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
,
Buffer-cache hash table entries: 8192 (order: 3, 32768 bytes)HCPGIR450W CP
enter
ed; disabled wait PSW 000A0000 80286216"
Instead of processing my parmfile, it looks like my boot record is
poiniting to an xinetd entry. Of course, this causes the ipl to fail
immediately. I can bring up the ramdisk that I used for installation and
mount the system disk there, but I don't know how to re-write the boot
record. Does this version of Red Hat have any boot loader similar to SuSE's
silo?
Thanks for all the help that you have all provided. Happy holidays.
Michael Lambert
