You didn't turn _off_ devfs support when you created your new kernel. Having it on is the default, and causes the symptoms you've seen.
Mark Post -----Original Message----- From: Murray Butler [mailto:[EMAIL PROTECTED]] Sent: Monday, February 10, 2003 2:17 PM To: [EMAIL PROTECTED] Subject: DASD problems under new 2.4.19 Hello all- I was hoping someone may enlighten me as to what I have not done or done wrong with my new kernel config. I went to the IBM site and downloaded the kernel, glibc and associated tools patches for the 2.4.19 kernel and glibc 2.2.5 and gcc 3.2 (no patches on gcc). I have run the compile of gcc, then the new glibc, then re-linked and done gcc again and followed with the rest of the toolchain and ending with the kernel. All compiled with the standard complaints about signed/unsigned and such, but no serious errors or fatalities. I moved the image and system.map, etc. into the /boot dir and ran zipl with the new image as teh target in the correct /boot dir. What I get when I boot is interesting, it boots normally, until I get to the device detection, then I get: dasd(eckd): /dev/dasdf ( 94: 20),0205@0a: 3390/0A(CU:3990/04) Cyl:1669 Head:15 Sec:224 dasd(eckd): /dev/dasdf ( 94: 20),0205@0a: DIAG210 returned VRDCRCCL = 04, VRDCC RTY = 82, VRDCCRFT = 82 dasd(eckd): /dev/dasdf ( 94: 20),0205@0a: XRC_supported reset because of missin g VM support dasd(eckd): /dev/dasde ( 94: 16),0204@09: (4kB blks): 239760kB at 48kB/trk comp atible disk layout dasd(eckd): /dev/dasdf ( 94: 20),0205@0a: 3390/0A(CU:3990/04): Configuration da ta read debug: dasdf: new level 3 as an example of my dasdf, also the next step of initialization gives me: dasd: waiting for responses... Partition check: /dev/dasd/0201:VOL1/ 0X0201: p1 /dev/dasd/0202:VOL1/ 0X0202: p1 /dev/dasd/0203:VOL1/ 0X0203: p1 /dev/dasd/0204:VOL1/ 0X0201: p1 /dev/dasd/0205:VOL1/ 0X0205: p1 dasd(eckd): We are interested in: CU 3880/00 dasd(eckd): We are interested in: CU 3990/00 dasd(eckd): We are interested in: CU 2105/00 dasd(eckd): We are interested in: CU 9343/00 dasd: Registered ECKD discipline successfully dasd(fba): FBA discipline initializing dasd(fba): /dev/dasda ( 94: 0),0200@05: 9336/10(CU:6310/80) 128MB at(512 B/blk ) debug: dasda: new level 3 this is MUCH different from the other boot which sees the devices as dasda, dasdb, dasdc, etc. The boot further succeeds in mounting the /dev/root device in read only as an ext2 partition, it goes on to fail while attempting to mount the / filesystem claiming that I have no such device. I come to the system maint prompt, if I enter the root passwd and look around in /dev, there are no devices for ti to mount whatsoever, no /dev/dasdb1, just /dev/dasd/0201/part1. I'm not sure of what I missed, but I must not have gotten something correct with the devfs, because it doesn't seem to be enumerating the devices correctly, or am I missing something more? Please contact me by personal e-mail if needed or if you need more detail of the problem. Thanks in advance, Murray Butler
