Dietmar, When you say SLES7, I'm assuming you're using the 2.4 version, since you were talking about chandev, but I want to be sure. Are you running the GA code, or the beta code?
When I mentioned additional console messages, I'm talking about the messages at the very beginning of the IPL, such as these: Linux version 2.2.16 ([EMAIL PROTECTED]) (gcc version 2.95.2 19991024 (release)) #1 SMP Wed Nov 8 10 Command line is: dasd=10F,100,106,107,109,104,101,105,102,108,010A,010B,D0C,110 root=/dev/dasdb1 noi y ro We are running under VM This machine has no IEEE fpu Initial ramdisk at: 0x02000000 (16777216 bytes) Detected device 0009 on subchannel 0000 - PIM = 80, PAM = 80, POM = FF Detected device 000C on subchannel 0001 - PIM = 80, PAM = 80, POM = FF Detected device 000D on subchannel 0002 - PIM = 80, PAM = 80, POM = FF Detected device 000E on subchannel 0003 - PIM = 80, PAM = 80, POM = FF Detected device 0190 on subchannel 0004 - PIM = F0, PAM = F0, POM = FF Detected device 019E on subchannel 0005 - PIM = F0, PAM = F0, POM = FF Detected device 0319 on subchannel 0006 - PIM = F0, PAM = F0, POM = FF Detected device 0E00 on subchannel 0007 - PIM = 80, PAM = 80, POM = FF Detected device 0E01 on subchannel 0008 - PIM = 80, PAM = 80, POM = FF Detected device 0191 on subchannel 0009 - PIM = F0, PAM = F0, POM = FF Detected device 0100 on subchannel 000A - PIM = F0, PAM = F0, POM = FF Detected device 0101 on subchannel 000B - PIM = F0, PAM = F0, POM = FF Detected device 0102 on subchannel 000C - PIM = F0, PAM = F0, POM = FF You're right the IPL delay shouldn't matter under VM, that was only intended for use in an LPAR. Mark Post -----Original Message----- From: Dietmar Rueger [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 04, 2002 1:01 PM To: [EMAIL PROTECTED] Subject: Re: 3172 lcs problem Mark, thanks for responding ... We are running SLES7 in an LPAR under zVM 4.3, have several Linux machines connected to the net by an MP3K Eth adapter and to one another by a VMLAN, everything working fine. The real 3172 with 2 LANSTREAMER interfaces is meant as additional gateway(s) for additional Linux machines, but this beast doesn't like to start working like under VSE. I don't know what additional console messages you mean, what I thought to be device detection for this is included in my previous post (Starting lcs module ...). An IPLDELAY of 2m is specified, but I'm not sure whether this is useful under VM at all. Every (unsuccessful) startup leaves the used port (adapter) in a disconnected state from the network (green adapter LED blinking, front panel LED goes from 2202 to 2101, reboot necessary to retry), so any advice to retry <insmod> and then <ifconfig tr0 up> until success is merely impossible. As I said before, no idea how to go on ... Dietmar Rueger NMC Informationssysteme GmbH mailto:[EMAIL PROTECTED]
