> > > -----Original Message----- > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > > Brad Hinson > > Sent: Monday, April 14, 2008 12:38 PM > > To: LINUX-390@VM.MARIST.EDU > > Subject: Re: FW: any help installing 4.4 for s390 (or s390x) on Z9- > BC? > > > > Hi Kelly, > > > > Does dmesg show any qeth-related errors during bootup? Also, do you > > get > > any errors when you perform the steps manually? i.e: > > > > echo 0.0.e200,0.0.e201,0.0.e202 > > /sys/bus/ccwgroup/drivers/qeth/group > > echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.e200/online > > > > Lastly, are you using the OSA in layer2 (OPTIONS='layer2=1' in > > ifcfg-eth0) or layer3 (ARP=no in ifcfg-eth0) mode? > > > > -Brad > > > Brad, > I don't see any qeth related messages at all when trying to boot the > installed image, but it may be failing due to volume group errors > before it gets that far. It lists all the DASD addresses, then panics > after the "Activation logical volumes" message with: > Kernel panic - not syncing: Attempted to kill init! > > > When trying to boot the installer via FTP, I get the messages below: > Qeth: loading qeth S/390 OSA-Express driver > Cat: /sys/devices/qeth/0.0.e200/if_name: No such file or directory > SIOCSIFNETMASK: No such device > SIOCSIFBRDADDR: No such device > > Thanks, > -Kelly
Oops, I didn't answer your other questions. Basically, I can't get any version of Centos up far enough to start messing with options like these, at least, not in any way that I know of. -Kelly ---------------------------------------------------------------------- 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
