Whether you like devfs or not, and use it or not, just keep in mind that if you ever install another kernel that comes straight from SuSE or Red Hat, that devfs will most likely be turned off, and you'll have a similar problem, just in reverse. I kind of like devfs myself, but I'm not sure I want to keep swapping back and forth between the two schemes.
Mark Post -----Original Message----- From: Dennis Wicks [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 11:00 AM To: [EMAIL PROTECTED] Subject: Re: Problem IPLing new 2.4.19 kernel Greetings; You probably have devfs enabled in your kernel. I think that is the default in 2.4.19 and probably earlier too. You can either rebuild your kernel and disable/turn off devfs or change your parmfile in /boot to something like root=/dev/dasd/0100/part1 ro noinitrd dasd=0100-010f,200-20f,300-30f and rerun zipl. You will also have to change any dev addresses in your fstab etc. that are the old /dev/dasda1 notation. It is a bit of a pain to make the conversion, but I personally like the devfs notation better. Good Luck! Dennis Alex Leyva <[EMAIL PROTECTED] To: [EMAIL PROTECTED] df.gob.mx> cc: Sent by: Linux on Subject: Re: Problem IPLing new 2.4.19 kernel 390 Port <[EMAIL PROTECTED] IST.EDU> 03/19/2003 09:39 AM Please respond to Linux on 390 Port I has the same problem, in my case its because the 2.4.19 kernel doesnt use the devices at /dev/dasdxxx, instead i have /dev/dasd/xxxx/, where xxxx is the address of the device, into the directory i have: # ls /dev/dasd/0200/ device disc part1 "Device Drivers and Installation Commands" have more info about this. On Wed, 19 Mar 2003, Rich Blair wrote: > Hello All. > Having trouble getting my new 2.4.19 kernel to IPL cleanly. > Upon IPLing things go fine up to a point. The last message that I get is > from fsck.ext2 which states: No such file or directory while trying to open > /dev/dasdb1. The superblock could not be read or does not describe a > correct ext2 filesystem...... I then end up in "filesystem repair mode" > > Here is the procedure I have followed: > Downloaded the 2.4.19 kernel from <outbind://34/www.kernel.org> > www.kernel.org > Downloaded and applied IBM patches: > Linux-2.4.19-s390-may2002 > Linux-2.4.19-s390-1-may2002 > Linux-2.4.19-s390-2-may2002 > Linux-2.4.19-s390-3-may2002 > Linux-2.4.19-s390-kerntypes-ma2002 > Linux-2.4.19.timer-1-may2002 > Next from the /usr/src/linux-2.4.19 directory: > make menuconfig; > make dep > make image > make modules > make modules_install > Copied /usr/src/linux-2.4.19/arch/s390/boot/image to /boot/kernel > Copied /usr/src/linux-2.4.19/arch/s390/boot/ipleckd.boot to /boot/kernel > Copied /usr/src/linux-2.4.19/System.map /boot/kernel > zipl > shutdown -r now. > Hopefully someone can straighten me out. > Thanks. > > Rich Blair | Mainframe Systems > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > ASG | <http://www.asg.com/> asg.com > 1333 Third Avenue South > Naples, Florida 34102 USA > > Tel: 239.435.2243 > Fax: 239.213.3717 > Toll Free: 800.932.5536 x2243 > -- Alejandro Leyva Rabinovich. Jefe de la Unidad Departamental de Soporte Ticnico (Administracisn de Mainframe). Direccisn General de Informatica. Secretarma de Finanzas. Gobierno del Distrito Federal.
