Re: Newbie -- s390 kernel build fails at fs/partitions/ibm.c
Richard Hitt wrote: I just got into debian-s390 last Friday after a couple of years doing kernel builds for various s390 distributions of RedHat, TurboLinux, and SuSE, and I'm trying to do a kernel build to correspond to the 2.4.17 kernel distributed with the debian 3.0 s390 distribution. I'm trying to make it as vanilla as possible, yet every time I do the image make, I get these error messages: Did you apply the s390 patches to the vanilla source tree? Not using them is known to cause build failures. You can get these S/390-specific patches from IBM's developerWorks or the kernel-patch-2.4.*-s390 Debian packages. However, the Debian S/390 patch packages are currently only available for kernel 2.4.17 and 2.4.19. The source code in the kernel-source-* Debian packages is basically Linus' source tree and does not include architecture-specific patches. So it probably won't build on anything but i386. Stefan
Re: Timer patch
Dennis Wicks wrote: Has anyone applied the timer patch from developer works to woody yet? Getting that on is one of the reasons I want to get to kernel version 2.4.17. Yes, I have compiled some kernels with the timer patch applied. I used the kernel sources from the package kernel-source-2.4.17, applied the S/390 patch from the package kernel-patch-2.4.17-s390 and then the timer patch from developerWorks. How about the other patches from the May 2002 stream? Our 2.4.17 is currently the August 2001 stream and will also stay at this level to avoid confusion. Jochen Röhrig will release a new kernel-image package for 2.4.17 soon which contains the latest patches from developerWorks and will hopefully be included in Debian 3.0r1. Once IBM releases S/390 patches for newer kernels we will create a Debian package with them. This package might also include the timer patch but it will not be enabled in the standard kernel. Greetings, Stefan Gybas
Re: Is anybody here?
Dennis Wicks wrote: I just joined this list yesterday and I haven't seen any traffic yet. Well, since you've asked your question about defining a CTC device on the LINUX390 mailing list, I have posted my answer there. You can also ask your questions on this list if you want to see more traffic here. :-) Greetings, Stefan Gybas
Re: Network Problem with S/390
[EMAIL PROTECTED] wrote: I want to install Debian Linux on S/390 and I have a Problem to connect the Network Interface. I want to use a Escon Connection. But it is not working. I install a SUSE Linux before and it works. Who can help me. Please post the complete netsetup dialog (especially the CTC chandev parameters) from your 3215/3270 console so we can see what's going wrong. Please post it to debian-s390@lists.debian.org instead of debian-boot, it's more appropriate there. Sorry, but we can't help you without knowing more details. Greetings, Stefan Gybas
Preparing NMU of debootstrap fot s390 boot-floppies
Hi! debootstrap needs some changes for the s390 boot-floppies: - the list of base and required packages should be adjusted, e.g. we are using kernel 2.4 and thus iptables is preferred over ipchains and we don't need the PPP packages - s390 is using devfs, so extracting devices.tar.gz is not a good solution (and these devices are i386-specific, anyway). I'll add devfs support which mounts devfs in $TARGET if it's mounted on the system that calls debootstrap and /usr/lib/debootstrap/devices.tar.gz is not present. Does anybody object to an NMU after further testing the patch on s390? -- Stefan Gybas
Re: Bug#129940: boot-floppies: S/390 (hercules): Can't find CTC adapter
On Sun, Jan 20, 2002 at 09:20:17PM +0100, Jochen Hein wrote: And I have instantly a running ctc0. Hm. I have found the bug, it was a missing line in the interactive CTC setup script. A new test version of the 3.0.19 root.bin can be found at http://people.debian.org/~sgybas/deb390/boot-floppies/root.bin-3.0.19 Please tell me if this works for you in interactive mode. -- Stefan Gybas
Re: Bug#129940: boot-floppies: S/390 (hercules): Can't find CTC adapter
Jochen Hein wrote: Uh, what's that protocol number? Shouldn't be there some explanation? Or is it documented in the cited manual? It's documented in the Red Book. I'm not sure if I should add some additional explanations because then nobody will read the manual and the protocol numbers might change. The default value will be used if you just press return, this works in most cases. What disturbs me something is that the search domain is derived from the hostnames domain. That ist mostly correct, and will work most of the time, but there may be situations where it is not what you want. Yes, that's true. But this script is only intended for a basic network setup - I'd like to minimize the number of questions. You can set up different DNS search domains in the network configuration to dbootstrap, after you make a telnet connection to your system. Please enter the read device numbers for your device in hexadecimal notation preceeded by 0x, e.g. 0x1000 or auto for automatic probing. However, auto probing might not work because OSA-2 cards use the same device type. Auto setup seems not to be automatic. Hm. I know, that's for the above reason. There's a documented way in the Red Book to force the kernel to allocate ctc interfaces, automatic setup works in this case. -- Stefan Gybas
boot-floppies 3.0.18 available
Hi! boot-floppies 3.0.18 for s390 have finally been installed into the Debian ftp archive. This version is based on kernel 2.4.16 which also supports ext3 so you can now do an installation with a journaling file system. You can download this version from any Debian mirror in the directory dists/woody/main/disks-s390/3.0.18-2002-01-16/. You need to get a kernel (either from the s390 directory for VM installations or from the s390-tape directory for LPAR installations), parmfile and root.bin. The Debian kernel has a special patch from Gerhard Tonn so it can read a second initial RAM disk. You can put IBM's OCO module on this second initrd and can install Debian with an OSA-2 (lcs) or OSA-Express (qdio/qeth) card this way. A script to create such a second initrd image can be obtained from the boot-floppies CVS or downloaded from http://people.debian.org/~sgybas/deb390/scripts/mkinitrd2-2416.sh . Instructions are at the beginning of this file, you need root access to a Linux system (any architecture) which supports loopback mounts. You can then use the debian.exec from the boot-floppies download area to IPL Debian from a VM reader. You need to rename the kernel to KERNEL.DEBIAN, the parmfile to PARMFILE.DEBIAN and root.bin to INITRD.DEBIAN when you do an FTP transfer to you VM system. Remeber to use binary mode for the kernel and initrd and a fixed record length of 80. If you have any questions or problems just send them to the debian-s390 mailing list. Please test this version (with and without OCO modules, VM and LPAR) and post your comments or bug reports. Thanks for your help! -- Stefan Gybas
Re: mklibs.sh
On Thu, Jan 10, 2002 at 08:18:00AM -0800, Donghwa Kim wrote: does any one know whether mklibs.sh has been tested on s390? Are you talking about the library reduction script from the boot-floppies? If so, yes it works on s390 and has been used for building boot-floppies. In newer boot-floppies versions we use mklibs.py as it is much faster than the shell script. Where can I find the newest version? In the boot-floppies CVS tree which is available through ViewCVS at http://cvs.debian.org/boot-floppies/scripts/rootdisk/ -- Stefan Gybas
Re: Installation under Hercules?
On Tue, Sep 11, 2001 at 09:32:15PM -0400, Matt Zimmerman wrote: I just replaced the kernel with the one from kernel-image-2.4.7-s390, and now it seems to be working. So as long as the next release of s390 boot-floppies uses kernel 2.4.7, it should be fine. Yes, boot-floppies will use 2.4.7 for s390 in the next release. Maybe IBM will release s390 patches for newer kernels before woody gets released, so we can switch to them. It looks like I spoke too soon. After formatting something over 148 cylinders, it oopsed again: We can't reproduce this on real hardware: Both 2.4.5 and 2.4.7 work fine there: I also formatted soms DASDs with these kernels without any problems at all. illegal operation: 0001 Very strange, but this looks like a bug in Hercules to me. -- Stefan Gybas
