> > > > I therefore removed the "INPUT" goal from /etc/yaird/Default.cfg > > (since input devices on S/390 z/Arch is irrelevant) as well > > as anything relating to mouse, etc.. > > OK, manageable so far ... >
Agreed.. although something needs to be done about it - eventually (otherwise dependent packages just won't install) > > The following then occurs : > > > > # yaird -o /tmp/a 2.6.14-2-s390x > > yaird error: unsupported device required: dasda (fatal) > > > > As a consequence, I am unable to upgrade to the 2.6.14 kernel (since > > linux-image-2.6.14-3-s390x and linux-image-2.6.14-3-s390 > both insist on > > only using yaird). > > Could you post .. Most certainly... > * output of yaird --debug -o blah.img > * output of yaird --test > * output of ls -lR /sys under your old kernel Output attached - 3 files (with hopefully self-explanatory file names) If file attachment is not accepted by BTS, I will look in the FAQ on how to achieve this (I am no real expert in reporting bugs !) > * advice as to what modules you expect to be loaded to get dasda > operational s390/s390x may need (from what I can gather) - dasd_eckd_mod (ECKD Device support) < That's what I need in my particular case - dasd_fba_mod (FBA Device support) - dcssblk (z/VM Shared segment support - although I'm not sure if this can be used as a rootfs) - xpram (Expanded storage - same restriction as above) - zfcp (QDIO/Fiber Channel devices - SCSI over FC) Because of the architectural constraint related to S/390 & z/Arch these may be the only ones needed - all I/O is standardized on this architecture. > > You may also want to look at initramfs-tools. > I did (this option was suggested by the debian-s390 people) ! Although the initramfs gets built, it fails to boot (the module is not included as part of the ram root fs) > Thanks, > Erik > Of course, should you need more information, I'll be glad to provide you with anything you need ! Thanks for your help ! --Ivan
bug340344-1-isw.tgz
Description: application/compressed
