Jill, I don't know why, but the kernel is not seeing your parmline: Command line is: We are running under VM
This is why you're getting the kernel panic. Could you post the contents of your lin exec, and where you got your kernel from? Mark Post -----Original Message----- From: Jill Grine [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 23, 2002 8:29 AM To: [EMAIL PROTECTED] Subject: Re: Subject: Kernel panic: VFS: Unable to mount root fs on 01: 00 Thanks for your response, Rob, but the website you have provided assumes OS/390 is running on the machine on which Linux is being installed. I am attempting to to run this under VM, and don't have OS/390 installed on this box. I hope all will forgive me for the following, it is the only way to convey the whole picture. ("lin" is a REXX that deletes any reader files, then reloads the LINUX files and executes.) parmfile: ramdisk_size=32768 dasd=200-202 root=/dev/ram0 ro ipldelay=30s CTCA 0E68 COUPLED TO TCPIP 0E69 CTCA 0E69 COUPLED TO TCPIP 0E68 Ready; T=0.48/0.56 09:11:54 lin 0000003 FILES PURGED RDR FILE 0103 SENT FROM LINUX1 PUN WAS 0103 RECS 019K CPY 001 A NOHOLD NOKEEP RDR FILE 0104 SENT FROM LINUX1 PUN WAS 0104 RECS 0001 CPY 001 A NOHOLD NOKEEP RDR FILE 0105 SENT FROM LINUX1 PUN WAS 0105 RECS 123K CPY 001 A NOHOLD NOKEEP 0000003 FILES CHANGED Linux version 2.2.16 ([EMAIL PROTECTED]) (gcc version 2.95.2 19991024 (releas e)) #1 SMP Fri Nov 3 09:38:59 GMT 2000 Command line is: We are running under VM This machine has no IEEE fpu Detected device 0E68 on subchannel 0000 - PIM = 80, PAM = 80, POM = FF Detected device 0E69 on subchannel 0001 - PIM = 80, PAM = 80, POM = FF Detected device 0191 on subchannel 0002 - PIM = 80, PAM = 80, POM = FF Detected device 0200 on subchannel 0003 - PIM = 80, PAM = 80, POM = FF Detected device 0201 on subchannel 0004 - PIM = 80, PAM = 80, POM = FF Detected device 0202 on subchannel 0005 - PIM = 80, PAM = 80, POM = FF (etc) Dected device 0120 on subchannel 000E - PIM = 80, PAM = 80, POM = FF Highest subchannel number detected (hex) : 000E SenseID : device 0E68 reports: Dev Type/Mod = 3088/08 SenseID : device 0E69 reports: Dev Type/Mod = 3088/08 SenseID : device 0191 reports: CU Type/Mod = 3990/C2, Dev Type/Mod = 3390/0A SenseID : device 0200 reports: CU Type/Mod = 3990/C2, Dev Type/Mod = 3390/0A SenseID : device 0201 reports: CU Type/Mod = 3990/C2, Dev Type/Mod = 3390/0A SenseID : device 0202 reports: CU Type/Mod = 3990/C2, Dev Type/Mod = 3390/0A SenseID : device 0009 reports: Dev Type/Mod = 3215/00 (etc.) SenseID : device 0120 reports: CU Type/Mod = 3880/01, Dev Type/Mod = 3370/00 Calibrating delay loop... 15.10 BogoMIPS SenseID : device 019D reports: CU Type/Mod = 3880/01, Dev Type/Mod = 3370/00 SenseID : device 0198 reports: CU Type/Mod = 3880/01, Dev Type/Mod = 3370/00 SenseID : device 0120 reports: CU Type/Mod = 3880/01, Dev Type/Mod = 3370/00 Calibrating delay loop... 15.26 BogoMIPS Memory: 257080k/262144k available (1088k kernel code, 0k reserved, 3976k data, 0 k init) Dentry hash table entries: 32768 (order 6, 256k) Buffer cache hash table entries: 262144 (order 8, 1024k) Page cache hash table entries: 65536 (order 6, 256k) debug: 16 areas reserved for debugging information debug: reserved 4 areas of 4 pages for debugging ccwcache VFS: Diskquotas version dquot_6.4.0 initialized POSIX conformance testing by UNIFIX Detected 1 CPU's Boot cpu address 0 cpu 0 phys_idx=0 vers=FF ident=0D0607 machine=7490 unused=0000 Linux NET4.0 for Linux 2.2 Based upon Swansea University Computer Society NET3.039 NET4: Unix domain sockets 1.0 for Linux NET4.0. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP TCP: Hash tables configured (ehash 262144 bhash 65536) Linux IP multicast router 0.06 plus PIM-SM Starting kswapd v 1.5 pty: 256 Unix98 ptys configured RAM disk driver initialized: 16 RAM disks of 32768K size loop: registered device at major 7 LVM version 0.8i by Heinz Mauelshagen (02/10/1999) lvm -- Driver successfully initialized md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8 Partition check: Kernel panic: VFS: Unable to mount root fs on 01:00 HCPGIR450W CP entered; disabled wait PSW 000A0000 8005684C -----Original Message----- From: Rob van der Heij [mailto:[EMAIL PROTECTED]] Sent: Monday, April 22, 2002 12:06 PM To: [EMAIL PROTECTED] Subject: Re: Subject: Kernel panic: VFS: Unable to mount root fs on 01: 00 >I followed SuSE's instructions on creating an IPL tape and used that for the >IPL of the LPAR. This worked fine - I did not get the "Kernel panic" >message this time. The only reason why I chose the DASD IPL volume (using >instructions that I got from another Manual) was because it was easier to >IPL from DASD than from tape. Should work though. Many reported that it works for them. Maybe check that you had the latest code from http://www.rvdheij.com/linuxipl.html If you get as far as this message it looks like Linux did pick up your parm line but failed to load the initrd. Any messages in that area? Do you get the message about the ramdisk found? Rob
