Post that error here. I've got the initrd mounted can look to see what might be happening. There might be a bug there that I can try to fix and have you test.
If it fails, I'll ask you to do this then: bash -x /linuxrc and send me the output off-list. You'll have to do a fair amount of cutting and pasting, unfortunately, but you're the first person with an LCS device to try any of this. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Robin Murray Sent: Wednesday, October 06, 2004 12:41 PM To: [EMAIL PROTECTED] Subject: Re: chandev question i'm pretty sure i tried lcs0 and it gave me an error something like "couldn't find the lcs0 module", but i will try it again to make sure. if that fails then yes, i'll give red hat a try. thanks mark. Robin Murray Tel: (902) 453-7300 x4177 Cell: (902) 430-0637 "Post, Mark K" <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[EMAIL PROTECTED]> 10/06/2004 01:36 PM Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject: Re: chandev question Robin, I used the front end of Red Hat installer as the basis for mine, since I really liked the idea of being able to specify just about all the parms you need in the parmfile. (I improved it a little bit, too, to scan what was in /proc/cmdline instead of relying on environment variables getting set.) I would say that your parmfile should have this in it: CHANDEV=lcs0,0x5012,0x5013 That matches what is in IBM's Device Drivers and Installation Commands manual for Linux/390. If you're using something other than port 0, you'll need to specify that as well. If you don't have a copy, there's a pointer to it on linuxvm.org. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Robin Murray Sent: Wednesday, October 06, 2004 11:30 AM To: [EMAIL PROTECTED] Subject: chandev question i'm getting closer to getting slack390 install tape onto the network via my 2216. i'm getting: "chandev_setup unknown verb detected eth0,0x5012,0x5013 interpretted as eth0,0x5012,0x5013" both the flagged statement and what it interprets it as are identical. i'm also getting gobs of "device not found" errors for my 2216 devices. /proc/chandev has the devices listed /proc/subchannels have the devices listed as 3088/1f. shouldn't these be 3172 (which is how we have the devices defined in our iocds)? if so, is there a way to force them to the proper device type? my parameter file is: DASD=C103-C104 root=/dev/ram0 ro HOST=upgrlpar.maritimelife.ca:eth0:10.13.15.1:1500 NETWORK=10.13.15.1:255.255.255.0:10.13.15.255:10.13.15.2 DNS=10.10.1.101 CHANDEV=eth0,0x5012,0x5013 can anyone see what's wrong with this? ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
