Re: Debian install problem
Maciek, > When I used the original ".ins" file from the Debian CD and changed the > filenames according to it, the installation went smoothly until the > first IPL. After the IPL I get a message from modprobe: > "can't locate module eth0". I am using OSA-2. > > Is it so because I didn't load the oco.bin file ? No, I don't think so. Since you are using a OSA-2 card this one should be lcs-based, not QDIO-based? Since lcs is open source you shouldn't need the OCO-modules. > I tried to find it on the net but it was nowhere to be found. > My distribution doesn't have it either... Debian doesn't distribute the OCO-ramdisk due to legal concerns. You can find a script for building the OCO-ramdisk on http://people.debian.org/~sgybas/deb390/scripts/ But anyway, you shouldn't need it. > I installed the base system over the network (through FTP) without any > problems. My parmfile doesn't contain any network parameters since I > wanted to enter them manually. Why did it work for the base > installation and why did it not work after the IPL ? Have a look at the end of /etc/modules.conf on your installed system. You should see something like alias tr0lcs #alias eth0 lcs alias eth0 qeth alias ctc0 ctc alias escon0 ctc alias iucv0 netiucv Try changing this to alias tr0lcs alias eth0 lcs #alias eth0 qeth alias ctc0 ctc alias escon0 ctc alias iucv0 netiucv (removing the # from the second line and putting it in front of the third line). Now the lcs-driver will be used for your ethernet card instead of the OCO qeth-driver (which probably is not installed on your system). This hopefully will fix your problem. Jochen Rvhrig - Debian S/390 Port ([EMAIL PROTECTED])
Re: Debian install problem
Maciek, > I prepared a CD to use it on my HMC with just 4 files: > kernel.debian > parmfile.debian > initrd.debian > debian.ins What are the contents of your debian.ins-file? The filenames must match the names of your kernel-, parmfile- and initrd-file, respectivly. However, if I remember correctly, the filenames must not be longer than 8 characters, which means you couldn't use the above names. I suggest to use the original Debian .ins-file as it can be found on the original Debian-CD and rename the kernel-, parmfile- and initrd-file accordingly: Without a 2nd ramdisk for OCO-modules: * Debian GNU/Linux for S/390 (boot from CD-ROM or FTP-Server) linux_vm 0x parmfile 0x00010480 root.bin 0x0080 Including a 2nd ramdisk for OCO-modules: * Debian GNU/Linux for S/390 (boot from CD-ROM or FTP-Server with OCO-Modules) linux_vm 0x parmfile 0x00010480 root.bin 0x0080 oco.bin 0x00c0 You could also have a look at the script, that generates the .ins-files for the official Debian-CD: http://cvs.debian.org/debian-cd/tools/boot/woody/boot-s390?rev=1.4&content-type=text/vnd.viewcvs-markup Jochen ([EMAIL PROTECTED])
Re: s390-tools needs ucd-snmp
On Fri, Dec 06, 2002 at 08:26:00AM +1000, Vic Cross wrote: > > And perhaps why there is a dependency on SNMP headers? osasnmpd attaches itself to ucd-snmpd using the AgentX interface therefore it needs some structures defined in the ucd-snmpd headers. Regards, Jochen
Re: s390-tools needs ucd-snmp
On Thu, Dec 05, 2002 at 05:12:03PM -0500, Post, Mark K wrote: > I'm trying to build the s390-tools for the May2002 stream. The code is > looking for ucd-snmp headers, specifically ucd-snmp/ucd-snmp-config.h, > ucd-snmp/ucd-snmp-includes.h, and ucd-snmp/ucd-snmp-agent-includes.h. I > found net-snmp 5.0.6 on SourceForge, but that package doesn't seem to have > everything necessary, even though it is supposed to be the replacement for > ucd-snmp. Could you try ucd-snmp 4.2.5 from http://prdownloads.sourceforge.net/net-snmp/ucd-snmp-4.2.5.tar.gz?download and consider the restrictions described on http://oss.software.ibm.com/linux390/restrictions2_4_17-may2002.shtml#s390toolsrestr20020531 Jochen
Re: mono RPMs
On Mon, Nov 11, 2002 at 02:39:05PM -0500, Matt Zimmerman wrote: > Have you tried the Debian packages for mono found here: > > http://www.debianplanet.org/mono/ They don't provide binaries for Debian/390 and the latest source-package is based in mono release 0.15 (Aug 23rd, 2002) which does not yet include Neale's patches. Probably the easiest way for just trying it out on Debian/390 is to build the latest snapshot-tarball from the mono CVS-repository (http://go-mono.com/snapshots/). Jochen Rvhrig ([EMAIL PROTECTED])
Re: mono RPMs
Neale, On Fri, Nov 08, 2002 at 01:36:47PM -0700, Ferguson, Neale wrote: > For those who'd like to play with the C# open-source package "mono", > the necessary RPMs can be downloaded from "http://go-mono.com/download";. > I don't think you need the -devel RPMs if you just want to play. What modifications did you do to get it running on 390? Do you have some patches or source-rpm's? On what system did you build the rpm's? SuSE? RedHat? What version? I'm just trying to get the alien-converted rpm's running on a Debian/390 system and unfortunately I only get a segfault when running mint on my sample program ... Jochen Rvhrig ([EMAIL PROTECTED])
Re: Compilation Failure for gdb 5.2
On Wed, Nov 06, 2002 at 04:15:52PM -0500, Post, Mark K wrote: > I'm trying to compile gdb 5.2 with gcc 2.95.3, glibc 2.1.3, and I'm getting > the following error: There are known problems with compiling gdb 5.2 on Linux/390 which should be fixed in gdb 5.2.1. Maybe hust give it a try ... Jochen Rvhrig
Re: Oh good, a kernel oops
On Tue, Jul 30, 2002 at 11:43:33 -0400, Adam Thornton wrote: > So obviously Debian isn't going to support it. Citing from a mail Stefan Gybas wrote yesterday on this list referring to the CONFIG_NET_FASTROUTE problem: > It was obviously changed in the OCO modules from 2002-06-17 > (qdio-2.4.17-s390-2.tar.gz and qeth-2.4.17-s390-2.tar.gz). The old > versions from 2002-02-18 (qdio-2.4.17-s390-1.tar.gz and > qeth-2.4.17-s390-1.tar.gz) work fine without CONFIG_NET_FASTROUTE > so these are the recommended modules for the Debian kernel. > > The Debian kernel was built and tested in May 2002 so we could not include > the latest patch from developerWorks (2002-06-12) and did not test the > latest OCO modules. Thanks for reporting this problem! So if you want to get a running Debian/390 with working qeth-support you should do the following: 1. Get the latest Debian/390 kernel image package from ftp://ftp.debian.org/debian/pool/main/k/kernel-image-2.4.17-s390/kernel-image-2.4.17-s390_2.4.17-2.1_s390.deb This is the kernel image that gets installed on your system when you install Debian/390 from scratch. 2. Install the kernel image package (if /lib/modules/2.4.17 exists, remove it or rename it to /lib/modules/2.4.17.old before installing the package): dpkg -i kernel-image-2.4.17-s390_2.4.17-2.1_s390.deb 3. Get the following module tarballs from the IBM Developerworks web site (http://oss.software.ibm.com/linux390/current2_4_17.shtml#oco-feb182002-31-exp): qdio-2.4.17-s390-1.tar.gz qeth-2.4.17-s390-1.tar.gz Note that these are not the latest modules - however these modules work and don't have the netdev_fastroute-problem. 4. Rename the modules contained in the tarballs to qdio.o and qeth.o respectively and copy them to /lib/modules/2.4.17/kernel/drivers/s390. Don't forget chown-ing them to root:root since otherwise you'll get problems when trying to load them. 5. Reboot your system. Hope this helps. Jochen -- [EMAIL PROTECTED]
Re: RedHat OCO Error
Moloko Monyepao wrote: > root@lnx1 patch]# tar -xzof redhat-oco-2.4.9-17-s390-2.tar.gz > redhat-oco/redhat-oco-2.4.9-17-2.tar.gz | tar -C / -xzf - lib I assume you try to execute the command from Section 3 of the RedHat-OCO-HowTo-1.pdf. There are 2 issues: - you must use capital "O" in the the options of the first tar-statement in order to extract to stdout (not small "o"); (that's why you get the "gzip: stdin: unexpected end of file"-message) - you must use "./lib" in the second tar-statement, not "lib" (this is a typo in the RedHat-OCO-HowTo-1.pdf) Jochen -- Dr. Jochen Röhrig Linux for eServer Development IBM Deutschland Entwicklung GmbH eMail: [EMAIL PROTECTED]
